This table defines allocation of virtual bandwidth pool for
the traffic classes. Basically there are two types of bandwidth
pool, Physical & Virtual. Physical bandwidth is the egress
interface bandwidth. It is not supported and will not be
explained more.
Virtual bandwidth is user defined bandwidth. Virtual bandwidth
provides an easy and flexible way to implement bandwidth pool
for call admission control to avoid physical bandwidth
limitations. In contrast to per-interface based physical
bandwidth management, Virtual bandwidth management is per-APN
based, that is, each APN has its own pool to admit request.
To use this type of bandwidth, user needs to make assumption of
what interface type and total bandwidth of Gi and Gn in both
directions to allocate bandwidth for each class.
The SNMP entity creates a conceptual row when the user
configures the bandwidth pool with some bandwidth value in the
range described in cggsnUmtsQosCacBWPoolBWVal.
The SNMP entity deletes the conceptual row, when the user
deletes the bandwidth pool. However, if the bandwidth pool is
associated with an APN or if bandwidth is currently been
utilized, then the conceptual row cannot be deleted.
The SNMP entity modifies the conceptual row, when the user
changes the bandwidth value. However, if any PDP context is
active in the APN using this pool, then the bandwidth value
can be changed to higher than the previously configured.
Parsed from file CISCO-GGSN-QOS-MIB.mib
Module: CISCO-GGSN-QOS-MIB
This table defines allocation of virtual bandwidth pool for
the traffic classes. Basically there are two types of bandwidth
pool, Physical & Virtual. Physical bandwidth is the egress
interface bandwidth. It is not supported and will not be
explained more.
Virtual bandwidth is user defined bandwidth. Virtual bandwidth
provides an easy and flexible way to implement bandwidth pool
for call admission control to avoid physical bandwidth
limitations. In contrast to per-interface based physical
bandwidth management, Virtual bandwidth management is per-APN
based, that is, each APN has its own pool to admit request.
To use this type of bandwidth, user needs to make assumption of
what interface type and total bandwidth of Gi and Gn in both
directions to allocate bandwidth for each class.
The SNMP entity creates a conceptual row when the user
configures the bandwidth pool with some bandwidth value in the
range described in cggsnUmtsQosCacBWPoolBWVal.
The SNMP entity deletes the conceptual row, when the user
deletes the bandwidth pool. However, if the bandwidth pool is
associated with an APN or if bandwidth is currently been
utilized, then the conceptual row cannot be deleted.
The SNMP entity modifies the conceptual row, when the user
changes the bandwidth value. However, if any PDP context is
active in the APN using this pool, then the bandwidth value
can be changed to higher than the previously configured.
This table defines allocation of virtual bandwidth pool for
the traffic classes. Basically there are two types of bandwidth
pool, Physical & Virtual. Physical bandwidth is the egress
interface bandwidth. It is not supported and will not be
explained more.
Virtual bandwidth is user defined bandwidth. Virtual bandwidth
provides an easy and flexible way to implement bandwidth pool
for call admission control to avoid physical bandwidth
limitations. In contrast to per-interface based physical
bandwidth management, Virtual bandwidth management is per-APN
based, that is, each APN has its own pool to admit request.
To use this type of bandwidth, user needs to make assumption of
what interface type and total bandwidth of Gi and Gn in both
directions to allocate bandwidth for each class.
The SNMP entity creates a conceptual row when the user
configures the bandwidth pool with some bandwidth value in the
range described in cggsnUmtsQosCacBWPoolBWVal.
The SNMP entity deletes the conceptual row, when the user
deletes the bandwidth pool. However, if the bandwidth pool is
associated with an APN or if bandwidth is currently been
utilized, then the conceptual row cannot be deleted.
The SNMP entity modifies the conceptual row, when the user
changes the bandwidth value. However, if any PDP context is
active in the APN using this pool, then the bandwidth value
can be changed to higher than the previously configured.
Parsed from file CISCO-GGSN-QOS-MIB.my.txt
Company: None
Module: CISCO-GGSN-QOS-MIB
This table defines allocation of virtual bandwidth pool for
the traffic classes. Basically there are two types of bandwidth
pool, Physical & Virtual. Physical bandwidth is the egress
interface bandwidth. It is not supported and will not be
explained more.
Virtual bandwidth is user defined bandwidth. Virtual bandwidth
provides an easy and flexible way to implement bandwidth pool
for call admission control to avoid physical bandwidth
limitations. In contrast to per-interface based physical
bandwidth management, Virtual bandwidth management is per-APN
based, that is, each APN has its own pool to admit request.
To use this type of bandwidth, user needs to make assumption of
what interface type and total bandwidth of Gi and Gn in both
directions to allocate bandwidth for each class.
The SNMP entity creates a conceptual row when the user
configures the bandwidth pool with some bandwidth value in the
range described in cggsnUmtsQosCacBWPoolBWVal.
The SNMP entity deletes the conceptual row, when the user
deletes the bandwidth pool. However, if the bandwidth pool is
associated with an APN or if bandwidth is currently been
utilized, then the conceptual row cannot be deleted.
The SNMP entity modifies the conceptual row, when the user
changes the bandwidth value. However, if any PDP context is
active in the APN using this pool, then the bandwidth value
can be changed to higher than the previously configured.
cggsnUmtsQosCacBWPoolTable OBJECT-TYPE SYNTAX SEQUENCE OF CggsnUmtsQosCacBWPoolEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines allocation of virtual bandwidth pool for the traffic classes. Basically there are two types of bandwidth pool, Physical & Virtual. Physical bandwidth is the egress interface bandwidth. It is not supported and will not be explained more. Virtual bandwidth is user defined bandwidth. Virtual bandwidth provides an easy and flexible way to implement bandwidth pool for call admission control to avoid physical bandwidth limitations. In contrast to per-interface based physical bandwidth management, Virtual bandwidth management is per-APN based, that is, each APN has its own pool to admit request. To use this type of bandwidth, user needs to make assumption of what interface type and total bandwidth of Gi and Gn in both directions to allocate bandwidth for each class. The SNMP entity creates a conceptual row when the user configures the bandwidth pool with some bandwidth value in the range described in cggsnUmtsQosCacBWPoolBWVal. The SNMP entity deletes the conceptual row, when the user deletes the bandwidth pool. However, if the bandwidth pool is associated with an APN or if bandwidth is currently been utilized, then the conceptual row cannot be deleted. The SNMP entity modifies the conceptual row, when the user changes the bandwidth value. However, if any PDP context is active in the APN using this pool, then the bandwidth value can be changed to higher than the previously configured." ::= { cggsnQosUmtsCac 5 }
cggsnUmtsQosCacBWPoolTable OBJECT-TYPE SYNTAX SEQUENCE OF CggsnUmtsQosCacBWPoolEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table defines allocation of virtual bandwidth pool for the traffic classes. Basically there are two types of bandwidth pool, Physical & Virtual. Physical bandwidth is the egress interface bandwidth. It is not supported and will not be explained more. Virtual bandwidth is user defined bandwidth. Virtual bandwidth provides an easy and flexible way to implement bandwidth pool for call admission control to avoid physical bandwidth limitations. In contrast to per-interface based physical bandwidth management, Virtual bandwidth management is per-APN based, that is, each APN has its own pool to admit request. To use this type of bandwidth, user needs to make assumption of what interface type and total bandwidth of Gi and Gn in both directions to allocate bandwidth for each class. The SNMP entity creates a conceptual row when the user configures the bandwidth pool with some bandwidth value in the range described in cggsnUmtsQosCacBWPoolBWVal. The SNMP entity deletes the conceptual row, when the user deletes the bandwidth pool. However, if the bandwidth pool is associated with an APN or if bandwidth is currently been utilized, then the conceptual row cannot be deleted. The SNMP entity modifies the conceptual row, when the user changes the bandwidth value. However, if any PDP context is active in the APN using this pool, then the bandwidth value can be changed to higher than the previously configured." ::= { cggsnQosUmtsCac 5 }
Vendor: Cisco
Module: CISCO-GGSN-QOS-MIB
[Automatically extracted from oidview.com]
cggsnUmtsQosCacBWPoolTable OBJECT-TYPE SYNTAX SEQUENCE OF CggsnUmtsQosCacBWPoolEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines allocation of virtual bandwidth pool for the traffic classes. Basically there are two types of bandwidth pool, Physical & Virtual. Physical bandwidth is the egress interface bandwidth. It is not supported and will not be explained more. Virtual bandwidth is user defined bandwidth. Virtual bandwidth provides an easy and flexible way to implement bandwidth pool for call admission control to avoid physical bandwidth limitations. In contrast to per-interface based physical bandwidth management, Virtual bandwidth management is per-APN based, that is, each APN has its own pool to admit request. To use this type of bandwidth, user needs to make assumption of what interface type and total bandwidth of Gi and Gn in both directions to allocate bandwidth for each class. The SNMP entity creates a conceptual row when the user configures the bandwidth pool with some bandwidth value in the range described in cggsnUmtsQosCacBWPoolBWVal. The SNMP entity deletes the conceptual row, when the user deletes the bandwidth pool. However, if the bandwidth pool is associated with an APN or if bandwidth is currently been utilized, then the conceptual row cannot be deleted. The SNMP entity modifies the conceptual row, when the user changes the bandwidth value. However, if any PDP context is active in the APN using this pool, then the bandwidth value can be changed to higher than the previously configured." ::= { cggsnQosUmtsCac 5 }
cggsnUmtsQosCacBWPoolTable OBJECT-TYPE SYNTAX SEQUENCE OF CggsnUmtsQosCacBWPoolEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines allocation of virtual bandwidth pool for the traffic classes. Basically there are two types of bandwidth pool, Physical & Virtual. Physical bandwidth is the egress interface bandwidth. It is not supported and will not be explained more. Virtual bandwidth is user defined bandwidth. Virtual bandwidth provides an easy and flexible way to implement bandwidth pool for call admission control to avoid physical bandwidth limitations. In contrast to per-interface based physical bandwidth management, Virtual bandwidth management is per-APN based, that is, each APN has its own pool to admit request. To use this type of bandwidth, user needs to make assumption of what interface type and total bandwidth of Gi and Gn in both directions to allocate bandwidth for each class. The SNMP entity creates a conceptual row when the user configures the bandwidth pool with some bandwidth value in the range described in cggsnUmtsQosCacBWPoolBWVal. The SNMP entity deletes the conceptual row, when the user deletes the bandwidth pool. However, if the bandwidth pool is associated with an APN or if bandwidth is currently been utilized, then the conceptual row cannot be deleted. The SNMP entity modifies the conceptual row, when the user changes the bandwidth value. However, if any PDP context is active in the APN using this pool, then the bandwidth value can be changed to higher than the previously configured." ::= { cggsnQosUmtsCac 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.241.1.3.4.5.1 | cggsnUmtsQosCacBWPoolEntry | 3 | 3 | Each entry in this table holds the total bandwidth that this pool provides and the corresponding allocation to the traffic classe… |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.241.1.3.4.1 | cggsnUmtsQosMapImsSigTrafClass | 1 | 1 | This object is to map the IP Multimedia Subsystem (IMS) signaling traffic to one of UMTS traffic class. Only 'interactive' or 'ba… |
| 1.3.6.1.4.1.9.9.241.1.3.4.2 | cggsnUmtsQosMapImsSigTrafHandPri | 1 | 1 | This object is to set the priority of traffic handling for interactive class. This object can be set only if the traffic class is… |
| 1.3.6.1.4.1.9.9.241.1.3.4.3 | cggsnUmtsQosCacPolicyTable | 1 | 11 | Call Admission Control (CAC) is to ensure that network resources are not oversubscribed to protect real-time traffic such as voic… |
| 1.3.6.1.4.1.9.9.241.1.3.4.4 | cggsnUmtsQosCacTcTable | 1 | 8 | This table defines Maximum Bit Rate and/or Guaranteed Bit rate that can be allowed for each traffic class in both uplink and down… |
| 1.3.6.1.4.1.9.9.241.1.3.4.6 | cggsnQosBWPoolTrafClassTable | 1 | 7 | This table is the sub table of cggsnUmtsQosCacBWPoolTable. This contains all the traffic class bandwidth allocation in percentage… |