Juniper-System-MIB: View SNMP OID List / Download MIB

The MIB objects for managing a Juniper E-series (JUNOSe) system. This MIB complements the ENTITY-MIB.entPhysicalTable by providing the system's physical information in a format that is more user friendly and provides additional elements not found in the Entity MIB, including state information, parameters for configuring the system and additional notifications. There are two families of E-series hardware systems supported by this MIB: ERX - first generation E-series systems ES2 - second generation E-series systems

Report system memory utilization has met the conditions of juniSystemHighMemUtilThreshold. If the memory capacity is greater than 2147483647, a -1 value is returned in juniSystemMemCapacity, and the actual memory capacity in units of 1024 bytes is returned in juniSystemMemKBytesCapacity.

Reports system memory utilization has met the conditions of juniSystemAbatedMemUtilThreshold. If the memory capacity is greater than 2147483647, a -1 value is returned in juniSystemMemCapacity, and the actual memory capacity in units of 1024 bytes is returned in juniSystemMemKBytesCapacity.

Reports a status change for a module. This trap is generated on a transition into a stable state (online or disabled) or on a transition out of online. If redundancy is supported for the module (juniSystemModuleRedundancySupported is true(1)), then the juniSystemModuleSpareServer and juniSystemModuleAssociatedSlot objects are also included in the notification.

Reports a change in the status of a power element.

Reports a transition between the three states of the fan subsystem. When the fan subsystem transitions to the failed state the Thermal Protection hold off time begins.

Reports a change in the temperature status. When the status transitions to the tooHigh state the system enters Thermal Protection mode.

Notification about changes in the state of Thermal Protection. This notification is sent when the tempProtectionStatus changes. It is also sent when the holdOffTimeRemaining is 50% of the holdOffTime.

Notification indicating that a slot or the entire system is about to restart due to a system console reload command. If the reload is only on an individual slot then the following object is included in the notification: juniSystemReloadSlotNumber

Notification indicating that a system resource's utilization has met the conditions of juniSystemUtilizationThresholdDirection. See the DESCRIPTIONs for the juniSystemUtilizationTable elements for details on what conditions trigger a resource utilization notification.

Notification about changes in the status, in case of ISSU upgrade. This notification is sent when the juniSystemIssuState changes. The trap parameter will indicate the current value of the juniSystemIssuState. This notification is supported on the second generation E-series platform family (E320 & E120) from 9.0 release onwards. This object is also supported on ERX-1440 in JUNOSe 9.2 and subsequent system releases.

Notification says that trap raised/cleared is with respect to link sfp's tx-max power threshold

Notification says that trap raised/cleared is with respect to link sfp's tx-min power threshold

Notification says that trap raised/cleared is with respect to link sfp's rx-max power threshold

Notification says that trap raised/cleared is with respect to link sfp's rx-min power threshold

Version identification of currently executing system-wide operational software.

Build date of currently executing system-wide operational software version.

Percentage of memory utilization on the primary system processor. A value of -1 indicates the utilization is unknown.

The total memory capacity in bytes of the primary system processor. If the memory capacity is greater than 2147483647, a -1 value is returned, and the actual memory capacity (in number of bytes divided by 1024) is returned in juniSystemMemKBytesCapacity.

The value of memory utilization in the primary system processor, where, if reached for the first time after a high memory threshold reset, a high memory utilization event notification will be sent to the management entity on this system. A high memory threshold reset occurs when the system is initialized (booted) or the memory utilization falls below the value in juniSystemAbatedMemUtilThreshold. The value of this object must always be greater than the value of juniSystemAbatedMemUtilThreshold.

The value of memory utilization in the primary system processor that is used to determine when to send an abated memory utilization event notification to the management entity on this system. The abated memory utilization event occurs if a high memory threshold reset has not occurred since the last high memory threshold event, and then the memory utilization falls to or below the value of this object. The abated memory utilization event then triggers a high memory threshold reset. The value of this object must always be less than the value of juniSystemHighMemUtilThreshold.

System boot configuration control: file - On a system reboot use the configuration settings specified by the juniSystemBootConfigFile. The juniSystemBootConfigControl and juniSystemBootConfigFile must be specified together in the same set request PDU. fileOnce - On the next system reboot use the configuration settings specified by the juniSystemBootConfigFile. Do not continue to use this file after using it once; on subsequent reboots use the running configuration. The juniSystemBootConfigControl and juniSystemBootConfigFile must be specified together in the same set request PDU. factoryDefaults - On the next system reboot use the factory default settings. On subsequent reboots use the running configuration. runningConfiguration - On a system reboot use the current configuration settings. Enumeration: 'fileOnce': 1, 'runningConfiguration': 3, 'file': 0, 'factoryDefaults': 2.

System boot backup configuration control is used to determine the configuration to be used when the boot logic chooses backup mode: file - On a system reboot in backup mode use the configuration settings specified by the juniSystemBootBackupConfigFile. If this option is specified, juniSystemBootBackupConfigFile, juniSystemBootBackupReleaseFile and this object must be specified together in the same set request PDU. factoryDefaults - On a system reboot in backup mode use the factory default configuration settings. If this option is specified, juniSystemBootBackupReleaseFile and this object must be specified together in the same set request PDU. none - Disallow the boot logic from using the backup release file and configuration (i.e., disable backup mode). Enumeration: 'none': 2, 'file': 0, 'factoryDefaults': 1.

