CISCO-RTTMON-MIB Table View

A table of which contains the supported Rtt
Monitor Types.
          
See the RttMonRttType textual convention for
the definition of each type.

A table of which contains the supported Rtt
Monitor Protocols.
          
See the RttMonProtocol textual convention 
for the definition of each protocol.

A table of which contains the previously
configured Script Names and File IO targets.
          
These Script Names and File IO targets are installed
via a different mechanism than this application, and
are specific to each platform.

A table which contains the definitions for key-strings
that will be used in authenticating RTR Control Protocol.

A table of Round Trip Time (RTT) monitoring definitions.
          
The RTT administration control is in multiple tables.  
This first table, is used to create a conceptual RTT 
control row.  The following tables contain objects which 
configure scheduling, information gathering, and 
notification/trigger generation.  All of these tables 
will create the same conceptual RTT control row as this 
table using this tables' index as their own index. 
          
This table is limited in size by the agent 
implementation.  The object rttMonApplNumCtrlAdminEntry
will reflect this tables maximum number of entries.

A table that contains Round Trip Time (RTT) specific
definitions.
          
This table is controlled via the 
rttMonCtrlAdminTable.  Entries in this table are
created via the rttMonCtrlAdminStatus object.

A table of Round Trip Time (RTT) monitoring 'fileIO'
specific definitions.
          
When the RttMonRttType is not 'fileIO' this table is
not valid.
          
This table is controlled via the 
rttMonCtrlAdminTable.  Entries in this table are
created via the rttMonCtrlAdminStatus object.

A table of Round Trip Time (RTT) monitoring 'script'
specific definitions.
          
When the RttMonRttType is not 'script' this table is
not valid.
          
This table is controlled via the
rttMonCtrlAdminTable.  Entries in this table are
created via the rttMonCtrlAdminStatus object.

A table of Round Trip Time (RTT) monitoring scheduling
specific definitions.
          
This table is controlled via the
rttMonCtrlAdminTable.  Entries in this table are
created via the rttMonCtrlAdminStatus object.

A table of Round Trip Time (RTT) monitoring statistics
definitions. 
          
The definitions in this table control what and how many
entries will be placed into the rttMonStatsCaptureTable.
          
The statistics capture table is a rollover table.  When 
the rttMonStatisticsAdminNumHourGroups index value 
exceeds its value defined in this table, the oldest 
corresponding group will be deleted and will be replaced 
with the new group.  All other indices will only fill to 
there maximum size.
          
NOTE:  The maximum size of this table is defined to be
       the product of the rttMonCtrlAdminIndex times
       rttMonStatisticsAdminNumHourGroups times
       rttMonStatisticsAdminNumPaths times
       rttMonStatisticsAdminNumHops times
       rttMonStatisticsAdminNumDistBuckets. 
          
NOTE WELL:  Each of the 'Num' objects values in this 
            have a special behavior.  When one of the
            objects is set to a value larger than the
            Rtt application can support the set will
            succeed, but the resultant value will
            be set to the applications maximum value. 
            The setting management station must reread
            this object to verify the actual value.
          
This table augments the rttMonCtrlAdminTable.

A table of Round Trip Time (RTT) monitoring history
definitions.
          
The definitions in this table control what and how many
entries will be placed into the 
rttMonHistoryCollectionTable.
          
The history collection table is a rollover table.  When 
the rttMonHistoryAdminNumLives index value exceeds its 
value defined in this table, the oldest corresponding 
'lives' group will be deleted and will be replaced with 
the new 'lives' group.  All other indices will only fill
to their maximum size.
          
NOTE:  The maximum size of this table is defined to be
       the product of the rttMonCtrlAdminIndex times
       rttMonHistoryAdminNumLives times
       rttMonHistoryAdminNumBuckets times
       rttMonHistoryAdminNumSamples.
          
NOTE WELL:  Each of the 'Num' objects values in this 
            have a special behavior.  When one of the
            objects is set to a value larger than the
            Rtt application can support the set will
            succeed, but the resultant value will
            be set to the applications maximum value. 
            The setting management station must reread
            this object to verify the actual value.
          
NOTE: this table is not applicable to http and jitter 
      probes

A table of which contains the Operational values for the
probe, and the conceptual RTT control row. 
          
This table augments the rttMonCtrlAdminTable.

A table of which contains the status of latest RTT
operation. 
          
When the RttMonRttType is 'pathEcho', operations 
performed to the hops along the path will be recorded
in this table.
          
This table augments the RTT definition table, 
rttMonCtrlAdminTable.

A table of which contains the list of conceptual RTT
control rows that will start to collect data when a 
reaction condition is violated and when 
rttMonReactAdminActionType is set to one of the 
following:
  -  triggerOnly
  -  trapAndTrigger
  -  nmvtAndTrigger
  -  trapNmvtAndTrigger
or when a reaction condition is violated and when any of the
row in rttMonReactTable has rttMonReactActionType as one of
the following:
  - triggerOnly
  - trapAndTrigger
          
The goal of this table is to define one or more 
additional conceptual RTT control rows that will become
active and start to collect additional history and
statistics (depending on the rows configuration values),
when a problem has been detected.
          
If the conceptual RTT control row is undefined, and a 
trigger occurs, no action will take place.  
          
If the conceptual RTT control row is scheduled to start 
at a later time, triggering that row will have no effect.
          
