Hi
I recently stumbled on your product while I was searching for a good network monitoring tool.
So I started a POC with Debian package but got some problems with Graphite, and had to reverted to the appliance.
Now that its running, I’m impressed over functions built in, especially the network auto mapping.
But there is one thing I don’t know how to handle.
We are mainly using Juniper EX4200, EX 3200 and EX2200 switches.
Our Juniper EX4200 switches are set up as virtual chassis (stacked switches), and they all have the same ip address.
The problem is that the switches, although they are in the same chassis, they are placed in different “rooms” a ring around our campus acting as distribution switches.
Se config:
dgc@MMACOR01> show virtual-chassis
Virtual Chassis ID: b0c6.9a6f.7500
Virtual Chassis Mode: Enabled
Mstr Mixed Neighbor List
Member ID Status Serial No Model prio Role Mode ID Interface
0 (FPC 0) Prsnt BM0209493141 ex4200-24t 250 Master* N 1 vcp-0
7 vcp-255/1/1
1 vcp-1
1 (FPC 1) Prsnt BM0209505602 ex4200-24t 140 Linecard N 0 vcp-0
4 vcp-255/1/1
0 vcp-1
2 (FPC 2) Prsnt BR0218490227 ex4200-24f 130 Linecard N 3 vcp-0
5 vcp-255/1/2
3 vcp-1
3 (FPC 3) Prsnt BR0218490131 ex4200-24f 120 Linecard N 2 vcp-0
9 vcp-255/1/2
2 vcp-1
4 (FPC 4) Prsnt BM0209493198 ex4200-24t 210 Backup N 5 vcp-0
1 vcp-255/1/1
5 vcp-1
5 (FPC 5) Prsnt BM0209485774 ex4200-24t 200 Linecard N 4 vcp-0
2 vcp-255/1/1
4 vcp-1
6 (FPC 6) Prsnt BR0209485019 ex4200-24f 190 Linecard N 7 vcp-0
8 vcp-255/1/1
7 vcp-1
7 (FPC 7) Prsnt BR0209484982 ex4200-24f 180 Linecard N 6 vcp-0
0 vcp-255/1/1
6 vcp-1
8 (FPC 8) Prsnt BR0213155003 ex4200-24f 170 Linecard N 9 vcp-0
6 vcp-255/1/1
9 vcp-1
9 (FPC 9) Prsnt BR0214421949 ex4200-24f 160 Linecard N 8 vcp-0
3 vcp-255/1/1
8 vcp-1
Member ID for next new member: None
{master:0}
dgc@MMACOR01>
And picture
[cid:image002.png@01D52A71.D4537D10]
It looks like I only can add a ip address once
Is there a way to add the other MMACOR01 switches so I can see them, even if they have the same IP?
Vänliga hälsningar / Best regards
Djuro Garvanovic
IT Infrastruktur
Nätverk och kommunikation
+46 40 323710
djuro.garvanovic(a)pagen.se<mailto:dgc@pagen.se>
http://www.linkedin.com/in/djuro
Pågen AB, Box 8143, SE-200 41 Malmö
Besöksadress: Kopparbergsgatan 19, Grind G5
www.pagen.se<http://www.pagen.se/>
www.facebook.com/pagensverige<http://www.facebook.com/pagensverige>
[cid:image001.png@01D0B4AF.B24D9610]
The seventh maintenance release of the 4.9 series of NAV is now out!
The source code is available for download at GitHub [1].
New packages for Debian 8/9 (Jessie/Stretch) are available in our APT
repository [2] as usual. Please be advised that the Debian 8 package
will be discontinued soon
The Debian packages for NAV 4.9 have been rebuilt using dh-virtualenv,
which means that most of the Python dependencies are now embedded into
the packages themselves. If you have previously added a priority apt pin
for packages from apt.uninett.no, you may now remove it, as there are no
longer any other packages needed from that repository to run NAV.
Please also be extra aware of config file changes. Look out for
`*.dpkg-dist` files in /etc/nav and make sure to update your running
config.
The virtual appliance is currently being updated at the time of this
writing, and will be uploaded soon.
Changes
=======
Fixed GitHub issues in this release:
* #1882 (Invalid VLANs are generated from Juniper switches)
* #1920 (Provide a hook for adding extra information in the What-If
tab in the IP Device Info page)
* #1946 (Vlans are categorized as linknets on Cisco Nexus with HSRP)
* #1953 (Adding new public filter in Alert Profiles fails)
* #1958 (NAV creates Graphite metrics with illegal characters in name)
* #1960 (Add option to control user administrator privileges from
LDAP)
Please see the release notes [3] for more details. Happy NAVing
everyone!
Links
=====
[1] https://github.com/UNINETT/nav/releases
[2] https://nav.uninett.no/install-instructions/#debian
[3] https://nav.uninett.no/doc/latest/release-notes.html#nav-4-9
--
mvh
Morten Brekkevold
Uninett