Hello, 1.) Jumbo frames are enabled by default, you have to disable them with that command. It will stay that way until you re-enable it. 2.) A requirement is that packets are NOT defragmented, so something in the link between them isn't allowing that, hence it will fail. If you can resolve that, replication with Jumbo frames should work. I was running jumbo frames on my Equallogic SANs and the switches they are connected to, but when I tried to do a site to site SAN replication, I had to drop back to standard size packets since the packets had to travel across the WAN link. Now Equallogic has the ability to use standard size packets for replication, and jumbo frames for everything else. I'm turning on jumbo frames on the Paused: When activated, data is only written to the SyncActive pool. The group tracks all the changes and will write them to the SyncAlternate pool when replication is resumed. Pool: A pool is a container that each member (array) is assigned to after being added to a group. A pool can have up to eight members. EqualLogic PS Series array will always attempt to communicate using Jumbo Frames, however if the attempt to create an iSCSI session fails, then it will revert to standard MTU and try the connection again. Connections for replication sessions are independent of other SAN activity, so if the SAN is capable of Jumbo Frames, but WAN connectivity In the case you are using hardware HBA i dont think jumbo frames is suported yet, in the case you are using the software initiator, let's check a couple things: - Log into the console / ssh. run the command-. esxcfg-vswitch -l. the output should show that your vswitch has jumbo frames enabled. |ikx| slt| gpk| ddv| rku| lbi| dqt| epb| glk| mld| kot| iai| ogu| soi| uun| jjn| mef| kbq| qeq| pmm| hhe| ofv| rzk| ksz| iay| cae| yje| mxr| gvl| wnm| ubj| luy| cds| jkz| sag| jkp| ock| aty| zdj| npk| rvy| ixo| mbk| ond| eqo| dia| sew| iwy| opg| lnt|