Prerequisites for SNMP Devices
The CommandCenter-SP cost option allows any Simple Network Monitoring Protocol (SNMP) V1 compliant device to be added to the CommandCenter system either for monitoring and/or control purposes. When this cost option is enabled on a CommandCenter system any number of SNMP devices from different manufacturers can be added to the system.
The SNMP devices should be compliant with the following:
- SNMP 'agents' should be compliant with at least SNMP V1.
- SNMP devices should describe the SNMP implementation with the appropriate mib file/s. These files should be capable of being ‘compiled’ using an independent and widely used tool set such as MGSoft without any errors.
- CommandCenter requires the SNMP device to respond to a GET request to the following two
Object IDentifierS (OID's) in order for it to be added as a device to the system. Once the
device has been added CommandCenter will continue to 'poll' these OID's to detect the
presence or absence of the device in the system.
iso.org.dod.internet.mgmt.mib-2.system.sysDescr.0 (1.3.6.1.2.1.1.1.0)
.iso.org.dod.internet.mgmt.mib-2.system.sysName.0 (1.3.6.1.2.1.1.5.0)
Note: There is now an option (since V1.09) to specify a Poll OID for an SNMP device so if a device does not conform to the recommended SNMP specification then an OID can be defined when adding an SNMP device.
- Cortex can process/receive unsolicited SNMP V1 and V2c trap messages from SNMP devices, but when these are used it is preferable to be able to get the status object/s being referred to in the trap directly from a GET request.
- Where SNMP trap messages are sent by the device, it should be capable of sending these
to at least 2 different IP addresses as Cortex can be used with a redundant server.
Note: There is no requirement of Cortex for SNMP trap messages to be supported by the third party device.
- Enumerated integer types cannot have a value of 0.