Products Affected | Top Assembly | Printed Circuit Assembly | Comments | Hardware Revision | ||
---|---|---|---|---|---|---|
Part Number | Rev | Part Number | Rev | |||
PA-8T1 | ALL | ALL | ALL | ALL | All versionsof this PA are affected only when installed in the noted VXR series chassis. | ALL |
NPE-G2 | 68-2588-03 | ALL | 73-10329-03 | ALL | Units manufactured under deviation D087457 or D087915 are NOT affected. | Less than 1.2. |
NPE-G2 | 68-2588-02 | ALL | 73-10329-02 | ALL | Units manufactured under deviation D087457 or D087915 are NOT affected. | Less than 1.2. |
PA-MC-2E1/120 | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MC-2T3+ | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MC-2T3-EC | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MC-4T1 | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MC-8T1 | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MC-8TE1+ | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MC-E3 | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MC-STM-1MM | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MC-STM-1SMI | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MC-T3-EC | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MCX-2TE1 | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MCX-8TE1 | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-POS-OC3MM | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-POS-OC3SMI | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-POS-OC3SML | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
CISCO7204VXR | 800-04766-11 | A0 | 73-3905-09 | A0 | Some hardware versions above 2.7 are also affected. Refer to How to Identify Hardware Levels section for more details. | 2.7 and lower (see comments). |
CISCO7204VXR-DC | 800-04766-11 | A0 | 73-3905-09 | A0 | Some hardware versions above 2.7 are also affected. Refer to How to Identify Hardware Levels section for more details. | 2.7 and lower (see comments). |
PA-MC-2T1 | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MC-8E1/120 | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
PA-MC-T3 | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
CISCO7206VXR | 800-04667-11 | A0 | 73-3223-11 | A0 | Some hardware versions above 2.7 are also affected. Refer to How to Identify Hardware Levels section for more details. | 2.7 and lower (see comments). |
CISCO7206VXR-DC | 800-04667-11 | A0 | 73-3223-11 | A0 | Some hardware versions above 2.7 are also affected. Refer to How to Identify Hardware Levels section for more details. | 2.7 and lower (see comments). |
PA-MCX-4TE1 | ALL | ALL | ALL | ALL | All versions of this PA are affected only when installed in the noted VXR series chassis. | ALL |
NPE-G2 processors manufactured under the above noted assembly and revision numbers have been found to have compatibility issues with specific revisions of Cisco 7204VXR and 7206VXR chassis and the above noted Port Adaptors. A limited number of chassis manufactured beyond the above noted assembly and revision numbers may also be subject to the compatibility issue.
All three (3) of the following conditions must be present for the compatibility issues to occur:
1. The revision of the NPE-G2 used is noted in the Products Affected section above.
2. At least one (1) of the Port Adaptors noted in the Products Affected section is plugged into the chassis.
3. An earlier-revision Cisco 7200VXR series chassis is used. Refer to the How to Identify Hardware Levels section for more details.
This field notice does not apply if any one (1) of these three (3) conditions is not present.
The above noted revisions of the NPE-G2 have been found to be incompatible with earlier revision Cisco 7204VXR and 7206VXR chassis when used in conjunction with the specific port adaptors noted above. The affected NPE-G2 processors were manufactured with a PCI bridge component that is not compatible with the PCI bridge component used in the earlier revision 7204VXR and 7206VXR chassis. The PCI bridge component used in the affected chassis has been found to manipulate PCI data transactions to the PCI bridge on the NPE-G2 in such a way that the data transactions can become corrupted. This data corruption will lead to a failure of the port adaptor and a possible system crash.
This issue mostly affects the noted revisions of the NPE-G2 processor when installed in 7200 VXR series chassis manufactured under the above noted top assembly numbers (TAN) and hardware revision number ranges (2.7 and below). A limited number of chassis with TAN and hardware revisions above 2.7 are also affected. An IOS command is available to verify if the suspect chassis is affected with this issue. Most of the affected chassis were shipped prior to (approximately) February 2004.
Problem symptoms associated with this issue include line protocol flaps and output drops on the affected Port Adaptors. Excessive CPU utilization and router crashes have also been observed. The following example shows output of the show controllers
command on the PA-MC-2T3+ port adaptor. Malformed packets at the "Freedm FIFO" buffer is a typical symptom that has been observed with this issue.
Example of Malformed Packets on the Freedm FIFO Buffer of the PA-MC-2T3+
Router#show controllers
[Output Omitted for Brevity]
2CT3+ SW Controller 3/0
ROM ver 0x10000, h/w ver 0.2.2, f/w ver 2.5.1, FREEDM rev 1
T3 linestate is Up, T1 linestate 0x0BE1F5BA, num_active_idb 21
Buffer pool size 640, particle size 512, cache size 640, cache end 107/89
Rx desctable 0x38552FA0, shadow 0x4C13A98, size 512, spin 128
rx queue 0x38566000, cache 0x38566000, fq base 0x38566800
rdq base 0x38566000, host_rxrdqr 0x385663D0, host_rxfqw 0x38566C08
Tx desctable 0x38554FE0, shadow 0x4C03A64, size 4096, spin 256
tx queue 0x38568000, cache 0x38568000
IDB type=0x16, status=0x0, fastsend 0x0
host_txrdqw 2523, fq base 0x3856C000, host_txfqr 0x3856F5C4
dynamic txlimit threshold 4096
TPD cache 0x4C14A00, size 4096, cache end 4059/4059, underrun 0
RPD cache 0x4C142CC, size 448, cache end 0
Freedm fifo 0x4BF4148, head ptr 0x4BF4AA8, tail ptr 0x4BF593C, reset 0
Freedm fifo corrupted count = 0, Malformed packets = 5400975 <-----Malformed Packets at Freedm fifo
PCI bus 6, PCI shared memory block 0x38550644, PLX mailbox addr 0xE0840040
FREEDM devbase 0xE0800000, PLX devbase 0xE0840000
Rx overruns 0, Tx underruns 0, tx rdq count 36
Tx bad vc 0
unprov_partial_packet 0
Firmware clock reliability 11/10
FREEDM err: cas 0, hdl 0, hdl_blk 0, ind_prov 0, tavail 0, tmac busy 0, rmac busy 0
rxrdq_wt 0xF5, rxrdq_rd 0xF4, rxsfq_wt 0x302, rxsfq_rd 0x313
[Output Omitted for Brevity]
There is no workaround for this issue. Replacement of the NPE-G2 Network Processing Engine is required.
NPE-G2 must be replaced through standard RMA process.
To follow the bug ID link below and see detailed bug information, you must be a registered customer and you must be logged in.
DDTS | Description |
---|---|
CSCsd44501 (registered customers only) | Line Protocol Flaps for PA CT3,CE3, MC-8TE1 With any Serial Encapsulation |
The affected hardware can be identified through the following steps. Refer to the Products Affected section of this field notice above for details on the revision levels affected by this issue.
Hardware Identification Summary
Step A | Step B | Step C | Step D | Step E |
---|---|---|---|---|
Confirm Physical Configuration of 7204VXR or 7206VXR Router |
Verify NPE-G2 Hardware Revision |
Verify the 7204VXR or 7206VXR Midplane Hardware Revision | Verify the "revid" of the PCI Bridge Component |
Replace the NPE-G2 Network Processing Engine |
If the 7204VXR or 7206VXR has an NPE-G2 and at least one (1) of the noted port adaptors (PA) installed then proceed to step B. Router configurations without the NPE-G2 and a specific PA are NOT affected by this issue. |
If the NPE-G2 hardware revision is lower than 1.2 then go step C. This field notice does not apply if the NPE-G2 hardware revision is 1.2 or above, or has a deviation level of either D087457 or D087195. |
If the VXR midplane hardware revision is 2.7 or lower, then go to directly to step E. If the VXR midplane hardware revision is greater than 2.8 then go to step D. |
If the VXR chassis has a PCI bridge component has a "class code, revid" with a value less than "0x0040" in its last four (4) digits, then proceed to step E. This field notice does not apply if the "class code, revid" has a value equal to, or greater than "0x0040" in its last four (4) digits. |
A replacement NPE-G2 must be handeled through standard RMA process |
Step A: Confirm Physical Configuration of 7204VXR or 7206VXR Series Router
Execute the IOS command show inventory
and compare resultant IOS output to the Products Affected section of this field notice. The router is subject to this field notice if it has an NPE-G2 Network Processing Engine and at least one (1) of the port adaptors noted in the Products Affected section of this field notice. A physical inspection of the suspect router can also be performed to confirm if the router is affected by the issue described in this field notice.
Steps B and C: Using Show C7200
to Determine VXR Midplane and NPE-G2 Revision Levels
Executing the IOS CLI command show c7200
on a suspect system will provide a confirmation of the NPE-G2 and midplane revision levels as shown in the following example. Systems with midplane hardware revisions of 2.7 and lower are definitely affected with the issue described in this field notice when used with the NPE-G2 and the above noted Port Adaptors. A limited number of chassis manufactured beyond revision 2.7 may also be subject to the compatibility issue.
Note: Cisco 7200 VXR series midplane revision numbers increment sequentially on both the right hand and left hand side of the decimal point. Hence, revisions sequence as 2.0, 2.1, 2.2, 2.3,..........2.9, 2.10, 2.11 and so on. For example, a midplane of revision 2.10 will be higher than a midplane revision of 2.8.
Step D: Using show pci bridge
to Determine Existence of Affected PCI Bridge Component
VXR midplane version levels greater than 2.8 must be checked further to confirm the existence of an affected PCI bridge component. The IOS CLI command show pci bridge <slot_number>
must be executed on at least one (1) slot of a suspect VXR chassis with a port adaptor (PA) installed. The last four (4) digits of the "(0x08):class code, revid" output is then confirmed to be a level that is affected by the issue. Values in the last four (4) digits of the "(0x08):class code, revid" of less than "0x0040" are affected by this issue. Values in the last four (4) digits of the "(0x08):class code, revid" equal to, or greater than, "0x0040" are not affected by this issue.
The following example shows the identification of a an affected PCI bridge component.
Router#show pci bridge 1
Bridge 4, Port Adaptor 1, Handle=1
DEC21150 bridge chip, Primary Bus 4, Secondary Bus 5,config=0x0
(0x00):dev, vendor id = 0x00231011
(0x04):status, command = 0x02B00147
(0x08):class code, revid = 0x06040006 <--"(0x08) : class code, revid" of 0x06040006 Are Affected
(0x0C):hdr, lat timer, cls = 0x00012E10 (0x18):sec lat,cls & bus no =
0x18050504 (0x1C):sec status, io base = 0x22A05141=
Received Master Abort on secondary bus
(0x20):mem base & limit = 0x48F04880
(0x24):prefetch membase/lim = 0x0001FF01
(0x30):io base/lim upper16 =0x00000000
(0x3C):bridge ctrl = 0x07030000
(0x40):arb/serr, chip ctrl = 0x02000000
(0x64):serr disable, gpio = 0xF0000000
(0x68):sec clk ctrl,serrsta = 0x000001FF
[Output Omitted for Brevity]
Note:
Positive identification of an affected chassis is confirmed when the output of the show pci bridge <slot_number>
command displays the last four (4) digits of output in the "(0x08) :class code, revid" of less than "0x0040". The value "0x06040006" shown in the above example represents a PCI bridge affected by the issue because the last four (4) digits shown ("0x0006") is lower than "0x0040". Values in the last four (4) digits of the "(0x08):class code, revid" equal to or greater than "0x0040" are not affected by this issue.
Note:
Suspect chassis will only have one type of PCI bridge component used in all slots of the chassis. The show pci bridge <slot_number>
command will only provide CLI output for slots with a port adaptor installed. Verification of the PCI component for one (1) slot of the suspect chassis provides verification for all slots in a suspect chassis.
Step E: Replace the NPE-G2 Network Processing Engine
A replacement NPE-G2 must be handled with the standard RMA process if the results of steps A through D confirm that the suspect router is affected by this field notice.
Identification of Affected Hardware Through Physical Inspection
Top View of NPE-G2 Showing Location of Printed Circuit Assembly (PCA) and Serial Number Decals
Close-Up View of NPE-G2 Printed Circuit Assembly (PCA) Number and Serial Number
Revision | Date | Comment |
---|---|---|
1.0 | 24-APR-2007 | Initial Public Release |
1.1 | 02-MAY-2007 | Updated with addtional port adaptors in the "Products Affected" section. |
1.2 | 06-APR-2009 | Removed upgrade program. |
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.