If the conceptual RTT control row is currently active, 
triggering that row will have no effect on that row, but 
the rttMonReactTriggerOperState object will transition to 
'active'.
          
An entry in this table can only be triggered when
it is not currently in a triggered state.  The
object rttMonReactTriggerOperState will 
reflect the state of each entry in this table.

A table of which contains the operational state
of each entry in the 
rttMonReactTriggerAdminTable.
          
This table augments the RTT trigger 
definition table, rttMonReactTriggerAdminTable.

A table to store the hop addresses in a Loose Source Routing
path. Response times are computed along the specified path
using ping.
          
This maximum table size is limited by the size of the 
maximum number of hop addresses that can fit in an IP header,
which is 8. The object rttMonEchoPathAdminEntry will reflect 
this tables maximum number of entries.
          
This table is coupled with rttMonCtrlAdminStatus.

A table of Round Trip Time (RTT) monitoring group scheduling
specific definitions.
This table is used to create a conceptual group scheduling
control row. The entries in this control row contain objects
used to define group schedule configuration parameters.
          
The objects of this table will be used to schedule a group of
probes identified by the conceptual rows of the
rttMonCtrlAdminTable.

A table of Auto SAA L3 MPLS VPN definitions.
          
The Auto SAA L3 MPLS VPN administration control is in multiple
tables.
          
This first table, is used to create a conceptual Auto SAA L3
MPLS VPN control row.  The following tables contain objects
which used in type specific configurations, scheduling and
reaction configurations. All of these tables will create the
same conceptual control row as this table using this table's
index as their own index.
          
In order to a row in this table to become active the following
objects must be defined.
  rttMplsVpnMonCtrlRttType,
  rttMplsVpnMonCtrlVrfName and
  rttMplsVpnMonSchedulePeriod.

A table that contains Auto SAA L3 MPLS VPN configured RTT
operation specific definitions.
          
This table is controlled via the rttMplsVpnMonCtrlTable.
Entries in this table are created via the
rttMplsVpnMonCtrlStatus object.

A table of Auto SAA L3 MPLS VPN monitoring scheduling
specific definitions.
          
This table is controlled via the rttMplsVpnMonCtrlTable.
Entries in this table are created via the
rttMplsVpnMonCtrlStatus object.

A Table of Auto SAA L3 MPLS VPN Notification definitions.
          
This table augments the rttMplsVpnMonCtrlTable.

A table that contains the reaction configurations. Each
conceptual row in rttMonReactTable corresponds to a reaction
configured for the probe defined in rttMonCtrlAdminTable.
          
For each reaction configured for a probe there is an entry in
the table.
          
Each Probe can have multiple reactions and hence there can be
multiple rows for a particular probe.
          
This table is coupled with rttMonCtrlAdminTable.

This table contains information about the generated
operation id as part of a parent IP SLA operation. The parent
operation id is pseudo-random number, selected by the management
station based on an operation started by the management 
station,when creating a row via the rttMonCtrlAdminStatus
object in the rttMonCtrlAdminTable table.

The statistics capture database.
          
The statistics capture table contains summarized 
information of the results for a conceptual RTT control 
row.  A rolling accumulated history of this information 
is maintained in a series of hourly 'group(s)'.  Each 
'group' contains a series of 'path(s)', each 'path' 
contains a series of 'hop(s)', each 'hop' contains a 
series of 'statistics distribution bucket(s)'.
          
Each conceptual statistics row has a current hourly 
group, into which RTT results are accumulated.  At the 
end of each hour a new hourly group is created which 
then becomes current.  The counters and accumulators in 
the new group are initialized to zero.  The previous 
group(s) is kept in the table until the table contains 
rttMonStatisticsAdminNumHourGroups groups for the 
conceptual statistics row;  at this point, the oldest 
group is discarded and is replaced by the newly created 
one.  The hourly group is uniquely identified by the 
rttMonStatsCaptureStartTimeIndex object.
          
If the activity for a conceptual RTT control row ceases 
because the rttMonCtrlOperState object transitions to 
'inactive', the corresponding current hourly group in 
this table is 'frozen', and a new hourly group is 
created when activity is resumed.
          
If the activity for a conceptual RTT control row ceases 
because the rttMonCtrlOperState object transitions to 
'pending' this whole table will be cleared and reset to 
its initial state.
          
When the RttMonRttType is 'pathEcho', the path 
exploration RTT requests' statistics will not be 
accumulated in this table.
          
NOTE: When the RttMonRttType is 'pathEcho', a source to 
      target rttMonStatsCapturePathIndex path will be 
      created for each rttMonStatsCaptureStartTimeIndex 
      to hold all errors that occur when a specific path
      had not been found or connection has not be setup.
          
Using this rttMonStatsCaptureTable, a managing 
application can retrieve summarized data from accurately 
measured periods, which is synchronized across multiple 
conceptual RTT control rows.  With the new hourly group
creation being performed on a 60 minute period, the 
managing station has plenty of time to collect the data, 
and need not be concerned with the vagaries of network 
delays and lost PDU's when trying to get matching data.  
Also, the managing station can spread the data gathering 
over a longer period, which removes the need for a flood 
of get requests in a short period which otherwise would 
occur.

The statistics collection database.
          
This table has the exact same behavior as the
rttMonStatsCaptureTable, except it does not keep
statistical distribution information.
          
For a complete table description see
the rttMonStatsCaptureTable object.