Re: IBM "Blade" interfaces - "Unknown" (63 Views)
Reply
Advisor
dick gripper
Posts: 51
Registered: ‎04-07-2008
Message 1 of 3 (63 Views)
Accepted Solution

IBM "Blade" interfaces - "Unknown"


Guys

Having issues getting IBM "Blade" interfaces to the correct state.
They are currently "unknown". Done the "netmon switch" bit:
ConnectorL2PortsLegacy=true
nonConnectorL2PortsLegacy=true
It's cured all the Switch interfaces regardless of vendor, but can get the "blades" managed, even through I can demandpoll. The blade stack also two cisco blades and they are OK, just the IBM's. Any help most appreciated.
Gripper
Trusted Contributor
ankit gupta_1
Posts: 121
Registered: ‎12-11-2007
Message 2 of 3 (63 Views)

Re: IBM "Blade" interfaces - "Unknown"

Hi Dick,
tell me this particular node is managed in your NNM Console or not?
If yes,so try to ping your interface IP from your NNM Console.
And last u have to poll the node through SNMP.if no try to put that community name in your NNM Console.

If you face any proble,feel free to ask me.

Points are welcome.

Regards
Ankit
Always Believe "The Best is yet to Come".
Advisor
dick gripper
Posts: 51
Registered: ‎04-07-2008
Message 3 of 3 (63 Views)

Re: IBM "Blade" interfaces - "Unknown"

Ankit..

Found out that the revision of blade Fiberchannel firmware doesn't "like" snmp requests and isn't "full" MIB2 compliant.

Other than that, they're fine...

Points given - closing the call

Thanks for your input

Gripper
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.