Unsolved
This post is more than 5 years old
6 Posts
0
2043
July 15th, 2013 11:00
IBM EN4093 switch discovery
Hi,
I was provided with the following addition in ./smarts/local/conf/discovery/oid2type_Field.conf
# IBM Switch
.1.3.6.1.4.1.20301.1.18.13 {
TYPE = Switch
VENDOR = IBM
MODEL = EN4093 10Gb Scalable Switch
CERTIFICATION = TEMPLATE
INSTRUMENTATION:
Interface-Fault = MIB2
Interface-Performance = MIB2
Port-Fault = MIB2
Port-Performance = MIB2
}
I want to monitor performance of CPU and Memory which are in the following OID:
hrProcessorLoad(1.3.6.1.2.1.25.3.3.1.2)
hrStorageSize(1.3.6.1.2.1.25.2.3.1.5),hrStorageUsed(1.3.6.1.2.1.25.2.3.1.6),hrStorageAllocationUnits(1.3.6.1.2.1.25.2.3.1.4)
My question is, will adding the following line make the the CPU and Memory monitoring work?
# IBM Switch
.1.3.6.1.4.1.20301.1.18.13 {
TYPE = Switch
VENDOR = IBM
MODEL = EN4093 10Gb Scalable Switch
CERTIFICATION = TEMPLATE
INSTRUMENTATION:
Interface-Fault = MIB2
Interface-Performance = MIB2
Port-Fault = MIB2
Port-Performance = MIB2
CPU/Memory = HostResources:DeviceID
}
Regards.
geraldmtl
6 Posts
0
July 15th, 2013 13:00
Hi jrabb,
we are still using 7.2, we are currently building a 9.x environment which should be ready in a few weeks.
We've opened a request with EMC and the EN4093 will be certified in the next release 9.2.2.
Our EN4093 needs to be monitored now, so i'll try with Smarts first and if it doesn't work, i'll have to script something.
Thanks for your reply, I'll update you on the result.
Regards.
geraldmtl
6 Posts
0
July 16th, 2013 06:00
So i made the modifications and it didn't discover the CPU/Memory components.
We'll wait for our new 9.x Smarts for proper discovery of the EN4093.
For now, we'll use another tool to monitor them.
Regards.
geraldmtl
6 Posts
0
July 24th, 2013 07:00
rpramuka,
Thank you for your input, I've done the modification but still cannot see the CPU and MEMORY. It looks like the discovery only finds the Interface, Port, IP and SNMP Agent.
I can't publish the snmpmibwalk since this is a client's switch.
Hopefully the next release 9.2.2. will fix that
Regards.