Monitoring of Subscriber Intelligence Solutions

You can monitor the following solution in GigaVUE‑FMafter configuring the solution through Ansible:

■   Monitoring Subscriber Aware Metadata Solution
■   Monitoring CUPS Solution

You can monitor the Subscriber-Aware Metadata (SAM) solution in GigaVUE‑FM after configuring the solution through Ansible.

To monitor the Subscriber-Aware Metadata (SAM), follow these steps:

1.   On the left navigation pane, click on .
2. Go to Physical > Orchestrated Flows > Mobility.
3. Select a Site from the SITE drop-down list.
4. Click on a solution alias to view the configuration details of the solution.

You can view any one of following types of SAM solution that is configured:

■   SAM in CUPS solution
o   No engine grouping model
o   Engine grouping model
■   SAM in Non-CUPS solution
o   No engine grouping model
o   Engine grouping model

You can monitor the following information from GigaVUE‑FM:

  • Interface
  • CPN-UPN
  • Forwarding Policies
  • Tool

The screen for SAM in CUPS solution for engine grouping model appears as shown in the figure:

The screen for SAM in Non-CUPS solution for engine grouping model appears as shown in the figure:

You can monitor the CUPS solution in GigaVUE‑FM after configuring the solution through Ansible. You can monitor the following information from GigaVUE‑FM:

  • Interface
  • CPN-UPN
  • Forwarding Policies
  • Tool

To view the CUPS solution, follow these steps:

  1. On the left navigation pane, click on .
  2. Go to Physical > Orchestrate > Mobility.
  3. Select a Site from the SITE drop-down list. If required, you can select multiple sites.

The screen appears as shown in the figure:

GigaVUE‑FM also helps you to view the statistics and health information of the following:

Components Statistics and Health Information for...
CPN-UPN function First level fabric maps
CPN-UPN node GigaSMART Group, SFFP Profile, Exporter, Listener, and IP interface.
Forwarding Policies GSOPS and Second level Map.

To view the statistics and health information, follow these steps:

  1. Go to Physical > Orchestrate > CUPS.
  2. Select a Site from the SITE drop-down list.
  3. Select a component from the GUI.
  4. Click Troubleshoot to view the statistics and health information.

Health Status of Solution

Health Status of a Solution depends on the health status of the CPN and UPN configured in the solution.

The health status of a solution is indicated by the following colors:

Color Health Status of Solution CPN/UPN Node State
Green Healthy -All the CPNs and UPNs health node status are green
Amber Partially Healthy- None of the CPNs/UPNs nodes is red or at least a node is not functioning properly.
Red Unhealthy- At least one None of the CPNs/UPNs node is not functioning properly.

A single CPN's health is based on the health of following components configured in the CPN:

  • Source Ports for CPN
  • First Level Maps
  • GigaSMART (vport, gsgroup and GSOP)
  • Second Level Maps
  • Destination Tools Ports
  • CPN IP Interface

Note:   Only active CPNs are considered in health computation.

A single UPN's health is based on the health of following components configured in the UPN:

  • Source Ports for UPN
  • First Level Maps
  • GigaSmart (vport, Gsgroup and gsop)
  • Second Level Maps
  • DestinationTools Ports
  • UPN IpInterface

Note:  Only Active UPNs are considered in health computation.

The following table explains the health status of a CPN/UPN in GigaVUE‑FM based on the health status of the components configured in the CPN/UPN:

Color UPN Health State
Green Healthy - All the above components of the CPN/UPN are successfully configured.
Amber Partially Healthy-None of the components or any of the CPN/UPN component is not successfully configured.
Red Unhealthy- At least one or any of the configuration status of the CPN/UPN component is not successfully configured.