VPI(s) to be used for the VC switching (VCC) on top of VPI 0 which is always used for VC switching. All VC switching VPI have similar valid VCI range which is determined by 'vpi-vci-range' attribute. Rest of the VPIs will be used for the VP switching. The user needs to understand that adding a VPI in a list of VC switching VPI will allocate more VCCs for this port. The user needs to make sure that VCCs for the other ports have been reduced to accomodate increase in VCC for this port because system can support only 32k VCCs on all trunk ports combined. If vci-range is 4k and VPI 0 is the only VPI doing VC switching for this port than this port occupies 4k VCCs. If user adds VPI 1 to the list of VPIs to do VCC then total 8k VCCs are occupied for this port. System will reject the confiugration if user tries to use more than 32k VCCs for all trunk ports combined. ANY CHANGES IN A LIST OF VPIs WILL BE EFFECTIVE IMMEDIATLY. IN ORDER TO DO THAT ALL CONNECTIONS WITHIN THIS SYSTEM WILL BE DROPPED AND REESTABLISHED.
Parsed from file mibe3atmnet.mib.txt
Company: None
Module: ASCEND-MIBE3ATMNETWORKPROFILE-MIB
VPI(s) to be used for the VC switching (VCC). It should always contain VPI 0 for VC switching. All VC switching VPI have similar valid VCI range which is determined by 'vpi-vci-range' attribute. Rest of the VPIs will be used for the VP switching. The user needs to understand that adding a VPI in a list of VC switching VPI will allocate more VCCs for this port. The user needs to make sure that VCCs for the other ports have been reduced to accommodate increase in VCC for this port because system can support only 32k VCCs on all trunk ports combined. If vci-range is 4k and VPI 0 is the only VPI doing VC switching for this port than this port occupies 4k VCCs. If user adds VPI 1 to the list of VPIs to do VCC then total 8k VCCs are occupied for this port. System will reject the configuration if user tries to use more than 32k VCCs for all trunk ports combined. ANY CHANGES IN A LIST OF VPIs WILL BE EFFECTIVE IMMEDIATLY. IN ORDER TO DO THAT ALL CONNECTIONS WITHIN THIS SYSTEM WILL BE DROPPED AND REESTABLISHED.
Parsed from file ASCEND-MIBE3ATMNET-MIB.mib
Module: ASCEND-MIBE3ATMNET-MIB
Vendor: Ascend Communications Inc.
Module: ASCEND-MIBE3ATMNET-MIB
[Automatically extracted from oidview.com]
e3AtmNetworkProfile__line_config__vc_switching_vpi OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "VPI(s) to be used for the VC switching (VCC) on top of VPI 0 which is always used for VC switching. All VC switching VPI have similar valid VCI range which is determined by 'vpi-vci-range' attribute. Rest of the VPIs will be used for the VP switching. The user needs to understand that adding a VPI in a list of VC switching VPI will allocate more VCCs for this port. The user needs to make sure that VCCs for the other ports have been reduced to accomodate increase in VCC for this port because system can support only 32k VCCs on all trunk ports combined. If vci-range is 4k and VPI 0 is the only VPI doing VC switching for this port than this port occupies 4k VCCs. If user adds VPI 1 to the list of VPIs to do VCC then total 8k VCCs are occupied for this port. System will reject the confiugration if user tries to use more than 32k VCCs for all trunk ports combined. ANY CHANGES IN A LIST OF VPIs WILL BE EFFECTIVE IMMEDIATLY. IN ORDER TO DO THAT ALL CONNECTIONS WITHIN THIS SYSTEM WILL BE DROPPED AND REESTABLISHED." ::= { mibe3AtmNetworkProfile__line_config__vc_switching_vpiEntry 5 }
e3AtmNetworkProfile-LineConfig-VcSwitchingVpi OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "VPI(s) to be used for the VC switching (VCC). It should always contain VPI 0 for VC switching. All VC switching VPI have similar valid VCI range which is determined by 'vpi-vci-range' attribute. Rest of the VPIs will be used for the VP switching. The user needs to understand that adding a VPI in a list of VC switching VPI will allocate more VCCs for this port. The user needs to make sure that VCCs for the other ports have been reduced to accommodate increase in VCC for this port because system can support only 32k VCCs on all trunk ports combined. If vci-range is 4k and VPI 0 is the only VPI doing VC switching for this port than this port occupies 4k VCCs. If user adds VPI 1 to the list of VPIs to do VCC then total 8k VCCs are occupied for this port. System will reject the configuration if user tries to use more than 32k VCCs for all trunk ports combined. ANY CHANGES IN A LIST OF VPIs WILL BE EFFECTIVE IMMEDIATLY. IN ORDER TO DO THAT ALL CONNECTIONS WITHIN THIS SYSTEM WILL BE DROPPED AND REESTABLISHED." ::= { mibe3AtmNetworkProfile-LineConfig-VcSwitchingVpiEntry 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.529.23.15.4.1.1 | e3AtmNetworkProfile-LineConfig-VcSwitchingVpi-Shelf-o, e3AtmNetworkProfile__line_config__vc_switching_vpi__shelf__ | 0 | 0 | None |
| 1.3.6.1.4.1.529.23.15.4.1.2 | e3AtmNetworkProfile-LineConfig-VcSwitchingVpi-Slot-o, e3AtmNetworkProfile__line_config__vc_switching_vpi__slot__ | 0 | 0 | None |
| 1.3.6.1.4.1.529.23.15.4.1.3 | e3AtmNetworkProfile-LineConfig-VcSwitchingVpi-Item-o, e3AtmNetworkProfile__line_config__vc_switching_vpi__item__ | 0 | 0 | None |
| 1.3.6.1.4.1.529.23.15.4.1.4 | e3AtmNetworkProfile-LineConfig-VcSwitchingVpi-Index-o, e3AtmNetworkProfile__line_config__vc_switching_vpi__index__ | 0 | 0 | None |