09-06-2011 02:06 PM
Did any one configure fillword for 8G port on DCX? If yes, can you post details as for what purpose you have configured. What happens, if it is not configured ? Any other useful information.
09-06-2011 02:27 PM
Yes i did, most of will config the fillword on 8g platform (Condor2 Golden Eye2).
Try help portcfgfillword in a cli session with your switch for an explination or google portcfgfillword for reasons why and what happens if you dont.
The 16G platform (Condor3) doesn't support this command as it autosets the right primitives.
09-06-2011 11:35 PM
The use of fillword on 8G depends on the type of device connected to the port. Where most devices work fine with the default setting of 0, some devices require other settings of the fillword-paramater. These requirements come from the manuals of these devices themselves. For example, the HP Flexfabric 8Gb modules require fillword mode 3 (-aa-then-ia; If ARBFF/ARBFF failed, then do IDLE/ARBFF). When configured wrong the port comes up but the performance is dramatically bad.
When operation the same port in 4Gb or slower, the fillword settings does not matter, regardless of the attached device. The fillword setting only applies to 8Gb capable ports running at 8Gb.
09-07-2011 06:05 AM
In my environment, we were having issues with our IBM SAN equipment logging into switches when the fill word was set to 0. After setting it to 3, everything was able to log in with no problems.
Our standard, going forward, is to set all the fill words to 3. We run a script after our code upgrade that changes all the ports.
09-07-2011 08:02 AM
the most common pattern for portCfgFillWord misconfiguration is "running 8G, unstable link or No_Sync, rapidly increasing enc_out/bad_os, but works fine if speed is fixed to 4G".
Industry best practice is to set portCfgFillWord mode 3 (ARB-ARB then IDLE/ARB) although some earlier 8G devices would require mode 0.
For more details please refer to Link Initialization and Fill Word Primitive Configuration brief (it's Brocade document but I only found it on HP web site): http://h30499.www3.hp.com/hpeb/attachments/hpeb/bl
Condor 3 ASIC detects proper fill word mode automatically hence portCfgFillWord command is not applicable on 16G platforms.
Hope this helps,