Router Redundancy Group Form (NNMi Advanced)

Tenants enable NNMi administrators to partition a network across multiple customers. The NNMi administrator controls the Tenant assignment for each Node. All Nodes in the Router Redundancy Group must be assigned to the same Tenant.

A Tenant is the top-level organization to which a n=Node belongs.

Router Redundancy Group Status reflects the most serious Severity value of the incidents associated with the Router Redundancy Group. Possible values are:

  Normal

 Warning

  Minor

  Major

  Critical

The icons are displayed only in table views.

Table of all of the routers that are members of the selected Router Redundancy Group. The table lists each router's interface that is associated with this Router Redundancy Group. Use this table to access information about each router.

Double-click the row representing a Router Redundancy Member. The Router Redundancy Member Form displays all details about the selected Router Redundancy Member.

Name of the selected router and its associated interface that is a member of the current Router Redundancy Group.

The name includes the fully-qualified DNS hostname assigned to the router and the Name attribute value that NNMi assigned to the interface.

This name appears in the following format:

<fully qualified hostname assigned to the router>[Interface Name:group_number]

For example:  HSRPRouter1.abc.example.com[Se1/1:1]

See Node Form for more information about node names. See Interface Form for more information about interface names.

Boolean attribute used to Indicate whether the selected router owns a Virtual IP Address (if any) for the Router Redundancy Group. See Virtual IP Addresses Form (NNMi Advanced) for more information.

If the selected router uses a Router Redundancy Protocol that does not support virtual addresses, the value is set to false.

The interface that is being used by the router to participate in the Router Redundancy Group.

To find out more information about this Interface:

Click the  Lookup icon and choose one of the following options:

•  Show Analysis to view the Analysis Pane information for the selected interface.
•  Open to open the Interface form.

Name attribute value from the Node Form of the selected router (the Router Redundancy Group member).

To find out more information about the Node:

Click the  Lookup icon and choose one of the following options:

•  Show Analysis to view the Analysis Pane information for the selected interface.
•  Open to open the Node form.

Name of the Router Redundancy Group to which the Router Redundancy Member belongs.

To find out more information about the Router Redundancy Group:

Click the  Lookup icon and choose one of the following options:

•  Show Analysis to view the Analysis Pane information for the selected interface.
•  Open to open the Router Redundancy Group form.

State of the Router Redundancy Member. State values are protocol-specific. For example:

• Hot Standby Router Protocol (HSRP) States: click here.

    Active - Indicates the router is forwarding packets that are sent to the router redundancy group.

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

    Initial - Indicates HSRPHot Standby Router Protocol is not running. This state occurs when an interface first comes up.

    Learn - Indicates the router has not yet determined the virtual IP address. This state occurs when the router is waiting to hear from the active router.

    Listen - Indicates the router knows the virtual IP address, but it is neither the active nor standby router. In this state, the router is waiting for a message from the active and standby routers.

    Speak - Indicates the router knows the virtual IP address. In this state, the router sends periodic messages and is ready to become an active or standby router.

• Virtual Router Redundancy Protocol (VRRP) States: click here.

    Master - Indicates the router is forwarding packets that are sent to the router redundancy group.

    Backup - Indicates the router is a candidate to become the next master router.

    Initialize - Indicates the router is not running VRRP protocol. This state occurs when an interface first comes up.

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.

  Other – The SNMP agent responded with a value for the MIB variable used to determine the Router Redundancy Member State that is not recognized. 

Name of the selected router and its associated interface that is a member of the current Router Redundancy Group.

The name includes the fully-qualified DNS hostname assigned to the router and the Name attribute value that NNMi assigned to the interface.

This name appears in the following format:

<fully qualified hostname assigned to the router>[Interface Name]

For example:  HSRPRouter1.abc.example.com[Se1/1]

Number NNMi uses to rank the tracked object whenever a Current State change occurs. NNMi uses this number indirectly in the calculation to determine the next Primary member of the Router Redundancy Group.

When a tracked object goes down, the priority of the tracked object (Track Priority) is subtracted from its Router Redundancy Member Priority value to produce a smaller member Priority number. If this new Priority number is smaller than one of the other member Priority numbers, the member with the highest Priority value becomes the new Primary router in the Router Redundancy Group.

For example, if an interface that has a Track Priority of 20 goes down on a Router Redundancy Member that has a member Priority of 250:

• The Track Priority (20) is subtracted from its member Priority (250-20=230).
• The new member Priority (230) is then compared to the Priority value of the other members in the Router Redundancy Group.
• If one of the members in the Router Redundancy Group has a higher member Priority, for example, 240, that member becomes the Primary router in the group (for example, HSRP Active or VRRP Master).

Name used to identify the selected Tracked Object. The name includes the fully-qualified DNS name assigned to the Router and the name assigned to its associated Tracked Object .

NNMi determines this Name value.

The name includes the fully-qualified DNS hostname assigned to the router and the Name attribute value that NNMi assigned to the interface.

This name appears in the following format:

<fully qualified hostname assigned to the router>[Interface Name]

For example:  HSRPRouter1.abc.example.com[Se1/1]

See Node Form for more information about node names. See Interface Form for more information about interface names.

To find out more information about this interface: 

Click the  Lookup icon and choose one of the following options:

•  Show Analysis to view the Analysis Pane information for the selected Tracked Object. (See Use the Analysis Pane for more information about the Analysis Pane.
•  Open to open the Interface form.

Number used to rank the tracked object. This number is used indirectly in the calculation that determines the next Active or Master member of the Router Redundancy Group whenever a State change occurs.

When a tracked object goes down, the priority of the tracked object (Track Priority) is subtracted from its Router Redundancy Member Priority value to produce a smaller member Priority number. If this new Priority number is smaller than one of the other member Priority numbers, the member with the highest Priority value becomes the new Master or Active router in the current Router Redundancy Group.

For example, if an interface that has a Track Priority of 20 goes down on a Router Redundancy Member that has a member Priority of 250:

• The Track Priority (20) is subtracted from its member Priority (250-20=230).
• The new member Priority (230) is then compared to the Priority value of the other members in the Router Redundancy Group.
• If one of the members in the Router Redundancy Group has a higher member Priority, for example, 240, that member becomes the Active or Master router in the group.

Virtual IP Addresses

Table view of the virtual IP addresses associated with the selected Router Redundancy Group. The virtual IP address is the IP address protected by this group and used by any router that is actively routing information packets (for example, VRRP Master). For each virtual IP address displayed, you can see the IP address value.

Double-click the row representing a Virtual IP Address. The Virtual IP Addresses Form (NNMi Advanced) displays all details about the selected Virtual IP Address.

Table of the Incidents associated with the selected Router Redundancy Group.

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 Router Redundancy Group.

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

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

Double-click the row representing a Status History. The Router Redundancy Group Status History Form (NNMi Advanced) displays all details about the selected Status.

Overall status for the current Router Redundancy Group. NNMi follows the ISO standard for status classification. Possible values are:

  No Status

  Normal

  Disabled

  Unknown

  Warning

  Minor

  Major

  Critical

The icons are displayed only in table views.

The dynamically generated list of summary statuses for the Router Redundancy Group that contributed to the current overall Status of the selected Router Redundancy Group. Status is set by the Causal Engine.

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 Router Redundancy Group that led up to the Router Redundancy Group's most current Status.

The Status value is correlated based on the most critical Conclusions.

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 Router Redundancy object.

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

Critical Status Conclusions

Major Status Conclusions

Minor Status Conclusions

Warning Status Conclusions

Unknown Status Conclusions

Normal Status Conclusions

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.