TELDAT-MON-FEATURES-NSM-MIB: View SNMP OID List / Download MIB

This module defines a MIB for Round Trip Time (RTT) monitoring of a list of targets, using a variety of protocols: MIB for management of Teldat feature Network Service Monitor. The table structure overview is as follows (t: indicates a table, at: indicates an augmented table, and it: indicates table with the same indices/control as parent table): NSM MIB |--- Application Group | |--- Application version string | |--- Max number of entries in teldatNsmCtrlAdminTable | |--- Overall Control Group | |t-- Master Definitions Table | | |--- Global Configuration Definitions | | |--- Config for a single RTT Life | | |it- Echo Specific Configuration | | |at- Schedule Configuration | | |at- Monitoring Operational State | | |at- Last RTT operation | |--- Statistics Collection Group | |t-- Statistics Capture Table | |--- Captured Statistics | |it- Statistics Collection Table | |it- Statistics Totals Table | |t-- HTTP Stats Table | |t-- Jitter Stats Table | |--- History Collection Group | |--- 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 teldatNsmCtrlAdminIndex 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. 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. 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. Statistics capture table will omit these responses to prevent skewed results.

Network Service Monitor (or RTT Teldat) application version string. The format will be: 'Version.Release.Patch-Level: Textual-Description' For example: '1.0.0: Initial RTT Teldat Application'

This object defines the maximum number of entries that can be added to the teldatNsmCtrlAdminTable. It is a fixed value: 32.

A table of NSM Round Trip Time (RTT) monitoring definitions. The NSM 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 and information gathering. All of these tables will create the same conceptual RTT control row as this table using this table index as their own index. This table is limited in size by the agent implementation. The object teldatNsmApplNumCtrlAdminEntry will reflect this tables maximum number of entries.

A base list of objects that define a conceptual RTT control row.

Uniquely identifies a row in the teldatNsmCtrlAdminTable. This is a pseudo-random number selected by the management station when creating a row via the teldatNsmCtrlAdminStatus object. If the pseudo-random number is already in use a 'genericError' return code will be returned when set operation is attempted.

Identifies the entity that created this table row.

A string which is used by a managing application to identify the RTT target. This string could be inserted into trap notifications, but has no other significance to the agent.

The type of NSM operation to be performed. This value must be set in the same PDU or before setting any type specific configuration.

This object defines an administrative threshold limit. If the RTT operation time exceeds this limit, the variables teldatNsmCtrlOperOverThresholdOccurred, teldatNsmHTTPStatsOverThresholds and teldatNsmJitterStatsOverThresholds are updated.

Specifies the duration between initiating each RTT operation. This object cannot be set to a value which would be a shorter duration than teldatNsmCtrlAdminTimeout. When the NsmRttType specifies an operation that is synchronous in nature, it may happen that the next RTT operation is blocked by a RTT operation which has not yet completed. In this case, the value of a counter (teldatNsmStatsCollectBusies) in teldatNsmStatsCaptureTable is incremented in lieu of initiating a RTT operation, and the next attempt will occur at the next teldatNsmCtrlAdminFrequency expiration.

Specifies the duration to wait for a RTT operation completion. The value of this object cannot be set to a value which would specify a duration exceeding teldatNsmCtrlAdminFrequency. For connection oriented protocols, this may cause the connection to be closed by the probe. Once closed, it will be assumed that the connection reestablishment will be performed. To prevent unwanted closure of connections, be sure to set this value to a realistic connection timeout.

When set to true, the resulting data in each RTT operation is compared with the expected data. This includes checking header information (if possible) and exact packet size. Any mismatch will be recorded in the teldatNsmStatsCollectVerifyErrors object. NsmRttTypes supported by now do not support this option, so the agent will transition this object to false. It is the management applications responsibility to check for this transition.

The status of the conceptual RTT control row. In order for this object to become active, the following row objects must be defined: - teldatNsmCtrlAdminRttType Additionally: - for echo probes teldatNsmEchoAdminProtocol and teldatNsmEchoAdminTargetAddress; - for jitter probes teldatNsmEchoAdminTargetAddress and teldatNsmEchoAdminTargetPort; - for http probe teldatNsmEchoAdminURL All other objects can assume default values. The conceptual RTT control row will be placed into a 'pending' state (via the teldatNsmCtrlOperState object) if teldatNsmScheduleAdminRttStartTime is not specified. Most conceptual RTT control row objects cannot be modified once this conceptual RTT control row has been created. The objects that can change are the following: - Objects in the teldatNsmScheduleAdminTable can be modified only when the value of this object is not 'active'. - The teldatNsmCtrlOperState can be modified to control the state of the probe. Once this object is in 'active' status, it cannot be set to 'notInService' while the teldatNsmCtrlOperState is in 'active' state. Thus the teldatNsmCtrlOperState object must be transitioned first. This object can be set to 'destroy' from any value at any time.

