LANtern-MIB: View SNMP OID List / Download MIB

A cableFailure(1) trap is generated whenever the LANtern network monitor detects a fault with the network cable.

A pingNotification(2) trap is generated whenever the LANtern network monitor receives the echo response to a proxy ping.

A duplicateIPAddr(3) trap is generated whenever the LANtern network monitor first detects more than one host using the same IP address.

A utilizationAlarm(4) trap is generated whenever the percent utilization parameter enters or leaves an alarm condition as defined by the thresholds set in the eAlarmTable.

An errorsAlarm(5) trap is generated whenever the percent errors parameter enters or leaves an alarm condition as defined by the thresholds set in the eAlarmTable.

A broadcastsAlarm(6) trap is generated whenever the percent broadcasts parameter enters or leaves an alarm condition as defined by the thresholds set in the eAlarmTable.

A collisionsAlarm(7) trap is generated whenever the percent collisions parameter enters or leaves an alarm condition as defined by the thresholds set in the eAlarmTable.

A hostInactive(9) trap is generated whenever the LANtern network monitor first detects that a monitored host has not transmitted for the specified interval. The LANtern will attempt to verify that the host is actually dead by pinging it before generating the trap.

A hostActive(10) trap is generated whenever the LANtern network monitor first detects that a monitored host has begun transmitting again (after being inactive).

A newHost(11) trap is generated whenever the LANtern network monitor first detects a new host transmitting on its network segment.

A hostLimitExceeded(12) trap is generated the first time the LANtern exceeds its host limit. eHostAddress is the address of the host which caused the limit to be exceeded.

An identifying ASCII string may be attached to the LANtern network monitor by writing adminIdentification. Conversely, the LANtern network monitor may be identified by reading adminIdentification. adminIdentification is stored in nonvolatile RAM.

Reading adminDateAndTime returns the current date and time in use by the LANtern network monitor. The LANtern network monitor's date and time may be adjusted at any time by writing to adminDateAndTime. However, although the new value is updated correctly as time advances, it does not replace the previous value until the LANtern network monitor is restarted. adminDateAndTime is stored in the clock/calendar chip.

A DisplayString defining the time zone of the LANtern network monitor. adminTimeZone is neither parsed nor used by the LANtern network monitor, it is merely stored and divulged upon request. It is strongly recommended that adminTimeZone be used to store time zone information in a manner identical to the UNIX System V time zone environment variable (TZ). This standard approach would permit interoperability with network management consoles from multiple vendors. adminTimeZone is stored in nonvolatile RAM.

The date and time when the LANtern network monitor was last powered on or restarted.

The date and time when the LANtern network monitor was last powered off or restarted. The value is 0 (midnight, 1 January 1900) after a cold start.

The type of data link encapsulation to be used on the monitored network. adminNetworkDataLink may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When adminNetworkDataLink is read, it returns the value currently in use, regardless of any previous writes. adminNetworkDataLink is stored in nonvolatile RAM. Enumeration: 'ethernetDIX': 1.

The IP address to be used by the LANtern network monitor on the monitored network. adminNetworkIPAddr may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When adminNetworkIPAddr is read, it returns the IP address currently in use, regardless of any previous writes. adminNetworkIPAddr is stored in nonvolatile RAM. On start up, if the LANtern does not have an IP address, it will attempt to acquire one via BOOTP and/or RARP. If neither method is successful, the address 192.68.205.1 is used.

The subnet mask for the monitored network. adminNetworkSubnetMask may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When adminNetworkSubnetMask is read, it returns the subnet mask currently in use, regardless of any previous writes. adminNetworkSubnetMask is stored in nonvolatile RAM. When the value 0.0.0.0 is stored in this variable, the LANtern assumes no subnetting. This value is acquired via BOOTP if the value of adminNetworkIPAddr is acquired via BOOTP. If neither BOOTP nor RARP succeeds in acquiring adminNetworkIPAddr, the value 255.255.255.128 is used

