MIDLEVELMGR-MIB: View SNMP OID List / Download MIB

Official name of the Mid-Level Manager.

Program number for the Mid-Level Manager.

Version number of the Mid-Level Manager.

Date and time when the Mid-Level Manager was compiled.

Time (in hundredths of a second) since the Mid-Level Manager was last re-initialized.

Textual identification of the contact person for the Mid-Level Manager on this managed node and information on how to contact this person.

Name of a local configuration file. When this field is set to a file name and smMlmProgramControlSaveConfiguration is set to true, a local configuration file is written to the path specified. When the Mid-Level Manager is reinitialized this file may be used as a configuration file if the '-i' option is used in conjunction with a '-c ', where the corresponds to the path of this local configuration file. This can be thought of as a 'Save As...' file to record the current configuration for future rollback if necessary.

Saved flags which will be used to start the agent. This field can be modified to be used with the smMlmProgramControlReInitializeMonitor function. The flags are saved in the file: /usr/etc/midmand.flags. On NT the flags are saved in the file: smv2/mlmv2.flg (for mlmv2).

Address of the box where MLM is running. This address is used while generating traps.

Maximum number of Tcp traps which are queued when the Tcp connection is down. Default value is 2048.

reserved.

The number of samples per interval to use for baselining and statistics. Default value is 10.

The maximum number of outstanding ping requests allowed for status checking. Default is 32.

Default number of retries for actions that can be retried. Not implemented.

Default number of timeout for actions that can timeout. Not implemented.

Current flags which were used to start or re-initialize the agent.

Re-intialize flags which will be used to start the agent. This field can be modified to be used with the smMlmProgramControlReInitializeMonitor function. For NT, this variable provides the time the Mid-Level Manager was last initialized. A SET to this will reinitialize the program. New command-line parameters can optionally be provided on the set. If no value is passed on the set (or if the 'last initialized' time string is passed), the Mid-Level Manager will reinitialize using original command-line parameters.

Allows the re-initializaton of the Mid-Level Manager Agent. Setting to trueReinit(2) uses the flags in smMlmProgramControlReinitFlags as the start-up flags. Setting to trueSaved(3) uses the flags in smMlmProgramControlSavedFlags as the start-up flags. The value of this variable returns to false once the re-start has occurred. Enumeration: 'trueSaved': 3, 'false': 1, 'trueReinit': 2.

Setting this variable to true(2) results in the current Mid-Level Manager Agent configuration being saved to the file specified by the value of the smMlmProgramControl LocalConfigurationFile variable. The value of this variable returns to false once the configuration is saved. Enumeration: 'true': 2, 'false': 1.

File name for logging information in the Mid-Level Manager Agent. The type of information being logged depends on the trace mask (ie. smMlmProgramLogMask).

Current size of the log file in bytes.

Maximum size of the log file in kilobytes.

Maximum number of log files to keep. When the data log file is full, it is rolled over to 1. Files are rolled up until the number of files specified by this field exists (ie. 1 becomes 2, etc.).

This field determines what is done when the maximum file size is exceeded and the number of log files specified already exists. If wrap is specified, then the oldest log file is removed, all other files are rolled up, and logging continues into a new file. If nowrap is specified, no more data will be logged until either the log file name is changed or the existing files are renamed (or removed). Flushing refers to whether or not each log entry is immediately written to the log file or whether the log data is written out in large chunks containing multiple log entries. Flushing allows the log file to always contain the latest log entries. However, CPU time can be saved if flushing is not activated. Enumeration: 'nowrapFlush': 3, 'nowrapNoflush': 4, 'wrapNoflush': 2, 'wrapFlush': 1.

The log mask field is used to indicate the type of information that is being logged. The log mask may contain the following literals: none logs nothing inform logs informational messages warning logs warning messages error logs error messages base logs Remote Manager base information command logs command table information filter logs filter table information analysis logs analysis table information threshold logs threshold table information polling logs MIB variable polling information smux logs SMUX interface traffic binary logs packets sent/received in binary call logs all internal functions called all logs all information For NT the log mask may contain the following literals: binary - logs packets sent/received in binary also invokes the call literal, call - logs all internal functions called, all - logs all information, screen - logs information to the screen

The data collection filename refers to the file used to store the data associated with the entries in the threshold table. The corresponding threshold table entry must have it's state set to enabledStoreOnly or enabledThresholdStore in order for data to be collected.

This field contains the current size of the collection file in bytes.

Maximum size of the data collection file in kilobytes. The action taken when the collection file contains this MaxFileSize Kbytes is determined by the data collection FileBehavior MIB variable.

This field refers to the number of collection files to keep. When the data collection file is full, is rolled up to 1 (where refers to the file defined by the DataCollectionFileName MIB variable). Files are 'rolled up' until the number of files specified by this field exists (ie. 1 becomes 2, etc.).

This field determines what is done when the maximum file size is exceeded AND the number of collection files specified already exists. If wrap is specified, then the oldest collection file is removed, all other files are rolled up, and collection continues into a new file. If nowrap is specified, no more data will be collected until either the collection file name is changed or the existing files are renamed (or removed). Flushing refers to whether or not each collection entry is immediately written to the log file or whether the collection data is written out in large chunks containing multiple collection entries. Flushing allows the collection file to always contain the latest collection entries. However, CPU time can be saved if flushing is not activated. Enumeration: 'nowrapFlush': 3, 'nowrapNoflush': 4, 'wrapNoflush': 2, 'wrapFlush': 1.

A settable integer with no function.

A settable counter with no function.

A settable gauge with no function.

A settable IP address with no function.

A settable TimeTicks with no function.

A settable DisplayString with no function.

File name for logging information about traps that are received by the Mid-Level Manager. The type of information being logged depends on the trace mask (ie. smMlmProgramTrapLogMask).

Current size of the trap log file in bytes.

Maximum size of the trap log file in kilobytes.

Maximum number of trap log files to keep. When the log file is full, it is rolled over to 1. Files are rolled up until the number of files specified by this field exists (ie. 1 becomes 2, etc.).

This field determines what is done when the maximum file size is exceeded and the number of trap log files specified already exists. If wrap is specified, then the oldest trap log file is removed, all other files are rolled up, and logging continues into a new file. If nowrap is specified, no more data will be logged until either the trap log file name is changed or the existing files are renamed (or removed). Flushing refers to whether or not each log entry is immediately written to the trap log file or whether the log data is written out in large chunks containing multiple log entries. Flushing allows the trap log file to always contain the latest log entries. However, CPU time can be saved if flushing is not activated. Enumeration: 'nowrapFlush': 3, 'nowrapNoflush': 4, 'wrapNoflush': 2, 'wrapFlush': 1.

Not yet implemented .

Mid-Level Manager resource utilization table.

Each entry contains a different resource summary.

Self, child, and total.

Amount of CPU time in user mode since start-up.

Amount of CPU time in system mode since start-up.

Total CPU time for process since start-up.

Maximum resident set size.

Integral size (kilobyte-seconds).

Unshared resident set size (kilobyte-seconds).

Unshared stack set size (kilobyte-seconds). Not supported on HP-UX

Page faults serviced without I/O activity.

Page faults serviced with I/O activity.

Number of times a process swapped.

Number of times a file system performed input.

Number of times a file system performed output.

Number of IPC messages sent.

Number of IPC messages received.

Number of signals received.

Number of voluntary context switches.

Number of involuntary context switches.

Mid-Level Manager information and error messages.

Each entry contains a different message summary.

Table index - no real meaning.

Time at which the message was generated.

Text of the message. Truncated after 80 bytes

Time (in seconds) at which message was generated.

Mid-Level Manager information and error messages.

Each entry contains a different message summary.

Table index - no real meaning.

Time at which the message was generated.

Text of the message. Truncated after 80 bytes

Time (in seconds) at which message was generated.

Mid-Level Manager information and error messages.

Each entry contains a different message summary.

Table index - no real meaning.

Time at which the message was generated.

Text of the message. Truncated after 80 bytes

Time (in seconds) at which message was generated.

Host Address of the system running Mid-Level Manager.

Host name of the system running Mid-Level Manager.

Domain name of the Mid-Level Manager.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the threshold table entry command name. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable that indicates whether the threshold is in arm or rearm state. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the condition operation for threshold value. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the value of the condition against which the variable value is tested. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the name of the node which was polled. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the name of the proxy on the node which was polled. Null if not a proxy. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the address of the node which was polled. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the domain name of the node which was polled. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the port corresponding to the subagent or the proxy agent at the node which was polled. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the object Identifier of the variable polled. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the type of the variable polled. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the value of the variable polled. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the value of the rearm or arm severity. The object id of the environment variable is carried in the threshold trap.

This field is not accessible. It is inserted in MIB to obtain an object id for the environment variable containing the object Identifier instance of the variable polled. The object id of the environment variable is carried in the threshold trap.

The number of open sessions.

Session table - list of nodes with which this agent is communicating.

Each entry contains objects for a particular device

Name or IP address of the node in the Mid-Level Manager monitor session.

Last known state of session Enumeration: 'down': 1, 'up': 2.

Time at which session state last changed.

Time at which session was last polled.

