Highlighted
2 Bronze

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.

0 Kudos
Reply
7 Replies
Highlighted
Not applicable

generald,

What version of Smarts IP are you currently running?

I have searched thru the Certification Matrix and it doesn't appear this device has been fully certified in any release.

You can try adding the line to see if it provides the desired output, but it is not a guarantee.

I have verified our code from IP versions 812 to 9.2 and these standard MIB's are present so you should get the correct Monitoring by adding the line:

CPU/Memory                      = HostResources:DeviceID

Follow these steps:

1) Add the line to the certification

2) Reload OID(./sm_tpmgr -s <AMPM_domain> --reloadoid)

3) Re-discover the device

Reply
Highlighted
2 Bronze

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.

0 Kudos
Reply
Highlighted
2 Bronze

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.

0 Kudos
Reply
Highlighted
Not applicable

generald,

You can also try either of the following:

CONT = Generic-Switch

or

CONT = Generic-MIB2


If either of these changes does not work we can perform some testing in house for you. We would need a walk of the device.


Run the following command to perform a mibwalk using the Smarts mibwalk utility located in the IP bin directory <basedir>/IP/smarts/bin/sm_snmpwalk <host_or_IP_of_device>

Remember to perform the following steps when making changes to the Oid2Type_Field.conf

1) Add the line to the certification

2) Reload OID(./sm_tpmgr -s <AMPM_domain> --reloadoid)

3) Re-discover the device


0 Kudos
Reply
Highlighted
2 Bronze

Hi generald,

You need to do one additional step.  The entry you added in the instrumentation section tells the reconfiguration process what instrumentation to create for a CPU or Memory.  It does not however tell the discovery process to discover the CPU or Memory.  You need to add another entry to the oid2type entry.  It should look like this:

# IBM Switch

.1.3.6.1.4.1.20301.1.18.13 {

TYPE          = Switch

VENDOR        = IBM

MODEL         = EN4093 10Gb Scalable Switch

CERTIFICATION = TEMPLATE

HOSTRESRCS    = MIB2                      <===================


INSTRUMENTATION:

Interface-Fault                 = MIB2

Interface-Performance           = MIB2

Port-Fault                      = MIB2

Port-Performance                = MIB2

CPU/Memory                      = HostResources:DeviceID

}

The HOSTRESRCS instructs the discovery front end to run the discovery that will find the CPU and Memory and create them if the device responds to the queries.

Hope this helps.

Ray

0 Kudos
Reply
Highlighted
2 Bronze

One final thing in case you did not know.  The HostResources tells the reconfiguration process to create instrumentation objects of CPU_Performance_HostResources for the CPU(s) and Memory_Performance_HostResources for the Memory objects.  The DeviceID tells it to use the DeviceID attribute as the index appended to the OID.

Ray

Reply
Highlighted
2 Bronze

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.

0 Kudos
Reply