The IP address of a gateway directly connected to the monitored network (the LANtern network monitor's default gateway). adminNetworkGateway may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When adminNetworkGateway is read it returns the gateway IP address currently in use, regardless of any previous writes. adminNetworkGateway is stored in nonvolatile RAM.

A table providing data on all authorized LANtern clients. The table is accessed by adminClientIPAddr. A new entry may be created by writing to a nonexistent instance. Note that adminClientIPAddr is set implicitly from this write; it cannot be written directly. An entry may subsequently be deleted by writing (any value) to adminClientDelete. adminClientTable is stored in nonvolatile RAM. Default: a single entry with: adminClientIPAddr.0.0.0.0=0.0.0.0, adminClientIPMask.0.0.0.0=0.0.0.0, adminClientCommunities.0.0.0.0=7

Data about each authorized client.

The IP address (or portion thereof) of a station authorized to access the LANtern network monitor.

A 32-bit mask that is bitwise anded with the candidate client's IP address before attempting to match against adminClientIPAddr.

A bit array where the presence of a particular bit indicates that use of that particular community name is permitted. Bit Community 2^0 administrator 2^1 logger 2^2 monitor.

A write (any value) causes the table entry to be deleted.

The IP address of the station that generated the authentication failure.

The community name string used in the PDU that generated the authentication failure.

A list of all stations wishing to receive traps from the LANtern network monitor; accessed by adminNotificationIPAddr. A new entry may be created by writing to a nonexistent instance. Note that adminNotificationIPAddr is set implicitly from this write; it cannot be written directly. An entry may subsequently be deleted by writing (any value) to adminNotificationDelete adminNotificationTable is stored in nonvolatile RAM.

Data for each station on the notification list.

The IP address of the station wishing to receive traps from the LANtern network monitor.

Traps are sent to all primaryContacts who have the corresponding bit set in adminNotificationTrapMask. Traps are sent to backupContacts only if they have the corresponding bit set in adminNotificationTrapMask and if a confirmed delivery to a station naming it as backup failed. Default: primaryContact(1) Enumeration: 'primaryContact': 1, 'backupContact': 2.

A bit array specifying which traps the station wishes to receive. Bit Trap 2^0 warmStart 2^1 cableFailure 2^2 reserved 2^3 duplicateIPAddr 2^4 utilizationAlarm 2^5 errorsAlarm 2^6 broadcastsAlarm 2^7 collisionsAlarm 2^8 authenticationFailure 2^9 hostInactive 2^10 hostActive 2^11 newHost 2^12 hostLimitExceeded

A bit array specifying which traps the station wishes to receive with confirmed delivery. Any bits set must also be set in adminNotificationTrapMask. If a trap sent with confirmed delivery is not acknowledged within adminNotificationTimeout seconds it is sent again. After adminNotificationRetries attempts to deliver the trap, the LANtern network monitor gives up, and tries to deliver it to the station specified by adminNotificationBackup.

For traps with confirmed delivery, adminNotificationTimeout specifies the interval (in seconds) between retries.

For traps with confirmed delivery, adminNotificationRetries specifies the number of retries that should be attempted before giving up and trying to deliver the trap to adminNotificationBackupIPAddr.

For traps with confirmed delivery, adminNotificationBackupIPAddr specifies the IP address of a backup station (also in adminNotificationTable) to be contacted should delivery of the trap to this station fail. Default: 0.0.0.0 (no backup)

A write (any value) causes the table entry to be deleted.

A unique handle that is generated for each trap issued and that is passed in the trap-PDU along with any other variable bindings.

A trap is acknowledged by writing the value of adminTrapHandle passed in the trap-PDU to adminTrapAcknowledge.

The name of the executable file to be downloaded from adminDownLoadServer.

The name of the file server from which to download a new executable image (adminDownLoadFile).

A write to adminDownload of temporaryChange(1) or permanentChange(2) causes the LANtern network monitor to discontinue its normal functions and perform a TFTP read of the file specified by adminDownLoadFile from the server specified by adminDownLoadServer into RAM. Upon successful completion of the file transfer, the new image is written to the flash EPROM memory (permanentChange only), destroying the previous image. The LANtern network monitor then performs a warm restart to activate the new image. A read of adminDownLoad returns the status of the last download. The values temporaryChange(1) and permanentChange(2) indicate a download is in progress. tftpFailed(4) indicates the server failed to respond or the transfer timed out. badFile(5) occurs if the LANtern network monitor determines the downloaded file has been corrupted or is not a LANtern executable. All other error codes are the values defined by the TFTP protocol [RFC 783], offset by six. Note: adminDownloadFile and adminDownLoadServer must be set prior (separate PDU) to setting adminDownLoad. Enumeration: 'permanentChange': 2, 'tftpFailed': 4, 'tftpUnknownTransferID': 11, 'badFile': 5, 'tftpUndefined': 6, 'tftpAccessViolation': 8, 'tftpIllegalOperation': 10, 'downloadSuccess': 3, 'tftpFileNotFound': 7, 'temporaryChange': 1.

A write to adminReset causes the LANtern network monitor to discontinue its normal functions and commence a restart sequence. The contents of RAM, including all counters and statistics, are lost. A coldRestart destroys the contents of the nonvolatile RAM and causes the LANtern network monitor to start up exactly as if power was supplied for the first time. This is equivalent to supplying power to the LANtern network monitor while holding the hardware reset button depressed. A warmRestart preserves the contents of the nonvolatile RAM and causes the LANtern network monitor to start up exactly as if the reset button had been pressed (or power was being restored after an outage). Enumeration: 'coldRestart': 1, 'warmRestart': 2.

The type of data link encapsulation to be used on the serial line. adminSerialDataLink may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When adminSerialDataLink is read, it returns the value currently in use, regardless of any previous writes. adminSerialDataLink is stored in nonvolatile RAM. Enumeration: 'slip': 1.

The IP address currently in use by the LANtern network monitor on the serial channel. adminSerialIPAddr may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When adminSerialIPAddr is read, it returns the IP address currently in use, regardless of any previous writes. adminSerialIPAddr is stored in nonvolatile RAM.

The subnet mask for the serial channel. adminSerialSubnetMask may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When this variable is read, it returns the subnet mask currently in use, regardless of any previous writes. When the value 0.0.0.0 is stored in this variable, the LANtern assumes no subnetting. adminSerialSubnetMask is stored in nonvolatile RAM.

A codification of the baud rate to be used on the serial line for incoming calls or when the line is directly connected. Change does not switch line speed until next state change of modem or reset. adminSerialBaudRate is stored in nonvolatile RAM. Enumeration: 'baud1200': 2, 'baud300': 1, 'baud19200': 7, 'baud7200': 5, 'baud2400': 3, 'baud4800': 4, 'baud9600': 6, 'baud38400': 8.

Once a phone connection has been established, the LANtern network monitor maintains that connection until either the other end hangs up or adminSerialTimeout seconds elapses with no communication. adminSerialTimeout is stored in nonvolatile RAM.

The type of connection used by the serial line. adminSerialConnection may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When adminSerialConnection is read, it returns the value currently in use, regardless of any previous writes. adminSerialConnection is stored in nonvolatile RAM. Enumeration: 'modem': 1, 'direct': 2.

The type of flow control used on the serial line. adminSerialFlowControl may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When adminSerialFlowControl is read, it returns the value currently in use, regardless of any previous writes. adminSerialFlowControl is stored in nonvolatile RAM. Enumeration: 'none': 1, 'rts-cts': 2.

A delimited string containing commands to initialize, dial, and hang up the modem. See Section 3.1.2 for more details on the format of this string. adminModemControl may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When adminModemControl is read, it returns the value currently in use, regardless of any previous writes. adminModemControl is stored in nonvolatile RAM.

A delimited string containing baud rates and modem responses when it connects at particular baud rates. See Section 3.1.2 for more details on the format of this string. adminModemConnect may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When adminModemConnect is read, it returns the value currently in use, regardless of any previous writes. adminModemConnect is stored in nonvolatile RAM.

A delimited string containing baud rates and modem responses when it connects at particular baud rates. See Section 3 for more details on the format of this string. adminModemNoConnect may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When adminModemNoConnect is read, it returns the value currently in use, regardless of any previous writes. adminModemNoConnect is stored in nonvolatile RAM.

A switch to enable or disable IP gatewaying between the serial line and the network. See Section 3 for more details on the format of this string. adminGatewayControl may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When adminGatewayControl is read, it returns the value currently in use, regardless of any previous writes. adminGatewayControl is stored in nonvolatile RAM. Enumeration: 'gateway-off': 1, 'gateway-on': 2.

A table that provides information about each possible phone connection that can be made over the serial channel. The table is accessed by adminPhoneIPAddr. A new entry can be created by writing to a nonexistent instance. Note that adminPhoneIPAddr is set implicitly from this write. adminPhoneIPAddr cannot be written directly. An entry may subsequently be deleted by writing (any value) to adminPhoneDelete. See Section 3 for more details about using the phone table. adminPhoneTable is stored in nonvolatile RAM.

Data for a particular phone connection that can be established over the serial channel.

The IP address of the machine or IP network (SLIP gateway) at adminPhoneNumber.

The IP subnet mask to be used when communicating over this phone connection. When the value 0.0.0.0 is stored in this variable, the LANtern network monitor assumes no subnetting. Default: 0.0.0.0 (no subnetting)

The IP address the LANtern network monitor uses for its serial port while communicating over this phone connection.

The phone number string the modem uses to dial the machine with IP address adminPhoneIPAddr.

An ASCII string specifying the logon sequence once the phone is connected.

A write (any value) causes the table entry to be deleted.

The total number of network events (good packets, error packets, and collisions) observed since counter initialization. A network event is any activity on the network in which signal transitions cause carrier sense to be active for more than 0.5 microseconds. Carrier sense dropouts that occur during collisions, and sometimes at the beginning or end of packets, are filtered out to ensure that an individual packet is counted only once.

The total number of legally formed packets received by the network controller since counter initialization.

The total number of good packets with the broadcast address as the destination address.

The total number of good packets with a multicast address as the destination address. The broadcast address is not included.

The total number of good packets with an individual host address as the destination address.

The total number of good packets between 64 and 127 octets in length, including the CRC.

The total number of good packets between 128 and 255 octets in length, including the CRC.

The total number of good packets between 256 and 511 octets in length, including CRC.

The total number of good packets between 512 and 1023 octets in length, including CRC.

The total number of good packets between 1024 and 1518 octets in length, including CRC.

The total number of errors detected since counter initialization. It is the sum of a CRC/Alignment errors, Oversize errors, Undersize errors, and Jabbers, as defined below.

The total number of legal size packets with a bad Frame Check Sequence (FCS) received by the network controller since counter initialization.

The total number of undersize packets received by the network controller since counter initialization. An undersize packet is one that is less than 64 octets long (including CRC) and is otherwise well formed.

The total number of oversize packets received by the network controller since counter initialization. An oversize packet is one that is longer than 1518 octets (including CRC) and is otherwise well-formed.

The total number of packets longer than 1518 octets with a bad Frame Check Sequence (FCS) received by the network controller since counter initialization.

The total number of local collisions observed since counter initialization. A local collision is a collision or other 'signal quality error' event that occurs on the segment to which the LANtern network monitor is attached.

The total number of packets shorter than 64 octets with a bad Frame Check Sequence (FCS) received by the network controller since counter initialization.

The total number of octets on the network in good packets. The source/destination address, the type/length field, and the CRC are included. This measurement gives a good indication of useful network throughput.

Time in microseconds. If read in the same PDU as other counters, this can be used to accurately compute statistics over time.

The number of microseconds during which carrier was detected on the cable. This can be used in conjunction with eTimeUSecs to accurately compute network utilization over time.

The number of discrete time intervals (or buckets) over which the logged data is saved. This number is a constant.

The interval, in seconds, represented by each bucket. eHistoryInterval is stored in nonvolatile RAM.

A log of the network events that occurred during each of the preceding eHistoryBuckets intervals of length eHistoryInterval.

Each logged counter has the same semantics as the counter with a similar name defined above, except that each counter records only those events that occurred during the log interval. The remaining log entries are defined below.

The number of network events (good packets, error packets, and collisions) observed during the interval. A network event is any activity on the network in which signal transitions cause carrier sense to be active for more than 0.5 microseconds. Carrier sense dropouts that occur during collisions, and sometimes at the beginning or end of packets, are filtered out to ensure that an individual packet is counted only once.

The number of legally formed packets received by the network controller during the interval.

The number of good packets with the broadcast address as the destination address received during the interval.

The number of good packets with a multicast address as the destination address received during the interval. The broadcast address is not included.

The number of good packets with an individual host address as the destination address received during the interval.

The number of good packets between 64 and 127 octets in length, including the CRC received during the interval.

The number of good packets between 128 and 255 octets in length, including the CRC received during the interval.

The number of good packets between 256 and 511 octets in length, including CRC received during the interval.

The number of good packets between 512 and 1023 octets in length, including CRC received during the interval.

The number of good packets between 1024 and 1518 octets in length, including CRC received during the interval.

The number of errors detected during the interval. It is the sum of a CRC/Alignment errors, Oversize errors, Undersize errors, and Jabbers, as defined below.

The number of legal size packets with a bad Frame Check Sequence (FCS) received by the network controller during the interval.

The number of undersize packets received by the network controller during the interval. An undersize packet is one that is less than 64 octets long (including CRC) and is otherwise well formed.

The number of oversize packets received by the network controller during the interval. An oversize packet is one that is longer than 1518 octets (including CRC) and is otherwise well- formed.

The number of packets longer than 1518 octets with a bad Frame Check Sequence (FCS) received by the network controller during the interval.

The number of local collisions observed during the interval. A local collision is a collision or other 'signal quality error' event that occurs on the segment to which the LANtern network monitor is attached.

The number of packets shorter than 64 octets with a bad Frame Check Sequence (FCS) received by the network controller during the interval.

The number of octets on the network in good packets during the interval. The source/destination address, the type/length field, and the CRC are included. This measurement gives a good indication of useful network throughput.

The average network utilization during this interval, in tenths of a percent.

The date and time of the start of the interval represented by the data in this bucket. This is the same as eHistoryIntervalEnd of the previous bucket.

The date and time of the end of the interval represented by the data in this bucket. This is the same as eHistoryIntervalStart of the next bucket.

A table of critical gauges for which an alarm is generated, if one exceeds its predetermined thresholds. The table is accessed by gauge type. The user-settable parameters of eAlarmTable are stored in nonvolatile RAM.

Parameters for each alarmed gauge.

Defines the network parameter being monitored by this gauge. percentUtilization: Average percent utilization. percentErrors: Errors as a percentage of total packets (good packets + errors). percentBroadcasts: Broadcast packets as a percentage of total good packets. percentCollisions: Local collisions as a percentage of total network events. Enumeration: 'percentCollisions': 4, 'percentBroadcasts': 3, 'percentUtilization': 1, 'percentErrors': 2.

The value, in tenths of one percent, of the monitored network parameter computed over the previous sampling interval.

If the gauge is enabled, its value is computed and an alarm (trap-PDU) is generated if either of its thresholds is exceeded. Otherwise, its value is not computed. eAlarmState is stored in nonvolatile RAM. Enumeration: 'armed': 2, 'disarmed': 1.

The interval, in seconds, over which eAlarmValue is sampled. eAlarmSampleTime is stored in nonvolatile RAM.

The minimum value the denominator of the alarm equation must achieve during the sample interval before the LANtern network monitor updates eAlarmValue. This can be used to prevent spurious alarms caused by very low traffic. eAlarmMinTraffic is stored in nonvolatile RAM.

The low threshold for eAlarmValue, in tenths of one percent. eAlarmLowThreshold is stored in nonvolatile RAM.

The high threshold for eAlarmValue, in tenths of one percent. eAlarmHighThreshold is stored in nonvolatile RAM.

The delta value used to offset the gauge value when the low threshold is passed, in tenths of one percent. eAlarmLowDelta is stored in nonvolatile RAM.

The delta value used to offset the gauge value when the high threshold is passed. eAlarmHighDelta is stored in nonvolatile RAM.

The lowest value seen for eAlarmValue, in tenths of one percent. This can be reset by writing to eAlarmLowWaterMark. The value written is ignored, and eAlarmLowWaterMark is set to the current value of eAlarmValue.

The highest value seen for eAlarmValue, in tenths of one percent. This can be reset by writing to eAlarmHighWaterMark. The value written is ignored, and eAlarmHighWaterMark is set to the current value of eAlarmValue.

The date and time eAlarmLowWaterMark was last set. This value is NULL until the first time eAlarmLowWaterMark is set.

The date and time eAlarmHighWaterMark was last set. This value is NULL until the first time eAlarmHighWaterMark is set.

If enabled, the LANtern network monitor generates a newHost trap whenever a new host first transmits on the network segment. Note that eHostNewHostAlarm is NOT stored in nonvolatile RAM, and returns to its default setting whenever the LANtern network monitor is reset (or powered-on). Enumeration: 'disabled': 1, 'enabled': 2.

The number of entries currently in eHostTable and eHostTTable.

Writing a date and time to eHostPurge causes the LANtern network monitor to purge all host table entries eHostTable where the date and time of both the most recent transmission and reception is earlier than that specified. All matrix entries (eMatrixSDTable and eMatrixDSTable) associated with the deleted host entries are also deleted. Hosts with the purge disable flag set are not deleted. Reading this variable returns the date and time of the last purge. The value returned is 0 (midnight 1 January 1900), if the table has never been purged.

Statistical data for each host seen on the network, accessed by MAC address. Entries may be 'preloaded' into the table by writing to eHostControl for the appropriate instance, which also creates a corresponding entry in eHostTTable and sets the date and time of first transmit to the current date and time. An entry can be deleted from the table by writing (any value) to eHostDelete. This also deletes the corresponding entry from eHostTTable and all entries from eMatrixSDTable and eMatrixDSTable that reference that host.

Statistical data for each host seen on the network, accessed by eHostAddress.

The MAC layer physical address of the host.

The total number of good packets transmitted to this address.

The total number of good packets transmitted by this host.

The total number of octets in good packets transmitted to this address.

The total number of octets in good packets transmitted by this host.

The total number of error (CRC, undersize, or oversize) packets transmitted to this address.

The total number of error (CRC, undersize, or oversize) packets transmitted by this host.

A bit array where each bit indicates a protocol that was seen in a packet transmitted by that host. The protocols currently monitored are: Bit Protocol 2^0 Unrecognized protocol (none of the following) 2^1 DOD (IP, ARP, RARP) 2^2 ISO 2^3 DEC 2^4 NetWare 2^5 AppleTalk (AppleTalk, AppleTalk ARP) 2^6 XNS 2^7 SNA 2^8 VINES

The date and time of the first good transmission by this host. If the host has not transmitted, this value is 0

The date and time of the most recent transmission by this host. If the host has not transmitted, this value is 0

The data and time of the most recent transmission to this address.

A collection of control bits and bit fields. These fields are grouped into one object to reduce network traffic (especially over the serial line) during startup. Writing to eHostControl may be used to pre-load entries into the table. This also has the side effect of inhibiting newHost traps for that host. BITS MEANING 2^0-2^2 3-bit host timeout code 0 - host timeout disabled 1 - 1 minute 2 - 2 minutes 3 - 4 minutes 4 - 8 minutes 5 - 16 minutes 6 - 32 minutes 7 - 64 minutes 2^3 onSegmentBit: if set, host is on LANtern's segment. 2^7 inhibitPurgeBit: if set, inhibit purge for this host.

An entry may be deleted from eHostTable by writing (any value) to eHostDelete. Note that this overrides the purge disable flag in eHostControl. Any entries in the matrix tables (eMatrixSDTable and eMatrixDSTable) that reference the host being deleted also are deleted.

Statistical data for each host that has transmitted on the network; accessed by eHostTFirstTransmit (and an ordinal number to resolve ambiguities).

The contents are identical to those described for eHostTable above except that the access for eHostTControl is read-only for all communities. The table is accessed by eHostTFirstTransmit (and an ordinal number to resolve ambiguities)

The MAC layer physical address of the host.

The total number of good packets transmitted to this address.

The total number of good packets transmitted by this host.

The total number of octets in good packets transmitted to this address.

The total number of octets in good packets transmitted by this host.

The total number of error (CRC, undersize, or oversize) packets transmitted to this address.

The total number of error (CRC, undersize, or oversize) packets transmitted by this host.

A bit array where each bit indicates a protocol that was seen in a packet transmitted by that host. The protocols currently monitored are: Bit Protocol 2^0 Unrecognized protocol (none of the following) 2^1 DOD (IP, ARP, RARP) 2^2 ISO 2^3 DEC 2^4 NetWare 2^5 AppleTalk (AppleTalk, AppleTalk ARP) 2^6 XNS 2^7 SNA 2^8 VINES

The date and time of the first good transmission by this host. If the host has not transmitted, this value is 0

The date and time of the most recent transmission by this host. If the host has not transmitted, this value is 0

The data and time of the most recent transmission to this address.

A collection of control bits and bit fields. These fields are grouped into one object to reduce network traffic (especially over the serial line) during startup. Writing to eHostControl may be used to pre-load entries into the table. This also has the side effect of inhibiting newHost traps for that host. BITS MEANING 2^0-2^2 3-bit host timeout code 0 - host timeout disabled 1 - 1 minute 2 - 2 minutes 3 - 4 minutes 4 - 8 minutes 5 - 16 minutes 6 - 32 minutes 7 - 64 minutes 2^3 onSegmentBit: if set, host is on LANtern's segment. 2^7 inhibitPurgeBit: if set, inhibit purge for this host.

The number of entries currently in eMatrixSDTable and eMatrixDSTable.

Writing a date and time to eMatrixPurge causes the LANtern network monitor to purge all matrix (eMatrixSDTable and eMatrixDSTable) table entries where the date and time of most recent transmission is earlier than the specified time. The whole table can be purged by writing a time later than the current time. Reading this variable returns the time of most recent manual or automatic purge. The value returned is 0 (midnight 1 January 1900), if the table has never been purged.

A table of network traffic sent from one particular source host to one particular destination host. A particular object instance is accessed by appending the source host address followed by the destination host address. This allows the table to be traversed with the source address as the major key and the destination address as the minor key. An entry may be deleted from the table by writing to eMatrixSDDelete.

The statistics for traffic in a particular direction between two hosts on the network.

The MAC layer physical address of the source host.

The MAC layer physical address of the destination host.

The number of good packets sent from eMatrixSDSourceAddress to eMatrixSDDestAddress.

The number of octets in good packets sent from eMatrixSDSourceAddress to eMatrixSDDestAddress.

The number of error (CRC/align/undersize/oversize) packets sent from eMatrixSDSourceAddress to eMatrixSDDestAddress.

A bit array where each bit indicates a protocol that was seen in a packet sent from eMatrixSDSourceAddress to eMatrixSDDestAddress. The protocols currently monitored are: Bit Protocol 2^0 Unrecognized protocol (none of the following) 2^1 DOD (IP, ARP, RARP) 2^2 ISO 2^3 DEC 2^4 NetWare 2^5 AppleTalk (AppleTalk, AppleTalk ARP) 2^6 XNS 2^7 SNA 2^8 VINES

The date and time the first transmission from eMatrixSDSourceAddress to eMatrixSDDestAddress.

The date and time of the most recent transmission from eMatrixSDSourceAddress to eMatrixSDDestAddress.

A write (any value) causes the table entry to be deleted.

A table of network traffic sent from one particular source host to one particular destination host. A particular object instance is accessed by appending the destination address followed by the source address. This allows the table to be traversed with the destination address as the major key and the source address as the minor key. An entry may be deleted from the table by writing to eMatrixDSDelete.

The contents of the table are identical to those described above for eMatrixSDTable.

The MAC layer physical address of the source host.

The MAC layer physical address of the destination host.

The number of good packets sent from eMatrixDSSourceAddress to eMatrixDSDestAddress.

The number of octets in good packets sent from eMatrixDSSourceAddress to eMatrixDSDestAddress.

The number of error (CRC/align/undersize/oversize) packets sent from eMatrixDSSourceAddress to eMatrixDSDestAddress.

A bit array where each bit indicates a protocol that was seen in a packet sent from eMatrixDSSourceAddress to eMatrixDSDestAng defining the time zone of thee protocols currently monitored are: Bit Protocol 2^0 Unrecognized protocol (none of the following) 2^1 DOD (IP, ARP, RARP) 2^2 ISO 2^3 DEC 2^4 NetWare 2^5 AppleTalk (AppleTalk, AppleTalk ARP) 2^6 XNS 2^7 SNA 2^8 VINES

The date and time the first transmission from eMatrixDSSourceAddress to eMatrixDSDestAddress.

The date and time of the most recent transmission from eMatrixDSSourceAddress to eMatrixDSDestAddress.

A write (any value) causes the table entry to be deleted.

The LANtern network monitor performs a periodic cable check every eMediaCheckInterval seconds. If eMediaCheckInterval is zero, periodic cable checks are not performed. eMediaCheckInterval is stored in nonvolatile RAM.

Reading eMediaStatus returns the most recent cable check, automatic or manual. Writing any value causby the LANtern network . This object is also passed in the cableFailure trap-PDU. Enumeration: 'transceiverCableBad': 2, 'cableOk': 1, 'ethernetCableBad': 3.

The maximum number of unicast addresses which the LANtern host table holds. A value of 0 indicates that there is no limit other than memory constraints. The value 0 will be returned by LANtern and the value 32 will be returned by LANtern LTD.

The count of the number of packets which were transmitted between hosts on the same segment as the LANtern.

The count of the number of octets in packets which were transmitted between hosts on the same segment as the LANtern.

The count of the number of packets which were transmitted by hosts on the same segment as the LANtern to hosts on other segments.

The count of the number of octets in packets which were transmitted by hosts on the same segment as the LANtern to hosts on other segments.

The count of the number of packets which were transmitted by hosts on other segments to hosts on the same segment as the LANtern.

The count of the number of octets in packets which were transmitted by hosts on other segments to hosts on the same segment as the LANtern.

The count of the number of packets seen on the LANtern's segment which were transmitted between hosts which are not on the LANtern's segment.

The count of the number of octets in packets seen on the LANtern's segment which were transmitted between hosts which are not on the LANtern's segment.

A count of the number of hosts which have been deleted since the LANtern was powered on.

Statistical data for each host that has transmitted on the network; accessed by eHostOOrderIndex. This table exists to permit rapid downloading of the host table.

The contents are identical to those described for eHostTable above except that the access for eHostOControl is read-only for all communities and eHostOOrderIndex appears only in this table.

The MAC layer physical address of the host.

The total number of good packets transmitted to this address.

The total number of good packets transmitted by this host.

The total number of octets in good packets transmitted to this address.

The total number of octets in good packets transmitted by this host.

The total number of error (CRC, undersize, or oversize) packets transmitted to this address.

The total number of error (CRC, undersize, or oversize) packets transmitted by this host.

A bit array where each bit indicates a protocol that was seen in a packet transmitted by that host. The protocols currently monitored are: Bit Protocol 2^0 Unrecognized protocol (none of the following) 2^1 DOD (IP, ARP, RARP) 2^2 ISO 2^3 DEC 2^4 NetWare 2^5 AppleTalk (AppleTalk, AppleTalk ARP) 2^6 XNS 2^7 SNA 2^8 VINES

The date and time of the first good transmission by this host. If the host has not transmitted, this value is 0

The date and time of the most recent transmission by this host. If the host has not transmitted, this value is 0

The data and time of the most recent transmission to this address.

A collection of control bits and bit fields. These fields are grouped into one object to reduce network traffic (especially over the serial line) during startup. Writing to eHostControl may be used to pre-load entries into the table. This also has the side effect of inhibiting newHost traps for that host. BITS MEANING 2^0-2^2 3-bit host timeout code 0 - host timeout disabled 1 - 1 minute 2 - 2 minutes 3 - 4 minutes 4 - 8 minutes 5 - 16 minutes 6 - 32 minutes 7 - 64 minutes 2^3 onSegmentBit: if set, host is on LANtern's segment. 2^7 inhibitPurgeBit: if set, inhibit purge for this host.

A (dense) ordinal that uniquely defines an entry in the eHostOTable table.

Writing an IP address to ipPingTarget causes the LANtern network monitor to ping that host (using ICMP Echo). When the LANtern network monitor receives the echo response, a pingNotification trap is issued to the host that requested the ping. The data passed with the trap are ipPingTarget and ipPingDuration. Note: There is a separate instance of this variable (indexed by the IP address of the host to receive the notification) for each ping outstanding. This is best illustrated by an example; suppose one wants to request the LANtern to ping host 130.57.1.2 and send the ping notification trap to host 130.57.8.9. Accordingly, a set request as follows has the desired effect: ipPingTarget.130.57.8.9 = 130.57.1.2

The elapsed time between the LANtern network monitor's issuance of the Ping and its receipt of the response. This data is passed with the pingNotification trap. Note: There is a separate instance of this variable (indexed by the IP address of the host to receive the notification) for each ping outstanding. This is best illustrated by an example; suppose one wants to request the LANtern to ping host 130.57.1.2 and send the ping notification trap to host 130.57.8.9. Accordingly, a set request as follows has the desired effect: ipPingDuration.130.57.8.9 = 130.57.1.2

Enables or disables duplicate IP address checking. ipDupeCheck may be written at any time; however, the change does not take effect until the LANtern network monitor is restarted. When ipDupeCheck is read, it returns the current state of duplicate IP address checking, regardless of any previous writes. ipDupeCheck is stored in nonvolatile RAM. Enumeration: 'disabled': 1, 'enabled': 2.

Table of active duplicate IP address alarms, accessed by IP address.

Data pertinent to the duplicate IP address alarm.

The IP address that was observed being used by more than one host.

The physical network address of the host that is authorized to use the IP address. Initially, this is the host that was first seen to use the IP address. Once an alarm has been generated, the administrator may override this assumption by writing the real authorized physical address to ipDupeGoodMACAddr.

The physical network address of the host that is erroneously using the IP address.

The date and time the duplicate usage of the IP address was detected.

When the condition causing the alarm has been fixed, the administrator should clear the alarm by writing to alarmDupIpClear. Either of the two MAC addresses can be sanctioned or, alternatively, all knowledge of that IP address can be purged by specifying sanctionNeither. Enumeration: 'sanctionBad': 2, 'sanctionGood': 1, 'sanctionNeither': 3.

A table containing mappings from physical media addresses to IP addresses; accessed by ipMACToIPMACAddr. ipMACToIPIPAddr is also required as a secondary index to resolve ambiguities since any given physical address may have more than one IP address. Note that this table is a by-product of duplicate IP address checking and, as such, is subject to the following limitations: the table has no entries if ipDupeCheck is disabled, data is available only for hosts on the (LANtern network monitor's) local subnet, and data is available only for hosts that have successfully transmitted an IP packet while the LANtern network monitor has been monitoring the segment. An entry may be deleted by writing (any value) to ipMACToIPDelete.

The mapping from a physical media address to an IP address.

The physical media address.

The IP address.

An entry may be deleted from ipMACToIPTable by writing (any value) to ipMACToIPDelete. This also deletes the entry in the ipDupeTable for the same IP address if such an entry exists.

Writing an ethernet address to ieee8022TestTarget causes the LANtern to send an 802.2 Test packet to that address.

Writing an ethernet address to ipxDiagnosticTarget causes the LANtern to send two diagnostic packets, one in ethernet frame format, and the other in 802.3 frame format.

The count of packets observed with an unknown protocol.

The count of octets in packets observed with an unknown protocol.

The count of packets observed with a protocol from the TCP/IP suite (IP, ARP, and RARP).

The count of octets in packets observed with a protocol from the TCP/IP suite (IP, ARP, and RARP).

The count of packets observed with a protocol from the ISO suite.

The count of octets in packets observed with a protocol from the ISO suite.

The count of packets observed with a protocol from the Digital Equipment Corporation protocol suite.

The count of octets in packets observed with a protocol from the Digital Equipment Corporation protocol suite.

The count of packets observed with a protocol from the NetWare suite.

The count of octets in packets observed with a protocol from the NetWare suite.

The count of packets observed with a protocol from the AppleTalk suite.

The count of octets in packets observed with a protocol from the AppleTalk suite.

The count of packets observed with a protocol from the XNS suite.

The count of octets in packets observed with a protocol from the XNS suite.

The count of packets observed with a protocol from the SNA suite.

The count of octets in packets observed with a protocol from the SNA suite.

The count of packets observed with a protocol from the Banyan VINES suite.

The count of octets in packets observed with a protocol from the Banyan VINES suite.