CISCO-WAN-ATM-PARTY-MIB.mib object view, vendor cisco

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-WAN-ATM-PARTY-MIB and use it to monitor vendor specific OID's.

CISCO-WAN-ATM-PARTY-MIB file content

Object view of CISCO-WAN-ATM-PARTY-MIB:

Scalar Object
cwapConfigEntry	.1.3.6.1.4.1.9.9.99998.1.1.1.1
An 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)).
Tabular Object
cwapRootVpi	.1.3.6.1.4.1.9.9.99998.1.1.1.1.1
This object identifies the Virtual Path Identifier(VPI) of the root endpoint this party is associated with.
cwapRootVci	.1.3.6.1.4.1.9.9.99998.1.1.1.1.2
This object identifies the Virtual Channel Identifier (VCI) of the root endpoint this party is associated with.
cwapReference	.1.3.6.1.4.1.9.9.99998.1.1.1.1.3
An arbitrary integer which serves to distinguish between the multiple parties attached to a root of a point-to-multipoint SPVC.
cwapNSAPAddress	.1.3.6.1.4.1.9.9.99998.1.1.1.1.4
The ATM NSAP address of this party.
cwapVpi	.1.3.6.1.4.1.9.9.99998.1.1.1.1.5
The VPI value of this party.
cwapVci	.1.3.6.1.4.1.9.9.99998.1.1.1.1.6
The VCI value of this party.
cwapReroute	.1.3.6.1.4.1.9.9.99998.1.1.1.1.7
The 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.
cwapAdminStatus	.1.3.6.1.4.1.9.9.99998.1.1.1.1.8
The 'administrative status' of this party.
cwapOperStatus	.1.3.6.1.4.1.9.9.99998.1.1.1.1.9
The 'operational status' of this party.
cwapIdentifier	.1.3.6.1.4.1.9.9.99998.1.1.1.1.10
An 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.
cwapUploadCounter	.1.3.6.1.4.1.9.9.99998.1.1.1.1.11
This 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.
cwapRootPhysicalId	.1.3.6.1.4.1.9.9.99998.1.1.1.1.12
This object contains physical description of the physical interface the root resides. The presentation of this object is implementation specific.
cwapRowStatus	.1.3.6.1.4.1.9.9.99998.1.1.1.1.13
This 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'.
Table
cwapConfigTable	.1.3.6.1.4.1.9.9.99998.1.1.1
This table contains mandatory 'party' configuration for all ATM point-to-multipoint Soft Permanent Virtual Channel Connections (SPVC).
Object Identifier
ciscoWanAtmPartyMIB	.1.3.6.1.4.1.9.9.99998
A 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
ciscoWanAtmPartyMIBNotifs	.1.3.6.1.4.1.9.9.99998.0
ciscoWanAtmPartyMIBObjects	.1.3.6.1.4.1.9.9.99998.1
cwapConfig	.1.3.6.1.4.1.9.9.99998.1.1
ciscoWanAtmPartyMIBConform	.1.3.6.1.4.1.9.9.99998.2
ciscoWanAtmPartyMIBCompliances	.1.3.6.1.4.1.9.9.99998.2.1
ciscoWanAtmPartyMIBGroups	.1.3.6.1.4.1.9.9.99998.2.2
Group
ciscoWanAtmPartyGroup	.1.3.6.1.4.1.9.9.99998.2.2.2
This group contains the information of a 'party' per each SPVC point-to-multipoint connection.