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
Parsed from file NncExtSPVC.mib.txt
Company: None
Module: NNCEXTSPVC-MIB
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
Parsed from file NNCEXTSPVC-MIB.mib
Module: NNCEXTSPVC-MIB
Vendor: Newbridge Networks Corporation
Module: NNCEXTSPVC-MIB
[Automatically extracted from oidview.com]
nncExtSpvc MODULE-IDENTITY LAST-UPDATED "20010215121735Z" ORGANIZATION "Alcatel CID" CONTACT-INFO "Alcatel CID Postal: 600 March Road Kanata, Ontario Canada K2K 2E6 Phone: +1 613 591 3600 Fax: +1 613 591 3680" 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 " ::= { nncExtensions 82 }
nncExtSpvc MODULE-IDENTITY LAST-UPDATED "20010215121735Z" ORGANIZATION "Alcatel CID" CONTACT-INFO "Alcatel CID Postal: 600 March Road Kanata, Ontario Canada K2K 2E6 Phone: +1 613 591 3600 Fax: +1 613 591 3680" 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 " ::= { nncExtensions 82 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.123.3.82.1 | nncExtSpvcObjects | 8 | 201 | None |
| 1.3.6.1.4.1.123.3.82.3 | nncExtSpvcGroups | 8 | 8 | None |
| 1.3.6.1.4.1.123.3.82.4 | nncExtSpvcCompliances | 1 | 1 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.123.3.1 | nncExtSystem | 6 | 16 | None |
| 1.3.6.1.4.1.123.3.2 | nncExtEnvironmental | 6 | 16 | None |
| 1.3.6.1.4.1.123.3.3 | nncExtRestart | 9 | 22 | None |
| 1.3.6.1.4.1.123.3.4 | nncExtCodeSpace | 4 | 19 | None |
| 1.3.6.1.4.1.123.3.5 | nncExtNVM | 2 | 7 | None |
| 1.3.6.1.4.1.123.3.6 | nncExtAlarm | 6 | 30 | None |
| 1.3.6.1.4.1.123.3.7 | nncExtNetSynch | 3 | 14 | None |
| 1.3.6.1.4.1.123.3.8 | nncExtPosition | 4 | 22 | None |
| 1.3.6.1.4.1.123.3.9 | nncExtDevice | 1 | 15 | None |
| 1.3.6.1.4.1.123.3.10 | nncExtDs1 | 8 | 72 | None |
| 1.3.6.1.4.1.123.3.11 | nncExtRptr | 2 | 18 | None |
| 1.3.6.1.4.1.123.3.12 | nncExtProbe | 1 | 3 | None |
| 1.3.6.1.4.1.123.3.13 | nncExtDiag | 2 | 4 | None |
| 1.3.6.1.4.1.123.3.14 | nncExtSyncDataCct | 2 | 14 | None |
| 1.3.6.1.4.1.123.3.29 | nncAtmStatistics | 4 | 179 | This module contains definitions for performance monitoring of the ATM layer and it's circuits. This MIB module contains the foll… |
| 1.3.6.1.4.1.123.3.30 | nncFrIntStatistics | 4 | 258 | This module contains definitions for performance monitoring of Frame Relay Streams |
| 1.3.6.1.4.1.123.3.31 | nncExtIntvlStats | 0 | 0 | The MIB module containing type definitions common to interval statistics collection mibs. |
| 1.3.6.1.4.1.123.3.32 | nncExtSVCSigStats | 4 | 177 | The MIB module containing management information for performance monitoring of SVC Signalling functions. |
| 1.3.6.1.4.1.123.3.40 | nncExtE3 | 4 | 43 | This module contains definitions for Newbridge extensions to E3 objects. It is used as a supplement to rfc1407. |
| 1.3.6.1.4.1.123.3.43 | nncExtMultiBridge | 5 | 85 | Newbridge's multi-BRIDGE MIB Module. for nodes which implements more than one bridge entity. |
| 1.3.6.1.4.1.123.3.44 | nncExtNotif | 4 | 85 | This MIB module contains information regarding Alarm and Trouble Ticket information forwarding as Notifications. |
| 1.3.6.1.4.1.123.3.47 | nncCEFillLevelStatistics | 3 | 9 | This module contains definitions for monitoring aal1 fill level statistics. |
| 1.3.6.1.4.1.123.3.49 | nncExtServiceNotif | 4 | 61 | This MIB module contains information regarding Service status information forwarded as Notifications. |
| 1.3.6.1.4.1.123.3.50 | nncExtPktStatistics | 4 | 59 | This module contains definitions for performance monitoring of the packets routed. This MIB module contains the following tables:… |
| 1.3.6.1.4.1.123.3.54 | nncAtmProtoStatistics | 3 | 38 | This module contains definitions for performance monitoring of the ATM cell layers. This MIB module contains the following tables… |
| 1.3.6.1.4.1.123.3.63 | nncAtmCongestionStatistics | 3 | 96 | This module contains the definitions for congestion statistics on ATM products. Congestion statistics allow the user to monitor… |
| 1.3.6.1.4.1.123.3.64 | nncSdslStatistics | 1 | 60 | This module contains definitions for SDSL Ports Stats. |
| 1.3.6.1.4.1.123.3.65 | nncExtPmStatistics | 4 | 89 | This module contains the definitions for statistics collected for OAM Performance Monitoring. The definition and requirement fo… |
| 1.3.6.1.4.1.123.3.69 | nncExtNEInventory | 3 | 22 | This module contains definition for monitoring the inventory of network elements in a network. The module can be used to query t… |
| 1.3.6.1.4.1.123.3.70 | nncBellcoreGR820Ds1Statistics | 3 | 47 | This module contains the definitions for the Bellcore GR820 statistics for DS1 lines. |
| 1.3.6.1.4.1.123.3.71 | nncAAL5 | 4 | 17 | This module contains definitions for monitoring and configuring AAL5 information on Newbridge ATM cards. |
| 1.3.6.1.4.1.123.3.72 | nncVS | 4 | 29 | This module contains definitions for monitoring and configuring Newbridge Voiceband Services cards. |
| 1.3.6.1.4.1.123.3.78 | nncExtRoutingStats | 3 | 467 | This MIB module contains management information for performance monitoring of call routing statistics. Seven types of statistics … |
| 1.3.6.1.4.1.123.3.79 | nncExtPvc | 3 | 84 | This module contains Alcatel's proprietary MIB definition for managing point-to-point and point-to-multipoint Permanent Virtual C… |
| 1.3.6.1.4.1.123.3.80 | nncExtVpttp | 3 | 8 | This module contains Alcatel's proprietary MIB definition for configuration of VP Trail Termination Points. This support is is pr… |