System boot force backup control: off - On the next system reboot do not force the boot logic to choose backup mode. on - On the next system reboot force the boot logic to choose backup mode. Attempting to set this object to on(1) while the juniSystemBootBackupConfigControl is set to none(2) will result in an error. Enumeration: 'on': 1, 'off': 0.

The system boot auto-revert control is used to determine when the boot logic should choose backup mode based of the reboot history: default - Use the default auto-revert tolerances: 3 reboots in 30 minutes. never - Never auto-revert to backup mode. set - Use the auto-revert tolerances specified by juniSystemBootAutoRevertCountTolerance and juniSystemBootAutoRevertTimeTolerance, which must be specified in the same PDU as this object when this value is specified. Enumeration: 'default': 0, 'never': 1, 'set': 2.

The auto-revert reboot count tolerance, used in conjunction with the value of juniSystemBootAutoRevertTimeTolerance when juniSystemBootAutoRevertControl is set to set(2) in the same PDU. For example, if this object is set to 4 and juniSystemBootAutoRevertTimeTolerance is set to 1200, then the boot logic will choose backup mode if 4 system reboots occur within 20 minutes. This object cannot be set to zero, but may contain a zero value when juniSystemBootAutoRevertControl is set to never(1).

The auto-revert reboot time tolerance, used in conjunction with the value of juniSystemBootAutoRevertCountTolerance when juniSystemBootAutoRevertControl is set to set(2) in the same PDU. This object cannot be set to zero, but will contain a zero value when juniSystemBootAutoRevertControl is set to never(1).

The system-wide boot release file name, with extension '.rel'. On a set operation, if there is no file found with the name specified, then an error is returned.

The system-wide boot configuration file name. This object and the juniSystemBootConfigControl object set to file(0) or fileOnce(1) must be specified together in the same set request PDU. If juniSystemBootConfigControl is file(0), only file names with extension '.cnf' are allowed. If juniSystemBootConfigControl is fileOnce(1), only file names with extensions '.cnf' or '.scr' are allowed. On a set operation, if the extension is not appropriate or there is no file found with the name specified, then an error is returned. If juniSystemBootConfigControl is not set to file(0) or fileOnce(1) then a get operation for this object will return a zero-length string.

The system-wide backup boot release file name, with extension '.rel'. A zero-length string indicates that there is no backup release file so the primary release file (juniSystemBootReleaseFile) will be used. On a set operation if there is no file found with the name specified, then an error is returned. The juniSystemBootBackupConfigControl object with a valid value other than none(2) must be specified together with this object in the same set request PDU, and if the juniSystemBootBackupConfigControl is set to file(0) then a valid juniSystemBootBackupConfigFile must also be included in the set request PDU.

The system-wide backup boot configuration file name, with extension '.cnf'. The juniSystemBootBackupReleaseFile object, the juniSystemBootBackupConfigControl object set to file(0), and this object must be specified together in the same set request PDU. On a set operation, if there is no file found with the name specified, then an error is returned. If juniSystemBootBackupConfigControl is not set to file(0) then a get operation for this object will return a zero-length string.

Global control for reverting primary modules back from their active redundant spare modules: off - Disable global reverts of redundant modules. immediate - All redundant module pairs are to revert as soon as the primary module is ready to enter the online state. timeOfDay - All redundant module pairs are to revert at the time specified by juniSystemRevertTimeOfDay, relative to midnight based on the system clock time. This object must be set concurrently with juniSystemRevertTimeOfDay when this value is specified. Note that this only applies to modules that have juniSystemModuleRedundancySupport set to true(1). Enumeration: 'timeOfDay': 2, 'off': 0, 'immediate': 1.

The number of seconds past midnight local time on any given day at which time redundant slot reverts are allowed to occur. This object must be set concurrently with juniSystemRevertControl { timeOfDay }.

Controls the sending of primary system processor memory utilization events. Setting the value of this object to true(1) will cause system memory utilization event notifications, if they occur, to be sent to the management entity on this system. Setting the value of this object to false(2) will disable memory utilization event notifications.

In a juniSystemReloadCommand notification, this object indicates the number of the slot that is being reloaded. Note that slot numbers are zero-based.

The type of resource utilization notification being sent. See the DESCRIPTIONs for the juniSystemUtilizationTable elements for details on what conditions trigger a resource utilization notification. Enumeration: 'falling': 2, 'rising': 1.

Controls the sending of system resource utilization threshold notifications. Setting the value of this object to true(1) will allow resource utilization threshold event notifications, if they occur, to be sent to the management entity on this system. Setting the value of this object to false(2) will disable resource utilization threshold utilization event notifications.

The total memory capacity in kilo-bytes (1024 bytes) of the primary system processor.

interface phy-uid.

represents power tx/rx max/min threshold value of sfp. currently displays 1.0000 for trap raised, 0.0000 for trap cleared

Table of subsystems. A subsystem supports a 'family' of module types; that is, each module type is supported by a particular software subsystem. For example, the ERX channelized T1 line card (CT1-FULL) is supported by the 'ct1' subsystem.

A table entry containing information pertaining to a subsystem. Subsystem information takes precedence over system-wide information, but not over individual module information.

Arbitrary subsystem identification number.

The name of the subsystem.

