1.1. Release Notes 2.0.4¶
1.1.1. Improvements and New Features¶
- this version improves discovery of L2 links between devices that reuse MAC addresses. For example, Juniper SRX devices configured with aggregated links (interface name reth0) can use the same MAC address for the aggregated interface reth. The same MAC address can be assigned to these interfaces on different devices which makes discovery of L2 links using siwtch forwarding tables difficult. NetSpyGlass v2.0.4 introduces new method of L2 link discovery that helps resolve links in this situation even when devices do not run LLDP.
- fix discovery of LLDP links for Cisco Nexus devices (in some cases NetSpyGlass could not correctly identify remote interfaces identified by port id type “7” and port id that is interface name)
- add a workaround for the case where some devices do not report their own management address via standard RFC1213-MIB and IP-MIB Oids but return it as part of the table lldpLocManAddrTable in LLDP-MIB. This seems to happen on some Cisco Nexus devices.
- disable discovery of STP (Spanning Tree) configuration and state by default. Use configuration parameter discovery.parameters.enableSpanningTreeDiscovery=true to enable.
- NSGDB-121: added configuration parameter hbase.zookeeperPath. Default value is /hbase. Use this parameter if your hbase configuration parameter zookeeper.znode.parent has value different from /hbase
1.1.2. Bug fixes¶
- fix bug that under special circumstances could abort network discovery when one or several devices have tunnel interfaces (error in the log looks like “java.io.NotSerializableException: net.happygears.nw2.common.RouteTableEntry”)
- graphite connector did not check amount of data that was queued to be sent to Graphite Carbon collector. In busy NetSpyGlass server that tried to send many metrics to Carbon over high latency link, or when Carbon server was little slow to absorb the data, some metrics could be lost.