Address family used to communicate with session Enumeration: 'hylink': 15, 'osi': 7, 'unix': 1, 'intf': 20, 'rif': 21, 'implink': 3, 'reserved31': 31, 'netware': 22, 'unknown': 65535, 'dli': 13, 'sna': 11, 'chaos': 5, 'datakit': 9, 'ns': 6, 'reserved32': 32, 'inet': 2, 'reserved30': 30, 'ccitt': 10, 'xtpPseudo': 19, 'link': 18, 'decnet': 12, 'lat': 14, 'pup': 4, 'route': 17, 'reserved28': 28, 'reserved29': 29, 'appletalk': 16, 'reserved26': 26, 'reserved23': 23, 'reserved24': 24, 'reserved25': 25, 'ecma': 8, 'reserved27': 27.

Remote Address of session.

Number of send transmit attempts made on session.

Number of packets received on session.

Last Time at which a transmission was sent

Last Time at which a packet was received

Minimum round-trip time to session since start-up.

Average response time for the most recent queries.

Average response time since start-up.

Maximum round-trip time to session since start-up.

Time stamp at which the SessionMinimumResponseTime was set.

Time stamp at which the SessionMaximumResponseTime was set.

Proxy Address of session, if session is with a proxy agent.

Remote port of session.

Domain Name of session.

Interface status table. This table is used to store the status and status checking protocol (ie. ICMP for IP) for each interface. This table is populated as a direct result of entries in the smMlmStatusMonitorTable.

Each entry contains objects for a status checking policy. The configuration specified is applied to all nodes and interfaces in the specified host.

This indicates the transport protocol used and determines the status checking protocol to be used. Enumeration: 'hylink': 15, 'osi': 7, 'unix': 1, 'intf': 20, 'rif': 21, 'implink': 3, 'reserved31': 31, 'netware': 22, 'unknown': 65535, 'dli': 13, 'sna': 11, 'chaos': 5, 'datakit': 9, 'ns': 6, 'reserved32': 32, 'inet': 2, 'reserved30': 30, 'ccitt': 10, 'xtpPseudo': 19, 'link': 18, 'decnet': 12, 'lat': 14, 'pup': 4, 'route': 17, 'reserved28': 28, 'reserved29': 29, 'appletalk': 16, 'reserved26': 26, 'reserved23': 23, 'reserved24': 24, 'reserved25': 25, 'ecma': 8, 'reserved27': 27.

This field specifies the address of the interface in octets.

This field specifies the address of the interface as a printable string.

This field specifies the hostname that corresponds to the address specified in the smMlmNetworkIfStatusNetAddress field.

This field is used to correlate this entry with the status monitor entry that governs the status checking of this interface.

The frequency at which the interface is being status checked. This field reflects the frequency configured in the governing status monitoring entry. It is displayed for information purposes only. In order to change this field the corresponding governing status entry's frequency must be changed or a new status entry may be introduced for this interface which overrides the existing entry.

This indicates the current status of the interface. Enumeration: 'down': 2, 'unknown': 1, 'up': 3.

This field displays the date/time string of the last state change.

This field displays the date/time string of the last time the interface status was checked.

This field displays the date/time string of the last time the status response was received.

Setting this field to true(1) will reset the counts for packets sent/received and last/max/min/avg roundtrip times. Enumeration: 'true': 2, 'false': 1.

This field contains a count of the total number of status request packets sent since the entry was instantiated (or the statistics were reset).

This field contains a count of the total number of status response packets received since the entry was instantiated (or the statistics were reset).

This field contains the number of time ticks from the time the status packet was sent until its response was received.

This field contains the average round trip time of the status packets received since the entry was instantiated (or the statistics were reset).

This field contains the minimum round trip time of the status packets received since the entry was instantiated (or the statistics were reset).

This field contains the time stamp for the minimum round trip time.

This field contains the maximum round trip time of the status packets received since the entry was instantiated (or the statistics were reset).

This field contains the time stamp for the maximum round trip time.

This field displays the date/time string of the last up time.

This field displays the date/time string of the last down time.

Threshold table.

Each entry contains objects for a particular threshold.

State for the threshold operation. The store operation allows the saving of the MIB variable data in a file during the threshold polling process. The threshold operation checks the value of retrieved variables against a threshold; these operations can be combined. When the threshold entry is enabled, it may participate based on threshold activation or deactivation times. The threshold entry is participating if the smMlmThresholdParticipationState is set to active. Enumeration: 'disabled': 1, 'enabledThresholdStore': 5, 'enabledStoreOnly': 4, 'invalid': 2, 'enabledThresholdOnly': 3.

This field is used as a label and as the SNMP instance identifier for variables in this row. The threshold name is appended to the row variable to uniquely identify the instance variable. For example, the instance of smMlmThresholdState (object ID .1.3.6.1.4.1.2.6.12.5.1.1.1) for a threshold entry named A is 65, with the full object identifier being .1.3.6.1.4.1.2.6.12.5.1.1.1.65. Each octet in in smMlmThresholdName is a value in dot notation for the variable.

This is a description of the threshold being performed for the benefit of administrators only; it is not used by the agent.

Owner ID (IP address or hostname) who generated this entry (not currently used).

This field specifies the MIB variable or expression on which thresholding is to be performed, in dotted numeric notation, followed by an instance identifier. For example, to perform threshold checking mib-2.interfaces.ifTable.ifEntry.ifInErrors (object ID .1.3.6.1.2.1.2.2.1.14) for interface 1, this field would contain .1.3.6.1.2.1.2.2.1.14.1. To perform threshold checking on all instances of a variable, an asterisk can be used. In the previous example, to perform threshold checking on all interfaces, the object ID .1.3.6.1.2.1.2.2.1.14.* would be entered. The instance ID can also be a non-numeric string, in which case each octet in the string is converted to an object identifier. For example, to threshold on the smMlmSystemFileSystemPercentUsed variable (object ID .1.3.6.1.4.1.2.6.12.2.5.2.1.4) for the /usr directory, .1.3.6.1.4.1.2.6.12.2.5.2.1.4./usr would be placed in this field since the Remote Manager filesystem table uses the directory name as the index. Most of the tables supported by the Remote Manager use a name as an index, so using the character form of the name provides a simple way to specify an instance identifier. Threshold MIB variable expressions can be any expression comprised of local or remote node MIB variables with the following high to low precedence and left to right associativity of operators: () : grouping - : unary minus * : multiplication, / : division, % : remainder + : addition, - : subtraction << : bitwise left shift, >> : bitwise right shift & : bitwise AND ^ : bitwise exclusive OR | : bitwise inclusive OR Expression evaluation/operators are based on standard c program execution. Counter MIB variables default to the delta value, calculated by subtracting the old MIB value from the current MIB value. Integer and gauge MIB variables default to the current value returned. The two functions @delta() and @value() can be used to override the above defaults. Displaystrings can be converted to a real value using the @delta() and @value() functions. Built-in functions available within expressions include: @sum(MIB variable expression, MIB variable expression, ...) - returns the sum of all values. @avg(MIB variable expression, MIB variable expression, ...) - returns the average of all values. @min(MIB variable expression, MIB variable expression, ...) - returns the minimum of all values. @max(MIB variable expression, MIB variable expression, ...) - returns the maximum of all values. @diff(MIB variable expression, MIB variable expression) - returns the positive difference in the two expressions. @delta(MIB variable expression) - uses the delta value calculated by subtracting the last returned MIB variable value from the current MIB variable value. This function can be used to force delta calculations on integer, gauge, and displaystring MIB variables. @value(MIB variable expression) - uses the current MIB variable value. This function can be used to force the use of actual values for counter MIB variables. @numInst(MIB variable expression) - returns the number of instances found for the MIB variable expression. @abs(MIB variable expression) - returns the positive value of the expression. @rand() - returns a random number between 0 and 42949667295. The \ character can be used as an escape character in the object ID to input the special character: period(.). For example: .1.3.6.1.2.1.2.2.1.14.1.\. replaces the \. with the integer 46, the ASCII decimal value for period(.). Agent Policy Manager (APM) uses the special string: {NV_x.x.x.x} as part of the object ID and the periods within the string ARE converted to the ASCII decimal value of 46. In other words, the periods are treated as characters instead of object ID delimiters. When using the Mid-Level Manager, if a name followed by a colon is prepended to the object identifier, it is taken to be an alias for a group of nodes (if defined in the Remote Manager Alias Table) or the name of a remote node. For example, entering aixnm007:1.3.6.1.2.1.2.2.1.14.* will cause threshold checking to be performed on all instances of ifInErrors on machine aixnm007. If aixnm007 is defined in the Alias Table as an alias for a group of machines, threshold checking of these variables will be done for every machine in the group.