The boot release file name for this subsystem, with extension '.rel'. If a file name is specified (a non-zero-length string), then this release file takes precedence over the system-wide boot release file (juniSystemBootReleaseFile) just for modules of the type specified by the subsystem name. On a set operation, if there is no file that matches the name specified, then an inconsistentValue error will be returned. Setting this object to a zero-length string deconfigures the subsystem-specific backup release file.

The backup boot release file name for this subsystem, with extension '.rel'. If a file name is specified (a non-zero-length string), then this release file takes precedence over the system-wide boot backup release file (juniSystemBootBackupReleaseFile) just for modules of the type specified by the subsystem name. This object cannot be set unless the system has a backup file, which means that juniSystemBootBackupReleaseFile must contain a file name (a non-zero-length string). On a set operation, if there is no file that matches the name specified, then an inconsistentValue error will be returned. Setting this object to a zero-length string deconfigures the subsystem-specific backup release file.

The highest number assigned to a slot in the system. In a particular hardware model, module slots have fixed numbers assigned to them, even though in some instances there may be no actual slots associated with a particular number. In all cases there is a maximum slot number that will never be exceeded: 2 for ERX-3xx models 6 for ERX-7xx models 13 for ERX-14xx models 16 for E320 models Note that slot numbers are zero-based.

The maximum number of modules and sub-modules (different levels) that can be associated with a slot number in the system. This value is constant for a particular hardware platform family. The number of levels is 2 for a first generation E-series (ERX) platform and is 4 for a second generation E-series platform. For the first generation E-series (ERX) platform family: level 1 - SRP or line card module level 2 - I/O adapter module For the second generation E-series platform family: level 1 - Forwarding module or SRP sub-module level 2 - Switch fabric slice (SFS) sub-module or module level 3 - Bay 0 I/O adapter level 4 - Bay 1 I/O adapter

A table of system module slot physical container configuration information.

A table entry describing the physical status of a system module slot container, which is designated by its slot and level positions. There is an entry in this table for all index pairs from { 0, 1 } to the maximum for each index, { juniSystemMaxSlotNumber, juniSystemMaxModulesPerSlot }, even if there is no corresponding module slot container in the system. A request for an index value outside this range will result in a 'no such' response.

The slot number. The actual upper limit of valid values is juniSystemMaxSlotNumber. Note that slot numbers are zero-based.

The relative position of a module or sub-module 'container' within a slot.

The status of the module slot container. unknown - The existence of a container cannot be determined noSlotContainer - The physical container does not exist empty - No module is present and no configuration information is available for this container moduleNotPresent - A module is configured but it is not currently in its container modulePresent - A module is inserted in the container Enumeration: 'moduleNotPresent': 3, 'unknown': 0, 'modulePresent': 4, 'noSlotContainer': 1, 'empty': 2.

The category of modules that can be configured for the container.

A table of system module and sub-module information. In this table, a module refers to a physical module (board) or a sub-module. A physical board may contain a single module or multiple sub-modules. For example, an ERX line card is a single module and appears as single entry in this table. An I/O adapter is a module that doesn't provide any operaitonal state information and it also appears as a single entry in this table. A second generation E-series SRP/SFS hardware module contains two sub-modules, each with its own operational state information: a System Resource Processor (SRP) sub-module and a Switch Fabric Slice (SFS) sub-module, which appear as two separate entries in this table, one for each sub-module.

A table entry that provides information about a specific system module or sub-module in a particular module location. There are only entries in this table for module locations that report a juniSystemSlotStatus of moduleNotPresent(3) or modulePresent(4).

The current operational status of the module (or sub-module): unknown - The status of the module cannot be determined notPresent - No hardware is currently present but there was a module previously configured in this position (see juniSystemModuleExpectedType); juniSystemModuleCurrentType is unknown(0) disabled - Disable for the reason specified in juniSystemModuleDisableReason hardwareError - Not operational due to a hardware failure booting - In the process of booting initializing - In the process of initialing online - Fully operational standby - In redundant standby mode inactive - In redundant inactive mode notResponding - Unable to communicate with the rest of the system Enumeration: 'hardwareError': 3, 'standby': 7, 'unknown': 0, 'initializing': 5, 'notResponding': 9, 'disabled': 2, 'inactive': 8, 'online': 6, 'booting': 4, 'notPresent': 1.

Indicates the condition causing the module (or sub-module) to be disabled: none - Value when the module is not disabled unknown - Unknown reason for disablement assessing - The module content is being assessed (transient initialization state) admin - The module is administratively disabled typeMismatch - The current module personality conflicts with configuration associated with a different (expected) module personality that previously occupied the slot fabricLimit - Module resource requirements exceed available fabric capacity imageError - Software image for the module is missing or invalid Enumeration: 'none': 0, 'assessing': 2, 'admin': 3, 'unknown': 1, 'typeMismatch': 4, 'fabricLimit': 5, 'imageError': 6.

The value of sysUpTime when the value of juniSystemModuleOperStatus last changed.

The personality of this module based on the combination of modules that are currently inserted in the slot. This could be different from the personality reported in juniSystemModuleExpectedType, in which case it may be necessary to set juniSystemModuleControl for the module in the primary level to 'flush' before the set of modules in this slot can be made operational.

The personality for this module position based on the combination of modules that were inserted in this slot when it was last configured. The value of this object will be different than the value of juniSystemModuleCurrentType when the value of juniSystemModuleOperStatus is disabled(2) and the value of juniSystemModuleDisableReason is typeMismatch(4). After one or more modules is removed from a slot, configuration information associated with the slot (its 'personality') may persist, inhibiting the operation of a different combination of modules in the slot (when new modules are inserted) until juniSystemModuleControl for the slot's primary module is set to flush(1).

