Mib File - NEC UNIVERGE SV9100 Features And Specifications

Hide thumbs Also See for UNIVERGE SV9100:

Table of Contents

Alarms on Netlink systems will be reported via the Primary System when in normal

operation. Alarms are identified by the NetLink node ID in the SNMP alarm string.

In a NetLink configuration only the Primary System will send SNMP messages. SNMP Traps

are not sent by secondary nodes when in stand-alone operation.

Release 8.0 Enhancement features require Version R8 or greater feature license (0418).

The SNMP Version that is supported is SNMPv1.

An SNMP packet may be lost when the network is busy. Lost packets will not be resent

because SNMP uses connection-less UDP transport.

Configuration change notifications are not sent if a user operation does not occur. This

includes SIP Registrations and Database Replications. These events are covered by

existing SNMP alarms.

MIB File

The MIB file is structured according to the following tables, only data listed here is available via

SNMP. The data for each of the items can be read or write. Read is data that can be requested

from the system. Write requires that a value be entered in the SNMP application. For example,

the slot number would need to be entered when querying a card.

Common MIB OID information is as follows, these OIDs will be seen at the beginning of the NEC

portion of each OID used by the SV9100.

14399 Marks the beginning of the NEC portion of the OID.

20 Represents KTS which means Key Telephone System.

The MIB OID parameters using the common parameters above are defined in more detail in the

following tables.

10. Position can be used to obtain information about a card in a specific slot in the system.

10. Position

30. CPU contains several items relating to the CPU. The following tables show a break down of

the data available.

1. System ID

NetLink System ID

2. System Card Position

Card Slot Number

1. Hardware Key Code

1. CPU Version

2. CPU Main Software Build Version

Read or Write

Read or Write