Preview Tool

Cisco Bug: CSCum73589 - PI 'CEFC Module status change' alarm

Last Modified

Feb 15, 2018

Products (1)

  • Cisco Prime Infrastructure

Known Affected Releases

1.2(1.12) 1.3(0.20) 1.4(0.45) 2.0(0.0.294)

Description (partial)

PI supports 'CEFC Module status change' alarm for wired/wireless devices.
whenever switch/router module status is changed, switch is able to send cefcModuleStatusChange trap to PI, and PI will be able to trigger 'CEFC Module status change' alarm.
there are two problems here.

1. 'CEFC Module status change' alarm doesn't provide any details about faulty slot/module numbers.
    when cefcModuleStatusChange trap is sent by device, actually the trap includes entPhysicalIndex number. 
	so, PI should be able to differentiate the alarms with different module slots. 
2.  in case 'CEFC Module status change' alarm was previously triggered and it still exists from Operate > Alarm & Events > Alarms,
    when the same device sends cefcModuleStatusChange trap with different module which is placed in different slot, although fauty module is different module with the previous one, PI only updates module status from the alarm which PI triggered previously.
	it does not trigger new separte alarm for different slot/module number.
	when I ran a lab test, I triggered cefcModuleStatusChange trap from 4500 switch by rebooting line card slot #1 first and then line card slot #7. ('hw-module module 1 reset' or 'hw-module switch 2 module 1 reset')
    when rebooting line card #7, it didn't generate new alarm for module #7 and I could see the message of the previously triggered 'CEFC Module status change' alarm was changed from 'INSERVICE' to 'null' and then to 'INSERVICE'.

PI version 1.2, 1.3, 1.4 and 2.0
Bug details contain sensitive information and therefore require a 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.