CISCO-WAN-MODULE-MIB
AI MIB Summary
The CISCO-WAN-MODULE-MIB enables configuration and statistical monitoring of service module parameters for ATM, Frame Relay, and Voice services within Cisco WAN switches. It tracks connection-specific operational states, traffic counters, and error statistics for these wide-area network interface modules.
The MIB to configure Connection Specific parameters and statistics related information in a Service Module. The Service Module(SM) is defined as any Module which provides services such as ATM, Frame Relay or Voice in a Wide Area Network(WAN) switch.
Main OID:
ciscoWanModuleMIB.1.3.6.1.4.1.9.9.145
26
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
26 total| Object Name |
|---|
ciscoWanModuleMIBThe MIB to configure Connection Specific parameters and
statistics related information in a Service Module.
The Service Module(SM) is defined as any Module which
provides services such as ATM, Frame Relay or Voice in a
Wide Area Network(WAN) switch. MODULE-IDENTITY .1.3.6.1.4.1.9.9.145 |
cwmMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.145.1 |
cwmConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.145.1.1 |
cwmConfigTableThis table contains objects required for configuring module
specific parameters. These parameters may be related to the
hardware specific parameters which can affect the
ATM Connection characteristics. SEQUENCE OF CwmConfigEntry .1.3.6.1.4.1.9.9.145.1.1.1 |
cwmConfigEntryEntry containing information for each module. CwmConfigEntry .1.3.6.1.4.1.9.9.145.1.1.1.1 |
cwmIndexThis object's value generally corresponds to the
slot number where the module resides. However,
system wide uniqueness is the only true requirement. Unsigned32 .1.3.6.1.4.1.9.9.145.1.1.1.1.1 |
cwmIngressSCTFileIdThe file ID of the Service Class Template(SCT) file. The SCT
holds the connection specific parameters for this module in
the ingress direction(From Network to the Switch).
Terminologies used:
SCT : Service Class Template
The Service Class Template ( or Service Template or SCT )
provides a means for inferring extended parameters, which
are generally platform-specific, from the set of standard
ATM protocol parameters passed in VSI(Virtual Switch Interface)
connection setup primitives. A set of Service Templates are
available in a non-volatile storage and is downloaded onto
each Service Module on power up.
In general, SCTs contain two classes of data. One class consists
of parameters necessary to establish a Virtual Connection
(i.e. Per-VC) and includes entries such as UPC(Usage Parameter Control)
actions, various bandwidth-related items, per-VC thresholds,
and some hardware-specific items.The second class of data items
includes those necessary to configure the associated
Class-of-Service Buffers that provide the QoS support.rw Unsigned32 .1.3.6.1.4.1.9.9.145.1.1.1.1.2 |
cwmIngressSCTFileNameThis variable contains the SCT filename. Write access
is not required. The filename has cwmIngressSCTFileId
value as the suffix. For example, the value SCT.INGR.13
for this object indicates 13 is the value of
cwmIngressSCTFileId.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.145.1.1.1.1.3 |
cwmAutoLineDiagEnableThis object enables/disables automatic diagnostic feature
of physical lines on module.
In case of a line alarm, enabling this feature temporarily
suspends traffic in both direction and starts local loop-back
testing. Disabling this feature will not effect the traffic
in one direction while another direction is in alarm.rw Enumeration .1.3.6.1.4.1.9.9.145.1.1.1.1.4 |
cwmSCTFileVerCfgThe Configured version of the Service Class Template(SCT)
file. This version applies to both the card SCT and the port
SCT files in a service module.
The port SCT files are specified while provisioning a port using
the caviFileId field in the CISCO-WAN-VIRTUAL-IF-MIB.my MIB.
The card SCT file is specifed in this MIB using the
cwmIngressSCTFileName object.
The configured version of the SCT does not take effect until
the service module is rebooted. However, graceful invocation
of a new SCT version can be achieved by using redundant service
modules. The configured SCT version is first applied on a standby
service module by rebooting it. When the standby reboots, it
comes up with the configured SCT version. Thereafter a switchover
can be performed, making the standby SM take over as active.rw Unsigned32 .1.3.6.1.4.1.9.9.145.1.1.1.1.5 |
cwmSCTFileVerOprThe operational version of the Service Class Template(SCT)
file. This is sct version currently in use. The operational
version could be different from the configured version
(cwmSCTFileVerCfg), until the service module is rebooted.ro Unsigned32 .1.3.6.1.4.1.9.9.145.1.1.1.1.6 |
cwmUploadCounterThis counter is used by the management station to
determine if any changes(other than ATM/FR connections)
have been done on configuration of a card.
The use of this object is implementation specific.
This requires the NMS application saving the previous
value of this object and compare it later for finding
any changes in the card.
The upload counter is incremented in, for instance:
- any physical interface characteristics are modified.
- any logical interface is added/deleted/modified.
- any IMA Group/MFR bundle is added/deleted/modified.
- any resource is added/deleted/modified on an interface.
- any configuration changes are done(not specified above)
which are not related to ATM/FR Connections
(SPVCs for example).ro Unsigned32 .1.3.6.1.4.1.9.9.145.1.1.1.1.7 |
cwmStatsConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.145.1.2 |
cwmStatConfigTableThis table has objects required for configuring module statistic
collection related parameters. The statistics related to interfaces
and ATM Connections are stored in a file. The statistics file can be
uploaded by NMS applications using file transfer protocols such as tftp
or ftp. While current interval of data is being collected in memory,
previous interval of data is uploaded by NMS. Each interval's
data will overwrite the previous interval's data in the statistic
file after the interval is over. SEQUENCE OF CwmStatConfigEntry .1.3.6.1.4.1.9.9.145.1.2.1 |
cwmStatConfigEntryEntry containing statistics configuration information for
the module. CwmStatConfigEntry .1.3.6.1.4.1.9.9.145.1.2.1.1 |
cwmStatBucketIntervalThis object contains the bucket interval in minutes used in
collecting statistics. This specifies the interval over
which the module accumulates a sample. This value also
defines the amount of time available to NMS application
to upload the statistic file in order to not miss one
interval worth of data.rw Enumeration .1.3.6.1.4.1.9.9.145.1.2.1.1.1 |
cwmStatCollectionIntervalThe collection interval of statistics. Within a sampling interval,
as defined by cwmStatBucketInterval, statistics counters are
updated every collection interval.
Default value of collection interval is same as bucket interval.
In case of bucket interval being 5 minutes, default(0) and five(5)
values for this object has the same effect.rw Enumeration .1.3.6.1.4.1.9.9.145.1.2.1.1.2 |
cwmStatCollectionStatusEnables or disables statistics collection on the module.rw Enumeration .1.3.6.1.4.1.9.9.145.1.2.1.1.3 |
cwmStatCurrentLevelThe current statistics level of the module.
A change in the card statistic level can take place only
after a module reset. This object shows the current module
statistic level. While cwmStatLevelConfigured object is
used to configure module statistic level. The value
set in cwmStatLevelConfigured object will take effect after
next module reset.ro StatisticsLevel .1.3.6.1.4.1.9.9.145.1.2.1.1.4 |
cwmStatLevelConfiguredThis object is used to configure the statistics level
for the module. The statistics level value set in this
object will take effect only on reset of the module.
This object can be set only if cwmStatCollectionStatus is set
to enable(1). This object cannot be set to notApplicable(0).rw StatisticsLevel .1.3.6.1.4.1.9.9.145.1.2.1.1.5 |
cwmStatMaximumConnectionsThe maximum number of connections for which the statistics are
being collected.ro Unsigned32 .1.3.6.1.4.1.9.9.145.1.2.1.1.6 |
ciscoWanModuleMIBNotificationPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.145.2 |
ciscoWanModuleMIBNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.145.2.0 |
ciscoWanModuleMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.145.3 |
ciscoWanModuleMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.145.3.1 |
ciscoWanModuleMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.145.3.2 |