ATM-SWITCHING-NODE-MIB: View SNMP OID List / Download MIB

The local date and time in the ATM agent.

The date and time of the last major change detected: - date and time reset - agent IP address(es), subnet mask(s), default gateway changed - LAN Emulation or IP ARP server address(es) changed - system parameters (name, contact, location) changed - module Changed -- module added/removed -- administrative State changed (isolate/attached) - interface changed: -- administrative State changed (enabled/disabled) -- operational state changed This variable is updated in relation with the following traps: - hello trap - change trap - linkUp/linkDown traps.

The purpose of this variable is to protect the path between the hub and the network management station. When set to secure (1), it is not possible to: - disable a port: -- if the SNMP request was received on this port -- if a LAN Emulation or an IP ARP server is on this port - isolate a module: -- if the SNMP request was received on this port -- if a LAN Emulation or an IP ARP server is on this port When set to unlock (2), the parameters referenced above can be modified for a limited time (30 seconds). When set to disabled (3), no protection is provided. Trying to modify one of these parameters results in a genErr error code in the Get-Response and a trap is returned to the agent.

The ATM address of the ARP server used when communicating with the switch agent using Classical IP over ATM (RFC 1577).

The state of the ATM subsystem. Setting this variable to reset, causes a reset of all the ATM modules. When the active switch is in slots 9/10, switch-a is returned. When the active switch is in slots 11/12, switch-b is returned.

When disabled, the hello trap is neither sent. When enabled, the hello trap can be sent by the agent when the appropriate trap condition is detected.

This table controls slot attachement to the ATM switch. An ATM module is operational only when inserted in a slot which is defined as attached to the switch.

Entries of switchTable. Each entry corresponds to a slot that is physically wired to the switch. These slots may be attached to or isolated from the ATM switch.

A slot number controlled by the switch.

The desired state of the slot connection to the switch. When a slot is isolated from the switch, the switch traffic from this slot to the switch is disabled. As a result, if an ATM module is plugged in this slot, it will not be operational. When a slot is attached to the switch, the switch is ready to receive ATM traffic from this slot. As a result, if an ATM module is plugged in this slot, it can be used for ATM traffic.

The actual state of the slot connection to the switch. When the administrative state is set to ISOLATE, the operational state becomes ISOLATED. When the operational state is set to ATTACH, the operational state may become either ATTACHED or ISOLATED depending on the hardware current status of the slot.

This table provides the list of ATM modules in the hub.

Entries of moduleTable.

The slot number for this module.

The type of module attached to the ATM switch in this slot. The unknown value is used when the ATM agent is unable to get information for this module (the module is isolated from the switch or is not operational).

A textual description of this module. This description is blank when no description is available.

The serial number for this module.

The version and release number for this module firmware (microcode).

The Part Number (P/N) and Engineering Change (EC) level for this module and Plant Location.

The administrative state of this module.

The operational test of this module.

The number of errors detected by this module on the traffic from the switch to this module.

The maximum number of VPC supported by this module. The current number of VPC that can be used is the difference between moduleMaxVpc and moduleUsedVpc.

The number of VPCs currently in use for this module. The current number of VPCs that can be used is the difference between moduleMaxVpc and moduleUsedVpc.

The maximum number of VCCs supported by this module. The current number of VCCs that can be used is the difference between moduleMaxVcc and moduleUsedVcc.

The number of VCC currently in use for this module. The current number of VCC that can be used is the difference between moduleMaxVcc and moduleUsedVcc.

This table provides the list of ports attached to the ATM switch (ATM ports). These ports belong to ATM modules inserted in slots that are attached to the ATM switch.

Entries of portTable. Each entry corresponds to a port that belongs to an ATM module. This module must be inserted in a slot that is attached to the ATM switch.

The slot number of this ports module.

The port number for this module.

The interface number of this port.

For each ATM port, this table maps the MIB-II interface index for this port with its physical slot and port numbers.

Entries of the interfaceTable. Each entry corresponds to a port that belongs to an ATM module. This module must be inserted in a slot that is attached to the ATM switch.

