SCOM SNMP Trap Management Pack for SEH ISD Print Servers

There is no COTS MP for monitoring SEH ISD300 Print Server devices.

Link to SEH Products Page Here

So I have authored a pack which is fairly clunky as it simply listens for SNMP traps and creates an alert 🙂 Feel free to take a copy if you have the need for it. It is Unsealed so you may want add some better functionality. I had to do it in a rush as I was migrating MOM2005 MP monitoring of the devices into SCOM 2007.

So the devices are Black Box SNMP hardware in terms of SCOM monitoring so I started by making contact to SEH and asked for the MIB database files so I can MIB walk the device and see what OID’s they have to which he replied they cannot supply. Anyway I will not go into MIB files and what you can and cant do with SNMP as it is a big area but in a nutshell my task is to migrate existing monitoring in MOM and get into SCOM. The pack is an SNMP trap based pack not SNMP read or SNMP probe. Passive monitoring I guess..

So I managed to get hold of the list of Error Codes that the SEH ISD 300 sends and they are as Follows.

ERROR (CRITICAL):

ISD300 Hardware Version 1.x + 2x
1 file-system check error
2 spool partition failed
3 SWAP error

ISD300 Hardware Version 3.x
1 file-system check error

ISD400 and ISD410
1 Spool partition failed
3 SWAP error

ISD300, ISD400 and ISD410
37 Driver package Installation Error
38 Driver package creation error
102 Active services check
103 Domain membership check
104 Windows client enumeration: connection count (>120)
105 Connection check: (local services)
106 S.M.A.R.T.: Temperature (>75) degree C
107 S.M.A.R.T.: HDD health status
108 Domain service health check: count max 0 (Winbind sockets)
109 Consistency check: (TDB check)
112 Backup Error
114 Spooler down
118 Cups Job Number (number of print jobs per queue >300)
130 Software Update Error
199 Emerge Reboot

WARNINGS:

203 Password for user ‘xxxxxxx’ changed
204 Windows client enumeration: connection count (>60)
205 Print queue ‘xxxxxxx’ deleted
206 S.M.A.R.T.: Temperature (>70) degree C
207 Printeradmin changed
208 Domain service health check: count max xx (Winbind sockets)
212 Printer Administrator lookup:
213 Memory usage check: usage at xxx percent (swap x MB)
214 Spool partition size check: usage at (>80) percent
215 Deamon health check: xxxx
216 Watchdog self test: size xxxxkb
217 Watchdog self test: count: x/x
218 Cups Job Number (number of print jobs per queue >200)
230 Software Update successful
299 Too many faulty logon attempts (as of SW 15.2.x / 16.2.x)

MESSAGES (INFORMATION):

305 Print Queue created
311 Logfile sent (as of SW 15.2.x / 16.2.x)
312 Backup created
314 Logfile backuped

SNMP TRAP DEFINITION

seh OBJECT IDENTIFIER ::= { enterprises 1229 }
sehisd OBJECT IDENTIFIER ::= { seh 3 }
sehtraps OBJECT IDENTIFIER ::= { sehisd 9 }
isdErrNo “error code” ::= { sehTraps 1 }
isdErrStr “textual representation” ::= { sehTraps 2 }

OID:
1.3.6.1.4.1.1229.3.9.1 => isdErrNo
1.3.6.1.4.1.1229.3.9.2 => isdErrStr

I have selected I think 17 of these Alerts as this is what the Print Server Support team wanted therfore the MP does not include all of the above but you can add should you need..

  • First thing to do is ensure you have a GW/RMS/MS or Agent Managed device to act as the SNMP Trap Catcher for the SEH or Network devices. I always use a dedicated Agent Managed SNMP Trap Server for this pupose as I do not like using the RMS. Also you often find in organisations SNMP security is tight, if not locked down for all but authorised devices so they likely dedicate a hardened server for SNMP trap handling for the monitoring. For help seting up SNMP on the SNMP Trap Server see this post.
  • Next thing you need to do is Discover the SEH or Network Device  in SCOM. The thing to remember here is that for the Discovery since the RMS is responsible for this task you will need to have SNMP Read access – UDP 161 to the Network Device. I will not detail how to discover network devices here.
  • Once the Discovery has finished what you MUST MUST remember to do is  make sure the SEH or Network device in the Administration Console/Network Devices view is managed by the Server that you have assigned as the SNMP Trap Server,  the SEH or network devices send there SNMP traps to.  Also remember to allow the SNMP Trap handling Server to ‘Act as proxy and discover managned objets on other computers’ in the Admin/Security Settings.
  • The Network availablilty for the SEH/network device will not be performed by your SNMP Trap Server at this points so additionally you will need to ensure the SNMP Trap Server also has SNMP Read access UDP 161 to the SEH or Network device to ensure the Device Availability Monitor will work..

Note: One thing to note about the SNMP settings on the SNMP trap Server is that the Security Tab is relevant to the Security for inbound connections so the SEH/Network devices to the SNMP Trap Server whereas the ‘Traps’ tab is what the SCOM agent will use to forward to Management Group so make sure the Community string is the same as the Rule or Monitor else it just will not work. Remember also when changing any SNMP settings always restart the service. many a time have I been troubleshooting SNMP alerts and failed as I have overlooked this. Additionally I always restart the OpsMgr health service also.
Secondly Load the SEH Override MP Pack into your test environment. Download Pack Here
Modify the Group named ‘ SEH Print Servers Group’ and set up a dynamic formula to populate or explicitly add which I do not advise especially when you have to import packs into other Management groups and the correct members are wrong. I used ( Object is SNMP Network Device AND ( Device Name Matches wildcard ?PDV ) AND True ) for my Dynamic query. Remember the SNMP device class is SNMP Network Device.
Note that there are some interesting things you need to know about SNMP Classes and how to improve SNMP health monitors. A fab post out here.

    Override the Monitors to Enabled and target ‘SEH Print Servers Group’

I will not go into detail here but you can for example create your own SNMP class with the help of a MP authored in the community here. I have not used this in this case but instead have targeted my monitors to the SNMP Network Device Class as default Disabled and we then override them to the Target Group ‘ SEH Print Servers Group’ mentioned above.

Advertisements
This entry was posted in Authoring, Management Packs and tagged . Bookmark the permalink.

One Response to SCOM SNMP Trap Management Pack for SEH ISD Print Servers

  1. Matthieu says:

    Very helpful for management pack on Scom 2012, Thanks.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s