CISCO-WAN-ATM-PARTY-MIB
The CISCO-WAN-ATM-PARTY-MIB manages the dynamic addition, removal, and configuration of leaf endpoints ("parties") within Cisco ATM point-to-multipoint Soft Permanent Virtual Circuit (SPVC) connections, operating under ITU-T Q.2971 signaling standards. This module specifically handles the multipoint topology extension by managing party state and parameters, excluding the root endpoint provisioning which is defined in the CISCO-WAN-ATM-CONN-MIB.
Imported Objects
Objects
22 total| Object Name |
|---|
ciscoWanAtmPartyMIBA management station can use this MIB to provision,
manage or delete one or more 'parties' on an ATM
point-to-multipoint Soft PVCC(SPVC) connection.
The user must add a root endpoint to the managed system
before proceed to add one or more 'parties' to the root.
The provision and management of a 'root' endpoint is
beyond the scope of this MIB. Please refer to
CISCO-WAN-ATM-CONN-MIB.my for the provisioning and
management of a 'root' endpoint.
This MIB is based on 'ITU-T recommendation Q.2971 (10/95)
BROADBAND INTEGRATED SERVICES DIGITAL NETWORK (B-ISDN)
- DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 2 (DSS 2) -
USER-NETWORK INTERFACE LAYER 3 SPECIFICATION FOR POINT-
TO-MULTIPOINT CALL/CONNECTION CONTROL MODULE-IDENTITY .1.3.6.1.4.1.9.9.99998 |
ciscoWanAtmPartyMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99998.0 |
ciscoWanAtmPartyMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99998.1 |
cwapConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99998.1.1 |
cwapConfigTableThis table contains mandatory 'party' configuration
for all ATM point-to-multipoint Soft Permanent Virtual
Channel Connections (SPVC). SEQUENCE OF CwapConfigEntry .1.3.6.1.4.1.9.9.99998.1.1.1 |
cwapConfigEntryAn entry in the 'cwapConfigTable'. Each entry
corresponds to one party of a point-to-multipoint
connection.
(1) To add an entry, the management
application must first provision a 'root' endpoint.
(2) While adding an entry, the variables
'cwapNSAPAddress', 'cwapVpi' and 'cwapVci' are
mandatory. The 'cwapNSAPAddress', 'csapVpi'
and 'cwapVci' are not required to be unique.
(3) The row creation will fail if the root endpoint does
not exist.
(4) The following management operations are permitted on
a row when the 'cwapRowStatus' is 'active':
a) row deletion.
b) toggling of the administrative status of a 'party'
via the 'cwapAdminStatus' object.
c) triggering a reroute via the 'cwapReroute' object.
(5) The table index 'ifIndex' refers to that of the root.
The 'ifIndex' identifies an ATM Virtual Interface
('ifType' atmVirtual(149)). CwapConfigEntry .1.3.6.1.4.1.9.9.99998.1.1.1.1 |
cwapRootVpiThis object identifies the Virtual Path
Identifier(VPI) of the root endpoint
this party is associated with. Integer32 .1.3.6.1.4.1.9.9.99998.1.1.1.1.1 |
cwapRootVciThis object identifies the Virtual
Channel Identifier (VCI) of the root
endpoint this party is associated with. Integer32 .1.3.6.1.4.1.9.9.99998.1.1.1.1.2 |
cwapReferenceAn arbitrary integer which serves to distinguish
between the multiple parties attached to a root of
a point-to-multipoint SPVC. Integer32 .1.3.6.1.4.1.9.9.99998.1.1.1.1.3 |
cwapNSAPAddressThe ATM NSAP address of this party.rw WanNsapAtmAddress .1.3.6.1.4.1.9.9.99998.1.1.1.1.4 |
cwapVpiThe VPI value of this party.rw Integer32 .1.3.6.1.4.1.9.9.99998.1.1.1.1.5 |
cwapVciThe VCI value of this party.rw Integer32 .1.3.6.1.4.1.9.9.99998.1.1.1.1.6 |
cwapRerouteThe management station uses this object to trigger the
re-routing of the party.
* Rerouting takes effect, when this object is set to true(1).
When set to false(2), no action is taken.
* The value 'false' will always be returned on snmp query
to this variable.
* During reroute operation, the 'cwapOperStatus' will contain
the value 'fail'. Upon successful completion of reroute,
the 'cwapOperStatus' will change to the value 'ok'. If the
reroute operation failed, the 'cwapOperStatus' will stay in
'fail'. The management station should query the
'cwapOperStatus' to decide if a reroute request is
successful or not.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.99998.1.1.1.1.7 |
cwapAdminStatusThe 'administrative status' of this party.rw WanPartyAdminStatus .1.3.6.1.4.1.9.9.99998.1.1.1.1.8 |
cwapOperStatusThe 'operational status' of this party.ro WanPartyOperStatus .1.3.6.1.4.1.9.9.99998.1.1.1.1.9 |
cwapIdentifierAn arbitrary integer which serves to
distinguish all parties on a node.
This value is assigned by the managed
system when a party is added.
The use of this variable is implementation specific.ro Unsigned32 .1.3.6.1.4.1.9.9.99998.1.1.1.1.10 |
cwapUploadCounterThis counter is used by the management station to
determine if a party had been modified and requires
further action from management station.
The use of this variable is implementation specific.
This functionality is conventionally achieved by time
stamping using a time-of-day clock. However, in switches
where time-of-day clock is not available, the following
scheme is used:
The upload counter is incremented, when:
* assignment of a party to a cwapIdentifier. This
happens when a party is added and assigned this
cwapIdentifier.
* de-assignment of connection from a cwapIdentifier. This
happens when a connection is deleted.
* When there is a status change done to this party.ro Unsigned32 .1.3.6.1.4.1.9.9.99998.1.1.1.1.11 |
cwapRootPhysicalIdThis object contains physical description of the
physical interface the root resides. The presentation of
this object is implementation specific.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.99998.1.1.1.1.12 |
cwapRowStatusThis object is used to create, modify or delete an entry
in the ciscoWanAtmPartyTable.
* A row may be created using the 'CreateAndGo' option. When
the row is successfully created, the RowStatus would be
set to 'active' by the agent.
* A row may be deleted by setting the RowStatus to 'destroy'.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.99998.1.1.1.1.13 |
ciscoWanAtmPartyMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99998.2 |
ciscoWanAtmPartyMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99998.2.1 |
ciscoWanAtmPartyMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.99998.2.2 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.