The interface number of the port represented by this entry. This is the same number as the index used to represent this interface in the MIB-II interface table.

The slot number of this ATM ports module.

The port number of this ATM port.

Whether this port is an internal port (on the backplane) or an external connector.

The administrative state for this port. When set to disabled, no ATM traffic can pass on this port; all connections (SVC and PVC) are cleared. When set to wrap-reply, this interface is wrapped so that all the traffic received from the attached line is sent back on this line. If the interface state is not changed, it will automatically go back to the disabled state after one minute.

The operational state for this port: - unknown: the status of this port is unknown (this can be the result of a module in error) - disabled-nosignal: no activity is detected at the physical layer while the port is enabled - disabled-idle:: activity from the remote device attached to this port has been detected by the physical layer. The port is disabled. - failing: an internal hard error has been detected on this port while the port is enabled - no signal: no activity is detected at the physical layer while the port is enabled - idle: activity from the remote device attached to this port has been detected by the physical layer. The port is enabled. - in-service: the remote device successfully acknowledges ILMI polling requests and SVC registration - pvcOnly: the remote device succesfully acknowledges ILMI polling requests but it rejects the ATM prefix registration. Only PVCs are supported. - misConfigured: an SSI to UNI or an SSI to NNI configuration has been detected - wrongNetworkPrefix: the switches on each end of an SSI link have incompatible network prefixes (the 12 first bytes have different values) - wrongNodeNumber: the switches on each end of an SSI link have the same ATM node Numbers. - failing-line: the port is enabled and a invalid signal is detected on the line - disabled-failing: the port is disabled and an anomaly is detected, either internal or external. - wrap-no-signal: the port is internally wrapped so that all the traffic received on the attached line is returned unchanged on the line. No activity is detected at the physical layer. - wrap-idle: the port is internally wrapped so that all the traffic received on the attached line is returned unchanged on the line and a valid signal is detected on the line. - wrap-failing-internal: an internal failure has been detected when the port has been turned into the wrap-reply state. The actual state of the port is undefined. - wrap-failing-line: the port is internally wrapped so that all the traffic received on the attached line is returned unchanged on the line and an invalid signal is detected on the line. When disabled, the port may be in only one of the following states: - unknown, disabled-failing, disabled-nosignal or disabled-idle.

The type of ATM access offered on this port: - UNI: User Network Interface - SSI: Switch-to-Switch interface - NNI: Network-to-Network interface

The type of cable attached to this port.

The speed of this interface, in bits per second.

The number of physical layer errors detected on this media such as violation errors and length errors.

When set to 0, this interface (and its physical connector) is directly located on the module identified by the slot number. When set to a non-zero value, this number identifies a feature card of the module that is used by this interface.

The source of the bit clock used for data transmission. When set to external, the source is the clock received from the line.

Whether data scrambling is used when transmitting on this line. Scrambling may be applied at the cell level, at the frame level or at cell and frame level.

For a UNI or a NNI port: the current bandwidth available for the reserved bandwidth connections on this port. For a SSI port: the current bandwidth available on this port. It is in bits per second.

For a UNI or a NNI port: the bandwidth, in bits per second, currently used by the reserved bandwidth connections on this port. For a SSI port: the bandwidth, in bits per second, currently reserved on this port.

When on, the switch throughput is monitored. When off, the switch thoughput is not monitored. Note that the monitoring decreases the system overall performances.

The total number of cells transmitted from the switch. Note that this value is the aggregate throughput of all the ports on several minutes.

The ifindexes of the five most receiving interfaces. The first ifindex given is the one corresponding to the interface which has received the more cells during the last polling interval. All ifIndexes are separated by a blank character. If there are less than 5 interfaces receiving data, there are less than 5 ifindexes listed.

The ifindexes of the five most transmitting interfaces. The first ifindex given is the one corresponding to the interface which has sent the more cells during the last polling interval. All ifIndexes are separated by a blank character. If there are less than 5 interfaces transmitting data, there are less than 5 ifindexes listed.

This table contains the cross-connections set-up in the switch for all existing VCL-based PVCs and SVCs.

Entries of vcXConnectTable.

The interface number for this ATM port.

