INXNTS-MIB: View SNMP OID List / Download MIB

A list of the INX-NTS Ethernet interface`s operational attributes, such as whether it is configured for multicast receive and the status of the MAC sublayer. You cannot access this variable; it is only a table marker in the MIB.

An entry in the INX-NTS Interface table. (See the previous variable, INX-NTS Interface Table, for an explanation of this table.) You cannot access this variable; it is only a table marker in the MIB. The following variables are entries in the table: Interface Table Index MAC Initialization Status MAC Operational Status Multicast Receive Status Nonaligned Frames Recd FCS Errored Frames Received

The value assigned to the INX-NTS Ethernet interface. Because the INX-NTS has only one interface, this variable always returns 1.

The initialization status of the MAC and PLS subsystems of the interface. Because the MAC and PLS subsystems on the INX-NTS are initialized at power-up and remain so, this variable always returns initialized(1), and may only be set to initialized(1). Enumeration: 'initialize': 1.

The operational status of the MAC sublayer, i.e., whether it is ready to transmit and receive frames. Because this sublayer is always active in the INX-NTS, this variable always returns enabled(1), and can only be set to enabled(1). Enumeration: 'enabled': 1.

The Multicast Receive status, i.e., whether the INX-NTS is configured to receive frames with a multicast address. Because Multicast Receive is always enabled on the INX-NTS, this variable always returns true(1), and can only be set to true(1). Enumeration: 'true': 1.

The number of frames received on the interface that are not an integral number of octets in length (i.e., the number of bits they contain is not a multiple of eight) and do not pass the FCS check. This condition indicates that the frames were corrupted during transmission.

The number of frames received on the interface that are an integral number of octets in length (i.e., the number of bits they contain is a multiple of eight) that do not pass the FCS check, indicating that the frames were corrupted during transmission.

A list of transmit errors and statistics for the INX-NTS Ethernet interface. You cannot access this variable; it is only a table marker in the MIB.

An entry in the Interface Transmit table. (See the previous variable, Interface Transmit Table, for an explanation of this table.) You cannot access this variable; it is only a table marker in the MIB. The following variables are entries in the table: Interface Transmit Index Single Collisions Transmitted Multiple Collisions Xmitted Total SQE Test Errors

The value assigned to the INX-NTS Ethernet interface. Because the INX-NTS has only one interface, this variable always returns 1.

The number of frames that were successfully transmitted after experiencing one and only one collision.

The number of frames that were successfully transmitted after experiencing more than one collision.

The number of frames for which the INX-NTS's collision detect logic did not detect a Signal-Quality-Error-Test (SQE-Test) signal immediately after a packet transmission. The INX-NTS does not generate SQE-Test error messages, so this variable always returns 0.

A list of receive errors and statistics for the INX-NTS Ethernet interface. You cannot access this variable; it is only a table marker in the MIB.

An entry in the Interface Receive table. (See the previous variable, Interface Receive Table, for an explanation of this table.) You cannot access this variable; it is only a table marker in the MIB. The following variables are entries in the table: Interface Receive Index Too Long Frames Recd In-Range Length Errors Recd Out-Range Length Errors Recd MAC Errors Received Autopartition Status Autopartition Disconnects Last Good Source Address Recd Source Address Changes Count

The value assigned to the INX-NTS Ethernet interface. Because the INX-NTS has only one interface, this variable always returns 1.

The number of frames received on the interface that exceed the maximum permitted frame size, i.e., 1180 octets.

The number of in-range length errors received. IEEE 802.3 frames contain a length field, indicating the length of the frame. If the value in the length field and the actual length of the frame do not match, even if the length of the frame is within 802.3 parameters, the receiving device returns an in-range error. The INX-NTS receives Ethernet frames that do not have a length in the length field. It therefore cannot detect this error, and this variable always returns 0.

The number of out-of-range length errors received. IEEE 802.3 frames contain a length field, indicating the length of the frame. If the length of the frame is outside 802.3 parameters, the receiving device returns an out-of-range error. The INX-NTS receives Ethernet frames that do not have a length in the length field. It therefore cannot detect this error, and this variable always returns 0.

The number of frames the interface could not receive because of an internal MAC sublayer receive error. This variable returns frames not counted by the Too Long Frames Received, Nonaligned Frames Received, FCS Errored Frames Received, In-Range Length Errors Recd, and Out-Range Length Errors Recd variables.

The autopartition status of the INX-NTS. Devices that support autopartitioning have the ability to autonomously disconnect from the network when they sense trouble, e.g., a device with a jabber condition. Because the INX-NTS interface does not support autopartitioning, this variable always returns notpartitioned(2). This object may be written to with the value notpartitioned(2). Enumeration: 'notpartitioned': 2.

The number of autopartitions the INX-NTS has performed. Devices that support autopartitioning maintain a log of the number of times they disconnected from the network. Because the INX-NTS interface does not support auto-partitioning, this variable always returns 0.

The source address of the last frame successfully received. Because this value changes too often to be useful, the INX-NTS interface does not record the last source address of received frames; therefore, this variable always returns a null value.

The number of times that the value of Last Good Source Address Recd has changed. The INX-NTS interface does not log source address changes; therefore, this variable always returns 0.

A list of transmit errors and statistics for the INX-NTS Ethernet interface. You cannot access this variable; it is only a table marker in the MIB.

An entry in the Interface Xmit Error/Stat table. (See the previous variable, Interface Xmit Error/Stat Table, for an explanation of this table.) You cannot access this variable; it is only a table marker in the MIB. The following variables are entries in the table: Interface Xmit Error/Stat Index Interface Transmit Status Transmissions Deferred Late Collisions Detected Excessive Collisions Detected MAC Transmit Errors Carrier Sense Errors Deferred Frames TDR Status

The value assigned to the INX-NTS Ethernet interface. Because the INX-NTS has only one interface, this variable always returns 1.

The transmit status of the interface, i.e., whether it is able to transmit frames. Because transmit is always enabled on the INX-NTS, this variable always returns true(1), and can only be set to true(1). Enumeration: 'true': 1.

The number of times the INX-NTS deferred transmission of data because it sensed traffic on the network. Because the INX-NTS does not record deferrals, this variable always returns 0.

The number of times that a collision has been detected on this bus later than 512 bit times from frame start.

The number of frames the interface could not transmit because of excessive collisions.

The number of frames the interface could not transmit because of an internal MAC sublayer transmit error. This variable counts frames not counted by the Late Collisions Detected, Excessive Collisions Detected, Carrier Sense Errors, and Deferred Frames variables.

The number of times that the carrier-sense condition was lost or never asserted when the INX-NTS attempted to transmit a frame on the interface. This count is incremented at most once per transmission attempt, even if the carrier-sense condition fluctuates during the transmit attempt.

The number of frames the INX-NTS deferred transmitting for an excessive period of time. Because the INX-NTS interface does not record deferrals, this variable always returns 0.

The status of Time Domain Reflectometry (TDR) on the INX-NTS. TDR is the ability of a device to check the viability of a cable by sending a signal to the end of the cable. The INX-NTS interface does not support Time Domain Reflectometry,so this variable always returns 0.

A histogram representing the frequency of collisions on the interface. In the Collision Frequency histogram, one dimension of each cell represents Collisions per Frame, and the other dimension represents Collision Frequency. You cannot access this variable; it is only a table marker in the MIB.

An entry in the Collision Frequency table. (See the previous variable, Collision Frequency Table, for an explanation of this table.) You cannot access this variable; it is only a table marker in the MIB. The following variables are entries in the table: Collision Frequency Index Collisions per Frame Collision Frequency

The value assigned to the INX-NTS Ethernet interface. Because the INX-NTS has only one interface, this variable always returns 1.

The number of media collisions per frame indicated by one cell in the collision histogram. The INX-NTS tracks the number of collisions up to 15.

The number of frames that were transmitted after experiencing exactly Collisions per Frame collisions on the INX-NTS Ethernet interface (see the previous variable, Collisions per Frame).

The number of Telnet sessions that have been initiated from the INX-NTS.

A table containing Telnet session-specific information that is appropriate to whatever side of a session the INX-NTS happens to be. There is one entry in the table for each telnet session that is active. You cannot access this variable; it is only a table marker in the MIB.

Information about a particular Telnet session. This variable is an entry in the Telnet Session table. (See the previous variable, Telnet Session Table, for an explanation of this table.) You cannot access this variable; it is only a table marker in the MIB. The following variables are entries in the table: Telnet Port Identifier Local IP Addr of TCP Cxn Remote IP Addr of TCP Cxn Local Port of TCP Connection Remote Port of TCP Connection UpTime at Session Start Session Options Telnet Session State Telnet User ID Octets Recd Octets Sent Protocol Type of Next Session Name of Next Session

The index value that uniquely identifies the terminal port table entry to which this entry is applicable.

The local IP address of the TCP connection that this Telnet session is using.

The remote IP address of the TCP connection that this Telnet session is using.

The local port number of the TCP connection that this Telnet session is using.

The remote port number of the TCP connection that this Telnet session is using.

The amount of time that has elapsed since the Telnet session was established.

Indicates which options are on/enabled/in the will/do state. Each octet in the string contains the numerical value of an option that is on. For example, if a session had options 1, 4, 10, 15, and 20 on, then Session Options On would return 5 octets, and the octets would contain the values 1, 4, 10, 15, and 20. The option values in the octet would contain the values 1, 4, 10, 15, and 20. The option values in the octet string can be in any order.

The state of the session. o serverActive(1) indicates that the INX-NTS is the Telnet server, and that a session is active-i.e., a user has logged in to this end of the connection. o client(3) indicates that the INX-NTS is the client end of the connection. In a typical Telnet session, this is the user's terminal. Enumeration: 'serverActive': 1, 'client': 3.

The identification of the user at the INX-NTS end of the Telnet session. Because user IDs are not implemented in the INX-NTS, this variable always returns a null string.

The number of octets of data received from the other end of the session. Because the INX-NTS does not keep octet counts for Telnet connections, this variable always returns 0.

The number of octets of data sent to the other end of the session. Because the INX-NTS does not keep octet counts for Telnet connections, this variable always returns 0.

The protocol used by the next session in the set of sessions currently established on this port. Because the INX-NTS does not keep this information for Telnet connections, this variable always returns 0.

The entry in the application protocol table identified by Protocol Type of Next Session. Because the INX-NTS does not keep this information, this variable always returns a null value (0.0).

The number of terminal ports on the INX-NTS. Because there are 16 ports on the INX-NTS, this variable always returns 16.

Allows you to view or change the INX-NTS sign-on message. This message is displayed when you enter command mode from idle mode, and when you connect to a slave port. The message can be up to 120 characters long.

Allows you to view or change the INX-NTS command-mode prompt. The default is inx-nts>. The prompt can contain up to 80 characters.

The password to use when entering administrative mode in the INX-NTS. For security reasons, this variable always returns the string PASSWORD-RESTRICTED. If you are using the INX-LCD, the default password is 123456. (Press each of the function keys located to the left of the Unit key in order from left to right.) If you are accessing the INX-NTS by another means, the default password is hello. To change this password, use the administrative command PASSWORD. Your new password can be up to 20 characters long.

The name that is appended to the host name when the INX-NTS requests a name server and the string entered by the user contains no period. (If the string does contain a period, the INX-NTS assumes it is a fully qualified domain name.)

The node name to be contained in future RWHO (UPTIME) broadcasts. The name can contain up to seven characters.

The number of buffers that a Telnet, RLOGIN, or LAT process can use for receiving inbound traffic.

The TCP read buffer size, in octets.

The TCP write buffer size, in octets.

The TCP default window size, in octets.

The TCP maximum segment size, in octets.

Allows you to view or change the INX-NTS break-in character, which permits you to escape from a connection and return to command mode. This variable returns the value of the ASCII character to use as the break-in character. The default value is 256, which sets the Break key as the break-in character.

The number of available octets in the far memory pool.

The lowest number of octets available in the far memory pool since the INX-NTS was reset.

The number of milliseconds that the INX-NTS TCP implementation waits between TCP protocol ACK packets. This variable must be set to a multiple of 50. If it is set to some value that is not a multiple of 50, then the value will be rounded down to a multiple of 50. For example, if you specify this variable as 199, it will actually be set to 150.

A table containing management information for a specific port on the INX-NTS. There are 16 entries in this table, one for each port. You cannot access this variable; it is only a table marker in the MIB.

An entry in the Port table (see the previous variable, Port Table, for an explanation of this table). You cannot access this variable; it is only a table marker in the MIB. The following variables are entries in the Port Table: Port Index First Session Type Current Session Type Current Number of Sessions Baud Rate for Received Data Baud Rate for Transmitted Data Port Parity Data Bits Sent Modem Control Type Flow Control for Data Received Flow Control for Data Sent RS-232 Ring Indicator Connection Password Telnet Abort Out Character Telnet Interrupt Character Inactivity Timeout Value Time Until Timer Expires Suppress Software Messages Port Function Port State Octets Rec'd Octets Trans XON Character XOFF Character Maximum Allowed Sessions TCP Port Number TCP Port Mode Transparent Mode for the Port Port Echo Setting Domain Name Server IP Addr

A unique value for each port. Because there are 16 ports on the INX-NTS, this variable always returns a value from 1 through 16.

The protocol used by the first session in the set of sessions for this port. For the INX-NTS, this variable returns telnet(4) for Telnet connections and dummy(5) for all other connections. If there are no sessions for this port, the variable returns none(1). Enumeration: 'dummy': 5, 'none': 1, 'telnet': 4.

The protocol that the currently active session is using to communicate with the other end of the connection. For the INX-NTS, this variable returns telnet(4) for Telnet connections and dummy(5) for all other connections. If there are no sessions for this port, the variable returns none(1). Enumeration: 'dummy': 5, 'none': 1, 'telnet': 4.

The current number of sessions that are associated with this port. This number includes sessions for which there is no MIB entry (i.e., any session other than a Telnet session).

The baud rate for data received by the port, in bits per second (bps). If you want the INX-NTS to automatically determine baud rates, you can configure it to do so by setting this variable to 0. If this variable returns 0, automatic baud rate determination is already in effect. If this variable returns a value other than 0, that value is the current baud rate. The default baud rate is 9600. Note: The INX-NTS uses only a single baud rate parameter, which is used in both directions. Therefore, you cannot set this variable and the following one, Baud Rate for Transmitted Data, to different values; the INX-NTS will use whichever value was last received by the management agent as the baud rate. Enumeration: 'br-300': 300, 'br-2400': 2400, 'br-600': 600, 'br-9600': 9600, 'br-4800': 4800, 'br-110': 110, 'br-38400': 38400, 'br-1200': 1200, 'br-19200': 19200.

The baud rate for data transmitted by the port, in bits per second (bps). If you want the INX-NTS to automatically determine baud rates, you can configure it to do so by setting this variable to 0. If this variable returns 0, automatic baud rate determination is already in effect. If this variable returns a value other than 0, that value is the current baud rate. The default baud rate is 9600. Note: The INX-NTS uses only a single baud rate parameter, which is used in both directions. Therefore, you cannot set this variable and the previous one, Baud Rate for Received Data, to different values; the INX-NTS will use whichever value was last received by the management agent as the baud rate. Enumeration: 'br-300': 300, 'br-2400': 2400, 'br-600': 600, 'br-9600': 9600, 'br-4800': 4800, 'br-110': 110, 'br-38400': 38400, 'br-1200': 1200, 'br-19200': 19200.

The parity of the port. Enter a value for parity that matches the parity setting of the device attached to the INX-NTS port. The default is none(1). The parity bit is stripped before the data is sent across the network. Enumeration: 'even': 3, 'none': 1, 'odd': 2.

The number of data bits in each character transmitted between the INX-NTS port and an attached device. Enter a value that matches the setting of the device attached to the port. The default is 8.

The type of modem control, if any, on this port. This setting determines the use of the modem control RS-232 signals. Enter a value that matches the setting of the attached device. o none(1) means that no modem control signals are in use. This is the default. o dce(2) means that the INX-NTS port will act as a DCE device in monitoring the modem control signals. This is the appropriate setting if you are attaching a DTE device (for example, a terminal) that uses these signals to the INX-NTS port. (Ports are always wired as DCE, regardless of modem settings.) o dte(3) means that the INX-NTS port will act as a DTE (Data Terminal Equipment) device in monitoring the modem control signals. Use this setting when attaching a DCE (Data Communication Equipment) device (such as a modem) to the INX-NTS port. Note: Setting Modem Control to DTE can require the use of a cabling adapter at the device. Enumeration: 'none': 1, 'dce': 2, 'dte': 3.

The type of flow control used on the port for received data. o None(1) indicates that no flow control is in use o Xonxoff(2) indicates that software flow control is in use. o Hardware(3) indicates that hardware flow control is in use. (This setting is not valid for use with an NTS-TELCO.) 0 Handx(4) indicates that both hardware and software flow control are in use. (This setting is not valid for use with an NTS-TELCO.) Enumeration: 'hardware': 3, 'none': 1, 'handx': 4, 'xonxoff': 2.

The type of flow control used on the port for data being sent. o None(1) indicates that no flow control is in use. o Xonxoff(2) indicates that software flow control is in use. For a terminal attached to an INX-NTS port, this setting allows you to press the XOFF control character (Ctrl-S by default) in order to halt output from the INX-NTS port to the screen, and the XON control character (Ctrl-Q by default) to resume output to the screen. o Hardware(3) indicates that hardware flow control is in use. (This setting not valid for use with an NTS-TELCO.) o Handx(4) indicates that both hardware and software flow control are in use. (This setting not valid for use with an NTS-TELCO.) Enumeration: 'hardware': 3, 'none': 1, 'handx': 4, 'xonxoff': 2.

The status of the Ring Indicator (RI) RS-232 signal. If you have set modem control (see the Modem Control Type variable) to DCE, you must set Ring to no(1). If you have set modem control to DTE, yes(2) means that the INX-NTS port will use the RI signal; no(1) means the signal will not be used. Enumeration: 'yes': 2, 'no': 1.

The password needed to connect to the port. The port password can be up to seven characters long.

The ASCII value of the character that invokes a Telnet Abort Output for this port. You use this character to suspend output to the screen for a current process.

The ASCII value of the character that invokes a Telnet Interrupt Process for this port. You use this character to kill a current process on a UNIX machine.

The number of minutes a port can be inactive before the INX-NTS closes all existing virtual circuits on that port. The timeout range can be from 1 to 255 minutes. This feature works on all ports except permanent. It is disabled for slave ports configured with network port numbers 7 (echo); 9 (sink); or 19 (source). To disable the inactivity timeout function, set this variable to 0.

Number of minutes left before the inactivity timer (see the previous variable, Inactivity Timeout Value) expires, and all virtual circuits for this port are closed. Setting this variable to 0 temporarily disables the inactivity timer, so virtual circuits are maintained as long as the port remains inactive. When port activity resumes, however, the inactivity timer is reactivated, and this variable is set to the value of Inactivity Timeout Value.

Whether software-generated messages are passed through the port. To suppress the sending of all messages generated by the LAT/TCP software, set this variable to yes(2). To enable the sending of such messages, set it to no(1). Traffic from network connections continues to pass through the port regardless of the setting of this variable. Enumeration: 'yes': 2, 'no': 1.

The ability of the port to initiate and accept connections. o slave(1) indicates that the port can only accept connections. If it is busy, it will reject a connection request. o terminal(2) indicates that this port can only initiate connections. o permckt(3) indicates that this port initiates and automatically maintains connections. o both(4) means this port can both accept and initiate connections. o demandckt(5) indicates the same status as permckt except that you must first press a key on the keyboard to activate the port. o queue(6) means this port accepts and holds connections. It will act like a slave port, except that instead of rejecting a request when it is busy, it stores the request until a resource becomes available. Enumeration: 'both': 4, 'slave': 1, 'permckt': 3, 'demandckt': 5, 'queue': 6, 'terminal': 2.

The state of the port. o disabled(1) indicates that the port cannot be used o active(3) means the port is enabled, and a device is connected. Setting an active(3) port to the disabled(1) state resets the port. All error conditions are cleared, and connections and sessions are terminated. Enumeration: 'disabled': 1, 'active': 3.

Total number of octets received on the port from the network connection(s).

Total number of octets sent onto the network connection(s) by the port.

The ASCII value of the XON character. This setting is meaningful only if XON/XOFF flow control is in use. (See the Flow Control for Data Received and Flow Control for Data Sent variables for more information.)

The ASCII value of the XOFF character. This setting is meaningful only if XON/XOFF flow control is in use. (See the Flow Control for Data Received and Flow Control for Data Sent variables for more information.)

Maximum number of sessions allowed on this port.

The TCP port number that this serial port uses when listening for Telnet connections. If this port is not configured to listen for inbound connection requests, this variable returns 65535. The default TCP port number is 23.

The TCP operating mode for the port. o rawsocket(1) means there is no application protocol; data is transferred to and from a TCP socket without interpretation. o nvt7bit(2) is for standard seven-bit NVT mode, in which the Telnet utility transfers 7-bit data. o nvt8bit(3) is for a modified Telnet NVT mode (data is transferred using eight bits per character). Enumeration: 'rawsocket': 1, 'nvt8bit': 3, 'nvt7bit': 2.

The default mode of the port. When this variable is set to on(1), you make it possible to enable full eight-bit transparency so that you can send binary or image files across the network. To set the port to non-transparent mode, set this variable to off(2). Enumeration: 'on': 1, 'off': 2.

The echo setting for the port. This echo setting determines whether echoing and such functions as line editing are done by the remote host or the local host. Remote echoing is the default and the recommended setting for your terminal. Local echoing allows you to connect to hosts that do not support remote echoing. Enumeration: 'remote': 2, 'local': 1.

The Internet address of the host you want to have act as the domain name server.

The number of entries in the boot table. Because there are two files that can be booted (chassis management protocol and high-level protocol), there will always be two entries in the INX-NTS boot table. Therefore, this variable will always return a 2, and can only be set to 2.

The setting of this variable determines whether this INX-NTS can provide boot images to other systems, returning true(2) if it can and false(1) if it cannot. Enumeration: 'true': 2, 'false': 1.

This table contains boot information for the INX-NTS. You cannot access this variable; it is only a table marker in the MIB.

An entry in the Boot table. (See the previous variable, Boot Table, for an explanation of this table.) You cannot access this variable; it is only a table marker in the MIB. The following variables are entries in the table: Boot Table Index Boot File Name IP Address for TFTP Boot Boot File Version Gateway Address for Booting

A unique value for each entry in the boot table. This variable returns 1 for the Chassis Management Protocol file and 2 for the operating software image file.

The name of the boot file that the INX-NTS will attempt to load.

The IP address of the node from which the INX-NTS will attempt a TFTP boot.

The revision level of the boot file.

The IP address of the gateway through which the INX-NTS can access the boot server.

the number of active entries in the threshold table.

The maximum number of active thresholds allowed.

Setting this variable creates a new entry in the Threshold table. You must type a number for the entry when you set this variable, but the INX-NTS assigns the actual entry number; that number is the one returned in the response to the set command. If you read this variable, it returns the number of the most recently generated threshold entry. Each threshold entry must have a unique index number, but the number assigned to an entry can be reused after you have deleted it.

How often, in seconds, thresholds exceeded are checked. To disable threshold checking, set this variable to 0.

A table containing information about the thresholds that have been set. You cannot access this variable; it is only a table marker in the MIB.

An entry in the Threshold table. (See the previous variable, Threshold Table, for an explanation of this table). You cannot access this variable; it is only a table marker in the MIB. The following variables are entries in the table: Threshold Table Index Threshold Status Threshold Object ID Threshold Value Threshold Hysteresis Direction of Approach to Thresh Threshold Trigger Count Threshold Community Name Threshold Eth Addr Destination Threshold IP Addr Destination

A unique value for each threshold.

The current status of the threshold. o delete(1) deletes the threshold entry specified. o unset(2) means that the threshold is newly created, currently being configured, or disabled. o armed(3) means that the threshold is active and generates a trap PDU when it is triggered. o safety(4) means that the threshold is active, but does not generate trap PDUs. Enumeration: 'safety': 4, 'armed': 3, 'unset': 2, 'delete': 1.

The complete object identifier of the variable on which this threshold is set. Threshold Object ID can be set only for Counter or Gauge variables. If you attempt to set a threshold for a variable of any other type, you receive a badValue error.

The threshold value for the variable identified by Threshold Object ID. If this particular variable is a gauge, then whenever its value rises above or drops below (depending on the setting of the Direction of Approach to Thresh variable) the value of Threshold Value, the threshold is considered to have been triggered. If this particular variable is a counter, then whenever its value increments by the value of Threshold Value, the threshold is considered to have been triggered.

The hysteresis value for the threshold. After a variable's threshold is triggered, the value of the variable must either drop below or rise above a certain value (depending on the setting of the Direction of Approach to Thresh variable), the hysteresis, before another trigger can be recognized. For example, if you set the threshold for module temperature to 80, the threshold is triggered the first time the temperature rises above 80. If you also set the hysteresis for this threshold to 60, the threshold will only be triggered again if the temperature drops below 60, and then rises past 80. If the temperature drops from 80 to 70, and then goes back to 80, the threshold is not triggered. If the hysteresis value is less than the threshold value, the variable's value must drop below the hysteresis before another trigger is recognized. If the hysteresis value is greater than the threshold value, the variable's value must rise above the hysteresis before another trigger is recognized. The value of the hysteresis depends on the value of the threshold and whether the value of the variable is rising or falling; therefore, set this variable in conjunction with both the Threshold Value and Direction of Approach to Thresh variables. This variable is relevant only to thresholds set on Gauge variables.

The direction in which a change in a Gauge variable's value causes a threshold to trigger. If its direction is up, a trigger occurs when the variable's value rises above the threshold value. In this case, the hysteresis must be less than or equal to the threshold value. If its direction is down, a trigger occurs when the variable's value falls below the threshold value. In this case, the hysteresis must be greater than or equal to the threshold value. This variable is relevant only to thresholds set on Gauge variables. Enumeration: 'down': 2, 'up': 1.

The number of times that this threshold has been triggered.

The community name to place in the authentication header of the trap PDU. This variable specifies the community to which the trap is to be sent when a threshold is triggered.

The Ethernet address of the node to which the trap is to be sent when the threshold is triggered.

The IP address of the node to which the trap is to be sent when the threshold is triggered.

The hardware revision level of the INX-NTS.

The firmware revision level of the INX-NTS.

The software revision level of the INX-NTS.

The serial number of the INX-NTS.

The reset state of the INX-NTS. o resetupdate(3) causes the INX-NTS to reset following the next NVRAM update. o notreset(1) has no effect. Enumeration: 'resetupdate': 3, 'notreset': 1.

The number of internal clock ticks that occur each second on the INX-NTS.

How often, in seconds, any rate statistic maintained by the INX-NTS is checked. The default is 20 seconds.

The number of times that the NVRAM has been changed.

The INTERNExT chassis slot in which the INX-NTS is located

The Ethernet bus connected to the INX-NTS in this slot. Enumeration: 'none': 4, 'bus-a': 2, 'bus-b': 3.

The type of connectivity module attached to the INX-NTS in this slot. If this variable returns the object identifier 1.3.6.1.4.1.28.1.3.4.1.1.1, the connectivity module is an NTS-RJ45. If this variable returns the object identifier 1.3.6.1.4.1.28.1.3.4.1.2.1, the connectivity module is an NTS-TELCO.

The hardware revision level of the connectivity module attached to the INX-NTS in this slot.

The serial number of the connectivity module attached to the INX-NTS in this slot.

The state of the connectivity module attached to the INX-NTS in this slot. For the INX-NTS, this variable always returns enabled(2). Enumeration: 'enabled': 2.

The bus connected to the connectivity module in this slot. Because the connectivity module is connected to the INX-NTS logic module, rather than to the internal chassis buses, this variable always returns other(3). Enumeration: 'other': 3.

The Ethernet media type setting for the connectivity module in this slot. This information is not relevant to the INX-NTS connectivity module, so this variable always returns other(3). Enumeration: 'other': 3.

The type of chassis (i.e., 3-slot or 12-slot) in which the INX-NTS is located.

The rate of frames that were successfully transmitted after experiencing one and only one collision. This variable corresponds to the Single Collisions Transmitted variable in the dot3 group.

The rate of frames that were successfully transmitted after experiencing more than one collision. This variable corresponds to the Multiple Collisions Xmitted variable in the dot3 group.

The rate of times the INX-NTS deferred transmission of data because it sensed traffic on the network. Because the INX-NTS does not record deferrals, this variable always returns 0. This variable corresponds to the Transmissions Deferred variable in the dot3 group.

The rate of times that a collision has been detected on this bus later than 512 bit times from frame start. This count is not maintained by the INX-NTS, so this variable always returns 0. This variable corresponds to the Late Collisions Detected variable in the dot3 group.

The rate of frames the interface could not transmit because of an internal MAC sublayer transmit error. This variable corresponds to the MAC Transmit Errors variable in the dot3 group.

The rate of times that the carrier-sense condition was lost or never asserted when the INX-NTS attempted to transmit a frame on the interface. This variable corresponds to the Carrier Sense Errors variable in the dot3 group.

The rate of frames the INX-NTS deferred transmitting for an excessive period of time. Because the INX-NTS interface does not record deferrals, this variable always returns 0. This variable corresponds to the Deferred Frames variable in the dot3 group.

The rate of frames the interface could not receive because of an internal MAC sublayer receive error. This variable corresponds to the MAC Errors Received variable in the dot3 group.

The rate of frames received on the interface that are an integral number of octets in length (i.e., the number of bits they contain is a multiple of eight) that do not pass the FCS check, indicating that the frames were corrupted during transmission. This variable corresponds to the FCS Errored Frames Received variable in the dot3 group.

The rate of frames received on the interface that are not an integral number of octets in length (i.e., the number of bits they contain is not a multiple of eight) and do not pass the FCS check. This indicates that the frames were corrupted during transmission. This variable corresponds to the Nonaligned Frames Recd variable in the dot3 group.

The rate of in-range length errors received. IEEE 802.3 frames contain a length field, indicating the length of the frame. If the value in the length field and the actual length of the frame do not match, even if the length of the frame is within 802.3 parameters, the receiving device returns an in-range error. The INX-NTS receives Ethernet frames that do not have a length field. It therefore cannot detect this error, and this variable always returns 0. This variable corresponds to the In-Range Length Errors Recd variable in the dot3 group.

The rate of out-of-range length errors received. IEEE 802.3 frames contain a length field, indicating the length of the frame. If the length of the frame is outside 802.3 parameters, the receiving device returns an out-of-range error. The INX-NTS receives Ethernet frames that do not have a length field. It therefore cannot detect this error, and this variable always returns 0. This variable corresponds to the Out-Range Length Errors Recd variable in the dot3 group.

The rate of frames received on the interface that exceed the maximum permitted frame size, i.e., 1012 octets. This variable corresponds to the Too Long Frames Recd variable in the dot3 group.