ZHONE-CARD-RESOURCES-MIB: View SNMP OID List / Download MIB

A table of unit/card status and functions for each card in A BAN system. Functions include software download management. The maximum cards in a BAN is 255 shelves x 17 cards per shelf, a typical configuration will consist of several hundred cards. A single card system will use shelf/slot index of 1,1 and will not be identifiable as a single card system based on the shelf, slot indices.

An entry per card or a singe row for a single CPU/card system.

Textual description of the unit/card or access device type.

The numerical representation of what unit/card type is present.

The manufacturing serial number for this unit/card.

CLEI code for the unit/card if defined, otherwise the value will be set to zero (0) by the card.

Manufacturing hardware revision code for the unit/card.

Revision level of any permenant (PROM) or semi- permenant (flash) code on the unit/card. This code is generally used as a bootstrap loader.

Results string generated by unit/card that displays the results of the POST (power-on-self-test). The first item in the text string indicates the overall results of the test. 'Pass' or 'Fail'. The reminder of the string enumerates the results of each test which will vary by unit/card type or may only enumerate failed tests.

Specifies the adminstrative status of the unit/card as follows: operational: the unit/card enters the operational state if able. In the operational state the unit/card is able to accept requests from other elements in the BAN or if a standalone device is processing requests from the WAN or local interfaces. disable: the unit/card ceases to accept requests from other elements. If the unit/card is operational and recieves this command it will complete processing of open requests if able. maintenance: enter a special maintenance state if available - if not available enter the disabled state and set adminStatus to disabled. warmreset - perform a warm reset of system software that does not reinitialize or reset hardware resources. reset - perform an immediate full reset, following a successful reset the unit/card should enter the operational state. Enumeration: 'reset': 5, 'warmreset': 4, 'disable': 2, 'maintenance': 3, 'operational': 1.

Indicates the operational status of the unit/card as follows: unknown: the card is in an unknown or error state operating: software has been loaded and is operating, the unit/card is accepting requests from other system elements or if a standalone unit it is processing requests form the WAN or local interfaces. non-operating: unit/card is not operating due to internal errors or it has been disabled by the management system. maintenance: the unit/card is in the maintenance state. Enumeration: 'unknown': 1, 'nonoperating': 3, 'operating': 2, 'maintenance': 4.

Enable the collection and forwarding of historical statistics on the unit/card. The default value is disabled. Note this value should be logically 'anded' with the the system statistics enbale to determine if the collection and forwarding of statistics should actually be enabled. Default value is 'disabled'. Enumeration: 'enable': 1, 'disable': 2.

The amount of time since this unit/card was last initialized (warm or full reset). The units are in 100ths of a second.

A string is returned that describes the processor type used on the unit/card.

Summary of the status of all physical ports on the unit/card. Each port is identified by it's ifTable index and the status is indicated as up|down|unknown.

This field is used to identify which interface types are s upported for a given card. In the case where a card has exactly one possible interface (such as the ethernet card) this field is exactly the same as the cardResourceCardType field. For polymorphic trunk cards this field reflects the interface card type which is installed.

This field is used to configure the resources for AAL2 for both high and low priority interfaces as the percentage of total available resources. Remainder of the resources would be used for AAL5.This field will be used if cardAtmConfiguration is entered as manual. This variable is not supported in this release.

This field is used to configure the resources for high priorty AAL2 interface as the percentage of total bandwidth allocated for AAL2. This field will be used if cardAtmConfiguration is entered as manual. This variable is not supported in this release.

DEPRECATED - use zhoneSysCardLineVoltage Specifies the voltage supplied to all lines(ports) of this card. Used on ISDN line cards. Enumeration: 'line-voltage-68-volts': 3, 'line-voltage-100-volts': 5, 'line-voltage-95-volts': 4, 'line-voltage-not-used': 1, 'line-voltage-60-volts': 2, 'line-voltage-110-volts': 6.

DEPRECATED - use zhoneSysCardVpiVciRange. The maximum vpi and vci values that may be used for this card. Enumeration: 'vpivci-range-not-applicable': 1, 'vpivci-range-vpi-15-vci-63': 2, 'vpivci-range-vpi-7-vci-127': 3.

Describes PWE timing origin and mode of timing recovery: none - no reference clock required, or PWE not supported. source-differential - the local Provider Edge (PE) device supplies the reference signal for differential recovery. source-adaptive - the local PE device participates in the adaptive clock recovery scheme. remote-differential - the remote PE device supplies the reference signal for differential recovery. remote-adaptive - the local PE device participates in the adaptive clock recovery scheme. Enumeration: 'remote-adaptive': 5, 'none': 1, 'remote-differential': 4, 'source-differential': 2, 'source-adaptive': 3.

