mirror/librenms-librenms
1
0
Fork 0
mirror of https://github.com/librenms/librenms.git synced 2024-10-07 16:52:45 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #1436 from paulgear/cisco-mibs-20150711

Browse Source 
Cisco MIBs 20150711
This commit is contained in:
Daniel Preussker
2015-07-11 10:34:38 +02:00
parent 4106d01a30 23b0076209
commit 9cdbdd17c1
4 changed files with 3795 additions and 238 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mibs/CISCO-LWAPP-DOT11-CLIENT-MIB
+426
View File
@@ -0,0 +1,426 @@
-- *******************************************************************
-- CISCO-LWAPP-DOT11-CLIENT-MIB.my: Dot11 Wireless Clients MIB
--
-- June 2006, Devesh Pujari, Srinath Candadai
--
-- Copyright (c) 2006 by Cisco Systems, Inc.
-- All rights reserved.
-- *******************************************************************
CISCO-LWAPP-DOT11-CLIENT-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
NOTIFICATION-TYPE
FROM SNMPv2-SMI
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF
TruthValue,
MacAddress
FROM SNMPv2-TC
ciscoMgmt
FROM CISCO-SMI
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
CLApIfType,
CLDot11ClientStatus
FROM CISCO-LWAPP-TC-MIB;
-- ********************************************************************
-- * MODULE IDENTITY
-- ********************************************************************
ciscoLwappDot11ClientMIB MODULE-IDENTITY
LAST-UPDATED "200611210000Z"
ORGANIZATION "Cisco Systems Inc."
CONTACT-INFO
"Cisco Systems,
Customer Service
Postal: 170 West Tasman Drive
San Jose, CA 95134
USA
Tel: +1 800 553-NETS
Email: [email protected]"
DESCRIPTION
"This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Access Point Protocol
tunnel from Cisco Light-weight LWAPP Access Points.
Information provided by this MIB is about the
configuration and monitoring of 802.11 wireless
clients in the network.
The relationship between CC and the LWAPP APs
can be depicted as follows:
+......+ +......+ +......+ +......+
+ + + + + + + +
+ CC + + CC + + CC + + CC +
+ + + + + + + +
+......+ +......+ +......+ +......+
.. . . .
.. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ AP + + AP + + AP + + AP + + AP +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ MN + + MN + + MN + + MN + + MN +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
The LWAPP tunnel exists between the controller and
the APs. The MNs communicate with the APs through
the protocol defined by the 802.11 standard.
LWAPP APs, upon bootup, discover and join one of the
controllers and the controller pushes the configuration,
that includes the WLAN parameters, to the LWAPP APs.
The APs then encapsulate all the 802.11 frames from
wireless clients inside LWAPP frames and forward
the LWAPP frames to the controller.
GLOSSARY
Access Point ( AP )
An entity that contains an 802.11 medium access
control ( MAC ) and physical layer ( PHY ) interface
and provides access to the distribution services via
the wireless medium for associated clients.
LWAPP APs encapsulate all the 802.11 frames in
LWAPP frames and sends them to the controller to which
it is logically connected.
Light Weight Access Point Protocol ( LWAPP )
This is a generic protocol that defines the
communication between the Access Points and the
Central Controller.
Mobile Node ( MN )
A roaming 802.11 wireless device in a wireless
network associated with an access point. Mobile Node,
Mobile Station(Ms) and client are used
interchangeably.
Wireless local-area network ( WLAN )
A local-area network that uses high-frequency radio
waves rather than wires to communicate between nodes.
Workgroup Bridge ( WGB )
A WGB can provide a wireless infrastructure connection
for a Ethernet-enabled devices. Devices that do not have
a wireless client adapter in order to connect to the
wireless network can be connected to a WGB through
Ethernet port.
REFERENCE
[1] Wireless LAN Medium Access Control ( MAC ) and
Physical Layer ( PHY ) Specifications
[2] Draft-obara-capwap-lwapp-00.txt, IETF Light
Weight Access Point Protocol "
REVISION "200611210000Z"
DESCRIPTION
"Initial version of this MIB module."
::= { ciscoMgmt 599 }
ciscoLwappDot11ClientMIBNotifs OBJECT IDENTIFIER
::= { ciscoLwappDot11ClientMIB 0 }
ciscoLwappDot11ClientMIBObjects OBJECT IDENTIFIER
::= { ciscoLwappDot11ClientMIB 1 }
ciscoLwappDot11ClientMIBConform OBJECT IDENTIFIER
::= { ciscoLwappDot11ClientMIB 2 }
cldcConfigObjects OBJECT IDENTIFIER
::= { ciscoLwappDot11ClientMIBObjects 1 }
cldcNotifObjects OBJECT IDENTIFIER
::= { ciscoLwappDot11ClientMIBObjects 2 }
cldcStatusObjects OBJECT IDENTIFIER
::= { ciscoLwappDot11ClientMIBObjects 3 }
-- ********************************************************************
-- Wireless Clients
-- ********************************************************************
cldcClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF CldcClientEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table represents the 802.11 wireless clients
that are associated with the APs that have joined
this controller.
An entry is created automatically by the controller
when the client gets associated to the AP. An existing
entry gets deleted when the association gets dropped.
Each client added to this table is uniquely identified
by the client's MAC address."
::= { cldcStatusObjects 1 }
cldcClientEntry OBJECT-TYPE
SYNTAX CldcClientEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry represents a conceptual row in this
table and provides the information about the
clients associated to the APs that have joined
the controller. An entry is identified the client's
MAC address."
INDEX { cldcClientMacAddress }
::= { cldcClientTable 1 }
CldcClientEntry ::= SEQUENCE {
cldcClientMacAddress MacAddress,
cldcClientStatus CLDot11ClientStatus,
cldcClientWlanProfileName SnmpAdminString,
cldcClientWgbStatus INTEGER ,
cldcClientWgbMacAddress MacAddress,
cldcClientProtocol INTEGER ,
cldcAssociationMode INTEGER ,
cldcApMacAddress MacAddress,
cldcIfType CLApIfType
}
cldcClientMacAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the MAC address of the
client for this entry and uniquely identifies
this entry. "
::= { cldcClientEntry 1 }
cldcClientStatus OBJECT-TYPE
SYNTAX CLDot11ClientStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The object that represents the current status of
the client."
::= { cldcClientEntry 2 }
cldcClientWlanProfileName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the WLAN Profile name
this 802.11 wireless client is connected to."
::= { cldcClientEntry 3 }
cldcClientWgbStatus OBJECT-TYPE
SYNTAX INTEGER {
regClient(1),
wgbClient(2),
wgb(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The object that represents the work group bridging
status of a DOT11 client.
'regClient' - The client is a wireless client
'wgbClient' - The client is connected via a WGB
'wgb' - The client is the WGB itself."
::= { cldcClientEntry 4 }
cldcClientWgbMacAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the MAC address of the
WGB this 802.11 wireless client to which it is
connected. This returns a non-zero value when
the cldcClientWgbStatus is wgbClient."
::= { cldcClientEntry 5 }
cldcClientProtocol OBJECT-TYPE
SYNTAX INTEGER {
dot11a(1),
dot11b(2),
dot11g(3),
unknown(4),
mobile(5),
dot11n24(6),
dot11n5(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The 802.11 protocol type of the client.
'dot11a' - The client is using 802.11a standard
to connect to the access point (AP)
'dot11b' - The client is using 802.11b standard
to connect to the access point (AP)
'dot11g' - The client is using 802.11g standard
to connect to the access point (AP)
'unknown' - The client protocol is unknown
'mobile' - The client using mobile wireless to
connect to the access point (AP).
'dot11n24' - The client is using 802.11n standard
with 2.4 GHz frequency to connect to
the access point (AP)
'dot11n5' - The client is using 802.11n standard
with 5 GHz frequency to connect to
the access point (AP)."
::= { cldcClientEntry 6 }
cldcAssociationMode OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
wep(2),
wpa(3),
wpa2(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The association mode for which the key decrypt
error occurred."
::= { cldcClientEntry 7 }
cldcApMacAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the radio MAC address
of a LWAPP AP."
::= { cldcClientEntry 8 }
cldcIfType OBJECT-TYPE
SYNTAX CLApIfType
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This object specifies the wireless interace type."
::= { cldcClientEntry 9 }
-- ********************************************************************
-- * NOTIFICATION Control objects
-- ********************************************************************
cldcKeyDecryptErrorEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The object to control the generation of
ciscoLwappDot11ClientKeyDecryptError notification.
A value of 'true' indicates that the agent generates
ciscoLwappDot11ClientKeyDecryptError notification.
A value of 'false' indicates that the agent doesn't
generate ciscoLwappDot11ClientKeyDecryptError notification."
DEFVAL { true }
::= { cldcConfigObjects 1 }
-- ********************************************************************
-- * NOTIFICATIONS
-- ********************************************************************
ciscoLwappDot11ClientKeyDecryptError NOTIFICATION-TYPE
OBJECTS {
cldcAssociationMode,
cldcApMacAddress,
cldcIfType
}
STATUS current
DESCRIPTION
"Issued when a decrypt error occurs. The WEP WPA or WPA2 Key
configured at the station may be wrong."
::= { ciscoLwappDot11ClientMIBNotifs 1 }
-- *******************************************************************
-- * Compliance statements
-- ********************************************************************
ciscoLwappDot11ClientMIBCompliances OBJECT IDENTIFIER
::= { ciscoLwappDot11ClientMIBConform 1 }
ciscoLwappDot11ClientMIBGroups OBJECT IDENTIFIER
::= { ciscoLwappDot11ClientMIBConform 2 }
ciscoLwappDot11ClientMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for the SNMP entities that
implement this MIB."
MODULE -- this module
MANDATORY-GROUPS {
ciscoLwappDot11ClientMIBConfigGroup,
ciscoLwappDot11ClientMIBNotifsGroup,
ciscoLwappDot11ClientMIBStatusGroup
}
::= { ciscoLwappDot11ClientMIBCompliances 1 }
-- ********************************************************************
-- * Units of conformance
-- ********************************************************************
ciscoLwappDot11ClientMIBConfigGroup OBJECT-GROUP
OBJECTS { cldcKeyDecryptErrorEnabled }
STATUS current
DESCRIPTION
"This collection of objects specifies the required
configuration parameters for the 802.11 wireless
clients."
::= { ciscoLwappDot11ClientMIBGroups 1 }
ciscoLwappDot11ClientMIBNotifsGroup NOTIFICATION-GROUP
NOTIFICATIONS { ciscoLwappDot11ClientKeyDecryptError }
STATUS current
DESCRIPTION
"This collection of objects specifies the
notifications for the 802.11 wireless clients."
::= { ciscoLwappDot11ClientMIBGroups 2 }
ciscoLwappDot11ClientMIBStatusGroup OBJECT-GROUP
OBJECTS {
cldcClientStatus,
cldcClientWlanProfileName,
cldcClientWgbStatus,
cldcClientWgbMacAddress,
cldcClientProtocol,
cldcAssociationMode,
cldcApMacAddress,
cldcIfType
}
STATUS current
DESCRIPTION
"This collection of objects specifies the required
status parameters for the 802.11 wireless clients."
::= { ciscoLwappDot11ClientMIBGroups 3 }
END
mibs/CISCO-LWAPP-SYS-MIB
+2149
View File
File diff suppressed because it is too large Load Diff
mibs/CISCO-LWAPP-TC-MIB
+754
View File
@@ -0,0 +1,754 @@
-- *******************************************************************
-- CISCO-LWAPP-TC-MIB.my: Cisco LWAPP MIBs Textual Conventions
-- March 2006, Prasanna Viswakumar
--
-- Copyright (c) 2006, 2007, 2010-2011 by Cisco Systems Inc.
-- All rights reserved.
-- *******************************************************************
CISCO-LWAPP-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
Unsigned32,
Gauge32
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC
ciscoMgmt
FROM CISCO-SMI;
-- ********************************************************************
-- * MODULE IDENTITY
-- ********************************************************************
ciscoLwappTextualConventions MODULE-IDENTITY
LAST-UPDATED "201109130000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems,
Customer Service
Postal: 170 West Tasman Drive
San Jose, CA 95134
USA
Tel: +1 800 553-NETS
Email: [email protected]"
DESCRIPTION
"This module defines textual conventions used
throughout the Cisco enterprise MIBs
designed for implementation on Central
Controllers that terminate the Light Weight
Access Point Protocol from LWAPP Access
Points.
The relationship between CC and the LWAPP APs
can be depicted as follows:
+......+ +......+ +......+ +......+
+ + + + + + + +
+ CC + + CC + + CC + + CC +
+ + + + + + + +
+......+ +......+ +......+ +......+
.. . . .
.. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ AP + + AP + + AP + + AP + + AP +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ MN + + MN + + MN + + MN + + MN +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
The LWAPP tunnel exists between the controller and
the APs. The MNs communicate with the APs through
the protocol defined by the 802.11 standard.
LWAPP APs, upon bootup, discover and join one of the
controllers and the controller pushes the configuration,
that includes the WLAN parameters, to the LWAPP APs.
The APs then encapsulate all the 802.11 frames from
wireless clients inside LWAPP frames and forward
the LWAPP frames to the controller.
GLOSSARY
Access Point ( AP )
An entity that contains an 802.11 medium access
control ( MAC ) and physical layer ( PHY ) interface
and provides access to the distribution services via
the wireless medium for associated clients.
LWAPP APs encapsulate all the 802.11 frames in
LWAPP frames and sends it to the controller to which
it is logically connected.
Advanced Encryption Standard ( AES )
In cryptography, the Advanced Encryption Standard
(AES), also known as Rijndael, is a block cipher
adopted as an encryption standard by the US
government. It is expected to be used worldwide
and analysed extensively, as was the case with its
predecessor, the Data Encryption Standard (DES).
AES was adopted by National Institute of Standards
and Technology (NIST) as US FIPS PUB 197 in
November 2001 after a 5-year standardisation
process.
Central Controller ( CC )
The central entity that terminates the LWAPP protocol
tunnel from the LWAPP APs. Throughout this MIB,
this entity is also referred to as 'controller'.
Light Weight Access Point Protocol ( LWAPP )
This is a generic protocol that defines the
communication between the Access Points and the
Central Controller.
Management Frame Protection ( MFP )
A proprietary mechanism devised to integrity protect
the otherwise unprotected management frames of the
802.11 protocol specification.
Message Integrity Check ( MIC )
A checksum computed on a sequence of bytes and made
known to the receiving party in a data communication,
to let the receiving party make sure the bytes
received were not compromised enroute.
Mobile Node ( MN )
A roaming 802.11 wireless device in a wireless
network associated with an access point.
Temporal Key Integrity Protocol ( TKIP )
A security protocol defined to enhance the limitations
of WEP. Message Integrity Check and per-packet keying
on all WEP-encrypted frames are two significant
enhancements provided by TKIP to WEP.
Wired Equivalent Privacy ( WEP )
A security method defined by 802.11. WEP uses a
symmetric key stream cipher called RC4 to encrypt the
data packets.
802.11n
802.11n builds upon previous 802.11 standards by
adding MIMO (multiple-input multiple-output). MIMO
uses multiple transmitter and receiver antennas to
allow for increased data throughput through spatial
multiplexing and increased range.
Control/Extension Channel
A single 802.11 channel is 20 MHz wide. 802.11n allows
the use of channels of width 40 MHz by combining two
20 MHz channels. The channels are known as the primary
or control channel and secondary or extension channel.
Both the channels are used for transmission
and reception of data.
REFERENCE
[1] Part 11 Wireless LAN Medium Access Control ( MAC )
and Physical Layer ( PHY ) Specifications.
[2] Draft-obara-capwap-lwapp-00.txt, IETF Light
Weight Access Point Protocol.
[3] Enhanced Wireless Consortium MAC Specification,
v1.24.
[4] Enhanced Wireless Consortium PHY Specification,
v1.27."
REVISION "201109130000Z"
DESCRIPTION
"Added new textual conventions CcxServiceVersion"
REVISION "201002230000Z"
DESCRIPTION
"Added new textual conventions CLApDot11RadioRole,
CLClientPowerSaveMode,and CLApDot11RadioSubband."
REVISION "200709110000Z"
DESCRIPTION
"Added new textual convention CLWebAuthType."
REVISION "200702050000Z"
DESCRIPTION
"Added new textual conventions CLDot11ChannelBandwidth,
CLDot11Band and CLApAssocFailureReason."
REVISION "200610310000Z"
DESCRIPTION
"Added new textual conventions CLMfpEventSource,
CLCdpAdvtVersionType and CLDot11ClientStatus."
REVISION "200604130000Z"
DESCRIPTION
"Initial version of this MIB module."
::= { ciscoMgmt 514 }
-- ********************************************************************
-- TEXTUAL CONVENTION
-- ********************************************************************
CLApIfType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the type of a
wireless interface.
The semantics are as follows:
dot11bg - This value indicates that the radio
interface follows 802.11b or 802.11g standard.
dot11a - This value indicates that the radio
interface follows 802.11a standard.
uwb - This value indicates that this is a Ultra
Wideband Interface."
SYNTAX INTEGER {
dot11bg(1),
dot11a(2),
uwb(3)
}
CLDot11Channel ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the possible channel
numbers in an 802.11 communication channel. The
802.11 radio interface of an Access Point operates
in one of the possible channels at any point of time
for wireless data communication with 802.11 based
wireless clients."
SYNTAX Unsigned32 (1..14 | 34 | 36 | 38 | 40 | 42 | 44 | 46
| 48 | 52 | 56 | 60 | 64 | 149 | 153
| 157 | 161)
CLDot11ClientStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the states
of an 802.11 client.
The semantics are as follows:
idle(1) - client is in idle mode.
aaaPending(2) - client's authentication is pending.
Request has been sent to AAA server for authentication.
authenticated(3) - client has been authenticated.
associated(4) - client is associated, but not
authenticated.
powersave(5) - client is in powersave mode.
disassociated(6) - client has dissociated and not in
any of the 802.11 networks managed by the controller.
tobedeleted(7) - client is marked for deletion.
probing(8) - state before association. The client
will be removed if it does not associate.
excluded(9) - client has been marked as excluded after fixed
number of authentication failures."
SYNTAX INTEGER {
idle(1),
aaaPending(2),
authenticated(3),
associated(4),
powersave(5),
disassociated(6),
tobedeleted(7),
probing(8),
excluded(9)
}
CLEventFrames ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the possible
802.11 management frame subtypes.
cLAssocRequestFrm - 802.11 Association Request
frame
cLAssocResponseFrm - 802.11 Association Response
frame
cLReAssocRequestFrm - 802.11 Reassociation
Request frame
cLReAssocResponseFrm - 802.11 Reassociation
Response frame
cLProbeRequestFrm - 802.11 Probe Request frame
cLProbeResponseFrm - 802.11 Probe Response
frame
cLReserved1 - Reserved for future use
cLReserved2 - Reserved for future use
cLBeaconFrm - 802.11 Beacon frame
cLAtimFrm - 802.11 Adhoc Traffic Indication
Map frame
cLDissociationFrm - 802.11 Dissociation
frame
cLAuthenticationFrm - 802.11 Authentication
frame
cLDeAuthenticationFrm - 802.11 Deauthentication
frame"
REFERENCE
"Part 11 Wireless LAN Medium Access Control ( MAC )
and Physical Layer ( PHY ) Specifications,
Section 7.1.3.1.2 - Type and Subtype fields"
SYNTAX BITS {
cLAssocRequestFrm(0),
cLAssocResponseFrm(1),
cLReAssocRequestFrm(2),
cLReAssocResponseFrm(3),
cLProbeRequestFrm(4),
cLProbeResponseFrm(5),
cLReserved1(6),
cLReserved2(7),
cLBeaconFrm(8),
cLAtimFrm(9),
cLDissociationFrm(10),
cLAuthenticationFrm(11),
cLDeAuthenticationFrm(12)
}
CLMfpEventType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The type of the MFP anomaly event.
invalidMic - The MFP Validation has identified
that the MIC carried by a particular management
frame is invalid.
invalidSeq - The MFP validation has identified
that a particular management frame is carrying an
invalid sequence number. Note that an invalid
sequence number error can also be detected due to an
incorrect timestamp in the MFP information element.
The incorrect timestamp could possibly be due to the
fact that the detecting AP's time window is not in
synchronization with that of other APs in the
MFP framework.
noMic - The MFP validation has detected a management
frame without the MFP information element.
unexpectedMic - The MFP validation has detected a
management frame as carrying a MIC value when
protection is not enabled on the WLAN.
ccmpDecryptError - An MFP frame that was apparently
received from a client in an AES-CCMP encrypted
session was rejected by the Access Point because it
could not be decrypted.
ccmpInvalidMhdrIe - An MFP frame that was apparently
received from a client in an AES-CCMP encrypted
session was rejected by the Access Point because it
contained an invalid MHDR information element, or the
MHDR information element was not present.
ccmpInvalidReplayCtr - An MFP frame that was apparently
received from a client in an AES-CCMP encrypted session
was rejected by the Access Point because the replay
counter was not valid.
tkipInvalidIcv - An MFP frame that was apparently
received from a client in a TKIP encrypted session was
rejected by the Access Point because it contained an
invalid Integrity Check Value.
tkipInvalidMic - An MFP frame that was apparently
received from a client in a TKIP encrypted session was
rejected by the Access Point because the message
integrity check failed.
tkipInvalidMhdrIe - An MFP frame that was apparently
received from a client in a TKIP encrypted session was
rejected by the Access Point because it contained an
invalid MHDR information element, or the MHDR
information element was not present.
tkipInvalidReplayCtr - An MFP frame that was apparently
received from a client in a TKIP encrypted session was
rejected by the Access Point because it the replay
counter was not valid.
bcastDisassociationFrameRcvd - The Access Point detected
a broadcast disassociation frame. Broadcast
disassociation frames are rejected by CCXv5 compliant
devices.
bcastDeauthenticationFrameRcvd - The Access Point
detected a broadcast deauthentication frame. Broadcast
deauthentication frames are rejected by CCXv5 compliant
devices.
bcastActionFrameRcvd - The Access Point detected a
broadcast action frame. Broadcast action frames are
rejected by CCXv5 compliant devices."
SYNTAX INTEGER {
invalidMic(1),
invalidSeq(2),
noMic(3),
unexpectedMic(4),
ccmpNoEncryptError(16),
ccmpDecryptError(17),
ccmpInvalidReplayCtr(19),
tkipNoEncryptError(20),
tkipInvalidIcv(21),
tkipInvalidMic(22),
tkipInvalidMhdrIe(23),
tkipInvalidReplayCtr(24),
bcastDisassociationFrameRcvd(32),
bcastDeauthenticationFrameRcvd(33),
bcastActionFrameRcvd(34)
}
CLMfpEventSource ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The source of the MFP anomaly event.
infrastructureMfp - The source of the MFP event is
an infrastructure device that implements MFP.
clientMfp - The source of the MFP event is a client
device that implements MFP."
SYNTAX INTEGER {
infrastructureMfp(1),
clientMfp(2)
}
CLMfpVersion ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention lists the versions of
the MFP protocol."
SYNTAX INTEGER {
mfpv1(1),
mfpv2(2)
}
CLTimeBaseStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is used to define the
time synchronization of entities with their
respective time bases.
cTimeBaseInSync - This value indicates that the
respective entity is in synchronization with
its time base.
cTimeBaseNotInSync - This value indicates that
the respective entity is not in synchronization
with its time base."
SYNTAX INTEGER {
cTimeBaseInSync(1),
cTimeBaseNotInSync(2)
}
CLSecEncryptType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the type of
encryption to be applied to a WLAN.
The semantics are as follows:
tkip - This value indicates that TKIP encryption
is configured for data protection.
aes - This value indicates that AES encryption
is configured for data protection."
SYNTAX BITS {
tkip(0),
aes(1)
}
CLSecKeyFormat ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the type of
the key configured for encryption."
SYNTAX INTEGER {
default(1),
hex(2),
ascii(3)
}
CLDot11RfParamMode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines how the RF
parameters used to manage roaming are chosen
by the controller.
default - controller reverts back to the default
values specified for the RF parameters.
auto - controller determines the RF parameters
automatically without any input from the end user.
custom - controller uses the RF parameters
configured by the end user. User is allowed to
configure the parameters only if the mode is set
to 'custom'."
SYNTAX INTEGER {
default(1),
custom(2),
auto(3)
}
CLTsmDot11CurrentPackets ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The number of packets received over a specified
period of time."
SYNTAX Gauge32
CLCdpAdvtVersionType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention lists the versions of
the CDP protocol in use in LWAPP APs and Controllers."
SYNTAX INTEGER {
cdpv1(1),
cdpv2(2)
}
CLDot11ChannelBandwidth ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the channel
bandwidth for 802.11n radio interfaces.
The semantics are as follows:
five - This value indicates that the bandwidth
is 5 MHz.
ten - This value indicates that the bandwidth
is 10 MHz.
twenty - This value indicates that the bandwidth
is 20 MHz.
aboveforty - This value indicates that the bandwidth
is 40 MHz with the extension channel above the control
channel.
belowforty - This value indicates that the bandwidth
is 40 MHz with the extension channel below the control
channel."
SYNTAX INTEGER {
five(1),
ten(2),
twenty(3),
aboveforty(4),
belowforty(5)
}
CLDot11Band ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the 802.11 frequency
band.
The semantics are as follows:
band2dot4 - This value indicates that the
2.4 GHz band is in use.
band5 - This value indicates that the
5 GHz band is in use."
SYNTAX INTEGER {
band2dot4(1),
band5(2)
}
CLApAssocFailureReason ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the possible reasons
for an AP's failure to get associated to a controller.
The semantics are as follows:
unknown - The reason for the AP not being able to
associate is unknown.
notSupported - The AP is not supported for management
by the controller."
SYNTAX INTEGER {
unknown(1),
notSupported(2)
}
CLWebAuthType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents either one of the following web auth types
internalDefault(1) -
The default login page will be
presented to the client for authentication.
internalCustom(2) -
The administrator has created and
uploaded a custom login page and it will be
presented to the clients for authentication.
external(3) -
This value indicates that the login page
will be served from the external web server. Note
that cLWAWebAuthType can be successfully set to this
value when the cLWAExternalWebAuthURL object has been
set to string with non-zero length."
SYNTAX INTEGER {
internalDefault(1),
internalCustom(2),
external(3)
}
CLClientPowerSaveMode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines power management mode
of this client.
The possible two modes are:
active(1) - The client is not in power-save mode
and it is actively sending or receiving
data.
powersave(2) - The client is in power-save mode and it
wakes up once a while to check for
pending data."
SYNTAX INTEGER {
active(1),
powersave(2)
}
CLApDot11RadioSubband ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the possible values
of subbands a radio can support.
Currently, this information is applicable to
A radios.
all(1) - This radio is a regular A radio that operates
in the full A band spectrum in the frequency
range 4940 Mhz - 5850 Mhz.
sub49(2) - This is an A radio that operates only in the
public safety (4.9 Ghz) sub band in the
frequency range 4940 Mhz - 5100 Mhz.
sub52(3) - This is an A radio that operates only in the
5.2 Ghz sub band in the frequency range
5250 Mhz - 5350 Mhz.
sub54(4) - This is an A radio that operates only in the
5.4 Ghz sub band in the frequency range
5470 Mhz - 5725 Mhz.
sub58(5) - This is an A radio that operates only in the
5.8 Ghz sub band in the frequency range
5725 Mhz - 5850 Mhz."
SYNTAX INTEGER {
all(1),
sub49(2),
sub52(3),
sub54(4),
sub58(5)
}
CLApDot11RadioRole ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the possible values
of role a radio can support.
shutdown(0) - This role states that the radio is
shut down.
upDownlink(1) - This radio provides both uplink
and downlink access.
uplink(2) - This role is applicable only for Ethernet
ports. This radio provides uplink access.
downlink(3) - This radio provides downlink access.
downlink radio allows child APs to join.
access(4) - This radio provides the access to the
clients.
uplinkAccess(5) - This radio role states that the radio
provides the uplink access to the clients.
downlinkAccess(6) - This radio role states that the radio
provides the downlink access to
the clients.
upDownlinkAccess(7) - This radio role states that the radio
provides both uplink and downlink access
to the clients.
unknown(8) - This radio role is unknown."
SYNTAX INTEGER {
shutdown(0),
upDownlink(1),
uplink(2),
downlink(3),
access(4),
uplinkAccess(5),
downlinkAccess(6),
upDownlinkAccess(7),
unknown(8)
}
CcxServiceVersion ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the service versions
supported by a CCX Next client. The supported services
include foundation, location, management and voice."
SYNTAX INTEGER {
none(1),
version1(2),
version2(3)
}
END
mibs/CISCO-SMI
+466 -238
View File
@@ -1,326 +1,554 @@
-- *****************************************************************
-- CISCO-SMI.my: Cisco Enterprise Structure of Management Information
--
--
-- April 1994, Jeffrey T. Johnson
--
-- Copyright (c) 1994-1997 by cisco Systems, Inc.
--
-- Copyright (c) 1994-1997, 2001, 2009, 2012 by cisco Systems Inc.
-- All rights reserved.
--
-- *****************************************************************
--
--
-- ****************************************************************
CISCO-SMI DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-IDENTITY,
enterprises
FROM SNMPv2-SMI;
MODULE-IDENTITY,
OBJECT-IDENTITY,
enterprises
FROM SNMPv2-SMI;
cisco MODULE-IDENTITY
LAST-UPDATED "200001110000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
" Cisco Systems
Customer Service
LAST-UPDATED "201208290000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Customer Service
Postal: 170 West Tasman Drive
San Jose, CA 95134
USA
Postal: 170 West Tasman Drive
San Jose, CA 95134
USA
Tel: +1 800 553-NETS
Tel: +1 800 553-NETS
E-mail: [email protected]"
DESCRIPTION
"The Structure of Management Information for the
Cisco enterprise."
REVISION "200001110000Z"
DESCRIPTION
"Added ciscoPolicy, ciscoPolicyAuto, ciscoPIB, and
ciscoPibToMib."
REVISION "9704090000Z"
DESCRIPTION
"Added ciscoPartnerProducts to generate sysObjectID
for partner platforms"
REVISION "9505160000Z"
DESCRIPTION
"New oid assignments for Cisco REPEATER MIB and others."
REVISION "9404262000Z"
DESCRIPTION
"Initial version of this MIB module."
::= { enterprises 9 } -- assigned by IANA
E-mail: [email protected]"
DESCRIPTION
"The Structure of Management Information for the
Cisco enterprise."
REVISION "201208290000Z"
DESCRIPTION
"Added ciscoSMB under otherEnterprises"
REVISION "200902030000Z"
DESCRIPTION
"Added ciscoSB under otherEnterprises"
REVISION "200203210000Z"
DESCRIPTION
"Added ciscoPKI for PKI policy and extension OIDs"
REVISION "200105220000Z"
DESCRIPTION
"Added transport protocol domains."
REVISION "200011012246Z"
DESCRIPTION
"Added ciscoDomains to define new transports. Also added
ciscoCpeCIB, which will contain managed objects that
contribute to the CPE Configuration Information Base (CIB)."
REVISION "200001110000Z"
DESCRIPTION
"Added ciscoPolicy, ciscoPolicyAuto, ciscoPIB, and
ciscoPibToMib."
REVISION "9704090000Z"
DESCRIPTION
"Added ciscoPartnerProducts to generate sysObjectID
for partner platforms"
REVISION "9505160000Z"
DESCRIPTION
"New oid assignments for Cisco REPEATER MIB and others."
REVISION "9404262000Z"
DESCRIPTION
"Initial version of this MIB module."
::= { enterprises 9 }
-- assigned by IANA
ciscoProducts OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoProducts is the root OBJECT IDENTIFIER from
which sysObjectID values are assigned. Actual
values are defined in CISCO-PRODUCTS-MIB."
::= { cisco 1 }
STATUS current
DESCRIPTION
"ciscoProducts is the root OBJECT IDENTIFIER from
which sysObjectID values are assigned. Actual
values are defined in CISCO-PRODUCTS-MIB."
::= { cisco 1 }
local OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Subtree beneath which pre-10.2 MIBS were built."
::= { cisco 2 }
STATUS current
DESCRIPTION
"Subtree beneath which pre-10.2 MIBS were built."
::= { cisco 2 }
temporary OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Subtree beneath which pre-10.2 experiments were
placed."
::= { cisco 3 }
STATUS current
DESCRIPTION
"Subtree beneath which pre-10.2 experiments were
placed."
::= { cisco 3 }
pakmon OBJECT-IDENTITY
STATUS current
DESCRIPTION
"reserved for pakmon"
::= { cisco 4 }
STATUS current
DESCRIPTION
"reserved for pakmon"
::= { cisco 4 }
workgroup OBJECT-IDENTITY
STATUS current
DESCRIPTION
"subtree reserved for use by the Workgroup Business Unit"
::= { cisco 5 }
STATUS current
DESCRIPTION
"subtree reserved for use by the Workgroup Business Unit"
::= { cisco 5 }
otherEnterprises OBJECT-IDENTITY
STATUS current
DESCRIPTION
"otherEnterprises provides a root object identifier
from which mibs produced by other companies may be
placed. mibs produced by other enterprises are
typicially implemented with the object identifiers
as defined in the mib, but if the mib is deemed to
be uncontrolled, we may reroot the mib at this
subtree in order to have a controlled version."
::= { cisco 6 }
STATUS current
DESCRIPTION
"otherEnterprises provides a root object identifier
from which mibs produced by other companies may be
placed. mibs produced by other enterprises are
typicially implemented with the object identifiers
as defined in the mib, but if the mib is deemed to
be uncontrolled, we may reroot the mib at this
subtree in order to have a controlled version."
::= { cisco 6 }
ciscoSB OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoSB provides root Object Identifier for Management
Information Base for products of Cisco Small Business.
This includes products rebranded from linksys aquisition.
MIB numbers under this root are managed and controlled
by [email protected]."
::= { otherEnterprises 1 }
ciscoSMB OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoSMB provides root Object Identifier for Management
Information Base for products of Cisco built for Small and
Medium Business market.The MIB numbers under this root are
managed and controlled by [email protected]"
::= { otherEnterprises 2 }
ciscoAgentCapability OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoAgentCapability provides a root object identifier
from which AGENT-CAPABILITIES values may be assigned."
::= { cisco 7 }
STATUS current
DESCRIPTION
"ciscoAgentCapability provides a root object identifier
from which AGENT-CAPABILITIES values may be assigned."
::= { cisco 7 }
ciscoConfig OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoConfig is the main subtree for configuration mibs."
::= { cisco 8 }
STATUS current
DESCRIPTION
"ciscoConfig is the main subtree for configuration mibs."
::= { cisco 8 }
ciscoMgmt OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoMgmt is the main subtree for new mib development."
::= { cisco 9 }
STATUS current
DESCRIPTION
"ciscoMgmt is the main subtree for new mib development."
::= { cisco 9 }
ciscoExperiment OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoExperiment provides a root object identifier
from which experimental mibs may be temporarily
based. mibs are typicially based here if they
fall in one of two categories
1) are IETF work-in-process mibs which have not
been assigned a permanent object identifier by
the IANA.
2) are cisco work-in-process which has not been
assigned a permanent object identifier by the
cisco assigned number authority, typicially because
the mib is not ready for deployment.
STATUS current
DESCRIPTION
"ciscoExperiment provides a root object identifier
from which experimental mibs may be temporarily
based. mibs are typicially based here if they
fall in one of two categories
1) are IETF work-in-process mibs which have not
been assigned a permanent object identifier by
the IANA.
2) are cisco work-in-process which has not been
assigned a permanent object identifier by the
cisco assigned number authority, typicially because
the mib is not ready for deployment.
NOTE WELL: support for mibs in the ciscoExperiment
subtree will be deleted when a permanent object
identifier assignment is made."
::= { cisco 10 }
NOTE WELL: support for mibs in the ciscoExperiment
subtree will be deleted when a permanent object
identifier assignment is made."
::= { cisco 10 }
ciscoAdmin OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoAdmin is reserved for administratively assigned
OBJECT IDENTIFIERS, i.e. those not associated with MIB
objects"
::= { cisco 11 }
STATUS current
DESCRIPTION
"ciscoAdmin is reserved for administratively assigned
OBJECT IDENTIFIERS, i.e. those not associated with MIB
objects"
::= { cisco 11 }
ciscoModules OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoModules provides a root object identifier
from which MODULE-IDENTITY values may be assigned."
::= { cisco 12 }
STATUS current
DESCRIPTION
"ciscoModules provides a root object identifier
from which MODULE-IDENTITY values may be assigned."
::= { cisco 12 }
lightstream OBJECT-IDENTITY
STATUS current
DESCRIPTION
"subtree reserved for use by Lightstream"
::= { cisco 13 }
STATUS current
DESCRIPTION
"subtree reserved for use by Lightstream"
::= { cisco 13 }
ciscoworks OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoworks provides a root object identifier beneath
which mibs applicable to the CiscoWorks family of network
management products are defined."
::= { cisco 14 }
STATUS current
DESCRIPTION
"ciscoworks provides a root object identifier beneath
which mibs applicable to the CiscoWorks family of network
management products are defined."
::= { cisco 14 }
newport OBJECT-IDENTITY
STATUS current
DESCRIPTION
"subtree reserved for use by the former Newport Systems
Solutions, now a portion of the Access Business Unit."
::= { cisco 15 }
STATUS current
DESCRIPTION
"subtree reserved for use by the former Newport Systems
Solutions, now a portion of the Access Business Unit."
::= { cisco 15 }
ciscoPartnerProducts OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoPartnerProducts is the root OBJECT IDENTIFIER from
which partner sysObjectID values may be assigned. Such
sysObjectID values are composed of the ciscoPartnerProducts
prefix, followed by a single identifier that is unique for
each partner, followed by the value of sysObjectID of the
Cisco product from which partner product is derived. Note
that the chassisPartner MIB object defines the value of the
identifier assigned to each partner."
::= { cisco 16 }
STATUS current
DESCRIPTION
"ciscoPartnerProducts is the root OBJECT IDENTIFIER from
which partner sysObjectID values may be assigned. Such
sysObjectID values are composed of the ciscoPartnerProducts
prefix, followed by a single identifier that is unique for
each partner, followed by the value of sysObjectID of the
Cisco product from which partner product is derived. Note
that the chassisPartner MIB object defines the value of the
identifier assigned to each partner."
::= { cisco 16 }
ciscoPolicy OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoPolicy is the root of the Cisco-assigned OID
subtree for use with Policy Management."
::= { cisco 17 }
STATUS current
DESCRIPTION
"ciscoPolicy is the root of the Cisco-assigned OID
subtree for use with Policy Management."
::= { cisco 17 }
-- Note that 1.3.6.1.4.1.9.17.1 is currently unassigned
-- Note that 1.3.6.1.4.1.9.17.1 is currently unassigned
ciscoPIB OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoPIB is the root of the Cisco-assigned OID
subtree for assignment to PIB (Policy Information
Base) modules."
::= { ciscoPolicy 2 }
STATUS current
DESCRIPTION
"ciscoPIB is the root of the Cisco-assigned OID
subtree for assignment to PIB (Policy Information
Base) modules."
::= { ciscoPolicy 2 }
ciscoPolicyAuto OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoPolicyAuto is the root of the Cisco-assigned
OID subtree for OIDs which are automatically assigned
for use in Policy Management."
::= { cisco 18 }
STATUS current
DESCRIPTION
"ciscoPolicyAuto is the root of the Cisco-assigned
OID subtree for OIDs which are automatically assigned
for use in Policy Management."
::= { cisco 18 }
-- Note that 1.3.6.1.4.1.9.18.1 is currently unassigned
-- Note that 1.3.6.1.4.1.9.18.1 is currently unassigned
ciscoPibToMib OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoPibToMib is the root of the Cisco-assigned
OID subtree for MIBs which are algorithmically
generated/translated from Cisco PIBs with OIDs
assigned under the ciscoPIB subtree.
These generated MIBs allow management
entities (other the current Policy Server) to
read the downloaded policy. By convention, for PIB
'ciscoPIB.x', the generated MIB shall have the
name 'ciscoPibToMib.x'."
::= { ciscoPolicyAuto 2 }
STATUS current
DESCRIPTION
"ciscoPibToMib is the root of the Cisco-assigned
OID subtree for MIBs which are algorithmically
generated/translated from Cisco PIBs with OIDs
assigned under the ciscoPIB subtree.
These generated MIBs allow management
entities (other the current Policy Server) to
read the downloaded policy. By convention, for PIB
'ciscoPIB.x', the generated MIB shall have the
name 'ciscoPibToMib.x'."
::= { ciscoPolicyAuto 2 }
ciscoDomains OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoDomains provides a root object identifier from which
different transport mapping values may be assigned."
::= { cisco 19 }
ciscoCIB OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoCIB is the root of the Cisco-assigned OID subtree for
assignment to MIB modules describing managed objects that
part of the CPE automatic configuration framework."
::= { cisco 20 }
ciscoCibMmiGroup OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoCibMmiGroup is the root of the Cisco-assigned OID
subtree for assignment to MIB modules describing managed
objects supporting the Modem Management Interface (MMI),
the interface that facilitates CPE automatic configuration."
::= { ciscoCIB 1 }
ciscoCibProvGroup OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoCibStoreGroup is the root of the Cisco-assigned OID
subtree for assignment to MIB modules describing managed
objects contributing to the Configuration Information Base
(CIB)."
::= { ciscoCIB 2 }
ciscoPKI OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoPKI is the root of cisco-assigned OID subtree for PKI
Certificate Policies and Certificate Extensions."
::= { cisco 21 }
-- ciscoAdmin assignments follow
ciscoProxy OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoProxy OBJECT IDENTIFIERS are used to uniquely name
party mib records created to proxy for SNMPv1."
::= { ciscoAdmin 1 }
ciscoPartyProxy OBJECT IDENTIFIER ::= { ciscoProxy 1 }
ciscoContextProxy OBJECT IDENTIFIER ::= { ciscoProxy 2 }
STATUS current
DESCRIPTION
"ciscoProxy OBJECT IDENTIFIERS are used to uniquely name
party mib records created to proxy for SNMPv1."
::= { ciscoAdmin 1 }
ciscoPartyProxy OBJECT IDENTIFIER
::= { ciscoProxy 1 }
ciscoContextProxy OBJECT IDENTIFIER
::= { ciscoProxy 2 }
--
-- Administrative assignments for repeaters
--
ciscoRptrGroupObjectID OBJECT-IDENTITY
STATUS current
DESCRIPTION
"ciscoRptrGroupObjectID OBJECT IDENTIFIERS are used to
uniquely identify groups of repeater ports for use by the
SNMP-REPEATER-MIB (RFC 1516) rptrGroupObjectID object."
::= { ciscoAdmin 2 }
STATUS current
DESCRIPTION
"ciscoRptrGroupObjectID OBJECT IDENTIFIERS are used to
uniquely identify groups of repeater ports for use by the
SNMP-REPEATER-MIB (RFC 1516) rptrGroupObjectID object."
::= { ciscoAdmin 2 }
ciscoUnknownRptrGroup OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The identity of an unknown repeater port group."
::= { ciscoRptrGroupObjectID 1 }
STATUS current
DESCRIPTION
"The identity of an unknown repeater port group."
::= { ciscoRptrGroupObjectID 1 }
cisco2505RptrGroup OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The authoritative identity of the Cisco 2505 repeater
port group."
::= { ciscoRptrGroupObjectID 2 }
STATUS current
DESCRIPTION
"The authoritative identity of the Cisco 2505 repeater
port group."
::= { ciscoRptrGroupObjectID 2 }
cisco2507RptrGroup OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The authoritative identity of the Cisco 2507 repeater
port group."
::= { ciscoRptrGroupObjectID 3 }
STATUS current
DESCRIPTION
"The authoritative identity of the Cisco 2507 repeater
port group."
::= { ciscoRptrGroupObjectID 3 }
cisco2516RptrGroup OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The authoritative identity of the Cisco 2516 repeater
port group."
::= { ciscoRptrGroupObjectID 4 }
STATUS current
DESCRIPTION
"The authoritative identity of the Cisco 2516 repeater
port group."
::= { ciscoRptrGroupObjectID 4 }
ciscoWsx5020RptrGroup OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The authoritative identity of the wsx5020 repeater
port group."
::= { ciscoRptrGroupObjectID 5 }
STATUS current
DESCRIPTION
"The authoritative identity of the wsx5020 repeater
port group."
::= { ciscoRptrGroupObjectID 5 }
--
-- Administrative assignments for chip sets
--
-- Administrative assignments for chip sets
ciscoChipSets OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Numerous media-specific MIBS have an object, defined as
an OBJECT IDENTIFIER, which is the identity of the chipset
realizing the interface. Cisco-specific chipsets have their
OBJECT IDENTIFIERS assigned under this subtree."
::= { ciscoAdmin 3 }
STATUS current
DESCRIPTION
"Numerous media-specific MIBS have an object, defined as
an OBJECT IDENTIFIER, which is the identity of the chipset
realizing the interface. Cisco-specific chipsets have their
OBJECT IDENTIFIERS assigned under this subtree."
::= { ciscoAdmin 3 }
ciscoChipSetSaint1 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The identity of the Rev 1 SAINT ethernet chipset
manufactured for cisco by LSI Logic."
::= { ciscoChipSets 1 }
STATUS current
DESCRIPTION
"The identity of the Rev 1 SAINT ethernet chipset
manufactured for cisco by LSI Logic."
::= { ciscoChipSets 1 }
ciscoChipSetSaint2 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The identity of the Rev 2 SAINT ethernet chipset
manufactured for cisco by LSI Logic."
::= { ciscoChipSets 2 }
STATUS current
DESCRIPTION
"The identity of the Rev 2 SAINT ethernet chipset
manufactured for cisco by LSI Logic."
::= { ciscoChipSets 2 }
ciscoChipSetSaint3 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The identity of the Rev 3 SAINT ethernet chipset
manufactured for cisco by Plessey."
::= { ciscoChipSets 3 }
STATUS current
DESCRIPTION
"The identity of the Rev 3 SAINT ethernet chipset
manufactured for cisco by Plessey."
::= { ciscoChipSets 3 }
ciscoChipSetSaint4 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The identity of the Rev 4 SAINT ethernet chipset
manufactured for cisco by Mitsubishi."
::= { ciscoChipSets 4 }
STATUS current
DESCRIPTION
"The identity of the Rev 4 SAINT ethernet chipset
manufactured for cisco by Mitsubishi."
::= { ciscoChipSets 4 }
-- Transport protocol domains
--
-- The textual conventions for these domains are defined in CISCO-TM.
ciscoTDomains OBJECT IDENTIFIER
::= { ciscoDomains 99999 }
ciscoTDomainUdpIpv4 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UDP over IPv4 transport domain. The corresponding
transport address is of type CiscoTAddressIPv4."
::= { ciscoTDomains 1 }
ciscoTDomainUdpIpv6 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The UDP over IPv6 transport domain. The corresponding
transport address is of type CiscoTAddressIPv6 for global IPv6
addresses and CiscoTAddressIPv6s for scoped IPv6 addresses."
::= { ciscoTDomains 2 }
ciscoTDomainTcpIpv4 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The TCP over IPv4 transport domain. The corresponding
transport address is of type CiscoTAddressIPv4."
::= { ciscoTDomains 3 }
ciscoTDomainTcpIpv6 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The TCP over IPv6 transport domain. The corresponding
transport address is of type CiscoTAddressIPv6 for global IPv6
addresses and CiscoTAddressIPv6s for scoped IPv6 addresses."
::= { ciscoTDomains 4 }
ciscoTDomainLocal OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The Posix Local IPC transport domain. The corresponding
transport address is of type CiscoTAddressLocal. The Posix
Local IPC transport domain incorporates the well known UNIX
domain sockets."
::= { ciscoTDomains 5 }
ciscoTDomainClns OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The CLNS transport domain. The corresponding transport
address is of type CiscoTAddressOSI."
::= { ciscoTDomains 6 }
ciscoTDomainCons OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The CONS transport domain. The corresponding transport
address is of type CiscoTAddressOSI."
::= { ciscoTDomains 7 }
ciscoTDomainDdp OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The DDP transport domain. The corresponding transport
address is of type CiscoTAddressNBP."
::= { ciscoTDomains 8 }
ciscoTDomainIpx OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The IPX transport domain. The corresponding transport
address is of type CiscoTAddressIPX."
::= { ciscoTDomains 9 }
ciscoTDomainSctpIpv4 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SCTP over IPv4 transport domain. The corresponding
transport address is of type CiscoTAddressIPv4."
REFERENCE
"RFC 2960 - Stream Control Transmission Protocol. R. Stewart,
Q. Xie, K. Morneault, C. Sharp, H. Schwarzbauer, T. Taylor,
I. Rytina, M. Kalla, L. Zhang, V. Paxson. October 2000."
::= { ciscoTDomains 10 }
ciscoTDomainSctpIpv6 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SCTP over IPv6 transport domain. The corresponding
transport address is of type CiscoTAddressIPv6 for global IPv6
addresses and CiscoTAddressIPv6s for scoped IPv6 addresses."
REFERENCE
"RFC 2960 - Stream Control Transmission Protocol. R. Stewart,
Q. Xie, K. Morneault, C. Sharp, H. Schwarzbauer, T. Taylor,
I. Rytina, M. Kalla, L. Zhang, V. Paxson. October 2000."
::= { ciscoTDomains 11 }
END