Textual description of the expected module in this slot.

The number of slot positions that the expected module spans. Most modules are only one slot wide, but some require extra space or backplane resources. These modules are identified as being in the lower numbered slot and spanning across the higher numbered slot(s).

The number of physical ports supported by the expected module type in this slot.

The serial number of the expected module in this slot. The serial number of the current module may be found in this module's entPhysicalSerialNum. A serial number is for a hardware board, so if there is more than one sub-module on a board, their serial numbers will all be the same.

The part number of the expected module in this slot. The part number of the current module may be found in this module's entPhysicalModelName. A part number is for a hardware board, so if there is more than one sub-module on a board, their part numbers will all be the same.

The revision level of the expected module in this slot. The revision level of the current module may be found in this module's entPhysicalHardwareRev. A revision level is for a hardware board, so if there is more than one sub-module on a board, their revision levels will all be the same.

The entPhysicalIndex value assigned to the module. The ENTITY-MIB.entPhysicalTable contains additional information about this module that can be retrieved using this index. An entPhysicalIndex is for a hardware board, so if there is more than one sub-module on a board, their entPhysicalIndex values will all be the same.

An indicator as to whether this module or sub-module has operational state information that can be managed. If the value of this object is true(1), then there is an entry for this module or sub-module in the juniSystemModuleSoftwareTable.

An indicator as to whether this module or sub-module is part of a redundancy group. If the value of this object is true(1), then there is an entry for this module or sub-module in the juniSystemModuleRedundancyTable.

The number of level positions that the expected module spans. Most modules are only one level 'high', but some require extra space or backplane resources. These modules are identified as being in the lower numbered level and spanning across the higher numbered level(s).

A table of system module software information. This includes the version of the software running on the particular module, the running software's use of the modules resources and the modules operational state. Some module types don't contain loadable software (they execute 'firmware') but include support for some of the objects in this table. For example, the E320 SFS (es2Sfs) modules only support juniSystemModuleAdminStatus and juniSystemModuleControl. Appropriate 'default' values are returned for the other objects. Some module types don't contain any software related information (e.g., ERX I/O adapters do not) in which case their value of juniSystemModuleSoftwareSupport will be false and there will not be a corresponding entry in this table.

A table entry that provides software information about a specific system module in a particular slot location.

Version identification of the currently executing operational software on this module. If the module is in a state where the software version is not known (e.g., module type mismatch), then the value of this object will be a zero-length string.

Last available module CPU utilization percentage. A value of -1 indicates the utilization is unknown. This value is calculated over a 5 second period.

Percentage of module memory utilization. A value of -1 indicates the utilization is unknown.

Provides administrative control to enable/disable the module. This object is read-only for certain types of modules.

Administrative control of this slot: noOperation - Setting this value has no effect. flush - Flushes the configuration associated with a module type that previously occupied this slot. Used to explicitly confirm that the slot is now empty, or contains a different card type. The module must be disabled when this value is asserted. See the description for juniSystemModuleDisableReason. reset - Resets the module. resetBackup - Resets the module using the backup release file. Get operations on this variable always return noOperation. Module types that do not support these operations simply ignore them. Enumeration: 'reset': 2, 'flush': 1, 'resetBackup': 3, 'noOperation': 0.

The boot release file name for this slot, with extension '.rel'. If a file name is specified (not a zero-length string), then this release file takes precedence over the subsystem boot release file (juniSystemSubsystemBootReleaseFile) and the system-wide boot release file (juniSystemBootReleaseFile) for just the module in this slot. Some module types (e.g., ERX SRP modules) don't allow this object to be set. On a set operation, if there is no file that matches the name specified, then an inconsistentValue error will be returned. Setting this object to a zero-length string deconfigures the slot-specific primary release file.

The backup boot release file name for this slot, with extension '.rel'. If a file name is specified (a non-zero-length string), then this release file takes precedence over the subsystem boot backup release file (juniSystemSubsystemBootBackupReleaseFile) and the system-wide boot backup release file (juniSystemBootBackupReleaseFile) for just the module in this slot. This object cannot be set unless the system has a backup file, which mean that juniSystemBootBackupReleaseFile must contain a file name (a non-zero-length string). Some module types (e.g., ERX SRP modules) don't allow this object to be set. On a set operation, if there is no file that matches the name specified, then an inconsistentValue error will be returned. Setting this object to a zero-length string deconfigures the slot-specific backup release file.

Percentage of average CPU utilization for the last five sec for this module. A value of -1 indicates the utilization is unknown.

Percentage of average CPU utilization for the last one minute for this module. A value of -1 indicates the utilization is unknown.

Percentage of average CPU utilization for the last five minutes for this module. A value of -1 indicates the utilization is unknown.

A table of system module redundancy information. Note that modules that do not support redundancy information will not appear in this table.

A table entry that provides information about a specific system module in a particular slot location.

Identifies the redundancy group as derived from hardware settings.

True only if this module is a spare redundant module.

If this module is a primary redundant module, then the module at the same slot level with the slot number identified by this variable is the spare module that serves as this module's backup. If this module is an active spare redundant module, then the module in the slot identified by this variable is the primary module for which this module is the spare. If this module is an inactive spare redundant module, then the value of this object is the slot number of the spare itself (the same value as the first index).

