Cisco Cisco ASR 5700 Guía Para Resolver Problemas
This trap/alarm can be ignored and cleared since the node is not truly SRP active and not handling
any traffic. Note the failure rate in the example above is much lower than the expected 100% and
bug CSCuu60841 has now fixed that issue in a future release so that it will always report 100%.
any traffic. Note the failure rate in the example above is much lower than the expected 100% and
bug CSCuu60841 has now fixed that issue in a future release so that it will always report 100%.
clear alarm outstanding
OR
To just clear that particular alarm:
clear alarm id <alarm id>
Another twist of this issue can occur on a newly SRP Standby chassis after an SRP switchover
has taken place. The alarm should be ignored in that scenario also since the chassis is SRP
Standby and DNS failures are therefore irrelevant.
has taken place. The alarm should be ignored in that scenario also since the chassis is SRP
Standby and DNS failures are therefore irrelevant.
Finally, it goes without saying that the cause for this alarm needs to be immediately investigated
on a truly SRP active PGW, as subscriber or billing impact will likely occur depending on what
types of FQDNs are attempting to be resolved.
on a truly SRP active PGW, as subscriber or billing impact will likely occur depending on what
types of FQDNs are attempting to be resolved.