This module contains Alcatel's proprietary MIB definition for
managing point-to-point and point-to-multipoint Permanent Virtual
Connections (PVCs).
The MIB supports the creation, modification, query and deletion of PVCs
(Permanent Virtual Connections) on Cell Relay endpoints,
both Permanent Virtual Path Connection (PVPC) and Permanent Virtual
Channel Connection (PVCC) are supported. PVPCs are defined by
nncCrPvpcTable and PVCCs are defined by nncCrPvccTable.
PVPCs or PVCC's connecting different endpoint types, CR to FR,
FR to CR, CR to CE, CE to CR, CE to FR or FR to CE are not suppported
at this point. Resource connections such as Signalling, PNNI, ILMI and
CPSS are also not supported.
PVCs can be created by one of two ways: using rowStats as
'createAndGo' or using rowStatus as 'createAndWait'+'active'.
In some cases, to create a PVC via this table requires two SET-REQs,
because one SET-REQ PDU cannot fit all required objects. In these cases,
the rowStatus is set to createAndWait(5) for the first 1 SET-REQ
and set to active(1) for the last SET-REQ.
In some cases, all required MIB objects can fit in one SET-REQ PDU.
In these cases the rowStatus should be set to createAndGo(4)
To delete a PVC, the SNMP manager should set rowStatus of the PVC
instance to 'destroy'.
Each PVC is modeled as set of entries in the PVC table. A point-
to-point PVC is modeled as one entry; a point-to-multipoint (N leafs)
is modeled as N entries in this table. The N entries of a point-to-
multipoint PVC shares the same source end point.
Some abreviations:
abr/ABR/Abr: Available Bit Rate
Bwd: Backward. For traffice descriptors from destination end point to source end point
cbr/CBR/Cbr: Constant Bit Rate
Dst: Dstination end point
Fwd: Forward. For traffic descriptors from source end point to destination end point
nt-vbr/ntvbr/NT-VBR: Non-Real-Time Variable Bit Rate
p2p: Point-to-Point
p2mp: Point-to-Multipoint
Src: Source end point
Targ: Target. For the destination end point info in source end point table
ubr/UBR/Ubr: Unspecified Bit Rate
VCI/Vci/vci: Virtual channel identifier
VCL/Vcl/vcl: Virtual channel link
VPI/Vpi/vpi: Virtual path identifier
VPL/Vpl/Vpl: Virtual path link
Parsed from file NncExtPVC.mib.txt
Company: None
Module: NNCEXTPVC-MIB
This module contains Alcatel's proprietary MIB definition for
managing point-to-point and point-to-multipoint Permanent Virtual
Connections (PVCs).
The MIB supports the creation, modification, query and deletion of PVCs
(Permanent Virtual Connections) on Cell Relay endpoints,
both Permanent Virtual Path Connection (PVPC) and Permanent Virtual
Channel Connection (PVCC) are supported. PVPCs are defined by
nncCrPvpcTable and PVCCs are defined by nncCrPvccTable.
PVPCs or PVCC's connecting different endpoint types, CR to FR,
FR to CR, CR to CE, CE to CR, CE to FR or FR to CE are not suppported
at this point. Resource connections such as Signalling, PNNI, ILMI and
CPSS are also not supported.
PVCs can be created by one of two ways: using rowStats as
'createAndGo' or using rowStatus as 'createAndWait'+'active'.
In some cases, to create a PVC via this table requires two SET-REQs,
because one SET-REQ PDU cannot fit all required objects. In these cases,
the rowStatus is set to createAndWait(5) for the first 1 SET-REQ
and set to active(1) for the last SET-REQ.
In some cases, all required MIB objects can fit in one SET-REQ PDU.
In these cases the rowStatus should be set to createAndGo(4)
To delete a PVC, the SNMP manager should set rowStatus of the PVC
instance to 'destroy'.
Each PVC is modeled as set of entries in the PVC table. A point-
to-point PVC is modeled as one entry; a point-to-multipoint (N leafs)
is modeled as N entries in this table. The N entries of a point-to-
multipoint PVC shares the same source end point.
Some abreviations:
abr/ABR/Abr: Available Bit Rate
Bwd: Backward. For traffice descriptors from destination end point to source end point
cbr/CBR/Cbr: Constant Bit Rate
Dst: Dstination end point
Fwd: Forward. For traffic descriptors from source end point to destination end point
nt-vbr/ntvbr/NT-VBR: Non-Real-Time Variable Bit Rate
p2p: Point-to-Point
p2mp: Point-to-Multipoint
Src: Source end point
Targ: Target. For the destination end point info in source end point table
ubr/UBR/Ubr: Unspecified Bit Rate
VCI/Vci/vci: Virtual channel identifier
VCL/Vcl/vcl: Virtual channel link
VPI/Vpi/vpi: Virtual path identifier
VPL/Vpl/Vpl: Virtual path link
Parsed from file NNCEXTPVC-MIB.mib
Module: NNCEXTPVC-MIB
Vendor: Newbridge Networks Corporation
Module: NNCEXTPVC-MIB
[Automatically extracted from oidview.com]
nncExtPvc MODULE-IDENTITY LAST-UPDATED "200101261907Z" ORGANIZATION "Alcatel Networks Corporation" 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's proprietary MIB definition for managing point-to-point and point-to-multipoint Permanent Virtual Connections (PVCs). The MIB supports the creation, modification, query and deletion of PVCs (Permanent Virtual Connections) on Cell Relay endpoints, both Permanent Virtual Path Connection (PVPC) and Permanent Virtual Channel Connection (PVCC) are supported. PVPCs are defined by nncCrPvpcTable and PVCCs are defined by nncCrPvccTable. PVPCs or PVCC's connecting different endpoint types, CR to FR, FR to CR, CR to CE, CE to CR, CE to FR or FR to CE are not suppported at this point. Resource connections such as Signalling, PNNI, ILMI and CPSS are also not supported. PVCs can be created by one of two ways: using rowStats as 'createAndGo' or using rowStatus as 'createAndWait'+'active'. In some cases, to create a PVC via this table requires two SET-REQs, because one SET-REQ PDU cannot fit all required objects. In these cases, the rowStatus is set to createAndWait(5) for the first 1 SET-REQ and set to active(1) for the last SET-REQ. In some cases, all required MIB objects can fit in one SET-REQ PDU. In these cases the rowStatus should be set to createAndGo(4) To delete a PVC, the SNMP manager should set rowStatus of the PVC instance to 'destroy'. Each PVC is modeled as set of entries in the PVC table. A point- to-point PVC is modeled as one entry; a point-to-multipoint (N leafs) is modeled as N entries in this table. The N entries of a point-to- multipoint PVC shares the same source end point. Some abreviations: abr/ABR/Abr: Available Bit Rate Bwd: Backward. For traffice descriptors from destination end point to source end point cbr/CBR/Cbr: Constant Bit Rate Dst: Dstination end point Fwd: Forward. For traffic descriptors from source end point to destination end point nt-vbr/ntvbr/NT-VBR: Non-Real-Time Variable Bit Rate p2p: Point-to-Point p2mp: Point-to-Multipoint Src: Source end point Targ: Target. For the destination end point info in source end point table ubr/UBR/Ubr: Unspecified Bit Rate VCI/Vci/vci: Virtual channel identifier VCL/Vcl/vcl: Virtual channel link VPI/Vpi/vpi: Virtual path identifier VPL/Vpl/Vpl: Virtual path link " ::= { nncExtensions 79 }
nncExtPvc MODULE-IDENTITY LAST-UPDATED "200101261907Z" ORGANIZATION "Alcatel Networks Corporation" 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's proprietary MIB definition for managing point-to-point and point-to-multipoint Permanent Virtual Connections (PVCs). The MIB supports the creation, modification, query and deletion of PVCs (Permanent Virtual Connections) on Cell Relay endpoints, both Permanent Virtual Path Connection (PVPC) and Permanent Virtual Channel Connection (PVCC) are supported. PVPCs are defined by nncCrPvpcTable and PVCCs are defined by nncCrPvccTable. PVPCs or PVCC's connecting different endpoint types, CR to FR, FR to CR, CR to CE, CE to CR, CE to FR or FR to CE are not suppported at this point. Resource connections such as Signalling, PNNI, ILMI and CPSS are also not supported. PVCs can be created by one of two ways: using rowStats as 'createAndGo' or using rowStatus as 'createAndWait'+'active'. In some cases, to create a PVC via this table requires two SET-REQs, because one SET-REQ PDU cannot fit all required objects. In these cases, the rowStatus is set to createAndWait(5) for the first 1 SET-REQ and set to active(1) for the last SET-REQ. In some cases, all required MIB objects can fit in one SET-REQ PDU. In these cases the rowStatus should be set to createAndGo(4) To delete a PVC, the SNMP manager should set rowStatus of the PVC instance to 'destroy'. Each PVC is modeled as set of entries in the PVC table. A point- to-point PVC is modeled as one entry; a point-to-multipoint (N leafs) is modeled as N entries in this table. The N entries of a point-to- multipoint PVC shares the same source end point. Some abreviations: abr/ABR/Abr: Available Bit Rate Bwd: Backward. For traffice descriptors from destination end point to source end point cbr/CBR/Cbr: Constant Bit Rate Dst: Dstination end point Fwd: Forward. For traffic descriptors from source end point to destination end point nt-vbr/ntvbr/NT-VBR: Non-Real-Time Variable Bit Rate p2p: Point-to-Point p2mp: Point-to-Multipoint Src: Source end point Targ: Target. For the destination end point info in source end point table ubr/UBR/Ubr: Unspecified Bit Rate VCI/Vci/vci: Virtual channel identifier VCL/Vcl/vcl: Virtual channel link VPI/Vpi/vpi: Virtual path identifier VPL/Vpl/Vpl: Virtual path link " ::= { nncExtensions 79 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.123.3.79.1 | nncExtPvcObjects | 2 | 78 | None |
| 1.3.6.1.4.1.123.3.79.3 | nncExtPvcGroups | 2 | 2 | None |
| 1.3.6.1.4.1.123.3.79.4 | nncExtPvcCompliances | 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.80 | nncExtVpttp | 3 | 8 | This module contains Alcatel's proprietary MIB definition for configuration of VP Trail Termination Points. This support is is pr… |
| 1.3.6.1.4.1.123.3.82 | nncExtSpvc | 3 | 213 | This module contains Alcatel CID's proprietary MIB definition for managing Soft Permanent Virtual Connections (SPVCs). This MIB s… |