MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 241 (cggsnQosMIB). 1 (cggsnQosMIBObjects). 3 (cggsnQosUmtsQos). 4 (cggsnQosUmtsCac). 5 (cggsnUmtsQosCacBWPoolTable)
OID : 1.3.6.1.4.1.9.9.241.1.3.4.5
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. cggsnQosMIB. cggsnQosMIBObjects. cggsnQosUmtsQos. cggsnQosUmtsCac. cggsnUmtsQosCacBWPoolTable
Enfants
Détails
OID1.3.6.1.4.1.9.9.241.1.3.4.5
Module CISCO-GGSN-QOS-MIB (CISCO)
NomcggsnUmtsQosCacBWPoolTable
Statuscurrent
DescriptionThis 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.