Condition operation for the threshold value. [type keyword] [statistics keyword] condition Allowed conditions are: =, >, >=, >+, <, <=, <-, !=, !, ~, ~=, !~, !~=, &, |, changes, doesNotChange, exists, and doesNotExist. The ~(LIKE) condition is for extended regular expression checking on strings. The style of the regular expression is of the format for the ed or egrep command. The ~(LIKE) is case insensitive, while the ~=(LIKE CASE) is case sensitive. The >+ and <- condition checks for a value increase(>+) above or a value decrease(<-) below the threshold value on consecutive polls. Once the condition is met the rearm condition is also checked on consecutive polls. The change condition causes a watchdog operation to be performed. That is, if the value changes between consecutive polls, the condition is satisfied. (The threshold value is ignored in this case). Similarly, the exist/doesNotExist checks for the actual existence of the MIB variable; this is useful for checking for the existence of rows in a table. The & and | conditions cause the MIB variable value to be ANDed/Ored with threshold value; if the result is nonzero, the condition is met and the trap and/or command to execute is performed. NOTE: Thresholds for Counter variables are computed by calculating the change(delta) in the sampled values and comparing this against the threshold value. In the case of Gauge and INTEGER variables, the actual value of the variable is checked against the threshold value. The statistics keywords 'iMax', 'iMin', 'iAvg', 'iSd', 'iVar', 'iRate', 'Max', 'Min', 'Avg', 'Sd', and 'Var' if placed in front of the condition (and separated from if by a space) allows the use of the interval or lifetime maximum, minimum, average, standard deviation, variance, and rate. These values are calculated for each MIB variable returned in the threshold. For the interval keywords the sampling interval is defined by the MIB variable: smMlmProgramControlSamplesPerInterval. For example, if the smMlmProgramControlSamplesPerInterval is 10 then the 'iAvg' keyword is the average value of the last ten samples returned to the threshold for each MIB value. The type keywords 'delta' and 'value', if placed in front of the condition or statistics keywords (and separated from it by a space) will override this default behavior. For example, a condition of 'value >' will cause threshold checking to be performed against the actual value rather than the change in the value even if the selected MIB variable is a Counter; a condition of 'delta >' causes the change in the variable (from the previous value) to be checked against the threshold, regardless of the type of the variable.

This field specifies the value against which retrieved variables are checked. The type of check which is done depends on the type of the retrieved variable. If the variable is numeric (INTEGER, Counter, etc.) this field is presumed to be a number, and a numeric comparison is performed using the specified threshold condition. If the retrieved variable is a DisplayString (OCTET STRING) and the 'value' keyword is used on the condition then both the retrieved variable and this field can be converted to a floating point number, a floating-point comparison is done; otherwise a string comparison is done. If the ~(LIKE) or ~=(LIKE CASE) condition is used then the value can be an extended regular expression. A value expression is also allowed to be specified. The expression can be any expression comprised of the following functions: 'Min' - lifetime minimum 'iMin' - interval minimum 'Max' - lifetime maximum 'iMax' - interval maximum 'Avg' - lifetime average 'iAvg' - interval average 'Sd' - lifetime standard 'iSd' - interval standard deviation deviation 'Var' - lifetime variance 'iVar' - interval variance 'Smpls' - lifetime samples 'iSmpls' - interval samples 'sTime' - sample time in secs 'iTime' - interval time in secs 'iRate' - rate of change over the interval The interval is defined by the MIB variable: smMlmProgramControlSamplesPerInterval. The expression has the following high to low precedence and left to right associativity of operators: () : grouping - : unary minus * : multiplication, / : division, % : remainder + : addition, - : subtraction << : bitwise left shift, >> : bitwise right shift & : bitwise AND ^ : bitwise exclusive OR | : bitwise inclusive OR Expression evaluation/operators are based on standard c program execution. For example: Avg+2*Sd is the average value over the lifetime of the threshold plus two times the standard deviation.

Threshold polling time. Polling units are decimal values appended by the unit: d - day, h - hour, m - minute, or s - second. If no unit is appended, the value is minutes. Multiple values/units are allowed (i.e. 1h45m = 1 hour, 45 minutes). The default poll time is 1 minute.

Last threshold value retrieved, in human-readable form. If more than one numeric value was retrieved for the threshold (because an alias was used or because multiple instances were retrieved), this field contains a note to see the Threshold Results Table for multiple results.

Not Implemented.

Not Implemented.

Not Implemented.

This field specifies the severity for the trap which is to be sent when an arm condition is met. Default is 1.

This field specifies the severity for the trap which is to be sent when a rearm condition is met. Default is 0.

Index to point to the expression result type. The index defines how the expression is evaluated, either using signed arithmetic for integer or unsigned arithmetic for counter and gauge. The result for counter wraps on overflow or underflow; the result for gauge latches at 0 for underflow or 4294967295 for overflow. Default value is integer. Enumeration: 'integer': 2, 'counter': 3, 'gauge': 4.

When enabled the threshold result(s) are stored in the Threshold Result Table. When disabled, no entries are generated for the Threshold Result Table. Default is enabled. Enumeration: 'disabled': 2, 'enabled': 1.

A human-readable description for the trap to be generated; this description is sent in the trap for operator use. The environment variables listed below, pre-appended with a $ sign, are allowed in the trap description field. SM6K_HOSTNAME={hostname running subagent} SM6K_DOMAIN_NAME={fully qualified hostname} SM6K_HOST_ADDRESS={ip address} SM6K_INSTANCE_NAME={instance string of row} SM6K_INSTANCE_ID={instance ASCII octet value of row} SM6K_THRESHOLD_CONDITION={condition in the threshold} SM6K_THRESHOLD_VALUE={threshold value} SM6K_THRESHOLD_ARMSTATE={-1 for arm, 0 for rearm} SM6K_THRESHOLD_THROTTLE_COUNT={count for arm or rearm} SM6K_THRESHOLD_NODE={node on which threshold condition was met} SM6K_THRESHOLD_VAR_OID={Object ID of variable for the threshold} SM6K_THRESHOLD_VAR_INSTANCE={instance for Object ID} SM6K_THRESHOLD_VAR_TYPE={Integer|Counter|Gauge} SM6K_THRESHOLD_VAR_VALUE={value of variable for the threshold} SM6K_THRESHOLD_VAR_OLDVALUE={previous value of variable} SM6K_THRESHOLD_SEVERITY={severity of threshold condition}

This field specifies the SNMP enterprise id for the trap which is to be sent when a threshold condition is met. If this is not set, a default will be used.

This field specifies a specific trap number to be sent when a threshold condition is met. If this value is zero, no trap will be sent.

Command to execute when threshold is met. A value of blank means no command is to be executed on a threshold met condition. Environment variables which are available on execution are: SM6K_HOSTNAME={hostname running subagent} SM6K_DOMAIN_NAME={fully qualified hostname} SM6K_HOST_ADDRESS={ip address} SM6K_INSTANCE_NAME={instance string of row} SM6K_INSTANCE_ID={instance ASCII octet value of row} SM6K_EXECUTION_REASON=Threshold SM6K_THRESHOLD_CONDITION={condition in the threshold} SM6K_THRESHOLD_VALUE={threshold value} SM6K_THRESHOLD_ARMSTATE={-1 for arm, 0 for rearm} SM6K_THRESHOLD_THROTTLE_COUNT={count for arm or rearm} SM6K_THRESHOLD_NODE={node on which threshold condition was met} SM6K_THRESHOLD_VAR_OID={Object ID of variable for the threshold} SM6K_THRESHOLD_VAR_INSTANCE={instance for Object ID} SM6K_THRESHOLD_VAR_TYPE={Integer|Counter|Gauge} SM6K_THRESHOLD_VAR_VALUE={value of variable for the threshold} SM6K_THRESHOLD_VAR_OLDVALUE={previous value of variable} SM6K_THRESHOLD_SEVERITY={severity of threshold condition}

Condition operation for the rearm threshold value. [type keyword] [statistics keyword] condition Allowed conditions are: =, >, >=, >+, <, <=, <-, !=, !, ~, ~=, !~, !~=, &, |, changes, doesNotChange, exists, and doesNotExist. Checking against the rearm condition is started when a threshold is reached and is stopped when the rearm condition is met. Once the rearm condition is met, the threshold condition operation is restarted. The ~(LIKE) condition is for extended regular expression checking on strings. The style of the regular expression is of the format for the ed or egrep command. The ~(LIKE) is case insensitive, while the ~=(LIKE CASE) is case sensitive. The >+ and <- condition checks for a value increase(>+) above or a value decrease(<-) below the threshold value on consecutive polls. Once the condition is met the arm condition is also checked on consecutive polls. NOTE: Thresholds for Counter variables are computed by calculating the change per second in the sampled values and comparing these against the threshold value. In the case of Gauge and INTEGER variables, the actual value of the variable is checked against the threshold value. The statistics keywords 'iMax', 'iMin', 'iAvg', 'iSd', 'iVar', 'iRate', 'Max', 'Min', 'Avg', 'Sd', and 'Var' if placed in front of the condition (and separated from if by a space) allows the use of the interval or lifetime maximum, minimum, average, standard deviation, variance, and rate. These values are calculated for each MIB variable returned in the threshold. For the interval keywords the sampling interval is defined by the MIB variable: smMlmProgramControlSamplesPerInterval. For example, if the smMlmProgramControlSamplesPerInterval is 10 then the 'iAvg' keyword is the average value of the last ten samples returned to the threshold for each MIB value. The type keywords 'delta' and 'value', if placed in front of the condition or statistics keywords (and separated from it by a space) will override this default behavior. For example, a condition of 'value >' will cause threshold checking to be performed against the actual value rather than the change in the value even if the selected MIB variable is a Counter; a condition of 'delta >' causes the change in the variable (from the previous value) to be checked against the threshold, regardless of the type of the variable.