When set to true, this entry will be shown in 'list config' command and can be saved into Non-volatile memory. This variable is not supported at the moment and always takes the value 'false'.

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

A list of objects that define specific configuration for NsmRttType conceptual RTT control rows.

Specifies the protocol to be used to perform the NSM RTT operation. The following list defines what protocol should be used for each probe type: echo - ipIcmpEcho http - httpAppl jitter - jitterAppl When this protocol does not support the type, a 'genericError' error will be returned.

A string which specifies the address of the target.

This object is used in echo (ipIcmpecho) and jitter probes, and its value represents the native payload size. REMEMBER: The ARR Header overhead is not included in this value. For echo probes the total packet size = (IP header(20) + ICMP header(8) + 8 (internal timestamps) + request size). For echo default request size is 28. For jitter probe it is 32. The minimum request size for echo is 28 bytes and for jitter it is 16. For jitter probes the maximum request size is 1500.

This object is not supported by protocols allowed at this moment.

This object represents the target's port number. This object is applicable to jitter probes.

A string which specifies the IP address of the source. This object is applicable to all supported probes.

This object represents the source's port number. If this object is not specified, the application will get a port allocated by the system. This object is applicable to http probes.

If this object is enabled, then NSM application will send control messages to a responder, residing on the target router to respond to the data request packets being sent by the source router. This object is not applicable to echo and http probes. This variable is not supported and it always takes the value 'true'.

This object represents the type of service octet in an IP header.

If this object is enabled then it means that the application calculates response time for a specific path. This object is applicable to echo probe only, but it is not supported and its value will be always 'false'.

A string which specifies the address of the target. This string can be in IP address format or a hostname. This object is not applicable to supported probes.

A string which specifies the IP address of the name-server. This object is not applicable to supported probes.

A code that represents the specific type of RTT operation. This object is applicable to http probe only.

A string which specifies the version number of the HTTP Server. The syntax for the version string is . An example would be 1.0, 1.1 etc.,. This object is applicable to http probe only.

A string which represents the URL to which a HTTP probe should communicate with. This object is applicable to http probe only.

If this object is false then it means that HTTP request should not download cached pages. This means that the request should be forwarded to the origin server. This object is applicable to http probe only, but it is not supported by the application at the moment.

This value represents the inter-packet delay between packets and is in milliseconds. This object is applicable to jitter probe only.

This value represents the number of packets that need to be transmitted. This value is currently used for Jitter probe. This object is applicable to jitter probe only.

This string represents the proxy server information. This object is applicable to http probe only, but it is not supported by the application at the moment.

This string stores the content of HTTP raw request. If the request cannot fit into String1 then it should be split and put in Strings 1 through 5. This object is applicable to http probe only, but it is not used by the application at the moment.

This string stores the content of HTTP raw request. teldatNsmEchoAdminString1-5 are concatenated to form the HTTP raw request used in the RTT operation. This object is applicable to http probe only, but it is not used by the application at the moment.

This string stores the content of HTTP raw request. teldatNsmEchoAdminString1-5 are concatenated to form the HTTP raw request used in the RTT operation. This object is applicable to http probe only, but it is not used by the application at the moment.

This string stores the content of HTTP raw request. teldatNsmEchoAdminString1-5 are concatenated to form the HTTP raw request used in the RTT operation. This object is applicable to http probe only, but it is not used by the application at the moment.

This string stores the content of HTTP raw request. teldatNsmEchoAdminString1-5 are concatenated to form the HTTP raw request used in the RTT operation. This object is applicable to http probe only, but it is not used by the application at the moment.

A code that represents the specific type of RTT operation. This object is not applicable to supported probes, and will always take the value 'ftpPassive'.

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

A list of objects that define specific configuration for the scheduling of NSM RTT operations.

This object value will be placed into the teldatNsmCtrlOperRttLife object when the teldatNsmCtrlOperState object transitions to 'active' or 'pending'. The value 2147483647 has a special meaning. When this object is set to 2147483647, the teldatNsmCtrlOperRttLife object will not decrement. And thus the life time will never end.

