Interpret Service Impact Incidents

The Service Impact Incidents view in the Incident Browsing workspace displays all of the incidents that have a Correlation Nature of  Service Impact. Service Impact incidents indicate a relationship between incidents in which a network service is affected by other incidents. By default, NNMi generates Service Impact incidents for Router Redundancy Groups. For example, an Interface Down incident can affect a Router Redundancy Group that is part of an HSRP service.

The Service Impact incident helps your troubleshooting efforts by identifying which service is affected.

(NNMi Advanced) As an example of a Service Impact incident and its relationship with other incidents: an Interface Down incident on an interface that is part of a Router Redundancy Group can affect the integrity of a Router Redundancy Group that is part of an HSRP service. To continue the example, A Router Redundancy Group Degraded incident might be the Service Impact incident used to indicate there is a problem with your HSRP service. The Interface Down incident would appear under the Conclusions tab for the Router Redundancy Degraded incident to indicate that it is part of the reason the Router Redundancy Group (and subsequent HSRP service) has become degraded.

NNMi provides the following incidents that have a Correlation Nature of Service Impact:

• Interpret Service Impact Incidents
• Interpret Service Impact Incidents
• Interpret Service Impact Incidents
• No Primary Card in Card Redundancy Group
• Interpret Service Impact Incidents
• No Secondary Card in Card Redundancy Group
• Interpret Service Impact Incidents
• Interpret Service Impact Incidents
• Interpret Service Impact Incidents

NNMi determines the Correlation Nature for an incident.

See Router Redundancy Group View () for more information about Router Redundancy Groups.

Multiple Primary Cards in Card Redundancy Group

A Multiple Primary Cards in Card Redundancy Group incident means NNMi determined multiple primary cards (for example, Card Active) are identified in a Card Redundancy Group.

This incident typically indicates that communication between cards in the group is malfunctioning.

A Multiple Primary Cards in Card Redundancy Group incident has Severity set to Critical.

On the Source Object form, NNMi updates information on the following tabs:

On the Source Node form, NNMi updates information on the following tabs:

On the maps, the icon for the Source Node is set to teal.

When NNMi determines that the group contains one primary card, NNMi updates the following attributes:

• The Card Redundancy Group Status changes to Normal.
• The Card Redundancy Group Conclusion changes to CrgNormal.
• NNMi updates Information in the Correlation Notes attribute and closes the incident.
• The Node Conclusion is CrgNormalInNode.

Multiple Primary Devices in Router Redundancy Group (NNMi Advanced)

A Multiple Primary Devices in Router Redundancy Group incident means NNMi detected multiple primary devices in a Router Redundancy Group (for example, HSRP Active or VRRP Master).

This incident typically indicates that protocol-specific communication between routers in the group is malfunctioning.

A Multiple Primary Devices in Router Redundancy Group incident has Severity set to Critical.

On the Source Object form, NNMi updates information on the following tabs:

When NNMi detects that the group has one primary member, NNMi updates Information in the Correlation Notes attribute and closes the incident.

When NNMi determines that the group has one primary member, NNMi udpates the following attributes:

• The Router Redundancy Group Status changes to Normal.
• The Router Redundancy Group Conclusion changes to RrgOnePrimary.
• NNMi updates Information in the Correlation Notes attribute and closes the incident.

Multiple Secondary Devices in Router Redundancy Group (NNMi Advanced)

A Multiple Secondary Devices in Router Redundancy Group incident means NNMi detected more than one secondary router in a Router Redundancy Group using a Router Redundancy Protocol that does not allow more than one router in a secondary role. That Router Redundancy Protocol has a third designator to indicate routers that are available, but not currently serving as primary or secondary (for example, HSRP Listen).

This incident typically indicates that protocol-specific communication between routers in the group is malfunctioning.

A Multiple Secondary Devices in Router Redundancy Group incident has Severity set to  Critical.

On the Source Object form NNMi updates information on the following tabs:

When NNMi determines that the group has has one secondary member, NNMi closes the incident and changes the Router Redundancy Group Status to Normal. No Conclusion is added.

No Primary Card in Card Redundancy Group

A No Primary Card in Card Redundancy Group incident means NNMi determined no primary card (for example, Card Active) is identified in a Card Redundancy Group.

This typically indicates one of the following: 

• One card, or both cards have an Operational State of Down
• NNMi has identified only secondary cards (for example Card Standby) in the Card Redundancy Group
• Communication between cards in the Card Redundancy Group is malfunctioning