This field specifies the value against which retrieved variables are checked. The type of check which is done depends on the type of the retrieved variable. If the variable is numeric (INTEGER, Counter, etc.) this field is presumed to be a number, and a numeric comparison is performed using the specified threshold condition. If the retrieved variable is a DisplayString (OCTET STRING) and the 'value' keyword is used on the condition then both the retrieved variable and this field can be converted to a floating point number, a floating-point comparison is done; otherwise a string comparison is done. If the ~(LIKE) or ~=(LIKE CASE) condition is used then the value can be an extended regular expression. A value expression is also allowed to be specified. The expression can be any expression comprised of the following functions: 'Min' - lifetime minimum 'iMin' - interval minimum 'Max' - lifetime maximum 'iMax' - interval maximum 'Avg' - lifetime average 'iAvg' - interval average 'Sd' - lifetime standard 'iSd' - interval standard deviation deviation 'Var' - lifetime variance 'iVar' - interval variance 'Smpls' - lifetime samples 'iSmpls' - interval samples 'sTime' - sample time in secs 'iTime' - interval time in secs 'iRate' - rate of change over the interval The interval is defined by the MIB variable: smMlmProgramControlSamplesPerInterval. The expression has the following high to low precedence and left to right associativity of operators: () : grouping - : unary minus * : multiplication, / : division, % : remainder + : addition, - : subtraction << : bitwise left shift, >> : bitwise right shift & : bitwise AND ^ : bitwise exclusive OR | : bitwise inclusive OR Expression evaluation/operators are based on standard c program execution. For example: Avg+2*Sd is the average value over the lifetime of the threshold plus two times the standard deviation.

Trap description for the generated rearm trap. The environment variables listed below, pre-appended with a $ sign, are allowed in the trap description field. SM6K_HOSTNAME={hostname running subagent} SM6K_DOMAIN_NAME={fully qualified hostname} SM6K_HOST_ADDRESS={ip address} SM6K_INSTANCE_NAME={instance string of row} SM6K_INSTANCE_ID={instance ASCII octet value of row} SM6K_THRESHOLD_CONDITION={condition in the threshold} SM6K_THRESHOLD_VALUE={threshold value} SM6K_THRESHOLD_ARMSTATE={-1 for arm, 0 for rearm} SM6K_THRESHOLD_THROTTLE_COUNT={count for arm or rearm} SM6K_THRESHOLD_NODE={node on which threshold condition was met} SM6K_THRESHOLD_VAR_OID={Object ID of variable for the threshold} SM6K_THRESHOLD_VAR_INSTANCE={instance for Object ID} SM6K_THRESHOLD_VAR_TYPE={Integer|Counter|Gauge} SM6K_THRESHOLD_VAR_VALUE={value of variable for the threshold} SM6K_THRESHOLD_VAR_OLDVALUE={previous value of variable} SM6K_THRESHOLD_SEVERITY={severity of threshold condition}

This field specifies the SNMP enterprise id for the trap which is to be sent when a rearm condition is met. If this is not set, a default will be used.

This field specifies a specific trap number to be sent when a rearm condition is met. If this value is zero, no trap will be sent.

Command to execute when the rearm threshold is met. A value of blank means no command will be executed on a rearm threshold met condition. Environment variables which are available on execution are: SM6K_HOSTNAME={hostname running subagent} SM6K_DOMAIN_NAME={fully qualified hostname} SM6K_HOST_ADDRESS={ip address} SM6K_INSTANCE_NAME={instance string of row} SM6K_INSTANCE_ID={instance ASCII octet value of row} SM6K_EXECUTION_REASON=Threshold SM6K_THRESHOLD_CONDITION={condition in the threshold} SM6K_THRESHOLD_VALUE={threshold value} SM6K_THRESHOLD_ARMSTATE={-1 for arm, 0 for rearm} SM6K_THRESHOLD_THROTTLE_COUNT={count for arm or rearm} SM6K_THRESHOLD_NODE={node on which threshold condition was met} SM6K_THRESHOLD_VAR_OID={Object ID of variable for the threshold} SM6K_THRESHOLD_VAR_INSTANCE={instance for Object ID} SM6K_THRESHOLD_VAR_TYPE={integer|counter|gauge} SM6K_THRESHOLD_VAR_VALUE={value of variable for the threshold} SM6K_THRESHOLD_VAR_OLDVALUE={previous value of variable} SM6K_THRESHOLD_SEVERITY={severity of threshold condition}

This field contains the name of the last node for which a threshold arm/rearm condition was met.

This field contains informational and error messages for this threshold entry.

This field contains the last time a (valid or invalid) response was received to a poll request.

Number of responses received to date.

Number of timeout conditions, indicating no response or an overrun condition (polling speed faster than the response time from the node(s) being queried).

Number of responses received containing no values. These responses may be caused by an invalid community name, by a remote SNMP subagent being down, or by a thresholding on a variable for which no instances exist.

This field contains the total count that the arm condition has been met.

This field contains the total count that the rearm condition has been met.

This field specifies the number of consecutive arm conditions which must be met before the threshold is armed. The ThresholdPollTime times the ThresholdThrottleArmCount minus 1 is the time interval in which the arm condition has been met. A value of 0 defaults to 1.

This field specifies the number of consecutive rearm conditions which must be met before the threshold is rearmed. The ThresholdPollTime times the ThresholdThrottleReArmCount minus 1 is the time interval in which the rearm condition has been met. A value of 0 defaults to 1.

This field indicates whether or not the entry is participating in the threshold. When the threshold entry is active, it is participating. When the threshold rule is inactive, it is not participating in the threshold, but will be participating when the activation time arrives. The participation state can be inactive only if activation/deactivation days are specified. Otherwise, the participation state is activated when the smMlmThresholdState field is set to enabled. If this field is set to notEnabled, the smMlmThresholdState field is not set to enabled. Enumeration: 'active': 2, 'inactive': 3, 'notEnabled': 1.

This field specifies the time to activate the threshold (ie. change the participation state from inactive to active). The format should be HH:MM where HH represents the hour (integer between 0 and 23) and MM represents the minute (integer between 0 and 59) to activate the threshold. A value all blanks will be interpreted as 00:00.

This field specifies the days of the week to activate the threshold at the time specified in the ActivationTime field (ie. change the participation state from inactive to active). The day of the week may be one of three literals: none - Doesn't Activate weekdays - Activates threshold entry on MTWThF all - Activates threshold entry every day SuMTWThFS Alternatively, the days of the week may be specified as a list of numbers between 0 and 6 (Sunday = 0, Monday = 1, ..., Saturday = 6). The expression '1,3,5' would activate the threshold entry at the specified time on MWF.

This field specifies the time to deactivate the threshold (ie. change the participation state from active to inactive). The format should be HH:MM where HH represents the hour (integer between 0 and 23) and MM represents the minute (integer between 0 and 59) to deactivate the threshold. A value all blanks will be interpreted as 00:00.

This field specifies the days of the week to deactivate the threshold at the time specified in the DeactivationTime field (ie. change the participation state from active to inactive). The day of the week may be one of three literals: none - Doesn't deactivate weekdays - Dectivates threshold entry on MTWThF all - Deactivates threshold entry every day SuMTWThFS Alternatively, the days of the week may be specified as a list of numbers between 0 and 6 (Sunday = 0, Monday = 1, ..., Saturday = 6). The expression '1,3,5' would deactivate the threshold entry at the specified time on MWF.

Threshold Arm Information table. This table provides the threshold arm status information. The table will be updated based on the results of the threshold condition checking. possible actions are as follows: * adds a new entry if in arm condition, threshold met, and no entry found. * removes an entry if in arm condition, threshold not met, and entry found, or if in rearm condition, and threshold met

Each entry contains the threshold name, node's IP address, and the mib's oid.

This field is the name of the threshold.

The IP address of the node.

The oid of the mib variable.

This field is simply used to append to the threshold name and IP address for uniqueness.

Threshold results table. This table provides the value results from the threshold table. The table is updated based on the results of the threshold table calculations. Possible actions are as follows: * adds a new entry if a new node/instance is found for the calculation. * removes an entry if a node/instance is not found for the previous calculation.

Each entry contains the threshold name, node's IP address, and the mib var's instance.

This field is the name of the threshold results.

The IP address of the node.

The instance identifier of the mib variable.

This field is simply used to append to the threshold name and IP address for uniqueness.

This field contains the date when the result was updated.

Index to point to output result type. The index defines how the expression is evaluated, either using signed arithmetic for integer or unsigned arithmetic for counter and gauge. The result for counter wraps on overflow or underflow; the result for gauge latches at 0 for underflow or 4294967295 for overflow. If the result is a string then the statistic information is not applicable. Enumeration: 'displaystring': 1, 'integer': 2, 'counter': 3, 'gauge': 4.

Integer result based on signed arithmetic.

Counter result based on unsigned arithmetic; this wraps at the maximum or minimum value.

Gauge result based on unsigned arithmetic; this latches at the maximum or minimum value.

Display result as a displayable string. This string is generated based on the ResultsIndex for the type of the resultant expression: integer, counter, or gauge.

Setting this field to true(1) will reset all the statistics information for this result. Enumeration: 'true': 2, 'false': 1.

Results life time integer minimum

Results life time integer maximum

Results life time integer data average

Results life time integer standard deviation

Results life time counter/gauge minimum

Results life time counter/gauge maximum

Results life time counter/gauge data average

Results life time counter/gauge standard deviation

Results life time samples

Results life time seconds

This field contains the date when the life time integer or counter/gauge minimum value was recorded.

This field contains the date when the lifetime integer or counter/gauge maximum value was recorded.

Results interval integer minimum

Results interval integer maximum

Results interval integer data average

Results interval integer standard deviation

Results interval counter/gauge minimum

