Preview Tool

Cisco Bug: CSCvi56478 - Ping failure from ASR920 to ASR903 w/ EAMapperError1 counter after upgrade to specific ES image

Last Modified

Jan 18, 2019

Products (1)

  • Cisco ASR 920 Series Aggregation Services Router

Known Affected Releases


Description (partial)

Ping failure from ASR920 to directly connected ASR903 after upgrade to customer-specific ES image.

If this issue is debugged by checking ASIC counters, the "EAMapperError1" counter is seen to increment to match the number of failed pings.

<pre>Router#req pla soft sdcli "nile stats zero_stats 0 0 all"
Writing 0x0 into Xenon stats ram....
Init statsregisters, packetcount, statsext registers....
Init channel stats ram....
Init mac stats ram....
Router#req plat soft sdcli "nile stat ipstat 0"          
EAMapperError1:                    packets : 0    bytes : NA   reason: 0x0
Router#ping y.y.y.y rep 10000 source te0/0/11 size 1500 time 0
Type escape sequence to abort.
Sending 10000, 1500-byte ICMP Echos to y.y.y.y, timeout is 0 seconds:
Packet sent with a source address of x.x.x.x
Success rate is 0 percent (0/10000)
Router#req plat soft sdcli "nile stat ipstat 0"                    
EAMapperError1:                    packets : 10000    bytes : NA   reason: 0x0   <------- increased by 10K after 10K failed ping</pre>

ASR920 is running customer specific engineering special image. This is NOT seen on any public CCO release.

ASR920 is connected to ASR903 via point-to-point L3 interface. Issue is not seen if the interfaces are configured with EVC and L3 on a BDI.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.