I have a question: I've installed a CISCOWORKS LMS 3.0 on a SUN Solaris 9, with HP NNM and using the LMS integration tool I'm able to acquire the devices from NNM. Then, trying to modify a device name in NNM, I have no sync in LMS. Should LMS notice that change? Is there a way to sync LMS with NNM changes without hand-made scripts?
No there is no way. Integration between NNM and LMS (or vice versa) is always a one-time procedure and reflects the status at this definite time; i.e. you 'export' the devices which are currently in one of the systems and 'import'them into the database of the other system (and if I remember well, it is always a merge).
You could run the integration after every change you make, but I would not recommend it....
With 'Changeing the name in NNM' I think you mean that you have changed the Display lable which is just a field in the NNM database and LMS will never get any information about changes in NNMs database.
Configure name resolution for your devices (either DNS or hosts file) and you will have a central place to change display lables in both of you mgmt software.
Yes, if you have marked CM > Admin > Device Discovery > Discovery Settings => Update DCR Display Name (default is 'not marked') then the label (Display Name) in DCR (and thus all other LMS apps) should change when name resolution for a device changes. Perhaps one exception.... as DFM in the past always behaves other way as the rest of LMS this could still be a problem.
NNMs name resolution was very strange in the past (NNM6.x)and as NNM 7.x still relies on netmon for discovery I think it is still truth. NNM sets the display name of a device acording to the following schema: (if one gives no result it tries the next in the list)
- DNS name of lowest numbered software loopback address
- DNS name of lowest numbered IP
- lowest numbered software loopback IP
- lowest numbered IP
you can exclude IPs from being used for selecting the hostname by adding them tothe file 'excludeip.conf' [in $OV_CONF)- (see the man pages from NNM for detailsas perhaps you have to create the file!)
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...