The message is emitted by the interface statistics module. The module is expecting a particular interface to be present, and did not find the data structure for that interface.
When a “EZsrhStruct_StatEntry_DoesExist failed” event occurs, a message similar to one of the following is reported:
node0.fpc7 ERROR! number: 0xA0025209, EZsrhStruct_StatEntry_DoesExist failed.
(FPC Slot 0, PIC Slot 0) ERROR! number: %PFE-3: 0xA0005209, EZsrhStruct_StatEntry_DoesExist failed.
This message can also occur with these syslog entries:
node0.fpc7 ERROR! number: 0xA0005209, EZprmHash_GetLock_NP_2: Retries exceeded while locking address 0x00104B09.
node0.fpc7 EZ: xeth_aus_ifl_stats_periodic xeth_aus_ifl_stats_periodic get iftbl entry faile 0xA0025209
node0.fpc7 xeth_aus_ifl_stats_periodic===> did not find tx ifl entry in hash tbl, ifl:261
(FPC Slot 0, PIC Slot 0) EZ: %PFE-3: ezchip_iq2_add_vc_table_entry get hash table entry failed:0xa0005209
The cause is due to the PIC interface being in a non-functional hardware state.
Examine the following outputs to help determine the cause of this message:
show log messages
show log chassisd
show interfaces extensive
show chassis fpc pic-status
Look for any related events that occurred at or just before the “EZsrhStruct_StatEntry_DoesExist failed” message in the syslog and chassisd outputs.
Perform these steps:
1.During a maintenance window, as it will impact transit traffic, try the following:
- Reset the PIC by using offline/online commands. This can be done with the commands:12request chassis pic offline pic-slot <pic_number> -or- request chassis pic fpc-slot <fpc_number> offline pic-slot <pic_number>request chassis pic online pic-slot <pic_number> -or- request chassis pic fpc-slot <fpc_number> online pic-slot <pic_number>
- Offline the PIC and reseat the PIC in its slot. (See commands listed above.) Check the slot pins with a flashlight when doing this to verify that there are no bent pins.
- Move the PIC to another slot to see if the issue follows the PIC.
- Swap the PIC with a known good module.
If the log messages continue, open a case with your technical support representative to investigate the issue further.