Results interval counter/gauge maximum

Results interval counter/gauge data average

Results interval counter/gauge standard deviation

Results interval samples

Results interval seconds

Results interval seconds rate of change

Analysis table.

Each entry contains objects for a particular analysis.

State for the analysis operation: disabled (1), invalid (2), or enabled (3). Enumeration: 'disabled': 1, 'enabled': 3, 'invalid': 2.

Analysis name for use as a label and row instance. The selection of a row in the table uses the analysis name as the instance for row selection. The analysis name is appended to the row variable to uniquely identify the instance variable. For example, the instance of smMlmAnalysisState is smMlmAnalysisState.smMlmAnalysisName, where each octet in smMlmAnalysisName is a value in dot notation for the variable.

Analysis description for the analysis operation.

Owner ID (IP address or hostname) who generated the command entry. This must be initialized by the user.

Analysis MIB variable expression. The expression can be any expression comprised of local or remote (MLM only) node MIB variables with the following high to low precedence and left to right associativity of operators: () : grouping - : unary minus * : multiplication, / : division, % : remainder + : addition, - : subtraction << : bitwise left shift, >> : bitwise right shift & : bitwise AND ^ : bitwise exclusive OR | : bitwise inclusive OR Expression evaluation/operators are based on standard c program execution. Counter MIB variables default to the delta value, calculated by subtracting the old MIB value from the current MIB value. Integer and gauge MIB variables default to the current value returned. The two functions @delta() and @value() can be used to override the above defaults. Displaystrings can be converted to a real value using the @delta() and @value() functions. Built-in functions available within expressions include: @sum(MIB variable expression, MIB variable expression, ...) - returns the sum of all values. @avg(MIB variable expression, MIB variable expression, ...) - returns the average of all values. @min(MIB variable expression, MIB variable expression, ...) - returns the minimum of all values. @max(MIB variable expression, MIB variable expression, ...) - returns the maximum of all values. @diff(MIB variable expression, MIB variable expression) - returns the positive difference in the two expressions. @delta(MIB variable expression) - uses the delta value calculated by subtracting the last returned MIB variable value from the current MIB variable value. This function can be used to force delta calculations on integer, gauge, and displaystring MIB variables. @value(MIB variable expression) - uses the current MIB variable value. This function can be used to force the use of actual values for counter MIB variables. @numInst(MIB variable expression) - returns the number of instances found for the MIB variable expression. @abs(MIB variable expression) - returns the positive value of the expression. @rand() - returns a random number between 0 and 42949667295. To use remote MIB variables, the alias name, host name, or IP address can be pre-appended to the MIB variable binding. Also, the object ID can accept a wildcard value (*). When MIB variables resolve to multiple values or nodes outside of the built-in functions, all resolved values are averaged before use in the expression. For example, routers:.1.2.3.4.5.0/100, would result in the averaging of all values returned for this aliased MIB variable before the division by 100 operation is performed.

Analysis polling time. Polling units are decimal values appended by the unit: d - day, h - hour, m - minute, s - second, or u - millisecond. If no unit is appended, the value is minutes. Multiple values/units are allowed (i.e. 1h45m = 1 hour, 45 minutes). The default and minimum poll time is 1 minute. This polling value is used only by the MIB variable polling center for retrieval of the local or remote MIB variable for caching. This is required so that the MIB variable values are cached and not requested with GET requests when the expression is evaluated.

Index to point to command output result type. The index defines how the expression is evaluated, either using signed arithmetic for integer or unsigned arithmetic for counter and gauge. The result for counter wraps on overflow or underflow; the result for gauge latches at 0 for underflow or 4294967295 for overflow. Enumeration: 'integer': 2, 'counter': 3, 'gauge': 4.

Integer result based on signed arithmetic.

Counter result based on unsigned arithmetic; this wraps at the maximum or minimum value.

Gauge result based on unsigned arithmetic; this latches at the maximum or minimum value.

Display result as a displayable string. This string is generated based on the ResultIndex for the type of the resultant expression: integer, counter, or gauge.

Return code from the evaluation of the expression.

Standard error output from the evaluation of the expression.

Global default as to whether or not the traps received are to be sent or blocked. If the trap matches a filter entry, the action specified is taken. If the trap doesn't match a filter entry and sendTraps is specified, the trap destinations from the trap destination table are used. Enumeration: 'blockTraps': 2, 'sendTraps': 1.

Indicator of whether or not the Mid-Level Manager Agent should connect to the snmp trap socket using UDP. If enabled (1), the traps will be read from the udp port. If disabled (2), only traps generated by the Mid-Level Manager (e.g. thresholding, status, discovery traps) and traps read from the tcp socket will be filtered by the Mid-Level Manager. Note: This field cannot be set to enabled if another process on the host is already receiving traps (ie. the manager). Conversely, another process on the host (ie. the manager) will not be able to receive traps if this field is set to enabled. Therefore, if a manager is running on the same host as the Mid-Level Manager, this field should be set to disabled. If this field is set to enabled and any other process is connected to the port specified by the UdpTrapReceptionPort then UpdTrapReceptionStatus variable is set to portBusy. To check the availability of the port, this field should be disabled and then set to enabled. Enumeration: 'disabled': 2, 'enabled': 1.

Current count of the number of traps that have been received by the Mid-Level Manager. This count is reset to zero whenever both the UdpTrapReception MIB variable and the TcpTrapReception MIB variable are set to disabled (from a enabled state).

Entries defining a particular filter. Each entry may be thought of as a single filter. Each filter is evaluated against each incoming trap. When the filter criteria matches the trap, the corresponding filter actions are taken. The table is indexed by the smMlmFilterName field.

Each entry contains the components for a particular filter.

State for the filter rule. When the state is set to invalid, the filter is deleted. When the filter entry is set to disabled, the filter is dormant. When the filter rule is enabled, it may participate in the filter rule base. The filter rule is participating if the smMlmFilterParticipationState is set to active. Enumeration: 'disabled': 1, 'enabled': 3, 'invalid': 2.

This field indicates whether or not the rule is participating in the filter rule base. When the filter rule is active, it is participating. When the filter rule is inactive, it is not participating in the filter rule base, but will be participating when the activation time arrives. The participation state can be inactive only if activation/deactivation days are specified. Otherwise, the participation state is activated when the smMlmFilterState field is set to enabled. If this field is set to notEnabled, the smMlmFilterState field is not set to enabled. Enumeration: 'active': 2, 'inactive': 3, 'notEnabled': 1.

This field contains the name for a particular filter. The instance identifier associated with every field in the filter entry is derived from the name (dot separated ASCII codes). Therefore, this name must be unique among all other filter names.

Description of the filter. This field should contain a general description of what the filter accomplishes. A user should be able to read this information and know what filtering is being done as well as why it is being done.

This field is used to determine whether or not the matching trap is forwarded on to a manager station. If sendTraps is specified, then the trap destinations specified in the filter are included in the list of destinations to which the trap is forwarded. If blockTraps is specified, then the trap will not be forwarded unless another filter is matched that specifies the trap is to be sent. When this field is set to ThrottleTraps, the throttle expression needs to be evaluated in order to decide whether to send or block the received trap. Enumeration: 'throttleTraps': 3, 'blockTraps': 2, 'sendTraps': 1.

This field is used to match the rule against the enterpriseID contained in the received trap. This is the default enterpriseID expression. If in the specific trap expression, this particular specific trap number does not have any enterpriseID associated with it for matching then the trap is matched with this rule. The entry may be an alias name (from the smMlmAlias table), an enterpriseID in dot notation, or an enterpriseID with a wildcard value (terminated by an asterisk). The enterpriseID in dot notation should be fully qualified. An enterpriseID with a wildcard value matches any enterpriseID with the same partial enterpriseID.