Information about the software running on this unit(system) or card.

A augmented table of the unit resource table specific for software information.

The software version that is currently running on this card. This object complies to the Zhone software revision syntax.

If warm upgrade is supported, this is the version of software that is loaded on the card that will be switched to with a warm upgrade. This value is set by the card sw after a loadUpgradeSoftware command is completed successfully.

Some items are only valid if warm upgrade is supported. loadUpgradeSoftware: the unit/card should request a load of the upgrade software from the previously downloaded on to the system. If an upgrade version of software is not available or the server(s) is unable to respond to the load request the card will set the cardSwStaus to upgradeloadFailed (warm upgrade only - this is ignored if warm upgrade is not supported). upgradeNow: the unit/card should upgrade to the already loaded upgrade software if warm upgrade is supported or reboot and load the upgrade software if warm upgrade is not supported. If the upgrade software has not been loaded or there is no grade software load available, the unit/card will set the cardSwStatus to upgradeFailed. When this value is set, the zhoneSysCardSwUpgradeEnable field is set to true in the genSystem mib associated with this card. upgradeOnReset: the unit/card will upgrade to the already loaded software the next time it is initialized. If the upgrade software is not loaded the card will set the cardSwStatus to upgradeFailed following reset. reloadCurrVers: the will re-initialize and load the previous version of code prior to the upgrade (which is either the 'specific' version or default version of software depending upon what has been provisioned) See the genSystem mib for details. When this value is set, the zhoneSysCardSwUpgradeEnable field is set to false. Enumeration: 'loadUpgradeSw': 1, 'reloadCurrRev': 4, 'upgradeOnReset': 3, 'upgradeNow': 2.

The upgrade status is indicated as follows: upgradeLoadSuccessful: following the setting of cardSwAdmin to loadUpgradeSw this status indicates the load to memory or storage was successful. loadingSw: the unit/card is loading upgrade software from the internal software load service (warm upgrade only). upgrading: the unit/card is in the process of switching to the upgrade software (warm upgrade only). upgradeLoadFailed: the upgrade version software load was not able to complete due to an error or the unit has determined the downloaded software to be invalid. upgradeFailed: the upgrade was not able to complete due a load error, invalid version loaded or upgrade software was loaded and unable to initialize. The unit/card has reverted to the 'current' version of software. upgradeImageNotAvail - The upgrade image is not available on this system. pendingUpgradeOnReset : The unit/card needs a reboot to upgrade to the already loaded software . upgradeNotRequested : The upgrade image is available on the system but the cardSwAdmin is not set to perform upgrade. Enumeration: 'upgradeImageNotAvail': 6, 'upgradeLoadFailed': 4, 'pendingUpgradeOnReset': 7, 'upgradeNotRequested': 8, 'upgrading': 3, 'loadingSw': 2, 'upgradeFailed': 5, 'upgradeLoadSuccessful': 1.

Augment table of the unit/card resource but specific to the runtime status information.

A row definition for the runtime software state/status.

The maximum physical memory that has been allocated at any time by the unit/card.

The amount of physical memory that is unallocated and not in use by the unit/card.

The amount of physical memory contained by the unit/card.

Percentage of time the CPU has spent executing tasks with priority of 200 or less. Tasks with priority of 200 or less (the higher the number, the lower the priority) are considered idle tasks.

Percentage of time the CPU has spent executing tasks with priority of 199 or higher.

Memory status of the card sent with memory trap. A trap is sent when each condition occurs. 1 - ramMemOK less then 90% of ram is used 2 - ramMemLow more then 90% of ram is used 3 - flashMemOK enough flash for maximum database 4 - flashMemLow not enough flash for maximum database 5 - flashMemOut no more flash memory, data no longer persistent Enumeration: 'flashMemOut': 5, 'ramMemOK': 1, 'flashMemLow': 4, 'ramMemLow': 2, 'flashMemOK': 3.

Percentage of time the CPU has spent executing tasks with priority of 001 to 099.

Percentage of time the CPU has spent executing tasks with priority of 100 to 179.

Percentage of time the CPU has spent executing tasks with priority of 180 to 199.

Percentage of time the CPU has spent executing tasks with priority of 200 to 250.

This contains the table of services configured to be running on this card. The card runs services that are either customer visible (can be configured by the user) or those that the customer can select which card to be run on. This table lists all services running on this card but only those services customer viewable can be modified. This table is only supported on multi-card systems (i.e. BAN).

A row in this table represents a redundant service that is running on this card.