The VPI value for this connection.

The VCI value for this connection.

The interface number for this ATM port.

The VPI value for this connection.

The VCI value for this connection.

Whether this cross-connection is part of a unicast or a multicast connection.

Whether this entry identifies this cross-connection in the upstream or downstream flow, as seen from the root. Downstream means that the connection was set up from the in parameters (interface, VPI, VCI) to the out parameters (interface, VPI, VCI). In particular, for a multicast SVC, this means that the call initiator (the root in this case) is on the interface side labeled vcXInIndex. Upstream means that the connection was set up from the out parameters (interface, VPI, VCI) to the in parameters (interface, VPI, VCI). As a result, any cross-connection is modeled in this table as two entries, depending on whether it is seen in the up or down stream.

This table contains the cross-connections set-up in the switch for all existing VPL-based PVCs and SVCs.

Entries of vpXConnectTable.

The interface number for this ATM port.

The VPI value for this connection.

The interface number for this ATM port.

The VPI value for this connection.

Whether this cross-connection is part of a unicast or a multicast connection.

Whether this entry identifies this cross-connection in the upstream or downstream flow, as seen from the root. Downstream means that the connection was set up from the in parameters (interface, VPI) to the out parameters (interface, VPI). Upstream means that the connection was set up from the out parameters (interface, VPI) to the in parameters (interface, VPI). As a result, any cross-connection is modeled in this table as two entries, depending on whether it is seen in the up or down stream.

This table contains basic characteristics on adjacent ATM devices attached to this switch.

Entries of neighborTable. Each entry corresponds to a port that belongs to an ATM module. This module must be inserted in a slot that is attached to the ATM switch.

The interface number for the port represented by this entry.

One of the IP addresses of the ATM SNMP agent of the node attached to the port/slot defined by this entry. When not available, 0.0.0.0 is returned.

One of the IP addresses of the ATM SNMP agent of the node attached to the port/slot defined by this entry. When not available, 0.0.0.0 is returned.

The ATM identification of the node attached to the port/slot defined by this entry. When not available, a null string is returned.

The interface number of the adjacent node to which the connection defined by this entry is attending. When not available, 0 is returned.

The value of the MIB-II sysDescr as reported by the device attached to this port. When not available, a null string is returned.

The value of the MIB-II sysOID as reported by the device attached to this port. When not available, a null string is returned.

The value of the MIB-II sysName as reported by the device attached to this port. When not available, a null string is returned.

The value of the MIB-II sysLocation as reported by the device attached to this port. When not available, a null string is returned.

The internal identifier for this trunk. Set to 0 if not a trunk.

A file transfer is initiated through a start command.

The date and time of the last transfer.

The IP address of the server used for file transfer.

The name of the file to transfer.

The type of file to transfer. Boot and operational codes can only be dowlnoaded. Logs, traces and dumps can only be uploaded.

The module target to which the transfer applies. When set to 0, the transfer applies to the agent itself.

The result of the latest file transfer. When one of the TFTP variables is modified, this variable is reset to not-initialized.

When on, the hub general trace facility is started. Messages are stored in the hub in a file that can be retrieved through TFTP. When off, the general trace facility is stopped and messages are no longer logged.

When on, the Topology and Routing Selection trace is started. Messages are stored in the hub in a file that can be retrieved through TFTP. When off, the control point trace facility is stopped and messages are no longer logged.

When start is selected, a dump of the Topology and Route Services component is taken. The dump is stored in the hub in a file that can be retrieved through TFTP.

When swap is selected, the backup microcode image is checked and, if valid, activated. The previously active microcode image becomes the backup image. The atm subsystem is reset.

The result of the latest microcode swap. When an operational code image is downloaded or when the system is reset, swapControl becomes not-initialized.

This table contains basic information on the Q2931 protocol for each signalling link defined per port. Usually, there is only one signalling channel per interface and thus one Q2931 protocol definition entry per interface.

Entries of atmQ2931ConfTable. Each entry corresponds to a pair of ATM interface, signalling channel. A signalling channel is uniquely defined on each interface by the VPI and VCI values allocated to it.