This is the time when this conceptional row will activate. This is the value of MIB-II's sysUpTime in the future. When sysUpTime equals this value this object will cause the activation of a conceptual RTT row. There are two values with a special meaning: - The first special value allows this conceptual RTT control row to immediately transition the teldatNsmCtrlOperState object into 'active' state when the teldatNsmCtrlAdminStatus object transitions to active. This special value is defined to be a value of this object that, when initially set, is 1. - The second special value allows this conceptual RTT control row to immediately transition the teldatNsmCtrlOperState object into 'pending' state when the teldatNsmCtrlAdminStatus object transitions to active. Also, when the teldatNsmCtrlOperRttLife counts down to zero (and not when set to zero), this special value causes this conceptual RTT control row to retransition the teldatNsmCtrlOperState object into 'pending' state. This special value is defined to be a value of this object that, when initially set, is smaller than the current sysUpTime. (With the exception of one, as defined in the previous paragraph).

The amount of time this conceptual Rtt control row will exist when not in an 'active' teldatNsmCtrlOperState. When this conceptual Rtt control row enters an 'active' state, this timer will be reset and suspended. When this conceptual RTT control row enters a state other than 'active', the timer will be restarted. When this value is set to zero, this entry will never be aged out.

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

A list of objects that describe the current state of probe, and the conceptual RTT control row.

This object is updated whenever an object in the conceptual RTT control row is changed or updated.

A string which can be used as an aid in tracing problems. The content of this field will depend on the type of target (teldatNsmEchoAdminProtocol). For all protocols supported by now, this value will be null. It is primarily intended that this object contains information which has significance to a human operator.

This object is set when the teldatNsmCtrlOperState is set to reset.

This object is the number of octets currently in use by this composite conceptual RTT row. A composite conceptual row include the control and statistics conceptual rows combined. (All octets that are addressed via the teldatNsmCtrlAdminIndex in this MIB.)

This object will only change its value when the NsmRttType is 'echo'. This object is set to true when the RTT connection fails to be established or is lost, and set to false when a connection is reestablished.

This object will change its value for all NsmRttTypes. This object is set to true when an operation times out, and set to false when an operation completes under teldatNsmCtrlAdminTimeout.

This object will change its value for all NsmRttTypes. This object is changed by operation completion times over threshold.

This is the total number of probe operations that have been attempted. This value is incremented for each start of an RTT operation. This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the teldatNsmMonMIB object. This value is not effected by the rollover of a statistics hourly group.

This object is decremented every second, until it reaches zero. When the value of this object is zero RTT operations for this row are suspended. This object will either reach zero by a countdown or it will transition to zero via setting the teldatNsmCtrlOperState. When this object reaches zero the agent needs to transition the teldatNsmCtrlOperState to 'inactive'. REMEMBER: The value 2147483647 has a special meaning. When this object has the value 2147483647, this object will not decrement. And thus the life time will never.

