Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Some article numbers may have changed. If this isn't what you're looking for, try searching all articles. Search articles

Article Number: 000058360

Connectrix Brocade B-Series: ED-DCX6 upgrades from v8.1 to 8.2.x may create a condition that allows the VF configuration file PORTMAP entry to exceed its character limitation, causing a panic.

Summary: ED-DCX6 upgrades from v8.1 to 8.2.x may create a condition that allows the VF configuration file PORTMAP entry to exceed its character limitation, causing a panic.

This article may have been automatically translated. If you have any feedback regarding its quality, please let us know using the form at the bottom of this page.

Article Content

Symptoms

Firmware download between FOS v8.1.x and FOS v8.2.x

Impact:   
  • Director switch cold recovery
  • User performs lscfg operation, which fails with PMGR-1006 raslog event
Environment:   
Dell EMC Hardware: Connectrix ED-DCX6-4B
Dell EMC Hardware: Connectrix ED-DCX6-8B
Dell EMC Software: Connectrix B-Series Fabric OS (FOS) 8.1
Dell EMC Software: Connectrix B-Series Fabric OS (FOS) 8.2

Issue:   
Upgrading from FOS 8.1.x to FOS 8.2.x may create an invalid set of port ranges in the PORTMAP entry of the virtual fabric (VF) configuration file.
This can only occur on X6-8 or X6-4 director switches after upgrading to FOS 8.2.0 or later versions from an earlier FOS version, and the PORTMAP entry grows in size >= 1024.

PORTMAP entry size can only grow beyond 1024 characters after using the "lscfg" CLI command repeatedly moving ports between logical switches. The current PORTMAP entry size is calculated by:   
  • Using CLI command configupload -vf, locate the uploaded configuration file, then grep PORTMAP <uploaded-configuration-filename>" and count the characters starting from "F" or "G" to the ending "]" character.
X6-8 or X6-4 director switches shipped from the factory with FOS 8.2.0 or later already installed will not be exposed to this issue unless they were downgraded to a version of FOS before 8.2.0 and then upgraded again to FOS 8.2.0 or later.

Symptom:   
NON - VF enabled switches:   
  • Users that do NOT have VF enabled will not see any external symptoms.
  • An examination of the PORTMAP entry in the VF configuration may show invalid port numbers in the table map, but without VF enabled, these invalid port number entries will not impact the operation of the switch.
  • Any port numbers between 1800 and 3399 are considered "invalid entries."
  • These will not impact a system without VF. However, if logical fabrics are in use, or there are plans to enable logical fabrics at a future time, then these invalid entries should be removed.
Any character limit above or approaching 1024 should be reduced to resolve or prevent the above-mentioned symptoms after the character limit is reached.

VF enabled switches:   
Users that have VF enabled will only see an impact if the size of the PORTMAP entry in the VF configuration file grows above 1024 entries.
This can happen if the repeated movement of ports from one logical switch to another happens. The size of the table is verified by the Admin to determine if they are approaching the failure point.

