Note:?This is an intermittent problem that can affect the GEIP when interacting with the 7513 chassis. This only happens on a hard boot, when the box is powered on and off.
A problem has been discovered concerning timing variations on the GEIP. It causes the GEIP to be unrecognizable to a 7513 Chassis when powering up the box. It also gives a PCI error back to the CLI.
This problem does not happen with any other product in the 7500 family, with the PA-GE, the GEIP+, or with the VIP4 family.
When this intermittent problem happens, there is a 200 ms rise time delay between the 7513 and the GEIP. This causes a PCI parity error or system error to occur on the PCI interface between the PCI bridge and the MAC on the GEIP. This failure brings down the GEIP.
The LEDs appear on the GEIP=, but the card is not recognized by the IOS.
There are two types of PCI error messages that appear on the CLI at boot up. To confirm that you are having this problem please check to make sure the following appears.
Press RETURN to get started!
00:00:51: %GEIP-1-MSG: slot8 PMA error register = 0001000100200020
00:00:51: %GEIP-1-MSG: slot8 PCI TRDY time-out
00:00:51: %GEIP-1-MSG: slot8 PCI Master Access failed
00:00:51: %GEIP-1-MSG: slot8 PCI master address = 0010001
00:00:51: %GEIP-1-MSG: slot8 System reloaded by a fatal hardware error
00:00:51: %GEIP-1-MSG: slot8 caller=0x600DCEE0
00:00:51: %GEIP-1-MSG: slot8 System exception: sig=22, code=0x0,
The simple workaround for this problem is to do an OIR on the GEIP.
Please look carefully at the version numbers listed under Products Affected. Later hardware versions do not have this issue.
Note:?Some GEIP cards were updated on Deviation Number D000477 and have a deviation sticker labeled D000477 on the printed circuit board of the PA next to the -73 part number. However, the Top Assy number and Revision levels were not changed in the PA EPROM. The port adapters updated under the deviation are acceptable for use, but will show as the old revision electronically.
To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.