Send Netdot-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-users digest..."
Today's Topics:
1. Issue with Discovering Cisco Nexus 7000 (YUUNI, OSAY OSMAN)
2. Updated Site.conf, still getting the Cannot find root device:
localhost topology error (Stafford Rau)
----------------------------------------------------------------------
Message: 1
Date: Fri, 2 Aug 2013 14:23:37 +0000
From: "YUUNI, OSAY OSMAN" <[email protected]>
Subject: [Netdot-users] Issue with Discovering Cisco Nexus 7000
To: "[email protected]" <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi all,
I'm having issues discovering our Cisco Nexus 7000 switches. The discovery
returns an error about an invalid IP. Basically it returns an IP address with
4. prepended like so
Invalid IP: 4.192.168.63.1. Each of the two switches returns a different IP
with the 4. prepended. An SNMPWalk shows that these addresses actually do not
exist in the switch. The snippet below shows that the 4. Comes from the MIB
IP-MIB::ipAdEntAddr.4.192.168.62.26 = IpAddress: 192.168.62.26
IP-MIB::ipAdEntAddr.4.192.168.62.34 = IpAddress: 192.168.62.34
Has anyone experienced this type of thing and how did you resolve it?
Kind regards,
Osay
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20130802/feed7ad2/attachment-0001.html
------------------------------
Message: 2
Date: Fri, 2 Aug 2013 11:54:06 -0700
From: Stafford Rau <[email protected]>
Subject: [Netdot-users] Updated Site.conf, still getting the Cannot
find root device: localhost topology error
To: [email protected]
Message-ID:
<caaqua9gk53rztryyo3tq0wxfj5g6obpbmkbxuysz+-gu6nm...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
As in the subject, I updated the NMS_DEVICE field in etc/Site.conf to point
to one of our core routers, then I re-ran bin/update_devices -T
--recursive. However, through the web interface topology report it's still
showing the error with 'localhost' as the topology root.
Is there another step I need to update the topology root?
When I look at Management->Devices->{the core router I'm using for the topo
root}->topology, the "Reference Point" field still says "localhost", but
when I change that field to be the core router and hit "Update View", it
builds the topology table correctly.
Thanks,
--Stafford
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20130802/4dbe32cc/attachment-0001.html
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 57, Issue 2
*******************************************
