Cisco Prime LMS 4.2.1 Customizable Interface Group

need to remove certain alarms for only certain type of interfaces, and worked many days and finally worked with help from TAC.

1.       Modified group rule for a customizable interface group with a valid group rule (Example: Customizable Interface Group 1) from Admin > System > Group Management > Fault.

2.      Modified the priority of that Interface Threshold Group  to higher priority from Monitor > Fault Settings > Setup > Priority Settings so that the interfaces satisfying the rule will fall under higher priority group.

3.       Apply changes after modifying the priority to apply all changes to in charge server  from Monitor > Fault Settings > Setup > Apply Changes.

4.       Then apply threshold values from Monitor > Fault Settings > Setup > Threshold Settings.

5.      Then apply changes to apply all threshold value changes to in charge server  from Monitor > Fault Settings > Setup > Apply Changes

Ciscoworks Prime LMS 4.2 DFM change of fault threshold

Below is an example of what I have to do to get rid of tons of OutOfRange Temperature o rVoltage Sensors Alerts:

First Stop daemon

  /etc/init.d/dmgtd stop

Modify the entry (please note the highlighted part)for my devices in oid2type_cisco.conf file (<NMSROOT>/objects/smarts/conf/discovery/oid2type_cisco.conf)  as shown below:

# Cisco Nexus 7000

 .1.3.6.1.4.1.9.12.3.1.3.612 {

    TYPE = Switch

    VENDOR = Cisco

    MODEL = N7K-C7010

    CERTIFICATION = CERTIFIED

    CONT = Cisco-EntityRF-Switch

    HEALTH = Nexus-Entity-EntSensor

    BRIDGE = Cisco

    NEIGHBOR = Cisco-Cdp

INSTRUMENTATION:

     Environment                     = CiscoEntityFRU:DeviceID

    Card-Fault                      = CiscoEntityFRU:DeviceID

    CPU/Memory                      = CiscoSystem:DeviceID

     Interface-Fault                 = MIB2

    Interface-Performance           = MIB2

    Port-Fault                      = MIB2

    Port-Performance                = MIB2

}

# Cisco ASR Router - 1004

.1.3.6.1.4.1.9.1.924 {

TYPE = Router

VENDOR = Cisco

MODEL = ASR1004

CERTIFICATION = TEMPLATE

CONT = Cisco-EntityFRU

NEIGHBOR = Cisco-Cdp

HEALTH = Cisco-Router-CRS-EntSensor

INSTRUMENTATION:

Environment = CiscoEntityFRU:DeviceID

CPU/Memory = CiscoRouter:DeviceID

Card-Fault = CiscoEntityFRU

Interface-Fault = MIB2

Interface-Performance = CiscoRouter

Interface-Ethernet-Performance = CiscoRouter_Ethernet

} 

# Cisco VSS Switch 

.1.3.6.1.4.1.9.1.896 {

    TYPE = Switch

    VENDOR = Cisco

    MODEL = VSS-1440

    CERTIFICATION = CERTIFIED

    CONT = Cisco-VSS-Switch

    VLAN = Cisco-Membership

    BRIDGE = Cisco

    NEIGHBOR = Cisco-Cdp

    HEALTH = Cisco-Router-CRS-EntSensor

INSTRUMENTATION:

    Environment                         = CiscoEntityFRU:DeviceID

    CPU/Memory                          = CiscoRouter:DeviceID

    Card-Fault                          = CiscoEntityFRU:DeviceID

    Interface-Fault                     = MIB2

    Interface-Performance               = MIB2

    Port-Fault                          = MIB2

    Port-Performance                    = MIB2

    Port-Ethernet-Performance           = dot3_Ethernet

}

Restart daemon

  /etc/init.d/dmgtd start

Re-discover the devices

exchange server out off disk space due to excessive amount of log files

an old friend called for help.  found exchange 2003 server mtadata folder filled with huge amount of log files (E00....log).   I ran ntbackup and did a exchange information store backup, immediately cleaned all the E00...log files, and reclaimed over 50 GB disk space.