The ifIndex value of the ATM interface which, with the signalling channel defined by its Vpi/Vci values, uniquely identifies this entry.

The Vpi value which, with the Vci value specified in atmQ2931SiVci, defines the signalling channel for this entry. Usually, there is one signalling channel per interface defined by Vpi=0,Vci=5.

The Vci value which, with the Vpi value specified in atmQ2931SiVpi, defines the signalling channel for this entry. Usually, there is one signalling channel per interface defined by Vpi=0,Vci=5.

T303 timer as defined in the ATM UNI Specification.

T308 timer as defined in the ATM UNI Specification.

T309 timer as defined in the ATM UNI Specification.

T310 timer as defined in the ATM UNI Specification.

T316 timer as defined in the ATM UNI Specification.

T317 timer as defined in the ATM UNI Specification.

T322 timer as defined in the ATM UNI Specification.

T398 timer as defined in the ATM UNI Specification.

T399 timer as defined in the ATM UNI Specification.

Number of set-up retries as defined in the ATM UNI Specification.

Number of release retries as defined in the ATM UNI Specification.

Number of restart retries as defined in the ATM UNI Specification.

Number of status retries as defined in the ATM UNI Specification.

This table contains statistics for the Q2931 protocol.

Entries of atmQ2931ConfTable. Each entry corresponds to a pair of ATM interface, signalling channel. A signalling channel is uniquely defined on each interface by the VPI and VCI values allocated to it.

The ifIndex value of the ATM interface which, with the signalling channel defined by its Vpi/Vci values, uniquely identifies this entry.

The Vpi value which, with the Vci value specified in atmQ2931StatsVci, defines the signalling channel for this entry. Usually, there is one signalling channel per interface defined by Vpi=0,Vci=5.

The Vci value which, with the Vpi value specified in atmQ2931StatsVpi, defines the signalling channel for this entry. Usually, there is one signalling channel per interface defined by Vpi=0,Vci=5.

This is the number of outgoing call attempts on this interface, including accepted as well as rejected calls.

This is the current number of outgoing calls in progress on this interface.

This is the number of outgoing calls that were cleared for a reason other than a DTE or operator initiated action.

This is the number of incoming call attempts on this interface, including accepted as well as rejected calls.

This is the current number of incoming calls in progress on this interface.

This is the number of calls that were rejected by the receiver.

This table contains basic information for each active Switched Virtual Connection (SVC).

Entries of atmSvcTable. Each entry uniquely defines two end-points of an SVC. In the case of a multicast SVC, each entry is defined by the association of the root and one party.

The ifIndex value of the ATM interface used by this SVC.

The Vpi value which, with the Vci value specified in atmQ2931SiVci, defines the signalling channel for this entry. Usually, there is one signalling channel per interface defined by Vpi=0,Vci=5.

The Vci value which, with the Vpi value specified in atmQ2931SiVpi, defines the signalling channel for this entry. Usually, there is one signalling channel per interface defined by Vpi=0,Vci=5.

The Q2931 call reference value used for this SVC.

One of the Q2931 end point reference values used by this SVC. In a unicast SVC, there is only one entry for this SVC in the table. In a multicast SVC, there is one entry per party.

The calling number carried in the calling party number information element of the call set-up message.

The called number carried in the called party number information element of the call set-up message.

This variable allows a network manager to clear this SVC. When this SVC is cleared (either by the manager using this variable or by one of the parties), the entry is deleted from this table and another entry is created in the atmSvcClearTable.

The date and time this call was placed.

The VPI value used by this SVC for this interface.

The VCI value used by this SVC for this interface.

The maximum number of entries supported by this local SNMP agent. When this value is exceeded, the entries are wrapped.

The maximum number of entries that can be written in the atmSvcLogTable before a trap is generated. When this number is reached, an svcLogOverflow trap is generated. When set to 0, no trap is generated.

This table contains a list of the latest Switched Virtual Connection (SVC) that were completed on this ATM node. An SVC is completed when it has been torn down at the originators request (normal completion) or by the network operator (forced tear down), or when it has been rejected or cleared by the network (exceptional condition).

