IP Multimedia Subsystem Connector SNMP capability
IBM Communication Service Enablers V7.2 IP Multimedia Subsystem Connector SNMP capability
This presentation deals with IBM IP Multimedia Subsystem Connector SNMP (Simple Network Management Protocol) Capability provided with ICSE version 7.2.
Table of contents
Table of contents Introduction High level architecture SNMP capability Netcool® versus IP Multimedia Subsystem Connector SNMP capability Installation and configuration Viewing the metrics Traps Reference
The agenda includes: - Introduction to the SNMP capability - High-level architecture of IP Multimedia Subsystem Connector - Features of the SNMP capability - Comparison between Netcool and IP Multimedia Subsystem Connector SNMP capability - Installation and configuration of the SNMP capability - How to view the metrics and understand it - An introduction to traps - Reference
Introduction
Introduction SNMP Capability collects information from ICSE (earlier known as WebSphere® software for Telecom) components such as Telecom Web Services Server (TWSS), Presence Server, IP Multimedia Subsystem Connector, and XML Document Management Server (XDMS) Each of these components publish two types of data : Performance metrics such as throughput and latency Fault and alarm Version 7.2 of ICSE comes with IP Multimedia Subsystem Connector SNMP Capability Replaces Tivoli® Netcool SSM/ASM Supports SNMP V1 / V2
SNMP Capability basically monitors the performance of devices over a network. Previously, ICSE (also known as WebSphere software for Telecom) used Tivoli Netcool. IP Multimedia Subsystem Connector SNMP Capability is a replacement and an enhancement to the features offered by Netcool. SNMP Capability collects information from ICSE components such as Telecom Web Services Server (TWSS), Presence Server, IP Multimedia Subsystem Connector, and XML Document Management Server (XDMS). There are two types of data that each of these components publish: • Performance metrics • Fault and Alarm In this release, IP Multimedia Subsystem Connector supports SNMP version 1 and version 2. Version 2 is also called version 2c, where “c” is for the community-based security that version 2 offers.
SNMP overview
SNMP overview Simple Network Management Protocol UDP-based application layer protocol SNMP uses an extensible design, where the available information is defined by management information bases (MIBs) MIBs describe the structure of the management data of a device subsystem; they use a hierarchical namespace containing object identifiers (OID) Each OID identifies a variable that can be read or set through SNMP SNMP request and response are in the form of protocol data units (PDUs) Each PDU has these fields: IP-header UDP-header version community PDU-type request-id error-status error-index variable-bindings
This slide provides an overview of SNMP. SNMP stands for Simple Network Management Protocol. It is an UDP-based application layer protocol. SNMP uses an extensible design, where the available information is defined by management information bases (MIBs). MIBs can be added and removed as per the requirement. But with this present offering, the WebSphere MIBs essential for SNMP Capability to function properly are packaged. MIBs describe the structure of the management data of a device subsystem; and use a hierarchical namespace containing object identifiers, known as OIDs. Each OID identifies a variable that can be read or set through SNMP. This slide also contains the typical protocol data unit or PDU format for SNMP request and response, which contains the IP-header, UDP-header, version community, and so on. Variable-bindings is the column where the OID and its value is contained.
High-level architecture of SNMP Capability
High-level architecture of SNMP Capability
High-level architecture of IP Multimedia Subsystem Connector SNMP Capability is shown in the diagram. Generally, there is an SNMP monitor provided by the service provider. This presentation takes the example of the MIB explorer that comes along with Tivoli Netcool. The monitor sends an SNMP query to the SNMP capability, which is the JAR file. The SNMP capability in turn contacts either the WebSphere Application Server or the WebSphere Enterprise Service Bus and it retrieves data from the PMI infrastructure of WebSphere. In addition to the Performance metrics, there is the Fault and Alarm feature. Whenever there is a fault in any of the ICSE (also knows as WsT – WebSphere software for Telecom) components, it sends a JMX notification to the SNMP capability, which in turn converts it into a trap and sends it to the SNMP monitor.
SNMP capability
SNMP capability IP Multimedia Subsystem Connector SNMP Capability: Connects to WebSphere Application Server using SOAP/RMI with or without security Opens a datagram socket listening on a specified port for SNMP requests Parses the SNMP requests Queries and retrieves the requested attribute values from the WsT or ICSE cluster and responds back to the requestor as SNMP response PDU Receives notifications from the WsT or ICSE cluster, transforms the same to an SNMP V1 /V2 Trap PDU, and sends the trap to the monitor
Some of the SNMP Capability features are: - It connects to WebSphere Application Server using SOAP/RMI with or without security. - It opens a datagram socket listening on a specified port for SNMP requests. - When it receives the request, it parses them and looks for the OIDs requested. - Then it queries and retrieves the requested attribute values from the WsT cluster illustrated in the previous slide. - It also receives notifications from the cluster, transforms the same to an SNMP v1 /v2 Trap PDU, and sends the trap to the monitor.
Netcool versus IP Multimedia Subsystem Connector SNMP capability
Netcool versus IP Multimedia Subsystem Connector SNMP capability Netcool Supports up to WebSphere version 6; temporary support for 7.0 Multiple subagents Uses server side application No specific traps feature for notifications from WebSphere Usage – command line and configuration files Extensible to any SNMP-enabled software SNMP capability Supports WebSphere version 7 and above Single agent (for WebSphere) No server side application Traps feature present for notifications from WebSphere Usage – single jar and configuration files Extensible to any SNMP-enabled software
Here is a comparison between Tivoli Netcool and IP Multimedia Subsystem Connector SNMP Capability. Netcool supports up to WebSphere version 6, and it also has a temporary support for 7.0. But going forward, ICSE monitoring support is provided by SNMP Capability. Netcool has multiple agents for different kinds of application servers, and IP Multimedia Subsystem Connector SNMP capability is only for WebSphere. Netcool uses a server side application to gather perform metrics, and SNMP capability does not use any server side application. There is no specific traps feature for notification from WebSphere in Netcool. This is a new feature added in SNMP capability for receiving fault and alarm from ICSE components and transforming them into traps. The usage is quite similar, except that SNMP capability is a single jar file and configuration files. Also, both Netcool and SNMP capability are extensible to any SNMP-enabled software.
Installation and configuration
Installation and configuration Pre-installation tasks – JRE version 1.6 and above, WebSphere version 7.0 and above Installation – A .zip file containing the SNMP capability jar file and configuration folders (Recommended to install on Deployment Manager machine) Configuration – Three XML files agentConfig.xml, jmxConfig.xml and trapConfig.xml agentConfig.xml – contains SNMP capability details jmxConfig.xml – contains details of WebSphere Application Server to be monitored trapConfig.xml – contains trap destination details Running the SNMP capability java [-options] –jar SNMPCapability.jar Troubleshooting – requires an additional argument while running the jar file java -Djava.util.logging.config.file=config/Logging.properties –jar SNMPCapability.jar
Before you install, check if the JRE version is 1.6 or above, and if the WebSphere version is 7.0 or above for both WebSphere Application Server and WebSphere Enterprise Service Bus. There is an interactive installer that comes along with IP Multimedia Subsystem Connector that helps you install the SNMP capability. The installation is straightforward. There is a .zip file that needs to be unpacked to any location on the system. This is done by the interactive installer. The procedure is described in detail in this slide. It is best that the SNMP capability is installed on the Deployment Manager machine. The configuration is mainly done through three XML files: - agentConfig.xml contains the SNMP capability details, such as the host name and the port on which the Java™ process is going to run. - jmxConfig.xml contains the details of WebSphere Application Server that has to be monitored - trapConfig.xml contains the trap destination details Details of the jmxConfig.xml file are mentioned in the next slide. To run the SNMP capability, run the jar file. Logs can be collected by providing an additional argument as given in this slide.
jmxConfig.xml
jmxConfig.xml
The jmxConfig.xml file contains all the details of the WebSphere Application Server that needs to be monitored. connectorType - can be SOAP or RMI. It is taken as SOAP by default. security - is the WebSphere security. It can be "yes" or "no". If "yes", the user name and password used to log onto the administration console is required. For the SOAP MBean Server: - the address is the WebSphere Application Server address - the port is the SOAP port - sample interval is recommended to be at least 60 so that performance is not hindered - the user name and password is required if security is enabled and it is the credentials used to log on to the administration console There are certain attributes that need to be specified for SSL security, like the path and password to the trust Store and key Store, and the path to the connectorSOAPconfig, which is the properties file provided by WebSphere Application Server for connection using SOAP. The attributes are similar for RMI. There is another node called MBean. This is where you can specify the collections or MBeans that have to be monitored. A collection node will have attributes such as expression, which gives the regular expression that is to be used to map MBeans that are to be monitored. There is counter mode, which can be automatic or manual. If it is automatic, all counters of the matched MBean are collected. If it is manual, the counters have to specified in a comma-separated format. This is the only part of the XML that is dynamic, which means it can be changed even while the capability is running. The other part of the XML can be changed after stopping and starting the capability.
agentConfig.xml
agentConfig.xml