Provides administrative control to enable/disable redundancy protection for the module in this slot.

Per-module control for reverting a primary module back from its active redundant spare module: off - Disable reverting to the primary module. immediate - Revert as soon as this primary module is ready to enter the online state. timeAndDate - Revert to this primary module at time specified by juniSystemModuleRedundancyRevertTime, provided it is in the inactive state. This control only applies to primary modules; spare modules can only be set to off(0). Enumeration: 'timeAndDate': 2, 'off': 0, 'immediate': 1.

The date and time associated with the timeAndDate (delayed) revert operation. Only the local format for DateAndTime is supported. On a set operation, if the time specified is prior to the current time, then an inconsistent value error is returned.This object must be set concurrently with juniSystemModuleRedundancyRevertControl { timeAndDate(2) }.

Table of system physical I/O ports. The information in this table reflects the ports for the expected module type in each slot; in event of a module mismatch, this table permits navigation of the existing configuration of the expected module type.

A table entry describing a physical port of the system.

Port number of this physical port, relative to the slot in which it resides. Each physical port is uniquely distinguished by its slot number, slot level and port number. Port numbers are zero-based.

The ifIndex of the Interfaces MIB ifTable entry corresponding to this physical port; if zero, the ifIndex is unknown or does not exist.

The entPhysicalIndex value assigned to this port. This index may be use to retrieve other information about the port, such as description and type, from the ENTITY-MIB.entPhysicalTable.

The administrative timing source for the system. This variable is used to select the desired timing source to be either primary, secondary or tertiary. Setting this variable will cause the system to change to the specified timing source, provided it is currently available. Setting this value to error(4) is not allowed. The system periodically monitors the status of the three timing sources. If the systems current timing source fails, the system will automatically downgrade to the next timing source. If the system is configured to automatically upgrade (juniSystemTimingAutoUpgrade is set to enable(1)) the system will switch back to the timing source indicated by this variable when it becomes available. A timing source failure can be detected by comparing the operational and administrative timing sources. If they are not equal, the system has swapped timing sources because the administratively set timing source is in the error state.

The operational timing source for the system. The system periodically monitors the status of three timing sources, primary, secondary and tertiary. If the systems current timing source fails, the system will automatically downgrade to the next timing source. If the system is configured to automatically upgrade (juniSystemTimingAutoUpgrade is set to enable(1)) the system will switch back to the higher timing source when it becomes available.

This object controls the automatic timing selector upgrade. Setting this object to disable(0) will prevent automatic upgrade to the next highest timing selector. Setting this object to enable(1) will enable the automatic upgrade of timing selectors.

Table of system timing selectors. This table only contains entries for the primary, secondary and tertiary selecors.

A table entry describing a system timing selector.

The system timing selector index associated with this entry. There are valid indexes for selector types primary(1), secondary(2), tertiary(3).

The system timing source type for this entry. This object must be set to timingInterfaceIfIndex(1) when setting the juniSystemTimingSourceIfIndex object or timingLine(3) when setting the juniSystemTimingSourceLine object. Also, if the value of this object is set to timingInternal(2), no other objects should be set, otherwise the agent will return an error. Enumeration: 'timingLine': 3, 'timingInternal': 2, 'timingInterfaceIfIndex': 1.

The ifIndex of the interface selected as the system timing source. If the juniSystemTimingSourceType object is not timingInterfaceIfIndex(1), then reading this object will return a zero value. The agent will not accept a set to this object unless the juniSystemTimingSourceType object is set to timingInterfaceIfIndex(1).

The line type timing source for this entry. If the juniSystemTimingSourceType object is not timingLine(3), then reading this object will return timingSourceLineUndefined(0). The agent will not accept a set to this object unless the juniSystemTimingSourceType object is set to timingLine(3). Attempting to set this object to timingSourceLineUndefined(0) will always return an inconsistantValue error. Attempting to set this object to a value that is not supported on the type of system running the agent will result in an inconsistantValue error. Enumeration: 'timingSourceLineUndefined': 0, 'timingSourceLineE1PortB': 2, 'timingSourceLineE1PortA': 1, 'timingSourceLineT1PortB': 4, 'timingSourceLineT1PortA': 3.

The status associated with the working (normal) source of this system timing working selector. Enumeration: 'timingStatusUnknown': 3, 'timingStatusOk': 1, 'timingStatusError': 2.

The status associated with the protected (backup) source of this system timing selector. If the system doesn't support protected timing sources, then sourceNotProtected(4) will be returned. Enumeration: 'timingStatusUnknown': 3, 'sourceNotProtected': 4, 'timingStatusOk': 1, 'timingStatusError': 2.

The speed of switching fabric, in gigabits per second.

The fabric revision number. If unknown, a zero-length string is reported.

The number of non-volatile storage (NVS) 'flash' cards in the system.

A table of NVS status information.

A table entry that provides the status information for a NVS flash card.

The index number of the NVS flash card. There is an entry in this table for all values of this index in the range of 1 to the value of juniSystemNvsCount.

