Broadband Cable Networks / Matti Susi June 2, 2004 1(7) EWS930 SNMP WIZARD FOR CATVisor EMS SERVER EWS930 SNMP Wizard is an SNMP agent service for the CATVisor EMS server. Through the agent an SNMP compatible NMS system can retrieve alarm information from the EMS server. The SNMP Wizard delivery contains a Windows base SNMP agent with an EMS server extension agent. The base agent is compatible with standard Windows extension agents and allows them to co-exist with the EMS server agent. An enterprise specific Teleste-EMS-MIB file is included in the delivery. Features Background information Compatible with standard Windows extension agents SNMPv1 support Monitoring of the EMS Server operation EMS event log as SNMP table Event log filtering, controllable over SNMP SNMP traps on new EMS events Suppression of specific traps, controllable over SNMP In many cable networks an NMS system is used as an umbrella management system for fault monitoring of the entire network hardware like including LAN devices, servers, telephony systems and cable data systems. The NMS system is used as the tool for the Network Operation Centre and therefore it should get information from the HFC system manager, as well. The easiest way to build such a link is to connect the HFC EMS system to the NMS over an SNMP link. By using the EMS in between, the NMS is released from the task of monitoring thousands HFC of elements and the NOC will still be informed about faults in the HFC system. The NMS can use the EMS servers data either by receiving the Traps from the EMS Server or by polling the EMS server MIB objects, or both. The SNMP Wizard has been designed to support both operation modes to let the operator select the mode that best suites to the operational procedures of the Network Operations Centre and the NMS system in use.
Broadband Cable Networks / Matti Susi June 2, 2004 2(7) System configuration with SNMP Wizard SNMP Network Manager EMS Explorer (EMS client) Intranet/ Internet EMS Server with SNMP Wizard Headend and HFC Network Elements Figure 1, System configuration with SNMP Wizard Computer requirements for SNMP Wizard See section: Computer requirements, EMS Server in the EMS System product Specification. MIB-2 (RFC 1213) support The SNMP Wizard implements MIB-2 System fully and the two first objects from the SNMP object group. The coldstart trap is sent each time when the SNMP Wizard process is started. Note: The value of the sysservices object is user selectable over the base agent configuration tool. EMS server status objects The EMS server information and status is indicated by the following MIB variables: servername servertimesincelastresponse servernoresponsetimeout The servertimesincelastresponse indicates the time since the last response from the EMS server process. The servernoresponsetimeout defines the maximum value of the servertimesincelastresponse before the agent declares the connection to the EMS server broken and sends a serverdown (9) trap.
Broadband Cable Networks / Matti Susi June 2, 2004 3(7) The emseventloginfo The emseventloginfo object group contains statistical information about the EMS server event log. The following objects are included: eventlogactivealarms number of active alarm events eventlogactivewarnings number of active warning events eventlogactivenotifications number of active notification events eventlognumberofentries total number of entries in emseventlogtable eventloglastindex the last index of the emseventlogtable Hint: The eventlognumberofentries and the eventloglastindex can be used by the SNMP manager to detect changes in the eventlogtable. The emseventlogtable The emseventlogtable containins information about all active events on the EMS server. Each table entry has the following objects: eventelementtype eventelementipaddress eventelementname eventelementlocation eventgroupid eventstarttime eventseverity eventmessage Hint: The contents of each field is taken directly from the EMS server s database and the information exists only if there is information in the corresponding database field (e.g. elementname and elementlocation fields). Filtering the emseventlogtable It is possible to suppress any of the three severity classes from the emseventlogtable using the filter objects in object group emseventlogfilters. Three filter objects exist: alarmfilter warningfilter notificationfilter By setting the corresponding filter object to enumerated value on (2), all entries with that severity are suppressed from the emseventlogtable. Note: Suppressing events from the emseventlogtable does not affect the summary variables in emseventloginfo object group. Traps For each new event detected by the EMS server the SNMP Wizard sends an SNMPv1 trap. Separate traps are used for each severity level:
Broadband Cable Networks / Matti Susi June 2, 2004 4(7) eventalarm (1) eventwarning (2) eventnotification (3) Use of separate trap numbers make filtering on the SNMP manager easier since there is no need to look at the traps variable bindings. A separate eventcleared (4) trap is sent every time the server detects a cleared event. All fields from the eventlogentry are included as variable bindings in the event trap. Hint: The trap variable eventgroupid associates traps to a particular event and can be used by the SNMP manager for clearing events automatically. The serverdown (9) trap indicates that the agent can no longer communicate with the EMS server process. Trap filtering The user may disable sending of any the event traps with the trap filter objects in object group emstrapcontrol: alarmtraps warningtraps notificationtraps clearedtraps The corresponding trap is suppressed by setting the filter variable to enumerated value disabled (2). The additional object TrapDelay defines the time (in seconds) an event has to be active before the trap is sent. It can be used e.g. to suppress traps from possible short duration events. SNMP Wizard Configuration Settings The SNMP Wizard comes with an agent configuration utility that installs into the Windows Control Panel. With the configuration utility the system administrator can set the SNMP parameters like trap destination addresses, community strings etc. Additional settings for the SNMP Wizard are done over registry variables. EMS server compatibility SNMP Wizard release 2.1 is compatible with EMS server releases 2.8 and upwards. The Wizard must be installed in the EMS server computer. Hardware requirements Please refer to EMS Server hardware requirements.
Broadband Cable Networks / Matti Susi June 2, 2004 5(7) APPENDIX 1, STRUCTURE OF TELESTE-EMS-MIB
Broadband Cable Networks / Matti Susi June 2, 2004 6(7) APPENDIX 2, CHANGES FROM SNMP WIZARD RELEASE 2.0 This sections describes the new features for the SNMP Wizard release 2.1. To support the new features the EmsWiz.mib version 2.1 or newer must be used. Trap enterprise The trap enterprise has been changed from teleste to emsserver. Specific traps for each severity level Three separate traps are now used for event reporting instead of the single newevent trap. Traps on cleared events An eventcleared trap is added. By using the GroupId variable, the SNMP manager can use this trap to clear out alarms. Number of serverdown trap changed and varbind list added The serverdown trap number is changed to 9 and two varbinds have been added (servername, servertimesincelastresponse). Trap filter objects added The user may disable sending of any event trap by trap filter objects in object group emstrapcontrol Changes in the eventlogtable New object eventelementipaddress is added. Syntax of the object eventstarttime has been changed from DisplayString to DateandTime. The syntax is imported from Teleste-root-MIB. Syntax of object eventseverity has been changed form from DisplayString to enumerated integer. Table entry eventmessageid has been removed because it has very little or no information for the manager application. Some existing table entries have been renamed for clarity. Event log filtering The user may now suppress any of the three severity classes in the emseventlogtable using filter objects in object group emseventlogfilters.
Broadband Cable Networks / Matti Susi June 2, 2004 7(7) BUG FIXES Event trap varbind OIDs The event trap varbinds now contain a full OIDs with the table index to associate the trap to the specific eventlogtable entry. Additional characters at the end of the eventmessage varbind removed Two unnecessary characters appended to each eventmessage variable (0xd and 0xa) have been removed.