Card Form

The name of the card. Sometimes it’s the descriptive string used by the network administrator to name the card. For example, SupIII1000SX, Ether10/100TX, RSM-Mod, and ATM-OC3-Phy.

If the Name value is null, NNMi uses the Component Identifier value (see Card Form: General Tab).

Node in which the card resides. This is the current value in NNMi’s database for the Name attribute of the host device. The value could be a DNS name, a MIB-II sysName, or an address (depending on how your NNMi administrator configured the discovery process).

Click the  Lookup icon and select Show Analysis or  Open to display more information about the node.

Overall status for the current card. NNMi follows the ISO standard for status classification. See the Card Form: Status Tab for more information. Possible values are:

  Normal

  Warning

  Minor

  Major

  Critical

  Disabled 

  Unknown

  No Status

Card status is derived from SNMP polling results for Administrative State, Operational State, and the most serious outstanding conclusion. See the Card Form: Conclusions Tab for information about how the current status was determined. See Watch Status Colors for more information about possible status values.

The calculated Management Mode for the card according to the Management Mode Hierarchy. This value reflects the current management mode of this card's parent object (either the Parent Component card or chassis, or the Managed By node). See How NNMi Assigns the Management Mode to an Object.

(NNMi Advanced - Global Network Management feature) Any change to this Management Mode setting is sent from a Regional Manager to the Global Manager during the next Spiral Discovery cycle on the Regional Manager.

Indicates whether or not NNMi is currently monitoring the card. Possible values are:

Inherited – Used to indicate that the card should inherit the Management Mode from this card's parent object (either the Parent Component card or chassis, or the Managed By node).

  Not Managed – Used to indicate that NNMi does not discover or monitor the card.

Out of Service – Used to indicate the card is unavailable because it is out of service or participating in a Scheduled Node Outage. NNMi does not discover or monitor this card.

NNMi administrators and Level 2 Operators can use the drop-down selection list to change the current setting.

Indicates whether this card participates in a group of cards that provide redundancy protection against card failure.

Either the current card Administrative State value. The NNMi State Poller interprets and normalizes the State value returned for the monitored attribute to handle the differences between vendors. The current Administrative State contributes towards the status calculation for this card. See the Card Form: Status Tab for more information.

Possible values are:

  Up – The SNMP agent responded with a card administrative status value of Up.

  Down – The SNMP agent responded with a card administrative status value of Down.

  Other – The SNMP agent responded with a value for card administrative status that is not recognized.

The following values indicate NNMi could not gather the required data:

  Agent Error – Indicates an error was returned in response to the query.

  No Polling Policy - No polling policy exists for this monitored attribute.

  Not Polled - Indicates that this attribute is intentionally not polled, based on current Monitoring Configuration settings, current Communication Configuration settings, or because the parent Node is set to Not Managed or Out of Service. This object attribute might or might not have an associated polling policy.

  Not Provided — The device does not support providing information for this monitored attribute.

 Unavailable - The agent responded with a value outside the range of possible values or returned a null value.

  Unset – Currently not used by NNMi.

The current card Operational State value.  The NNMi State Poller interprets and normalizes the State value returned for the monitored attribute to handle the differences between vendors. The current Operational State contributes towards the status calculation for this card. See the Card Form: Status Tab for more information.

Possible values are:

 Up – The SNMP agent responded that the card is operationally up, ready to receive and send network traffic.

 Disabled – The card's Administrative State is set to  Down.

  Down – The SNMP agent responded that the card is operationally down.

  Dormant – Indicates the card is in a "pending” state, waiting for some external event.

  Minor Fault – Indicates that the card or one of its hardware components is experiencing a partial failure.

  Not Present – Indicates that the card module is not installed or is missing.

  Other – The SNMP agent responded with a value for card operational status that is not recognized.

  Testing – The SNMP agent responded that the card is in test mode.

  Transient – Indicates the card is in a transient state. For example, rebooting.

  Unknown – The SNMP agent responded with a card operational status value of unknown.

