CISCO-VISM-CAC-MIB.mib object view, vendor Stratacom
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2024 can import MIB file CISCO-VISM-CAC-MIB and use it to monitor vendor specific OID's.
CISCO-VISM-CAC-MIB file content
Object view of CISCO-VISM-CAC-MIB:
| Scalar Object |
| vismChanCacEntry |
.1.3.6.1.4.1.351.110.5.5.3.1.3.1 |
|
Each entry in this table corresponds to a PVC, since
the CAC functionality is applied on a per PVC basis. The
bandwidth is allocated on a per PVC basis and the
connection admission control is done by comparing the
available bandwidth on a PVC with the required bandwidth
as a result of new connection setup request or upspeed
request.
|
| vismPortCacPvcAddFailures |
.1.3.6.1.4.1.351.110.5.5.20.1 |
|
Total number of attempts to add or modify a PVC to VISM
virtual port that were rejected by port level CAC.
|
| vismPortCacSvcAddFailures |
.1.3.6.1.4.1.351.110.5.5.20.2 |
|
Total number of attempts to add a SVC (Switched Virtual
Circuit) to VISM virtual port that were rejected by port
level CAC.
|
| vismVcCacPvcFailures |
.1.3.6.1.4.1.351.110.5.5.20.3 |
|
Total number of attempts to admit voice connections over
bearer PVC connections that were rejected by voice CAC.
It is sum of all voice CAC failures for all VISM bearer
PVC connections.
|
| vismVcCacPvcUpspeedFailures |
.1.3.6.1.4.1.351.110.5.5.20.4 |
|
Total number of attempts to upspeed voice connections
over bearer PVC connections that were rejected by port
level CAC.
|
| vismPortCacSvcUpspeedFailures |
.1.3.6.1.4.1.351.110.5.5.20.5 |
|
Total number of attempts to upspeed voice connections
over bearer SVC connections that were rejected by
port level CAC.
|
| Tabular Object |
| vismChanNum |
.1.3.6.1.4.1.351.110.5.5.3.1.3.1.1 |
|
This attribute defines the index for the vismChanCac Table.
The LCN(Logical channel number) number is the same as
the LCN value used as the index for the vismChanCnfGrpTable
(defined in CISCO-VISM-CONN-MIB MIB) i.e. vismCnfChanNum.
|
| vismChanCacMaster |
.1.3.6.1.4.1.351.110.5.5.3.1.3.1.2 |
|
This attribute defines whether the PVC is the master end
or slave end. CAC functionality is applied only at the master
end of the PVC. It is not necessary if the PVC end is configured
as the slave end. This is to prevent the glare condition
resulting from the simultaneous allocation of the same
bandwidth for different calls from both ends. This parameter
is applicable only in the trunking mode.
|
| vismChanCacPassedCons |
.1.3.6.1.4.1.351.110.5.5.3.1.3.1.3 |
|
This attribute defines the count of connections that
passed successfully the CAC function. CAC functionality is
applied either due to
1) The CRCX message sent to VISM from the Call Agent to set
up a new connection OR at the time of 'addcid' command in
AAL2 trunking application.
2) Upspeed request due to fax/modem tone detection on a
connection configured for compression.
|
| vismChanCacRejectedCons |
.1.3.6.1.4.1.351.110.5.5.3.1.3.1.4 |
|
This attribute defines the count of connections that
got rejected due to CAC function. The CAC rejection was
due to the bandwidth not being available on a given PVC.
|
| vismChanCacRejectionPolicy |
.1.3.6.1.4.1.351.110.5.5.3.1.3.1.5 |
|
This attribute defines the policy that needs to be applied
once the CAC function rejects the upspeeding of a connection,
due to a fax/modem switchover request. The applicable
options are
'delete' - to delete the connection that got rejected by CAC
for upspeed.
'maintain' - to maintain the connection with the prior
compression scheme.
'unspecified' - The CAC rejection policy as defined in
the card level object vismCacRejectionPolicy(defined in
CISCO-VISM-MODULE-MIB MIB) will be used, else the value
of this object will be used.
Note that the default value of maintaining the prior
encoding scheme is applicable in the trunking application
only since the connection is not deleted after the fax/modem
switchover.In the case of switching application, the
connection is deleted after the fax/modem switchover.
Configuring this object will not have any affect when
card level CAC object vismCacEnable(defined in
CISCO-VISM-MODULE-MIB MIB) is disabled.
|
| vismChanCarrierLossPolicy |
.1.3.6.1.4.1.351.110.5.5.3.1.3.1.6 |
|
This object defines the policy that needs to be applied
when a carrier loss is detected. The possible policies
are defined as follows:
'previousCodec' - switch to the pre-upspeed codec when a
a carrier loss is detected.
'upspeedCodec' - remain with the upspeed codec when a
carrier loss is detected.
'unspecified' - The card level object value
vismCarrierLossPolicy(defined in
CISCO-VISM-MODULE-MIB MIB) will be used.
Configuring this object will not have any affect when
card level CAC object vismCacEnable (defined in
CISCO-VISM-MODULE-MIB MIB) is disabled.
|
| vismChanVADTolerance |
.1.3.6.1.4.1.351.110.5.5.3.1.3.1.7 |
|
The value in this object refers to the customer accepted
drop rate for voice connections when the bandwidth usage
exceeds allowed value.
A value of zero indicates the card level object
vismVADTolerance(defined in CISCO-VISM-MODULE-MIB MIB)
value will be used.
Configuring this object will not have any affect when
card level CAC object vismCacEnable(defined in
CISCO-VISM-MODULE-MIB MIB) is disabled.
|
| vismChanVADDutyCycle |
.1.3.6.1.4.1.351.110.5.5.3.1.3.1.8 |
|
This object refers to the talk-spurts duty cycle.
A value of zero indicates the card level object
vismVADDutyCycle(defined in CISCO-VISM-MODULE-MIB MIB)
value will be used.
Configuring this object will not have any affect when
card level CAC object vismCacEnable(defined in
CISCO-VISM-MODULE-MIB MIB) is disabled.
|
| networkCacConfigState |
.1.3.6.1.4.1.351.110.5.5.3.1.3.1.9 |
|
This attribute defines whether the originating and terminating
VISMs are configured properly or not, by default the
configuration is assumed to be 'ok' and this object is set
to 'ok', if later during upspeed if we discover that both
the originating and terminating VISMs are configured as
either CAC master or slave then it is considered as an
invalid configuration and this object will be set to 'notOk'
and trapNetworkCacConfigState(defined in
CISCO-VISM-TRAPS-MIB MIB) change trap will be sent.
This parameter is applicable only in trunking applications.
|
| Table |
| vismChanCacTable |
.1.3.6.1.4.1.351.110.5.5.3.1.3 |
|
This table defines the CAC success or failure statistics.
CAC functionality is applied on a per PVC(Permanent virtual
circuit) basis for accepting the new calls in a switching
model (i.e when CRCX(CreateConnection) message is received
from the call agent) and when adding a new binding between a
CID(Channel Identifier) and a PVC in the AAL2 trunking
application ('addcid' command). In both switching and trunking
models, the CAC functionality is applied for upspeeding the
connections due to the detection of fax/modem tone on a
connection configured with voice compression. The entries in
this table are implicitly created and deleted with the
creation and deletion of entries in vismChanCnfGrpEntry
(defined in CISCO-VISM-CONN-MIB MIB).
|
| Object Identifier |
| ciscoVismCacMIB |
.1.3.6.1.4.1.351.150.96 |
|
The MIB module containing the CAC information
for VISM service module.
|
| vismCardCacFailuresGrp |
.1.3.6.1.4.1.351.110.5.5.20 |
| ciscoVismCacMIBConformance |
.1.3.6.1.4.1.351.150.96.2 |
| ciscoVismCacMIBGroups |
.1.3.6.1.4.1.351.150.96.2.1 |
| ciscoVismCacMIBCompliances |
.1.3.6.1.4.1.351.150.96.2.2 |
| Group |
| ciscoVismChanCacGroup |
.1.3.6.1.4.1.351.150.96.2.1.1 |
|
A collection of objects providing CAC
feature on PVC.
|
| ciscoVismCardCacFailuresGrp |
.1.3.6.1.4.1.351.150.96.2.1.2 |
|
A collection of objects providing CAC statistics
for both SVC and PVC connection.
|