The status of non-volatile storage (NVS): notPresent - The SRP or the flash card is not accessible. writeProtected - NVS is write-protected. volumeError - Status poll of NVS failed. nearCapacity - Utilization exceeds 85% of NVS capacity. ok - NVS is fully operational with ample capacity. noConfigSpace - Utilization exceeds the ability to save the running configuration. Enumeration: 'noConfigSpace': 5, 'ok': 4, 'nearCapacity': 3, 'volumeError': 2, 'notPresent': 0, 'writeProtected': 1.

The capacity of NVS storage in megabytes.

The percentage of NVS storage used. A value of -1 indicates NVS utilization is unknown.

The entPhysicalIndex value assigned to this NVS flash card. This index may be use to retrieve other information about the NVS flash card, such as description and type, from the ENTITY-MIB.entPhysicalTable.

The number of power elements in the system.

A table of status variables for the system power elements.

A table entry describing status of a system power element.

The index number of the power element. There is an entry in this table for all values of this index in the range of 1 to the value of juniSystemPowerCount.

The status of the power element: notPresent - The power element is removed from the chassis. inactive - No power is available from this element. good - Power is available from this element. failed - The power element is not working. sensorFailed - The power element sensor has failed. unknown - The status of the power element is not availiable. Enumeration: 'good': 2, 'unknown': 5, 'failed': 3, 'inactive': 1, 'sensorFailed': 4, 'notPresent': 0.

The entPhysicalIndex value assigned to this power element. This index may be use to retrieve other information about the power element, such as description and type, from the ENTITY-MIB.entPhysicalTable.

The maximum number of fan subsystems that may be present in the system. This is a fixed number for each product type.

A table of status of the system's fan subsystems.

A table entry describing status of a fan subsystem.

The index number of the fan subsystem. This is a number in the range of 1 to the value of juniSystemFanCount.

Status of fan subsystem. failed - The fan subsystem has a critical failure, or has been removed, and is now non-operational. ok - All components are operational. warning - The fan subsystem has a non-critical failure. Enumeration: 'failed': 0, 'warning': 2, 'ok': 1.

The entPhysicalIndex value assigned to this fan subsystem. This index may be use to retrieve other information about the fan subsystem, such as description and type, from the ENTITY-MIB.entPhysicalTable.

The maximum number of possible temperature sensors in the system.

A table of status of the system's temperature sensors.

A table entry describing status of a temperature sensor. Sensors are located throughout the system. The ENTITY_MIB.entPhysicalTable provides detailed information about the location of each sensor. The index for a table entry is fixed based on a product-specific algorithm that uses the maximum number of sensors that may be on any module type associated with each of the available slots. This means that entries for sensors associated with empty slots and the 'extra' sensors on modules that have less than the maximum number of sensors for the slot type will have a notPresent status.

An arbitrary number to uniquely identify the temperature sensor.

The status of a temperature sensor: unknown - sensor is not present or is not accessible failed - sensor is broken tooLow - temperature is below nominal range nominal - temperature is within nominal range tooHigh - temperature is above nominal range tooLowWarning - temperature is near the nominal lower limit tooHighWarning - temperature is near the nominal upper limit Enumeration: 'tooLowWarning': 5, 'tooHigh': 4, 'tooHighWarning': 6, 'failed': 1, 'nominal': 3, 'unknown': 0, 'tooLow': 2.

The temperature measured by this sensor in degrees Celsius. This measurement is valid only if the value of the corresponding juniSystemTempStatus is tooLow, nominal or tooHigh.

The entPhysicalIndex value assigned to this temperature sensor. If the temperature sensor is not present this object will return a value of 0. For non-zero values this index may be used to retrieve other information about the temperature sensor from the ENTITY-MIB.entPhysicalTable, such as description and location.

Thermal Protection status: off - No thermal protection. monitoring - Monitoring. inHoldOff - Hold off time has begun. activatedHoldOffExpired - Hold off time has expired; the system is in thermal protection mode. activatedTempTooHigh - The temperature is too high, the system is in thermal protection mode. Enumeration: 'inHoldOff': 2, 'monitoring': 1, 'activatedTempTooHigh': 4, 'off': 0, 'activatedHoldOffExpired': 3.

The time, in seconds, before the system enters Thermal Protection mode after a critical thermal failure is detected.

The time remaining, in seconds, before the system enters Thermal Protection mode while the ThermalProtectionStatus is set to inHoldOff. The value decrements every second until it reaches zero, and the status changes to activatedHoldOffExpired. When ThermalProtectionStatus is not inHoldOff or activatedHoldOffExpired, the value is set to the hold off time.

A table of status of the utilization of system resources. It is an implementation option as to which resources (if any) are supported in this table. It is also an implementation option as to whether the threshold objects are supported for a particular instance.

A table entry describing the status of the utilization of a system resource.

This index identifies a type of enumerated value that is used for the juniSystemUtilizationResourceSubType. See the DESCRIPTION for juniSystemUtilizationResourceSubType for the mapping of Type to SubType enumeration and the corresponding units of measure used for each type of resource. Enumeration: 'interface': 1, 'memory': 2.

This index uses an enumerated value that is different for each value of juniSystemUtilizationResourceType. The following table shows the mapping of Type to SubType enumeration and the corresponding units of measure used for each type of resource. Type SubType Units -----------+-------------------------------+---------------------------- interface Juniper-UNI-IF-MIB.juniIfType number of interfaces memory SNMPv2-TC.StorageType HOST-RESOURCES-MIB.KBytes

This index element identifies the format of the location information so that the juniSystemUtilizationLocation index element can be properly interpreted.

