View Maintenance Reports

Tasks You Can Perform

You can perform the following tasks on individual report page:

View details about individual reports.
- Link Oversubscription, see Table 1.
- Link Utilization Changes, see Table 2.
- LSP Path Changes, see Table 3.
- Maintenance Simulation, see Table 4.
- Path Delay, see Table 5.
- Peak Interface Utilization, see Table 6.
- Peak Link Utilization, see Table 7.
- Peak Simulation Summary, see Table 8.
- Peak Tunnel Failure, see Table 9.
Download the report—Hover over the Download button and select a format, CSV or JSON, to export the detailed maintenance report.
Show/Hide Columns—Choose to show or hide a specific column in the table.

Hover over the More Options (vertical ellipsis) > Show/Hide Columns and select the Column-Name check box of the columns you want to display on the page.

Link Oversubscription Report

If link oversubscription does not occur for the maintenance events, the report will be empty.

Table 1 describes the fields on the Link Oversubscription Page.

Table 1: Fields on the Link Oversubscription Page
Field	Description
Simulation Type	Type of exhaustive maintenance simulation. It can be Node, Link, SRLG, or a combination of the three types.
Event	Name of the network element under maintenance. It can be node name, link name or facility (SRLG) name.
Layer	Type of Layer—Demand or Tunnel.
Link Name	Name of the link.
Node A	Name or IP address of Node A (ingress node).
Interface	Name of interface A.
Node Z	Name or IP address of Node Z (egress node).
Change	Change in the link bandwidth (in bps).
Bandwidth	Bandwidth (in bps) of the link.
Used Bandwidth	Bandwidth (in bps) allocated for tunnels resulting from the specified maintenance event simulation.

Link Utilization Changes Report

Table 2 describes the fields on the Link Utilization Changes Page.

Table 2: Fields on the Link Utilization Changes Page
Field	Description
Link Name	Name of the link.
Node:Interface	Node and interface name of the local node.
Remote Node	Name of the node at the remote end.
Change	Change made to the link. Link Down is displayed when the link is under maintenance. If there is a change in link utilization, this field will be empty.
Bandwidth	Total bandwidth (in bps) available for traffic.
New Utilization	Percentage value of new link utilization. Range is between 0 and 1. For example, 0.8 implies 80% link utilization.
Utilization	Percentage value of original link utilization. Range is between 0 and 1. If the link is under maintenance, this field will be empty.
Difference	Difference between the new and original link utilization.

LSP Path Changes Report

Table 3 describes the fields on the LSP Path Changes page.

Table 3: Fields on the LSP Path Changes Page
Field	Description
LSP Name	Name of the LSP.
Node A	Name of Node A (ingress node).
Node Z	Name of Node Z (egress node).
Hop Count	Original hop count of the LSP.
New Hop Count	New hop count of the LSP resulting from the specified maintenance event simulation.
Path Cost	An integer value for the cost associated with the original LSP path. When an LSP is routed over multiple links, path cost is the cumulative value of all individual link costs that the LSP goes through.
New Path Cost	An integer value for the cost associated with the new (rerouted) LSP path.
Path	Displays the IP addresses that the original LSP goes through from Node A.
New Path	Displays the IP addresses that the new (rerouted) LSP goes through from Node A.
Protection	Displays the name of the standby or secondary path associated with the LSP, if any.
Delay	Delay (in milliseconds) associated with the original LSP. When an LSP is routed over multiple links, delay is the cumulative value of all individual link delays that the LSP goes through.
New Delay	Delay (in milliseconds) associated with the new (rerouted) LSP.
Delay Change	Percentage increase or decrease in the delay. It is calculated by: `(Delay-New Delay/Delay)*100`.
Bandwidth	Bandwidth (in bps) of the LSP.
New Bandwidth	Bandwidth (in bps) after the LSP is rerouted.
Type	Type of LSP (delegated or device controlled).

Maintenance Simulation Report

Table 4 describes the fields on Maintenance Simulation Page.

Table 4: Fields on the Maintenance Simulation Page
Field	Description
Event ID	Name of the maintenance event.
Status	Status of the maintenance event execution— Completed-Pass or Completed-Fail (execution is completed but with errors).
Simulation Time	Time when you click on Simulate on the maintenance tab of the network information table.
Fail Count	Total number of path routing failures that occurred during the maintenance event simulation.
Oversubscription Count	Total number of links where oversubscription (more than 100%) occurred during maintenance event simulation.
Simulation Type	Type of exhaustive maintenance simulation. It can be Node, Link, SRLG, or a combination of the three types.