The RttMonOperStatus object is used to manage the 'state' of the probe that is implementing this conceptual RTT control row. This status object has six defined values: reset(1) - Reset this entry; transition to 'pending'. orderlyStop(2) - Shutdown this entry at the end of the next RTT operation attempt; transition to 'inactive'. immediateStop(3) - Shutdown this entry immediately (if possible); transition to 'inactive'. pending(4) - This value is not settable and this conceptual RTT control row is waiting for further control via the teldatNsmScheduleAdminTable. This object can transition to this value via two mechanisms: first by reseting this object, and second by creating a conceptual RTT control row with the teldatNsmScheduleAdminRttStartTime object with its special value. inactive(5) - This value is not settable and this conceptual RTT control row is waiting for further control via the teldatNsmScheduleAdminTable. This object can transition to this value via two mechanisms: first by setting this object to 'orderlyStop' or 'immediateStop', second by the teldatNsmCtrlOperRttLife object reaching zero. active(6) - This value is not settable and this conceptual RTT control row is currently active. restart(7) - This value is only settable when the state is active. It clears the data of this entry and remain on active state. The probes action when this object is set to 'reset': - All rows in teldatNsmStatsCaptureTable that relate to this conceptual RTT control row (only 1 in current implementation) are destroyed. - A single new teldatNsmStatsCaptureTable row is created. - teldatNsmCtrlOperRttLife is set to teldatNsmScheduleAdminRttLife. - teldatNsmCtrlOperNumRtts is set to zero. - teldatNsmCtrlOperTimeoutOccurred, teldatNsmCtrlOperOverThresholdOccurred, and teldatNsmCtrlOperConnectionLostOccurred are set to false. - The next RTT operation is controlled by the objects in the teldatNsmScheduleAdminTable. - All open connections must be maintained. This can be used to synchronize various RTT definitions, so that the RTT requests occur simultaneously, or as simultaneously as possible. The probes action when this object transitions to 'inactive' (via setting this object to 'orderlyStop' or 'immediateStop' or by teldatNsmCtrlOperRttLife reaching zero): - All statistics and collection information table entries will be closed and kept. - teldatNsmCtrlOperTimeoutOccurred, teldatNsmCtrlOperOverThresholdOccurred, and teldatNsmCtrlOperConnectionLostOccurred are set to false. - The next RTT request is controlled by the objects in the teldatNsmScheduleAdminTable. - All open connections are to be closed and cleanup. teldatNsmCtrlOperState STATE +-------------------------------------------+ | A | B | C | ACTION | 'pending' | 'inactive' | 'active' | +----------------+--------------+--------------+-------------+ | OperState set | noError |inconsistent- | noError | | to 'reset' | | Value | | | | -> A | | -> A | +----------------+--------------+--------------+-------------+ | OperState set | noError | noError | noError | |to 'orderlyStop'| -> B | -> B | -> B | | or to | | | | |'immediateStop' | | | | +----------------+--------------+--------------+-------------+ | AdminStatus | -> C | -> C | see (1) | | transitions to | | | | | 'active' & | | | | | RttStartTime is| | | | | special value | | | | | of one. | | | | +----------------+--------------+--------------+-------------+ | AdminStatus | -> A | -> A | see (1) | | transitions to | | | | | 'active' & | | | | | RttStartTime is| | | | | special value | | | | | of less than | | | | | current time, | | | | | excluding one. | | | | +----------------+--------------+--------------+-------------+ | AdminStatus | -> A | -> B | see (2) | | transitions to | | | | | 'notInService' | | | | +----------------+--------------+--------------+-------------+ | AdminStatus | -> B | -> B | -> B | | transitions to | | | | | 'delete' | | | | +----------------+--------------+--------------+-------------+ | AdminStatus is | -> C | -> C | -> C | | 'active' & the | | | see (3) | | RttStartTime | | | | | arrives | | | | +----------------+--------------+--------------+-------------+ | RowAgeout | -> B | -> B | -> B | | expires | | | | +----------------+--------------+--------------+-------------+ | OperRttLife | N/A | N/A | -> B | | counts down to | | | | | zero | | | | +----------------+--------------+--------------+-------------+ (1) - teldatNsmCtrlOperState must have transitioned to 'inactive' or 'pending' before the teldatNsmCtrlAdminStatus can transition to 'active'. See (2). (2) - teldatNsmCtrlAdminStatus cannot transition to 'notInService' unless teldatNsmCtrlOperState has been previously forced to 'inactive' or 'pending'. (3) - When this happens the teldatNsmCtrlOperRttLife will not be updated with the teldatNsmScheduleAdminRttLife. NOTE: In order for all objects in a PDU to be set at the same time, this object can not be part of a multi-bound PDU. Enumeration: 'reset': 1, 'orderlyStop': 2, 'immediateStop': 3, 'inactive': 5, 'restart': 7, 'active': 6, 'pending': 4.

A table of which contains the status of latest RTT (NSM) operation. This table augments the RTT definition table, teldatNsmCtrlAdminTable.

A list of objects that record the latest RTT (NSM) operation.

The completion time of the latest RTT (NSM) operation successfully completed.

A sense code for the completion status of the latest RTT (NSM) operation.

An application specific sense code for the completion status of the latest RTT operation. This object will only be valid when the teldatNsmLatestRttOperSense object is set to 'applicationSpecific'. Otherwise, this object's value is not valid.

A sense description for the completion status of the latest RTT (NSM) operation when the teldatNsmLatestRttOperSense object is set to 'applicationSpecific'.

The value of the agent system time at the time of the latest RTT (NSM) operation.

This is a string which specifies the address of the target for this RTT (NSM) operation. This address will be just the teldatNsmEchoAdminTargetAddress address. See teldatNsmEchoAdminTargetAddress for a complete description.

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)'. In current implementation, the rolling accumulated information history is maintained only in one hourly 'group'; each 'group' will contained only one 'path', each path one 'hop', and each 'hop' one 'statistics distribution bucket'. 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 the maximum number of groups established for the conceptual statistics row: in current implementation only an hourly 'group' is maintained; at this point, the oldest group is discarded and is replaced by the newly created one (as only one group is kept, previously groups are deleted). The hourly group is uniquely identified by the teldatNsmStatsCaptureStartTimeIndex object. If the activity for a conceptual RTT control row ceases because the teldatNsmCtrlOperState object transitions to 'inactive', the corresponding current hourly group in this table must be 'frozen', and a new hourly group created when activity is resumed: in this particular case, current hourly group will be deleted and a new one created when activity is resumed. If the activity for a conceptual RTT control row ceases because the teldatNsmCtrlOperState object transitions to 'pending' this whole table will be cleared and reset to its initial state. Using this teldatNsmStatsCaptureTable, 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.

