This module defines a MIB for Round Trip Time
(RTT) monitoring of a list of targets, using a
variety of protocols.
The table structure overview is a follows (t:
indicates a table, at: indicates an augmented
table, and it: indicates table with the same
indices/control as parent table):
RTTMON MIB
|
| |
| |
| |
| |t
| |
| |t
| |
| |t
| |
| |
| |
| |t
|
|
| |t
| | |
| | |
| | |it- Echo Specific Configuration
| | |it- Echo Path Hop Address Configuration
| | |it- File I/O Specific Configuration
| | |it- Script Specific Configuration
| | |at- Schedule Configuration
| | |at- Reaction Specific Config
| | |at- Statistics Capture Configuration
| | |at- History Collection Configuration
| | |at- Monitoring Operational State
| | |at- Last RTT operation
| |
| |t
| |at- Reaction Trigger Operational State
|
|
| |t
| |
| |
| |
| |
| |it- Statistics Collection Table
| |it- Statistics Totals Table
| |t
| |t
|
|
| |t
| |
| |
|
|
| |t
| |t
DEFINITIONS:
conceptual RTT control row -
This is a row in the 'Overall Control
Group'. This row is indexed via the
rttMonCtrlAdminIndex object. This row
is spread across multiple real tables
in the 'Overall Control Group'.
probe -
This is the entity that executes via a
conceptual RTT control row and populates
a conceptual statistics row and a
conceptual history row.
Rtt operation -
This is a single operation performed by
a probe. This operation can be a single
Rtt attempt/completion or a group of Rtt
attempts/completions that produce one
operation table entry.
ARR Protocol Definition:
The format of the RTT Asymmetric Request/Responses
(ARR) protocol is as follows:
The ARR Header (total of 12 octets):
4 octet -> eyecatcher: 'WxYz'
1 octet -> version : 0x01 - protocol version
1 octet -> command : 0x01 - logoff request
0x02 - echo request
0x03 - echo response
0x04 - software version request
0x05 - software version response
2 octet -> sequence number (Network Byte Order)
4 octet -> response data size (Network Byte Order)
The ARR Data:
n octets -> request/response data
: 'AB..ZAB..ZAB..'
For software version request/response the
protocol version octet will contain the version
number of the responder. Thus the sequence
number, etc will not be included.
For snaLU0EchoAppl and snaLU2EchoAppl all character
fields will be in EBCDIC.
The response data should be appended to the
origin request data. This allows data
verification to check the data that flows in
both directions. If the response data size is
smaller than the request data size the original
request data will be truncated.
An example would be:
Request: / Response:
'WxYz' / 'WxYz'
0x01 / 0x01
0x02 / 0x03
0x0001 / 0x0001
0x00000008 / 0x00000008
'ABCDEF' / 'ABCDEFGH'
NOTE: We requested 8 bytes in the response and
the response had 8 bytes. The size of the
request data has no correlation to the
size of the response data.
NOTE: For native RTT request/response (i.e.
ipIcmpecho) operations both the 'Header'
and 'Data' will be included. Only the
'sequence number' in the Header will be
valid.
NOTE: For non-connection oriented protocol the
initial RTT request/response operation will
be preceded with an RTT request/response
operation to the target address to force
path exploration and to prove
connectivity. The History collection table
will contain these responses, but the
Statistics capture table will omit them to
prevent skewed results.
Parsed from file CISCO-RTTMON-MIB.mib
Module: CISCO-RTTMON-MIB
ciscoRttMonMIB MODULE-IDENTITY
LAST-UPDATED "9903110000Z"
ORGANIZATION "Cisco IBU Engineering Working Group"
CONTACT-INFO
"Cisco Systems, Inc.
Customer Service
Postal: 170 W Tasman Drive
San Jose, CA 95134
Tel: +1 800 553 NETS
[email protected]"
DESCRIPTION
"This module defines a MIB for Round Trip Time
(RTT) monitoring of a list of targets, using a
variety of protocols.
The table structure overview is a follows (t:
indicates a table, at: indicates an augmented
table, and it: indicates table with the same
indices/control as parent table):
RTTMON MIB
|--- Application Group
| |--- Application Identity
| |--- Application Capabilities
| |--- Application Reset
| |t-- Supported RTT Types
| |--- Truth Value
| |t-- Supported Protocols
| |--- Truth Value
| |t-- Application Preconfigured
| |--- Script Names
| |--- File Paths
|
|--- Overall Control Group
| |t-- Master Definitions Table
| | |--- Global Configuration Definitions
| | |--- Config for a single RTT Life
| | |it- Echo Specific Configuration
| | |it- Echo Path Hop Address Configuration
| | |it- File I/O Specific Configuration
| | |it- Script Specific Configuration
| | |at- Schedule Configuration
| | |at- Reaction Specific Config
| | |at- Statistics Capture Configuration
| | |at- History Collection Configuration
| | |at- Monitoring Operational State
| | |at- Last RTT operation
| |
| |t-- Reaction Trigger Table
| |at- Reaction Trigger Operational State
|
|--- Statistics Collection Group
| |t-- Statistics Capture Table
| |--- Captured Statistics
| |--- Path Information
| |--- Distribution Capture
| |--- Mean and Deviation Capture
| |it- Statistics Collection Table
| |it- Statistics Totals Table
| |t-- HTTP Stats Table
| |t-- Jitter Stats Table
|
|--- History Collection Group
| |t-- History Collection Table
| |-- Path Information
| |-- Completion Information per operation
|
|--- Latest Operation Group
| |t-- Latest HTTP Oper Table
| |t-- Latest Jitter Oper Table
DEFINITIONS:
conceptual RTT control row -
This is a row in the Overall Control
Group. This row is indexed via the
rttMonCtrlAdminIndex object. This row
is spread across multiple real tables
in the Overall Control Group.
probe -
This is the entity that executes via a
conceptual RTT control row and populates
a conceptual statistics row and a
conceptual history row.
Rtt operation -
This is a single operation performed by
a probe. This operation can be a single
Rtt attempt/completion or a group of Rtt
attempts/completions that produce one
operation table entry.
ARR Protocol Definition:
The format of the RTT Asymmetric Request/Responses
(ARR) protocol is as follows:
The ARR Header (total of 12 octets):
4 octet -> eyecatcher: WxYz
1 octet -> version : 0x01 - protocol version
1 octet -> command : 0x01 - logoff request
0x02 - echo request
0x03 - echo response
0x04 - software version request
0x05 - software version response
2 octet -> sequence number (Network Byte Order)
4 octet -> response data size (Network Byte Order)
The ARR Data:
n octets -> request/response data
: AB..ZAB..ZAB..
For software version request/response the
protocol version octet will contain the version
number of the responder. Thus the sequence
number, etc will not be included.
For snaLU0EchoAppl and snaLU2EchoAppl all character
fields will be in EBCDIC.
The response data should be appended to the
origin request data. This allows data
verification to check the data that flows in
both directions. If the response data size is
smaller than the request data size the original
request data will be truncated.
An example would be:
Request: / Response:
WxYz / WxYz
0x01 / 0x01
0x02 / 0x03
0x0001 / 0x0001
0x00000008 / 0x00000008
ABCDEF / ABCDEFGH
NOTE: We requested 8 bytes in the response and
the response had 8 bytes. The size of the
request data has no correlation to the
size of the response data.
NOTE: For native RTT request/response (i.e.
ipIcmpecho) operations both the Header
and Data will be included. Only the
sequence number in the Header will be
valid.
NOTE: For non-connection oriented protocol the
initial RTT request/response operation will
be preceded with an RTT request/response
operation to the target address to force
path exploration and to prove
connectivity. The History collection table
will contain these responses, but the
Statistics capture table will omit them to
prevent skewed results."
REVISION "9903110000Z"
DESCRIPTION "the following modifications are done in the MIB
(a) new tables created
- rttMonLatestHTTPOperTable
- rttMonLatestJitterOperTable
- rttMonHTTPStatsTable
- rttMonJitterStatsTable
(b) some columns added to rttMonEchoAdminTable and
(c) some objects obsoleted"
View at oid-info.com
This module defines a MIB for Round Trip Time
(RTT) monitoring of a list of targets, using a
variety of protocols.
The table structure overview is a follows (t:
indicates a table, at: indicates an augmented
table, and it: indicates table with the same
indices/control as parent table):
RTTMON MIB
|
| |
| |
| |
| |t
| |
| |t
| |
| |t
| |
| |
| |
| |t
|
|
| |t
| | |
| | |
| | |it- Echo Specific Configuration
| | |it- Echo Path Hop Address Configuration
| | |it- File I/O Specific Configuration
| | |it- Script Specific Configuration
| | |at- Schedule Configuration
| | |at- Reaction Specific Config
| | |at- Statistics Capture Configuration
| | |at- History Collection Configuration
| | |at- Monitoring Operational State
| | |at- Last RTT operation
| |
| |t
| |at- Reaction Trigger Operational State
|
|
| |t
| |
| |
| |
| |
| |it- Statistics Collection Table
| |it- Statistics Totals Table
| |t
| |t
|
|
| |t
| |
| |
|
|
| |t
| |t
DEFINITIONS:
conceptual RTT control row -
This is a row in the 'Overall Control
Group'. This row is indexed via the
rttMonCtrlAdminIndex object. This row
is spread across multiple real tables
in the 'Overall Control Group'.
probe -
This is the entity that executes via a
conceptual RTT control row and populates
a conceptual statistics row and a
conceptual history row.
Rtt operation -
This is a single operation performed by
a probe. This operation can be a single
Rtt attempt/completion or a group of Rtt
attempts/completions that produce one
operation table entry.
ARR Protocol Definition:
The format of the RTT Asymmetric Request/Responses
(ARR) protocol is as follows:
The ARR Header (total of 12 octets):
4 octet -> eyecatcher: 'WxYz'
1 octet -> version : 0x01 - protocol version
1 octet -> command : 0x01 - logoff request
0x02 - echo request
0x03 - echo response
0x04 - software version request
0x05 - software version response
2 octet -> sequence number (Network Byte Order)
4 octet -> response data size (Network Byte Order)
The ARR Data:
n octets -> request/response data
: 'AB..ZAB..ZAB..'
For software version request/response the
protocol version octet will contain the version
number of the responder. Thus the sequence
number, etc will not be included.
For snaLU0EchoAppl and snaLU2EchoAppl all character
fields will be in EBCDIC.
The response data should be appended to the
origin request data. This allows data
verification to check the data that flows in
both directions. If the response data size is
smaller than the request data size the original
request data will be truncated.
An example would be:
Request: / Response:
'WxYz' / 'WxYz'
0x01 / 0x01
0x02 / 0x03
0x0001 / 0x0001
0x00000008 / 0x00000008
'ABCDEF' / 'ABCDEFGH'
NOTE: We requested 8 bytes in the response and
the response had 8 bytes. The size of the
request data has no correlation to the
size of the response data.
NOTE: For native RTT request/response (i.e.
ipIcmpecho) operations both the 'Header'
and 'Data' will be included. Only the
'sequence number' in the Header will be
valid.
NOTE: For non-connection oriented protocol the
initial RTT request/response operation will
be preceded with an RTT request/response
operation to the target address to force
path exploration and to prove
connectivity. The History collection table
will contain these responses, but the
Statistics capture table will omit them to
prevent skewed results.
Parsed from file cisco-rttmon.mib.txt
Company: None
Module: CISCO-RTTMON-MIB
This module defines a MIB for Round Trip Time
(RTT) monitoring of a list of targets, using a
variety of protocols.
The table structure overview is a follows (t:
indicates a table, at: indicates an augmented
table, and it: indicates table with the same
indices/control as parent table):
RTTMON MIB
|
| |
| |
| |
| |t
| |
| |t
| |
| |t
| |
| |
| |
| |t
|
|
| |t
| | |
| | |
| | |it- Echo Specific Configuration
| | |it- Echo Path Hop Address Configuration
| | |it- File I/O Specific Configuration
| | |it- Script Specific Configuration
| | |at- Schedule Configuration
| | |at- Reaction Specific Config
| | |at- Statistics Capture Configuration
| | |at- History Collection Configuration
| | |at- Monitoring Operational State
| | |at- Last RTT operation
| |
| |t
| |at- Reaction Trigger Operational State
|
|
| |t
| |
| |
| |
| |
| |it- Statistics Collection Table
| |it- Statistics Totals Table
| |t
| |t
|
|
| |t
| |
| |
|
|
| |t
| |t
DEFINITIONS:
conceptual RTT control row -
This is a row in the 'Overall Control
Group'. This row is indexed via the
rttMonCtrlAdminIndex object. This row
is spread across multiple real tables
in the 'Overall Control Group'.
probe -
This is the entity that executes via a
conceptual RTT control row and populates
a conceptual statistics row and a
conceptual history row.
Rtt operation -
This is a single operation performed by
a probe. This operation can be a single
Rtt attempt/completion or a group of Rtt
attempts/completions that produce one
operation table entry.
ARR Protocol Definition:
The format of the RTT Asymmetric Request/Responses
(ARR) protocol is as follows:
The ARR Header (total of 12 octets):
4 octet -> eyecatcher: 'WxYz'
1 octet -> version : 0x01 - protocol version
1 octet -> command : 0x01 - logoff request
0x02 - echo request
0x03 - echo response
0x04 - software version request
0x05 - software version response
2 octet -> sequence number (Network Byte Order)
4 octet -> response data size (Network Byte Order)
The ARR Data:
n octets -> request/response data
: 'AB..ZAB..ZAB..'
For software version request/response the
protocol version octet will contain the version
number of the responder. Thus the sequence
number, etc will not be included.
For snaLU0EchoAppl and snaLU2EchoAppl all character
fields will be in EBCDIC.
The response data should be appended to the
origin request data. This allows data
verification to check the data that flows in
both directions. If the response data size is
smaller than the request data size the original
request data will be truncated.
An example would be:
Request: / Response:
'WxYz' / 'WxYz'
0x01 / 0x01
0x02 / 0x03
0x0001 / 0x0001
0x00000008 / 0x00000008
'ABCDEF' / 'ABCDEFGH'
NOTE: We requested 8 bytes in the response and
the response had 8 bytes. The size of the
request data has no correlation to the
size of the response data.
NOTE: For native RTT request/response (i.e.
ipIcmpecho) operations both the 'Header'
and 'Data' will be included. Only the
'sequence number' in the Header will be
valid.
NOTE: For non-connection oriented protocol the
initial RTT request/response operation will
be preceded with an RTT request/response
operation to the target address to force
path exploration and to prove
connectivity. The History collection table
will contain these responses, but the
Statistics capture table will omit them to
prevent skewed results.
ciscoRttMonMIB MODULE-IDENTITY LAST-UPDATED "201006110000Z" ORGANIZATION "Cisco IOS" CONTACT-INFO "Cisco Systems, Inc. Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 Tel: +1 800 553 NETS [email protected]" DESCRIPTION "This module defines a MIB for Round Trip Time (RTT) monitoring of a list of targets, using a variety of protocols. The table structure overview is a follows (t: indicates a table, at: indicates an augmented table, and it: indicates table with the same indices/control as parent table): RTTMON MIB | | | | | | | | |t | | | |t | | | |t | | | | | | | |t | | | |t | | | | | | | | |it- Echo Specific Configuration | | |it- Echo Path Hop Address Configuration | | |it- File I/O Specific Configuration | | |it- Script Specific Configuration | | |at- Schedule Configuration | | |at- Reaction Specific Config | | |at- Statistics Capture Configuration | | |at- History Collection Configuration | | |at- Monitoring Operational State | | |at- Last RTT operation | | | |t | |at- Reaction Trigger Operational State | | | |t | | | | | | | | | |it- Statistics Collection Table | |it- Statistics Totals Table | |t | |t | | | |t | | | | | | | |t | |t DEFINITIONS: conceptual RTT control row - This is a row in the 'Overall Control Group'. This row is indexed via the rttMonCtrlAdminIndex object. This row is spread across multiple real tables in the 'Overall Control Group'. probe - This is the entity that executes via a conceptual RTT control row and populates a conceptual statistics row and a conceptual history row. Rtt operation - This is a single operation performed by a probe. This operation can be a single Rtt attempt/completion or a group of Rtt attempts/completions that produce one operation table entry. ARR Protocol Definition: The format of the RTT Asymmetric Request/Responses (ARR) protocol is as follows: The ARR Header (total of 12 octets): 4 octet -> eyecatcher: 'WxYz' 1 octet -> version : 0x01 - protocol version 1 octet -> command : 0x01 - logoff request 0x02 - echo request 0x03 - echo response 0x04 - software version request 0x05 - software version response 2 octet -> sequence number (Network Byte Order) 4 octet -> response data size (Network Byte Order) The ARR Data: n octets -> request/response data : 'AB..ZAB..ZAB..' For software version request/response the protocol version octet will contain the version number of the responder. Thus the sequence number, etc will not be included. For snaLU0EchoAppl and snaLU2EchoAppl all character fields will be in EBCDIC. The response data should be appended to the origin request data. This allows data verification to check the data that flows in both directions. If the response data size is smaller than the request data size the original request data will be truncated. An example would be: Request: / Response: 'WxYz' / 'WxYz' 0x01 / 0x01 0x02 / 0x03 0x0001 / 0x0001 0x00000008 / 0x00000008 'ABCDEF' / 'ABCDEFGH' NOTE: We requested 8 bytes in the response and the response had 8 bytes. The size of the request data has no correlation to the size of the response data. NOTE: For native RTT request/response (i.e. ipIcmpecho) operations both the 'Header' and 'Data' will be included. Only the 'sequence number' in the Header will be valid. NOTE: For non-connection oriented protocol the initial RTT request/response operation will be preceded with an RTT request/response operation to the target address to force path exploration and to prove connectivity. The History collection table will contain these responses, but the Statistics capture table will omit them to prevent skewed results." REVISION "201006040000Z" DESCRIPTION "Changes added for video operation: -Added new MIB object rttMonEchoAdminVideoTrafficProfile -Changed the maximum range of rttMonEchoAdminCallDuration to 600 -Changed the minimum range of rttMonEchoAdminCallDuration to 1 from 10" REVISION "200904070000Z" DESCRIPTION "- Added rttMonEchoAdminTargetMEPPort object in rttMonEchoAdminEntry." REVISION "200803240000Z" DESCRIPTION "- Added nine new objects rttMonLatestJitterOperRTTSumHigh, rttMonLatestJitterOperRTTSum2High, rttMonLatestJitterOperOWSumSDHigh, rttMonLatestJitterOperOWSum2SDHigh, rttMonLatestJitterOperOWSumDSHigh, rttMonLatestJitterOperOWSum2DSHigh, rttMonJitterStatsRTTSumHigh, rttMonJitterStatsOWSumSDHigh, rttMonJitterStatsOWSumDSHigh. - Modified the unit and the description of rttMonLatestRttOperCompletionTime, rttMonJitterStatsRTTSum, rttMonJitterStatsOWSumSD, rttMonJitterStatsOWSumDS, rttMonLatestJitterOperRTTSum, rttMonLatestJitterOperRTTSum2, rttMonLatestJitterOperOWSumSD, rttMonLatestJitterOperOWSumDS, rttMonLatestJitterOperOWSum2SD, rttMonLatestJitterOperOWSum2DS." REVISION "200801060000Z" DESCRIPTION "Added a new object rttMonEchoAdminTargetEVC." REVISION "200612080000Z" DESCRIPTION "Added a new object rttMonCtrlAdminGroupName to support the auto measure project. Group Name will be shown for auto generated operations." REVISION "200606080000Z" DESCRIPTION "Added a new rttMonRttType named as lspPingPseudowire. Added an object rttMonEchoAdminLSPVccvID to support lspPingPseudowire. Change the default value of rttMplsVpnMonTypeLpdScanPeriod from 1 to 240." REVISION "200603020000Z" DESCRIPTION "Added two new rttMonRttType's ethernetPing and ethernetJitter. Added four objects rttMonEchoAdminTargetMPID, rttMonEchoAdminTargetVLAN, rttMonEchoAdminTargetDomainName and rttMonEchoAdminEthernetCOS in rttMonEchoAdminEntry to support ethernetPing and ethernetJitter. Change the default value of rttMplsVpnMonTypeLpdScanPeriod from 0 to 1. Modified the range of rttMonApplProbeCapacity and rttMonApplNumCtrlAdminEntry to 1 .. 2147483647. Modified the range of rttMonLatestJitterOperMOS, rttMonJitterStatsMinOfMOS and rttMonJitterStatsMaxOfMOS to (0|100 .. 500). Modified the SYNTAX of rttMonCtrlAdminOwner to OCTET STRING because OwnerString is deprecated." REVISION "200508110000Z" DESCRIPTION "- TEXTUAL Conventions previously defined in the MIB are defined in CISCO-RTTMON-TC-MIB." REVISION "200504210000Z" DESCRIPTION "- Added new objects given in ciscoCtrlGroupRev4 to rttMonGrpScheduleAdminTable. - Changed description of object rttMonHTTPStatsRTTMax." REVISION "200501040000Z" DESCRIPTION "Added two new rttMonRttType's rtp and lspGroup. Added a new object rttMonApplLpdGrpStatsReset to reset the LPD Group Stats. Added rttMonLpdGrpStatsTable for supporting LSP Path Discovery. Added two new notifications rttMonLpdDiscoveryNotification and rttMonLpdGrpStatusNotification. Added and modified descriptions of some objects in rttMplsVpnMonCtrlTable, rttMplsVpnMonTypeTable and rttMplsVpnMonReactTable for LSP Path Discovery. Added 6 options in the rttMonReactVar. Added rttMonEchoAdminSourceVoicePort and rttMonEchoAdminCallDuration in rttMonEchoAdminTable." REVISION "200408260000Z" DESCRIPTION "Added a table rttMonReactTable, which defines the the reaction configurations for the probes. Deprecated the old reaction table rttMonReactAdminTable. This is replaced by the new table (rttMonReactTable). Depreacted the notification types rttMonConnectionChangeNotification rttMonTimeoutNotification rttMonThresholdNotification rttMonVerifyErrorNotification Added new notification type rttMonNotification. Added two objects, rttMonGrpScheduleAdminFreqMax and rttMonGrpScheduleAdminFreqMin to table rttMonGrpScheduleAdminTable." REVISION "200405180000Z" DESCRIPTION "- Add the following fields for VoIP GK registration delay: RttMonEchoAdminEntry: rttMonEchoAdminGKRegistration - Add the following fields for VoIP Post dial delay: RttMonOperation: voipDTAlertRinging(6), voipDTConnectOK(7) RttMonRttType: voip(13) RttMonProtocol: voipAppl(31) RttMonEchoAdminEntry: rttMonEchoAdminCalledNumber rttMonEchoAdminDetectPoint - Add HTTP code 301, 302 as non-error scenario. - Modify description for rttMonEchoAdminNameServer: it is applicable for DNS and HTTP probe. - Modify rttMonCtrlAdminFrequency range from Integer32 (0..604800) to (1..604800) - Added following new objects for jitter probe precision and other improvements: rttMonEchoAdminPrecision, rttMonEchoAdminProbePakPriority, rttMonJitterStatsIAJOut, rttMonJitterStatsIAJIn, rttMonJitterStatsAvgJitter, rttMonJitterStatsAvgJitterSD, rttMonJitterStatsAvgJitterDS, rttMonJitterStatsUnSyncRTs, rttMonLatestJitterOperIAJIn, rttMonLatestJitterOperAvgJitter, rttMonLatestJitterOperAvgSDJ, rttMonLatestJitterOperAvgDSJ, rttMonLatestJitterOperOWAvgSD, rttMonLatestJitterOperOWAvgDS, rttMonLatestJitterOperIAJOut, rttMonLatestJitterOperNTPState, rttMonEchoAdminOWNTPSyncTolAbs, rttMonEchoAdminOWNTPSyncTolPct, rttMonEchoAdminOWNTPSyncTolType, rttMonLatestJitterOperUNSyncRTs" REVISION "200401200000Z" DESCRIPTION "Created new tables for Auto SAA L3 MPLS VPN. rttMplsVpnMonCtrlTable rttMplsVpnMonTypeTable rttMplsVpnMonScheduleTable rttMplsVpnMonReactTable. Modified MIB for creation of echo and pathecho operations based on MPLS LSP Ping." REVISION "200308110000Z" DESCRIPTION "Added 1 object rttMonScheduleAdminRttRecurring to the rttMonScheduleAdminTable. Added a new table rttMonGrpScheduleAdminTable for group scheduling. This table contains the following objects rttMonGrpScheduleAdminIndex rttMonGrpScheduleAdminProbes rttMonGrpScheduleAdminPeriod rttMonGrpScheduleAdminFrequency rttMonGrpScheduleAdminLife rttMonGrpScheduleAdminAgeout rttMonGrpScheduleAdminStatus. Modified the default value of rttMonReactTriggerAdminStatus from createAndGo to no default value. Corrected the Revision clause specified for the existing and all the earlier submissions." REVISION "200305210000Z" DESCRIPTION "Range for rttMonLatestJitterOperMOS, rttMonJitterStatsMinOfMOS and rttMonJitterStatsMaxOfMOS to be changed to 100..500 instead of 1..5. Modifying the range of rttMonApplProbeCapacity and rttMonApplNumCtrlAdminEntry to 1..10000.Added value other(0) for RttResponseSense and changed the range of objects rttMonLatestRttOperApplSpecificSense and rttMonHistoryCollectionApplSpecificSense to 0..2147483647. Added range for rttMonApplAuthIndex." REVISION "200304150000Z" DESCRIPTION "Removed default values from rttMonEchoAdminCodecInterval rttMonEchoAdminCodecPayload rttMonEchoAdminCodecNumPackets. Corrected some typos in the earliar revision." REVISION "200303120000Z" DESCRIPTION "Added 5 objects in the rttMonEchoAdminTable to support codec configuration. Added few objects in rttMonLatestJitterOperTable and rttMonJitterStatsTable for ICPIF (Calculated Planning Impairment Factor) and MOS (Mean Opinion Score) scores." REVISION "200011030000Z" DESCRIPTION "deprecated 4 objects in the rttMonJitterStatsTable and added the same objects with a SYNTAX of Gauge32. Also added the capability to specify a VrfName." REVISION "9906150000Z" DESCRIPTION "created rttMonAuthTable." ::= { ciscoMgmt 42 }
ciscoRttMonMIB OBJECT IDENTIFIER ::= { ciscoMgmt 42 }
Automatically extracted from Cisco "SNMP v2 MIBs".
ciscoRttMonMIB MODULE-IDENTITY LAST-UPDATED "200504210000Z" ORGANIZATION "Cisco IOS" CONTACT-INFO "Cisco Systems, Inc. Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 Tel: +1 800 553 NETS [email protected]" DESCRIPTION "This module defines a MIB for Round Trip Time (RTT) monitoring of a list of targets, using a variety of protocols. The table structure overview is a follows (t: indicates a table, at: indicates an augmented table, and it: indicates table with the same indices/control as parent table): RTTMON MIB | | | | | | | | |t | | | |t | | | |t | | | | | | | |t | | | |t | | | | | | | | |it- Echo Specific Configuration | | |it- Echo Path Hop Address Configuration | | |it- File I/O Specific Configuration | | |it- Script Specific Configuration | | |at- Schedule Configuration | | |at- Reaction Specific Config | | |at- Statistics Capture Configuration | | |at- History Collection Configuration | | |at- Monitoring Operational State | | |at- Last RTT operation | | | |t | |at- Reaction Trigger Operational State | | | |t | | | | | | | | | |it- Statistics Collection Table | |it- Statistics Totals Table | |t | |t | | | |t | | | | | | | |t | |t DEFINITIONS: conceptual RTT control row - This is a row in the 'Overall Control Group'. This row is indexed via the rttMonCtrlAdminIndex object. This row is spread across multiple real tables in the 'Overall Control Group'. probe - This is the entity that executes via a conceptual RTT control row and populates a conceptual statistics row and a conceptual history row. Rtt operation - This is a single operation performed by a probe. This operation can be a single Rtt attempt/completion or a group of Rtt attempts/completions that produce one operation table entry. ARR Protocol Definition: The format of the RTT Asymmetric Request/Responses (ARR) protocol is as follows: The ARR Header (total of 12 octets): 4 octet -> eyecatcher: 'WxYz' 1 octet -> version : 0x01 - protocol version 1 octet -> command : 0x01 - logoff request 0x02 - echo request 0x03 - echo response 0x04 - software version request 0x05 - software version response 2 octet -> sequence number (Network Byte Order) 4 octet -> response data size (Network Byte Order) The ARR Data: n octets -> request/response data : 'AB..ZAB..ZAB..' For software version request/response the protocol version octet will contain the version number of the responder. Thus the sequence number, etc will not be included. For snaLU0EchoAppl and snaLU2EchoAppl all character fields will be in EBCDIC. The response data should be appended to the origin request data. This allows data verification to check the data that flows in both directions. If the response data size is smaller than the request data size the original request data will be truncated. An example would be: Request: / Response: 'WxYz' / 'WxYz' 0x01 / 0x01 0x02 / 0x03 0x0001 / 0x0001 0x00000008 / 0x00000008 'ABCDEF' / 'ABCDEFGH' NOTE: We requested 8 bytes in the response and the response had 8 bytes. The size of the request data has no correlation to the size of the response data. NOTE: For native RTT request/response (i.e. ipIcmpecho) operations both the 'Header' and 'Data' will be included. Only the 'sequence number' in the Header will be valid. NOTE: For non-connection oriented protocol the initial RTT request/response operation will be preceded with an RTT request/response operation to the target address to force path exploration and to prove connectivity. The History collection table will contain these responses, but the Statistics capture table will omit them to prevent skewed results." REVISION "200504210000Z" DESCRIPTION "- Added following enumerations to RttMonRttType TC lspTrace, lspPing and icmpjitter. - Added following enumerations to RttMonReactVar TC: successivePacketLoss, maxOfLatencyDS, maxOfLatencySD, latencyDSAvg, latencySDAvg, packetLoss, iaJitterSD, mosCQSD and rFactorSD. - Added following new tables: rttMonLatestIcmpJitterOperTable and rttMonIcmpJitterStatsTable. ICMP Jitter operations are initiated in rttMonCtrlAdminTable. - Added new objects given in ciscoStatsGroupRev9 to rttMonLatestRtpOperTable, rttMonRtpStatsTable to support Source to Destination direction statistics. - Added new objects given in ciscoCtrlGroupRev4 to rttMonGrpScheduleAdminTable. - Changed description of object rttMonHTTPStatsRTTMax." REVISION "200501040000Z" DESCRIPTION "Added two new rttMonRttType's rtp and lspGroup. Added a new object rttMonApplLpdGrpStatsReset to reset the LPD Group Stats. Added rttMonLpdGrpStatsTable for supporting LSP Path Discovery. Added two new notifications rttMonLpdDiscoveryNotification and rttMonLpdGrpStatusNotification. Added and modified descriptions of some objects in rttMplsVpnMonCtrlTable, rttMplsVpnMonTypeTable and rttMplsVpnMonReactTable for LSP Path Discovery. Added rttMonLatestRtpOperTable and rttMonRtpStatsTable statistics table for rtp. Added 6 options in the rttMonReactVar. Added rttMonEchoAdminSourceVoicePort and rttMonEchoAdminCallDuration in rttMonEchoAdminTable." REVISION "200408260000Z" DESCRIPTION "Added a table rttMonReactTable, which defines the the reaction configurations for the probes. Deprecated the old reaction table rttMonReactAdminTable. This is replaced by the new table (rttMonReactTable). Depreacted the notification types rttMonConnectionChangeNotification rttMonTimeoutNotification rttMonThresholdNotification rttMonVerifyErrorNotification Added new notification type rttMonNotification. Added two objects, rttMonGrpScheduleAdminFreqMax and rttMonGrpScheduleAdminFreqMin to table rttMonGrpScheduleAdminTable." REVISION "200405180000Z" DESCRIPTION "- Add the following fields for VoIP GK registration delay: RttMonEchoAdminEntry: rttMonEchoAdminGKRegistration - Add the following fields for VoIP Post dial delay: RttMonOperation: voipDTAlertRinging(6), voipDTConnectOK(7) RttMonRttType: voip(13) RttMonProtocol: voipAppl(31) RttMonEchoAdminEntry: rttMonEchoAdminCalledNumber rttMonEchoAdminDetectPoint - Add HTTP code 301, 302 as non-error scenario. - Modify description for rttMonEchoAdminNameServer: it is applicable for DNS and HTTP probe. - Modify rttMonCtrlAdminFrequency range from Integer32 (0..604800) to (1..604800) - Added following new objects for jitter probe precision and other improvements: rttMonEchoAdminPrecision, rttMonEchoAdminProbePakPriority, rttMonJitterStatsIAJOut, rttMonJitterStatsIAJIn, rttMonJitterStatsAvgJitter, rttMonJitterStatsAvgJitterSD, rttMonJitterStatsAvgJitterDS, rttMonJitterStatsUnSyncRTs, rttMonLatestJitterOperIAJIn, rttMonLatestJitterOperAvgJitter, rttMonLatestJitterOperAvgSDJ, rttMonLatestJitterOperAvgDSJ, rttMonLatestJitterOperOWAvgSD, rttMonLatestJitterOperOWAvgDS, rttMonLatestJitterOperIAJOut, rttMonLatestJitterOperNTPState, rttMonEchoAdminOWNTPSyncTolAbs, rttMonEchoAdminOWNTPSyncTolPct, rttMonEchoAdminOWNTPSyncTolType, rttMonLatestJitterOperUNSyncRTs" REVISION "200401200000Z" DESCRIPTION "Created new tables for Auto SAA L3 MPLS VPN. rttMplsVpnMonCtrlTable rttMplsVpnMonTypeTable rttMplsVpnMonScheduleTable rttMplsVpnMonReactTable. Modified MIB for creation of echo and pathecho operations based on MPLS LSP Ping." REVISION "200308110000Z" DESCRIPTION "Added 1 object rttMonScheduleAdminRttRecurring to the rttMonScheduleAdminTable. Added a new table rttMonGrpScheduleAdminTable for group scheduling. This table contains the following objects rttMonGrpScheduleAdminIndex rttMonGrpScheduleAdminProbes rttMonGrpScheduleAdminPeriod rttMonGrpScheduleAdminFrequency rttMonGrpScheduleAdminLife rttMonGrpScheduleAdminAgeout rttMonGrpScheduleAdminStatus. Modified the default value of rttMonReactTriggerAdminStatus from createAndGo to no default value. Corrected the Revision clause specified for the existing and all the earlier submissions." REVISION "200305210000Z" DESCRIPTION "Range for rttMonLatestJitterOperMOS, rttMonJitterStatsMinOfMOS and rttMonJitterStatsMaxOfMOS to be changed to 100..500 instead of 1..5. Modifying the range of rttMonApplProbeCapacity and rttMonApplNumCtrlAdminEntry to 1..10000.Added value other(0) for RttResponseSense and changed the range of objects rttMonLatestRttOperApplSpecificSense and rttMonHistoryCollectionApplSpecificSense to 0..2147483647. Added range for rttMonApplAuthIndex. " REVISION "200304150000Z" DESCRIPTION "Removed default values from rttMonEchoAdminCodecInterval rttMonEchoAdminCodecPayload rttMonEchoAdminCodecNumPackets. Corrected some typos in the earliar revision." REVISION "200303120000Z" DESCRIPTION "Added 5 objects in the rttMonEchoAdminTable to support codec configuration. Added few objects in rttMonLatestJitterOperTable and rttMonJitterStatsTable for ICPIF (Calculated Planning Impairment Factor) and MOS (Mean Opinion Score) scores." REVISION "200011030000Z" DESCRIPTION "deprecated 4 objects in the rttMonJitterStatsTable and added the same objects with a SYNTAX of Gauge32. Also added the capability to specify a VrfName." REVISION "9906150000Z" DESCRIPTION "created rttMonAuthTable." ::= { ciscoMgmt 42 }
ciscoRttMonMIB MODULE-IDENTITY LAST-UPDATED "201604140000Z" ORGANIZATION "Cisco IOS" CONTACT-INFO "Cisco Systems, Inc. Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 Tel: +1 800 553 NETS [email protected]" DESCRIPTION "This module defines a MIB for Round Trip Time (RTT) monitoring of a list of targets, using a variety of protocols. The table structure overview is a follows (t: indicates a table, at: indicates an augmented table, and it: indicates table with the same indices/control as parent table): RTTMON MIB | | | | | | | | |t | | | |t | | | |t | | | | | | | |t | | | |t | | | | | | | | |it- Echo Specific Configuration | | |it- Echo Path Hop Address Configuration | | |it- File I/O Specific Configuration | | |it- Script Specific Configuration | | |at- Schedule Configuration | | |at- Reaction Specific Config | | |at- Statistics Capture Configuration | | |at- History Collection Configuration | | |at- Monitoring Operational State | | |at- Last RTT operation | | | |t | |at- Reaction Trigger Operational State | | | |t | | | | | | | | | |it- Statistics Collection Table | |it- Statistics Totals Table | |t | |t | | | |t | | | | | | | |t | |t DEFINITIONS: conceptual RTT control row - This is a row in the 'Overall Control Group'. This row is indexed via the rttMonCtrlAdminIndex object. This row is spread across multiple real tables in the 'Overall Control Group'. probe - This is the entity that executes via a conceptual RTT control row and populates a conceptual statistics row and a conceptual history row. Rtt operation - This is a single operation performed by a probe. This operation can be a single Rtt attempt/completion or a group of Rtt attempts/completions that produce one operation table entry. ARR Protocol Definition: The format of the RTT Asymmetric Request/Responses (ARR) protocol is as follows: The ARR Header (total of 12 octets): 4 octet -> eyecatcher: 'WxYz' 1 octet -> version : 0x01 - protocol version 1 octet -> command : 0x01 - logoff request 0x02 - echo request 0x03 - echo response 0x04 - software version request 0x05 - software version response 2 octet -> sequence number (Network Byte Order) 4 octet -> response data size (Network Byte Order) The ARR Data: n octets -> request/response data : 'AB..ZAB..ZAB..' For software version request/response the protocol version octet will contain the version number of the responder. Thus the sequence number, etc will not be included. For snaLU0EchoAppl and snaLU2EchoAppl all character fields will be in EBCDIC. The response data should be appended to the origin request data. This allows data verification to check the data that flows in both directions. If the response data size is smaller than the request data size the original request data will be truncated. An example would be: Request: / Response: 'WxYz' / 'WxYz' 0x01 / 0x01 0x02 / 0x03 0x0001 / 0x0001 0x00000008 / 0x00000008 'ABCDEF' / 'ABCDEFGH' NOTE: We requested 8 bytes in the response and the response had 8 bytes. The size of the request data has no correlation to the size of the response data. NOTE: For native RTT request/response (i.e. ipIcmpecho) operations both the 'Header' and 'Data' will be included. Only the 'sequence number' in the Header will be valid. NOTE: For non-connection oriented protocol the initial RTT request/response operation will be preceded with an RTT request/response operation to the target address to force path exploration and to prove connectivity. The History collection table will contain these responses, but the Statistics capture table will omit them to prevent skewed results." REVISION "201604140000Z" DESCRIPTION "Refined rttMonCtrlAdminFrequency range in the new compliance statement from Integer32 (0..604800) to (1..604800). This change was advertised in revision 200405180000Z but was not implemented. Refined range for the following port objects to exclude value 0 rttMonEchoAdminTargetPort, rttMonEchoAdminSourcePort, rttMonEchoAdminEmulateSourcePort, rttMonEchoAdminEmulateTargetPort Added following objects to support random start-time feature for scheduling group and sla probes. rttMonScheduleAdminStartType, rttMonScheduleAdminStartDelay, rttMonGrpScheduleAdminStartType, rttMonGrpScheduleAdminStartDelay Added following objects to report over threshold statistics for jitter probes rttMonLatestJitterOperNumOverThresh, rttMonJitterStatsNumOverThresh Deprecated rttMonCtrlAdminTag and replaced with rttMonCtrlAdminLongTag Added new compliance ciscoRttMonMibComplianceRev23." REVISION "201404100000Z" DESCRIPTION "Added following objects for Fabric Path Echo probe rttMonEchoAdminTargetSwitchId, rttMonEchoAdminProfileId, rttMonEchoAdminOutputInterface Added new compliance ciscoRttMonMibComplianceRev22." REVISION "201208160000Z" DESCRIPTION "Added following objects to support Y1731 Synthetic Loss Measurement rttMonEchoAdminEnableBurst, rttMonEchoAdminAggBurstCycles, rttMonEchoAdminLossRatioNumFrames, rttMonEchoAdminAvailNumFrames Added following object to support improving accuracy for jitter probes measurement. rttMonEchoAdminTstampOptimization Deprecated rttMonScheduleAdminConceptRowAgeout and replace with rttMonScheduleAdminConceptRowAgeoutV2. Deprecated rttMonControlEnableErrors, rttMonStatsRetrieveErrors and replace with rttMonStatsCollectCtrlEnErrors, rttMonStatsCollectRetrieveErrors. Modified the descriptions for rttMonLatestJitterOperMOS rttMonLatestJitterOperICPIF, rttMonJitterStatsMinOfMOS rttMonJitterStatsMinOfICPIF, rttMonJitterStatsMaxOfMOS rttMonJitterStatsMaxOfICPIF Added new compliance ciscoRttMonMibComplianceRev21." REVISION "201109150000Z" DESCRIPTION "Added following objects to rttMonEchoAdmin to support Y1731 extensions. - rttMonEchoAdminTargetMacAddress, - rttMonEchoAdminSourceMacAddress and - rttMonEchoAdminSourceMPID" REVISION "201102210000Z" DESCRIPTION "Added four new objects rttMonEchoAdminEmulateSourceAddress, rttMonEchoAdminEmulateSourcePort, rttMonEchoAdminEmulateTargetAddress, rttMonEchoAdminEmulateTargetPort to RttMonEchoAdminEntry." REVISION "201010180000Z" DESCRIPTION "Added three new objects rttMonEchoAdminDscp, rttMonEchoAdminReserveDsp, rttMonEchoAdminInputInterface" REVISION "201006040000Z" DESCRIPTION "Changes added for video operation: -Added new MIB object rttMonEchoAdminVideoTrafficProfile -Changed the maximum range of rttMonEchoAdminCallDuration to 600 -Changed the minimum range of rttMonEchoAdminCallDuration to 1 from 10" REVISION "200904070000Z" DESCRIPTION "- Added rttMonEchoAdminTargetMEPPort object in rttMonEchoAdminEntry." REVISION "200803240000Z" DESCRIPTION "- Added nine new objects rttMonLatestJitterOperRTTSumHigh, rttMonLatestJitterOperRTTSum2High, rttMonLatestJitterOperOWSumSDHigh, rttMonLatestJitterOperOWSum2SDHigh, rttMonLatestJitterOperOWSumDSHigh, rttMonLatestJitterOperOWSum2DSHigh, rttMonJitterStatsRTTSumHigh, rttMonJitterStatsOWSumSDHigh, rttMonJitterStatsOWSumDSHigh. - Modified the unit and the description of rttMonLatestRttOperCompletionTime, rttMonJitterStatsRTTSum, rttMonJitterStatsOWSumSD, rttMonJitterStatsOWSumDS, rttMonLatestJitterOperRTTSum, rttMonLatestJitterOperRTTSum2, rttMonLatestJitterOperOWSumSD, rttMonLatestJitterOperOWSumDS, rttMonLatestJitterOperOWSum2SD, rttMonLatestJitterOperOWSum2DS." REVISION "200801060000Z" DESCRIPTION "Added a new object rttMonEchoAdminTargetEVC." REVISION "200612080000Z" DESCRIPTION "Added a new object rttMonCtrlAdminGroupName to support the auto measure project. Group Name will be shown for auto generated operations." REVISION "200606080000Z" DESCRIPTION "Added a new rttMonRttType named as lspPingPseudowire. Added an object rttMonEchoAdminLSPVccvID to support lspPingPseudowire. Change the default value of rttMplsVpnMonTypeLpdScanPeriod from 1 to 240." REVISION "200603020000Z" DESCRIPTION "Added two new rttMonRttType's ethernetPing and ethernetJitter. Added four objects rttMonEchoAdminTargetMPID, rttMonEchoAdminTargetVLAN, rttMonEchoAdminTargetDomainName and rttMonEchoAdminEthernetCOS in rttMonEchoAdminEntry to support ethernetPing and ethernetJitter. Change the default value of rttMplsVpnMonTypeLpdScanPeriod from 0 to 1. Modified the range of rttMonApplProbeCapacity and rttMonApplNumCtrlAdminEntry to 1 .. 2147483647. Modified the range of rttMonLatestJitterOperMOS, rttMonJitterStatsMinOfMOS and rttMonJitterStatsMaxOfMOS to (0|100 .. 500). Modified the SYNTAX of rttMonCtrlAdminOwner to OCTET STRING because OwnerString is deprecated." REVISION "200508110000Z" DESCRIPTION "- TEXTUAL Conventions previously defined in the MIB are defined in CISCO-RTTMON-TC-MIB." REVISION "200504210000Z" DESCRIPTION "- Added new objects given in ciscoCtrlGroupRev4 to rttMonGrpScheduleAdminTable. - Changed description of object rttMonHTTPStatsRTTMax." REVISION "200501040000Z" DESCRIPTION "Added two new rttMonRttType's rtp and lspGroup. Added a new object rttMonApplLpdGrpStatsReset to reset the LPD Group Stats. Added rttMonLpdGrpStatsTable for supporting LSP Path Discovery. Added two new notifications rttMonLpdDiscoveryNotification and rttMonLpdGrpStatusNotification. Added and modified descriptions of some objects in rttMplsVpnMonCtrlTable, rttMplsVpnMonTypeTable and rttMplsVpnMonReactTable for LSP Path Discovery. Added 6 options in the rttMonReactVar. Added rttMonEchoAdminSourceVoicePort and rttMonEchoAdminCallDuration in rttMonEchoAdminTable." REVISION "200408260000Z" DESCRIPTION "Added a table rttMonReactTable, which defines the the reaction configurations for the probes. Deprecated the old reaction table rttMonReactAdminTable. This is replaced by the new table (rttMonReactTable). Depreacted the notification types rttMonConnectionChangeNotification rttMonTimeoutNotification rttMonThresholdNotification rttMonVerifyErrorNotification Added new notification type rttMonNotification. Added two objects, rttMonGrpScheduleAdminFreqMax and rttMonGrpScheduleAdminFreqMin to table rttMonGrpScheduleAdminTable." REVISION "200405180000Z" DESCRIPTION "- Add the following fields for VoIP GK registration delay: RttMonEchoAdminEntry: rttMonEchoAdminGKRegistration - Add the following fields for VoIP Post dial delay: RttMonOperation: voipDTAlertRinging(6), voipDTConnectOK(7) RttMonRttType: voip(13) RttMonProtocol: voipAppl(31) RttMonEchoAdminEntry: rttMonEchoAdminCalledNumber rttMonEchoAdminDetectPoint - Add HTTP code 301, 302 as non-error scenario. - Modify description for rttMonEchoAdminNameServer: it is applicable for DNS and HTTP probe. - Modify rttMonCtrlAdminFrequency range from Integer32 (0..604800) to (1..604800) - Added following new objects for jitter probe precision and other improvements: rttMonEchoAdminPrecision, rttMonEchoAdminProbePakPriority, rttMonJitterStatsIAJOut, rttMonJitterStatsIAJIn, rttMonJitterStatsAvgJitter, rttMonJitterStatsAvgJitterSD, rttMonJitterStatsAvgJitterDS, rttMonJitterStatsUnSyncRTs, rttMonLatestJitterOperIAJIn, rttMonLatestJitterOperAvgJitter, rttMonLatestJitterOperAvgSDJ, rttMonLatestJitterOperAvgDSJ, rttMonLatestJitterOperOWAvgSD, rttMonLatestJitterOperOWAvgDS, rttMonLatestJitterOperIAJOut, rttMonLatestJitterOperNTPState, rttMonEchoAdminOWNTPSyncTolAbs, rttMonEchoAdminOWNTPSyncTolPct, rttMonEchoAdminOWNTPSyncTolType, rttMonLatestJitterOperUNSyncRTs" REVISION "200401200000Z" DESCRIPTION "Created new tables for Auto SAA L3 MPLS VPN. rttMplsVpnMonCtrlTable rttMplsVpnMonTypeTable rttMplsVpnMonScheduleTable rttMplsVpnMonReactTable. Modified MIB for creation of echo and pathecho operations based on MPLS LSP Ping." REVISION "200308110000Z" DESCRIPTION "Added 1 object rttMonScheduleAdminRttRecurring to the rttMonScheduleAdminTable. Added a new table rttMonGrpScheduleAdminTable for group scheduling. This table contains the following objects rttMonGrpScheduleAdminIndex rttMonGrpScheduleAdminProbes rttMonGrpScheduleAdminPeriod rttMonGrpScheduleAdminFrequency rttMonGrpScheduleAdminLife rttMonGrpScheduleAdminAgeout rttMonGrpScheduleAdminStatus. Modified the default value of rttMonReactTriggerAdminStatus from createAndGo to no default value. Corrected the Revision clause specified for the existing and all the earlier submissions." REVISION "200305210000Z" DESCRIPTION "Range for rttMonLatestJitterOperMOS, rttMonJitterStatsMinOfMOS and rttMonJitterStatsMaxOfMOS to be changed to 100..500 instead of 1..5. Modifying the range of rttMonApplProbeCapacity and rttMonApplNumCtrlAdminEntry to 1..10000.Added value other(0) for RttResponseSense and changed the range of objects rttMonLatestRttOperApplSpecificSense and rttMonHistoryCollectionApplSpecificSense to 0..2147483647. Added range for rttMonApplAuthIndex." REVISION "200304150000Z" DESCRIPTION "Removed default values from rttMonEchoAdminCodecInterval rttMonEchoAdminCodecPayload rttMonEchoAdminCodecNumPackets. Corrected some typos in the earliar revision." REVISION "200303120000Z" DESCRIPTION "Added 5 objects in the rttMonEchoAdminTable to support codec configuration. Added few objects in rttMonLatestJitterOperTable and rttMonJitterStatsTable for ICPIF (Calculated Planning Impairment Factor) and MOS (Mean Opinion Score) scores." REVISION "200011030000Z" DESCRIPTION "deprecated 4 objects in the rttMonJitterStatsTable and added the same objects with a SYNTAX of Gauge32. Also added the capability to specify a VrfName." REVISION "9906150000Z" DESCRIPTION "created rttMonAuthTable." ::= { ciscoMgmt 42 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.42.1 | ciscoRttMonObjects | 5 | 722 | None |
| 1.3.6.1.4.1.9.9.42.2 | rttMonNotificationsPrefix | 1 | 9 | None |
| 1.3.6.1.4.1.9.9.42.3 | ciscoRttMonMibConformance | 2 | 82 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.6 | ciscoTcpMIB | 3 | 20 | An extension to the IETF MIB module for managing TCP implementations |
| 1.3.6.1.4.1.9.9.10 | ciscoFlashMIB | 2 | 164 | This MIB provides for the management of Cisco Flash Devices. |
| 1.3.6.1.4.1.9.9.13 | ciscoEnvMonMIB | 4 | 68 | The MIB module to describe the status of the Environmental Monitor on those devices which support one. |
| 1.3.6.1.4.1.9.9.16 | ciscoPingMIB | 3 | 31 | Modified description of ciscoPingAddress object. |
| 1.3.6.1.4.1.9.9.17 | ciscoVinesMIB | 2 | 188 | " REVISION "9506070000Z |
| 1.3.6.1.4.1.9.9.18 | ciscoIsdnuIfMIB | 3 | 29 | ISDN BRI integrated U Interface MIB module. This MIB manages the ISDN BRI integrated U Interface in the router. |
| 1.3.6.1.4.1.9.9.19 | ciscoSnapshotMIB | 2 | 28 | Snapshot routing MIB |
| 1.3.6.1.4.1.9.9.20 | channel | 2 | 169 | This is the MIB module for objects used to manage the Cisco Mainframe Channel Connection (CMCC) cards. |
| 1.3.6.1.4.1.9.9.22 | ciscoRptrMIB | 3 | 32 | " REVISION "9512050000Z |
| 1.3.6.1.4.1.9.9.23 | ciscoCdpMIB | 2 | 78 | The MIB module for management of the Cisco Discovery Protocol in Cisco devices. |
| 1.3.6.1.4.1.9.9.24 | ciscoDspuMIB | 2 | 150 | Used to define and manage DSPU objects. |
| 1.3.6.1.4.1.9.9.25 | ciscoImageMIB | 2 | 10 | Router image MIB which identify the capabilities and characteristics of the image |
| 1.3.6.1.4.1.9.9.26 | ciscoIsdnMib | 3 | 34 | The MIB module to describe the status of the ISDN Interfaces on the routers. |
| 1.3.6.1.4.1.9.9.27 | ciscoCallHistoryMib | 2 | 40 | The MIB module to describe and store the call information of the routers for accounting purposes. |
| 1.3.6.1.4.1.9.9.28 | ciscoSnaSdllcMIB | 3 | 28 | ciscoSnaSdllcMIB MODULE-IDENTITY LAST-UPDATED "9812170000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cus… |
| 1.3.6.1.4.1.9.9.29 | ciscoRsrbMIB | 3 | 45 | This is the MIB module for objects used to manage RSRB. Overview of remote source-route bridging (RSRB) management and MIB MIB … |
| 1.3.6.1.4.1.9.9.30 | ciscoStunMIB | 3 | 41 | The MIB module for serial Tunneling. Overview of STUN MIB MIB description The STUN MIB provides the configuration and operationa… |
| 1.3.6.1.4.1.9.9.31 | ciscoTcpOffloadMIB | 2 | 20 | This is the MIB module for objects used to manage the cisco tcp offload feature. The IBM mainframe (host) supports TCP/IP. As a … |
| 1.3.6.1.4.1.9.9.32 | ciscoCipTcpIpMIB | 2 | 88 | This is the MIB module for objects used to manage the cisco TCP/IP stack running on the Cisco Mainframe Channel Connection (CMCC)… |
| 1.3.6.1.4.1.9.9.33 | ciscoCipCsnaMIB | 3 | 66 | None |
| 1.3.6.1.4.1.9.9.34 | ciscoCipLanMIB | 2 | 24 | This is the Management Information Base (MIB) module for objects used to manage the cisco internal LAN support in Cisco Mainframe… |
| 1.3.6.1.4.1.9.9.35 | ciscoBstunMIB | 3 | 71 | The MIB module for Block Serial Tunneling. Overview of BSTUN MIB MIB description The BSTUN MIB provides the configuration and o… |
| 1.3.6.1.4.1.9.9.36 | ciscoBscMIB | 2 | 46 | The MIB module for BSC. Overview of BSC MIB MIB description The BSC MIB provides the configuration and operational information on… |
| 1.3.6.1.4.1.9.9.37 | ciscoQueueMIB | 3 | 23 | This is the MIB module for objects used to manage interface queuing in Cisco devices. |
| 1.3.6.1.4.1.9.9.38 | ciscoLecsMIB | 2 | 77 | The MIB module for the management of LANE Configuration in Cisco devices. |
| 1.3.6.1.4.1.9.9.39 | ciscoLesMIB | 2 | 82 | The MIB module for the management of LANE Service in Cisco devices. |
| 1.3.6.1.4.1.9.9.40 | ciscoBusMIB | 2 | 37 | The MIB module for the management of LANE broadcast and unknown servers. |
| 1.3.6.1.4.1.9.9.41 | ciscoSyslogMIB | 3 | 49 | The MIB module to describe and store the system messages generated by the IOS and any other OS which supports syslogs. |
| 1.3.6.1.4.1.9.9.43 | ciscoConfigManMIB | 3 | 75 | Configuration management MIB. The MIB represents a model of configuration data that exists in various locations: running in use b… |
| 1.3.6.1.4.1.9.9.44 | ciscoICsuDsuMIB | 4 | 70 | Integrated CSU/DSU MIB module. For T1 and Switched 56 kbps interfaces. |
| 1.3.6.1.4.1.9.9.45 | ciscoAtmIfPhysMIB | 2 | 39 | A minimal set of managed objects for tracking the status of DS3/E3/DS1/E1 and SONET interfaces. |
| 1.3.6.1.4.1.9.9.46 | ciscoVtpMIB | 3 | 261 | The MIB module for entities implementing the VTP protocol and Vlan management. |
| 1.3.6.1.4.1.9.9.47 | ciscoModemMgmtMIB | 3 | 112 | This MIB module provides modem call related data for tracking the progress and status of a call. |
| 1.3.6.1.4.1.9.9.48 | ciscoMemoryPoolMIB | 3 | 32 | MIB module for monitoring memory pools |
| 1.3.6.1.4.1.9.9.49 | ciscoFrameRelayMIB | 2 | 158 | Cisco Frame Relay MIB |
| 1.3.6.1.4.1.9.9.50 | ciscoAtmServiceRegistryMIB | 2 | 14 | A MIB module to allow an NMS to monitor and configure the information which an ATM switch makes available via the ILMI's Service … |
| 1.3.6.1.4.1.9.9.51 | ciscoAtmSwAddrMIB | 2 | 11 | ATM Switch address MIB |
| 1.3.6.1.4.1.9.9.52 | ciscoIpEncryptionMIB | 3 | 51 | Used to manage the encryption feature. |
| 1.3.6.1.4.1.9.9.53 | ciscoVmpsMIB | 3 | 55 | The MIB module for the management of the VLAN Membership Policy Server. |
| 1.3.6.1.4.1.9.9.54 | ciscoTn3270ServerMIB | 3 | 105 | The MIB module for TN3270 Server. MIB description The PU and LU MIB are defined in RFC 1666. This MIB provides additional informa… |
| 1.3.6.1.4.1.9.9.55 | ciscoAsppMIB | 2 | 29 | The ASPP MIB provides the configuration and operational information on asynchronous polled protocols such as the asynchronous sec… |
| 1.3.6.1.4.1.9.9.56 | ciscoVlanBridgingMIB | 2 | 13 | A set of managed objects for optimizing access to bridging related data from RFC 1493. This MIB is modeled after portions of RFC… |
| 1.3.6.1.4.1.9.9.57 | ciscoCompressionServiceAdapterMIB | 2 | 19 | Used to manage the compression service adapter. |
| 1.3.6.1.4.1.9.9.59 | ciscoStackMakerMIB | 2 | 15 | The MIB module for Cisco Systems' StackMaker. |
| 1.3.6.1.4.1.9.9.60 | ciscoAtmDualPhyMIB | 3 | 26 | Initial version of this MIB module. Phy definition Throughout this document phy is used as an abbreviation for Physical Interface.… |
| 1.3.6.1.4.1.9.9.61 | ciscoAccessEnvMonMIB | 3 | 13 | The MIB module to describe the additional status of the Environmental Monitor on those Cisco Access devices which support one. |
| 1.3.6.1.4.1.9.9.62 | ciscoVoiceAnalogIfMIB | 2 | 90 | Analog Voice Interface MIB module. This MIB manages the E&M, FXO, FXS Interfaces in the router. |
| 1.3.6.1.4.1.9.9.63 | ciscoVoiceDialControlMIB | 3 | 377 | This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing management of voice telephony peers on both a circuit-s… |
| 1.3.6.1.4.1.9.9.64 | ciscoVoiceInterfaceMIB | 2 | 24 | Common Voice Interface MIB module. The MIB module manages the common voice related parameters for both voice analog and ISDN inte… |
| 1.3.6.1.4.1.9.9.65 | ciscoPnniMIB | 2 | 49 | The MIB module for managing Cisco specific extensions to the ATM Forum PNNI MIB. |
| 1.3.6.1.4.1.9.9.66 | ciscoAal5MIB | 2 | 25 | Cisco Enterprise AAL5 MIB file that provide AAL5 specific information that are either excluded by RFC 1695 or specific to Cisco p… |
| 1.3.6.1.4.1.9.9.67 | ciscoAtmAccessListMIB | 2 | 39 | A cisco ATM access list mib module. |
| 1.3.6.1.4.1.9.9.68 | ciscoVlanMembershipMIB | 3 | 90 | The MIB module for the management of the VLAN Membership within the frame work of Cisco VLAN Architecture, v 2.0 by Keith McClog… |
| 1.3.6.1.4.1.9.9.69 | ciscoLecDataVccMIB | 3 | 13 | This MIB module is a Cisco extension to the ATM Forum's LANE Client MIB. This extension identifies those VCCs which are being us… |
| 1.3.6.1.4.1.9.9.72 | ciscoCipCmpcMIB | 3 | 46 | This is the Management Information Base (MIB) module for objects used to manage the Cisco Multi-Path Channel (MPC) support on Cis… |
| 1.3.6.1.4.1.9.9.73 | ciscoCipTgMIB | 2 | 98 | This is the Management Information Base (MIB) module for objects used to manage Transmission Groups (TGs) in Cisco Mainframe Chan… |
| 1.3.6.1.4.1.9.9.74 | ciscoDlswExtMIB | 3 | 134 | The MIB module for management of Cisco specific Data Link Switching protocol enhancements. DLSw is described in RFC 1795 and RFC… |
| 1.3.6.1.4.1.9.9.76 | ciscoDlcSwitchMIB | 2 | 55 | This is the MIB module for objects used to manage FRAS sessions to the endstation. These objects are specific to downstream or end… |
| 1.3.6.1.4.1.9.9.77 | ciscoLecExtMIB | 3 | 12 | This MIB module is a Cisco extension to the ATM Forum's LANE Client MIB. |
| 1.3.6.1.4.1.9.9.78 | ciscoAtmSigDiagMIB | 2 | 58 | The MIB module to facilitate the diagnosis of failures of ATM Signalling requests. Through this MIB, an ATM device retains infor… |
| 1.3.6.1.4.1.9.9.80 | ciscoFtpClientMIB | 2 | 29 | The MIB module for invoking Internet File Transfer Protocol (FTP) operations for network management purposes. |
| 1.3.6.1.4.1.9.9.81 | ciscoBulkFileMIB | 3 | 63 | The MIB module for creating and deleting bulk files of SNMP data for file transfer. |
| 1.3.6.1.4.1.9.9.82 | ciscoStpExtensionsMIB | 3 | 300 | The MIB module for managing Cisco extensions to the 802.1D Spanning Tree Protocol (STP). |
| 1.3.6.1.4.1.9.9.83 | ciscoWredMIB | 2 | 26 | Cisco WRED MIB - Overview Cisco Weighted Random Early Detection/Drop is a method which avoids traffic congestion on an output int… |
| 1.3.6.1.4.1.9.9.84 | ciscoIpStatMIB | 2 | 34 | Cisco IP Statistics MIB - Overview This MIB incorporates objects to provide support for the Cisco IP statistics as implemented in… |
| 1.3.6.1.4.1.9.9.85 | ciscoCasIfMIB | 2 | 119 | Channel Associated Signal Interface MIB module. This MIB manages the generic CAS (Channel Associated Signal)or DS0 clear channel … |
| 1.3.6.1.4.1.9.9.86 | ciscoDspMgmtMIB | 4 | 141 | ciscoDspMgmtMIB MODULE-IDENTITY LAST-UPDATED "200008140000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cu… |
| 1.3.6.1.4.1.9.9.87 | ciscoC2900MIB | 3 | 133 | The MIB module for Catalyst 2900 enterprise specific information |
| 1.3.6.1.4.1.9.9.88 | ciscoAtmExtMIB | 3 | 50 | ciscoAtmExtMIB MODULE-IDENTITY LAST-UPDATED "9706200000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custo… |
| 1.3.6.1.4.1.9.9.89 | csCugMIB | 2 | 24 | This MIB module is for closed user group support (virtual private networks). |
| 1.3.6.1.4.1.9.9.91 | entitySensorMIB, ciscoEntitySensorMIB | 3 | 42 | The CISCO-ENTITY-SENSOR-MIB is used to monitor the values of sensors in the Entity-MIB (RFC 2037) entPhysicalTable. |
| 1.3.6.1.4.1.9.9.92 | ciscoEntityAssetMIB | 3 | 29 | Monitor the asset information of items in the ENTITY-MIB (RFC 2037) entPhysical table. |
| ... | ||||