Live Pipes and Fault Management

Contents
casp1032
Contents
Live Pipes functionality lets you turn on port status monitoring for individual links and display the status of a link by using status color indicators. A link is a connection between two devices that
CA Spectrum
has resolved to the port level. Live Pipes display a combined condition color from the two resolved ports representing each side of the link.
When a pipe is deleted,
CA Spectrum
removes all of its underlying associations (such as links_with and connects_to). If the pipe being deleted represents more than one link,
CA Spectrum
asks you to confirm the deletion.
Enable or Disable Live Pipes System-Wide
Live Pipes are enabled system-wide by default. Without Live Pipes enabled on a system-wide basis, enabling Live Pipes for individual links is not available.
To enable or disable Live Pipes system-wide
  1. Expand the Live Pipes subview in the VNM model’s Information tab.
  2. Click ‘set’ in the Live Pipes field and select Enabled or Disabled from the drop-down list as desired.
Live Pipes for individual links are disabled by default. All individual pipes are gold or silver until Live Pipes are enabled. When an individual live pipe is enabled, the ok_to_poll (0x11dd8) attribute is set to TRUE for both ports that are involved in the link. The status of the linked ports is monitored if ok_to_poll is TRUE and the port status polling conditions in the Port Status Polling Criteria section are met.
You can enable a live pipe for an individual link.
Follow these steps:
  1. Right-click the link that you want to enable as a live pipe, and select ‘Enable/Disable Live Links.’
  2. Select the check box for the link to enable and click OK.
    The Enable/Disable Live Links dialog closes. The link that you selected is enabled as a live pipe.
Receiving Port Alarms
To receive alarms on a port model, the following conditions must be met:
  • Live Pipes must be enabled system-wide
  • Live Pipes for the link of interest must be enabled separately
If there is no model on the other side of the link, an alarm can still be generated when the status of the link changes by setting a watch on the MIB-II ifOperStatus attribute. When the ifOperStatus attribute returns a value other than 1, an alarm is generated. With this method, an alarm can still be generated even if the port is intentionally down (the ifAdminStatus attribute has been set to OFF).
You can set the default value of ok_to_poll in the MTE for any port model type. When a port connection is made,
CA Spectrum
will set both ports’ ok_to_poll attributes to their MTE default values so that the pipe will automatically become live if the you want. When the connection is removed, the value for ok_to_poll remains at the MTE default value.
When
CA Spectrum
notices a change in the link's status, it will generate one of the events and alarms listed in Port Status Events and Alarms on the two ports involved in the link, and will also change the color of the live pipe to reflect its new status.
Port Status Monitoring Settings
The settings described in the following table let you to control the service of Live Pipes. These settings appear in the VNM model’s Information tab, Live Pipes subview.
Note:
The settings described in this section apply to port status monitoring throughout
CA Spectrum
, not just ports associated with Live Pipes.
  • Live Pipes
    Setting this (global) option to Disabled turns off all pipes in the
    SpectroSERVER
    and no status polling will be performed for any ports associated with a pipe. However, any port which also has the PollPortStatus attribute set to TRUE will still be polled for status changes.
    Attribute ID:
    0x11df9
  • Alarm Linked Ports
    Setting this option to TRUE will cause ports with a good status to have a gray alarm generated on it when linked with a bad or unreachable port.
    Attribute ID:
    0x11fbd
  • Suppress Linked Port Alarms
    Setting this option to TRUE causes ports with a bad status to suppress their red alarms and generate a gray alarm if either the linked port or the connected device is bad or unreachable. Only one port in the link will be alarmed red. The other will be gray.
    Attribute ID:
    0x11fbe
  • Port Always Down Alarm Suppression
    Enabling this option will cause
    CA Spectrum
    to suppress red alarms and assert a gray condition if a port has always been down since first being modeled in
    CA Spectrum
    .
    Attribute ID:
    0x12a03
Any port status alarm will be automatically cleared by
CA Spectrum
if the port's ok_to_poll and PollPortStatus attributes are both set to FALSE.
Monitoring Physical and Logical Connections
CA Spectrum
can monitor the related physical connections of multilink bundles that are resolved to the logical connection via a Live Pipe. When Live Pipes are enabled on the logical connection, the physical ports on one side of the multilink bundle are polled. If Live Pipes are disabled, the polling on the associated physical ports are stopped.
You may need to configure the MultiLinkVirtualIfTypes (0x12e3d) attribute to contain the list of ifType values for multilink bundles for which
CA Spectrum
should also poll the related physical connections. This attribute is pre-configured with the pppMultilinkBundle (108) ifType.
To avoid creating multiple alarms when a single physical connection goes down,
CA Spectrum
only polls the physical connections on one side of the multilink bundle. The side that is polled is determined by reading the Criticality (0x1290c) attribute for the logical connections and choosing the side with the higher value. If the values are equivalent, the connection with the lowest model handle is chosen. Also, the NetworkLinkType (0x12a79) attribute on the physical port models on the side that is polled is set to the same value of the NetworkLinkType attribute of the multilink virtual interface model.
The polling of the non-resolved physical ports on one side of the multilink bundle results in the following alarm behaviors:
  • An alarm is generated on a physical port model whenever a physical connection that is part of a multilink bundle goes down.
  • If the logical connection is down and at least one of the related physical connections is up, an alarm is generated on a multilink virtual interface model.
  • If all of the physical connections are down and the logical connection also goes down, the logical interface is put into the suppressed (grey) state.
The physical ports on the side that is not being polled remain in the green state at all times, unless some other type of monitoring has been enabled on them.
Examples: Monitor Physical and Logical Connections
In the following examples, two devices are connected through a multilink bundle of three pairs of physical port links. “O” represents a physical port and “o” represents a logical interface. Live Pipes are enabled on the logical connection between the multilink bundles. There are physical connections between O1a and O2a, O1b and O2b, and O1c and O2c, but these connections are not resolved in
CA Spectrum
.
When Live Pipes are enabled on the logical connection between the multilink bundles, the three physical ports on Device 1 (O1a, O1b, O1c) are also polled because o1’s Criticality (10) is greater than o2’s Criticality (5).
If the physical connection between O1a and O2a goes down, an alarm is generated on port O1a and port O2a remains green:
SPEC--livepipes_logical_connection_example_1
If all three physical connections are down, alarms are generated on ports O1a, O1b, and O1c, ports O2a, O2b, and O2c remain green, and logical connections o1 and o2 are put into a suppressed state:
spec--livepipes_logical_connction_example_2_OTH