A list of objects which accumulate the results of a series of RTT operations over a 60 minute time period. The statistics capture table is a rollover table. When teldatNsmStatsCaptureStartTimeIndex groups exceeds the maximum established value (1), the oldest corresponding hourly group will be deleted and will be replaced with the new teldatNsmStatsCaptureStartTimeIndex hourly group. All other indices will fill to there maximum size. The statistics capture table has five indices. Each described as follows: - The first index correlates its entries to a conceptual RTT control row via the teldatNsmCtrlAdminIndex object. - The second index is a rollover group and it uniquely identifies a 60 minute group. (The teldatNsmStatsCaptureStartTimeIndex object is used to make this value unique). Remmber: only one hourly 'group' is kept in the table. - The third index uniquely identifies the paths in a statistics period. (The period is 60 minutes). A path will be created for each unique path through the network. Note: A path that does not contain the target is considered a different path than one which uses the exact same path, but does contain the target. For all supported values of NsmRttType this index will be one (only one path is considered). - The fourth index uniquely identifies the hops in each path, as grouped by the third index. This index does imply the order of the hops along the path to a target. For all supported values of NsmRttType this index will be one. - The fifth index uniquely creates a statistical distribution bucket. In current implementation only one statistical distribution is kept.

The time when this row was created. This object is the second index of the teldatNsmStatsCaptureTable Table. When the number of teldatNsmStatsCaptureStartTimeIndex groups exceeds the maximum established value (1), the oldest teldatNsmStatsCaptureStartTimeIndex group (that will be the previous one, the current hourly group) will be removed and replaced with the new entry.

For all supported values of NsmRttType, this object will be one: only one path will be contained in each hourly 'group'. For a particular value of teldatNsmStatsCaptureStartTimeIndex, the agent assigns the first instance of a path a value of 1, then second instance a value of 2, and so on. The sequence keeps incrementing until the number of paths equals maximum allowed value (1 in current implementation); then no new paths are kept for the current teldatNsmStatsCaptureStartTimeIndex group. So, for each hourly 'group', only one path is kept, identified by value 1. NOTE: A source to target teldatNsmStatsCapturePathIndex path will be created for each teldatNsmStatsCaptureStartTimeIndex to hold all errors that occur when a specific path or connection has not be setup. This value directly represents the path to a target.

For all supported values of NsmRttType, this object will be one: only one hop will be contained in each path (i.e., one hop in each hourly 'group'). For a particular value of teldatNsmStatsCapturePathIndex, the agent assigns the first instance of a hop a value of 1, then second instance a value of 2, and so on. The sequence keeps incrementing until the number of hops equals maximum allowed value (1 in current implementation); then no new hops are kept for the current teldatNsmStatsCapturePathIndex. So, for each hourly 'group', only one path and one hop are kept, both identified by value 1 (each one). This value directly represents a hop along the path to a target and shows the order along the path to a target.

This object uniquely defines a statistical distribution bucket for a given value of teldatNsmStatsCaptureHopIndex. In current implementation only one statistical distribution is kept for each hop (i.e., one statistical distribution, one hop, and one path for each hourly 'group'). For a particular value of teldatNsmStatsCaptureHopIndex, the agent assigns the first instance of a distribution a value of 1, then second instance a value of 2, and so on. The sequence keeps incrementing until the number of statistics distribution intervals equals maximum allowed value (1 in current implementation); then all values that fall above the last interval will be placed into the last interval: this means all values will be accumulated in the only existing distribution interval. Each of these statistical distribution buckets contain the results of each completion. Remember: only one statistical distrbution is kept.

The number of RTT (NSM) operations that have completed without an error and without timing out. This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the teldatNsmMonMIB object.

The number of RTT (NSM) operations successfully completed, but in excess of teldatNsmCtrlAdminThreshold. This number is a subset of the accumulation of all teldatNsmStatsCaptureCompletions. The operation time of these completed operations will be accumulated. This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the teldatNsmMonMIB object.

The accumulated completion time of RTT (NSM) operations which complete successfully.

The low order 32 bits of the accumulated squares of completion times (in milliseconds) of RTT (NSM) operations which complete successfully. Low/High order is defined where the binary number will look as follows: ------------------------------------------------- | High order 32 bits | Low order 32 bits | ------------------------------------------------- For example the number 4294967296 would have all Low order bits as '0' and the rightmost High order bit will be 1 (zeros,1).

The high order 32 bits of the accumulated squares of completion times (in milliseconds) of RTT (NSM) operations which complete successfully. See the teldatNsmStatsCaptureSumCompletionTime2Low object for a definition of Low/High Order.

The maximum completion time of any RTT (NSM) operation which completes successfully.

The minimum completion time of any RTT (NSM) operation which completes successfully.

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

A list of objects which accumulate the results of a series of RTT (NSM) operations over a 60 minute time period. This entry has the exact same behavior as the teldatNsmStatsCaptureEntry, except it does not keep statistical distribution information. For a complete entry description see the teldatNsmStatsCaptureEntry object.