This index is used to specify the resource instance based on its location. Its value is interpreted based on the location type identified by the juniSystemUtilizationLocationType index element.

The maximum number of units of the resource the system can support. See the DESCRIPTION of juniSystemUtilizationResourceSubType for what constitutes a unit of value for this object. Note that for some resources this value may not always be achievable due to other resource constraints.

The current number of units of the resource in the system. See the DESCRIPTION for juniSystemUtilizationResourceSubType for what constitutes a unit of value for this object. Note that some resource types may have instances that do not consume any limited resources and therefore are not included in this count (e.g. IP loopback interfaces do not consume routing resources and therefore don't have a capacity limit, whereas 'external' IP interfaces do).

The threshold value (risingVal), which, in conjunction with juniSystemUtilizationHoldDownTime (holdTime) and juniSystemUtilizationThresholdFalling (fallingVal), is used to decide when to trigger an event indicating that the resource utilization, juniSystemUtilizationCurrentValue (currentVal), is approaching or has reached its maximum capacity, juniSystemUtilizationMaxCapacity (maxVal). See the DESCRIPTION for juniSystemUtilizationResourceSubType for what constitutes a unit of value for this object. The value of fallingVal must be less than the value of this object. This object provides one element in the formula used to determine when to send a utilization notification. If the currentVal rises to equal the risingVal and no other utilization event (either rising or falling) has been triggered within the holdTime, or if the holdTime for a falling threshold notification expires and the currentVal is at or above the risingVal, then and only then is a rising threshold utilization notification sent. The following pseudo-code states the algorithm more precisely. When the resource is created or initialized ( currentVal == 0 ): lastTrapType = none; lastTrapTime = 0; When currentVal increments (increases): if ( currentVal == risingVal && lastTrapTime + holdTime <= currentTime ) { triggerUtilizationTrapRising(); lastTrapType = rising; lastTrapTime = currentTime; } When currentVal decrements (decreases): if ( currentVal == fallingVal && lastTrapTime + holdTime <= currentTime ) { triggerUtilizationTrapFalling(); lastTrapType = falling; lastTrapTime = currentTime; } When the rising threshold value is modified: if ( currentVal < oldRisingVal && currentVal >= newRisingVal && lastTrapTime + holdTime <= currentTime ) triggerUtilizationTrapRising(); lastTrapType = rising; lastTrapTime = currentTime; } When the falling threshold value is modified: if ( currentVal > oldFallingVal && currentVal <= newFallingVal && lastTrapTime + holdTime <= currentTime ) triggerUtilizationTrapFalling(); lastTrapType = falling; lastTrapTime = currentTime; } When a hold-down time expires (lastTrapTime + holdTime == currentTime): switch ( lastTrapType ) { case rising: if ( currentVal <= fallingVal ) { triggerUtilizationTrapFalling(); lastTrapType = falling; lastTrapTime = currentTime; } else { lastTrapType = none; } break; case falling: if ( currentVal >= risingVal ) { triggerUtilizationTrapRising(); lastTrapType = rising; lastTrapTime = currentTime; } else { lastTrapType = none; } break; }

The threshold value (fallingVal), which, in conjunction with juniSystemUtilizationHoldDownTime (holdTime) and juniSystemUtilizationThresholdRising (risingVal), is used to decide when to trigger an event indicating that the resource utilization, juniSystemUtilizationCurrentValue (currentVal), has fallen to or below this level after having exceeded this value. See the DESCRIPTION for juniSystemUtilizationResourceSubType for what constitutes a unit of value for this object. The value of this object must be less than the value of risingVal. This object provides one element in the formula used to determine when to send a utilization notification. If the currentVal falls to equal the fallingVal and no other utilization event (either rising or falling) has been triggered within the holdTime, or if the holdTime for a rising threshold notification expires and the currentVal is at or below the fallingVal, then and only then is a falling threshold utilization notification sent. The pseudo-code in the juniSystemUtilizationThresholdRising DESCRIPTION states the algorithm more precisely.

The hold-down time (holdTime) used in conjunction with juniSystemUtilizationThresholdRising (risingVal) and juniSystemUtilizationThresholdFalling (fallingVal) to decide when to trigger an event indicating that the resource utilization, juniSystemUtilizationCurrentValue (currentVal), has reached or surpassed one of the thresholds. This object provides one element in the formula used to determine when to send a utilization notification. If the resource utilization increases to the rising threshold value but a prior rising or falling utilization event has been triggered within this hold-down time then no rising threshold utilization notification may be sent at that time. If the resource utilization decreases to the falling threshold value but a prior rising or falling utilization event has been triggered within this hold-down time then no falling threshold utilization notification may be sent at that time. However, if the end of a hold-down period for a rising threshold utilization notification is reached and the current value is at or below the falling threshold value, then a falling threshold notification is sent and the hold-down timer is restarted. Likewise, if the end of a hold-down period for a falling threshold utilization notification is reached and the current value is at or above the rising threshold value, then a rising threshold notification is sent and the hold-down timer is restarted. The pseudo-code in the juniSystemUtilizationThresholdRising DESCRIPTION states the algorithm more precisely.

A table of status of the cpu utilization by various tasks.

A table entry describing cpu utilization of a particular task.

A TimeFilter for this task profile entry. Allows GetNext and GetBulk to find task profile rows which have changed since a specified value of sysUptime.

Task name associated with this task profile entry.

