Management IP address on L2 devices

Discussion:

zenossuser714

2012-09-11 13:04:42 UTC

zenossuser714 [http://community.zenoss.org/people/zenossuser714] created the discussion

"Management IP address on L2 devices"

To view the discussion, visit: http://community.zenoss.org/message/68482#68482

--------------------------------------------------------------
Hello, People!

I recently began using Zenoss 4.2.0 and faced some problems with L2 devices (DSLAM). That devices (ZTE, Zyxel) don't provide management IP address information via SNMP, so Zenoss can't associate IP address/netmask and IP routing info with devices. Without that information Zenoss can't add device IP address to Networks tab (for IP address inventorization) and show that device in Network Map. Is it possible to define IP information statically?

Zenoss can successfully get L2 interfaces info (status, speed, rate) via SNMP.

Thanks in advance.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/68482#68482]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

nilie

2012-09-11 14:25:18 UTC

Permalink

zenossuser714

2012-09-11 16:40:48 UTC

Permalink

zenossuser714 [http://community.zenoss.org/people/zenossuser714] created the discussion

"Re: Management IP address on L2 devices"

To view the discussion, visit: http://community.zenoss.org/message/68508#68508

--------------------------------------------------------------
Hi nilie,

L2 devices have a management IP address/netmask, default gateway, static routes (L3 information needed for device management).

I want to place L2 devices on Network Map for simple visual monitoring. Also, as that devices use IP addresses, I want Network tab contain that addresses.

Thank You.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/68508#68508]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

nilie

2012-09-12 19:18:39 UTC

Permalink

nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: Management IP address on L2 devices"

To view the discussion, visit: http://community.zenoss.org/message/68529#68529

--------------------------------------------------------------
L2 devices have only a default gateway, no static routes and no routing table. However, taking a closer look on my Zenoss v3.1 server it seems you are right. There are some devices having IP addresses that do no show up in Networks tab. From what I could see in my case, those devices are only being pinged, no other performance collection is performed.
Now I don't understand any more how Zenoss is putting those IP addresses in its DB. I was expecting that whenever you add a device (even if it is just an IP address you're monitoring via ping) the IP address associated with that device (the management IP address in your case) should show up in Networks tab automatically.
Is anyone else having this issue ?
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/68529#68529]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

zenossuser714

2012-09-13 04:42:50 UTC

Permalink

Post by nilie
L2 devices have only a default gateway, no static routes and no routing table.

I don't agree with you here, manageable L2 devices also have a Connected route in routing table (for subnet in which it sits), also most manageable L2 devices have an ability to add static routes (needed to access device, not for traffic passing L2 device).

Post by nilie
Now I don't understand any more how Zenoss is putting those IP addresses in its DB.

As I understood, Zenoss add IP address in DB only if it knows a device subnet (via routing table). Without that info Zenoss knows only IP address (without mask), and can't determine to which subnet device belongs.

The problem in some devices, they don't provide needed information. In my case DSLAMs (ZTE 9806, Zyxel 1248).
L2 device Cisco Catalyst 2950 successfully provide that info (IP, routes).

If Zenoss has an ability to statically add IP address to DB it will solve the problem.

Thanks.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/68530#68530]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

nilie

2012-09-13 13:59:41 UTC

Permalink

nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: Management IP address on L2 devices"

To view the discussion, visit: http://community.zenoss.org/message/68541#68541

--------------------------------------------------------------
Is it Zenoss providing that routing info for your Catalyst 2950 or the switch itself ?

Here's what my Catalyst 2950 are saying :

BNCTRESWAN-LDN-2950S02#sh ip route
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^
% Invalid input detected at '^' marker.

BNCTRESWAN-LDN-2950S02#
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/68541#68541]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

zenossuser714

2012-09-13 17:33:51 UTC

Permalink

zenossuser714 [http://community.zenoss.org/people/zenossuser714] created the discussion

"Re: Management IP address on L2 devices"

To view the discussion, visit: http://community.zenoss.org/message/68550#68550

--------------------------------------------------------------
Catalyst 2950 provide subnet mask via SNMP, so Zenoss can determine subnet to which Catalyst connected.

*snmpwalk -c private -v 1 c2950.example.com ipAdEntNetMask*
IP-MIB::ipAdEntNetMask.192.168.0.2 = IpAddress: 255.255.255.0

IOS C2950 Software: 12.1(22)EA13
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/68550#68550]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

nilie

2012-09-13 19:06:54 UTC

Permalink

zenossuser714

2012-09-14 04:43:12 UTC

Permalink

Post by nilie
And the routes ? What is the OID to get them on your Catalyst 2950 ?

No. Neither Catalyst 2950, nor 3750 provides routes via SNMP. Only IP addresses/subnet masks. I think it is sufficient info Zenoss.

L2 switch ZyXEL ES-2108 provides IP address/mask and IP routes via SNMP.

*snmpwalk -c private -v 1 z2108.example.com ipAd*
IP-MIB::ipAdEntAddr.127.0.0.1 = IpAddress: 127.0.0.1
IP-MIB::ipAdEntAddr.172.16.234.13 = IpAddress: 172.16.234.13
IP-MIB::ipAdEntIfIndex.127.0.0.1 = INTEGER: 1
IP-MIB::ipAdEntIfIndex.172.16.234.13 = INTEGER: 1
IP-MIB::ipAdEntNetMask.127.0.0.1 = IpAddress: 255.255.0.0
IP-MIB::ipAdEntNetMask.172.16.234.13 = IpAddress: 255.255.255.128
IP-MIB::ipAdEntBcastAddr.127.0.0.1 = INTEGER: 1
IP-MIB::ipAdEntBcastAddr.172.16.234.13 = INTEGER: 1
IP-MIB::ipAdEntReasmMaxSize.127.0.0.1 = INTEGER: 65535
IP-MIB::ipAdEntReasmMaxSize.172.16.234.13 = INTEGER: 65535

*snmpwalk -c private -v 1 z2108.example.com ipRoute*
RFC1213-MIB::ipRouteDest.0.0.0.0 = IpAddress: 0.0.0.0
RFC1213-MIB::ipRouteDest.127.0.0.0 = IpAddress: 127.0.0.0
RFC1213-MIB::ipRouteDest.172.16.234.0 = IpAddress: 172.16.234.0
RFC1213-MIB::ipRouteIfIndex.0.0.0.0 = INTEGER: 1
RFC1213-MIB::ipRouteIfIndex.127.0.0.0 = INTEGER: 1
RFC1213-MIB::ipRouteIfIndex.172.16.234.0 = INTEGER: 1
RFC1213-MIB::ipRouteMetric1.0.0.0.0 = INTEGER: 1
RFC1213-MIB::ipRouteMetric1.127.0.0.0 = INTEGER: 1
RFC1213-MIB::ipRouteMetric1.172.16.234.0 = INTEGER: 1
RFC1213-MIB::ipRouteMetric2.0.0.0.0 = INTEGER: -1
RFC1213-MIB::ipRouteMetric2.127.0.0.0 = INTEGER: -1
RFC1213-MIB::ipRouteMetric2.172.16.234.0 = INTEGER: -1
RFC1213-MIB::ipRouteMetric3.0.0.0.0 = INTEGER: -1
RFC1213-MIB::ipRouteMetric3.127.0.0.0 = INTEGER: -1
RFC1213-MIB::ipRouteMetric3.172.16.234.0 = INTEGER: -1
RFC1213-MIB::ipRouteMetric4.0.0.0.0 = INTEGER: -1
RFC1213-MIB::ipRouteMetric4.127.0.0.0 = INTEGER: -1
RFC1213-MIB::ipRouteMetric4.172.16.234.0 = INTEGER: -1
RFC1213-MIB::ipRouteNextHop.0.0.0.0 = IpAddress: 172.16.234.4
RFC1213-MIB::ipRouteNextHop.127.0.0.0 = IpAddress: 127.0.0.1
RFC1213-MIB::ipRouteNextHop.172.16.234.0 = IpAddress: 172.16.234.13
RFC1213-MIB::ipRouteType.0.0.0.0 = INTEGER: direct(3)
RFC1213-MIB::ipRouteType.127.0.0.0 = INTEGER: direct(3)
RFC1213-MIB::ipRouteType.172.16.234.0 = INTEGER: direct(3)
RFC1213-MIB::ipRouteProto.0.0.0.0 = INTEGER: local(2)
RFC1213-MIB::ipRouteProto.127.0.0.0 = INTEGER: local(2)
RFC1213-MIB::ipRouteProto.172.16.234.0 = INTEGER: local(2)
RFC1213-MIB::ipRouteAge.0.0.0.0 = INTEGER: 0
RFC1213-MIB::ipRouteAge.127.0.0.0 = INTEGER: 0
RFC1213-MIB::ipRouteAge.172.16.234.0 = INTEGER: 0
RFC1213-MIB::ipRouteMask.0.0.0.0 = IpAddress: 0.0.0.0
RFC1213-MIB::ipRouteMask.127.0.0.0 = IpAddress: 255.255.0.0
RFC1213-MIB::ipRouteMask.172.16.234.0 = IpAddress: 255.255.255.128
RFC1213-MIB::ipRouteMetric5.0.0.0.0 = INTEGER: -1
RFC1213-MIB::ipRouteMetric5.127.0.0.0 = INTEGER: -1
RFC1213-MIB::ipRouteMetric5.172.16.234.0 = INTEGER: -1
RFC1213-MIB::ipRouteInfo.0.0.0.0 = OID: SNMPv2-SMI::zeroDotZero
RFC1213-MIB::ipRouteInfo.127.0.0.0 = OID: SNMPv2-SMI::zeroDotZero
RFC1213-MIB::ipRouteInfo.172.16.234.0 = OID: SNMPv2-SMI::zeroDotZero

L2 DSLAM devices don't provide any info for IP.

*$snmpwalk -c private -v 1 zxdsl1248.example.com ip*
*$*
*$snmpwalk -c private -v 1 ztdsl9806.example.com ip*
*$*
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/68552#68552]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]