Identifies the service. The Servide ID, together with a Service Instance, uniquely identify a service running on a particular card.

The instance of this service that is running on the card. For example, if multiple versions of a service is running, this will be the differentiator. In the case of routing domains, this would be the rdIndex. In most cases this value is 0 which is allowed even though this field is used as an INDEX.

Represents the time that service entered the current cardServiceStatus. Value is in system ticks.

The status for this particular service instance. The possible values are: unAvailable (1) - The service is unavailable for unknown reasons. This is an error situation. This value may not be supported by the device. inActive (2) - This service instance is waiting in line to become standby. There may be 0 or more services of this type in this state. standBy (3) - Next in line to become active if the current active service should fail. If there's more than one service instance running, there will be one instance in standby mode. active (4) - The current active service performing this function. Enumeration: 'standBy': 3, 'active': 4, 'inActive': 2, 'unAvailable': 1.

The table of active services running on the system

A row in this table represents an active service running on a card.

Identifies the shelf where the active service is running.

Identifies the slot where the active service is running.

Represents the time that service became Active. Value is in system ticks.

The table of standby services running on the system

A row in this table represents a standby service running on a card..

Identifies the shelf where the standby service is running.

Identifies the slot where the standby service is running.

Represents the time that service became Standby. Value is in system ticks.

Traps related to Card Services

This object identity adds a zero(0) for the next to last sub-identifier which should be used for new SNMPv2 Traps.

This trap is generated whenever a redundancy state change occurs.

This trap indicates that all services on the standby card are synchronized with their active couterparts, and that the card is fully ready as the standby.

The following defines the information pertinent for external relays.

A Table of External Relay Interface status for handling relays on a card and for the TAC card,this is of 12 Rows.

One entry for each relay on a card.

A provisionable name which may used in referring to an external relay. This external relay name should be unique on the box.If not set , it defaults to a unique value where x=shelf number, y=slot , and z=relayId.

The object describes the state of the external relays. An external relay may have one of two states: relayStateOpen(1) indicates that the external relay is open or is not connected. relayStateClosed(2) indicates that the external relay is closed. Enumeration: 'relayStateOpen': 1, 'relayStateClosed': 2.

Specifies whether relay is normally open or normally closed. The other state will then generate an alarm. A value of not-specified is valid for MTAC and 1U cards, where alarms are not present in the central alarm manager. For the mxk i/o alarm board relays, a value should be present for all relays that are in use. Enumeration: 'normallyOpen': 2, 'normallyClosed': 3, 'notSpecified': 1.

This table is used to map an external relay name to the relay Id. This table contains all entries for relays defined in the system. For example, if 2 TAC cards are present there will be 24 entries in this table.

One row for each relay.

A numeric identifier which identifies the relay.

Traps defined for the external relays.

In order to make this a v2 trap (0).

This trap is thrown when the state of an external TAC card relay changes.

This trap is thrown when the state of an MXK I/O Alarm Card relay changes.

Description.

This group contains objects associated with the zhone external relay interface.

This group contains trap definitions associated with the external relays.

Memory Trap

Memory trap

Memory notification

Notification sent when CPU Usage crosses a predetermined threshold value.

Description. The following defines the information pertinent for ZRG boards.

Description. The object describes the state of the ZRG board power supply. The power may have one or two states from the following states: normalMode(0) indicates that the load is receiving power from commercial power batteryON(1) indicates that the load is receiving power from battery. batteryLOW(2) indicates that the battery has been reduced to the point that roughly 20% of the available runtime is available. batteryBAD(3) indicates that the battery has failed it's periodic test. The battery should be replaced as system availability has been compromised. batteryGone(4) indicates that the battery is disconnected. Load will not be supported if the commercial power fails. noUPS(5) indicates that the UPS unit is disconnected. Load will not be supported if the commercial power fails. Bits: 'batteryON': 1, 'batteryBAD': 3, 'noUPS': 5, 'normalMode': 0, 'batteryLOW': 2, 'batteryGone': 4.

Traps defined for the ZRG power source/state.

In order to make this a v2 trap (0).

Description.

ZNID Resources.

ZNID Battery Status object used for notification reporting. Bits: 'batteryPowerLow': 2, 'normal': 0, 'noUPS': 5, 'onBatteryPower': 1, 'replaceBattery': 3, 'batteryRemoved': 4.

ZNID Battery Status object used for notification reporting.

ZNID notification objects.

ZNID notifications.

ZNID battery status notification.

ZNID notification group.

ZNID object group.

Contains the resources utilized on a per CPU basis. Note that in a single cpu system, this data represents the entire system.