When the NsmRttType is 'echo', this object represents the number of times that the target became disconnected. For all other values of NsmRttType, this object will remain zero. For connectionless protocols this has no meaning, and will consequently remain 0. Since this error does not indicate any information about the failure of an RTT (NSM) operation, no response time information for this instance will be recorded in the appropriate objects. If this error occurs, it will be accumulated in the source to target path (the only which always exists). This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the teldatNsmMonMIB object.

The number of occasions when a RTT (NSM) operation was not completed before a timeout occurred, i.e. teldatNsmCtrlAdminTimeout was exceeded. Since the RTT operation was never completed, the completion time of these operations are not accumulated, nor do they increment teldatNsmStatsCaptureCompletions. This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the teldatNsmMonMIB object.

The number of occasions when a RTT (NSM) operation could not be initiated because a previous RTT (NSM) operation has not been completed. When the initiation of a new operation cannot be started, this object will be incremented and the operation will be omitted. (The next operation will start at the next Frequency). Since a RTT (NSM) operation was never initiated, the completion time of these operations is not accumulated, nor do they increment teldatNsmStatsCaptureCompletions. This error will be accumulated in the source to target path, the only will always exists. This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the teldatNsmMonMIB object.

When the NsmRttType is 'echo' this is the number of occasions when a RTT (NSM) operation could not be initiated because the connection to the target has not been established. For all other NsmRttTypes this object will remain zero. This cannot occur for connectionless protocols, but may occur for connection oriented protocols (such as SNA). Since a RTT (NSM) operation was never initiated, the completion time of these operations are not accumulated, nor do they increment teldatNsmStatsCaptureCompletions. If this error occurs, it will be accumulated in the source to target path, the only which always exists. This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the teldatNsmMonMIB object.

The number of occasions when a RTT (NSM) operation could not be initiated because some necessary internal resource (for example memory) was not available, or the operation completion could not be recognized. Since a RTT (NSM) operation was never initiated or was not recognized, the completion time of these operations are not accumulated, nor do they increment teldatNsmStatsCaptureCompletions. This error will be accumulated in the source to target path, the only which always exists. This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the teldatNsmMonMIB object.

When the NsmRttType is 'echo' this is the number of RTT (NSM) operation completions received with an unexpected sequence identifier. For all other values of NsmRttType this object will remain zero. When this has occurred some of the possible reasons may be: - a duplicate packet was received - a response was received after it had timed-out - a corrupted packet was received and was not detected The completion time of these operations are not accumulated, nor do they increment teldatNsmStatsCaptureCompletions. This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the teldatNsmMonMIB object.

The number of RTT (NSM) operation completions received with data that does not compare with the expected data. The completion time of these operations are not accumulated, nor do they increment teldatNsmStatsCaptureCompletions. This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the teldatNsmMonMIB object. Verify operations are not supported in this implementation, so this variable always remains zero.

This object is a string which specifies the address of the target for the RTT (NSM) operation. This address will be just the teldatNsmEchoAdminTargetAddress address. The interpretation of this string depends on the type of RTT operation selected, as specified by the teldatNsmEchoAdminProtocol object.

The statistics totals database. This table has the exact same behavior as the teldatNsmStatsCaptureTable, except it only keeps 60 minute group values. For a complete table description see the teldatNsmStatsCaptureTable object.

A list of objects which accumulate the results of a series of RTT (NSM) operations over a 60 minute time period. This entry has the exact same behavior as the teldatNsmStatsCaptureEntry, except it only keeps 60 minute group values. For a complete entry description see the teldatNsmStatsCaptureEntry object.

The length of time since this conceptual statistics row was created.

The number of RTT (NSM) operations that have been initiated. This number includes all RTT (NSM) operations which succeed or fail for whatever reason. This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the teldatNsmMonMIB object.

The HTTP statistics collection database. The HTTP statistics table contains summarized information of the results for a conceptual RTT control row. A rolling accumulated history of this information could be maintained in a series of hourly 'group(s)', but in current implementation only one hourly 'group' is kept. The operation of this table is same as that of teldatNsmStatsCaptureTable, except information is only distributed in one hourly group, and there is no division according to 'path', 'hop' or statistical distribution buckets.

A list of objects which accumulate the results of a series of RTT (HTTP) operations over a 60 minute time period. This entry is created only if the teldatNsmCtrlAdminRttType is http. The operation of this table is same as that of teldatNsmStatsCaptureTable, except information is only distributed in one hourly group, and there is no division according to 'path', 'hop' or statistical distribution buckets.

