CSS11150 management port snmp support

[Neil Preston]

Problem with SNMP to CSS11150 management interface, the documentation indicates that SNMP management of this CSS interface is possible for retrieving port information but it doesn't seem to work. Note we must manage the device by the management interface as we operate the CSS devices as pairs in an ACTIVE/STANDBY configuration.

CSS11150 software version ap0610405, CSS SNMP config as standard (no restrictions, communtiy names, trap destinations etc)

[Gilles Dufour]

could you define exactly what is not working ?

Is it snmp ?

Is it just the port info ?

Did you verify connectivity with the management port from your server/host ?

Regards,

Gilles.

[Neil Preston]

connectivity to the management port works fine (icmp) from the snmp server, when I test snmp connectivity using HP openview there is no response. No response when I try to snmpwalk the device either it just times out. Using a packet sniffer I can see that the snmp requests get to the CSS management port using the correct read-only community string but the CSS will not respond. The peer ACTIVE CSS does respond when I snmpwalk its management interface, this problem is applicable to the standby unit only.

[jesp]

Make sure that whatever is connection to the management port is originating from an address that is in the same subnet as the management port address.

If not, then the CSS will route the reply back to whatever the routing table suggest as the optimal route (your 0.0.0.0 proberly) - But if that is firewalled (next hop is a firewall, or there is a firewall on the way back), the packet is going to be dropped by the firewall.

So most likely the CSS is responding but the response is sent on one of the gig ports.

You have two choices:

1 : make sure the HP openview box has an interface in the same subnet as the CSS management interface.

2 : connect to an address that is on one of the gig ports.

[Neil Preston]

I don't think this is the issue, i have ping/telnet/html access to the management port from my openview box, the problem is specific to snmp, using a packet sniffer I was able to prove that the CSS did not respond to the snmp queries

[jfoerster]

Hi,

which sort of "standby" are you using? Are you using box-to-box redundancy or VRRP redundancy?

In case of box-to-box the standby CSS won't respond until the acitve box fails.

Kind regards,

Joerg

[Neil Preston]

Hi,

we are using box to box redundency, however I thought that was the whole point of the CSS management port, i.e you can manage the device via that port regardless of the fact it is in STANDBY state. In standby state the management port does respond to ping traffic, we have telnet capability, HTML access etc, but no snmp functionality.

[t814687]

Hi, we have almost same issue right now where we have connectivity to CSS via mgmt port from NNM. We trying to use mgmt ip in NNM to poll the device status, but when the NNM pools the device it uses global ip interface table and it can not see the mgmt port IP there and delets the device. is there a way to overcome this?