The following values indicate NNMi could not gather the required data:

  Agent Error – Indicates an SNMP error was returned in response to an SNMP query to this agent.

  No Polling Policy - No polling policy exists in Monitoring Configuration settings for this monitored attribute.

  Not Polled - Indicates that this attribute is intentionally not polled, based on current Monitoring Configuration settings, current Communication Configuration settings, current polling policies, or because the parent Node is set to Not Managed or Out of Service

  Unavailable - The SNMP agent responded with a value for card operational status of Not-Specified, so NNMi is unable to determine the State. Other possibilities: the SNMP agent returned a value outside the range of possible values or returned a null value.

  Unset – Currently not used by NNMi.

Either the current MIB-II Standby State value or a value the NNMi State Poller interprets and normalizes to handle differences between vendors. The current Standby State contributes towards the status calculation for this card. See the Card Form: Status Tab for more information.

Possible values are:

  Active - Indicates the card is the active card in the Card Redundancy Group.

  Cold-Standby - Indicates the card is not in use, but is available to take over the role of the active card after it is initialized.

  Hot-Standby - Indicates the card is not in use, but can immediately take over the role of the active card.

  Standby - Indicates the card is a candidate to become the next active card.

  Error - Indicates the card cannot take over the role of active or standby card in the Card Redundancy Group.

  Other – The SNMP agent on the card responded with a value for Standby State of Other or one that is not recognized. 

  Transient – Indicates the card is in a transient state. For example, rebooting.

  Unknown - Indicates the card is unable to report Standby State.

The following values indicate NNMi could not gather the required data:

  Agent Error – Indicates an error was returned in response to the query.

  No Polling Policy - No polling policy exists for this monitored attribute.

  Not Polled - Indicates that this attribute is intentionally not polled, based on current Monitoring Configuration settings, current Communication Configuration settings, or because the parent Node is set to Not Managed or Out of Service. This object attribute might or might not have an associated polling policy.

  Not Provided — The device does not support providing information for this monitored attribute.

 Unavailable - The agent responded with a value outside the range of possible values or returned a null value.

  Unset – Currently not used by NNMi.

(NNMi Advanced - Global Network Management feature) The text you enter here is not sent from a Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global Manager can add notes that are stored in the NNMi database on the Global Manager.

Provided for network operators to use for any additional information about this card that you want to communicate to your team.

