1. System Center 2012 Device Monitoring Solution
Created by Tyson Flint & Gabe Markowitz
March 26th, 2014

2. Overview of Devices used for the Proof of Concept 25 Different Hardware Types
IP Based Security Cameras
Digital Alarm Receivers
Panasonic WV-NW484S
Bosch D6600
Panasonic WV-NF284
Lantronix UDS 2100
Panasonic WV-SF336 H264
Lantronix CoBox-FL-11 UDS
ArecontVision AV3135
ArecontVision AV2155 H264
Stentofon Zenitel (Intercoms)
ArecontVision AV8365 H264
Sony SNC-DH120_VCS2
Stentofon Master Exchange - AlphaWebXE
Sony SNC-DH220 H264
AlphaWebX
Sony SNC-DH140_VCS2
IQinVision IQA12S
IQinVision IQeye852
Intrusion Panel
IQinVision IQA10S
Bosch B420 Intrusion Panel
Axis P3354 H264
Axis P3344
Axis P3343 H264
PoE Switch
Power Supply Panels
Interlogix GE-DS-82-POE Managed Switch
LifeSafety Power
Altronix
Storage Array
Equilogic MD1000
Access Control Panels
Mercury (Lenel) LNL-3300
5 camera manufacturers
7 non-camera manufacturers
(dealt with 12 different companies)
25 different hardware models were represented
Device discoveries for models made by a manufacturer were common to all devices by that manufacturer, for example all ArecontVision cameras had PSIA support, but no SNMP support, all Axis cameras had temperature probes. 2 2 2 2 2

3. Overview of Investigation
Evaluate device for SNMP support or not.
Support for enabling SNMP remotely via HTTP.
Remote reboot capability either by writing to a value to an OID or by using a special HTTP request.
Are the OIDs writeable, or read-only (like the sysContact, sysName, sysLocation, sysDescription fields – info pulled by SCOM).
Do the OIDs returned by an SNMPWalk show custom private enterprise OIDs? Are we able to get the MIB file from the device manufacturer?
Do the devices have sensors or probes and can they be alerted upon via SNMP or HTTP?
Which version of SNMP does the device support (v1, v2c, v3)?
Rebooting a camera remotely is one of the methods we use to resolve issues remotely.
Another method to remotely resolve issues is to cycle the power for that camera on the network switch’s PoE port.
SNMP v1 – Community string is the only security
SNMP v2 – Adds the ability to add a approved IP range for management tasks
SNMP v3 – Adds individual username support for securely managing device across the public internet 3 3 3 3 3

4. Standard OIDs used by System Center 2012 All SNMP Based Cameras, Security Panels, Power Supplies, Switches and Management Servers
Object Name
OID
Values
Comments
sysDescr
NW484 Series
Model number
sysObjectID ID
sysUpTime
23:20.6
Lapsed time after turning on a camera
sysContact
The address or the phone number of who's responsible for the device.
sysName
047 11XE OTC EAS #6801
A friendly name to be used to manage the camera
sysLocation
REDMOND-CAMPUS122-LNVR12
The name of the location where the camera is installed.
If a device has any support for SNMP, these OID were always present.
These are the OIDs that SCOM is pulling in from the devices to present useful information to the monitoring engineer.
Right now, one of our monitors alerts us when the sysUpTime is less than 24 hours, so the techs will know the device was recently rebooted. 4 4 4 4 4

5. SNMP Tools used in obtaining Device Information
The following tools were used in discovering PoC device capabilities:
GetIf -
iReasoning MIB Browser –
SmpSoft Free Command-line Tools –
Net-SNMP for Windows –
Fiddler HTTP debugging proxy –
WMI Code Creator –
Foundstone SuperScan – 5 5 5 5 5

6. Device Commonalties:
Commonalities across all devices used during the PoC:
Most devices utilized SNMP v1 and v2c
Most Devices used Standard MIB’s.
Many Device Manufactures have Enterprise OID’s for additional functionality.
Devices used Industry Standard OID’s.
1.1 – sysDescr egp
2.1 – interface counters cmot
1.3 – at transmission
ip counters – SNMP counters
Icmp counters ifMIBObjects
TCP counters – ipv6MIBObjects 6 6 6 6 6

7. Items That Could be Standardized:
What we found lacking that could be beneficial across all devices:
Better availability of Enterprise MIB Files. Out of 16 device manufactures we were able to obtain 5 Enterprise MIBs.
Standard way of enabling and configuring SNMP on devices.
Standard implementation of SNMP on devices. Some devices are read only!
Standardization of OID Values. SysUpTime for example has been implemented on some devices with different values. Example 23:23.6 & 23:23:6
Many devices have probes that are not available from SNMP.
OID’s can be difficult to pair with a friendly name unless tools are used.
MIB files with friendly descriptions. Many devices had blank descriptions. 7 7 7 7 7

8. Challenges: Challenges we found when working with devices:
Non- consistent way of enabling SNMP on devices. Some had web interfaces, some used web commands. Some devices SNMP was enabled by default with standard community strings.
Some devices have Read Only sysDescr OID’s.
Obtaining MIB files from manufactures.
OID values returned are not consistent with the data type represented.
Senor data available in ONVIF, PSIA and HTTP but not available via SNMP.
MIB’s are not always friendly. Some OID’s give a name such as Sensor 2 but don’t provide a description of the sensor. 8 8 8 8 8

9. Nice to Haves:
Items that would make implementing SNMP Monitoring easer:
MIBs available for download or embedded on the device’s file system.
MIBs should have the description field populated. OID names are not always Intuitive.
sysDescr OIDs should be writable.
Device senor information available through SNMP OIDs.
Standardization and enforcement during firmware development of OID values for given data types. (TimeTicks)
More devices with support for SMNP v3. 9 9 9 9 9

10. System Center 2012 Demo

11. Questions?

12. Thank you.