Cisco Bug: CSCur22439 - lic enforce admindown status not sync
Jan 30, 2017
- Cisco uBR10000 Series Universal Broadband Routers
Known Affected Releases
Symptom: After PRE switchover, some rf-channels, previously in no-shut status, are in shutdown status and cause service down for some modems. Conditions: In order to hit CSCur22439, all below four conditions need to be met and in sequential, and there's no PRE Switchover between step 3 and 4. Usually all these steps don't happen in one shot, it may take a long time to meet all of them (several months or more than 1 year) in customer side. Step 1: Licenses is being decreased (e.g. 72->60). The removed/decreased rf-channels (12 rf-channels) on active PRE (PRE A) are labeled as ?license forced shut-down? with flags being set to 1. The flags are supposed to be sync up on both active PRE (PRE A) and standby PRE (PRE B). However, there is a bug that causes the sync up failure. This bug had been fixed in SCH6 and SCI1. Step 2: Standby PRE (PRE B) reload itself (for any reason) later. When it comes back again, the flags for 12 license forced shut-down rf-channels will be reset to initial status (0), the rf-channels are in shut-down status on both PRE. Two PRE5 are not in sync (rf-channel status are in sync but flags are not in sync). Step 3: Licenses is being increased (e.g 60->70). The license count and flag on active PRE (PRE A) are changed accordingly (10 licenses are un-shut and the flags for them are changed to 0). However, the flag sync will fail on standby PRE due to the bug. Hence, standby PRE (PRE B) still has 12 shut-down rf-channels with flags set as 0. Two PRE5 are not in sync. Step 4: PRE Switchover occurs (for any reason). PRE B now becomes active PRE, however, there are still 12 rf-channels are in shut-down status which is not expected (only 60 rf-channels are usable). Customer supposes to have 70 rf-channels usable. Customer has to manually un-shut those 10 rf-channels to make it work.
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