Cisco Bug: CSCup34047 - Additional checks/logs to find the trigger for Wrong DNS query
Last Modified
Feb 05, 2017
Products (1)
- Cisco ASR 5000 Series
Known Affected Releases
15.0(17)
Description (partial)
Symptom: Customer was observing some wrong DNS query from ASR5K with wrong/unexpected MCC and MNC. Jun 02 11:28:33.104 queries: client 196.46.161.194#49047: query: rac0028.lac4050.mnc7b4.mcc692.gprs IN A Jun 02 11:29:07.020 queries: client 196.46.161.194#51457: query: rac0071.lac0139.mncb22.mcc65b.gprs IN A Current logging in asr5k is not able to capture the trigger for this issue . We need additional logging to find the trigger for this. Conditions: Customer was observing some wrong DNS query from ASR5K with wrong/unexpected MCC and MNC. Jun 02 11:28:33.104 queries: client 196.46.161.194#49047: query: rac0028.lac4050.mnc7b4.mcc692.gprs IN A Jun 02 11:29:07.020 queries: client 196.46.161.194#51457: query: rac0071.lac0139.mncb22.mcc65b.gprs IN A Current logging in asr5k is not able to capture the trigger for this issue . We need additional logging to find the trigger for this.
Bug details contain sensitive information and therefore require a Cisco.com 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