1                    Trap support in SNMP from V4.0.01

Version 4.0.01 extends the SNMP management interface, described in the Integration and Customization Manual, to include sending SNMP alarm notifications. This means that you can integrate information about alarms from MetaSwitch NEs into your existing management applications or develop new applications to manage them.

In particular, Micromuse are developing an add-on to the NetCool network management program, so that the alarms reported in the EMS can be notified to NetCool and displayed in the NetCool interface. Contact your usual NetCool support personnel at Micromuse for more details of the availability of this software.

For details of the format of SNMP notifications, see the alarmTrap table at the end of the MetaSwitch MIB definition file. This is provided on the EMS installation CD, in the file /sdk/snmp/metaswitch.mib, or in the file with the same name in the SDK ZIP file provided to you by your MetaSwitch support representative.

The Element Management System object in the EMS is changed slightly to include new fields for managing SNMP alarm notifications. For full details of the changes, see MetaSwitch Class 5 Softswitch V4.0.1 Enhancements.

The pre-V4.0.01 trap support is made superfluous by these changes and the corresponding notification tables have been removed. The information in the Integration and Customization Manual about configuring the SNMP Master Agent now refers only to support for SNMP GET, GET-NEXT and SET commands. SNMP Trap support is now managed using the new fields in the Element Management System object in the EMS. For more details, see MetaSwitch Class 5 Softswitch V4.0.1 Enhancements.

 

2                    Changes to the interface to pre-V4.0.01 NEs

This section describes the changes that have been made to the EMS SNMP interface for managing Pre-V4.0.01 Network Elements (NEs) between the 4.0 and 4.0.01 EMS releases.  These will affect any client SNMP application that currently uses the SNMP interface to manage pre-V4.0.01 NEs through a pre-V4.0.01 EMS, and needs to continue managing the same NEs through a 4.0.01 EMS.

2.1             Tables changed on pre-V4.0.01 NEs

emsTableData

·         New field emsR1SNMPAlrmNotifsCfgd

·         New field emsR1SNMPAlrmNotifsDestAddr

·         New field emsR1SNMPAlrmNotifsDestPort

·         New field emsR1SNMPAlrmNotifsSourcePort

·         New field emsR1SNMPAlrmNotifsCommunity

·         New field emsR1SNMPAlrmNotifsNextCfgd

·         New field emsR1SNMPAlrmNotifsNextDestAddr

·         New field emsR1SNMPAlrmNotifsNextDestPort

·         New field emsR1SNMPAlrmNotifsNextSourcePort

·         New field emsR1SNMPAlrmNotifsNextCommunity

 

mGLAPDResourceTableData

·         Field mGLAPDResourceAlrmState removed

·         Field mGLAPDResourceAlrmStateTimestamp removed

·         Field mGLAPDResourceAlrmLogCorr removed

·         Field mGLAPDResourceAlrmEvtsAttnRq removed

·         Field mGLAPDResourceAlrmResetTimestamp removed

·         Field mGLAPDResourceR1AlrmState removed

·         Field mGLAPDResourceR1AlrmStateTimestamp removed

·         Field mGLAPDResourceR1AlrmLogCorr removed

·         Field mGLAPDResourceR1AlrmEvtsAttnRq removed

·         Field mGLAPDResourceR1AlrmResetTimestamp removed

 

Sys2510EthSwitchTableData

·         New field sys2510EthSwitchSerialNum

 

 

2.2             Tables replaced on pre-V4.0 NEs

There are no tables replaced on pre-V4.0 NEs.

 

 

3                    Differences between the interfaces to V4.0 NEs and V4.0.01 NEs

This section describes the differences in the 4.0.01 EMS SNMP interface between the tables for managing V4.0 Network Elements and the tables for managing V4.0.01 Network Elements.  These will affect any client SNMP application that currently uses the SNMP interface to manage V4.0 NEs through a V4.0.01 EMS, and needs to continue managing the NEs when they are upgraded to V4.0.01.

·         Section 2.1 lists the differences that mean changes are required to client applications that use these tables as soon as the NE is upgraded to V4.0.01.

·         Section 2.2 lists the differences that mean changes will be necessary for any client application that wishes to use the new V4.0.01 features.  These differences will not affect a client that wishes to continue with the same functionality as it had when managing V4.0 NEs.

·         Section 2.3 lists the new tables that have been added to access new V4.0.01 features. 

3.1             Tables retired between V4.0 and V4.0.01

There are no tables retired between V4.0 and V4.0.01. 

 

3.2             Tables deprecated between V4.0 and V4.0.01

The following table is deprecated between V4.0 and V4.0.01 because new features are supported on a V4.0.01 NE.  Any client that uses this table can continue to use it to manage a V4.0.01 NE, but will have to be changed to use the new revision of the table to manage the new features on the V4.0.01 NE.

Sys2510EthSwitchTableData:

·         No fields changed. 

 

 

3.3             Tables added in V4.0.01

No new tables added in V4.0.01.