Check the PORTMAP:   
    1. As admin user, run command configupload -vf. The output can be used to see the PORTMAP entries in the VF configuration file.
    It shows both the FC and the GE PORTMAPs, and it shows PORTMAPs for all logical switches.
    1. To manually check the 1024 limit, count characters from the "F" or "G" to the final "]" or Contact Support.
    Example:   
    The FC PORTMAP from the example file that is uploaded below has 528 characters.
    The GE PORTMAP from the example file that is uploaded below has 510 characters.

    Symptoms before the character limit is reached:    

    Example of uploaded file:    
    # BROCADE
    # VERSION 822
    # PLATFORM 166
    # SWITCHCONF
    SYSTEM max
    ATTRIBUTE SYS_NAME:sw0
    ATTRIBUTE VF:0
    ATTRIBUTE ETHSW_ENABLED:0
    ATTRIBUTE BLADE_IDS1:00afafbab20000
    ATTRIBUTE BLADE_IDS2:b1b10000000000
    SWITCH fcsw-0
    ATTRIBUTE FID:128 SWNAME:sw0 USR:3400 GE:256 ICL:128 DS:1 TID:775683370
    PIN 5
    PORTMAP FC:[0-447,768-895,1152-1215,1816-1823,1848-1855,1880-1887,1912-1919,1944-1951,1976-1983,2008-2015,2040-2047,2072-2079,2104-2111,2136-2143,2168-2175,2200-2207,2232-2239,2264-2271,2296-2303,2328-2335,2360-2367,2392-2399,2424-2431,2456-2463,2488-2495,2520-2527,2552-2559,2584-2591,2616-2623,2648-2655,2680-2687,2712-2719,2744-2751,2776-2783,2808-2815,2840-2847,2872-2879,2904-2911,2936-2943,2968-2975,3000-3007,3032-3039,3064-3071,3096-3103,3128-3135,3160-3167,3192-3199,3224-3231,3256-3263,3288-3295,3320-3327,3352-3359,3384-3391]
    PORTMAP GE:[0-255,1816-1823,1848-1855,1880-1887,1912-1919,1944-1951,1976-1983,2008-2015,2040-2047,2072-2079,2104-2111,2136-2143,2168-2175,2200-2207,2232-2239,2264-2271,2296-2303,2328-2335,2360-2367,2392-2399,2424-2431,2456-2463,2488-2495,2520-2527,2552-2559,2584-2591,2616-2623,2648-2655,2680-2687,2712-2719,2744-2751,2776-2783,2808-2815,2840-2847,2872-2879,2904-2911,2936-2943,2968-2975,3000-3007,3032-3039,3064-3071,3096-3103,3128-3135,3160-3167,3192-3199,3224-3231,3256-3263,3288-3295,3320-3327,3352-3359,3384-3391]

    The PORTMAP can also be found in the RAS supportsave file. (Not RAS_POST; RAS only.)

    It may appear multiple times because the supportsave does a 'cat' of vf-conf.<swbd>, switch-conf.<swbd>, and .save files. The 'cat' of vf-conf.<swbd> is the best file to use.
     
    Example from supportsave file switch0-xxx.xxx.xx.xxx-S1cp-202001152137.RAS.txt:    
    ********************************************************
    SWITCHCMD /bin/cat /etc/fabos/config/vf-conf.166:
    ********************************************************
    /bin/cat /etc/fabos/config/vf-conf.166:
    SYSTEM max
    ATTRIBUTE SYS_NAME:sw0
    ATTRIBUTE VF:0
    ATTRIBUTE ETHSW_ENABLED:0
    ATTRIBUTE BLADE_IDS1:00afaf00000000
    ATTRIBUTE BLADE_IDS2:b1b10000000000
    SWITCH fcsw-0
    ATTRIBUTE FID:128 SWNAME:sw0 USR:3400 GE:256 ICL:128 DS:1 TID:901059396
    PIN 5
    PORTMAP FC:[0-447,768-895,1152-1215,1816-1823,1848-1855,1880-1887,1912-1919,1944-1951,1976-1983,2008-2015,2040-2047,2072-2079,2104-2111,2136-2143,2168-2175,2200-2207,2232-2239,2264-2271,2296-2303,2328-2335,2360-2367,2392-2399,2424-2431,2456-2463,2488-2495,2520-2527,2552-2559,2584-2591,2616-2623,2648-2655,2680-2687,2712-2719,2744-2751,2776-2783,2808-2815,2840-2847,2872-2879,2904-2911,2936-2943,2968-2975,3000-3007,3032-3039,3064-3071,3096-3103,3128-3135,3160-3167,3192-3199,3224-3231,3256-3263,3288-3295,3320-3327,3352-3359,3384-3391]
    PORTMAP GE:[0-255,1816-1823,1848-1855,1880-1887,1912-1919,1944-1951,1976-1983,2008-2015,2040-2047,2072-2079,2104-2111,2136-2143,2168-2175,2200-2207,2232-2239,2264-2271,2296-2303,2328-2335,2360-2367,2392-2399,2424-2431,2456-2463,2488-2495,2520-2527,2552-2559,2584-2591,2616-2623,2648-2655,2680-2687,2712-2719,2744-2751,2776-2783,2808-2815,2840-2847,2872-2879,2904-2911,2936-2943,2968-2975,3000-3007,3032-3039,3064-3071,3096-3103,3128-3135,3160-3167,3192-3199,3224-3231,3256-3263,3288-3295,3320-3327,3352-3359,3384-3391]


    Symptoms after the character limit is reached:    
    pdmd and hasmd panic symptoms:   
    The standby CP2 takes over by initiating a reboot to CP1 due to a pdmd panic.

    A hasmd panic is then triggered on CP2 resulting in a double Processor Reboot on the switch and subsequent cold recovery.
    1. Active CP1 panic pdm
    [KSWD-1002], 204763/5877, SLOT 1 | FFDC | CHASSIS, WARNING, , Detected termination of process pdmd:2942
    [HAM-1014], 204765/5878, SLOT 1 | CHASSIS, CRITICAL, , Non restartable component (pdm (pid=2942)) died
    1. Standby CP2 takeover, but standby CP2 also panics with hasmd
    [HAM-1004], 152469/1316, SLOT 2 | CHASSIS, INFO, BPGLCG01SL35V, Processor rebooted - Reset., reboot.c
    1. Active CP comes up reset standby and Cold recovery.
    [EM-5012], 204809/0, SLOT 1 | CHASSIS, INFO, BPGLCG01SL35V, start emd FSS_RECOV_COLD
    [HAM-1004], 5879, SLOT 1 | CHASSIS, INFO, BPGLCG01SL35V, Processor rebooted - Reset.
    [HAM-1004], 5942, SLOT 2 | CHASSIS, INFO, BPGLCG01SL35V, Processor rebooted - Reset.
    • Switchshow may have ports that are persistently disabled with an Area has been acquired status:    
    BASE:FID128:admin> switchshow | grep Area
    256 1 32 338840 N16 No_Sync Disabled (Persistent) (Area has been acquired)
    258 1 34 338a40 N16 No_Sync Disabled (Persistent) (Area has been acquired)
    264 1 40 338040 N16 No_Sync Disabled (Persistent) (Area has been acquired)
    266 1 42 338240 N16 No_Sync Disabled (Persistent) (Area has been acquired)
    268 1 44 338440 N16 No_Sync Disabled (Persistent) (Area has been acquired)
    270 1 46 338640 N16 No_Sync Disabled (Persistent) (Area has been acquired)
    272 2 32 339840 N16 No_Sync Disabled (Persistent) (Area has been acquired)
    [truncated]
    • lscfg show output could show that ALL ports are with -1 status:    
    SW0:FID128:admin> lscfg --show
    Created switches FIDs(Domain IDs): 128(ds)(51) 127(51) 100(51) 77(51)
    Slot 1 2 3 4 5 6 7 8 9 10 11 12
    -------------------------------------------------------------------------------
    Port
    0 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    1 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    2 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    3 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    4 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    5 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    6 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    7 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    8 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    9 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    10 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    11 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    12 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    13 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    14 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    15 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    16 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    17 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    18 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    19 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    20 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    21 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    22 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    23 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    24 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    25 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    26 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    27 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    28 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    29 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    30 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    31 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    32 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    33 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    34 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    35 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    36 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    37 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    38 | | | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 |
    • An HAfailover fails with the following error when the lscfg --show output is in this state:    
    hafailover >>>
    can t failover because system is not ready yet or other LS/HA config is in progress.

    Hashow >>>
    Local CP (Slot 6, CP0): Active, Cold Recovered
    Remote CP (Slot 7, CP1): Standby, Faulted
    HA enabled, Heartbeat Up, HA State synchronized

    Cause

    FOS 8.2.x has a larger PORTMAP buffer size to enable support for FCOE ports. The data that is synchronized from FOS 8.1.x during HA is smaller in size and may lead to corrupted data being observed in the higher port ranges.

    Resolution

    Resolution:    
    A nondisruptive process to repair the PORTMAP entries in the VF configuration file can be performed but requires ROOT access to issue the required commands to repair the PORTMAP entries. 

    Contact Brocade Support if the PORTMAP entries are growing (GE or FC) near the 1024 size limit.

    The set of commands to repair the PORTMAP entries in the VF configuration file can then be provided after examining a SupportSave from the switch.

    Alternatively, a DISRUPTIVE recovery process can be followed for users that do not have ROOT access to their switch:   
    1. Run command configupload -vf.
    2. Manually modify the uploaded VF config file to NOT contain ranges that have port numbers between 1800 and 3399.
    3. Run command configdownload -vf (using the modified VF config file).
    This will result in an automatic cold reboot of the switch as the new repaired PORTMAP is installed.

    Workaround:   
    1. Directly upgrade to FOS 8.2.2b or later from FOS 8.1.x.
    2. If the chassis is upgraded to a version before FOS 8.2.x already and VF is disabled, no action is required.
    3. If the chassis is upgraded to a version before FOS 8.2.x already and VF is enabled with no ports movements between logical fabrics planned, no immediate action is required.
    4. If the chassis is upgraded to a version before FOS 8.2.x already and VF is enabled with ports movements between logical fabrics planned using lscfg, contact Brocade Support to check and clean up the PORTMAP entries in the VF configuration file.

    Article Properties

    Affected Product

    Connectrix

    Product

    Connectrix, Connectrix ED-DCX6-4B, Connectrix ED-DCX6-8B

    Last Published Date

    25 Jun 2021

    Version

    3

    Article Type

    Solution

    Back to Top