5150 Connectivity Module SNMP

SNMP Overview
Simple Network Management Protocol (SNMP) is a component of the Internet Protocol Suite as defined by the Internet Engineering Task Force (IETF) and is used for managing devices on IP Networks. SNMP consists of a set of standard for network management, an application layer protocol, a database schema and a set of data objects. It is used mostly in network management systems to monitor system configuration and overall conditions of managed devices (i.e. router, switch servers, workstations, printers, modem racks) connected on the network. SNMP exposes the information from the managed systems as variables. Each managed system executes at all times, a software component call an agent which reports status of the variables via SNMP to a network management system (NMS). The NMS runs the managing application that queries monitor and control the variables of the managed devices. SNMP uses the management information base (MIB) to define the information from the managed devices. MIB describes the information through structure of hierarchical namespaces containing object identifiers (OID) where each OID identifies if a variable can be read or set via SNMP. MIB uses the notation defined by Abstract Syntax Notification One (ASN.1). SNMP operates in the application layer of the Internet Protocol Suite (Layer 7 of the OSI model). The SNMP agent receives requests on UDP port 161. The SNMP manager may send requests from any available source port to port 161 in the agent. The agent response will be sent back to the source port on the SNMP manager. The SNMP manager receives notifications on port 162. The agent may generate notifications from any available port. There are three protocol specifications in SNMP which can be differentiated by the number of protocol data units (PDU) they implement.
SNMPV1 implements the basic five (5) core protocol data units GetRequest, SetRequest, GetNextRequest, Response, and Trap. SNMPV2 implements all PDUs of SNMPV1 with the addition of the GetBulkRequest and InformRequest. SNMPV3 implements all the PDUs of SNMPV2 with the addition of security and remote configuration enhancements to SNMP.

Connectivity Module SNMP Structure

The 5150 Connectivity Module implements the basic SNMP implementation for its Ethernet interface as is found in almost any Ethernet enabled device. It supports the storage of the IP settings and keeps track of several counters for network traffic. This is indicated as the System Variables by the diagram shown below. The Project Variables block is the private ASCO MIB which is the structure definition of information from serial devices connected via TTL/RS485 ports. This so called private MIB was compiled to allow the read/write requests from the SNMP Manager via the Kernel SNMP module. SNMP requests are processed by the kernel depending on the private MIB description.

50 Hanover Rd, Florham Park, NJ 07932-1591 USA For sales or service call 1 800 800-2726 www.ascopower.com

381339-306

Connectivity Module SNMP

Connectivity Module SNMP Implementation

The Connectivity Module SNMP implementation is meant to be the SNMP management interface for the ASCO ATS (Automatic transfer switch). When SNMP feature is enabled, the Connectivity Module will request for the status and analog information from the ATS at regular interval. This is done by the SNMP_Scan function which also qualifies and stores all the incoming information. Whenever one is detected to be out of range or different from what was expected, SNMP_Scan sends out an appropriate SNMP to the SNMP manager. Take note that ASCO SNMP implementation only allows the SNMP managers to read information of the Connectivity Module and the ASCO ATS. It will not allow any write request. In addition, the SNMP feature is only available on the following Connectivity Module product lines: 629800-004 with firmware version 869764-003 and up. 629800-006 with firmware version 898381-003 and up.

For further information, see Connectivity Module manual 381333-367.

ASCO MIB File

Written using the MIB module definition language based on the Structure of Management Information (SMI) specifications, the official ASCO Power Technologies Management Information Base or MIB file was assigned the ASCO part number 934904. This MIB contains definition of objects, object hierarchy and object attributes describing the characteristics of the Connectivity Module-hosting a 7000 Series ATS with Power Manager Xp over Ethernet; it serves as a roadmap for monitoring and managing these two devices. The graphic at the right is a representation of the ASCO MIB file. A zip file containing the ASCO MIB file can be downloaded from the location shown below.
http://www.emersonnetworkpower.com/en-US/ Products/PowerSwitchingandControls/ MonitoringandControl/Pages/ ASCO5150ConnectivityModuleAcc72E.aspx

381339-306

Connectivity Module SNMP

SNMP Managers
To test the SNMP feature of the Connectivity Module, two industrially available SNMP managers, the AdRem SNMP Manager from AdRem software and the MGSOFT MIB Browser of MGSOFT were used. Both applications are capable of walking through device SNMP data, determining available OIDs , receiving trap messages and forwarding received trap messages. Each has an MIB compiler that comes with hundreds of precompiled MIBs that allow users to edit or create their private MIBs and recompile them for portability/distribution purposes. Packed with an MIB browser, both applications allows the user to browse through MIB tree data, create and use custom SNMP views for easier manageability. Both AdRem and MGSoft are powerful SNMP management consoles that give user an organized graphical view into a SNMP enabled device along with a straightforward way to control device remotely.

SNMP TRAP Messages

