NNCEXTSPVC-MIB :: nncExtSpvc

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NNCEXTSPVC-MIB › nncExtSpvc

nncExtSpvc

Module: NNCEXTSPVC-MIB

OID (symbolic): NNCEXTSPVC-MIB::nncExtSpvc

OID (numeric): 1.3.6.1.4.1.123.3.82

Node type: MODULE-IDENTITY

Description: This module contains Alcatel CID's proprietary MIB definition for managing Soft Permanent Virtual Connections (SPVCs). This MIB supports the creation, modification, query, and deletion of SPVCs (Soft Permanent Virtual Connections), on Cell Relay (ATM), Frame Relay, and Circuit Emulation endpoints. For Cell Relay-based endpoints, Permanent Virtual Path Connection (PVPC) and Permanent Virtual Channel Connection (PVCC) are supported, while SPVCCs are supported on Frame Relay and Circuit Emulation endpoints.

Cell Relay SPVCs, Frame Relay SPVCs and Circuit Emulation SPVCs are supported in this MIB. SPVCs with any other service types are not supported at this point.

For SPVCs interworking across different endpoint types, CR to FR, FR to CR, CR to CE, CE to CR connections are supported. CE to FR or FR to CE are not suppported.

Operator directed routing for SPVC connections is not supported at this point.

To create an SPVC, the required MIB objects from the destination table must be configured and sent to the destination endpoint. Next, the MIB objects from the source endpoint table (based on the endpoint type and SPVC type - either nncCrSpvpcTable, nncCrSpvccTable, nncFrSpvcTable, or nncCeSpvcTable) are configured and sent to the source endpoint. Assuming a PDU with a RowStatus of 'createAndGo' or 'Active' has been received, if the adminStatus of the SPVC is set to 'enabled', the SPVC will be connected; if the adminStatus of the SPVC is set to 'disabled', the SPVC will be configured but not connected.

SPVC creation SET-REQuests can be sent two ways: using a RowStatus value of 'createAndGo', or using multiple SET-REQs using RowStatus values of 'createAndWait' and 'active'.

Creating an SPVC using rowStatus=createAndWait(5)

In the case of multiple SET-REQs, the RowStatus is set to createAndWait(5) for all but the last SET-REQ, and set to active(1) for the last SET-REQ. The SPVC is configured only after the last PDU (with RowStatus as 'active') is received.

Creating an SPVC using rowStatus=createAndGo(4)

In the other case, all required MIB objects can fit in one SET-REQ. If using only one SET-REQ, the RowStatus should be set to createAndGo(4).

In both cases, default values for MIB objects will be used wherever possible.

To delete an SPVC, the correct table objects must be sent to both the destination endpoint and the source endpoint for the given SPVC, using the correct index, and setting the rowStatus to 'destroy'. This will delete the specified SPVC.

Some abreviations:

abr/ABR/Abr: Available Bit Rate Bwd: Backward. For traffice descriptors from destination endpoint to source endpoint (receiving traffic) cbr/CBR/Cbr: Constant Bit Rate Dst: Destination endpoint Fwd: Forward. For traffic descriptors from source endpoint to destination endpoint (transmitting traffic) nt-vbr/nrtvbr/NRT-VBR: Non-Real-Time Variable Bit Rate Src: Source endpoint Targ: Target. For the destination endpoint info in source endpoint table ubr/UBR/Ubr: Unspecified Bit Rate

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.123newbridgeNNCGNI0001-SMI
1.3.6.1.4.1.123.3nncExtensionsNNCGNI0001-SMI
Numeric OIDNameModule
1.3.6.1.4.1.123.3.82nncExtSpvcNNCEXTSPVC-MIB