OPERATIONAL DEFECT DATABASE
...
...
**Cosmetic change request, no functional impact. Applicable to all Cat9K running IOS-XE*** Requesting to change the description of the keyword from "ASIC No" to "ASIC Instance No" in the following CLI. This is leading to confusion in field. Switch#sh pl hard fed active fwd-asic drops exceptions asic ? ASIC No <<<<<<<<<< should read as ASIC instance No. (ASIC + CORE combination) ! This ASIC # is actually the ASIC instance (0=ASIC 0 /CORE 0, 1= ASIC 0 /CORE 1, 2=ASIC 1/CORE 0 etc) and not really the ASIC# as it states in "show platform hardware fed active ifm mapping" Example below- Switch#sh pl soft fed active ifm mappings Interface IF_ID Inst Asic Core Port SubPort Mac Cntx LPN GPN Type Active GigabitEthernet1/0/1 0x8 2 1 0 0 0 4 4 1 101 NIF Y GigabitEthernet1/0/2 0x9 2 1 0 1 1 4 4 2 102 NIF Y <<< Inst 2, ASIC 1, CORE 0 ! To get fwd-asic exception stats from respective instanced, we should put "2" in below CLI. However, the CLI description says "ASIC no" and hence engineers/customers ending up using wrong values (for example, they are using the value 1 here in this context, as indicated by IFM mapping output) . If the description is read as "ASIC instance no." as opposed to "ASIC no.", it would be helpful. Switch#sh pl hard fed active fwd-asic drops exceptions asic ? ASIC No <<<<<<<<<<<<<<<<<<<<<< Switch#sh pl hard fed active fwd-asic drops exceptions asic 2 ****EXCEPTION STATS ASIC INSTANCE 2 (asic/core 1/0)**** <<<<<
NA
NA
Cosmetic change request, no functional impact
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