Entries of atmSvcLogTable.

An identification value for this entry, assigned by the local SNMP agent. This value is assigned for each new SVC call or add-party request. This index is allocated in a decreasing order, so that a get-next request on the table allows to retrieve the latest calls first.

The ifIndex value of the ATM interface used by this SVC.

The calling number carried in the calling party number information element of the call set-up message.

The called number carried in the called party number information element of the call set-up message.

The date and time this call was placed.

The date and time this call was cleared.

The cause of the clearing of this SVC.

The forward Quality Of Service requested for this call.

The backward Quality Of Service requested for this call.

The forward bandwidth requested for this call.

The backward bandwidth requested for this call.

This table contains basic information on the SAAL protocol for each signalling link defined per port. Usually, there is only one signalling channel per interface and thus one SAAL protocol definition entry per interface.

Entries of atmSaalConfTable. Each entry corresponds to a pair of ATM interface, signalling channel. A signalling channel is uniquely defined on each interface by the VPI and VCI values allocated to it.

The ifIndex value of the ATM interface which, with the signalling channel defined by its Vpi/Vci values, uniquely identifies this entry.

The Vpi value which, with the Vci value specified in atmSaalConfSiVci, defines the signalling channel for this entry. Usually, there is one signalling channel per interface defined by Vpi=0,Vci=5.

The Vci value which, with the Vpi value specified in atmSaalConfSiVpi, defines the signalling channel for this entry. Usually, there is one signalling channel per interface defined by Vpi=0,Vci=5.

The state of the SAAL for this interface as defined in the Q.2110 Specification, Chapter 7.3.

Timer_POLL as defined in the Q.2110 Specification. This timer is running in the active phase to assure that the peer receiver is polled often enough to return its status.

Timer_KEEP-ALIVE as defined in the Q.2110 Specification. This timer is started when entering the transient phase.

Timer_NO-RESPONSE as defined in the Q.2110 Specification. This timer indicates the maximum time interval during which at least one STAT PDU needs to be received.

Timer_CC as defined in the Q.2110 Specification. Transmission of PDUs is protected by this timer during establishment and release of a connection and during resynchronization or recovery.

Timer_IDLE as defined in the Q.2110 Specification. This timer is started upon receipt of a STAT PDU when entering the idle phase (no POLL PDUs sent).

MaxCC as defined in the Q.2110 Specification. This is the maximum value for the state variable VT(CC), corresponding to the maximum number of transmissions of a BGN, END, ER or RS PDU.

MaxPD as defined in the Q.2110 Specification. This is the maximum iacceptable value for the state variable VT(PD) before sending a POLL PDU and resetting VT(PD) to zero. This parameter is an upper limit for counter VT(PD) that sends a POLL PDU after every (MaxPD) SD PDUs.

MaxSTAT as defined in the Q.2110 Specification. This is the maximum number of list elements placed in a STAT PDU.

This table contains statistics for the SAAL protocol, for outgoing calls only.

Entries of atmSaalConfTable. Each entry corresponds to a pair of ATM interface, signalling channel. A signalling channel is uniquely defined on each interface by the VPI and VCI values allocated to it.

The ifIndex value of the ATM interface which, with the signalling channel defined by its Vpi/Vci values, uniquely identifies this entry.

The Vpi value which, with the Vci value specified in atmSaalStatsSiVci, defines the signalling channel for this entry. Usually, there is one signalling channel per interface defined by Vpi=0,Vci=5.

The Vci value which, with the Vpi value specified in atmSaalStatsSiVpi, defines the signalling channel for this entry. Usually, there is one signalling channel per interface defined by Vpi=0,Vci=5.

Error conditions A to M, as defined in the Q.2110 Specification. This is the number of received unsolicited or or inappropriate PDUs.

Error condition O as defined in the Q.2110 Specification. This is the number of failing retries.

Error condition P as defined in the Q.2110 Specification. This is the number of failing polls.

The number of times sequence gaps were detected by the peer entity.

The number of times frames were re-transmitted due to sequence gaps detected by the peer entity.

Error conditions Q to V as defined in the Q.2110 Specification.