Path Delay Report

Table 5 describes the fields on the Path Delay page.

Table 5: Fields on the Path Delay Page
Field	Description
Path Name	Name of the path.
From	Name of the ingress node.
To	Name of the egress node.
Bandwidth	Bandwidth (in bps) associated with the path.
Priority	Priority for the path traffic. Range 1 through 7.
Path	Displays the IP addresses that the LSP goes through.
Distance	Total path distance. Note: 0 indicates that path was not rerouted during the simulation.
Delay	Propagation delay of the path in normal mode.
Fail Count	Number of times this path was disconnected during the maintenance event failure simulation.
Worst Distance	Worst path distance of the alternate routes that occurred during the maintenance event failure simulation.
Worst Delay	Worst propagation delay of the alternate routes that occurred during the maintenance event failure simulation.
Worst Delay Cause	Cause of the worst delay during the maintenance event simulation. It can be due to one of the following: NDFAIL (node failure) LINKFAIL (link failure) FACFAIL (facility failure) SIMPLACE (alias for element that is put under maintenance)
Delay Cause Event	Network element that caused the worst delay during the maintenance event simulation. It can caused by a node, a link (From and To nodes are displayed), or a facility.

Peak Interface Utilization Report

Table 6 describes fields on the Peak Interface Utilization page.

Table 6: Fields on the Peak Interface Utilization Page
Field	Description
Node:Interface	Name of the node and interface associated with the interface.
Link Count	Number of links associated with the interface.
Bandwidth	Total bandwidth (in bps) available for the user traffic.
Used Bandwidth	Bandwidth (in bps) used by tunnels in normal mode.
Peak Bandwidth	Maximum bandwidth (in percentage) used by tunnels during the maintenance event failure simulation. For example, 5 implies 50% utilization.
Utilization	Bandwidth utilization (in percentage). It is calculated as 100*(UsedBandwidth/TotalBandwidth).
Peak Utilization	Peak bandwidth utilization (in percentage). It is calculated as 100*(PeakBandwidth/TotalBandwidth).
Tunnel Count	Number of tunnels carried by the link in normal mode.
Peak Tunnel Count	Maximum number of tunnels carried by the link during the maintenance event failure simulation.
Worst Load Cause	Cause of the worst load (bandwidth utilization) during the maintenance event simulation. It can be due to one of the following: NDFAIL (node failure) LINKFAIL (link failure) FACFAIL (facility failure) SIMPLACE (alias for element that is put under maintenance)
Load Cause Event	Network element that caused the worst load during the maintenance event simulation. It can be caused by a node, a link (From and To nodes are displayed), or a facility.
Worst Tunnel Cause	Cause of the worst (or increased) tunnel count during the maintenance event simulation. It can be due to one of the following: NDFAIL (node failure) LINKFAIL (link failure) FACFAIL (facility failure) SIMPLACE (alias for element that is put under maintenance)
Tunnel Cause Event	Network element that caused the worst tunnel count during the maintenance event simulation. It can be caused by a node, a link (From and To nodes are displayed), or a facility.

Peak Link Utilization Report

Table 7 describes the fields on Peak Link Utilization page.