Number of times task associated with this task profile entry being invoked.

Rate of invokation for the task associated with this task profile entry.

Total running time for the task associated with this task profile entry.

Percentage running time for the task associated with this task profile entry.

Average running time per invokation for the task associated with this task profile entry.

Utilization in terms of percentage during the five seconds measurement interval for the task associated with this task profile entry.

Utilization in terms of percentage during the one minute measurement interval for the task associated with this task profile entry.

Utilization in terms of percentage during the five minutes measurement interval for the task associated with this task profile entry.

Number of instances consolidated for CPU utilization calculation in this task profile entry.

The state of the system with respect to ISSU upgrade: idle - ISSU is currently idle initializing - ISSU initialization is in-progress initialized - ISSU has successfully initialized upgrading - ISSU is currently upgrading to the new armed release stopping - ISSU is currently in the process of stopping This object is supported on the second generation E-series platform family (E320 & E120) in JUNOSe 9.0 and subsequent system releases. This object is also supported on ERX-1440 in JUNOSe 9.2 and subsequent system releases. Enumeration: 'stopping': 5, 'initialized': 3, 'idle': 1, 'upgrading': 4, 'initializing': 2.

The currently running release file name, with extension '.rel'. The system was booted last time with this release file. This object is supported on the second generation E-series platform family (E320 & E120) in JUNOSe 9.0 and subsequent system releases. This object is also supported on ERX-1440 in JUNOSe 9.2 and subsequent system releases.

The currently armed release file name, with extension '.rel'. The system will be booted with this release file, after ISSU (if it is not aborted). This object is supported on the second generation E-series platform family (E320 & E120) in JUNOSe 9.0 and subsequent system releases. This object is also supported on ERX-1440 in JUNOSe 9.2 and subsequent system releases.

The status of the system with respect to ISSU upgrade. ok - no error or warning found warning - at least one upgrade warning found, upgrade is possible error - at least one upgrade error found, upgrade is not possible This object is supported on the second generation E-series platform family (E320 & E120) in JUNOSe 9.0 and subsequent system releases. This object is also supported on ERX-1440 in JUNOSe 9.2 and subsequent system releases. Enumeration: 'warning': 2, 'ok': 1, 'error': 3.

A Table of criteria for an ISSU initialization. This table will be empty for unsupported platforms. These objects are supported on the second generation E-series platform family (E320 & E120) in JUNOSe 9.0 and subsequent system releases. This object is also supported on ERX-1440 in JUNOSe 9.2 and subsequent system releases.

A table entry describing the criteria for an ISSU initialization.

The index associated with an entry of the system ISSU Criteria Table.

To initialize ISSU, few criteria need to be met. If these criteria were not met, ISSU cannot be initialized. This object provides the criteria details.

To initialize ISSU, few criteria need to be met. If these criteria were not met, ISSU cannot be initialized. This object indicates whether a criteria has met. It will be conditional when that the user can choose to accept the consequences of proceeding with ISSU with non-ideal operating conditions. Enumeration: 'yes': 1, 'conditional': 3, 'no': 2.

Obsolete compliance statement for entities that implement the Juniper E-series System MIB. This statement became obsolete when system resource utilization support was added.

Obsolete compliance statement for entities that implement the Juniper E-series System MIB. This statement became obsolete when the system resource utilization trap enabled and the KByte memory capacilty objects were added.

Obsolete compliance statement for entities that implement the Juniper E-series System MIB. This statement became obsolete when the module level span object was added.

Obsolete compliance statement for entities that implement the Juniper E-series System MIB.

Obsolete compliance statement for entities that implement the Juniper E-series System MIB.

The compliance statement for entities that implement the Juniper E-series System MIB.

The compliance statement for entities that implement the Juniper E-series System MIB.

The compliance statement for entities that implement the Juniper E-series System MIB.

Obsolete collection of management objects providing system-wide software status and control information in a Juniper E-series product. This group became obsolete when the system resource utilization threshold trap enable/disable and the KByte memory capacilty objects were added.

A collection of management objects providing subsystem software control information in a Juniper E-series product.

Obsolete collection of management objects that provide system module information in a Juniper E-series product. This group became obsolete when the module level span object was added.

A collection of management objects providing physical I/O port information in a Juniper E-series product.

A collection of management objects providing system timing source information in a Juniper E-series product.

A collection of management objects providing system fabric information in a Juniper E-series product.

A collection of management objects providing system non-volatile storage (NVS) information in a Juniper E-series product.

A collection of management objects providing system power element information in a Juniper E-series product.

A collection of management objects providing system temperature control information in a Juniper E-series product.

A collection of management objects providing system information for notification in a Juniper E-series product.

Obsolete collection of notifications for system events in a Juniper E-series product. This group became obsolete when the system resource utilization notification was added.

Obsolete collection of management objects providing system resource utilization information and notification control for a Juniper E-series product.

A collection of notifications for system events in a Juniper E-series product.

A collection of management objects providing system-wide software status and control information in a Juniper E-series product.

A collection of management objects that provide system module information in a Juniper E-series product.

A collection of management objects providing system resource utilization information and notification control for a Juniper E-series product.

A collection of management objects that provide system module information in a Juniper E-series product.

A collection of management objects that provide ISSU related information in a Juniper E-series product.

A collection of notifications for system events in a Juniper E-series product.

A collection of notifications for system events in a Juniper E-series product.