This is the time when this row was created. This index uniquely identifies a HTTP stats row in the teldatNsmHTTPStatsTable.

The number of HTTP operations that have completed successfully.

The number of HTTP operations that violate threshold.

The sum of HTTP operations that are successfully measured.

The sum of squares of the RTT's that are successfully measured (low order 32 bits).

The sum of squares of the RTT's that are successfully measured (high order 32 bits).

The minimum RTT taken to perform HTTP operation.

The minimum RTT taken to perform HTTP operation.

The sum of RTT taken to perform DNS query within the HTTP operation.

The sum of RTT taken to connect to the HTTP server.

The sum of RTT taken to download the object specified by URL.

The sum of the size of the message body received as a response to the HTTP request.

The number of requests that could not connect to the DNS Server.

The number of requests that could not connect to the HTTP Server.

The number of requests that timed out during HTTP transaction.

The number of requests that had DNS Query errors.

The number of requests that had HTTP errors while downloading the base page.

The number of occasions when a HTTP operation could not be initiated because an internal error.

The number of occasions when an HTTP operation could not be initiated because a previous HTTP operation has not been completed.

The Jitter statistics collection database. The Jitter statistics table contains summarized information of the results for a conceptual RTT control row. A rolling accumulated history of this information could be maintained in a series of hourly 'group(s)', but in current implementation only one hourly 'group' is kept. The operation of this table is same as that of teldatNsmStatsCaptureTable, except information is only distributed in one hourly group, and there is no division according to 'path', 'hop' or statistical distribution buckets.

A list of objects which accumulate the results of a series of RTT (Jitter) operations over a 60 minute time period. This entry is created only if the teldatNsmCtrlAdminRttType is jitter. The operation of this table is same as that of teldatNsmStatsCaptureTable, except information is only distributed in one hourly group, and there is no division according to 'path', 'hop' or statistical distribution buckets.

The time when this row was created.

The number of jitter operation that have completed successfully.

The number of jitter operations that violate threshold.

The number of RTT's that are successfully measured.

The sum of RTT's that are successfully measured.

The sum of squares of RTT's that are successfully measured (low order 32 bits).

The sum of squares of RTT's that are successfully measured (high order 32 bits).

The minimum of RTT's that were successfully measured.

The maximum of RTT's that were successfully measured.

The minimum of absolute values of all positive jitter values from packets sent from source to destination.

The maximum of absolute values of all positive jitter values from packets sent from source to destination.

The sum of number of all positive jitter values from packets sent from source to destination.

The sum of all positive jitter values from packets sent from source to destination.

The sum of square of RTT's of all positive jitter values from packets sent from source to destination (low order 32 bits).

The sum of square of RTT's of all positive jitter values from packets sent from source to destination (high order 32 bits).

The minimum of all negative jitter values from packets sent from source to destination.

The maximum of all negative jitter values from packets sent from source to destination.

The sum of number of all negative jitter values from packets sent from source to destination.

The sum of RTT's of all negative jitter values from packets sent from source to destination.

The sum of square of RTT's of all negative jitter values from packets sent from source to destination (low order 32 bits).

The sum of square of RTT's of all negative jitter values from packets sent from source to destination (high order 32 bits).

The minimum of all positive jitter values from packets sent from destination to source.

The maximum of all positive jitter values from packets sent from destination to source.

The sum of number of all positive jitter values from packets sent from destination to source.

The sum of RTT's of all positive jitter values from packets sent from destination to source.

The sum of squares of RTT's of all positive jitter values from packets sent from destination to source (low order 32 bits).

The sum of squares of RTT's of all positive jitter values from packets sent from destination to source (high order 32 bits).

The minimum of all negative jitter values from packets sent from destination to source.

The maximum of all negative jitter values from packets sent from destination to source.

The sum of number of all negative jitter values from packets sent from destination to source.

The sum of RTT's of all negative jitter values from packets sent from destination to source.

The sum of squares of RTT's of all negative jitter values from packets sent from destination to source (low order 32 bits).

The sum of squares of RTT's of all negative jitter values from packets sent from destination to source (high order 32 bits).

The number of packets lost when sent from source to destination.

The number of packets lost when sent from destination to source.

The number of packets arrived out of sequence.

The number of packets that are lost for which we cannot determine the direction.

The number of packets that arrived after the timeout.

The number of occasions when a jitter operation could not be initiated because an internal error.

The number of occasions when a jitter operation could not be initiated because a previous jitter operation has not been completed.

The sum of one way times from source to destination. This variable is not supported in current implementation.

The sum of squares of one way times from source to destination (low order 32 bits). This variable is not supported in current implementation.

The sum of squares of one way times from source to destination (high order 32 bits). This variable is not supported in current implementation.

