mirror of
https://github.com/librenms/librenms.git
synced 2024-10-07 16:52:45 +00:00
mibs for RTTMON/IPSLA/SAA and cleaned up discovery
git-svn-id: http://www.observium.org/svn/observer/trunk@435 61d68cd4-352d-0410-923a-c4978735b2b8
This commit is contained in:
Adam Amstrong
693
mibs/CISCO-ETHER-CFM-MIB.my
Normal file
693
mibs/CISCO-ETHER-CFM-MIB.my
Normal file
@@ -0,0 +1,693 @@
|
||||
--------------------------------------------------------------------
|
||||
-- CISCO-ETHER-CFM-MIB.my : Cisco Ethernet Connectivity Fault
|
||||
-- Management (CFM) MIB
|
||||
--
|
||||
-- December 2004, Samer Salam
|
||||
--
|
||||
-- Copyright (c) 2004-2006 by Cisco Systems, Inc.
|
||||
-- All rights reserved.
|
||||
-------------------------------------------------------------------
|
||||
|
||||
CISCO-ETHER-CFM-MIB DEFINITIONS ::= BEGIN
|
||||
|
||||
IMPORTS
|
||||
Gauge32,
|
||||
Unsigned32,
|
||||
MODULE-IDENTITY,
|
||||
NOTIFICATION-TYPE,
|
||||
OBJECT-TYPE
|
||||
FROM SNMPv2-SMI
|
||||
|
||||
SnmpAdminString
|
||||
FROM SNMP-FRAMEWORK-MIB
|
||||
|
||||
NOTIFICATION-GROUP,
|
||||
OBJECT-GROUP,
|
||||
MODULE-COMPLIANCE
|
||||
FROM SNMPv2-CONF
|
||||
|
||||
VlanId
|
||||
FROM Q-BRIDGE-MIB
|
||||
|
||||
TEXTUAL-CONVENTION,
|
||||
MacAddress,
|
||||
TimeStamp
|
||||
FROM SNMPv2-TC
|
||||
|
||||
ciscoMgmt
|
||||
FROM CISCO-SMI;
|
||||
|
||||
ciscoEtherCfmMIB MODULE-IDENTITY
|
||||
LAST-UPDATED "200412280000Z"
|
||||
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: cs-ethermibs@cisco.com"
|
||||
DESCRIPTION
|
||||
"This MIB module defines the managed objects
|
||||
and notifications for Ethernet Connectivity
|
||||
Fault Management (CFM).
|
||||
|
||||
CFM is an end-to-end per service instance Ethernet layer
|
||||
Operations, Administration and Management (OAM) protocol.
|
||||
|
||||
CFM events include:
|
||||
|
||||
- Maintenance End-Point (MEP) coming up: establishing
|
||||
connectivity
|
||||
|
||||
- Maintenance End-Point going down: losing connectivity
|
||||
|
||||
- Maintenance End-Point unknown: unexpected
|
||||
|
||||
- Maintenance End-Point missing: expected but not reachable
|
||||
|
||||
- Continuity Check Configuration Error: collision in MEP IDs
|
||||
|
||||
- Continuity Check Loop: forwarding loop in network
|
||||
|
||||
- Continuity Check Cross-connect: cross-connected
|
||||
forwarding path.
|
||||
|
||||
The following acronyms are used in this module:
|
||||
|
||||
- MEP: Maintenance End Point
|
||||
|
||||
- MEPID: Maintenance End Point Identifier
|
||||
|
||||
- CC: Continuity Check
|
||||
|
||||
- CCDB: Continuity Check Database
|
||||
|
||||
- SVLAN: Service Provider Virtual Local Area Network
|
||||
|
||||
- VLAN: Virtual Local Area Network
|
||||
|
||||
- CLI: Command Line Interface.
|
||||
|
||||
- OAM: Operations Administration and Management."
|
||||
REVISION "200412280000Z"
|
||||
DESCRIPTION
|
||||
"The initial revision of this MIB."
|
||||
::={ ciscoMgmt 461 }
|
||||
|
||||
ciscoEtherCfmMIBNotifs OBJECT IDENTIFIER ::= { ciscoEtherCfmMIB 0 }
|
||||
ciscoEtherCfmMIBObjects OBJECT IDENTIFIER ::= { ciscoEtherCfmMIB 1 }
|
||||
ciscoEtherCfmMIBConform OBJECT IDENTIFIER ::= { ciscoEtherCfmMIB 2 }
|
||||
|
||||
cecCfmEvents OBJECT IDENTIFIER ::= { ciscoEtherCfmMIBObjects 1 }
|
||||
|
||||
-- Textual Conventions
|
||||
|
||||
CfmMepid ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The identifier of a maintenance end point."
|
||||
SYNTAX Unsigned32 (0..8191)
|
||||
|
||||
-- MIB Object Definitions
|
||||
|
||||
cEtherCfmMaxEventIndex OBJECT-TYPE
|
||||
SYNTAX Unsigned32 (1..4294967295)
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This object specifies the maximum upper value supported
|
||||
for the cEtherCfmEventIndex index by this agent."
|
||||
::= { cecCfmEvents 1 }
|
||||
|
||||
cEtherCfmEventTable OBJECT-TYPE
|
||||
SYNTAX SEQUENCE OF CEtherCfmEventEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This table contains a collection of Ethernet CFM notifications
|
||||
generated by the device. The notifications correspond to events
|
||||
recognized by the device and fall into the following classes:
|
||||
|
||||
- MEP-Up
|
||||
|
||||
- MEP-Down
|
||||
|
||||
- Configuration Error
|
||||
|
||||
- Forwarding Loop
|
||||
|
||||
- Cross-connected Ethernet Connection
|
||||
|
||||
- Crosscheck Missing MEP
|
||||
|
||||
- Crosscheck Unknown MEP
|
||||
|
||||
- Crosscheck Service Up
|
||||
|
||||
A conceptual row is created in this table whenever the device
|
||||
encounters one of the events listed above. Rows can only be
|
||||
created by the agent, and not at the request of the management
|
||||
station.
|
||||
|
||||
Rows are deleted at the request of a management station by
|
||||
setting the cEtherCfmEventDeleteRow object to 'delete'.
|
||||
Another way of deleting rows is through the CLI.
|
||||
|
||||
Although this table may be indexed uniquely by the
|
||||
cEtherCfmEventIndex index, the first two indices
|
||||
(cEtherCfmEventDomainIndex and cEtherCfmEventSvlan) are used
|
||||
to speed-up queries per maintenance domain and per customer
|
||||
service instance. Furthermore, these two indices will help
|
||||
in defining the MIB views easily in order to restrict access
|
||||
to the MIB to particular entities (be it a service provider,
|
||||
or operator, or customer)."
|
||||
::= { cecCfmEvents 2 }
|
||||
|
||||
cEtherCfmEventEntry OBJECT-TYPE
|
||||
SYNTAX CEtherCfmEventEntry
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"An entry in this table is created for every event reported
|
||||
by Ethernet CFM."
|
||||
INDEX { cEtherCfmEventDomainIndex,
|
||||
cEtherCfmEventSvlan,
|
||||
cEtherCfmEventIndex }
|
||||
::= { cEtherCfmEventTable 1 }
|
||||
|
||||
CEtherCfmEventEntry ::= SEQUENCE {
|
||||
cEtherCfmEventDomainIndex Unsigned32,
|
||||
cEtherCfmEventSvlan VlanId,
|
||||
cEtherCfmEventIndex Unsigned32,
|
||||
cEtherCfmEventDomainName SnmpAdminString,
|
||||
cEtherCfmEventType INTEGER,
|
||||
cEtherCfmEventLastChange TimeStamp,
|
||||
cEtherCfmEventServiceId SnmpAdminString,
|
||||
cEtherCfmEventLclMepid CfmMepid,
|
||||
cEtherCfmEventLclMacAddress MacAddress,
|
||||
cEtherCfmEventLclMepCount Gauge32,
|
||||
cEtherCfmEventLclIfCount Gauge32,
|
||||
cEtherCfmEventRmtMepid CfmMepid,
|
||||
cEtherCfmEventRmtMacAddress MacAddress,
|
||||
cEtherCfmEventRmtPortState INTEGER,
|
||||
cEtherCfmEventRmtServiceId SnmpAdminString,
|
||||
cEtherCfmEventCode INTEGER,
|
||||
cEtherCfmEventDeleteRow INTEGER
|
||||
}
|
||||
|
||||
cEtherCfmEventDomainIndex OBJECT-TYPE
|
||||
SYNTAX Unsigned32 (1..4294967295)
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This object represents the ID which uniquely identifies
|
||||
a CFM maintenance domain on the device. Every domain can
|
||||
be uniquely identified by its user-defined
|
||||
name (cEtherCfmEventDomainName) or device-assigned ID (this
|
||||
object)."
|
||||
|
||||
::= { cEtherCfmEventEntry 1 }
|
||||
|
||||
cEtherCfmEventSvlan OBJECT-TYPE
|
||||
SYNTAX VlanId
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The service VLAN identifier of the customer service
|
||||
instance to which the event belongs."
|
||||
::= { cEtherCfmEventEntry 2 }
|
||||
|
||||
cEtherCfmEventIndex OBJECT-TYPE
|
||||
SYNTAX Unsigned32 (1..4294967295)
|
||||
MAX-ACCESS not-accessible
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A monotonically increasing integer for the sole purpose of
|
||||
indexing CFM events. When it reaches the maximum value
|
||||
supported by the agent, as defined in the
|
||||
cEtherCfmMaxEventIndex object, the agent wraps the value
|
||||
back to 1 and may flush existing entries."
|
||||
::= { cEtherCfmEventEntry 3 }
|
||||
|
||||
cEtherCfmEventDomainName OBJECT-TYPE
|
||||
SYNTAX SnmpAdminString
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The name of the CFM maintenance domain."
|
||||
::= { cEtherCfmEventEntry 4 }
|
||||
|
||||
cEtherCfmEventType OBJECT-TYPE
|
||||
SYNTAX INTEGER {
|
||||
mepUp(1),
|
||||
mepDown(2),
|
||||
xconnect(3),
|
||||
loop(4),
|
||||
config(5),
|
||||
xcheckMissing(6),
|
||||
xcheckUnknown(7),
|
||||
xcheckServiceUp(8)
|
||||
}
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This object informs the management station of how to interpret
|
||||
the rest of the objects within a row, as summarized in the
|
||||
following table:
|
||||
|
||||
Legend I: Ignored Object
|
||||
V: Valid Object
|
||||
|
||||
Object cEtherCfmEventType
|
||||
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8
|
||||
================================================================
|
||||
| | | | | | | |
|
||||
cEtherCfmEventDomainIndex | V | V | V | V | V | V | V | V
|
||||
| | | | | | | |
|
||||
cEtherCfmEventSvlan | V | V | V | V | V | V | V | V
|
||||
| | | | | | | |
|
||||
cEtherCfmEventIndex | V | V | V | V | V | V | V | V
|
||||
| | | | | | | |
|
||||
cEtherCfmEventLastChange | V | V | V | V | V | V | V | V
|
||||
| | | | | | | |
|
||||
cEtherCfmEventServiceId | V | V | V | V | V | V | V | V
|
||||
| | | | | | | |
|
||||
cEtherCfmEventDomainName | V | V | V | V | V | V | V | V
|
||||
| | | | | | | |
|
||||
cEtherCfmEventLclMepid | I | I | I | V | V | I | I | I
|
||||
| | | | | | | |
|
||||
cEtherCfmEventLclMacAddress | V | V | V | V | V | V | V | V
|
||||
| | | | | | | |
|
||||
cEtherCfmEventLclMepCount | V | V | I | I | I | I | I | I
|
||||
| | | | | | | |
|
||||
cEtherCfmEventLclIfCount | V | V | I | I | I | I | I | I
|
||||
| | | | | | | |
|
||||
cEtherCfmEventRmtMepid | V | V | V | I | I | V | V | I
|
||||
| | | | | | | |
|
||||
cEtherCfmEventRmtMacAddress | V | V | V | I | V | V | V | I
|
||||
| | | | | | | |
|
||||
cEtherCfmEventRmtPortState | V | I | I | I | I | I | I | I
|
||||
| | | | | | | |
|
||||
cEtherCfmEventRmtServiceId | I | I | V | I | I | I | I | I
|
||||
| | | | | | | |
|
||||
cEtherCfmEventCode | V | V | I | I | I | I | I | I
|
||||
| | | | | | | |
|
||||
cEtherCfmEventDeleteRow | V | V | V | V | V | V | V | V
|
||||
| | | | | | | |
|
||||
|
||||
Note: When reading any ignored object, a value of 0 will
|
||||
be returned by the agent."
|
||||
::= { cEtherCfmEventEntry 5 }
|
||||
|
||||
cEtherCfmEventLastChange OBJECT-TYPE
|
||||
SYNTAX TimeStamp
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The value of sysUpTime at the time when this row was created."
|
||||
::= { cEtherCfmEventEntry 6 }
|
||||
|
||||
cEtherCfmEventServiceId OBJECT-TYPE
|
||||
SYNTAX SnmpAdminString (SIZE(1..100))
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The customer service instance to which the event belongs."
|
||||
::= { cEtherCfmEventEntry 7 }
|
||||
|
||||
cEtherCfmEventLclMepid OBJECT-TYPE
|
||||
SYNTAX CfmMepid
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The identifier of the local MEP impacted by the event."
|
||||
::= { cEtherCfmEventEntry 8 }
|
||||
|
||||
cEtherCfmEventLclMacAddress OBJECT-TYPE
|
||||
SYNTAX MacAddress
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The MAC address of the device reporting the event."
|
||||
::= { cEtherCfmEventEntry 9 }
|
||||
|
||||
cEtherCfmEventLclMepCount OBJECT-TYPE
|
||||
SYNTAX Gauge32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of local MEPs affected by the event."
|
||||
::= { cEtherCfmEventEntry 10 }
|
||||
|
||||
cEtherCfmEventLclIfCount OBJECT-TYPE
|
||||
SYNTAX Gauge32
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The number of local interfaces affected by the event."
|
||||
::= { cEtherCfmEventEntry 11 }
|
||||
|
||||
cEtherCfmEventRmtMepid OBJECT-TYPE
|
||||
SYNTAX CfmMepid
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The maintenance end-point identifier of the remote
|
||||
MEP causing the event entry to be logged."
|
||||
::= { cEtherCfmEventEntry 12 }
|
||||
|
||||
cEtherCfmEventRmtMacAddress OBJECT-TYPE
|
||||
SYNTAX MacAddress
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The MAC address of the remote maintenance point for which
|
||||
the event entry is being logged."
|
||||
::= { cEtherCfmEventEntry 13 }
|
||||
|
||||
cEtherCfmEventRmtPortState OBJECT-TYPE
|
||||
SYNTAX INTEGER {
|
||||
up(1),
|
||||
down(2),
|
||||
adminDown(3),
|
||||
test(4),
|
||||
remoteExcessiveErrors(5),
|
||||
localExcessiveErrors(6),
|
||||
localNoData(7)
|
||||
}
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The operational state of the port on which the
|
||||
remote MEP is configured. This information is
|
||||
derived from the port-state as indicated in the
|
||||
CC message. The possible values are:
|
||||
|
||||
'up' - The port is operationally up.
|
||||
|
||||
'down' - The port is operationally (but not
|
||||
administratively) down.
|
||||
|
||||
'adminDown' - The port is administratively down.
|
||||
|
||||
'test' - The port is in test mode (perhaps
|
||||
due to an IEEE Standard 802.3ah OAM
|
||||
intrusive loopback operation).
|
||||
|
||||
'remoteExcessiveErrors' - 802.3ah OAM reports that the other
|
||||
end of the link is receiving an
|
||||
excessive number of invalid frames.
|
||||
|
||||
'localExcessiveErrors' - 802.3ah OAM reports that this end of
|
||||
the link is receiving an excessive
|
||||
number of invalid frames.
|
||||
|
||||
'localNoData' - No data and no CFM messages have been
|
||||
received for an excessive length of
|
||||
time."
|
||||
REFERENCE
|
||||
"IEEE 802.1ag Draft 1.0: Section 19.4.9.1 and
|
||||
IEEE 802.3ah-2004: Clause 57."
|
||||
::= { cEtherCfmEventEntry 14 }
|
||||
|
||||
cEtherCfmEventRmtServiceId OBJECT-TYPE
|
||||
SYNTAX SnmpAdminString (SIZE(1..100))
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The ID that the remote device has configured for the
|
||||
customer service instance (VLAN)."
|
||||
::= { cEtherCfmEventEntry 15 }
|
||||
|
||||
cEtherCfmEventCode OBJECT-TYPE
|
||||
SYNTAX INTEGER {
|
||||
new(1),
|
||||
returning(2),
|
||||
portState(3),
|
||||
lastGasp(4),
|
||||
timeout(5),
|
||||
configClear(6),
|
||||
loopClear(7),
|
||||
xconnectClear(8),
|
||||
unknownClear(9)
|
||||
}
|
||||
MAX-ACCESS read-only
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This object is used in decoding 'mepUp' and 'mepDown' events.
|
||||
|
||||
** For 'mepUp', the following codes are relevant:
|
||||
|
||||
'new' - This is the very first time the device
|
||||
receives a CC message from the remote MEP.
|
||||
|
||||
'returning' - The device received a CC message from a
|
||||
remote MEP for which it had an expired
|
||||
CCDB entry.
|
||||
|
||||
'portState' - The device received a CC message from a
|
||||
remote MEP for which it has a valid CCDB
|
||||
entry, and the message indicates a port
|
||||
status change.
|
||||
|
||||
** For 'mepDown', the following codes are relevant:
|
||||
|
||||
'lastGasp' - The device received a CC message from a
|
||||
remote MEP with zero lifetime.
|
||||
|
||||
'timeout' - The local CCDB entry for the remote MEP
|
||||
expired.
|
||||
|
||||
'configClear' - A previous CC message from a MEP that
|
||||
triggered a configuration error event
|
||||
is cleared.
|
||||
|
||||
'loopClear' - A previous CC message from a MEP that
|
||||
triggered a loop error event is cleared.
|
||||
|
||||
'xconnectClear' - A previous CC message from a MEP that
|
||||
triggered a crossconnect error event
|
||||
is cleared.
|
||||
|
||||
'unknownClear' - A previous CC message from a MEP that
|
||||
triggered an unknown MEP event is
|
||||
cleared."
|
||||
::= { cEtherCfmEventEntry 16 }
|
||||
|
||||
cEtherCfmEventDeleteRow OBJECT-TYPE
|
||||
SYNTAX INTEGER {
|
||||
noop(1),
|
||||
delete(2)
|
||||
}
|
||||
MAX-ACCESS read-write
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This object allows the management station to
|
||||
delete a row in the cEtherCfmEventTable in order
|
||||
to free system resources.
|
||||
|
||||
When reading this object the value of 'noop' will be
|
||||
returned. This object can only be set to 'delete'.
|
||||
|
||||
When this object is set to 'delete', the conceptual
|
||||
row corresponding to this object will be deleted to
|
||||
free system resources. This is equivalent to clearing
|
||||
the event log. Should the trigger that caused the event
|
||||
to be logged reoccur, the event will be re-asserted but
|
||||
in a different conceptual row."
|
||||
::= { cEtherCfmEventEntry 17 }
|
||||
|
||||
-- Notifications
|
||||
|
||||
ciscoEtherCfmNotificationPrefix OBJECT IDENTIFIER ::=
|
||||
{ ciscoEtherCfmMIBNotifs 0 }
|
||||
|
||||
cEtherCfmCcMepUp NOTIFICATION-TYPE
|
||||
OBJECTS {
|
||||
cEtherCfmEventServiceId,
|
||||
cEtherCfmEventLclMacAddress,
|
||||
cEtherCfmEventLclMepCount,
|
||||
cEtherCfmEventLclIfCount,
|
||||
cEtherCfmEventRmtMepid,
|
||||
cEtherCfmEventRmtMacAddress,
|
||||
cEtherCfmEventCode,
|
||||
cEtherCfmEventRmtPortState
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This notification is generated in the following cases:
|
||||
|
||||
- when a remote MEP first comes up, that is when we receive
|
||||
a CC message from that MEP for the first time.
|
||||
|
||||
- when the device receives a CC message from a MEP for which
|
||||
it has an expired CCDB entry.
|
||||
|
||||
- when a CC message is received for a remote MEP for which
|
||||
the device already has a CCDB entry and the port-state in
|
||||
the received CC message is different from the cached
|
||||
previous state."
|
||||
::= { ciscoEtherCfmNotificationPrefix 1 }
|
||||
|
||||
cEtherCfmCcMepDown NOTIFICATION-TYPE
|
||||
OBJECTS {
|
||||
cEtherCfmEventServiceId,
|
||||
cEtherCfmEventLclMacAddress,
|
||||
cEtherCfmEventLclMepCount,
|
||||
cEtherCfmEventLclIfCount,
|
||||
cEtherCfmEventRmtMepid,
|
||||
cEtherCfmEventRmtMacAddress,
|
||||
cEtherCfmEventCode
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This notification is generated when a remote MEP goes down;
|
||||
i.e. the entry in CCDB corresponding to this MEP times out
|
||||
or the device receives a CC message with zero hold-time."
|
||||
::= { ciscoEtherCfmNotificationPrefix 2 }
|
||||
|
||||
cEtherCfmCcCrossconnect NOTIFICATION-TYPE
|
||||
OBJECTS {
|
||||
cEtherCfmEventServiceId,
|
||||
cEtherCfmEventLclMacAddress,
|
||||
cEtherCfmEventRmtMepid,
|
||||
cEtherCfmEventRmtMacAddress,
|
||||
cEtherCfmEventRmtServiceId
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This notification is generated when a device receives a CC
|
||||
message with the service ID not matching the one locally
|
||||
configured for the VLAN in question."
|
||||
::= { ciscoEtherCfmNotificationPrefix 3 }
|
||||
|
||||
cEtherCfmCcLoop NOTIFICATION-TYPE
|
||||
OBJECTS {
|
||||
cEtherCfmEventServiceId,
|
||||
cEtherCfmEventLclMacAddress,
|
||||
cEtherCfmEventLclMepid
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This notification is generated when a device receives a CC
|
||||
message with the same MEPID and MAC address as those of
|
||||
the device itself, indicating that there is a forwarding
|
||||
loop and that the device is receiving its own CC messages."
|
||||
::= { ciscoEtherCfmNotificationPrefix 4 }
|
||||
|
||||
cEtherCfmCcConfigError NOTIFICATION-TYPE
|
||||
OBJECTS {
|
||||
cEtherCfmEventServiceId,
|
||||
cEtherCfmEventLclMacAddress,
|
||||
cEtherCfmEventLclMepid,
|
||||
cEtherCfmEventRmtMacAddress
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This notification is generated when a device receives a CC
|
||||
message with the same MEPID but different MAC address as
|
||||
those of the device itself, indicating that there is a
|
||||
mis-configuration in the network where a remote device
|
||||
has the same MEPID configured."
|
||||
::= { ciscoEtherCfmNotificationPrefix 5 }
|
||||
|
||||
cEtherCfmXCheckMissing NOTIFICATION-TYPE
|
||||
OBJECTS {
|
||||
cEtherCfmEventServiceId,
|
||||
cEtherCfmEventLclMacAddress,
|
||||
cEtherCfmEventRmtMepid,
|
||||
cEtherCfmEventRmtMacAddress
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This notification is generated when an expected
|
||||
(configured) MEP does not come up during the cross-check
|
||||
start timeout interval."
|
||||
::= { ciscoEtherCfmNotificationPrefix 6 }
|
||||
|
||||
cEtherCfmXCheckUnknown NOTIFICATION-TYPE
|
||||
OBJECTS {
|
||||
cEtherCfmEventServiceId,
|
||||
cEtherCfmEventLclMacAddress,
|
||||
cEtherCfmEventRmtMepid,
|
||||
cEtherCfmEventRmtMacAddress
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This notification is generated when an unexpected MEP
|
||||
comes up."
|
||||
::= { ciscoEtherCfmNotificationPrefix 7 }
|
||||
|
||||
cEtherCfmXCheckServiceUp NOTIFICATION-TYPE
|
||||
OBJECTS {
|
||||
cEtherCfmEventServiceId,
|
||||
cEtherCfmEventLclMacAddress
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"This notification is generated when all the MEPs belonging
|
||||
to a customer service instance come up before the expiration of
|
||||
the cross-check start timeout interval."
|
||||
::= { ciscoEtherCfmNotificationPrefix 8 }
|
||||
|
||||
ciscoEtherCfmMIBCompliances OBJECT IDENTIFIER ::=
|
||||
{ ciscoEtherCfmMIBConform 1 }
|
||||
ciscoEtherCfmMIBGroups OBJECT IDENTIFIER ::=
|
||||
{ ciscoEtherCfmMIBConform 2 }
|
||||
|
||||
-- Conformance
|
||||
ciscoEtherCfmMIBCompliance MODULE-COMPLIANCE
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Compliance statement for agents that support the Ethernet
|
||||
CFM MIB."
|
||||
MODULE
|
||||
MANDATORY-GROUPS {
|
||||
ciscoEtherCfmMIBEventGroup,
|
||||
ciscoEtherCfmMIBNotifGroup
|
||||
}
|
||||
::= { ciscoEtherCfmMIBCompliances 1 }
|
||||
|
||||
-- Units of Conformance
|
||||
ciscoEtherCfmMIBEventGroup OBJECT-GROUP
|
||||
OBJECTS {
|
||||
cEtherCfmMaxEventIndex,
|
||||
cEtherCfmEventDomainName,
|
||||
cEtherCfmEventType,
|
||||
cEtherCfmEventLastChange,
|
||||
cEtherCfmEventServiceId,
|
||||
cEtherCfmEventLclMepid,
|
||||
cEtherCfmEventLclMacAddress,
|
||||
cEtherCfmEventLclMepCount,
|
||||
cEtherCfmEventLclIfCount,
|
||||
cEtherCfmEventRmtMepid,
|
||||
cEtherCfmEventRmtMacAddress,
|
||||
cEtherCfmEventRmtPortState,
|
||||
cEtherCfmEventRmtServiceId,
|
||||
cEtherCfmEventCode,
|
||||
cEtherCfmEventDeleteRow
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Set of objects needed for CFM events."
|
||||
::= { ciscoEtherCfmMIBGroups 1 }
|
||||
|
||||
ciscoEtherCfmMIBNotifGroup NOTIFICATION-GROUP
|
||||
NOTIFICATIONS {
|
||||
cEtherCfmCcMepUp,
|
||||
cEtherCfmCcMepDown,
|
||||
cEtherCfmCcCrossconnect,
|
||||
cEtherCfmCcLoop,
|
||||
cEtherCfmCcConfigError,
|
||||
cEtherCfmXCheckMissing,
|
||||
cEtherCfmXCheckUnknown,
|
||||
cEtherCfmXCheckServiceUp
|
||||
}
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Set of notifications implemented in this module."
|
||||
::= { ciscoEtherCfmMIBGroups 2 }
|
||||
|
||||
END
|
||||
9301
mibs/CISCO-RTTMON-MIB.my
Normal file
9301
mibs/CISCO-RTTMON-MIB.my
Normal file
File diff suppressed because it is too large
Load Diff
736
mibs/CISCO-RTTMON-TC-MIB.my
Normal file
736
mibs/CISCO-RTTMON-TC-MIB.my
Normal file
@@ -0,0 +1,736 @@
|
||||
|
||||
-- *****************************************************************
|
||||
-- CISCO-RTTMON-TC-MIB.my: IP SLA Textual Conventions MIB file
|
||||
--
|
||||
-- August 2005, Katherine Yang
|
||||
--
|
||||
-- Copyright (c) 2005-2006 by cisco Systems, Inc.
|
||||
-- All rights reserved.
|
||||
--
|
||||
-- *****************************************************************
|
||||
|
||||
CISCO-RTTMON-TC-MIB DEFINITIONS ::= BEGIN
|
||||
|
||||
IMPORTS
|
||||
MODULE-IDENTITY,
|
||||
Integer32,
|
||||
Unsigned32
|
||||
FROM SNMPv2-SMI
|
||||
TEXTUAL-CONVENTION
|
||||
FROM SNMPv2-TC
|
||||
ciscoMgmt
|
||||
FROM CISCO-SMI;
|
||||
|
||||
|
||||
ciscoRttMonTCMIB MODULE-IDENTITY
|
||||
LAST-UPDATED "200608280000Z"
|
||||
ORGANIZATION "Cisco Systems, Inc."
|
||||
CONTACT-INFO
|
||||
"Cisco Systems, Inc.
|
||||
Customer Service
|
||||
|
||||
Postal: 170 W Tasman Drive
|
||||
San Jose, CA 95134
|
||||
|
||||
Tel: +1 800 553 NETS
|
||||
Email: cs-ipsla@cisco.com"
|
||||
DESCRIPTION
|
||||
"This MIB contains textual conventions used by
|
||||
CISCO-RTTMON-MIB, CISCO-RTTMON-RTP-MIB and
|
||||
CISCO-RTTMON-ICMP-MIB, but they are not limited
|
||||
to only these MIBs.
|
||||
These textual conventions were originally defined in
|
||||
CISCO-RTTMON-MIB.
|
||||
|
||||
Acronyms:
|
||||
FEC: Forward Equivalence Class
|
||||
LPD: Label Path Discovery
|
||||
LSP: Label Switched Path
|
||||
MPLS: Multi Protocol Label Switching
|
||||
RTT: Round Trip Time
|
||||
SAA: Service Assurance Agent
|
||||
VPN: Virtual Private Network
|
||||
CFM: Connection Fault Management"
|
||||
REVISION "200608110000Z"
|
||||
DESCRIPTION
|
||||
"Added RttMonIdLst and RttMonCtrlIndex textual conventions."
|
||||
REVISION "200607170000Z"
|
||||
DESCRIPTION
|
||||
"Added enumeration 'lspPingPseudowire' to RttMonRttType TC."
|
||||
REVISION "200603020000Z"
|
||||
DESCRIPTION
|
||||
"Added ethernetPing and ethernetJitter in RttMonRttType.
|
||||
Added ethernetPingAppl and ethernetJitterAppl
|
||||
in RttMonProtocol "
|
||||
REVISION "200508090000Z"
|
||||
DESCRIPTION
|
||||
"Initial version of this MIB module."
|
||||
::= { ciscoMgmt 485 }
|
||||
|
||||
|
||||
-- Textual Conventions
|
||||
|
||||
RttReset ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"When the value set to 'reset', the entire RTT application
|
||||
goes through a reset sequence, making a best
|
||||
effort to revert to its startup condition. At other times,
|
||||
the value is 'ready'."
|
||||
SYNTAX INTEGER {
|
||||
ready(1),
|
||||
reset(2)
|
||||
}
|
||||
|
||||
RttMonOperation ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The following are specific RTT operations for a
|
||||
particular probe type:
|
||||
notApplicable(0) - This object is not applicable for the
|
||||
probe type.
|
||||
httpGet(1) - HTTP get request
|
||||
httpRaw(2) - HTTP request with user defined payload
|
||||
ftpGet(3) - FTP get request
|
||||
ftpPassive(4) - FTP passive mode
|
||||
ftpActive(5) - FTP active mode
|
||||
voipDTAlertRinging(6) - Voip post dial delay detect point:
|
||||
Alerting / Ringing
|
||||
voipDTConnectOK(7) - Voip post dial delay detect point:
|
||||
Connect /OK"
|
||||
SYNTAX INTEGER {
|
||||
notApplicable(0),
|
||||
httpGet(1),
|
||||
httpRaw(2),
|
||||
ftpGet(3),
|
||||
ftpPassive(4),
|
||||
ftpActive(5),
|
||||
voipDTAlertRinging(6),
|
||||
voipDTConnectOK(7)
|
||||
}
|
||||
-- Operation completion sense code textual convention
|
||||
|
||||
RttResponseSense ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"These are the defined values for a completion status
|
||||
of a RTT operation.
|
||||
|
||||
other(0) - the operation is not started or completed
|
||||
or this object is not applicable for
|
||||
the probe type.
|
||||
ok(1) - a valid completion occurred and
|
||||
timed successfully
|
||||
disconnected(2) - the operation did not occur because
|
||||
the connection to the target
|
||||
was lost
|
||||
overThreshold(3) - a valid completion was received but
|
||||
the completion time exceeded a
|
||||
threshold value
|
||||
timeout(4) - an operation timed out; no completion
|
||||
time recorded
|
||||
busy(5) - the operation did not occur because a
|
||||
previous operation is still
|
||||
outstanding
|
||||
notConnected(6) - the operation did not occur because no
|
||||
connection (session) exists with the
|
||||
target
|
||||
dropped(7) - the operation did not occur due to lack
|
||||
of internal resource
|
||||
sequenceError(8) - a completed operation did not contain
|
||||
the correct sequence id; no completion
|
||||
time recorded
|
||||
verifyError(9) - a completed operation was received, but
|
||||
the data it contained did not match
|
||||
the expected data; no completion time
|
||||
recorded
|
||||
applicationSpecific(10)
|
||||
- the application generating the operation
|
||||
had a specific error
|
||||
dnsServerTimeout(11)
|
||||
- DNS Server Timeout
|
||||
tcpConnectTimeout(12)
|
||||
- TCP Connect Timeout
|
||||
httpTransactionTimeout(13)
|
||||
- HTTP Transaction Timeout
|
||||
dnsQueryError(14)
|
||||
- DNS Query error (because of unknown address
|
||||
etc.,)
|
||||
httpError(15)
|
||||
- HTTP Response StatusCode is not OK (200),
|
||||
or permenent redirect(301), temporary redirect
|
||||
(302) then HTTP error is set.
|
||||
error(16)
|
||||
- if there are socket failures or some other
|
||||
errors not relavant to the actual probe, they
|
||||
are recorded under this error
|
||||
mplsLspEchoTxError(17)
|
||||
- MPLS echo request transmission failure.
|
||||
mplsLspUnreachable(18)
|
||||
- MPLS Target FEC not reachable or unsupported
|
||||
mpls echo reply code.
|
||||
mplsLspMalformedReq(19)
|
||||
- MPLS echo request was malformalformed, pointed
|
||||
out by the reply router.
|
||||
mplsLspReachButNotFEC(20)
|
||||
- MPLS echo request processed by the downstream
|
||||
router but not the target."
|
||||
SYNTAX INTEGER {
|
||||
other(0),
|
||||
ok(1),
|
||||
disconnected(2),
|
||||
overThreshold(3),
|
||||
timeout(4),
|
||||
busy(5),
|
||||
notConnected(6),
|
||||
dropped(7),
|
||||
sequenceError(8),
|
||||
verifyError(9),
|
||||
applicationSpecific(10),
|
||||
dnsServerTimeout(11),
|
||||
tcpConnectTimeout(12),
|
||||
httpTransactionTimeout(13),
|
||||
dnsQueryError(14),
|
||||
httpError(15),
|
||||
error(16),
|
||||
mplsLspEchoTxError(17),
|
||||
mplsLspUnreachable(18),
|
||||
mplsLspMalformedReq(19),
|
||||
mplsLspReachButNotFEC(20)
|
||||
}
|
||||
-- Operation type textual convention
|
||||
|
||||
RttMonRttType ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Specifies the type of RTT operation to be performed.
|
||||
|
||||
The value 'echo' will cause the RTT application to
|
||||
perform a timed echo request/response operation directed
|
||||
at the 'RttMonTargetAddress'.
|
||||
|
||||
The value 'pathEcho' will cause the RTT application
|
||||
to perform path discovery to the 'RttMonTargetAddress',
|
||||
then it will perform a timed echo request/response
|
||||
operation directed at the each hop along the path.
|
||||
This operation will provide two types of information,
|
||||
first the path and second the time delay along the path.
|
||||
|
||||
NOTE: The 'pathEcho' time delay operation is a heuristic
|
||||
measurement because an intermediate hop may forward
|
||||
the different echo request/response at different
|
||||
rates. Thus the time delay difference between two
|
||||
hops along a path may contain very little 'true'
|
||||
statistical meaning.
|
||||
|
||||
The value 'fileIO' will cause the RTT application to
|
||||
write, read, or write/read a file to a preconfigured
|
||||
file server.
|
||||
|
||||
The value 'script' will cause the RTT application to
|
||||
execute a preconfigured script.
|
||||
|
||||
The value 'udpEcho' will cause the RTT application
|
||||
to perform a timed udp packet send/receive operation
|
||||
directed at the 'RttMonTargetAddress'.
|
||||
|
||||
The value 'tcpConnect' will cause the RTT application
|
||||
to perform a timed tcp connect operation directed at the
|
||||
'RttMonTargetAddress'.
|
||||
|
||||
The value 'http' will cause the RTT application
|
||||
to perform a download of the object specified in the URL.
|
||||
|
||||
The value 'dns' will cause the RTT application
|
||||
to perform a name lookup of an IP Address or a hostname.
|
||||
|
||||
The value 'jitter' will cause the RTT application
|
||||
to perform delay variance analysis.
|
||||
|
||||
The value 'dlsw' will cause the RTT application
|
||||
to perform a keepalive operation to measure the response
|
||||
time of a DLSw peer.
|
||||
|
||||
The value 'dhcp' will cause the RTT application
|
||||
to perform an IP Address lease request/teardown operation.
|
||||
|
||||
The value 'voip' will cause the RTT application
|
||||
to perform call set up operation to measure the response.
|
||||
|
||||
The value 'rtp' will cause the RTT application to perform
|
||||
delay variance analysis for RTP packet.
|
||||
|
||||
The value 'lspGroup' will cause the RTT application to logically
|
||||
group Label Switched Paths discovered as part of LSP Path
|
||||
Discovery to the target and perform an RTT operation end to end
|
||||
over each path in the Group. The type of operation configured
|
||||
is determined by rttMplsVpnMonCtrlRttType.
|
||||
|
||||
The value 'icmpjitter' will cause the RTT application
|
||||
to perform delay variance analysis using ICMP timestamp packets.
|
||||
|
||||
The value of 'lspPingIpv4' will cause the RTT application to
|
||||
perform ping over LSP path.
|
||||
|
||||
The value of 'lspTraceIpv4' will cause the RTT application to
|
||||
perform trace over LSP path.
|
||||
|
||||
The value of 'ethernetPing' will cause the RTT application to
|
||||
perform delay variance analysis using regular 802.1ag loopback frame.
|
||||
|
||||
The value of 'ethernetJitter' will cause the RTT application to
|
||||
perform delay variance analysis using CFM frame.
|
||||
|
||||
The value of 'lspPingPseudowire' will cause the RTT application to
|
||||
perform LSP Ping over Pseudowire and measure response time."
|
||||
SYNTAX INTEGER {
|
||||
echo(1),
|
||||
pathEcho(2),
|
||||
fileIO(3),
|
||||
script(4),
|
||||
udpEcho(5),
|
||||
tcpConnect(6),
|
||||
http(7),
|
||||
dns(8),
|
||||
jitter(9),
|
||||
dlsw(10),
|
||||
dhcp(11),
|
||||
ftp(12),
|
||||
voip(13),
|
||||
rtp(14),
|
||||
lspGroup(15),
|
||||
icmpjitter(16),
|
||||
lspPing(17),
|
||||
lspTrace(18),
|
||||
ethernetPing(19),
|
||||
ethernetJitter(20),
|
||||
lspPingPseudowire(21)
|
||||
}
|
||||
-- Operation type for Auto SAA L3 MPLS VPN textual convention
|
||||
|
||||
RttMplsVpnMonRttType ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Specifies the type of RTT operation to be performed for
|
||||
Auto SAA L3 MPLS VPN.
|
||||
|
||||
The value 'jitter' will cause the Auto SAA L3 MPLS VPN to
|
||||
automatically configure jitter operations.
|
||||
|
||||
The value 'echo' will cause the Auto SAA L3 MPLS VPN to
|
||||
automatically configure jitter operations.
|
||||
|
||||
The value 'pathEcho' will cause the Auto SAA L3 MPLS VPN to
|
||||
automatically configure jitter operations."
|
||||
SYNTAX INTEGER {
|
||||
jitter(1),
|
||||
echo(2),
|
||||
pathEcho(3)
|
||||
}
|
||||
-- --
|
||||
-- Auto SAA L3 MPLS VPN LSP Path Discovery
|
||||
-- Failure Cause textual convention
|
||||
|
||||
RttMplsVpnMonLpdFailureSense ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"These are the defined values for the causes of failure in
|
||||
LSP Path Discovery.
|
||||
|
||||
unknown(1) - The cause of failure for the
|
||||
LSP Path Discovery cannot be
|
||||
determined. The discovery for
|
||||
the target PE may not have
|
||||
started.
|
||||
noPath(2) - No paths were found to the
|
||||
target FEC while doing the
|
||||
LSP Path Discovery.
|
||||
allPathsBroken(3) - All paths to the target FEC
|
||||
are broken. This means an
|
||||
untagged interface on the LSP
|
||||
to the target.
|
||||
allPathsUnexplorable(4) - All paths to the target FEC are
|
||||
unexplorable. This identifies
|
||||
a case where there is some
|
||||
problem in reaching the next
|
||||
hop while doing Discovery.
|
||||
allPathsBrokenOrUnexplorable(5) - All paths to the target FEC are
|
||||
are either broken or
|
||||
unexplorable.
|
||||
timeout(6) - The LSP Path Discovery could
|
||||
not be completed for the
|
||||
target FEC within the
|
||||
configured time.
|
||||
error(7) - Error occurred while
|
||||
performing LSP Path Discovery.
|
||||
It might be also due to some
|
||||
reasons unrelated to LSP Path
|
||||
Discovery."
|
||||
SYNTAX INTEGER {
|
||||
unknown(1),
|
||||
noPath(2),
|
||||
allPathsBroken(3),
|
||||
allPathsUnexplorable(4),
|
||||
allPathsBrokenOrUnexplorable(5),
|
||||
timeout(6),
|
||||
error(7)
|
||||
}
|
||||
-- textual convention
|
||||
|
||||
RttMplsVpnMonLpdGrpStatus ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"These are the defined values for the status of the LPD Group.
|
||||
|
||||
unknown(1) - This indicates that some/all of the probes which are
|
||||
part of the LPD group have not completed even
|
||||
a single operation, so the group status cannot be
|
||||
identified.
|
||||
up(2) - This state indicates that all the probes which are
|
||||
part of the LPD group are up with latest return
|
||||
code as 'ok'.
|
||||
partial(3) - This state indicates that some probes are up and
|
||||
running fine and some are not 'ok'.
|
||||
down(4) - This state indicates that all the probes to the
|
||||
target are not running fine. This state indicates
|
||||
that there is connectivity problem to the target
|
||||
PE."
|
||||
SYNTAX INTEGER {
|
||||
unknown(1),
|
||||
up(2),
|
||||
partial(3),
|
||||
down(4)
|
||||
}
|
||||
|
||||
RttMonProtocol ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Specifies the protocol to be used to perform the timed
|
||||
echo request/response. The following protocols are
|
||||
defined:
|
||||
|
||||
NOTE: All protocols that end in 'Appl' will support
|
||||
the asymetric request/response (ARR) protocol.
|
||||
See the DESCRIPTION for ciscoRttMonMIB for a
|
||||
complete description of the asymetric
|
||||
request/response protocol.
|
||||
|
||||
notApplicable - no protocol is defined
|
||||
ipIcmpEcho - uses Echo Request/Reply as defined
|
||||
in RFC792 for Internet Protocol
|
||||
networks
|
||||
ipUdpEchoAppl - uses the UDP based echo server
|
||||
snaRUEcho - uses the REQECHO and ECHOTEST RU's
|
||||
to an SSCP over an SNA LU-SSCP
|
||||
session
|
||||
snaLU0EchoAppl - uses test RU's sent to the Echo
|
||||
Server over an SNA LU0-LU0 session
|
||||
snaLU2EchoAppl - uses test RU's sent to the Echo
|
||||
Server over an SNA LU2-LU2 session
|
||||
snaLU62Echo - uses the native appn ping ie. aping
|
||||
snaLU62EchoAppl - uses test RU's sent to the ARR
|
||||
Echo Server over an SNA LU6.2-LU6.2
|
||||
session
|
||||
appleTalkEcho - uses Echo Request/Reply as defined
|
||||
for appleTalk networks
|
||||
appleTalkEchoAppl - uses the appleTalk based echo
|
||||
server
|
||||
decNetEcho - uses Echo Request/Reply as defined
|
||||
for DECNet networks
|
||||
decNetEchoAppl - uses the DECnet based echo server
|
||||
ipxEcho - uses Echo Request/Reply as defined
|
||||
for Novell IPX networks
|
||||
ipxEchoAppl - uses the Novel IPX based echo
|
||||
server
|
||||
isoClnsEcho - uses Echo Request/Reply as defined
|
||||
for ISO CLNS networks
|
||||
isoClnsEchoAppl - uses the ISO CLNS based echo
|
||||
server
|
||||
vinesEcho - uses Echo Request/Reply as defined
|
||||
for VINES networks
|
||||
vinesEchoAppl - uses the VINES based echo server
|
||||
xnsEcho - uses Echo Request/Reply as defined
|
||||
for XNS networks
|
||||
xnsEchoAppl - uses the XNS based echo server
|
||||
apolloEcho - uses Echo Request/Reply as defined
|
||||
for APOLLO networks
|
||||
apolloEchoAppl - uses the APOLLO based echo
|
||||
server
|
||||
netbiosEchoAppl - uses the netbios based echo
|
||||
server
|
||||
ipTcpConn - uses the tcp's connect mechanism
|
||||
httpAppl - uses udp for name resolution,
|
||||
tcp connect and tcp data transfer
|
||||
mechanisms for HTTP data download
|
||||
from a particular HTTP Server
|
||||
dnsAppl - uses udp for name resolution
|
||||
jitterAppl - uses udp for packet transfers
|
||||
dlswAppl - uses tcp for sending keepalives
|
||||
dhcpAppl - uses udp for sending dhcp requests
|
||||
ftpAppl - uses tcp for connect & data transfer
|
||||
mplsLspPingAppl - uses MPLS Echo Request/Response as per
|
||||
draft-ietf-mpls-lsp-ping-04 ietf
|
||||
standard
|
||||
voipAppl - uses Symphony infrastructure to measure
|
||||
H.323/SIP call set up time
|
||||
rtpAppl - uses Symphony infrastructure to measure
|
||||
rtp packets delay variance.
|
||||
icmpJitterAppl - uses ICMP Timestamp for packet transfer
|
||||
to measure jitter.
|
||||
ethernetPingAppl - uses regular 802.1ag loopback frame
|
||||
ethernetJitterAppl - uses CFM frames ."
|
||||
SYNTAX INTEGER {
|
||||
notApplicable(1),
|
||||
ipIcmpEcho(2),
|
||||
ipUdpEchoAppl(3),
|
||||
snaRUEcho(4),
|
||||
snaLU0EchoAppl(5),
|
||||
snaLU2EchoAppl(6),
|
||||
snaLU62Echo(7),
|
||||
snaLU62EchoAppl(8),
|
||||
appleTalkEcho(9),
|
||||
appleTalkEchoAppl(10),
|
||||
decNetEcho(11),
|
||||
decNetEchoAppl(12),
|
||||
ipxEcho(13),
|
||||
ipxEchoAppl(14),
|
||||
isoClnsEcho(15),
|
||||
isoClnsEchoAppl(16),
|
||||
vinesEcho(17),
|
||||
vinesEchoAppl(18),
|
||||
xnsEcho(19),
|
||||
xnsEchoAppl(20),
|
||||
apolloEcho(21),
|
||||
apolloEchoAppl(22),
|
||||
netbiosEchoAppl(23),
|
||||
ipTcpConn(24),
|
||||
httpAppl(25),
|
||||
dnsAppl(26),
|
||||
jitterAppl(27),
|
||||
dlswAppl(28),
|
||||
dhcpAppl(29),
|
||||
ftpAppl(30),
|
||||
mplsLspPingAppl(31),
|
||||
voipAppl(32),
|
||||
rtpAppl(33),
|
||||
icmpJitterAppl(34),
|
||||
ethernetPingAppl(35),
|
||||
ethernetJitterAppl(36)
|
||||
}
|
||||
|
||||
RttMonCodecType ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Specifies the codec type to be used with the jitter probe.
|
||||
The following codec types are defined:
|
||||
|
||||
notApplicable - no CodecType is defined
|
||||
g711ulaw - uses G.711 U Law 64000 bps
|
||||
g711alaw - uses G.711 A Law 64000 bps
|
||||
g729a - uses G.729 8000 bps"
|
||||
SYNTAX INTEGER {
|
||||
notApplicable(0),
|
||||
g711ulaw(1),
|
||||
g711alaw(2),
|
||||
g729a(3)
|
||||
}
|
||||
|
||||
RttMonLSPPingReplyMode ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"Specifies the Reply mode for the MPLS LSP Echo request
|
||||
packets. The following reply modes are supported:
|
||||
|
||||
replyIpv4Udp(1) - an mpls echo request will normally
|
||||
have reply via IPv4 UDP packets.
|
||||
replyIpv4UdpRA(2) - reply via IPv4 UDP Router Alert. Used
|
||||
when IPv4 return path is deemed
|
||||
unreliable."
|
||||
SYNTAX INTEGER {
|
||||
replyIpv4Udp(1),
|
||||
replyIpv4UdpRA(2)
|
||||
}
|
||||
|
||||
RttMonTargetAddress ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A string which specifies the address of the target for
|
||||
the RTT operation; a value of RttMonTargetAddress
|
||||
which corresponds to a 'broadcast' address is disallowed.
|
||||
|
||||
The interpretation of this string depends on the type of
|
||||
RTT operation selected, as specified by RttMonProtocol;
|
||||
consequently, this object cannot be created until
|
||||
RttMonProtocol has been created (or must be in the same
|
||||
PDU).
|
||||
|
||||
SNA addresses will be provided in ASCII, but will be
|
||||
converted to EBCDIC
|
||||
|
||||
It is interpreted as follows, for the specified values of
|
||||
RttMonProtocol:
|
||||
|
||||
ipIcmpEcho, ipUdpEchoAppl, ipTcpConn, jitterAppl, dlswAppl,
|
||||
dnsAppl, httpAppl, and dhcpAppl
|
||||
- 4 octets
|
||||
|
||||
snaRUEcho
|
||||
- N octets, containing the value of the sna
|
||||
HOSTNAME of which the SSCP LU will be used
|
||||
for the operation. For many systems this value
|
||||
can be empty, and the system will use the
|
||||
implied SSCP LU. For example 'NSPECHO'.
|
||||
|
||||
snaLU0EchoAppl and snaLU2EchoAppl
|
||||
- N octets, the first x octets are the HOSTNAME
|
||||
(Alternatively, this could be a PU name defined
|
||||
to transport to the desired HOST), the second
|
||||
y octets are the APPLID, and the last z octets
|
||||
are the MODENAME of the Echo Server (blank
|
||||
for a MODENAME default). The address will be
|
||||
encoded with a size byte preceding each of
|
||||
the x y and z called s. For example sxsysz
|
||||
as in '0x06CWBC060x07NSPECHO0x00' where
|
||||
HOSTNAME = CWBC06, APPLID = NSPECHO, and
|
||||
MODENAME is defaulted to 8 blanks.
|
||||
NOTE: MODENAME is either size 0 or 8.
|
||||
|
||||
snaLU62Echo and snaLU62EchoAppl
|
||||
- N octets, the first x octets are the LU-NAME,
|
||||
the second y octets are the TP-NAME, and the
|
||||
last z octets are the MODENAME of the Echo
|
||||
Server. The address will be encoded with a size
|
||||
byte preceding each of the x y and z called s.
|
||||
For example sxsysz (zero size before z for a
|
||||
MODENAME default). The LU-NAME is composed of
|
||||
8 bytes '.' 8 bytes. The Transaction Program
|
||||
name (TP-NAME) is 1-64 bytes. The MODENAME
|
||||
is 8 bytes.
|
||||
|
||||
appleTalkEcho, appleTalkEchoAppl
|
||||
|
||||
decNetEcho, decNetEchoAppl
|
||||
|
||||
ipxEcho, ipxEchoAppl
|
||||
|
||||
isoClnsEcho, isoClnsEchoAppl
|
||||
|
||||
vinesEcho, vinesEchoAppl
|
||||
|
||||
xnsEcho, xnsEchoAppl
|
||||
apolloEcho, apolloEchoAppl
|
||||
|
||||
netbiosEchoAppl, voipAppl
|
||||
- unsupported protocols.
|
||||
|
||||
mplsLspPingAppl
|
||||
- 8 octets, the first 4 octets are the FEC address
|
||||
and the next 4 octets are the FEC address mask."
|
||||
SYNTAX OCTET STRING
|
||||
|
||||
RttMonReactVar ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The following are specific Reaction variables for a
|
||||
particular probe type:
|
||||
rtt(1) - Round Trip Time
|
||||
jitterSDAvg(2) - Jitter average from source to Destination
|
||||
jitterDSAvg(3) - Jitter average from destination to source
|
||||
packetLossSD(4) - Packet loss from source to destination
|
||||
packetLossDS(5) - Packet loss from destination to source
|
||||
mos(6) - Mean Opinion Score
|
||||
timeout(7) - Timeout of the Operation
|
||||
connectionLoss(8) - Connection Failed to the destination
|
||||
verifyError(9) - Data corruption occurs
|
||||
jitterAvg(10) - Jitter Average in both the directions
|
||||
icpif(11) - Calculated Planning Impairment Factor
|
||||
packetMIA(12) - Missing In Action
|
||||
packetLateArrival(13) - Packets arriving Late
|
||||
packetOutOfSequence(14) - Packets arriving out of sequence
|
||||
maxOfPositiveSD(15) - Maximum positive jitter from
|
||||
Source to Destination
|
||||
maxOfNegativeSD(16) - Maximum negative jitter from
|
||||
Source to Destination
|
||||
maxOfPositiveDS(17) - Maximum positive jitter from
|
||||
Destination to Source
|
||||
maxOfNegativeDS(18) - Maximum negative jitter from
|
||||
Destination to Source.
|
||||
iaJitterDS(19) - Inter arrival jitter from
|
||||
Destination to Source
|
||||
frameLossDS(20) - Number of frame loss recorded
|
||||
at source DSP
|
||||
mosLQDS(21) - Listener quality MOS at Source
|
||||
mosCQDS(22) - Conversational quality MOS at source
|
||||
rFactorDS(23) - R-Factor value at Destination.
|
||||
successivePacketLoss(24)- Successive Dropped Packet
|
||||
maxOfLatencyDS(25) - Maximum Latency from Destination
|
||||
to Source
|
||||
maxOfLatencySD(26) - Maximum Latency from Source
|
||||
to Destination
|
||||
latencyDSAvg(27) - Latency average from Destination
|
||||
to Source
|
||||
latencySDAvg(28) - Latency average from Source
|
||||
to Destination
|
||||
packetLoss(29) - Packets loss in both directions
|
||||
iaJitterSD(30) - Inter arrival jitter from
|
||||
Source to Destination
|
||||
mosCQSD(31) - Conversational quality MOS at
|
||||
Destination
|
||||
rFactorSD(32) - R-Factor value at Destination."
|
||||
SYNTAX INTEGER {
|
||||
rtt(1),
|
||||
jitterSDAvg(2),
|
||||
jitterDSAvg(3),
|
||||
packetLossSD(4),
|
||||
packetLossDS(5),
|
||||
mos(6),
|
||||
timeout(7),
|
||||
connectionLoss(8),
|
||||
verifyError(9),
|
||||
jitterAvg(10),
|
||||
icpif(11),
|
||||
packetMIA(12),
|
||||
packetLateArrival(13),
|
||||
packetOutOfSequence(14),
|
||||
maxOfPositiveSD(15),
|
||||
maxOfNegativeSD(16),
|
||||
maxOfPositiveDS(17),
|
||||
maxOfNegativeDS(18),
|
||||
iaJitterDS(19),
|
||||
frameLossDS(20),
|
||||
mosLQDS(21),
|
||||
mosCQDS(22),
|
||||
rFactorDS(23),
|
||||
successivePacketLoss(24),
|
||||
maxOfLatencyDS(25),
|
||||
maxOfLatencySD(26),
|
||||
latencyDSAvg(27),
|
||||
latencySDAvg(28),
|
||||
packetLoss(29),
|
||||
iaJitterSD(30),
|
||||
mosCQSD(31),
|
||||
rFactorSD(32)
|
||||
}
|
||||
|
||||
RttMonIdLst ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"A string that specifies a list of the IP SLA probe
|
||||
identifiers or other numeric identifiers.
|
||||
The identifiers will be specified in the following form.
|
||||
(a) Individual identifiers with comma separated as 1,5,3.
|
||||
(b) Range form including hyphens with multiple ranges
|
||||
being
|
||||
separated by comma as 1-10,12-34.
|
||||
(c) Mix of the above two forms as 1,2,4-10,12,15,19-25."
|
||||
SYNTAX OCTET STRING (SIZE (0..255))
|
||||
|
||||
RttMonCtrlIndex ::= TEXTUAL-CONVENTION
|
||||
STATUS current
|
||||
DESCRIPTION
|
||||
"The value of this object identifies the row in the
|
||||
ipslaEthernetGrpCtrlTable and ipslaEthernetGrpReactTable.
|
||||
It can be used for other IP SLA control tables."
|
||||
SYNTAX Unsigned32 (1..2147483647 )
|
||||
|
||||
END
|
||||
Reference in New Issue
Block a user