Welcome, Guest. Please login or register.

Author Topic: 2nd HP onboard Administrator for Blade Systems  (Read 2465 times)

ascii

  • Full Member
  • ***
  • Posts: 100
    • View Profile
2nd HP onboard Administrator for Blade Systems
« on: May 07, 2014, 01:32:31 PM »
i changed the def file for the Bladecenter a little bit.

since i'm a network engineer i care more about the Interconnects than the Blades itself.
I see the interconnect Bays as modules not the servers.

Code: [Select]
# Definition for 1.3.6.1.4.1.11.5.7.1.2 created by Defgen 1.8 on 7.May 2014 (ascii)
 
# General
SNMPv 2HC
Type HPOA
Typoid 1.3.6.1.4.1.232.22.2.3.1.1.1.5.1
Sysdes 1.3.6.1.4.1.232.22.2.3.1.1.1.3.1
OS other
Icon bsgn
Size 10
Bridge
ArpND old
Dispro
Serial 1.3.6.1.4.1.232.2.2.2.1.0
Bimage 1.3.6.1.4.1.232.22.2.3.1.1.1.8.1
CfgChg
CfgWrt
VLnams
VLnamx
Group 1.3.6.1.4.1.232.22.2.3.1.1.1.9.1
Mode
 
# Interfaces
StartX
EndX
IFname
IFaddr adr
IFalia
IFalix
InBcast
InDisc
OutDisc
IFvlan
IFvlix
IFpowr
IFpwix
IFdupl
IFduix
Halfdp
Fulldp
 
# Modules
Modesc 1.3.6.1.4.1.232.22.2.6.1.1.1.6
Moclas
Movalu
Moslot 1.3.6.1.4.1.232.22.2.6.1.1.1.3
Modhw 1.3.6.1.4.1.232.22.2.6.1.1.1.9
Modsw
Modfw
Modser 1.3.6.1.4.1.232.22.2.6.1.1.1.7
Momodl 1.3.6.1.4.1.232.22.2.6.1.1.1.8
 
# RRD Graphing
CPUutl
Temp 1.3.6.1.4.1.232.22.2.3.1.2.1.6.2
MemCPU 1.3.6.1.4.1.2021.4.11.0
Custom Temp;G;C 1.3.6.1.4.1.232.22.2.3.1.2.1.6.3

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2780
    • View Profile
    • NeDi
Re: 2nd HP onboard Administrator for Blade Systems
« Reply #1 on: May 08, 2014, 01:13:06 AM »
Good point, I was considering that. But since the interconnects can be discovered as devices I thought I'd be redundant. Too bad the VC domain cannot exactly be found in the OA for mapping...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo