1 / 12

System Center 2012 Device Monitoring Solution

System Center 2012 Device Monitoring Solution. Created by Tyson Flint & Gabe Markowitz. March 26th, 2014. Overview of Devices used for the Proof of Concept 25 Different Hardware Types. IP Based Security Cameras Panasonic WV-NW484S Panasonic WV-NF284 Panasonic WV-SF336 H264

chelsea-roth
Download Presentation

System Center 2012 Device Monitoring Solution

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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 Concept25 Different Hardware Types IP Based Security Cameras • Panasonic WV-NW484S • Panasonic WV-NF284 • Panasonic WV-SF336 H264 • ArecontVisionAV3135 • ArecontVisionAV2155 H264 • ArecontVisionAV8365 H264 • Sony SNC-DH120_VCS2 • Sony SNC-DH220 H264 • Sony SNC-DH140_VCS2 • IQinVision IQA12S • IQinVision IQeye852 • IQinVision IQA10S • Axis P3354 H264 • Axis P3344 • Axis P3343 H264 Power Supply Panels • LifeSafety Power • Altronix Access Control Panels • Mercury (Lenel) LNL-3300 Digital Alarm Receivers • Bosch D6600 • Lantronix UDS 2100 • Lantronix CoBox-FL-11 UDS-5350558 Stentofon Zenitel (Intercoms) • Stentofon Master Exchange - AlphaWebXE • AlphaWebX Intrusion Panel • Bosch B420 Intrusion Panel PoE Switch • Interlogix GE-DS-82-POE Managed Switch Storage Array • Equilogic MD1000

  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)?

  4. Standard OIDs used by System Center 2012All SNMP Based Cameras, Security Panels, Power Supplies, Switches and Management Servers

  5. SNMP Tools used in obtaining Device Information The following tools were used in discovering PoC device capabilities: • GetIf - http://www.wtcs.org/SNMP4tpc/getif.htm • iReasoning MIB Browser – http://ireasoning.com/mibbrowser.shtml • SmpSoft Free Command-line Tools – http://www.SNMPsoft.com/freetools • Net-SNMP for Windows – http://www.net-SNMP.org • Fiddler HTTP debugging proxy – http://www.telerik.com/fiddler • WMI Code Creator – http://www.microsoft.com/en-us/download/details.aspx?id=8572 • FoundstoneSuperScan – http://www.mcafee.com/us/downloads/free-tools/superscan3.aspx

  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 8.1 -- egp • 2.1 – interface counters 9.1 -- cmot • 1.3 – at 10.1 -- transmission • 4.1 -- ip counters 11.1 – SNMP counters • 5.1 -- Icmp counters 31.1 -- ifMIBObjects • 6.1 -- TCP counters 55.1 – ipv6MIBObjects

  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.

  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.

  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.

  10. System Center 2012 Demo

  11. Questions?

  12. Thank you.

More Related