Table 7: Fields on the Peak Link Utilization Page
Field	Description
Link Name	Name of the link.
Node A:Interface	ID of node and associated interface for node A where the link originates.
Loc A	Name of the source node where the link originates (ingress).
Node Z:Interface	ID of node and associated interface for node Z where the link terminates (egress).
Loc Z	Name of the node at Z end (egress).
Vdr	The vendor associated with this link. Possible values for vendors include those that are specific to a certain country or region, and are listed in the tariff database. If a vendor is not specified, this value is set to the default value DEF.
Link Type	The type of link being used. The trunk type is subsequently used in determining link pricing and bandwidth availability.
Bandwidth	Total bandwidth (in bps) available for the user traffic (between node A and Z).
Used Bandwidth	Bandwidth (in bps) used by tunnels in normal mode on this interface.
Peak Bandwidth	Maximum bandwidth (in bps) used by tunnels during the maintenance event failure simulation (between node A and Z).
Utilization	Bandwidth utilization (in percentage). It is calculated as per the following formula: 100*(UsedBandwidth/TotalBandwidth)
Peak Utilization	Peak bandwidth utilization (in percentage). It is calculated as per the following formula: 100*(PeakBandwidth/TotalBandwidth)
Tunnel Count	Number of tunnels carried by the link in normal mode.
Peak Tunnel Count	Maximum number of tunnels carried by the link during the maintenance event failure simulation.
Oversubscription Count	Number of failures that caused used bandwidth to exceed `(1-fatpct)*TotalBw where fatpct=0.00%`.
Worst Load Cause	Cause of the worst load (bandwidth utilization) during the maintenance event simulation. It can be due to one of the following: NDFAIL (node failure) LINKFAIL (link failure) FACFAIL (facility failure) SIMPLACE (alias for element that is put under maintenance)
Load Cause Event	Network element that caused the worst load during the maintenance event simulation. It can be caused by a node, a link (From and To nodes are displayed), or a facility.
Worst Tunnel Cause	Cause of the worst (or increased) tunnel count during the maintenance event simulation. It can be due to one of the following: NDFAIL (node failure) LINKFAIL (link failure) FACFAIL (facility failure) SIMPLACE (alias for element that is put under maintenance)
Tunnel Cause Event	Network element that caused the worst tunnel count during the maintenance event simulation. It can be caused by a node, a link (From and To nodes are displayed), or a facility.

Peak Simulation Summary Report

Table 8 describes the fields on Peak Simulation Summary page.

Table 8: Fields on the Peak Simulation Summary Page
Field	Description
Simulation Type	Type of exhaustive maintenance simulation. It can be Node, Link, SRLG, or a combination of the three types.
Event	Name of the network element under maintenance. It can be node name, link name or facility (SRLG) name.
UP/Down	Operation performed in the simulation—Up or Down.
Layer	Type of Layer—Demand or Tunnel.
Impact Count	Number of tunnels impacted by the simulation.
Impact Bandwidth	Total bandwidth (in bps) of the impacted demand or tunnel.
Fail Count	Number of disconnected flows ( tunnels that are terminated at failed nodes are not included).
Fail Bandwidth	Total bandwidth (in bps) of disconnected flows
Fail Bandwidth Percentage	100*FailedBandwidth/TotalFlowBandwidth percentage
Highest Priority Fail	Highest priority of failed flows.
Oversubscription Count	Number of links where bandwidth oversubscription has occurred.
Max Hop	Maximum path hop count after failure.
Average Hop	Average path hop count after failure.
Terminated Count	Number of flows terminated at failed nodes.
Terminated Bandwidth	Total bandwidth (in bps) of flows terminated at failed nodes.

Peak Tunnel Failure

Table 9 describes the fields on the Peak Tunnel Failure page.

Table 9: Fields on the Peak Tunnel Failure Page
Field	Description
Simulation Type	Type of exhaustive maintenance simulation. It can be Node, Link, SRLG, or a combination of the three types.
Event	Name of the network element under maintenance. It can be node name, link name or facility (SRLG) name.
Layer	Type of Layer—Demand or Tunnel.
Path Name	Name of the path.
From	Name of the ingress node.
To	Name of the egress node.
ToIPAddr	IP address of the egress (To) node.
Bandwidth	Total bandwidth (in bps) available for the user traffic.
Priority	Setup and Hold priority for the LSP traffic. Range is 0 (highest priority) through 7 (lowest priority). The default is 7, which is the standard MPLS LSP definition in Junos OS. For example, 7,0 implies that 7 is the setup priority and 0 is the hold priority.
Path Comment	Comment (in text format) about the failed tunnel path. It can have one of the following values: Not Routed—Tunnel has failed and has not been routed. Time Expired—Tunnel is no longer active in the network. For example, when you schedule an LSP, the LSP will be active only during the scheduled time period. When you run a maintenance simulation when this LSP is not in the scheduled time period, it will be marked here as Time Expired.
Info	Only when a node failure occurs during maintenance simulation, this field displays one of the following values: Pass Through—Implies that this LSP passes through but does not originate or terminates at the failed node. Terminated at Node—Implies that this LSP originates or terminates on the failed node.

ON THIS PAGE