Type a maximum of 1024 characters. Alpha-numeric, spaces, and special characters (~ ! @ # $ % ^ & * ( ) _+ -) are permitted.

You can sort your Card table views based on this value. Therefore, you might want to include keywords for this attribute value.

The hardware manufacturer's designator for the card, determined by the vendor. For example:

• cevCat6kWsSup720Base
• wssup720base(1002)
• cat6k-ws-sup720-base

Card serial number, determined by the vendor.

The firmware version or revision for the card, determined by the vendor. For example, 5.4(2).

The hardware version or revision for the card, determined by the vendor. For example, 3.1.

The software version or revision for the card, determined by the vendor. For example, 12.2(33)SXI

The unique value assigned to each Physical Component (card or chassis). The value chosen is always consistent with the Name value assigned to the card's hosted port. For example, the physical index of card hosting port Fa5/1 is 5 and the physical index of card hosting port J8 is J.

If ENTITY-MIB is the only MIB supported for a particular card, this attribute has the same value as the Physical Index attribute.

The description assigned to the card by the operating system of the device in which the card is mounted. Examples:

• WS-X5530 1000BaseSXSupervisor Rev. 1.8
• WS-X5225R 10/100BaseTX Ethernet Rev. 1.1
• HP J4111A 8-port 10/100Base-TX module

Ports

Table of all of the ports associated with the selected card. Use this table to access information about each port associated with the selected card.

Double-click the row representing a Port. The Port Form displays all details about the selected Port.

Table of all of the Physical Component: Cards that are plugged into the selected card. Use this table to access information about each child card associated with the selected parent card.

Double-click the row representing a child Physical Component. The Card Form displays all details about the selected card.

Table of all of the capabilities associated with the selected Card. Use this table to access information about each Capability.

Double-click the row representing a Capability. The Physical Component Capability Form displays all details about the selected Capability.

For more information, see Card Capabilities Provided by NNMi.

Label used to identify the Capability that was added to the Physical Component object.

For more information see the following:

• Card Form: Capabilities Tab shows a list of all available Capabilities for that cards.

Used as a unique identifier for the Capability. Any capability provided by NNMi begins with the prefix com.hp.nnm.capability.

For more information:

• Card Capabilities Provided by NNMi

The actual value for the Custom Attribute for the selected card. Limit 2,000 of any combination of keyboard entries including spaces.

For more information, see Physical Component Custom Attribute Form (Card).

Value assigned to this Custom Attribute for the selected Card object. Limit 2,000 of any combination of keyboard entries including spaces.

For more information, see Card Form: Custom Attributes Tab.

Table view of the fault and performance metrics associated with the current card. You can use this table to determine the Status, Name, and Type for each Physical Sensor metric associated with the selected card.

Double-click the row representing a Physical Sensor. The Physical Sensor Monitored Attribute Form displays all details about the selected Node Sensor.

Table view of fault and performance metrics associated with the current card. You can use this table to determine the Status, Name, and Type for each Node Sensor metric associated with the selected card.

Double-click the row representing a Node Sensor. The Node Sensor Form displays all details about the selected Node Sensor.

Table of the Incidents associated with the selected card.

These Incidents are sorted by creation time so that you can view the Incidents in chronological order. Use this table to determine which Incidents are still open for the selected card.

Double-click the row representing an incident. The Incident Form displays all details about the selected incident.

See Incident Form for more details about the incident attributes that appear in the incident table's column headings.

Overall status for the current card. NNMi follows the ISO standard for status classification. Possible values are:

  No Status

  Normal

  Disabled

  Unknown

  Warning

  Minor

  Major

  Critical

See Watch Status Colors for more information about possible status values.

Physical Component status is derived from SNMP polling results for Administrative State, Operational State, and the most serious outstanding conclusion. For information about how the current status was determined, see the following:

• Card Form: Conclusions Tab
• Chassis Form: Conclusions Tab

The icons are displayed only in table views.

Table of up to the last 30 changes in the status for the Card. This table is useful for obtaining a summary of the Card Status so that you can better determine any patterns in behavior and activity.

Double-click the row representing a Status History. The Physical Component Status History Form (Card) displays all details about the selected Status.

Overall status for the current chassis. See Watch Status Colors for more information about possible status values.

NNMi follows the ISO standard for status classification. Possible values are:

  No Status

  Normal

  Disabled

  Unknown

  Warning

  Minor

  Major

  Critical

Physical Component status is derived from SNMP polling results for Administrative State, Operational State, and the most serious outstanding conclusion.

The icons are displayed only in table views.

For more information see the following:

• Card Form: Status Tab

Date and time indicating when the status was last set.

The table of dynamically generated summary statuses for the card that contributed to the current overall Status of the selected card. Status is set by the Causal EngineThe NNMi Causal Engine analyzes the health of your network and provides the ongoing health status reading for each device. The Causal Engine also extensively evaluates problems and determines the root cause for you, whenever possible, sending incidents to notify you of problems. Any incident generated from a Causal Engine management event has an Origin of NNMi in your incident views..

Each Conclusion listed is outstanding and contributes to the current overall Status.

This table is useful for obtaining a quick summary of the problem description for the current card that led up to the card's most current Status.

Card Status is derived from the most serious outstanding Conclusion and SNMP polling results for Administrative State and Operational State.

Double-click the row representing a Conclusion. The Conclusion form displays all details about the selected Conclusion.

The following table describes the possible Conclusions that might appear for a Card object.

A Y in the Incident? column indicates that the Conclusion results in an incident.

Critical Status Conclusions

Disabled Status Conclusions

Major Status Conclusions

Minor Status Conclusions

Unknown Status Conclusions

Normal Status Conclusions

Status is derived from the most serious outstanding Conclusion and SNMP polling results for Administrative State and Operational State.

The time of the last change in Status.

For more information about each conclusion, see the following:

• Card Form: Conclusions Tab

Created

Date and time the selected object instance was created. NNMi uses the locale of the client and the date and time from the NNMi management server.

This value does not change when a node is rediscovered. This is because the Node object is modified, but not created.

Last Modified

Date the selected object instance was last modified. NNMi uses the locale of the client and the date and time from the NNMi management server.

Note the following:

• When a node is rediscovered, the Last Modified time is the same as the Discovery Completed time. This is because the node’s Discovery State changes from Started to Completed.
• When a Node is initially discovered, the Last Modified time is slightly later than the Created time. This is because node discovery does not complete until after the Node is created.

ID

The Unique Object Identifier, which is unique within the NNMi database.

UUID

The Universally Unique Object Identifier, which is unique across all databases.