Nortel-Magellan-Passport-DisdnJapanInsMIB: View SNMP OID List / Download MIB

This entry controls the addition and deletion of dataSigChanIns components.

A single entry in the table represents a single dataSigChanIns component.

This variable is used as the basis for SNMP naming of dataSigChanIns components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the dataSigChanIns tables.

This variable represents the index for the dataSigChanIns tables.

This entry controls the addition and deletion of dataSigChanInsFramer components.

A single entry in the table represents a single dataSigChanInsFramer component.

This variable is used as the basis for SNMP naming of dataSigChanInsFramer components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the dataSigChanInsFramer tables.

This variable represents the index for the dataSigChanInsFramer tables.

This group contains the base provisioning data for the Framer component. Application or hardware interface specific provisioning data is contained in other provisionable Framer groups.

An entry in the dataSigChanInsFramerProvTable.

This attribute contains a hardware component name. The attribute associates the application with a specific link. This defines the module processor on which Framer's parent component (as well as Framer itself) will run.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the dataSigChanInsFramerStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains the operational statistics data for a Framer component.

An entry in the dataSigChanInsFramerStatsTable.

This attribute counts the number of frames transmitted to the link interface by Framer. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames received from the link interface by Framer. This count wraps to zero after reaching its maximum value.

The number of bytes received from the link interface by Framer.

This attribute counts the total number of aborts received. This count wraps to zero after reaching its maximum value.

This attribute counts the total number of frames with CRC errors. This count wraps to zero after reaching its maximum value.

This attribute counts the total number of frames with LRC errors. This count wraps to zero after reaching its maximum value.

This attribute counts the total number of frames that were non octet aligned. This count wraps to zero after reaching its maximum value.

This attribute counts the total number of frames received from the link for which overruns occurred. This count wraps to zero after reaching its maximum value.

This attribute counts the total number of frames transmitted to the link for which underruns occurred. This count wraps to zero after reaching its maximum value.

This attribute counts the total number of frames received which were too large. The frame was longer than 500 bytes. This count wraps to zero after reaching its maximum value.

This group represents the provisionable Layer 2 attributes of the Q931 CCITT protocol.

An entry in the dataSigChanInsL2Table.

This attribute specifies the layer2 enable request timer.

This attribute specifies the maximum time between a layer 2 frame and its acknowledgement

This attribute specifies the maximum number of re-transmissions of a layer2 frame.

This attribute specifies the maximum time that a no layer 2 traffic situation can last. Expiry triggers a check on whether the far end is a live.

This attribute specifies the maximum number of octets in an information field.

This attribute specifies the maximum number of frames for B channel use.

This group defines the general options of the d-channel signalling link.

An entry in the dataSigChanInsProvTable.

This attribute specifies whether the layer 2 HDLC interface is the network or user side of the connection. Enumeration: 'network': 1, 'user': 2.

This group provides the operational attributes for the signalling protocol.

An entry in the dataSigChanInsOperTable.

This attribute indicates the number of currently active channels. This includes data and voice channels.

This attribute indicates the maximum number of channels that have been active on this signalling channel during the last polling period.

This attribute indicates the state of the D-channel. outOfService means that there is no layer 2 or layer 3 connectivity to the PBX. establishing means that the signalling channel is attempting to stage the layer 2. established means that the layer 2 is enabled. If the signalling channel stays in the established state, then it is waiting for a restart from the PBX. enabling means that the resources for processing calls are being initialized. If the signalling channel stays in the enabling state then it is waiting for a restart acknowledgement from the PBX. inService means that the resources for processing calls are available. restarting means that the resources for call processing are being rei- initialized. Enumeration: 'outOfService': 0, 'established': 2, 'establishing': 1, 'enabling': 3, 'restarting': 5, 'inService': 4.

This group contains a series of operational attributes which turn on and off several kinds of tracing.

An entry in the dataSigChanInsToolsTable.

This attribute defines which types of tracing are active for this signalling channel. The tracing messages are sent to the debug stream. To see the messages the agentQueue attribute in Col/debug must be greater than 0 and a Telnet NMIS session must list the debug stream in in its data streams (ex. set nmis telnet session/1 dataStreams debug). Different types of tracing can be enabled simultaneously. Note that tracing consumes additional CPU resources and will slow down call processing on a heavily loaded card. If there is message block exhaustion tracing will be suspended for a period and then automatically reenabled. An alarm is generated on tracing suspension and resumption. This mechanism protects the function processor against excessive numbers of tracing messages. Types of tracing include: protocolErrors - get details of any protocol errors which are occuring. Protocol errors are also reported in summary form as alarms. q931Summary - Summary of the Q.931 messages on the signalling link, including certain call details (calling number, called number, release codes). q931Hex - Q.931 messages displayed in hex format. Useful to determine protocol compliance in case of errors reported on local or remote ends. q931Symbolic - Q.931 messages parsed to give maximum detail. Useful for understanding content of messages flowing on the link. portHex - Messages in hex format being sent and received on the link. Description of bits: protocolErrors(0) q931Summary(1) q931Hex(2) q931Symbolic(3) portHex(4)