Home/Catalog/XEDIA-SYSTEM-MIB

XEDIA-SYSTEM-MIB

AI MIB Summary

The XEDIA-SYSTEM-MIB provides SNMP objects to monitor and manage system-level parameters, including hardware status, resource utilization, and operational state, specifically for Xedia embedded networking devices.

This module defines objects for management of Xedia devices.
Main OID:
xediaSystemMIB.1.3.6.1.4.1.838.3.1
207
Objects
Active
Status
5
Dependencies

Imported Objects

SNMPv2-SMI
SNMPv2-TC
SNMPv2-CONF
XEDIA-REG
IF-MIB

Objects

207 total
Object Name
xediaSystemMIBThis module defines objects for management of Xedia devices.
MODULE-IDENTITY
.1.3.6.1.4.1.838.3.1
xsysObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1
xsysGeneral
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1.1
xsysDateTimeThe current date and time of the system. Note that this can also be used to set the current date and time as well as read it.rw
DateAndTimeForm
.1.3.6.1.4.1.838.3.1.1.1.1
xsysOperStatusThe current operational status of the system as a whole. A value 'unknown(1)' indicates that the current state of the system could not be determined. The value 'running(2)' indicates that the system is up and running and that no unusual error conditions are known. The 'warning(3)' state indicates that agent has been informed of an unusual error condition by the operational software (e.g., a device driver) but that the system is still 'operational'. (The xsysBootDiagsCode object may provide more information.) A value of 'testing(4)', indicates that the system is not available for use because it is in the testing state. The state of 'down(5)' is used only when the agent has been informed that the system is not available for any use. (How it can tell you it's down is an interesting question.)ro
Enumeration
.1.3.6.1.4.1.838.3.1.1.1.2
xsysResetControlThis is the 'software reset button' of the agent. When read, this object always returns the value 'ready(1)'. When set to 'reset(2)', the system will reset and reload its configuration from NVRAM. When set to 'resetToDefaults(3)', the system will delete its configuration parameters and then reset, which will cause it to come up with its default configuration.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.1.3
xsysNextBootDiagsLevelThe level of diagnostic tests to run the next time the system is reset. Setting the value 'none(1)' skips all diagnostic tests (and therefore makes the system boot faster). The value 'normal(2)' (the default) runs the basic set of diagnostic teams. The value 'full(3)' runs a greater-than-normal set of tests that may be useful to diagnose unusual hardware failures.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.1.4
xsysBootDiagsCodeAn error code giving more detail about a boot diagnostics failure indicated by xsysOperStatus 'warning(3)' or 'down(5)'. The value 0 indicates no failure detected or an unknown failure type. See the product user's guide for interpretation of the error code.ro
Integer32
.1.3.6.1.4.1.838.3.1.1.1.5
xsysLastBootTypeAn indication of type of the last system boot. The value 'warmBoot(2)' indicates the system was reset by software (e.g., via the xsysResetControl object). The value 'coldBoot(3)' indicates the system was reset via a hardware reset button or power cycle.ro
Enumeration
.1.3.6.1.4.1.838.3.1.1.1.6
xsysNumResetsA count of the number of times the system has been reset either via a hardware switch, via the software xsysResetControl object, or via any other means (cable seeking backhoe, software spasm, etc.) Note that a manager can use this object to determine if it has missed any warmStart or coldStart traps and to detect counter discontinuities.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.1.7
xsysDisableLoginPromptSetting this object to the value 'true(1)' will disable the login prompt so that users of the Command Line Interface (CLI) automatically get admin permissions.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.8
xsysFile
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1.1.9
xsysCompactFlashThis is the command to compact Flash memory to regain space. To begin a compact, set the object to 'compact'. When read, this object will return the appropriate status. The status 'ready' is returned when a compact is possible, 'compactInProgress' is returned when there is an unfinished compact still running, and 'flashNotAvailable' is returned if another system is currently manipulating the flash.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.1.9.1
xsysRunningImageInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1.1.9.2
xsysRunningImageNameThe software name for the currently running software image.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.9.2.1
xsysRunningImageVersionThe running image version.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.9.2.2
xsysRunningImageBuildDateThe running image build date.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.9.2.3
xsysBootImageTableA table of 'boot files' (either real or virtual) that can be used.
SEQUENCE OF XsysBootImageEntry
.1.3.6.1.4.1.838.3.1.1.1.9.3
xsysBootImageEntryInformation about a single Boot Image
XsysBootImageEntry
.1.3.6.1.4.1.838.3.1.1.1.9.3.1
xsysBootImageIndexThe index of the table.
INTEGER
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.1
xsysBootImageBootPriorityThe boot priority for a given entry. Lowest is highest priority.rw
Unsigned32
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.2
xsysBootImageSrcThe source of the file to transfer. The only valid selection is Network or Flash.rw
XStorageType -- network or flash only
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.3
xsysBootImageSrcNameThe name of the source file to be transfered.rw
DisplayString
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.4
xsysBootImageSrcTypeThe type of file represented by the file source name.ro
XFileType
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.5
xsysBootImageDestNameThe local name of the destination file.rw
DisplayString
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.6
xsysBootImageServerAddrThe IP address of the remote TFTP server.rw
IpAddress
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.7
xsysBootImageLocalAddrThe local IP address used during a boot TFTP.rw
IpAddress
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.8
xsysBootImageMaskThe IP address mask used during a boot TFTP.rw
IpAddress
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.9
xsysBootImageDefaultRouterThe IP address for the default router used during a boot TFTP.rw
IpAddress
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.10
xsysBootImageSlotThe internal slot (slot/port) used during a boot TFTP.rw
Unsigned32
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.11
xsysBootImagePortThe internal port (slot/port) used during a boot TFTP.rw
Unsigned32
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.12
xsysBootImageOperStatusThe status of the last boot image transfer.ro
XTransferStatus
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.13
xsysBootImageRowStatusThis object is used to add and remove entries from the table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.9.3.1.14
xsysTransferTableA table of 'files' (either real or virtual) that can be transfered.
SEQUENCE OF XsysTransferEntry
.1.3.6.1.4.1.838.3.1.1.1.9.4
xsysTransferEntryInformation about a single 'file' that can be transfered. The file may be in an actual file system or it may be a virtual file that exists only in memory, perhaps in a different format than it will have once it is transfered. For example, the eventLog may be stored as a linked list of data structures in RAM on the local system but uploaded in human-readable ASCII to the remote system. This table will be initialized to contain entries for the types of files it allows transfer of, though these entries will return the value 'notReady(3)' for their xsysTransferRowStatus column until the user provides values for any required columns. The agent may also not allow these entries to be deleted from the table. (Therefore, for agents that only support transfer of a fixed number of 'files', this can be implemented as a fixed length table.) Legal Transfers Matrix: SRC network flash nvram ram D network N Y (1) Y (1) Y (2) E flash Y (3) N Y (4) N S nvram Y (5) Y (6) N N T ram Y (7) Y (7) N N (1) this is how you back up config files to the network (2) done by dumper automatically when crash occurs (3) this is how you upgrade software from network (4) this is how you backup config locally (5) this is how you restore config from network (6) this is how you restore config locally (7) done by loader automatically during boot
XsysTransferEntry
.1.3.6.1.4.1.838.3.1.1.1.9.4.1
xsysTransferIndexIndicates the row entry number within the table.
Unsigned32
.1.3.6.1.4.1.838.3.1.1.1.9.4.1.1
xsysTransferSrcThe source of the file to transfer.rw
XStorageType
.1.3.6.1.4.1.838.3.1.1.1.9.4.1.2
xsysTransferSrcNameThe file name of the source file.rw
DisplayString
.1.3.6.1.4.1.838.3.1.1.1.9.4.1.3
xsysTransferDestThe destination for the file to transfer.rw
XStorageType
.1.3.6.1.4.1.838.3.1.1.1.9.4.1.4
xsysTransferDestNameThe file name of the destination file.rw
DisplayString
.1.3.6.1.4.1.838.3.1.1.1.9.4.1.5
xsysTransferServerAddrThe IP address of the the TFTP server.rw
IpAddress
.1.3.6.1.4.1.838.3.1.1.1.9.4.1.6
xsysTransferOperStatusThe status of the last transfer procedure, if any. This object will have a value of 'statusUnknown(2)' if no transfer process has been performed. The 'incompatibleFile(6)' may result, for example, if the file is a software image that is not compatible with this hardware, or, as another example, if the file contains configuration parameters for a newer revision of software than is currently running on the system. The other values should be self-explanatory.ro
XTransferStatus
.1.3.6.1.4.1.838.3.1.1.1.9.4.1.7
xsysTransferOperProgressA percent value updated periodically to represent the progress of a TFTP session.ro
INTEGER
.1.3.6.1.4.1.838.3.1.1.1.9.4.1.8
xsysTransferActionThe object is used to initiate the transfer manually. When read, it always returns the value 'ready(1)'. Setting the object to 'execute(2)' initiates the transfer as long as the xsysTransferRowStatus is 'active(1)' and another transfer is not currently in progress. The 'executeAndCreateBootRecord(3)' additionally creates a BootImageEntry if the transfer is of an OS image into flash. If the BootImageTable is full, the file transfer will fail. The newly created BootImageEntry will be initialized with the lowest priority and RowStatus of notInService. The value 'abort(3)' attempts to abort the transfer and will return a inconsistentValue SNMP error when set if the xsysTransferOperStatus is not currently 'inProgress(1)'. The action 'secureTransfer' is similar to the 'execute' action except it can only be used for configuration files when the source or destination is nvram. SecureTransfer uses authentication and encryption to protect the configuration file from modification, and from interception.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.1.9.4.1.9
xsysTransferRowStatusThis object is used to add and remove entries from the table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.9.4.1.10
xsysTransferEncryptPasswordThe password used for en/decryption.rw
DisplayString
.1.3.6.1.4.1.838.3.1.1.1.9.4.1.11
xsysStorageTableA table of storage devices. Note that this table parallels the one in the Host Resources MIB.
SEQUENCE OF XsysStorageEntry
.1.3.6.1.4.1.838.3.1.1.1.9.5
xsysStorageEntryInformation about the capacity and utilization of a storage device. The Xedia Velociraptor 1.0.0 product will have entries of type ram, nvram, and flash.
XsysStorageEntry
.1.3.6.1.4.1.838.3.1.1.1.9.5.1
xsysStorageAreaThe type of storage represented by this entry. Note that the value 'network(1)' cannot be used in this context.
XStorageType
.1.3.6.1.4.1.838.3.1.1.1.9.5.1.2
xsysStorageDescrA textual description of this storage device.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.9.5.1.3
xsysStorageAllocationUnitsThe size, in bytes, that xsysStorageSize and xsysStorageUsed is measured in.ro
Unsigned32 UNITS "bytes"
.1.3.6.1.4.1.838.3.1.1.1.9.5.1.4
xsysStorageSizeThe size of the storage device in the units identified by xsysStorageAllocationUnits.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.1.9.5.1.5
xsysStorageUsedThe amount of the storage represented by this entry that is allocated, in units of hrStorageAllocationUnits.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.1.9.5.1.6
xsysStorageAllocationFailuresThe number of requests for storage represented by this entry that could not be honored due to not enough storage. It should be noted that as this object has a SYNTAX of Counter32, that it does not have a defined initial value. However, it is recommended that this object be initialized to zero.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.1.9.5.1.7
xsysStorageBytesTotalThe size of the storage device in bytes.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.1.9.5.1.8
xsysStorageBytesUsedThe amount of the storage represented by this entry that is allocated, in bytes.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.1.9.5.1.9
xsysStorageBytesAvailableThe amount of the storage represented by this entry that is not allocated, in bytes.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.1.9.5.1.10
xsysFileListTableA table of File List entries.
SEQUENCE OF XsysFileListEntry
.1.3.6.1.4.1.838.3.1.1.1.9.6
xsysFileListEntryInformation about the files on the system.
XsysFileListEntry
.1.3.6.1.4.1.838.3.1.1.1.9.6.1
xsysFileNameA textual name of the file.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.9.6.1.1
xsysFileTypeThe type of file represented by the file name.ro
XFileType
.1.3.6.1.4.1.838.3.1.1.1.9.6.1.2
xsysFileBuildNameA textual Build name of the file.ro
DisplayString
.1.3.6.1.4.1.838.3.1.1.1.9.6.1.3
xsysFileBuildDateA textual Build date of the file.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.9.6.1.4
xsysFileBuildVersionA textual Version of the file.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.9.6.1.5
xsysFileSrcNameThe original source file name of the originating file.ro
DisplayString
.1.3.6.1.4.1.838.3.1.1.1.9.6.1.6
xsysFileSrcThe source type of the original file.ro
XStorageType
.1.3.6.1.4.1.838.3.1.1.1.9.6.1.7
xsysFileHostThe IP Address of the TFTP host that was used to copy the original source file. Or 0.0.0.0 if not applicable.ro
IpAddress
.1.3.6.1.4.1.838.3.1.1.1.9.6.1.8
xsysFileDateThe date associated with the file.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.9.6.1.9
xsysFileSizeThe size of the file in the units identified by xsysStorageAllocationUnits.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.1.9.6.1.10
xsysFileIsActiveThe active flag associated with the file.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.9.6.1.11
xsysFileRowStatusThis object is used to remove entries from the table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.9.6.1.12
xsysWatchdogUpdateThe number of seconds between the watchdog timer updates. A watch dog reset will occur if the timer is not updated within three (3) cycles. A value of 0 disables the watchdog timout. The valid range of a functioning update is 20-30 seconds. note: a node boot is required for changes to take affect.rw
INTEGER (0 | 20..30) UNITS "seconds"
.1.3.6.1.4.1.838.3.1.1.1.10
xsysDateTimeEpochSecondsThe current Date and Time represented by the number of seconds since January 1, 1970ro
Integer32
.1.3.6.1.4.1.838.3.1.1.1.11
xsysSnmpErrorLog
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1.1.12
xsysSnmpErrorLastThe error information logged from the last SNMP request.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.12.1
xsysSnmpErrorTableA table of File List entries.
SEQUENCE OF XsysSnmpErrorEntry
.1.3.6.1.4.1.838.3.1.1.1.12.2
xsysSnmpErrorEntryInformation about the files on the system.
XsysSnmpErrorEntry
.1.3.6.1.4.1.838.3.1.1.1.12.2.1
xsysSnmpErrorIpAddressThe IP Address of the errored request.
IpAddress
.1.3.6.1.4.1.838.3.1.1.1.12.2.1.1
xsysSnmpErrorReqIDThe PDU Request ID of the errored request.
Unsigned32
.1.3.6.1.4.1.838.3.1.1.1.12.2.1.2
xsysSnmpErrorMessageThe textual message of the errored request.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.12.2.1.3
xsysDebugModeThe Administrative mode to control destructive debug commands.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.1.13
xsysCreateSubInterfaceThe name of the layer interface for which a new sub-interface is to be created on. The layer interface must be the aggregate for that layer. For example, a value of ipsec.1 creates a sub-interface ipsec.1.1.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.14
xsysPreLoginBannerThe text string displayed prior to logging into the system from either the directly connect consol, or telnet. The standard control characters can be used to customize the output.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.15
xsysMotherBoardSerialNumberThe text string representing the serial number of the system's mother boardro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.1.16
xsysConfigParams
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1.2
xsysConfigLastWriteDateTimeThe value of xsysDateTime the last time any configuration parameter value was written to non-volatile memory. A zero-length value indicates that no changes have been made and that the system is running using all defaults. Note that this parameter must be saved in non-volatile memory across re-initializations of the system.ro
DateAndTimeForm
.1.3.6.1.4.1.838.3.1.1.2.1
xsysConfigLastWriteSourceThe source address of the entity that made the last configuration change to the system. The value 127.0.0.1 (the loopback address) indicates the local console. This value must also be saved in non-volatile memory across re-initializations of the system.ro
IpAddress
.1.3.6.1.4.1.838.3.1.1.2.2
xsysSubsystemTableThis table allows subsystems to be reset on an individual basis (as opposed to as a group using the xsysResetControl object).
SEQUENCE OF XsysSubsystemEntry
.1.3.6.1.4.1.838.3.1.1.2.3
xsysSubsystemEntryA subsystem that's currently running.
XsysSubsystemEntry
.1.3.6.1.4.1.838.3.1.1.2.3.1
xsysSubsystemNameThe name that uniquely identifies the subsystem.
DisplayString
.1.3.6.1.4.1.838.3.1.1.2.3.1.1
xsysSubsystemResetControlSetting this object causes individual subsystems to take action, as defined below. Not all subsystems support all of the actions available. Valid actions for each subsystem can be set without errors. If an action is invalid for a subsystem, then an error PDU of 'BadValue' is returned. o ready - NoOp. No action is taken by the subsystem. o defaultConfig - All configuration records associated with the particular subsystem are deleted. The subsystem will restore to default configuration if possible, or it continues to run using its runtime values. On the next node boot, default records will be written to the configuration memory. o reset - The subsystem will be restarted using its existing configuration memory. o resetToDefaults - All configuration records associated with the particular subsystem are deleted. The subsystem is then restarted, causing default records to be written to configuration memory. o purgeRecords - All old configuration records associated with the particular subsystem are deleted. Some subsystems maintain old configuration records. This allows you to downgrade without losing configuration information. These old configuration records consume configuration memory. Purging old configuration records frees the associated configuration memory for current use. When read, the value of the object is always 'ready(1)'.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.2.3.1.2
xsysConfigFileStartThe address of the start of the virtual config file.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.2.4
xsysConfigEndOfFileThe address of the end of the virtual config file.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.2.5
xsysConfigEndOfDataThe address where data ends in the config file.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.2.6
xsysConfigDataSizeThe sum of all data blocks in the config file.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.2.7
xsysConfigFreeBlocksTotalBytesThe sum of all free blocks in the config file.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.2.8
xsysConfigNumberConfigRecsThe number records in file counter.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.2.9
xsysConfigPercentFullThe percentage of NVRAM that is full.ro
Gauge32
.1.3.6.1.4.1.838.3.1.1.2.10
xsysConfigCompressionDisplays whether configuration file compression is currently active or not. The operational effects of compression are transparent to the user.ro
Enumeration
.1.3.6.1.4.1.838.3.1.1.2.11
xsysEvents
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1.4
xsysEventTableA table of events in the order that they were generated. An event may or may not be added to this (conceptual) table based on whether it passes all of the input filter criteria identified below. Also, when the table is retrieved via SNMP operations, it may or may not include a specific event based on the current output filter criteria.
SEQUENCE OF XsysEventEntry
.1.3.6.1.4.1.838.3.1.1.4.1
xsysEventEntryInformation about a single event.
XsysEventEntry
.1.3.6.1.4.1.838.3.1.1.4.1.1
xsysEventIndexIndicates the number of the event. Events are numbered sequentially from 1 - n. A management station can keep track of the last event it uploaded and periodically GET-NEXT from there to determine if there have been any new events. This means that, as events are removed from the table their indices are not reused until the next reset to default configuration (which loses all stored events). Also, the agent must store the 'next available event number' value across re-initializations of the system, resetting it to 1 only when the configuration is reset to defaults.
Unsigned32
.1.3.6.1.4.1.838.3.1.1.4.1.1.1
xsysEventDateTimeThe date and time when this event was generated.ro
DateAndTimeForm
.1.3.6.1.4.1.838.3.1.1.4.1.1.2
xsysEventSubsystemThe subsystem this event was generated by.ro
DisplayString
.1.3.6.1.4.1.838.3.1.1.4.1.1.3
xsysEventLevelThe level of the event.ro
Enumeration
.1.3.6.1.4.1.838.3.1.1.4.1.1.4
xsysEventIdThe identifier of the event. This id is unique within a subsystem.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.4.1.1.5
xsysEventMsgTextual message associated with the event.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.4.1.1.6
xsysEventMaxTableSizeThe maximum number of events in the event log table. When the number of events exceeds this value, newer events continue to be added and the oldest events are discarded. Changing this object takes affect on the next system boot. Note that the last 20 warning and fatal level events are also stored to non-volatile memory and are relogged into event log upon the next system boot.rw
Integer32
.1.3.6.1.4.1.838.3.1.1.4.2
xsysEventInFilterLevelThe current event input filter level. The user can choose to not log events of the lower levels, but they cannot filter out warning and fatal events. By default, debug and trace events are filtered on input.rw
BIT STRING { debug(0), trace(1), info(2) }
.1.3.6.1.4.1.838.3.1.1.4.3
xsysEventOutFilterLevelThe current event output filter level. The output filter effects which entries are returned when the table is dumped (e.g., via a GET-NEXT sweep). By default, no events are filtered on output.rw
BIT STRING { debug(0), trace(1), info(2), warning(3), fatal(4) }
.1.3.6.1.4.1.838.3.1.1.4.4
xsysEventOutFilterDateTimeThe current event output filter level based on date/time. Only events with xsysEventDateTime at or after this date are returned. By default, events from all date/times are returned.rw
DateAndTimeForm
.1.3.6.1.4.1.838.3.1.1.4.5
xsysEventSubsystemFilterTableA table of filter information by subsystem.
SEQUENCE OF XsysEventSubsystemFilterEntry
.1.3.6.1.4.1.838.3.1.1.4.6
xsysEventSubsystemFilterEntryFilter information for a particular subsystem.
XsysEventSubsystemFilterEntry
.1.3.6.1.4.1.838.3.1.1.4.6.1
xsysEventSubsystemFilterSubsystemThe subsystem this filter applies to.
DisplayString
.1.3.6.1.4.1.838.3.1.1.4.6.1.1
xsysEventSubsystemFilterDirectionThe direction(s) to filter events from this subsystem, if any. By default, events from a subsystem are not filtered in either direction.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.4.6.1.2
xsysEventIdFilterTableA table of filter information for each subsystem/id combination.
SEQUENCE OF XsysEventIdFilterEntry
.1.3.6.1.4.1.838.3.1.1.4.7
xsysEventIdFilterEntryInformation for a particular subsystem/id combination.
XsysEventIdFilterEntry
.1.3.6.1.4.1.838.3.1.1.4.7.1
xsysEventIdFilterIdThe identifier of the event this filter information is for.
Unsigned32
.1.3.6.1.4.1.838.3.1.1.4.7.1.1
xsysEventIdFilterNameThe textual name of the event.ro
DisplayString
.1.3.6.1.4.1.838.3.1.1.4.7.1.2
xsysEventIdFilterMessageThe descriptive message of the eventro
DisplayString
.1.3.6.1.4.1.838.3.1.1.4.7.1.3
xsysEventIdFilterDirectionThe direction(s) in which to filter this event id. Note that the filter information per event id is only looked at if the subsystem as a whole is not being filtered. By default, individual event ids are not filtered.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.4.7.1.4
xsysEventsClearAllControlSetting this object to 'execute(2)' removes all entries from the xsysEventTable. When read, this object always returns the value 'ready(1)'.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.4.8
xsysEventsAsTrapsThis object is used to control whether Xedia system events are sent as SNMP traps. Generally, it is not appropriate to send all events as traps since this would consume a fairly large amount of network bandwidth. However, in the case where the events may be useful for debugging purposes, this object can be changed to 'true(1)'.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.4.9
xsysEventDisplayNormally, all events that pass the input filter criteria are both logged and written out to the system console. This can be a problem if the console is being used interactively, for example to configure the system. Therefore, this object can be set to 'false(2)' to disable printing of the events as they occur to the display. Instead, the user can display the event log using explicit commands.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.4.10
xsysEventsAsSyslogMessagesThis object is used to control whether Xedia system events are sent as UNIX syslog messages. Generally, it is not appropriate to send all events as syslog messages since this would consume a fairly large amount of network bandwidth and system resources, such as CPU processing. However, in the case where it is desirable to archive system events to a host with a hard drive, or tools that can manipulate the log output, this object can be changed to 'true(1)'.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.4.11
xsysEventSyslogRemoteServerPTS FIX THIS - NEEDS DESCRIPTION HERE The address(es) of the remote host where a syslogd syslog daemon is running and awaits messages from this AccessPoint. Maximum number of remote servers is limited to 5.rw
DisplayString
.1.3.6.1.4.1.838.3.1.1.4.13
xsysEventNvRamMaxTableSizeThe maximum number of warning and fatal level events could be stored to non-volatile memory and are relogged into event log upon the next system boot. When the number of events exceeds this value, newer events continue to be added and the oldest events are discarded. Changing this object takes affect on the next system boot.rw
Integer32
.1.3.6.1.4.1.838.3.1.1.4.14
xsysHardware
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1.5
xsysProcessorDescrA textual description of the (main) processor for the system. This should include the manufacturer and the revision/clock speed.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.5.1
xsysPowerSupplyTypeThe type of the power supply.ro
Enumeration
.1.3.6.1.4.1.838.3.1.1.5.2
xsysCpuUtilizationThe average, over some implementation-defined sampling period, of the percentage of time that the system's (main) processor was not idle.ro
Gauge32
.1.3.6.1.4.1.838.3.1.1.5.3
xsysPciTableA table of PCI devices in the system.
SEQUENCE OF XsysPciEntry
.1.3.6.1.4.1.838.3.1.1.5.4
xsysPciEntryInformation about a single PCI device in the system.
XsysPciEntry
.1.3.6.1.4.1.838.3.1.1.5.4.1
xsysPciDeviceIndexA arbitrary unique number to identify the PCI device in the system.
Unsigned32
.1.3.6.1.4.1.838.3.1.1.5.4.1.1
xsysPciVendorIdThe vendor (manufacturer) of the device. Values that are relevent to the Xedia Velociraptor include: 4113 (0x1011) - DEC 0000 (0x0000) - Darkroom Technology ?? 0000 (0x0000) - SDL ?? 4523 (0x11ab) - Galileo Technologyro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.5.4.1.2
xsysPciDeviceIdA vendor-defined identifier for the particular device.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.5.4.1.3
xsysPciRevisionIdA revision number of the device, assigned by the vendor.ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.5.4.1.4
xsysPciBaseClassThe type (class) of PCI device.ro
Enumeration
.1.3.6.1.4.1.838.3.1.1.5.4.1.5
xsysPciSubClassThe sub-type (or sub-class) of the PCI device. This value can only be interpreted relative to the xsysPciBaseClass value. Interesting device sub-classes relevent to Xedia's Velociraptor: Class networkController: ethernetController(0), tokenRingController(1), fddiController(2), atmController(3), otherNetworkController(4) Class bridgeDevice: hostPciBridge(0), pciIsaBridge(1), pciEisaBridge(2), pciMicroChannelBridge(3), pciPciBridge(4), pciPcmciaBridge(5), pciNuBusBridge(6), pciCardBusBridge(7), otherBridgeDevice(128)ro
Unsigned32
.1.3.6.1.4.1.838.3.1.1.5.4.1.6
xsysPciStatusThis is the PCI status register. Most of these bits are totally uninteresting to the end-user but are included for debugging purposes. For more detail see Table 6-3 'Status Register Bits' in the reference below.ro
BIT STRING { reserved0(0), reserved1(1), reserved2(2), reserved3(3), reserved4(4), mhz66Capable(5), udfSupported(6), fastBackToBackCapable(7), dataParityErrorDetected(8), devselTiming1(9), devselTiming2(10), signaledTargetAbort(11), receivedTargetAbort(12), receivedMasterAbort(13), signaledSystemError(14), detectedParityError(15) }
.1.3.6.1.4.1.838.3.1.1.5.4.1.7
xsysPciIfIndexThe ifIndex of the associated interface or 0 if the PCI device is not interface-related.ro
InterfaceIndexOrZero (IF-MIB)
.1.3.6.1.4.1.838.3.1.1.5.4.1.8
xsysPciFatalBusErrorsThe total number of fatal bus errors that were detected by this device. This will be a sum of xsysPciMasterAborts, xsysPciParityErrors, and xsysPciTargetAbortsro
Counter32
.1.3.6.1.4.1.838.3.1.1.5.4.1.9
xsysPciMasterAbortsThe total number master abort errors that were detected by this device.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.5.4.1.10
xsysPciParityErrorsThe total number of parity errors that were detected by this device.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.5.4.1.11
xsysPciTargetAbortsThe total number of target abort errors that were detected by this device.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.5.4.1.12
xsysSerial
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1.6
xsysSerialConfigTableThis table contains configuration information for the serial ports of the system.
SEQUENCE OF XsysSerialConfigEntry
.1.3.6.1.4.1.838.3.1.1.6.1
xsysSerialConfigEntryConfiguration information for one of the system's serial ports.
XsysSerialConfigEntry
.1.3.6.1.4.1.838.3.1.1.6.1.1
xsysSerialPortNumberThe physical port number of the serial port.
Unsigned32
.1.3.6.1.4.1.838.3.1.1.6.1.1.1
xsysSerialBaudRateThe baud rate in bits per second for this serial port.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.6.1.1.2
xsysSerialDataBitsThe number of data bits for this serial port.rw
Unsigned32
.1.3.6.1.4.1.838.3.1.1.6.1.1.3
xsysSerialParityThe type of parity supported on this serial port.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.6.1.1.4
xsysSerialStopBitsThe number of stop bits on this serial port.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.6.1.1.5
xsysSerialFlowControlThe type of flow control used on this serial port.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.6.1.1.6
xsysSerialTimeoutThe number of seconds of inactivity to allow before timing out the session using the serial port. The value 0 means no timeout.rw
Unsigned32
.1.3.6.1.4.1.838.3.1.1.6.1.1.7
xsysInterfaces
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1.7
xsysIfNameIndexTableA table of ifName to ifIndex mappings. This table makes it easier for the manager to get the ifIndex using the textual name that the user interfaces uses to identify the interface (e.g., eth.1, fr.1)
SEQUENCE OF XsysIfNameIndexEntry
.1.3.6.1.4.1.838.3.1.1.7.1
xsysIfNameIndexEntryA single ifName to ifIndex mapping.
XsysIfNameIndexEntry
.1.3.6.1.4.1.838.3.1.1.7.1.1
xsysIfNameThe value of ifName for the ifEntry with the same ifIndex as xsysIfIndex.
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.7.1.1.1
xsysIfIndexThe value of ifIndex for the interface this entry is associated with.ro
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.838.3.1.1.7.1.1.2
xsysIfStackDisplayTableThis table contains a read-only display of the interface stack in indented format. The first row will correspond to one of the system's physical interfaces. The following rows will be in order of which interfaces are stacked on top of which with blank space at the beginning of the xsysIfStackDisplayString values to show the hierarchy. (Note that several rows may be indented to the same level if they are stacked on top of the same lower-layer interface.) When the top of one stack is reached, the next physical interface will start at the left again.
SEQUENCE OF XsysIfStackDisplayEntry
.1.3.6.1.4.1.838.3.1.1.7.2
xsysIfStackDisplayEntryInformation about one entry in the interface stack.
XsysIfStackDisplayEntry
.1.3.6.1.4.1.838.3.1.1.7.2.1
xsysIfStackDisplayIndexThe row number in the table.
Integer32
.1.3.6.1.4.1.838.3.1.1.7.2.1.1
xsysIfStackDisplayStringThe descriptive string for the entry in the stack table. This string will contain (at least) the ifName of the corresponding interface. The string will start with blank space in order to indent the text so that the resulting table presents an outline view of the interface stack.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.7.2.1.2
xsysHttpd
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1.8
xsysHttpdAdminStatusThe desired state of the web server running on the system. By default, the web server is running but the manager can disable it using this control in order to save memory and/or for security reasons. This object is implementation-dependent and may require a node boot to change the value of xsysHttpdOperStatus.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.8.1
xsysHttpdOperStatusThe actual state of the web server.ro
Enumeration
.1.3.6.1.4.1.838.3.1.1.8.2
xsysHttpdNmsWebServerThe domain name or IP address of the web server that will be referenced in the pages generated by the embedded HTTPD for images, documentation, and other space-consuming data.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.8.3
xsysHttpdNmsWebServerPortThe TCP port being used by the web server identified by xsysHttpdNmsWebServer.rw
Integer32
.1.3.6.1.4.1.838.3.1.1.8.4
xsysTelnetd
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1.9
xsysTelnetdAdminStatusThe desired state of the Telnet server running on the system. By default, the Telnet server is running but the manager can disable it using this control in order to save memory and/or for security reasons. This object is implementation-dependent and may require a node boot to change the value of xsysTelnetOperStatus.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.9.1
xsysTelnetdOperStatusThe actual state of the Telnet server.ro
Enumeration
.1.3.6.1.4.1.838.3.1.1.9.2
xsysDns
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.1.10
xsysDnsDomainThe domain name suffix used when fully qualified domain names are not specified. When no domain suffix is specified, you must use fully qualified domain names. When a domain suffix is specified you may use the host or node name portion of the domain name when referring to domain names within the domain sub-tree (suffix) specified by this object. For example, setting this object to `xedia.com' allows you to refer to the node `barbados.xedia.com' as `barbados'. For those familiar with the UNIX operating system, this object is equivalent to the `domain' keyword in the /etc/resolv.conf file. For example, setting this object to `xedia.com' has the same affect as specifying `domain xedia.com' in your /etc/resolv.conf file. Values of this object must adhere to the rules for domain names specified in RFC 1034 and RFC 1035.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.10.1
xsysDnsAdminStatusThe desired state of the DNS resolver. The DNS resolver is operational by default, but is unable to resolve names or addresses until at least one name server is defined. The DNS resolver can therefore be removed from operation by removing all configured name servers, or by setting this object to `down'.rw
Enumeration
.1.3.6.1.4.1.838.3.1.1.10.2
xsysDnsOperStatusThe actual state of the DNS resolver. `up' indicates that the resolver is able to resolve names and addresses. `down' indicates that the resolver is administratively disabled from resolving names. `noNameServerDefined' indicates that the resolver is up, but is unable to resolve names or addresses because no name servers have been configured.ro
Enumeration
.1.3.6.1.4.1.838.3.1.1.10.3
xsysDnsQueriesThe number of queries sent by the resolver.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.10.4
xsysDnsResponsesThe number of responses returned by name servers.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.10.5
xsysDnsNoErrorResponsesThe number of responses returned by name servers which contained response codes indicating no error.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.10.6
xsysDnsFormattedIllegallyResponsesThe number of responses returned by name servers which contained response codes indicating that the question was formatted illegally.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.10.7
xsysDnsServerFailedResponsesThe number of responses returned by name servers which contained response codes indicating that the server failed to respond.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.10.8
xsysDnsNameDoesNotExistResponsesThe number of responses returned by name servers which contained response codes indicating that the requested name does not exist.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.10.9
xsysDnsServerDoesNotSupportResponsesThe number of responses returned by name servers which contained response codes indicating that the nameserver does not support the requested operation.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.10.10
xsysDnsServerRefusedToAnswerResponsesThe number of responses returned by name servers which contained response codes indicating that the name server refused to answer.ro
Counter32
.1.3.6.1.4.1.838.3.1.1.10.11
xsysDnsNameServerTableTable of safety belt information used by the resolver when it hasn't got any better idea of where to send a query, such as when the resolver is booting or is a stub resolver. Entries created in or deleted from the standard Resolver MIB (RFC 1612) dnsResConfigSbeltTable are also created in or deteted from this table. When creating entries in the dnsResConfigSbeltTable, default values are used for the columns which do not exist in this table. Similarly, modifications to this table are also reflected in the dnsResConfigSbeltTable. The table below shows the relationships between the two tables. dnsResConfigSbeltTable xsysDnsNameServerTable ========================== ========================== INDEX INDEX dnsResConfigSbeltAddr xsysDnsNameServerAddr dnsResConfigSbeltSubTree dnsResConfigSbeltClass dnsResConfigSbeltAddr xsysDnsNameServerAddr dnsResConfigSbeltName DEF_VAL '' dnsResConfigSbeltRecursion DEF_VAL recursive(2) dnsResConfigSbeltPref xsysDnsNameServerPref dnsResConfigSbeltSubTree DEF_VAL '' dnsResConfigSbeltClass DEF_VAL 1 (IN - Internet) dnsResConfigSbeltStatus xsysDnsNameServerStatus
SEQUENCE OF XsysDnsNameServerEntry
.1.3.6.1.4.1.838.3.1.1.10.12
xsysDnsNameServerEntryAn entry in the resolver's Sbelt table. Rows may be created or deleted at any time by the DNS resolver and by SNMP SET requests. Whether the values changed via SNMP are saved in stable storage across `reset' operations is implementation-specific.
XsysDnsNameServerEntry
.1.3.6.1.4.1.838.3.1.1.10.12.1
xsysDnsNameServerAddrThe IP address of the Sbelt name server identified by this row of the table.
IpAddress
.1.3.6.1.4.1.838.3.1.1.10.12.1.1
xsysDnsNameServerPrefThis value identifies the preference for the name server identified in this row of the table. The lower the value, the more desirable the resolver considers this server.rw
INTEGER
.1.3.6.1.4.1.838.3.1.1.10.12.1.2
xsysDnsNameServerStatusRow status column for this row of the Name Server table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.10.12.1.3
xsysDnsCacheTableThis table contains information about all the resource records currently in the resolver's cache. Entries created in or deleted from the standard Resolver MIB (RFC 1612) dnsResCacheRRTable are also created in or deteted from this table.
SEQUENCE OF XsysDnsCacheEntry
.1.3.6.1.4.1.838.3.1.1.10.13
xsysDnsCacheEntryAn entry in the resolvers's cache. Rows may be created only by the resolver. SNMP SET requests may be used to delete rows.
XsysDnsCacheEntry
.1.3.6.1.4.1.838.3.1.1.10.13.1
xsysDnsCacheNameOwner name of the Resource Record in the cache which is identified in this row of the table. As described in RFC-1034, the owner of the record is the domain name were the RR is found.
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.10.13.1.1
xsysDnsCacheClassDNS class of the Resource Record in the cache which is identified in this row of the table. Only class `internet' is supported at this time.
Enumeration
.1.3.6.1.4.1.838.3.1.1.10.13.1.2
xsysDnsCacheTypeDNS type of the Resource Record in the cache which is identified in this row of the table.
Enumeration
.1.3.6.1.4.1.838.3.1.1.10.13.1.3
xsysDnsCacheIndexA value which makes entries in the table unique when the other index values (xsysDnsCacheName, xsysDnsCacheClass, and xsysDnsCacheType) do not provide a unique index.
Integer32
.1.3.6.1.4.1.838.3.1.1.10.13.1.4
xsysDnsCacheTTLTime-To-Live of RR in DNS cache. This is the initial TTL value which was received with the RR when it was originally received, subject to the maximum limit value specified in dnsResCacheMaxTTL.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.10.13.1.5
xsysDnsCacheElapsedTTLElapsed seconds since RR was received.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.10.13.1.6
xsysDnsCacheSourceHost from which RR was received, 0.0.0.0 if unknown.ro
IpAddress
.1.3.6.1.4.1.838.3.1.1.10.13.1.7
xsysDnsCacheDataRDATA portion of a cached RR. The value is in the format defined for the particular DNS class and type of the resource record.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.10.13.1.8
xsysDnsCacheStatusStatus column for the resolver cache table. Since only the agent (DNS resolver) creates rows in this table, the only values that a manager may write to this variable are active(1) and destroy(6).rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.838.3.1.1.10.13.1.9
xsysNotifications
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.2
xsysNotificationPrefix
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.2.0
xsysSystemEventAn SNMP trap definition for carrying Xedia system events. Some events have specific SNMP traps, such as linkUp or linkDown traps. (These are generally events with levels of info(3), warning(4), or fatal(5).) The events which do not have specific SNMP traps defined for them will be sent using this NOTIFICATION-TYPE if xsysEventsAsTraps is set to 'true(1)'.
NOTIFICATION-TYPE
.1.3.6.1.4.1.838.3.1.2.0.1
xsysConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.3
xsysCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.3.1
xsysGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.1.3.2
XEDIA-SYSTEM-MIB - SNMP MIB Reference | MIBs Explorer