This field is used to match against the address of the agent that generated the trap. For the Mid-Level Manager, the agent address expression is a comma separated list of: 1) an smMlmAliasName (from the smMlmAlias table) 2) a resolvable hostname 3) an ipAddress expression. If the agent address expression contains an smMlmAliasName or hostname, the addresses to check the trap against are determined each time a trap is received. An ipAddress expression contains four dot separated sub-expressions that can be either: 1) a decimal number between 0 and 255 2) an inclusive range of numbers between 0 and 255 specified by [#-#] (ie. [0-127]) 3) an asterisk (which is simply interpreted as [0-255]). An example ipAddress expression is '9.67.[128-130].*'.

This field is used to match against the generic trap number contained in the received trap. This field allows a comma separated list of generic trap numbers. If specific trap numbers are to be checked, a 6 (ie. enterprise-specific trap) must be encoded in the generic expression. The generic traps are: 0 - Cold Start 1 - Warm Start 2 - Link Down 3 - Link Up 4 - Authentication Failure 5 - EGP Neighbor Loss 6 - Enterprise Specific

This field is used to match against the specific trap number contained in the received trap along with the enterpriseID. This allows specific traps numbers to be grouped with enterpriseID. This field allows a comma separated list of specific groups or specific trap numbers or range of specific traps. A range of specific trap numbers may be specified by using the range format of '[#-#]' (ie. [100-199]). A group of specific trap numbers or range with EnterpriseID can be specified using the grouping format 'EnterpriseID(x,y,[a-b])' example: .1.3.6.1.4.1.2.6.12( 15, 20, [100-199]) This field will only be checked if a 6 (ie. enterprise-specific trap) is contained in the generic trap expression.

This field is used to match trap against the environment variables, set on the basis of MIB variables and other information flowing in the trap. The expression can be any expression with left operand as environment variable name( prepended with $) and right operand as values of variables or regular expression, with the following operators: () : grouping && : logical and || : logical or == : equal to != : not equal to < : less than <= : less than equal to > : greater than >= : greater than equal to ! : negation The precedence and associativity of operators is same as in c language and expression evaluation is based on standard c program execution. Set of environment variables that can be used in the expression are: SM6K_HOSTNAME={hostname running subagent} SM6K_DOMAIN_NAME={fully qualified hostname} SM6K_HOST_ADDRESS={ip address} SM6K_INSTANCE_NAME={instance string of row} SM6K_INSTANCE_ID={instance ASCII octet value of row} SM6K_EXECUTION_REASON=Filter_Matched|Filter_Armed| Filter_Disarmed SM6K_TRAP_ENTERPRISE={enterprise ID from the trap} SM6K_TRAP_AGENT_ADDRESS={IP address of the sending agent} SM6K_TRAP_GENERIC_NUM={generic trap number of the trap} SM6K_TRAP_SPECIFIC_NUM={specific trap number of the trap} SM6K_TRAP_TIME_TICKS={time ticks since the sending agent was started} SM6K_NUM_TRAP_VARS={number of MIB variables in the trap} SM6K_TRAP_VAR_OBJ_ID#={Object ID for MIB variable in trap} SM6K_TRAP_VAR_TYPE#=INTEGER|Counter|Gauge|TimeTicks| IpAddress|OCTET_STRING|Opaque| OBJECT_IDENTIFIER|NULL|Unknown SM6K_TRAP_VAR_VALUE#={value of the MIB object} where the # is replaced by the trap variable's positional number in the trap (starting at 1). Values can be in the form of integer, dot notation or string or hex string. If it is a string it should be within quotes. Format of regular expression is: RE:expression (within double quotes), where 'expression' is the extended regular expression in the style of ed or egrep command. example: Check for trap number 22 from System Information Agent. ( $SM6K_TRAP_ENTERPRISE == .1.3.6.1.4.1.2.6.12) && ( $SM6K_TRAP_SPECIFIC_NUM == 22 ) If the expression evaluates to TRUE, then the trap is matched.

This field contains the number of traps that have matched this filter. This count is reset to zero whenever the filter entry's state is set to enabled (from the disabled state).

This field specifies the time to activate the filter (ie. change the participation state from inactive to active). The format should be HH:MM where HH represents the hour (integer between 0 and 23) and MM represents the minute (integer between 0 and 59) to activate the filter. A value all blanks will be interpreted as 00:00.

This field specifies the days of the week to activate the filter at the time specified in the ActivationTime field (ie. change the participation state from inactive to active). The day of the week may be one of three literals: none - Doesn't Activate weekdays - Activates filter entry on MTWThF all - Activates filter entry every day SuMTWThFS Alternatively, the days of the week may be specified as a list of numbers between 0 and 6 (Sunday = 0, Monday = 1, ..., Saturday = 6). The expression '1,3,5' would activate the filter entry at the specified time on MWF.

This field specifies the time to deactivate the filter (ie. change the participation state from active to inactive). The format should be HH:MM where HH represents the hour (integer between 0 and 23) and MM represents the minute (integer between 0 and 59) to deactivate the filter. A value all blanks will be interpreted as 00:00.

This field specifies the days of the week to deactivate the filter at the time specified in the DeactivationTime field (ie. change the participation state from active to inactive). The day of the week may be one of three literals: none - Doesn't deactivate weekdays - Dectivates filter entry on MTWThF all - Deactivates filter entry every day SuMTWThFS Alternatively, the days of the week may be specified as a list of numbers between 0 and 6 (Sunday = 0, Monday = 1, ..., Saturday = 6). The expression '1,3,5' would deactivate the filter entry at the specified time on MWF.

This field specifies the destinations for any traps that match the filter criteria specified. This field allows ip addresses, alias names (from the smMlmAlias table) or resolvable hostnames separated by commas. If this field is left blank, the trap will be sent to the trap destinations specified in the smMlmTrapDestination table. Each host listed can specify a destination port number and protocol (tcp or udp ) or service name using the format: x+y/z where x can be ip address or hostname or alias name y can be port number or protocol or service name z can be port number or protocol. example: testhost+162/tcp or 9.67.162.81+udp/162 If the port or protocol is not specified then default value is used. The default port number is '162' and default protocol is 'udp'.

This field specifies the command to be executed when a received trap matches the filter. A set of environment variables are defined that contain information from the received trap. They may be used by the command that is executed. The following environment variables pertain to the Mid-Level Manager filter: SM6K_HOSTNAME={hostname running subagent} SM6K_DOMAIN_NAME={fully qualified hostname} SM6K_HOST_ADDRESS={ip address} SM6K_INSTANCE_NAME={instance string of row} SM6K_INSTANCE_ID={instance ASCII octet value of row} SM6K_EXECUTION_REASON=Filter_Matched|Filter_Armed| Filter_Disarmed The following environment variables pertain to the received trap: SM6K_TRAP_ENTERPRISE={enterprise ID from the trap} SM6K_TRAP_AGENT_ADDRESS={IP address of the sending agent} SM6K_TRAP_GENERIC_NUM={generic trap number of the trap} SM6K_TRAP_SPECIFIC_NUM={specific trap number of the trap} SM6K_TRAP_TIME_TICKS={time ticks since the sending agent was started} SM6K_NUM_TRAP_VARS={number of MIB variables in the trap} In addition, for each variable flowing in the trap: SM6K_TRAP_VAR_OBJ_ID#={Object ID for MIB variable in trap} SM6K_TRAP_VAR_TYPE#=INTEGER|Counter|Gauge|TimeTicks| IpAddress|OCTET_STRING|Opaque| OBJECT_IDENTIFIER|NULL|Unknown SM6K_TRAP_VAR_VALUE#={value of the MIB object} where the # is replaced by the trap variable's positional number in the trap (starting at 1) For more information see the accompanying documentation.

Not implemented

Not implemented

Not implemented

This field is used to indicate whether the throttle sends the first N matching traps (sendFirstN) or sends after receiving N matching traps (sendAfterN). The value of N is specified by the smMlmFilterThrottleArmTrapCount. Enumeration: 'sendFirstN': 1, 'sendAfterN': 2.

This field specifies the number of matching traps to receive before throttling is armed. This is the N referred to in the FilterThrottleType field.

This field specifies the command to execute when the ThrottleArmTrapCount number of traps have been received (ie. when the throttle is ARMED). A set of environment variables are defined that contain information from the received trap. They may be used by the command that is executed. The following environment variables pertain to the Mid-Level Manager filter: SM6K_HOSTNAME={hostname running subagent} SM6K_DOMAIN_NAME={fully qualified hostname} SM6K_HOST_ADDRESS={ip address} SM6K_INSTANCE_NAME={instance string of row} SM6K_INSTANCE_ID={instance ASCII octet value of row} SM6K_EXECUTION_REASON=Filter_Armed SM6K_THROTTLE_ARM_COUNT={value of ThrottleArmTrapCount} SM6K_THROTTLE_DISARM_COUNT={value of ThrottleDisarmTrapCount} SM6K_THROTTLE_DISARM_TIMER={value of ThrottleDisarmTimer} The following environment variables pertain to the received trap: SM6K_TRAP_ENTERPRISE={enterprise ID from the trap} SM6K_TRAP_AGENT_ADDRESS={IP address of the sending agent} SM6K_TRAP_GENERIC_NUM={generic trap number of the trap} SM6K_TRAP_SPECIFIC_NUM={specific trap number of the trap} SM6K_TRAP_TIME_TICKS={time ticks since the sending agent was started} SM6K_NUM_TRAP_VARS={number of MIB variables in the trap} In addition, for each variable flowing in the trap: SM6K_TRAP_VAR_OBJ_ID#={Object ID for MIB variable in trap} SM6K_TRAP_VAR_TYPE#=INTEGER|Counter|Gauge|TimeTicks| IpAddress|OCTET_STRING|Opaque| OBJECT_IDENTIFIER|NULL|Unknown SM6K_TRAP_VAR_VALUE#={value of the MIB object} where the # is replaced by the trap variable's positional number in the trap (starting at 1).

Not implemented

Not implemented

Not implemented

This field specifies the time period to elapse before the throttle is disarmed (reset). It is important to note that if smMlmThrottleDisarmTrapCount is set to a value greater than 0, the amount of time specified may not elapse before the throttle is disarmed. This time period is from the time the throttle is started (ie. from the time the first matching trap is received), not from the time the throttle is armed. Therefore, it is possible that the throttle will not be armed before the throttle is disarmed (reset). In this case, the disarm command is NOT executed.

This field specifies the delta number of traps to receive before the throttle is disarmed. This field value is a delta and only refers to the number of matching traps received AFTER the throttle has been armed. It is important to note that if the smMlmThrottleDisarmTimer is set, the number of matching traps specified may not occur before the throttle is disarmed.

This field specifies the command to execute when the throttle is DISARMED. The throttle is disarmed when either 1) the smMlmThrottleDisarmTrapCount matching traps have occurred after the throttle was armed, or 2) the smMlmFilterThrottleDisarmTimer has expired. NOTE: If the above mentioned timer expires and the throttle is NOT currently ARMED, the throttle is reset, but this disarm command is NOT executed. So, the disarm command is only executed if the throttle is armed before being disarmed. A set of environment variables are defined that contain information from the received trap. They may be used by the command that is executed. The following environment variables pertain to the Mid-Level Manager filter: SM6K_HOSTNAME={hostname running subagent} SM6K_DOMAIN_NAME={fully qualified hostname} SM6K_HOST_ADDRESS={ip address} SM6K_INSTANCE_NAME={instance string of row} SM6K_INSTANCE_ID={instance ASCII octet value of row} SM6K_EXECUTION_REASON=Filter_Disarmed SM6K_THROTTLE_ARM_COUNT={value of ThrottleArmTrapCount} SM6K_THROTTLE_DISARM_COUNT={value of ThrottleDisarmTrapCount} SM6K_THROTTLE_DISARM_TIMER={value of ThrottleDisarmTimer} The following environment variables pertain to the received trap: SM6K_TRAP_ENTERPRISE={enterprise ID from the trap} SM6K_TRAP_AGENT_ADDRESS={IP address of the sending agent} SM6K_TRAP_GENERIC_NUM={generic trap number of the trap} SM6K_TRAP_SPECIFIC_NUM={specific trap number of the trap} SM6K_TRAP_TIME_TICKS={time ticks since the sending agent was started} SM6K_NUM_TRAP_VARS={number of MIB variables in the trap} In addition, for each variable flowing in the trap: SM6K_TRAP_VAR_OBJ_ID#={Object ID for MIB variable in trap} SM6K_TRAP_VAR_TYPE#=INTEGER|Counter|Gauge|TimeTicks| IpAddress|OCTET_STRING|Opaque| OBJECT_IDENTIFIER|NULL|Unknown SM6K_TRAP_VAR_VALUE#={value of the MIB object} where the # is replaced by the trap variable's positional number in the trap (starting at 1).

