cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
806
Views
0
Helpful
3
Replies

LMS 2.6 - Issue with WS-SVC-CMM, also Email Alert question

chharris41
Level 1
Level 1

I have a Cat 6504-E chassis with a WS-SVC-CMM. The CMM shows red on topology map because LMS wants to use it's loopback 0 address for management. For some reason, the CMM can ping out but the loopback cannot be reached, not even fom the supervisor engine. How do I configure a route onthe sup engine to point to the CMM looback??

Also,

I would like to change the email alerts to be more device specific, right now in the email I get this:

MANAGED OBJECT = 10.255.255.35

I would like to change it to the device name, or even host name of device. Is this possible? Also would like to tweak the EVENT DESCRIPTION = field to reflect the circuit ID's for WAN interfaces.

Thanks in advance for your help.

3 Replies 3

Joe Clarke
Cisco Employee
Cisco Employee

By loopback, do you mean a 127/8 address? What does the show cdp nei detail look like on the Sup?

As for you DFM IP address issue, this thread may help you:

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network%20Infrastructure&topic=Network%20Management&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddd9845

I have a loopback address configured on the CMM - 10.255.255.93 (loopback 0). The Supervisor engine shows the CMM in cdp neighbors under diff address (10.9.26.10). I've tried changing the mgmt address on the topology map (right click device, change mgmt ip address) - problem is that it keeps reverting back to loopback address any time discovery/collection runs. How do I get LMS to forget about the loopback and use other address permanently?

You will have to either disable Discovery, or configure Discovery to use some other mechanism other than Resolve by Loopback. Note: it might be easier to advertise a route for this address by creating a static route on your MSFC (or whatever does routing for the VLAN that has the 10.9.26.10 address), then redistribute that route into your routing protocol.