The MIB module for Airline Protocol Support.
**************************************************************
* Acronym Definitions *
* *
* ALPS : AirLine Protocol Support *
* AX.25 : Airline X.25 *
* EMTOX : Exchange of Mixed Traffic over X.25 *
* ASCU : Agent Set Control Unit *
* *
**************************************************************
Overview of ALPS (AirLine Protocol Support) MIB
==============================================
MIB description
Document to refer: 'Configuring ALPS' section in Cisco IOS Command
Reference & Configuration Guide.
The ALPS MIB provides configuration and operational information
for Cisco's Airline protocol support for IBM-P1024B(ALC) and
Unisys-P1024C(UTS) protocols encapsulation over TCP/IP. The
following entities are managed:
1. Peers
2. ALPS Circuits
3. ASCUs (Agent Set Control Units)
4. ALC interface
5. ALPS Host link interface to the host
HOST(Emtox/Ax.25) <
router router
The router connected to the Host is called the Central router and the router
connected to the ASCU is called the Remote router. We anticipate one Central
router connecting to a large number of Remote routers. Each router has a
local peer, which connects to its counterpart on the other router (referred
to as the remote peer) via a TCP connection. ALPS circuits are set up over
this TCP connection either on a permanent or on-demand basis.
A logical grouping of ASCUs are connected via a single circuit - this has
no connection to the physical interfaces that the ASCUs are connected to.
The only restriction is that all the ASCUs should be directly connected to
the same router.
Multiple ASCUs can connect to a single serial interface and several terminals
connect to an ASCU. However, terminals are not visible to the ALPS feature
- the router talks only to the ASCUs. An ASCU can be identified by
* the interface it is on and its Interface Address (IA) or
* the circuit it is on, and its A1 and A2 values, which identify it
within the circuit.
Thus there are two ways of identifying an ASCU - or
Circuit names are globally unique.
The connection to the host is via one of two flavors of X.25 - either
AX.25 (for PVCs) or EMTOX (for SVCs). Each X.25 VC corresponds to one ALPS
circuit. There are several hostlinks between a host and the Central router
and load balancing is done across these. EMTOX allows the host to
dial out to a terminal. This requires the use of an X.121 to IP address
translation table to connect to the appropriate remote peer.
Parsed from file CISCO-ALPS-MIB.mib
Module: CISCO-ALPS-MIB
ciscoAlpsMIB MODULE-IDENTITY
LAST-UPDATED "200001280000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
" Cisco Systems
Customer Service
Postal: 170 W. Tasman Drive
San Jose, CA 95134
USA
Tel: +1 800 553-NETS
E-mail: [email protected]"
DESCRIPTION
"The MIB module for Airline Protocol Support.
**************************************************************
* Acronym Definitions *
* *
* ALPS : AirLine Protocol Support *
* AX.25 : Airline X.25 *
* EMTOX : Exchange of Mixed Traffic over X.25 *
* ASCU : Agent Set Control Unit *
* *
**************************************************************
Overview of ALPS (AirLine Protocol Support) MIB
==============================================
MIB description
Document to refer: Configuring ALPS section in Cisco IOS Command
Reference & Configuration Guide.
The ALPS MIB provides configuration and operational information
for Ciscos Airline protocol support for IBM-P1024B(ALC) and
Unisys-P1024C(UTS) protocols encapsulation over TCP/IP. The
following entities are managed:
1. Peers
2. ALPS Circuits
3. ASCUs (Agent Set Control Units)
4. ALC interface
5. ALPS Host link interface to the host
HOST(Emtox/Ax.25) <----> Central <---> IP Network <---> Remote <----> ASCU
router router
The router connected to the Host is called the Central router and the router
connected to the ASCU is called the Remote router. We anticipate one Central
router connecting to a large number of Remote routers. Each router has a
local peer, which connects to its counterpart on the other router (referred
to as the remote peer) via a TCP connection. ALPS circuits are set up over
this TCP connection either on a permanent or on-demand basis.
A logical grouping of ASCUs are connected via a single circuit - this has
no connection to the physical interfaces that the ASCUs are connected to.
The only restriction is that all the ASCUs should be directly connected to
the same router.
Multiple ASCUs can connect to a single serial interface and several terminals
connect to an ASCU. However, terminals are not visible to the ALPS feature
- the router talks only to the ASCUs. An ASCU can be identified by
* the interface it is on and its Interface Address (IA) or
* the circuit it is on, and its A1 and A2 values, which identify it
within the circuit.
Thus there are two ways of identifying an ASCU -
The connection to the host is via one of two flavors of X.25 - either
AX.25 (for PVCs) or EMTOX (for SVCs). Each X.25 VC corresponds to one ALPS
circuit. There are several hostlinks between a host and the Central router
and load balancing is done across these. EMTOX allows the host to
dial out to a terminal. This requires the use of an X.121 to IP address
translation table to connect to the appropriate remote peer."
REVISION "200001280000Z"
DESCRIPTION
"Modification for ALC and Service Message Enhancements"
REVISION "9901070000Z"
DESCRIPTION
"Additional modifications to support ALPS/MATIP.
NOTE: The alpsIfHLinkHostHld object has been updated to
change its range. SMI (RFC2578 section 10.2 Extending an
Information Module: Object Definitons) requires a new object
defined and the old object obsoleted. This is also an
index module which would require the old table to be
obsoleted and a new one created. After review it has been
decided to minimize impacts/disruptions to customer
applications, we are not going to follow the SMI guidlines."
REVISION "9812310000Z"
DESCRIPTION
"Modifications to support ALPS/MATIP."
REVISION "9812080000Z"
DESCRIPTION
"Modifications to allow publishing."
REVISION "9805200000Z"
DESCRIPTION
"Change ranges for some variables and update descriptions."
View at oid-info.com
The MIB module for Airline Protocol Support.
**************************************************************
* Acronym Definitions *
* *
* ALPS : AirLine Protocol Support *
* AX.25 : Airline X.25 *
* EMTOX : Exchange of Mixed Traffic over X.25 *
* ASCU : Agent Set Control Unit *
* *
**************************************************************
Overview of ALPS (AirLine Protocol Support) MIB
==============================================
MIB description
Document to refer: 'Configuring ALPS' section in Cisco IOS Command
Reference & Configuration Guide.
The ALPS MIB provides configuration and operational information
for Cisco's Airline protocol support for IBM-P1024B(ALC) and
Unisys-P1024C(UTS) protocols encapsulation over TCP/IP. The
following entities are managed:
1. Peers
2. ALPS Circuits
3. ASCUs (Agent Set Control Units)
4. ALC interface
5. ALPS Host link interface to the host
HOST(Emtox/Ax.25) <
router router
The router connected to the Host is called the Central router and the router
connected to the ASCU is called the Remote router. We anticipate one Central
router connecting to a large number of Remote routers. Each router has a
local peer, which connects to its counterpart on the other router (referred
to as the remote peer) via a TCP connection. ALPS circuits are set up over
this TCP connection either on a permanent or on-demand basis.
A logical grouping of ASCUs are connected via a single circuit - this has
no connection to the physical interfaces that the ASCUs are connected to.
The only restriction is that all the ASCUs should be directly connected to
the same router.
Multiple ASCUs can connect to a single serial interface and several terminals
connect to an ASCU. However, terminals are not visible to the ALPS feature
- the router talks only to the ASCUs. An ASCU can be identified by
* the interface it is on and its Interface Address (IA) or
* the circuit it is on, and its A1 and A2 values, which identify it
within the circuit.
Thus there are two ways of identifying an ASCU - or
Circuit names are globally unique.
The connection to the host is via one of two flavors of X.25 - either
AX.25 (for PVCs) or EMTOX (for SVCs). Each X.25 VC corresponds to one ALPS
circuit. There are several hostlinks between a host and the Central router
and load balancing is done across these. EMTOX allows the host to
dial out to a terminal. This requires the use of an X.121 to IP address
translation table to connect to the appropriate remote peer.
Parsed from file CISCO-ALPS-MIB.my.txt
Company: None
Module: CISCO-ALPS-MIB
The MIB module for Airline Protocol Support.
**************************************************************
* Acronym Definitions *
* *
* ALPS : AirLine Protocol Support *
* AX.25 : Airline X.25 *
* EMTOX : Exchange of Mixed Traffic over X.25 *
* ASCU : Agent Set Control Unit *
* *
**************************************************************
Overview of ALPS (AirLine Protocol Support) MIB
==============================================
MIB description
Document to refer: 'Configuring ALPS' section in Cisco IOS Command
Reference & Configuration Guide.
The ALPS MIB provides configuration and operational information
for Cisco's Airline protocol support for IBM-P1024B(ALC) and
Unisys-P1024C(UTS) protocols encapsulation over TCP/IP. The
following entities are managed:
1. Peers
2. ALPS Circuits
3. ASCUs (Agent Set Control Units)
4. ALC interface
5. ALPS Host link interface to the host
HOST(Emtox/Ax.25) <
router router
The router connected to the Host is called the Central router and the router
connected to the ASCU is called the Remote router. We anticipate one Central
router connecting to a large number of Remote routers. Each router has a
local peer, which connects to its counterpart on the other router (referred
to as the remote peer) via a TCP connection. ALPS circuits are set up over
this TCP connection either on a permanent or on-demand basis.
A logical grouping of ASCUs are connected via a single circuit - this has
no connection to the physical interfaces that the ASCUs are connected to.
The only restriction is that all the ASCUs should be directly connected to
the same router.
Multiple ASCUs can connect to a single serial interface and several terminals
connect to an ASCU. However, terminals are not visible to the ALPS feature
- the router talks only to the ASCUs. An ASCU can be identified by
* the interface it is on and its Interface Address (IA) or
* the circuit it is on, and its A1 and A2 values, which identify it
within the circuit.
Thus there are two ways of identifying an ASCU - or
Circuit names are globally unique.
The connection to the host is via one of two flavors of X.25 - either
AX.25 (for PVCs) or EMTOX (for SVCs). Each X.25 VC corresponds to one ALPS
circuit. There are several hostlinks between a host and the Central router
and load balancing is done across these. EMTOX allows the host to
dial out to a terminal. This requires the use of an X.121 to IP address
translation table to connect to the appropriate remote peer.
ciscoAlpsMIB MODULE-IDENTITY LAST-UPDATED "200802140000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The MIB module for Airline Protocol Support. ************************************************************** * Acronym Definitions * * * * ALPS : AirLine Protocol Support * * AX.25 : Airline X.25 * * EMTOX : Exchange of Mixed Traffic over X.25 * * ASCU : Agent Set Control Unit * * * ************************************************************** Overview of ALPS (AirLine Protocol Support) MIB ============================================== MIB description Document to refer: 'Configuring ALPS' section in Cisco IOS Command Reference & Configuration Guide. The ALPS MIB provides configuration and operational information for Cisco's Airline protocol support for IBM-P1024B(ALC) and Unisys-P1024C(UTS) protocols encapsulation over TCP/IP. The following entities are managed: 1. Peers 2. ALPS Circuits 3. ASCUs (Agent Set Control Units) 4. ALC interface 5. ALPS Host link interface to the host HOST(Emtox/Ax.25) < router router The router connected to the Host is called the Central router and the router connected to the ASCU is called the Remote router. We anticipate one Central router connecting to a large number of Remote routers. Each router has a local peer, which connects to its counterpart on the other router (referred to as the remote peer) via a TCP connection. ALPS circuits are set up over this TCP connection either on a permanent or on-demand basis. A logical grouping of ASCUs are connected via a single circuit - this has no connection to the physical interfaces that the ASCUs are connected to. The only restriction is that all the ASCUs should be directly connected to the same router. Multiple ASCUs can connect to a single serial interface and several terminals connect to an ASCU. However, terminals are not visible to the ALPS feature - the router talks only to the ASCUs. An ASCU can be identified by * the interface it is on and its Interface Address (IA) or * the circuit it is on, and its A1 and A2 values, which identify it within the circuit. Thus there are two ways of identifying an ASCU - or Circuit names are globally unique. The connection to the host is via one of two flavors of X.25 - either AX.25 (for PVCs) or EMTOX (for SVCs). Each X.25 VC corresponds to one ALPS circuit. There are several hostlinks between a host and the Central router and load balancing is done across these. EMTOX allows the host to dial out to a terminal. This requires the use of an X.121 to IP address translation table to connect to the appropriate remote peer." REVISION "200802140000Z" DESCRIPTION "Imported X121Adress from RFC1382 MIB & Integer32 from SNMPv2-SMI. TEXTUAL-CONVENTION AlpsCktName syntax is changed to OCTET STRING from DisplayString & AlpsAscuA1A2Value's Syntax is changed to Integer32 from INTEGER. Syntax of following objects are changed from INTEGER to Integer32: alpsPeerLocalAtpPort, alpsPeerKeepaliveMaxRetries, alpsRemPeerLocalPort, alpsRemPeerRemotePort, alpsRemPeerTCPQlen, alpsRemPeerCfgTCPQLen, alpsRemPeerCfgStatRetry, alpsRemPeerConnLocalPort, alpsRemPeerConnForeignPort, alpsRemPeerConnNumActCirc, alpsRemPeerConnTCPQLen, alpsRemPeerConnStatIntvl, alpsRemPeerConnStatRetry, alpsCktBaseNumActiveAscus, alpsCktBaseHostLinkNumber, alpsCktBaseRemHld, alpsCktBaseLocalHld, alpsCktX25LCN, alpsCktP1024Ax25LCN, alpsCktP1024WinOut, alpsCktP1024WinIn, alpsCktP1024OutPktSize, alpsCktP1024InPktSize, alpsCktP1024SvcMsgList, alpsCktAscuId, alpsIfP1024MaxErrCnt, alpsIfP1024MaxRetrans, alpsIfP1024CurrErrCnt, alpsIfP1024MinGoodPollResp, alpsIfP1024PollingRatio, alpsIfHLinkHostHld, alpsIfHLinkNumber, alpsIfHLinkActiveCkts, alpsAscuId, alpsAscuMaxMsgLength, alpsSvcMsgListNum and alpsSvcMsgNum." REVISION "200001280000Z" DESCRIPTION "Modification for ALC and Service Message Enhancements" REVISION "9901070000Z" DESCRIPTION "Additional modifications to support ALPS/MATIP. NOTE: The alpsIfHLinkHostHld object has been updated to change its range. SMI (RFC2578 section 10.2 Extending an Information Module: Object Definitons) requires a new object defined and the old object obsoleted. This is also an index module which would require the old table to be obsoleted and a new one created. After review it has been decided to minimize impacts/disruptions to customer applications, we are not going to follow the SMI guidlines." REVISION "9812310000Z" DESCRIPTION "Modifications to support ALPS/MATIP." REVISION "9812080000Z" DESCRIPTION "Modifications to allow publishing." REVISION "9805200000Z" DESCRIPTION "Change ranges for some variables and update descriptions." ::= { ciscoMgmt 95 }
ciscoAlpsMIB OBJECT IDENTIFIER ::= { ciscoMgmt 95 }
Automatically extracted from Cisco "SNMP v2 MIBs".
ciscoAlpsMIB MODULE-IDENTITY LAST-UPDATED "200802140000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The MIB module for Airline Protocol Support. ************************************************************** * Acronym Definitions * * * * ALPS : AirLine Protocol Support * * AX.25 : Airline X.25 * * EMTOX : Exchange of Mixed Traffic over X.25 * * ASCU : Agent Set Control Unit * * * ************************************************************** Overview of ALPS (AirLine Protocol Support) MIB ============================================== MIB description Document to refer: 'Configuring ALPS' section in Cisco IOS Command Reference & Configuration Guide. The ALPS MIB provides configuration and operational information for Cisco's Airline protocol support for IBM-P1024B(ALC) and Unisys-P1024C(UTS) protocols encapsulation over TCP/IP. The following entities are managed: 1. Peers 2. ALPS Circuits 3. ASCUs (Agent Set Control Units) 4. ALC interface 5. ALPS Host link interface to the host HOST(Emtox/Ax.25) < router router The router connected to the Host is called the Central router and the router connected to the ASCU is called the Remote router. We anticipate one Central router connecting to a large number of Remote routers. Each router has a local peer, which connects to its counterpart on the other router (referred to as the remote peer) via a TCP connection. ALPS circuits are set up over this TCP connection either on a permanent or on-demand basis. A logical grouping of ASCUs are connected via a single circuit - this has no connection to the physical interfaces that the ASCUs are connected to. The only restriction is that all the ASCUs should be directly connected to the same router. Multiple ASCUs can connect to a single serial interface and several terminals connect to an ASCU. However, terminals are not visible to the ALPS feature - the router talks only to the ASCUs. An ASCU can be identified by * the interface it is on and its Interface Address (IA) or * the circuit it is on, and its A1 and A2 values, which identify it within the circuit. Thus there are two ways of identifying an ASCU - or Circuit names are globally unique. The connection to the host is via one of two flavors of X.25 - either AX.25 (for PVCs) or EMTOX (for SVCs). Each X.25 VC corresponds to one ALPS circuit. There are several hostlinks between a host and the Central router and load balancing is done across these. EMTOX allows the host to dial out to a terminal. This requires the use of an X.121 to IP address translation table to connect to the appropriate remote peer." REVISION "200802140000Z" DESCRIPTION "Imported X121Adress from RFC1382 MIB & Integer32 from SNMPv2-SMI. TEXTUAL-CONVENTION AlpsCktName syntax is changed to OCTET STRING from DisplayString & AlpsAscuA1A2Value's Syntax is changed to Integer32 from INTEGER. Syntax of following objects are changed from INTEGER to Integer32: alpsPeerLocalAtpPort, alpsPeerKeepaliveMaxRetries, alpsRemPeerLocalPort, alpsRemPeerRemotePort, alpsRemPeerTCPQlen, alpsRemPeerCfgTCPQLen, alpsRemPeerCfgStatRetry, alpsRemPeerConnLocalPort, alpsRemPeerConnForeignPort, alpsRemPeerConnNumActCirc, alpsRemPeerConnTCPQLen, alpsRemPeerConnStatIntvl, alpsRemPeerConnStatRetry, alpsCktBaseNumActiveAscus, alpsCktBaseHostLinkNumber, alpsCktBaseRemHld, alpsCktBaseLocalHld, alpsCktX25LCN, alpsCktP1024Ax25LCN, alpsCktP1024WinOut, alpsCktP1024WinIn, alpsCktP1024OutPktSize, alpsCktP1024InPktSize, alpsCktP1024SvcMsgList, alpsCktAscuId, alpsIfP1024MaxErrCnt, alpsIfP1024MaxRetrans, alpsIfP1024CurrErrCnt, alpsIfP1024MinGoodPollResp, alpsIfP1024PollingRatio, alpsIfHLinkHostHld, alpsIfHLinkNumber, alpsIfHLinkActiveCkts, alpsAscuId, alpsAscuMaxMsgLength, alpsSvcMsgListNum and alpsSvcMsgNum." REVISION "200001280000Z" DESCRIPTION "Modification for ALC and Service Message Enhancements" REVISION "9901070000Z" DESCRIPTION "Additional modifications to support ALPS/MATIP. NOTE: The alpsIfHLinkHostHld object has been updated to change its range. SMI (RFC2578 section 10.2 Extending an Information Module: Object Definitons) requires a new object defined and the old object obsoleted. This is also an index module which would require the old table to be obsoleted and a new one created. After review it has been decided to minimize impacts/disruptions to customer applications, we are not going to follow the SMI guidlines." REVISION "9812310000Z" DESCRIPTION "Modifications to support ALPS/MATIP." REVISION "9812080000Z" DESCRIPTION "Modifications to allow publishing." REVISION "9805200000Z" DESCRIPTION "Change ranges for some variables and update descriptions." ::= { ciscoMgmt 95 }
ciscoAlpsMIB MODULE-IDENTITY LAST-UPDATED "200802140000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The MIB module for Airline Protocol Support. ************************************************************** * Acronym Definitions * * * * ALPS : AirLine Protocol Support * * AX.25 : Airline X.25 * * EMTOX : Exchange of Mixed Traffic over X.25 * * ASCU : Agent Set Control Unit * * * ************************************************************** Overview of ALPS (AirLine Protocol Support) MIB ============================================== MIB description Document to refer: 'Configuring ALPS' section in Cisco IOS Command Reference & Configuration Guide. The ALPS MIB provides configuration and operational information for Cisco's Airline protocol support for IBM-P1024B(ALC) and Unisys-P1024C(UTS) protocols encapsulation over TCP/IP. The following entities are managed: 1. Peers 2. ALPS Circuits 3. ASCUs (Agent Set Control Units) 4. ALC interface 5. ALPS Host link interface to the host HOST(Emtox/Ax.25) < router router The router connected to the Host is called the Central router and the router connected to the ASCU is called the Remote router. We anticipate one Central router connecting to a large number of Remote routers. Each router has a local peer, which connects to its counterpart on the other router (referred to as the remote peer) via a TCP connection. ALPS circuits are set up over this TCP connection either on a permanent or on-demand basis. A logical grouping of ASCUs are connected via a single circuit - this has no connection to the physical interfaces that the ASCUs are connected to. The only restriction is that all the ASCUs should be directly connected to the same router. Multiple ASCUs can connect to a single serial interface and several terminals connect to an ASCU. However, terminals are not visible to the ALPS feature - the router talks only to the ASCUs. An ASCU can be identified by * the interface it is on and its Interface Address (IA) or * the circuit it is on, and its A1 and A2 values, which identify it within the circuit. Thus there are two ways of identifying an ASCU - or Circuit names are globally unique. The connection to the host is via one of two flavors of X.25 - either AX.25 (for PVCs) or EMTOX (for SVCs). Each X.25 VC corresponds to one ALPS circuit. There are several hostlinks between a host and the Central router and load balancing is done across these. EMTOX allows the host to dial out to a terminal. This requires the use of an X.121 to IP address translation table to connect to the appropriate remote peer." REVISION "200802140000Z" DESCRIPTION "Imported X121Adress from RFC1382 MIB & Integer32 from SNMPv2-SMI. TEXTUAL-CONVENTION AlpsCktName syntax is changed to OCTET STRING from DisplayString & AlpsAscuA1A2Value's Syntax is changed to Integer32 from INTEGER. Syntax of following objects are changed from INTEGER to Integer32: alpsPeerLocalAtpPort, alpsPeerKeepaliveMaxRetries, alpsRemPeerLocalPort, alpsRemPeerRemotePort, alpsRemPeerTCPQlen, alpsRemPeerCfgTCPQLen, alpsRemPeerCfgStatRetry, alpsRemPeerConnLocalPort, alpsRemPeerConnForeignPort, alpsRemPeerConnNumActCirc, alpsRemPeerConnTCPQLen, alpsRemPeerConnStatIntvl, alpsRemPeerConnStatRetry, alpsCktBaseNumActiveAscus, alpsCktBaseHostLinkNumber, alpsCktBaseRemHld, alpsCktBaseLocalHld, alpsCktX25LCN, alpsCktP1024Ax25LCN, alpsCktP1024WinOut, alpsCktP1024WinIn, alpsCktP1024OutPktSize, alpsCktP1024InPktSize, alpsCktP1024SvcMsgList, alpsCktAscuId, alpsIfP1024MaxErrCnt, alpsIfP1024MaxRetrans, alpsIfP1024CurrErrCnt, alpsIfP1024MinGoodPollResp, alpsIfP1024PollingRatio, alpsIfHLinkHostHld, alpsIfHLinkNumber, alpsIfHLinkActiveCkts, alpsAscuId, alpsAscuMaxMsgLength, alpsSvcMsgListNum and alpsSvcMsgNum." REVISION "200001280000Z" DESCRIPTION "Modification for ALC and Service Message Enhancements" REVISION "9901070000Z" DESCRIPTION "Additional modifications to support ALPS/MATIP. NOTE: The alpsIfHLinkHostHld object has been updated to change its range. SMI (RFC2578 section 10.2 Extending an Information Module: Object Definitons) requires a new object defined and the old object obsoleted. This is also an index module which would require the old table to be obsoleted and a new one created. After review it has been decided to minimize impacts/disruptions to customer applications, we are not going to follow the SMI guidlines." REVISION "9812310000Z" DESCRIPTION "Modifications to support ALPS/MATIP." REVISION "9812080000Z" DESCRIPTION "Modifications to allow publishing." REVISION "9805200000Z" DESCRIPTION "Change ranges for some variables and update descriptions." ::= { ciscoMgmt 95 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.95.1 | ciscoAlpsMIBObjects | 6 | 194 | None |
| 1.3.6.1.4.1.9.9.95.2 | ciscoAlpsMIBNotificationPrefix | 1 | 7 | None |
| 1.3.6.1.4.1.9.9.95.3 | alpsMibConformance | 2 | 18 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.45 | ciscoAtmIfPhysMIB | 2 | 39 | A minimal set of managed objects for tracking the status of DS3/E3/DS1/E1 and SONET interfaces. |
| 1.3.6.1.4.1.9.9.46 | ciscoVtpMIB | 3 | 261 | The MIB module for entities implementing the VTP protocol and Vlan management. |
| 1.3.6.1.4.1.9.9.47 | ciscoModemMgmtMIB | 3 | 112 | This MIB module provides modem call related data for tracking the progress and status of a call. |
| 1.3.6.1.4.1.9.9.48 | ciscoMemoryPoolMIB | 3 | 32 | MIB module for monitoring memory pools |
| 1.3.6.1.4.1.9.9.49 | ciscoFrameRelayMIB | 2 | 158 | Cisco Frame Relay MIB |
| 1.3.6.1.4.1.9.9.50 | ciscoAtmServiceRegistryMIB | 2 | 14 | A MIB module to allow an NMS to monitor and configure the information which an ATM switch makes available via the ILMI's Service … |
| 1.3.6.1.4.1.9.9.51 | ciscoAtmSwAddrMIB | 2 | 11 | ATM Switch address MIB |
| 1.3.6.1.4.1.9.9.52 | ciscoIpEncryptionMIB | 3 | 51 | Used to manage the encryption feature. |
| 1.3.6.1.4.1.9.9.53 | ciscoVmpsMIB | 3 | 55 | The MIB module for the management of the VLAN Membership Policy Server. |
| 1.3.6.1.4.1.9.9.54 | ciscoTn3270ServerMIB | 3 | 105 | The MIB module for TN3270 Server. MIB description The PU and LU MIB are defined in RFC 1666. This MIB provides additional informa… |
| 1.3.6.1.4.1.9.9.55 | ciscoAsppMIB | 2 | 29 | The ASPP MIB provides the configuration and operational information on asynchronous polled protocols such as the asynchronous sec… |
| 1.3.6.1.4.1.9.9.56 | ciscoVlanBridgingMIB | 2 | 13 | A set of managed objects for optimizing access to bridging related data from RFC 1493. This MIB is modeled after portions of RFC… |
| 1.3.6.1.4.1.9.9.57 | ciscoCompressionServiceAdapterMIB | 2 | 19 | Used to manage the compression service adapter. |
| 1.3.6.1.4.1.9.9.59 | ciscoStackMakerMIB | 2 | 15 | The MIB module for Cisco Systems' StackMaker. |
| 1.3.6.1.4.1.9.9.60 | ciscoAtmDualPhyMIB | 3 | 26 | Initial version of this MIB module. Phy definition Throughout this document phy is used as an abbreviation for Physical Interface.… |
| 1.3.6.1.4.1.9.9.61 | ciscoAccessEnvMonMIB | 3 | 13 | The MIB module to describe the additional status of the Environmental Monitor on those Cisco Access devices which support one. |
| 1.3.6.1.4.1.9.9.62 | ciscoVoiceAnalogIfMIB | 2 | 90 | Analog Voice Interface MIB module. This MIB manages the E&M, FXO, FXS Interfaces in the router. |
| 1.3.6.1.4.1.9.9.63 | ciscoVoiceDialControlMIB | 3 | 377 | This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing management of voice telephony peers on both a circuit-s… |
| 1.3.6.1.4.1.9.9.64 | ciscoVoiceInterfaceMIB | 2 | 24 | Common Voice Interface MIB module. The MIB module manages the common voice related parameters for both voice analog and ISDN inte… |
| 1.3.6.1.4.1.9.9.65 | ciscoPnniMIB | 2 | 49 | The MIB module for managing Cisco specific extensions to the ATM Forum PNNI MIB. |
| 1.3.6.1.4.1.9.9.66 | ciscoAal5MIB | 2 | 25 | Cisco Enterprise AAL5 MIB file that provide AAL5 specific information that are either excluded by RFC 1695 or specific to Cisco p… |
| 1.3.6.1.4.1.9.9.67 | ciscoAtmAccessListMIB | 2 | 39 | A cisco ATM access list mib module. |
| 1.3.6.1.4.1.9.9.68 | ciscoVlanMembershipMIB | 3 | 90 | The MIB module for the management of the VLAN Membership within the frame work of Cisco VLAN Architecture, v 2.0 by Keith McClog… |
| 1.3.6.1.4.1.9.9.69 | ciscoLecDataVccMIB | 3 | 13 | This MIB module is a Cisco extension to the ATM Forum's LANE Client MIB. This extension identifies those VCCs which are being us… |
| 1.3.6.1.4.1.9.9.72 | ciscoCipCmpcMIB | 3 | 46 | This is the Management Information Base (MIB) module for objects used to manage the Cisco Multi-Path Channel (MPC) support on Cis… |
| 1.3.6.1.4.1.9.9.73 | ciscoCipTgMIB | 2 | 98 | This is the Management Information Base (MIB) module for objects used to manage Transmission Groups (TGs) in Cisco Mainframe Chan… |
| 1.3.6.1.4.1.9.9.74 | ciscoDlswExtMIB | 3 | 134 | The MIB module for management of Cisco specific Data Link Switching protocol enhancements. DLSw is described in RFC 1795 and RFC… |
| 1.3.6.1.4.1.9.9.76 | ciscoDlcSwitchMIB | 2 | 55 | This is the MIB module for objects used to manage FRAS sessions to the endstation. These objects are specific to downstream or end… |
| 1.3.6.1.4.1.9.9.77 | ciscoLecExtMIB | 3 | 12 | This MIB module is a Cisco extension to the ATM Forum's LANE Client MIB. |
| 1.3.6.1.4.1.9.9.78 | ciscoAtmSigDiagMIB | 2 | 58 | The MIB module to facilitate the diagnosis of failures of ATM Signalling requests. Through this MIB, an ATM device retains infor… |
| 1.3.6.1.4.1.9.9.80 | ciscoFtpClientMIB | 2 | 29 | The MIB module for invoking Internet File Transfer Protocol (FTP) operations for network management purposes. |
| 1.3.6.1.4.1.9.9.81 | ciscoBulkFileMIB | 3 | 63 | The MIB module for creating and deleting bulk files of SNMP data for file transfer. |
| 1.3.6.1.4.1.9.9.82 | ciscoStpExtensionsMIB | 3 | 300 | The MIB module for managing Cisco extensions to the 802.1D Spanning Tree Protocol (STP). |
| 1.3.6.1.4.1.9.9.83 | ciscoWredMIB | 2 | 26 | Cisco WRED MIB - Overview Cisco Weighted Random Early Detection/Drop is a method which avoids traffic congestion on an output int… |
| 1.3.6.1.4.1.9.9.84 | ciscoIpStatMIB | 2 | 34 | Cisco IP Statistics MIB - Overview This MIB incorporates objects to provide support for the Cisco IP statistics as implemented in… |
| 1.3.6.1.4.1.9.9.85 | ciscoCasIfMIB | 2 | 119 | Channel Associated Signal Interface MIB module. This MIB manages the generic CAS (Channel Associated Signal)or DS0 clear channel … |
| 1.3.6.1.4.1.9.9.86 | ciscoDspMgmtMIB | 4 | 141 | ciscoDspMgmtMIB MODULE-IDENTITY LAST-UPDATED "200008140000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cu… |
| 1.3.6.1.4.1.9.9.87 | ciscoC2900MIB | 3 | 133 | The MIB module for Catalyst 2900 enterprise specific information |
| 1.3.6.1.4.1.9.9.88 | ciscoAtmExtMIB | 3 | 50 | ciscoAtmExtMIB MODULE-IDENTITY LAST-UPDATED "9706200000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custo… |
| 1.3.6.1.4.1.9.9.89 | csCugMIB | 2 | 24 | This MIB module is for closed user group support (virtual private networks). |
| 1.3.6.1.4.1.9.9.91 | entitySensorMIB, ciscoEntitySensorMIB | 3 | 42 | The CISCO-ENTITY-SENSOR-MIB is used to monitor the values of sensors in the Entity-MIB (RFC 2037) entPhysicalTable. |
| 1.3.6.1.4.1.9.9.92 | ciscoEntityAssetMIB | 3 | 29 | Monitor the asset information of items in the ENTITY-MIB (RFC 2037) entPhysical table. |
| 1.3.6.1.4.1.9.9.94 | ciscoAtmPvcMIB | 2 | 19 | PVC's (Permanent Virtual Channel) can carry bridged PDUs (BPDUs) using the encapsulation method detailed in RFC1483. This is an alt… |
| 1.3.6.1.4.1.9.9.96 | ciscoConfigCopyMIB | 3 | 40 | This MIB facilitates writing of configuration files of an SNMP Agent running Cisco's IOS in the following ways: to and from the n… |
| 1.3.6.1.4.1.9.9.97 | ciscoSwitchEngineMIB | 3 | 385 | This MIB module defines management objects for Cisco Layer 2/3 switches. These devices may either have a single (central) switch… |
| 1.3.6.1.4.1.9.9.98 | ciscoPagpMIB | 2 | 52 | The MIB module for configuration of Fast Etherchannel and the operation of the Port Aggregation Protocol (PAgP). These features a… |
| 1.3.6.1.4.1.9.9.99 | ciscoLocalDirectorMIB | 3 | 88 | The MIB module to view information about LocalDirector. The Cisco LocalDirector is a device designed for the purpose of load balan… |
| 1.3.6.1.4.1.9.9.101 | ciscoSwitchCgmpMIB | 2 | 18 | Switch-side Cisco Group Management Protocol MIB for Layer 2 Switch devices. |
| 1.3.6.1.4.1.9.9.102 | ciscoMediaMailDialControlMIB | 2 | 63 | This MIB module enhances the IETF Dial Control MIB (RFC2128) for providing management of dial peers on both a circuit-switched te… |
| 1.3.6.1.4.1.9.9.103 | ciscoRmonConfigMIB | 3 | 123 | This module defines configuration extensions for some of the IETF RMON MIBs. The following terms are used throughout this MIB: A S… |
| 1.3.6.1.4.1.9.9.105 | ciscoC8500RedundancyMIB | 3 | 49 | This MIB allows management of redundancy of CPU and switch cards for the Catalyst 8540 switch, and other products with similar im… |
| 1.3.6.1.4.1.9.9.106 | ciscoHsrpMIB | 3 | 38 | ciscoHsrpMIB MODULE-IDENTITY LAST-UPDATED "9808030000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custome… |
| 1.3.6.1.4.1.9.9.107 | ciscoHsrpExtMIB | 2 | 36 | ciscoHsrpExtMIB MODULE-IDENTITY LAST-UPDATED "9808030000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cust… |
| 1.3.6.1.4.1.9.9.109 | ciscoProcessMIB | 3 | 187 | The MIB module to describe active system processes. |
| 1.3.6.1.4.1.9.9.110 | ciscoAtmSwitchFrRmMIB | 3 | 30 | This MIB module describes a set of objects used for switch Resource Management (RM) for Frame Relay/Frame based User-to-Network (… |
| 1.3.6.1.4.1.9.9.112 | ciscoAtmSwitchFrIwfMIB | 2 | 109 | A MIB module for managing Frame Relay to ATM interworking connections, and Frame Relay to Frame Relay switched connections via an… |
| 1.3.6.1.4.1.9.9.113 | ciscoCarMIB | 2 | 36 | Cisco CAR MIB - Overview Cisco Weighted Rate-limit, known as Commited Access Rate (CAR), is a traffic control method which uses a… |
| 1.3.6.1.4.1.9.9.114 | ciscoCableSpectrumMIB | 3 | 162 | This is the MIB Module for Cable Spectrum Management for DOCSIS-compliant Cable Modem Termination Systems (CMTS). Spectrum manage… |
| 1.3.6.1.4.1.9.9.115 | ciscoCasaFaMIB | 3 | 78 | This MIB module in conjunction with the CISCO-CASA-MIB, defines the SNMP management information base for managing the Cisco Appli… |
| 1.3.6.1.4.1.9.9.116 | ciscoDocsExtMIB | 3 | 235 | This is the MIB module for the Cisco specific extension objects of Data Over Cable Service, Radio Frequency interface. There is … |
| 1.3.6.1.4.1.9.9.117 | ciscoEntityFRUControlMIB | 3 | 147 | The CISCO-ENTITY-FRU-CONTROL-MIB is used to monitor and configure operational status of Field Replaceable Units (FRUs) and other … |
| 1.3.6.1.4.1.9.9.118 | ciscoUdldpMIB | 3 | 51 | Cisco Uni Direction Link Detection Protocol MIB |
| 1.3.6.1.4.1.9.9.120 | ciscoNetworkRegistrarMIB | 3 | 125 | MIB for Cisco Network Registrar (CNR). |
| 1.3.6.1.4.1.9.9.121 | ciscoAtmNetworkClockMIB | 3 | 53 | The MIB module for management of network clock distribution and the Network Clock Distribution Protocol (NCDP) in Cisco de… |
| 1.3.6.1.4.1.9.9.122 | ciscoCasaMIB | 3 | 78 | This MIB contains the basic objects for managing a Cisco Appliance Services Architecture (CASA) Entity. A CASA Entity can be a Ma… |
| 1.3.6.1.4.1.9.9.124 | ciscoCallResourcePoolMIB | 3 | 114 | The MIB module for call resource pool management. This MIB supports the resource pool manager feature of CISCO IOS. This feature … |
| 1.3.6.1.4.1.9.9.125 | ciscoWANRsrcPartMIB | 2 | 55 | The MIB module to manage resource partition objects. A resource partition is configured on a virtual interface (ifType value atmV… |
| 1.3.6.1.4.1.9.9.126 | ciscoSonetMIB | 3 | 136 | The MIB module to describe SONET/SDH interfaces objects. This is an extension to the standard SONET MIB(RFC 2558). |
| 1.3.6.1.4.1.9.9.128 | ciscoVlanIfTableRelationshipMIB | 1 | 12 | ciscoVlanIftableRelationshipMIB |
| 1.3.6.1.4.1.9.9.129 | ciscoAtmVirtualIfMIB | 2 | 139 | The MIB module to manage ATM Virtual interface objects. ATM virtual interfaces are configured on a physical line. |
| 1.3.6.1.4.1.9.9.130 | ciscoAdslDmtLineMIB | 3 | 72 | This MIB module serves as an enterprise-specific extension of the ADSL-LINE-MIB. The structure of this MIB module shadows the st… |
| 1.3.6.1.4.1.9.9.131 | ciscoSystemMIB | 3 | 57 | The systemGroup (see RFC 1907) provides a standard set of basic system information. This MIB module contains Cisco-defined exten… |
| 1.3.6.1.4.1.9.9.132 | ciscoDs3MIB | 2 | 140 | The MIB module to describe DS3 line objects. This is an extension to the standard DS3 MIB(RFC 2496). |
| 1.3.6.1.4.1.9.9.133 | ciscoAtmCellLayerMIB | 1 | 138 | The MIB module to describe ATM cell layer objects and statistics of a physical line. |
| 1.3.6.1.4.1.9.9.134 | ciscoClusterMIB | 3 | 49 | The MIB module for the management of a group of devices called a 'cluster'. A cluster comprises: 1. A command switch, which is a… |
| 1.3.6.1.4.1.9.9.135 | ciscoWirelessP2pBpiMIB | 3 | 66 | This is the MIB Module for the Baseline Privacy Interface (BPI) at Point to Point Wireless Radio Card. This is a specialization o… |
| 1.3.6.1.4.1.9.9.136 | ciscoWirelessIfMIB | 3 | 307 | This is the MIB Module for the Cisco Wireless Radio Point to Point interface specification. I) Relationship of the Cisco Wireless… |
| 1.3.6.1.4.1.9.9.137 | ciscoWirelessTextualConventions | 0 | 0 | This module defines textual conventions used in Cisco Wireless MIBs. |
| 1.3.6.1.4.1.9.9.138 | ciscoEntityAlarmMIB | 3 | 66 | This MIB module defines the managed objects that support the monitoring of alarms generated by physical entities contained by the… |
| 1.3.6.1.4.1.9.9.139 | ciscoEntityProvMIB | 3 | 13 | This MIB module defines the objects that support provisioning of 'container' class physical entities. Provisioning sets up a 'co… |
| 1.3.6.1.4.1.9.9.140 | ciscoCopsClientMIB | 3 | 43 | This MIB module is for configuration & statistic query of Common Open Policy Service(COPS) client feature on the Cisco device. C… |
| 1.3.6.1.4.1.9.9.141 | ciscoVSIControllerMIB | 2 | 21 | This MIB module is used for configuring ATM Capable Switch to be aware of VSI Controller information. Terminolgies used: VSI … |
| 1.3.6.1.4.1.9.9.144 | ciscoTransactionConnectionMIB | 2 | 66 | The MIB module for retrieving Cisco Transaction Connection configuration and status. Cisco Transaction Connection routes transac… |
| 1.3.6.1.4.1.9.9.145 | ciscoWanModuleMIB | 3 | 32 | The MIB to configure Connection Specific parameters and statistics related information in a Service Module. The Service Module(SM… |
| ... | ||||