Not implemented

Not implemented

Not implemented

This field is not supported. Enumeration: 'armed': 2, 'disarmed': 1.

This field is not supported.

This field is not supported.

Contains informational and error messages for this filter rule.

This field is used to indicate whether the throttle is to be applied on a per node and trap type basis (byNodeAndTrapType) or only per node basis (byNode) or only per trap type basis (byTrapType) or on all traps that match the filter rule (byNone). Enumeration: 'byNode': 2, 'byTrapType': 3, 'byNodeAndTrapType': 1, 'byNone': 4.

This field is used to set additional criteria for variables of which the traps will be throttled. These variables are contained in the trap and the position of the variable or variables is specified as a comma seperated list. A range of specific trap variables may be specified by using the range format of '[#-#]' (ie. [100-199]). For example, 1,[4-10],15, means the throttle uses variable binding postitions 1,4,5,6,7,8,9,10, and 15 as the additional throttle criteria.

Indicator of whether or not the Mid-Level Manager should connect to the tcp trap socket. If enabled(1), the traps will be read from the socket. If disabled(2), only traps generated by the Mid-Level Manager (e.g. thresholding, status, discovery traps) and traps received from the UDP socket will be filtered by the Mid-Level Manager. Note: This field cannot be set to enabled if another process on the host is already listening to the configured TCP port (i.e. the manager). Conversely, another process on the host (ie. the manager) will not be able to receive traps if this field is set to enabled. Therefore, if a manager is running on the same host as the Mid-Level Manager, this field should be set to disabled. If this field is set to enabled and any other process is connected to the port specified by the TcpTrapReceptionPort then TcpTrapReceptionStatus variable is set to portBusy. To recheck the availability of the port, this field should be disabled and then reset to enabled. Enumeration: 'disabled': 2, 'enabled': 1.

The status is set to enabled if TcpTrapReception is enabled if the Mid-Level Manager is able to connect to the TCP port. If TcpTrapReception is disabled then this status is set to disabled. This field is to portBusy when TcpTrapReception is enabled, but the Mid-Level Manager could not connect to the TcpTrapReceptionPort. Enumeration: 'disabled': 2, 'portBusy': 3, 'enabled': 1.

The status is set to enabled if UdpTrapReception is enabled if the Mid-Level Manager is able to connect to the UDP port. If UdpTrapReception is disabled then this status is set to disabled. This field is to portBusy when UdpTrapReception is enabled, but the Mid-Level Manager could not connect to the UdpTrapReceptionPort. Enumeration: 'disabled': 2, 'portBusy': 3, 'enabled': 1.

This field specifies the port number on which the MLM receives snmp traps via UDP.

This field specifies the port number on which the MLM receives snmp traps via TCP.

Contains informational and error messages about trap reception fields.

Alias table.

Each entry contains objects for a particular alias.

State of the alias entry: disabled (1), invalid (2), or enabled (3). Enumeration: 'disabled': 1, 'enabled': 3, 'invalid': 2.

Name that can be used in the threshold and analysis MIB variable definitions to allow multiple remote node retrieval of the MIB variable value.

List of alias names, host names, or IP addresses separated by white space or commas.

Expanded alias.

Trap destination table. This table is used to define the trap destinations for traps to be forwarded by the filtering piece of the subagent. It does not replace or update filtering entries in the snmpd.conf file. If filtering is being used, the snmpd.conf file should be setup to send traps to loopback.

Each entry contains objects for a particular trap destination.

State for the trap destination entry. Enabling this trap destination causes the traps being filtered to use this destination as a default destination (ie. the filtering entry may override where traps are to be sent). Enumeration: 'disabled': 1, 'enabled': 3, 'invalid': 2.

This field is simply used as the name of this entry.

This field specifies the hosts to which filtered traps are forwarded. It may be a list containing alias names (contained in the smMlmAlias table), resolvable hostnames, or IP Addresses. Each name in the list should be separated by a comma or white space. Each host listed can specify a destination port number and protocol (tcp or udp ) or service name using the format: x+y/z where x can be ip address or hostname or alias name y can be port number or protocol or service name z can be port number or protocol. example: testhost+162/tcp or 9.67.162.81+udp/162 If the port or protocol is not specified then default value is used. The default port number is '162' and default protocol is 'udp'.

This mask is used as a global filtering mechanism. The mask is used to indicate which traps are to be sent to the Destination Host. Bits 0 through 6, when read from LEFT to RIGHT, correspond to generic trap numbers 0 through 6. The generic traps are as follows: 0 - Cold Start 1 - Warm Start 2 - Link Down 3 - Link Up 4 - Authentication Failure 5 - EGP Neighbor Loss 6 - Enterprise Specific This field should be set to 254 to send all traps that the filter passes to the trap destination table. To send only linkDown (2) and linkUp (3) traps, the mask could be set to 48 (ie. 0011 0000).

This field indicates whether or not the destination is participating in the trap forwarding. When the destination is active, it is participating. When the destination is inactive, it is not participating, but will be participating when the activation time arrives. The participation state can be inactive only if activation/deactivation days are specified. Otherwise, the participation state is activated when the smMlmTrapDestinationState field is set to enabled. If this field is set to notEnabled, the smMlmTrapDestinationState field is not set to enabled. Enumeration: 'active': 2, 'inactive': 3, 'notEnabled': 1.

This field specifies the time to activate the trap destination. (i.e. changes the participation state from inactive to active). The format should be HH:MM where HH represents the hour (integer between 0 and 23) and MM represents the minute (integer between 0 and 59) to activate the destination. A value of all blanks will be interpreted as 00:00.

This field specifies the days of the week to activate the trap destination at the time specified in the ActivationTime field (ie. change the participation state from inactive to active). The day of the week may be one of three literals: none - Doesn't activate weekdays - Activates destination entry on MTWThF all - Activates destination entry every day SuMTWThFS Alternatively, the days of the week may be specified as a list of numbers between 0 and 6 (Sunday = 0, Monday = 1, ..., Saturday = 6). The expression '1,3,5' would activate the destination entry at the specified time on MWF.

This field specifies the time to deactivate the destination. (ie. change the participation state from active to inactive). The format should be HH:MM where HH represents the hour (integer between 0 and 23) and MM represents the minute (integer between 0 and 59) to deactivate the destination. A value all blanks will be interpreted as 00:00.

This field specifies the days of the week to deactivate the trap destination at the time specified in the DeactivationTime field (ie. change the participation state from active to inactive). The day of the week may be one of three literals: none - Doesn't deactivate weekdays - Dectivates destination on MTWThF all - Deactivates destination every day SuMTWThFS Alternatively, the days of the week may be specified as a list of numbers between 0 and 6 (Sunday = 0, Monday = 1, ..., Saturday = 6). The expression '1,3,5' would deactivate the destination entry at the specified time on MWF.

Contains informational and error messages for this trap destination entry.

Table of user information.

Each entry contains objects for a particular administrative community.

Indication that administrative information is either valid (1), invalid (2), or outdated (3). Note: Setting state to invalid will delete the row. Enumeration: 'valid': 1, 'outDated': 3, 'invalid': 2.

Name of administrative information. There should be a corporate-wide policy on naming information in order to avoid possible naming conflicts.

Owner of this piece of administrative information.

Description of the administrative information.

The actual administrative information.

Status monitor table. This table is used to define the status checking policies for interfaces.

Each entry contains objects for a status checking policy. The configuration specified is applied to all nodes and interfaces in the specified host.

