Cisco Bug: CSCtc53079 - CFM config created on non-existent EFP on attempt to exceed scale limits
Jan 11, 2017
- Cisco ASR 9000 Series Aggregation Services Routers
Known Affected Releases
Symptoms: When attempting to configure an EFP with a CFM MEP upon it, the EFP creation fails, but the CFM MEP configuration appears to succeed. After attempting to commit the configuration, the EFP creation failure is reported as a semantic error by the <CmdBold>show configuration failed<noCmdBold> command: RP/0/RSP0/CPU0:ios(config-if-cfm-mep)#show configuration failed !! SEMANTIC ERRORS: This configuration was rejected by !! the system due to semantic errors. The individual !! errors with each failed configuration command can be !! found below. interface GigabitEthernet0/1/0/0.8001 l2transport !!% The combined L2 and L3 sub-interface limit for the card has been reached: Node limit is 32768 The same command also shows an apply error for the CFM MEP configuration: !! APPLY ERRORS: This configuration was accepted by the system, !! but errors occurred when the system attempted to make the !! configuration operational. The individual errors for each !! failed configuration command can be found below. These errors !! will cause an inconsistency between the system's running !! configuration and its operational state, which may be addressed !! by using the 'no' form of the command to remove it from the !! running configuration. interface GigabitEthernet0/1/0/0.8001 l2transport ethernet cfm mep domain INTERDOMAIN service LOCAL779 mep-id 40 !!% 'ifmgr' detected the 'warning' condition 'The protocol/capsulation/interface could not be found' However, the CFM MEP configuration is still visible in the running configuration: RP/0/RSP0/CPU0:ios#show running interface GigabitEthernet0/1/0/0.8001 interface GigabitEthernet0/1/0/0.8001 ethernet cfm mep domain INTERDOMAIN service LOCAL779 mep-id 40 The <CmdBold>show interface<noCmdBold> command confirms that the EFP has not been successfully created: RP/0/RSP0/CPU0:ios(config-if-cfm-mep)#show interface GigabitEthernet0/1/0/0.8001 Interface not found (GigabitEthernet0_1_0_0.8001) Conditions: The problem occurs when attempting to configure a number of EFPs that exceeds the scale limit for the line card, and when the configuration for those EFPs includes CFM MEP configuration.
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