Guest

Preview Tool

Cisco Bug: CSCur49663 - Msg drop on cell-id mismatch in stack after BVCI to Cell-ID map change

Last Modified

Dec 25, 2016

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases

16.0(1)

Description (partial)

Symptom:
Following logs are seen after the BVCI to Cell-ID mapping change is initiated by Peer particularly if the RAC is 0.

2014-Oct-21+05:53:51.445 [gmm 88102 info] [2/0/6456 <sessmgr:33> sgsn_cmn.c:1243] [software internal user syslog] gm_bdy3.c:2019 [110:6] Msg drop (expected ci-0x655-1f-1-0-9b) : tlli-0x7f010f30 nsei-23 bvci-75 ci-0x655-1f-1-0-60
2014-Oct-21+05:53:51.693 [gmm 88102 info] [2/0/6456 <sessmgr:33> sgsn_cmn.c:1243] [software internal user syslog] gm_bdy3.c:2019 [110:6] Msg drop (expected ci-0x655-1f-1-0-9a) : tlli-0xff010f31 nsei-23 bvci-74 ci-0x655-1f-1-0-61
2014-Oct-21+05:53:51.942 [gmm 88102 info] [4/0/6693 <sessmgr:115> sgsn_cmn.c:1243] [software internal user syslog] gm_bdy3.c:2019 [110:6] Msg drop (expected ci-0x655-1f-1-0-99) : tlli-0x7f010f32 nsei-23 bvci-73 ci-0x655-1f-1-0-62

Because of this the message is getting dropped at the stack. Mostly this is because the cell-id change is not getting updated in stack as its expecting the message from the old cell-id whereas the message is coming with the newly updated Cell-ID as part of the BVC-RESET procedure

Conditions:
Initial Configuration:
BVCI: 75 Cell-ID: 155
BVCI: 74 Cell-ID: 154
BVCI: 73 Cell-ID: 153

Command Used for Cell-ID mapping change:
sitt_is -instance 1 -nsei 23 -bvci 76 -nsvci 23 -cellid 95 -cause 0 bvc_reset
sitt_is -instance 1 -nsei 23 -bvci 75 -nsvci 23 -cellid 96 -cause 0 bvc_reset
sitt_is -instance 1 -nsei 23 -bvci 74 -nsvci 23 -cellid 97 -cause 0 bvc_reset
sitt_is -instance 1 -nsei 23 -bvci 73 -nsvci 23 -cellid 98 -cause 0 bvc_reset
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
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.