State for the status monitor entry. Enabling this status monitor entry causes the interfaces contained in the host (or group) specified to be checked using the specified parameters (eg. interval, timeout, retries, ...). Enumeration: 'disabled': 1, 'enabled': 3, 'invalid': 2.

This field is simply used as the name of this entry.

This field is used to describe the entry. Used for annotative purposes only.

This indicates the address family of the address specified. Currently, only inet(2) is supported. Any other address family will be treated as an invalid value. Enumeration: 'hylink': 15, 'osi': 7, 'unix': 1, 'intf': 20, 'rif': 21, 'implink': 3, 'reserved31': 31, 'netware': 22, 'unknown': 65535, 'dli': 13, 'sna': 11, 'chaos': 5, 'datakit': 9, 'ns': 6, 'reserved32': 32, 'inet': 2, 'reserved30': 30, 'ccitt': 10, 'xtpPseudo': 19, 'link': 18, 'decnet': 12, 'lat': 14, 'pup': 4, 'route': 17, 'reserved28': 28, 'reserved29': 29, 'appletalk': 16, 'reserved26': 26, 'reserved23': 23, 'reserved24': 24, 'reserved25': 25, 'ecma': 8, 'reserved27': 27.

This field specifies the group of interfaces to which the status monitor entry is applied. It may be an alias name (contained in the smMlmAlias table), resolvable hostname, or network address.

This field shows the resolved group of interfaces to which the status monitor entry is applied. If the entry is disabled, this field is blank.

This field shows the group of interfaces that the status monitor entry was not able to resolve. This field contains any string entered that either did not match an alias name, was not a host name or an IP address. It is possible that a name shown in this field is the result of resolving an alias name and the resulting names were not hostnames or IP addresses.

This indicates how often to status check the interfaces that this policy governs. Frequency units are decimal values appended by the unit: d - day, h - hour, m - minute, s - second, u - millisecond. If no unit is appended, the value is minutes. Multiple values/units are allowed (i.e. 1m30s = 1 minute, 30 seconds). The default frequency is 5 minutes.

This indicates the number of seconds wait for a response to the status request before retrying the request. The default timeout is 1 second.

This indicates the total number of times to try the status request if no response is received. The default is 3 attempts.

This field contains informational and error messages for this status monitor entry.

This variable is used to indicate whether the Mid-Level Manager should engage in discovery activity. Once enabled(2), the MLM will discover any nodes with which it communicates. However, additional discovery capabilities may be configured using the Sensor and BroadcastSearch fields. Enumeration: 'disabled': 1, 'enabled': 2.

This field indicates whether or not the Mid-Level Manager should watch network packets in order to ascertain which nodes are currently on the network. This field is only used if the DiscoverySwitch field is enabled. If this field is set to passiveSensing(2), then only packets received will be examined for new nodes. If this field is set to activeSensing(3), then not only will received packets be examined, but any hints contained in those received packets will be investigated by querying those hint addresses. It is recommended that activeSensing(3) be used to more rapidly discover your network. Enumeration: 'disabled': 1, 'passiveSensing': 2, 'activeSensing': 3.

Maximum number of packets which discovery reads at one time. The higher this number is, the faster nodes will be discovered, but the more processing time will be required. The default for this field is 128.

Discovery uses an adaptive algorithm in deciding how often to search for new nodes; as more nodes are discovered, the frequency at which the discovery process listens decreases. This variable sets the maximum time between listening intervals. The maximum read interval is specified using decimal values appended by the unit: d - day, h - hour, m - minute, s - second, u - millisecond. If no unit is appended, the value is minutes. Multiple values/units are allowed (i.e. 1m30s = 1 minute, 30 seconds). The default for this field is 5m (5 minutes).

Indicator of whether or not the AIX Mid-Level Manager should perform a broadcast query to determine which machines are on the network at the configured BroadcastSearchTime, on the configured BroadcastSearchDays. It is a good idea to perform a broadcast search to discover nodes that are not initiating communication (e.g. file servers, bridges, hubs, etc.). In addition, this should be done at least as often as the NodeExpirationPeriod to avoid deleting them from the DiscoveryTable. If enabledOnce(2), then the broadcast search is only done once - at the next configured time and day. This field is then automatically set back to disabled(1) after the broadcast search is initiated. If enabledRepeated, then the broadcast search is done periodically at each configured time and day. The time and day to perform the broadcast search are configured using the ActiveSearchTime and ActiveSearchDay fields. It is a good idea to configure a broadcast search to be done at least as often as the configured NodeExpirationPeriod. Enumeration: 'disabled': 1, 'enabledRepeated': 3, 'enabledOnce': 2.

This field specifies the time to perform a broadcast request to determine who is on the network. This will cause a traffic burst to occur, so ideally it should be done at a time when low traffic levels are expected on the local network. The format should be HH:MM where HH represents the hour (integer between 0 and 23) and MM represents the minute (integer between 0 and 59) to perform the active search. If this field is set to all blanks, it will be interpreted as 00:00 (midnight).

This field specifies the days of the week to perform the broadcast search at the time specified in the BroadcastSearchTime field (ie. send out an active request). The day of the week may be one of three literals: none - Broadcast search will never be done weekdays - Broadcast search on MTWThF all - Broadcast search every day SuMTWThFS Alternatively, the days of the week may be specified as a list of numbers between 0 and 6 (Sunday = 0, Monday = 1, ..., Saturday = 6). The expression '1,3,5' would cause a broadcast search to be done at the specified time on Monday, Wednesday, and Friday.

When set to true(2), a broadcast search for which machines are on the network is initiated immediately. It may take up to 15 seconds to realize results from this operation if the Sensor is not enabled. Setting this field when the DiscoverySwitch is set to disabled causes the broadcast query to be done, but no responses are recorded. Enumeration: 'true': 2, 'false': 1.

This field specifies the amount of time a node remains in the table of discovered nodes. Setting this field allows nodes that have not been heard from to be removed from the discovered nodes table. If this field is blank, nodes are NEVER removed from the discovered nodes table. However, if the same Network Address is used with a new MAC Address, the MAC address of the existing entry is changed and a trap is sent. The node expiration period is specified using decimal values appended by the unit: d - day, h - hour, m - minute, s - second, u - millisecond. If no unit is appended, the value is minutes. Multiple values/units are allowed (i.e. 1h45m = 1 hour, 45 minutes). The default for this field is 7d (7 days). It is a good idea to perform an active search at least as often as this node expiration time period to avoid losing nodes that are not initiating communication (e.g. file servers, bridges, hubs, etc.). However, nodes of this type that are being status checked by the status checker table will continue to exist.

This field specifies the amount of time before a new/old node trap is sent. This allows many new nodes to be sent in the same trap, thus reducing notification traffic. The default is 1m (1 minute).

This field contains the number of addresses that have been discovered (i.e. the number of entries in the DiscoveryTable).

This field contains the maximum number of rings away from the current ring that a node can be on and still be discovered. For example, if this number is 0, only nodes on the local ring will be discovered. Note that this is only effective for token rings; Ethernet frames do not contain routing information in the MAC frame header.

This field contains messages concerning the discovery component of Mid-Level Manager.

Entries define a node that was detected to occur on the local network. The table is indexed by the smMlmDiscoveryAddressFamily, smMlmDiscoveryNetAddress fields.

Each entry contains the nodes detected on the local network.

This indicates the transport protocol used and determines the output format of the network address. Enumeration: 'hylink': 15, 'osi': 7, 'unix': 1, 'intf': 20, 'rif': 21, 'implink': 3, 'reserved31': 31, 'netware': 22, 'unknown': 65535, 'dli': 13, 'sna': 11, 'chaos': 5, 'datakit': 9, 'ns': 6, 'reserved32': 32, 'inet': 2, 'reserved30': 30, 'ccitt': 10, 'xtpPseudo': 19, 'link': 18, 'decnet': 12, 'lat': 14, 'pup': 4, 'route': 17, 'reserved28': 28, 'reserved29': 29, 'appletalk': 16, 'reserved26': 26, 'reserved23': 23, 'reserved24': 24, 'reserved25': 25, 'ecma': 8, 'reserved27': 27.

This field specifies the address of the discovered node as octets.

This field specifies the printable address of the discovered node.

This field specifies the MAC Address of the discovered node as octets.

This field specifies the printable MAC Address of the node.

The transposed MAC address is the MAC address with the bits in each byte of the address reversed, so that the least significant bit is now the most significant bit and vice versa. This is useful for token ring addresses since these addresses are usually represented in non-canonical form rather than the canonical form specified in the IEEE 802 specification and used by Ethernet, where the bit that travels first on the LAN is placed in the least significant bit as it appears in memory.

This field is the printable form of the transposed MAC address.

This field specifies the last time that the discovery process encountered this address. Addresses that are are not seen for the period of time defined in the smMlmDiscoveryExpirationTime parameter are removed from this table.

This field specifies the routing information to a node; it is valid only for token ring interfaces. It contains multiple routing information segments separated with two zero bytes. The length of each segment is present in the routing control field (the first byte of each segment).

This field displays the known routes to a node, in the form: [Route 1] [Route 2] ... [Route n]. Each route entry has the form: [RCF: (Ring)/Bridge->(Ring)/Bridge->...(Ring)] where RCF is the hexadecimal representation of the route control field in the packet from which this route was discovered (in hexadecimal), Ring is the bridge number, and Bridge is the bridge number. Note that this information is only displayed for token rings.