Cisco Bug: CSCuw43333 - local-Cause code display is incorrect for vlr-down/unreachable-mmesvc
Dec 24, 2016
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: There are two issues noticed with the cli used to configured local-cause-code mapping for vlr-down and vlr-unreachable emm-cause code to imsi-unknown-in-hss. 1, Even though we have option to configure "local-cause-code-mapping vlr-down emm-cause-code imsi-unknown-in-hss" & "local-cause-code-mapping vlr-unreachable emm-cause-code imsi-unknown-in-hss" under mme-service. When we issue "show config", in the above cli "hss" is replaced with "hlr" mme-service mmesvc s1-mme sctp port 25 mme-id group-id 32777 mme-code 2 plmn-id mcc 123 mnc 456 associate egtp-service mme_egtp context MME . . . . local-cause-code-mapping congestion emm-cause-code eps-service-not-allowed-in-this-plmn esm-cause-code congestion local-cause-code-mapping vlr-down emm-cause-code imsi-unknown-in-hlr ======> this should be imsi-unknow-in-hss local-cause-code-mapping vlr-unreachable emm-cause-code imsi-unknown-in-hlr =====> this should be imsi-unknow-in-hss local-cause-code-mapping peer-node-unknown emm-cause-code network-failure. 2, After saving the config with "local-cause-code-mapping vlr-down emm-cause-code imsi-unknown-in-hlr" and "local-cause-code-mapping vlr-unreachable emm-cause-code imsi-unknown-in-hlr" configured under mme-service. After we reload the MME[asr5k] with the saved config, the local-casue code with emm-cause-code imsi-unknow-in-hss is not getting configured again and the default cause code is configured againt vlr-down and vlr-unreachable. NOTE: The save and reload issue for local-cause-code-mapping.*" under mme-service is seen only when teh emm-cause-code is mapped to imsi-unknown-hss . Conditions: when the customer wants to use the ""local-cause code mapping cli configuration under mme-service for vlr-down/unreachable with mapped emm-cause code as "imsi-unknow-in hss"
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases