Idea Details

SysEdge should report all(!) IP addresses configured on a device

Last activity 03-30-2016 02:18 PM
Kristian_S's profile image
03-30-2016 02:06 PM

## What is the use case of the new feature?

Our customer has configured a second IP address on a physical Ethernet interface:

[root@amd1 ~]# ifconfig -a

eth0 Link encap:Ethernet HWaddr 00:08:02:46:0B:EB

inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0

...

eth0:1 Link encap:Ethernet HWaddr 00:08:02:46:0B:EB

inet addr:192.168.2.4 Bcast:192.168.2.255 Mask:255.255.255.0

 

The second IP address however did not appear in monitoring applications like Spectrum and we found out that this is because SysEdge doesn't report the second IP.

When dumping the agent one would expect that the second IP address is listed in the ipAddrTable (1.3.6.1.2.1.4.20), while this is the MIB tree providing all IPv4 addresses in the current releases. However this is not the case; only the first IP address on the physical interface (and the loop back interface) is (/are) listed:

.1.3.6.1.2.1.4.20.1.1.127.0.0.1 IpAddress 127.0.0.1

.1.3.6.1.2.1.4.20.1.1.192.168.1.4 IpAddress 192.168.1.4

.1.3.6.1.2.1.4.20.1.2.127.0.0.1 Integer 1

.1.3.6.1.2.1.4.20.1.2.192.168.1.4 Integer 2

.1.3.6.1.2.1.4.20.1.3.127.0.0.1 IpAddress 255.0.0.0

.1.3.6.1.2.1.4.20.1.3.192.168.1.4 IpAddress 255.255.255.0

 

The MIB tree ipAddressTable (1.3.6.1.2.1.4.34) is even totally empty and doesn't provide any information at all.

 

## Describe the new feature in detail

We want SysEdge to report all(!) IP addresses that are configured on a device.

 

## Describe how you envision this new feature being implemented

Best would be to finally implement the ipAddressTable as intended and provide all configured IP addresses in that MIB tree including IPv4 and IPv6 addresses.

 

## What business problem will be solved by adding this new feature?

The customer can't see the second IP address in Spectrum to have it documented in his NMS. But beside specific use cases, that customers can't find out from the agents which IP addresses are already in use and that custom modules for cluster devices don't work, this is something the SysEdge is made for (to provide system information) and what it currently isn't fully doing.

 

## Describe the importance and urgency

importance: middle

urgency: low


Comments

03-30-2016 02:18 PM

It's not really a secondary address but rather a logical subinterface.  It would be great if it appeared as such and show up as "stacked" on the physical interface, similar to how VLAN interfaces show up on routers and switches.