Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

View L3VPN Passive Assurance Monitoring Results

After provisioning an L3VPN service instance in the network, Paragon Automation automatically monitors the health of the service and its related parameters. You can view the health check results and the alerts generated to indicate if any user action is required. The monitoring data is categorized into accordions and each accordion displays related information and alerts generated.

You can view the following accordions for L3VPN service instances:

Note:

KPI-related data may not be displayed in the accordion tables and on the graphs when:

  • There are device errors
  • The data displayed is derived from or is dependent on another KPI which is not being streamed by the devices

View BGP Health Check Results

The BGP accordion displays information about BGP peers and peering session states.

To access the BGP accordion:

  1. Navigate to the Orchestration > Instances > Service Instances page.

  2. Select a service instance and click the service-instance-name hyperlink to access the Service-Instance-Name Details page.

  3. Click the Passive Assurance tab.

  4. Click to expand the BGP accordion.

Table 1 lists the fields in the BGP Neighbors table.

To view health check results for the BGP neighbors, click any hyperlinked entry in the BGP Neighbors table to open the corresponding accordion in the BGP Detail page.

Table 1: Fields in the BGP Neighbors Table

Field

Description

Device Name

Name of the PE device on which the service is provisioned.

Peer Address

IP address of the peer or neighbor PE device in the MPLS network.

Peer State

Current peering session state of the BGP neighbor.

The state of the neighbor:

  • Active—BGP is initiating a transport protocol connection in an attempt to connect to a peer. If the connection is successful, BGP sends an Open message.
  • Connect—BGP is waiting for the transport protocol connection to be completed.
  • Established—The BGP session has been established, and the peers are exchanging update messages.
  • Idle—BGP is waiting for a Start event and is the first stage of a connection.
  • OpenConfirm—BGP has acknowledged receipt of an open message from the peer and is waiting to receive a keepalive or notification message.
  • OpenSent—BGP has sent an open message and is waiting to receive an open message from the peer.

Flap Count

Number of BGP session flaps from the device.

View Health Check Results for BGP Parameters

The BGP Details page displays the health check results for the peering session state and session flap count of BGP neighbors, categorized into accordions. The accordion heading displays the parameter name, alerts generated for the parameter, and a condensed view of the performance graph displaying the health and functioning of the parameter.

To view the health check results in detail, click to expand the corresponding accordion. The accordion displays the performance graph for the peering session state and session flap count of BGP neighbors. For more information about performance graphs, see Performance Graphs to View Passive Assurance Monitoring Data.

Table 2 lists the accordions on the BGP Detail page.
Table 2: Accordions on the BGP Detail Page

Accordion

Description

Peer State

View information and events related to peering session state of the BGP neighbors. The x-axis (horizontal) on the performance graph displays the time range for which information is displayed. The y-axis (vertical) displays the interface. The graph displays a line with the data points related to events that have occurred.

Flap Count

View information and events related to the number of times the BGP session flapped. The x-axis (horizontal) on the performance graph displays the time range for which information is displayed. The y-axis (vertical) displays the number of flaps. The graph displays a line with the data points related to events that have occurred.

View OSPF Health Check Results

The OSPF accordion displays the information about OSPF neighbors related parameters.

To access the OSPF accordion:

  1. Navigate to the Orchestration > Instances > Service Instances page.

  2. Select a service instance and click the service-instance-name hyperlink to access the Service-Instance-Name Details page.

  3. Click the Passive Assurance tab.

  4. Click and expand the OSPF accordion.

Table 3 lists the fields in the OSPF Neighbor State table.

To view health check results for the OSPF neighbors, click any hyperlinked entry in the OSPF Neighbor State table to open the corresponding accordion in the OSPF Details page.

Table 3: Fields in the OSPF Neighbors State Table

Field

Description

Device Name

Name of the PE device on which the service is provisioned.

Instance Name

Name of the service instance configured on the PE device.

Neighbor Address

IP address of the interface that connects the PE device to a CE device.

Interface Name

Name of the interface of the PE device; for example, et-0/0/0.0.

Neighbor State

Displays the current peer session state of the OSPF neighbor.