A No Primary Card in Card Redundancy Group incident has Severity set to Critical.

On the Source Object form, NNMi updates information on the following tabs:

On the Source Node form, NNMi updates information on the following tabs:

On the maps, the icon for the Source Node is set to teal.

When NNMi determines that the group contains a primary card, NNMi udpates the following attributes:

• The Card Redundancy Group Status changes to Normal.
• The Card Redundancy Group Conclusion changes to CrgNormal.
• NNMi updates Information in the Correlation Notes attribute and closes the incident.
• The Node Conclusion is CrgNormalInNode.

No Primary Device in Router Redundancy Group (NNMi Advanced)

A No Primary Device in Router Redundancy Group incident means NNMi detected zero primary devices in a Router Redundancy group (for example, zero HSRP Active or VRRP Master).

This typically indicates one of the following:

• Too many routers are down.
• Protocol specific communication between routers in the group is malfunctioning.

A No Primary Device in Router Redundancy Group incident has Severity set to Critical.

On the Source Object form, NNMi updates information on the following tabs:

When NNMi determines that the group has a Primary member, NNMi udpates the following attributes:

• The Router Redundancy Group Status changes to Normal.
• The Router Redundancy Group Conclusion changes to RrgOnePrimary.
• NNMi updates Information in the Correlation Notes attribute and closes the incident.

No Secondary Card in Card Redundancy Group

A No Secondary Card in Card Redundancy Group incident means NNMi determined no secondary card (for example, Card Standby) is identified in a Card Redundancy Group.

This typically indicates the following:

• One of the two cards in the group has an Operational State of Down.
• The other card has been identified as primary (for example, Card Active).
• The Card Redundancy Group is functioning properly.

A No Primary Card in Card Redundancy Group incident has Severity set to Minor.

On the Source Object form, NNMi updates information on the following tabs:

On the Source Node form, NNMi updates information on the following tabs:

On the maps, the icon for the Source Node is set to teal.

When NNMi determines that the group contains a secondary card, NNMi udpates the following attributes:

• The Card Redundancy Group Status changes to Normal.
• The Card Redundancy Group Conclusion changes to CrgNormal.
• NNMi updates Information in the Correlation Notes attribute and closes the incident.
• The Node Conclusion is CrgNormalInNode.

No Secondary Device in Router Redundancy Group (NNMi Advanced)

A No Secondary Device in Router Redundancy Group incident means NNMi detected zero secondary devices in a Router Redundancy Group (for example, zero HSRP Standby or VRRP Backup).

This incident typically indicates the following:

• Protocol-specific communication between routers in the group is malfunctioning.
• The group is routing packets properly because NNMi detected a primary device.

A No Secondary Device in Router Redundancy Group incident has Severity set to Warning.

On the Source Object form, NNMi updates information on the following tabs:

When NNMi determines that the group has a secondary member, NNMi closes the incident and changes the Router Redundancy Group Status to Normal. No Conclusion is added.

Primary Device in Router Redundancy Group Switched (NNMi Advanced)

A Primary Device in Router Redundancy Group Switched incident means NNMi detected that the Primary role moved from one device to another in a Router Redundancy Group.

The group is routing packets properly.

Reasons for this incident include one or more of the following:

• A router or interface in the Router Redundancy Group has gone down.
• A tracked object (interface or IP address) in the Router Redundancy Group has gone down.

When a Primary Device in Router Redundancy Group Switched incident is generated, the Router Redundancy Group maintains its current status.

A Primary Device in Router Redundancy Group Switched incident has Severity set to Critical

On the Source Object form, NNMi updates information on the following tab:.

Router Redundancy Group Degraded (NNMi Advanced)

This incident occurs only in Router Redundancy Groups with more than two routers.

A Router Redundancy Group Degraded incident means NNMi determined the following:

• The Router Redundancy Group still has a primary and secondary device.
• The remaining devices in the group are down or in an unexpected protocol-specific state. For example, in HSRP other member routers should be in Listen state.

Typically, the protocol-specific communication between routers is malfunctioning. However, the group is routing packets properly.

A Router Redundancy Group Degraded incident has Severity set to Warning.

On the Source Object form, NNMi updates information on the following tabs:

When NNMi determines that the group has a active, standby and listen members, NNMi closes the incident and changes the Router Redundancy Group Status to Normal. No Conclusion is added.