| Table of Contents |
|---|
Initialisation
References
- Definition
SOS is assigned the OID: 1.3.6.1.4.1.24723Anchor sos_oid sos_oid - explanation: iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 24723
- see http://oid-info.com/get/1.3.6.1.4.1.24723
Resources
- Articles
- Network Management and SMTP
- Microsoft Technet Article: How SNMP works
- Downloads
Prerequisites
- Each message transferred by SNMP has to be assigned a respective OID that is an extension to the SOS assigned OID
- OIDs used for a product such as JobScheduler, JADE would YADE would be assigned a product extension.
- For a specific product the OID is further extended for use by messages for that product.
- OIDs of all SOS products are collected into one MIB.
Component Architecture
- Presentation: JobScheduler_SNMP_Support.pptx
- Document: JobScheduler_SNMP_Support.pdf
PDF name JobScheduler_SNMP_Support.pdf
Implementation
Prerequisites
- Implementation for SNMPv3
- No previous versions are supported
SNMP Messages
SNMP Message Types
- Communication makes use of a set of predefined message types.
- Excerpt extracted from chapter SNMP Message Types in http://technet.microsoft.com/en-us/library/cc783142(v=ws.10).aspx#w2k3tr_snmp_how_oqdv:
...
| SNMP Message | From / To | Message Description |
|---|---|---|
Inform | Manager / Agent | This command is similar to the Trap initiated by the Agent, additionally Inform includes confirmation from the SNMP Manager on receiving the message |
| Response | Agent / Manager | It is the command used to carry back the value(s) or signal of actions directed by the SNMP Manager |
SNMP Trap Types
- Communication makes use of a set of predefined trap types.
- Excerpt extracted from chapter SNMP Trap Types in http://technet.microsoft.com/en-us/library/cc783142(v=ws.10).aspx#w2k3tr_snmp_how_oqdv:
| Trap Type | Trap Name | Description |
|---|---|---|
0 | ColdStart | The SNMP agent initialized its configuration tables. |
1 | WarmStart | The SNMP agent re-initialized its configuration tables. |
2 | LinkDown | The state of a network adapter on the SNMP agent changed from up to down. |
3 | Linkup | The state of a network adapter on the SNMP agent changed from down to up. |
4 | authenticationFailure | The SNMP agent received a message from an SNMP manager, but the message contained an invalid community name. |
5 | egpNeighborLoss | The SNMP agent could not communicate with its Exterior Gateway Protocol (EGP) peer. |
6 | enterpriseSpecific | Reserved for vendor-defined error conditions and error codes. |
Communication
- UDP is the only protocol being used.
- By default SNMP uses port 161 for request / response.
- Commands for Trap and Inform use port 162 for communication.
Implementation Architecture
- JobScheduler Monitoring Interface
- is moved from operation as a job to operation in a servlet container
- works independently from JobScheduler
- uses the JobScheduler database as exclusive source of information
- JobScheduler SNMP Agent
- is implemented as a concurrent process in the JobScheduler Monitoring Interface