The state of the neighbor:

  • Attempt—Valid only for neighbors attached to nonbroadcast networks. It indicates that no recent information has been received from the neighbor, but that a more concerted effort must be made to contact the neighbor.

  • Down—Initial state of a neighbor conversation. It indicates that no recent information has been received from the neighbor. Hello packets might continue to be sent to neighbors in the Down state, although at a reduced frequency.

  • Exchange—Routing device is describing its entire LSDB by sending database description packets to the neighbor. Each packet has a sequence number and is explicitly acknowledged.

  • ExStart—First step in creating an adjacency between the two neighboring routing devices. The goal of this step is to determine which routing device is the primary, and to determine the initial sequence number (ISN).

  • Full—Neighboring routing devices are fully adjacent. These adjacencies appear in router link and network link advertisements.

  • Init—A hello packet has recently been sent by the neighbor. However, bidirectional communication has not yet been established with the neighbor. This state might occur, for example, because the routing device did not appear in the neighbor's hello packet.

  • Loading—Link-state request packets are sent to the neighbor to acquire more recent advertisements that have been discovered (but not yet received) in the Exchange state.

  • 2-Way—Communication between the two routing devices is bidirectional. This state has been ensured by the operation of the Hello Protocol. 2-Way is the most advanced state short of beginning adjacency establishment. The (backup) designated router is selected from the set of neighbors in state 2Way or greater.

Neighbor ID

IP address of the CE device.

View Health Check Results for OSPF Parameters

The OSPF Details page displays the health check results for the peering session state of OSPF neighbors. You can view PE device name, interface name, IP address of the CE device, instance name, and IP address of the interface that connects PE device to CE device at the top of the page. The accordion heading displays the parameter name, alerts generated for the parameter, and a condensed view of the performance graph displaying the health and functioning of the parameter.

To view the health check results of a parameter in detail, click and expand the accordion. The accordion displays the performance graph for the OSPF neighbor state. For more information about performance graphs, see Performance Graphs to View Passive Assurance Monitoring Data.

Table 4 lists the accordion on the OSPF Detail page.
Table 4: Accordion on the OSPF Detail Page

Accordion

Description

Neighbor State

View information and events related to the peering session state of OSPF neighbors. The x-axis (horizontal) on the performance graph displays the time range for which information is displayed. The y-axis (vertical) displays the interface. The graph displays a line with the data points related to events that have occurred.

View L3VPN Service Health Check Results

The L3VPN accordion displays the information about L3VPN services.

To access the L3VPN accordion:

  1. Navigate to the Orchestration > Instances > Service Instances page.

  2. Select a service instance and click the service-instance-name hyperlink to access the Service-Instance-Name Details page.

  3. Click the Passive Assurance tab.

  4. Click and expand the L3VPN accordion.

Table 5 lists the fields that are displayed in the L3VPN table.

To view health check results for the L3VPN parameters, click any hyperlinked entry in the L3VPN table to open the corresponding accordion in the L3VPN Detail page.

Table 5: Fields in the L3VPN Table

Field

Description

VPN Network Access ID

Unique ID that you assigned to the site network access or connection between the PE device and the CE device.

VPN State

VPN connection status.

You can view the VPN state for BGP and OSPF neighbors. For static and direct routes, the VPN state is not available.

Device Name

Name of the PE device used on which the L3VPN service is provisioned.

Protocol Used

Name of the protocols used for the L3VPN service between the PE device and the CE device.

Paragon Automation supports the OSPF and BGP routing protocols. For static and direct routes, the value is blank.

Neighbor Session

Peering session state of the neighbors.

A session is formed between neighbors with the same AS in a network. A routing protocol such as BGP, OSPF runs between the established session to exchange routes.

Interface Name

Name of the interface on the PE device that connects to the CE device; for example, ge-0/0/0.

Instance IFL No

Logical interface instance of a PE device; for example, 100.

Interface Status

Status of the logical interface of a PE device.

Routing Instance Name

Name of the routing instance configured on the PE device.

View Health Check Results for L3VPN Parameters

The L3VPN Details page displays the health check results of the L3VPN parameters, categorized into accordions. You can view the name of the PE device on which service is provisioned. The accordion heading displays the parameter name, alerts generated for the parameter, and a condensed view of the performance graph displaying the health and functioning of the parameter.

To view the health check results of an interface parameter in detail, click to expand the corresponding accordion. The accordion displays the performance graph for the parameter. For more information about performance graphs, see Performance Graphs to View Passive Assurance Monitoring Data.

Table 6 lists the accordions on the L3VPN Detail page.
Table 6: Accordions on the L3VPN Detail Page

Accordion

Description

VPN State

View information and events related to the VPN state of the BGP or OSPF neighbors. For static and direct routes, the VPN State is not available. The x-axis (horizontal) on the performance graph displays the time range for which information is displayed. The y-axis (vertical) displays the VPN state. The graph displays a line with the data points related to events that have occurred.

Interface Status

View information and events related to the status of the interface from a PE device. The x-axis (horizontal) on the performance graph displays the time range for which information is displayed. The y-axis (vertical) displays the interface status. The graph displays a line with the data points related to events that have occurred.