Error condition W as defined in the Q.2110 Specification. This is the number of times that transmission was not permitted by the peer entity due to a lack of credit.

Error condition X as defined in the Q.2110 Specification. This is the number of times that credit was obtained from the peer entity to allow transmission.

The status of the PVC handler in the switch. When no more memory is available, the creation of new PVCs is rejected with a generic Error sense code.

This table lists all PVCs defined per interface. There is only one entry in this table per PVC (point-to-point or point-to-multipoint PVC).

Entries of atmPvcTable. Policing parameters are those requested when creating the PVC. The actual values used by the network to satisfy these requirements may slightly differ. These values are attached to virtual links and are available in virtual link tables, such as the RFC-1695 VPL/VCL tables.

The ifIndex value of the ATM interface used by this PVC.

A value used to uniquely identify this PVC on this interface. To create a new PVC on a given interface, an unused PVC identifier must be found.

States values: active: the PVC is operational notInService: the PVC is failing notReady: values are missing to be able to activate this PVC Actions: active: this requests to re-start a failing PVC (which status was notInService) destroy: this requests to delete a PVC createAndWait: this requests to create a PVC To create a new PVC, this variable must be set to createAndWait with an index where: - atmPvcIndex is the number of the interface from where the PVC is created - atmPvcIdentifier is an unused PVC identifier for this interface To activate a PVC, this variable must be set to active. Default values are provided for all attributes except for the atmPvcEpRemIndex. If this attribute is not set, the PVC will remain in the notReady state. To delete a point-to-point PVC, this variable must be set to destroy.

A unicast PVC is defined between two endpoints, using either a VP or a VC connection.

The end-point where the PVC is created is identified as the primary or root end-point. the other end-point is the identified as the secondary or leaf end-point.

The VPI value assigned to this PVC at the origin. A value of 65536 means that no value has been specified by the operator. If no value has been specified, the VPI value is then automatically allocated by the agent when activating the PVC.

The VCI value assigned to this PVC at the origin. For VP-type PVC, this value is not applicable and is set to 0. A value of 65536 means that no value has been specified by the operator. If no value has been specified, the VCI value is then automatically allocated by the agent when activating the PVC.

The QOS requested for this PVC to the originator.

The QOS requested for this PVC from the originator.

The first parameter used to define the policy requested for this PVC.

The type of policy requested for this PVC.

The fourth parameter used to define the policy requested for this PVC.

The third parameter used to define the policy requested for this PVC.

This table lists the characteristics of the remote end-points of defined PVCs. There is one entry for each PVC defined in the atmPvcTable.

Entries of atmPvcEpTable. One entry is automatically created by the agent when a PVC is created in the PVC Table. No additional entry can be created in this table if the PVC is defined as point-to-point in the PVC table.

The ifIndex value of the ATM interface used by this PVC.

A value used to uniquely identify this PVC on this interface. This is the same identifier as the one used in the atmPvcTable to identify the PVC that this end-point belongs to.

A value used to uniquely identify a remote end-point of a PVC, when associated with an interface index and a PVC identifier. For a point-to-point PVC, this value is always set to 0.

States values: active: the PVC is operational notInService: the PVC is failing notReady: values are missing to be able to activate this PVC Actions: active: this requests to re-start a failing unicast PVC (status was notInService) destroy: this requests to delete a unicast PVC.

A detailed cause for the current PVC status.

The ATM address of the remote ATM switch where the PVC ends. If none is specified, the ATM address of the target switch (local) is used and the PVC is confined to the target switch (local switch).

The ifindex value used at the remote end to identify the interface where the PVC ends. This entry will remain in the notReady state until this attribute is set (and the atmPvcRowStatus is set to active).

The VPI value assigned to this PVC at the destination (remote end). If left at 65536 (default value), one value is automatically allocated by the agent.

The VCI value assigned to this PVC at the destination. For VP-type PVC, this value is not applicable and is set to 0. If left at 65536 (default value), one value is automatically allocated by the agent (for VC only).

The date and time of the latest PVC activation.

The cause of the failure as defined by Q2931.

The number of times this PVC failed.