after discovering a new link, you sometimes have to hit "Action-Refresh" TWICE for the map to show the link. this would be a bug if that is the problem, but it has happened before. Otherwise here are a few more tips.
OpenManage™ Network Manager server and client require resolution of equipment names to work
completely, whether by host files or domain name system (DNS). Often the application server cannot
respond to hosts with IP addresses alone. This may also impact link discovery.
If you have name resolution setup and stil no luck, follow the rules below to allow OMNM to discover the ethernet links. By setting the appropriate CLI commands, you will be able to display thes links in your OMNM Topology Map.
You will need to add the follwing LLDP commands to any 6xxx, 7xxx, or 8xxx Powerconnect switches as appropriate.
lldp med transmit-tlv location (no effect in our Powerconnect Switches)
lldp med transmit-tlv inventory (no effect in our Powerconnect Switches)
REQUIRED GLOBAL COMMANDS of 6xxx, 7xxx, 8xxx.
lldp notification-interval 10
You can also try the following which are often suspect when the links don't appear....
1. Resync devices in OMNM especially after making any kind of change.
2. Make sure you have Telnet listed as a Mngmt. Interface on your switch (or SSH)
3. Put on a default-gateway (and then resync, and then re-map)
Each device should have a default-gateway (for managment) that points toward OMNM.
4. If still no link, delete any existing link(s) (in Links) between the two devices in question and delete any old links that are no longer active on the devices. This is particularly important when using stacked modular switches.
5. If still no link, delete the devices from Resources and rediscover them from scratch.
6. Again, after discovering a new link, you sometimes have to hit "Action-Refresh" TWICE for the map to show the link.
I hope something here will help you get past the issue.
DELL-Victor
98 Posts
0
August 30th, 2011 15:00
after discovering a new link, you sometimes have to hit "Action-Refresh" TWICE for the map to show the link. this would be a bug if that is the problem, but it has happened before. Otherwise here are a few more tips.
OpenManage™ Network Manager server and client require resolution of equipment names to work
completely, whether by host files or domain name system (DNS). Often the application server cannot
respond to hosts with IP addresses alone. This may also impact link discovery.
If you have name resolution setup and stil no luck, follow the rules below to allow OMNM to discover the ethernet links. By setting the appropriate CLI commands, you will be able to display thes links in your OMNM Topology Map.
You will need to add the follwing LLDP commands to any 6xxx, 7xxx, or 8xxx Powerconnect switches as appropriate.
lldp transmit-tlv port-desc sys-name sys-desc sys-cap
lldp transmit-mgmt
lldp notification
lldp med confignotification
lldp med transmit-tlv location (no effect in our Powerconnect Switches)
lldp med transmit-tlv inventory (no effect in our Powerconnect Switches)
REQUIRED GLOBAL COMMANDS of 6xxx, 7xxx, 8xxx.
lldp notification-interval 10
You can also try the following which are often suspect when the links don't appear....
1. Resync devices in OMNM especially after making any kind of change.
2. Make sure you have Telnet listed as a Mngmt. Interface on your switch (or SSH)
3. Put on a default-gateway (and then resync, and then re-map)
Each device should have a default-gateway (for managment) that points toward OMNM.
4. If still no link, delete any existing link(s) (in Links) between the two devices in question and delete any old links that are no longer active on the devices. This is particularly important when using stacked modular switches.
5. If still no link, delete the devices from Resources and rediscover them from scratch.
6. Again, after discovering a new link, you sometimes have to hit "Action-Refresh" TWICE for the map to show the link.
I hope something here will help you get past the issue.
Victor