The minimum of all one way times from source to destination. This variable is not supported in current implementation.

The maximum of all one way times from source to destination. This variable is not supported in current implementation.

The sum of one way times from destination to source. This variable is not supported in current implementation.

The sum of squares of one way times from destination to source (low order 32 bits). This variable is not supported in current implementation.

The sum of squares of one way times from destination to source (high order 32 bits). This variable is not supported in current implementation.

The minimum of all one way times from destination to source. This variable is not supported in current implementation.

The maximum of all one way times from destination to source. This variable is not supported in current implementation.

The number of one way times that are successfully measured. This variable is not supported in current implementation.

A table which contains the status of latest HTTP RTT operation.

A list of objects that record the latest HTTP RTT operation. This entry is created automatically after the teldatNsmCtrlAdminEntry is created. Also the entry is automatically deleted when teldatNsmCtrlAdminEntry is deleted.

Round Trip Time taken to perform HTTP operation. This value is the sum of DNSRTT, TCPConnectRTT and TransactionRTT.

Round Trip Time taken to perform DNS query within the HTTP operation. If an IP Address is specified in the URL, then DNSRTT is 0.

Round Trip Time taken to connect to the HTTP server.

Round Trip Time taken to download the object specified by the URL.

The size of the message body received as a response to the HTTP request.

An application specific sense code for the completion status of the latest RTT (NSM HTTP) operation.

An sense description for the completion status of the latest RTT (NSM HTTP) operation.

A table which contains the status of latest Jitter operation.

A list of objects that record the latest Jitter operation.

The number of RTT's that were successfully measured.

The sum of Jitter RTT's that are successfully measured.

The sum of squares of RTT's that are successfully measured.

The minimum of RTT's that were successfully measured.

The maximum of RTT's that were successfully measured.

The minimum of all positive jitter values from packets sent from source to destination.

The maximum of all positive jitter values from packets sent from source to destination.

The sum of number of all positive jitter values from packets sent from source to destination.

The sum of RTT's of all positive jitter values from packets sent from source to destination.

The sum of square of RTT's of all positive jitter values from packets sent from source to destination.

The minimum of absolute values of all negative jitter values from packets sent from source to destination.

The maximum of absolute values of all negative jitter values from packets sent from source to destination.

The sum of number of all negative jitter values from packets sent from source to destination.

The sum of all negative jitter values from packets sent from source to destination.

The sum of square of RTT's of all negative jitter values from packets sent from source to destination.

The minimum of all positive jitter values from packets sent from destination to source.

The maximum of all positive jitter values from packets sent from destination to source.

The sum of number of all positive jitter values from packets sent from destination to source.

The sum of RTT's of all positive jitter values from packets sent from destination to source.

The sum of squares of RTT's of all positive jitter values from packets sent from destination to source.

The minimum of all negative jitter values from packets sent from destination to source.

The maximum of all negative jitter values from packets sent from destination to source.

The sum of number of all negative jitter values from packets sent from destination to source.

The sum of RTT's of all negative jitter values from packets sent from destination to source.

The sum of squares of RTT's of all negative jitter values from packets sent from destination to source.

The number of packets lost when sent from source to destination.

The number of packets lost when sent from destination to source.

The number of packets arrived out of sequence.

The number of packets that are lost for which we cannot determine the direction.

The number of packets that arrived after the timeout.

An application specific sense code for the completion status of the latest Jitter RTT operation.

An sense description for the completion status of the latest Jitter RTT operation. It is a zero-length string in current implementation.

The sum of one way latency from source to destination. This variable is not supported in current implementation.

The sum of squares of one way latency from source to destination. This variable is not supported in current implementation.

The minimum of all one way latency from source to destination. This variable is not supported in current implementation.

The maximum of all one way latency from source to destination. This variable is not supported in current implementation.

The sum of one way latency from destination to source. This variable is not supported in current implementation.

The sum of squares of one way latency from destination to source. This variable is not supported in current implementation.

The minimum of all one way latency from destination to source. This variable is not supported in current implementation.

The maximum of all one way latency from destination to source. This variable is not supported in current implementation.

The number of successful one way latency measurements. This variable is not supported in current implementation.

The compliance statement for new MIB extensions without the obsolete items.

A collection of objects providing the NSM (RTT) Monitoring Application defaults and global information. This group of information is provided to the agent when the application starts.

A collection of objects providing the Administration, Operational, Last Statistical values for the NSM (RTT) Monitoring Application, a collection of objects that were added to enhance the functionality of the RTT application and a collection of objects that were added to enhance the functionality of the RTT application to configure HTTP, DNS and Jitter probes.

A collection of objects providing accumulated statistical history.

A collection of objects that were added to store the latest operational results for HTTP and Jitter probes.