One important feature in SNMP is sending a trap. A trap is a one-way message sent from one application to another (which typically on a remote host); such as a router, switch or server; to the NMS. Their purpose is merely to notify other applications that something has happened, noticed, etc. One of the problems about SNMP trap is that messages are sent via UDP, which means they are not guaranteed to arrive. In addition, they are unacknowledged so no one will know if the remote application received the messages. Nonetheless trap messages are sent out anyway for notification. For the Connectivity Module, trap messaging is a way to notify changes on ATS status and power metering conditions. These changes are alarms in the ATS operation and are strictly monitored during runtime. Below is a list of ATS alarm conditions that are sent out as trap messages.
1. ATS transfer to emergency source 2. ATS retransfer to normal source 3. Engine running 4. Normal source unavailable 5. Emergency source unavailable 6. Power manager digital inputs 1 to 8 activation 7. Power manager digital outputs 1 to 4 activation

As an example, the next page shows captured screen shots from two SNMP manager applications running concurrently and monitoring the same connectivity module with a 7000 Series ATS; SNMP managers showing log for ATS transferred to Emergency source.

381339-306

Connectivity Module SNMP

MGSOFT SNMP Trap Ringer Console

ADREM SNMP Manager

381339-306

Connectivity Module SNMP

Monitoring SNMP Parameters

Using the ASCO MIB file, SNMP managers are able to monitor parameters in real-time through their MIB Browser. Following are screen-captured shots from different SNMP managers reading real-time parameters of ATS. Below is an Implementation of the ASCO MIB in the MGSOFT environment.

Parameters monitored above are: 1. Connectivity Module - baud rate, TCP port, serial reply timeout & retries 2. ATS - phase voltage, ATS position and source availability 3. Power Manager - power, current, voltage and digital I/O status

381339-306

Connectivity Module SNMP

The screen below shows an implementation of the ASCO MIB in the AdRem environment.

381339-306

Connectivity Module SNMP

Procedure to Enable SNMP

Observe safety precautions in manual 381333-367.

System/Peripherals needed:
Laptop computer (with Windows XP, MSIE version 6 or up & latest JRE loaded). ASCO Connectivity Module P/N: 629800004/006 with SW P/N:869764-003/898381003 or higher. OMRON 24V DC Power Supply if device not powered through the TTL by 7000 Series ATS. Ethernet crossover cable 7000 Series ATS 1. Configure your laptop with the following TCP settings. (Do this first before proceeding). IP Address: 169.254.001.100 Subnet: 255.255.000.000 Gateway: 000.000.000.000 2. Disconnect the Connectivity Module from Local Area Network (LAN). Make sure all ASCO device(s) are connected to the Connectivity Module. NOTE: If doing this OFFLINE from ASCO device(s), you can use the OMRON power supply to power-up the Connectivity Module. 3. Connect your laptop to the Connectivity Module using the crossover cable. Push the RESET button once to reset. 4. From your laptop, launch MSDOS and ping the connectivity module to confirm connection. You must receive replies from the Connectivity Module. Otherwise, double-check your connection and settings. 5. When you get ping replies from Connectivity Module, launch Internet explorer and type-in this URL on the address box; http://169.254.001.001/config.html to access log-in page.

6. From the configuration page, you will reconfigure the Connectivity Module to the required IP, subnet and gateway addresses given by the LAN administrator. As shown below, the IP Address was changed to 155.104.006.252. Make sure for the IP, subnet and gateway addresses have (4) octets where each octet has (3) three digits in it.

In addition, the serial speed you will assign must match the baud rate setting of the ASCO device(s) that are connected to the Connectivity Module.

7. Then click on the SNMP button, to view SNMP settings.

Just click on the login button to get through the configuration page.

8. Put a check on the checkbox SNMP Enabled to enable SNMP.

7

381339-306

Connectivity Module SNMP

9. Assign the community name for READ/WRITE and the IP addresses of the SNMP managers. 10. Assign the IP addresses of the SNMP managers. Start with the 1st IP address and be sure the addresses have 4 octets where each octet has 3 digits (xxx.xxx.xxx.xxx) in it. Click the Close button. 11. Review all the settings and hit Update Server to store changes. This will RESET the Connectivity Module. 12. Connect the Connectivity Module back to the LAN. Then hit RESET button once. 13. Before re-connecting to the same LAN, reconfigure your laptop with a unique IP address given by the LAN administrator. 14. Ping the Connectivity Module new IP address to make sure it is accessible on the LAN. 15. Ping the SNMP manager IP addresses to make sure they are also accessible on the LAN.
RESET button

Technical Support
All questions, concerns or request for technical support regarding the Connectivity Module SNMP feature must be forwarded to the ASCO Services through the addresses and contact number given below.
ASCO Services Inc. 60 Hanover Road Florham Park, New Jersey 07932 1 800 800 ASCO(2726) customercare@asco.com

381339-306