The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco EPN Manager provides several ways to see, at a glance, if there are any problems with circuits/VCs:
To identify which circuits/VCs are affected by a specific fault:
Step 1 | From the left side bar, choose Monitor > Monitoring Tools > Alarms and Events. |
Step 2 | In the alarm table, locate the required alarm. You can use the simple or advanced filters to locate the alarm, if necessary. |
Step 3 | Click on the arrow to the left of the row to expand the row and display the alarm details. |
Step 4 | Locate the Impacted Circuits/VCs pane. All circuits/VCs that are affected by the selected alarm are listed in this pane, with basic information for each circuit/VC. You can access the Circuit/VC 360 view to get more details about the circuit/VC by clicking the i icon. |
Step 5 | If necessary, you can modify or delete the circuit/VC from the Impacted Circuits/VCs pane by selecting a circuit/VC and clicking the Modify or Delete button. This opens the Provisioning Wizard. See Modify a Circuit/VC and Delete a Circuit/VC for more information. |
Cisco EPN Manager provides information about why the provisioning operation of a circuit/VC has failed so that you can troubleshoot the issues. In the Circuits/VCs table, you can identify problems with a circuit/VC by looking at the Provisioning state and the Serviceability and Discovery states. If there has been an error during the provisioning of a circuit/VC and the circuit/VC could not be created, the Provisioning state will be Create Failed. You can click the i icon in the Provisioning column to see the configuration of the devices involved in the failure, as well as details about the specific error(s) that occurred.
Note | Information about a circuit/VC failure can also be accessed from the Circuit/VC 360 view. See Get Quick Information About a Circuit/VC: Circuit/VC 360 View. |
To view additional information about a circuit/VC provisioning failure from the Circuits/VCs table:
For optical circuits, if the Serviceability state is Down and the Discovery state is Partial, click the i icon next to the Serviceability column to view the Serviceability Details data pop-up window that displays information about why the circuit's serviceability state is Down. You can also view the Serviceability Details data pop-up window from the Circuit/VC 360 view. For information about how to access the Circuit/VC 360 view, see Get Quick Information About a Circuit/VC: Circuit/VC 360 View.
Cisco EPN Manager provides the ping and traceroute features to troubleshoot service failures. You can use OAM commands to access these features and monitor the connectivity and path between two endpoints in a service. You can then isolate and resolve the failure. The technologies that are supported for the different IOS devices are:
You can perform ping or traceroute using the OAM commands to troubleshoot a service failure. See Perform a Ping or Traceroute Using OAM Command
To launch MPLS LSP technology OAM command from Network Devices table:
Command or Action | Purpose |
---|
If you are launching OAM command from the Service/Circuit 360, the service type is the criteria that determines the technology that is supported. See Overview of Circuit/VC Discovery and Provisioning to know in detail about the different service types.
To launch OAM command from Circuit 360:
Command or Action | Purpose | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Step 1 | Choose . | |||||||||||
Step 2 | In the Network Topology window, click the Circuits/VCs tab and click the i icon next to the circuit to view the Circuit 360. Based on the service type of the circuit you selected, the supported technology OAM commands as mentioned in this table are displayed. |
| ||||||||||
Step 3 | Click Actions and select the Technology OAM that is displayed for the service type you chose. |
If you are launching OAM command from the alarm browser, the event type is the criteria that determines the technology that is supported.
To launch OAM command from an alarm browser:
Command or Action | Purpose | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Step 1 | Choose . | |||||||||||
Step 2 | In the Alarms table, select an alarm with an event type listed in the "Event Type for which you can launch the OAM command" column in this table. |
| ||||||||||
Step 3 | Click Troubleshoot above the Alarms table and select OAM Commands. |
To perform a ping or traceroute using OAM command:
Step 1 | Launch the TechnologyOAM Command window. See Troubleshoot a Service Failure Using OAM Commands for the OAM command launch points for the supported technologies. | ||||||||||||||||||
Step 2 | Based on the
launch point, select the required fields as displayed in this table for the
selected technology type.
| ||||||||||||||||||
Step 3 | Choose to perform a ping, and choose to perform a traceroute. |
The results of the ping and traceroute commands are displayed in the following formats:
Note |
|
Note | The traceroute command results for all the technologies are displayed in visual format. |
Note | Only the traceroute command results are displayed in tabular format. |
Note | Both ping and traceroute command results are displayed as raw data. |
Cisco EPN Manager provides several predefined templates that can be used to monitor the connectivity and performance of virtual connections (VCs) in a Carrier Ethernet network. To use these templates, choose Configuration > Templates > Features & Technologies > CLI Templates > System Templates - CLI. See Perform EOAM Connectivity and Performance Checks for more information.
When you run a performance test, Cisco EPN Manager connects to the network elements to provide real-time data. To get historical information, see View Performance Metrics and Reports for Circuits/VCs.
CE performance tests verify the correct configuration and performance of CE EVCs at the time of activation. You can also use the CE performance tests to troubleshoot an EVC that is already in operation.
The Y.1564 Ethernet service activation or performance test methodology allows turning up, installing, and troubleshooting Ethernet-based services. Using this test, you can verify the service configuration and performance from UNI to UNI. This ensures that the SLA will be met according to the bandwidth profile purchased, and the promised class of service.
These tests provide complete validation of Ethernet service-level agreements (SLAs) in a single test. Using a traffic generator performance profile, you can create the traffic based on your requirements. The network performance, such as throughput, loss, and availability, are analyzed using Layer 2 traffic with various bandwidth profiles.
Note | You can only run performance tests on EVCs that are configured on the network and discovered by Cisco EPN Manager . |
The Y.1564 performance test is supported on the following devices running IOS 15.4(S) or IOS XE 3.12S and higher:
List of devices that can be specified as either source or destination:
Cisco ASR 920
Cisco ASR 920 24SZIM
Cisco ASR 920 24TZM
Cisco ASR 920 24SZM
Cisco ASR 920 4S ZD
Cisco ASR 920 8S Z0A
Cisco ASR 920 12 CZA
Cisco ASR 920 12 CZD
Cisco ASR 920 4S ZA
Cisco ASR 920 8S Z0D
Cisco ASR 920 12 CZ IM
Cisco ASR 901
Cisco ASR 901S
Cisco ASR 901_10G
Cisco ASR 903 RSP2/RSP3
Cisco NCS 4201
Cisco NCS 4202
Cisco ME 3600X-24CX-M
Cisco ME 3600X-24CXE-M
Cisco ME1200
List of devices that can be specified as destination (loopback) only:
To run a Y.1564 performance test on an EVC, do the following:
Interface <interface-name>
qos map tag-cos pcp 0 dei 0 cos 0 dpl 0
qos map tag-cos pcp 0 dei 1 cos 0 dpl 1
qos map tag-cos pcp 1 dei 0 cos 1 dpl 0
qos map tag-cos pcp 1 dei 1 cos 1 dpl 1
qos map cos-tag cos 0 dpl 0 pcp 0 dei 0
qos map cos-tag cos 0 dpl 1 pcp 0 dei 1
qos map cos-tag cos 1 dpl 0 pcp 1 dei 0
qos map cos-tag cos 1 dpl 1 pcp 1 dei 1
Step 1 | Choose Network Topology page. to open the | ||
Step 2 | From the toolbar, click Device Groups to open the Device Groups pop-up window. | ||
Step 3 | Locate and click the device group that contains the circuit/VC you want to test, then close the pop-up window. | ||
Step 4 | Click the Circuits/VCs tab, locate the relevant service, and then click its i (information) icon to open its Circuit/VC 360 view. | ||
Step 5 | From the top
right corner of the view, choose
to open the Y.1564 performance test settings
page.
| ||
Step 6 | Configure the
settings for the performance test:
| ||
Step 7 | Click
Run
Test.
When the test is completed, the results are displayed at the bottom of the Y.1564 performance test settings page. |
The Y.1731 Performance Monitoring (PM) provides a standard ethernet PM function that includes measurement of ethernet frame delay, frame delay variation, frame loss, and frame throughput measurements specified by the ITU-T Y-1731 standard and interpreted by the Metro Ethernet Forum (MEF) standards group. Using this test, you can verify the delay and loss measurements such as the delay and loss probe status, delay and loss probe availability, two-way delay, two-way jitter, loss forward, and loss backward for your circuit/VC.
Note | This performance test is supported on Cisco IOS and Cisco IOS-XR devices only. |
Following are the prerequisites that must be met before you run a performance test based on Y.1731 for a circuit/VC:
Step 1 | From the left sidebar, choose . | ||
Step 2 | Click Device Groups, and then select the location that contains the circuit/VC you want to test. | ||
Step 3 | In the Network Topology window, click Circuits/VCs. | ||
Step 4 | Locate the required circuit/VC, and then click the information icon to access its Circuit/VC 360 view. | ||
Step 5 | Choose
.
| ||
Step 6 | Choose the required source and destination devices and their corresponding interfaces. | ||
Step 7 | From the CoS drop-down list, choose the priority of the probe. The default value is 0. | ||
Step 8 | Choose the required measurement type. The options are Delay, Loss, and Loss & Delay. | ||
Step 9 | If required, define the advanced performance test parameters as
follows:
| ||
Step 10 | Click Run Test. When the test is completed, the results will be displayed at the bottom of the Performance Test page, under the Test Results area. |
Cisco EPN Manager performance test for optical circuits is based on the ITU-T recommendations as defined in G.709 and G.798.
Cisco EPN Manager supports the following performance tests for Optical Circuits:
Optical Performance Monitoring Parameters monitor the quality of optical signals and are used to measure the average optical power transmitted and received between end points in optical circuits. From these measurements, you can derive critical network performance parameters such as channel presence verification, channel wavelength, ASE noise, optical signal power, and optical signal to noise ratio (OSNR) per channel. You can then use these parameters to manage the network reliability and quality of service.
Follow the steps below to view the performance monitoring parameters for an optical circuit:
Step 1 | From the left sidebar, choose . | ||
Step 2 | Select the device group that contains the circuit/VC you want to test. | ||
Step 3 | In the Circuits/VCs pane on the left, locate the required service and click the i icon to access its Circuit/VC 360 view. | ||
Step 4 | Choose
Actions
>
Optical PM
Parameters
.
| ||
Step 5 | Select an optical monitoring type based on which the performance data will be displayed. For more information about the optical monitoring types and the associated performance counters, see Performance Counters for Optical Monitoring Policies. | ||
Step 6 | Choose the performance monitoring time interval as 15 minutes or 24 hours to collect the performance data from the device. | ||
Step 7 | Specify the time interval to automatically refresh the performance data. | ||
Step 8 | Click
Auto
Refresh. The performance data for the circuit is
displayed as a tabular representation. For the detailed descriptions of the
performance data, see
Performance Counters for Optical Monitoring Policies.
Based on the time interval specified to refresh the performance data, the newly retrieved data is displayed at the beginning of the table. For example, if the time interval specified is 10 seconds, the performance data is automatically refreshed every 10 seconds and the newly retrieved data is displayed at the beginning of the table. The table displays the last 20 entries of the performance data retrieved. |
PRBS test is supported for OTN Circuits of type ODU UNI. PRBS bit error count measures the reliability of the link between the endpoints. This test is supported for NCS4K-20T-O-S cards. When PRBS test is run between 2 endpoints (ODU Controller or sub-controller), the source device sends a bit pattern through one or more midpoints (intermediate controller or sub-controller) and the same bit pattern is received by the destination device, the test results can be viewed from both the endpoints. You can also run the PRBS test on a controller, configuring the other endpoint as a loopback, source, or source-sink.
For information on configuring PRBS on an ODU controller, see Configure PRBS on ODU Controllers.
To run a PRBS performance test for an optical circuit:
Step 1 | From the left sidebar, choose . |
Step 2 | Select the device group that contains the circuit/VC of type ODU UNI you want to test. |
Step 3 | In the Circuits/VCs pane on the left, locate the required service and click the i icon to access its Circuit/VC 360 view. |
Step 4 | Choose . |
Step 5 | To assign roles to the endpoints, in the Endpoint table, click the endpoint's role and select one of the following options from the drop-down list: |
Step 6 | To assign
patterns to the endpoints, in the
Endpoint
table, click the endpoint's pattern and select the desired pattern from the
drop-down list.
|
Step 7 | To change the loopback mode, in the Loopbacks table, click the endpoint's or midpoint's loopback mode and select one of the following options from the drop-down: |
Step 8 | In the Test Results area, select the endpoint from the Sink Controller drop-down list. |
Step 9 | Click one of the following Interval radio button, to set the time interval to collect the data from the device: |
Step 10 | Click Go. |
Step 11 | Click
Auto
Refresh. The test result for the endpoints is displayed as a tabular
representation which includes bit error count, packets lost and found
timestamps and packet lost and found counts.
Based on the time interval specified to refresh the test, the newly retrieved data is displayed at the beginning of the table. For example, if the time interval specified is 10 seconds, the data is automatically refreshed every 10 seconds and the newly retrieved data is displayed at the beginning of the table. |
Bit error rate test (BERT) allows you to test cables and diagnose signal problems in the field. This testing mechanism is supported on the Cisco NCS 42xx Series(T1/E1 Ports). This test generates a specific pattern on to the outgoing data stream of a circuit controller and then analyzes the incoming data stream for the same pattern. The bits that do not match the expected pattern are counted as bit errors.
The bit error rate is determined by comparing the erroneous bits received with the total number of bits received. You can view and analyze the total number of error bits transmitted and the total number of bits received on the circuit. You can retrieve error statistics anytime during the test.
BERT Pattern |
Description |
---|---|
0s |
Test pattern consisting of all 0's that is used to test line coding. |
1s |
Test pattern consisting of all 1's that is used to test alternating line volt and repeaters. |
2^11 |
Pseudo-random repeating test pattern that consists of 2,048 bits. |
2^15 |
Pseudo-random repeating test pattern that consists of 32,767 bits. |
2^20-O153 |
Pseudo-random repeating test pattern that consists of 1,048,575 bits. |
2^20-QRSS |
Pseudo-random QRSS O.151 test pattern that is 1,048,575 bits in length. |
2^23 |
Pseudo-random 0.151 test pattern that is 8,388,607 bits in length. |
alt-0-1 |
Repeating alternating pattern of zeros and ones. |
To run a BERT performance test for a CEM circuit:
Step 1 | From the left sidebar, choose . |
Step 2 | In the
Circuits/VCs tab, locate the required CEM service and click
the
i icon to
access its Circuit/VC 360 view. In the Circuit/VC 360 view, choose
.
Alternatively, you can reach this page through and from the Circuits/VCs pane, access the Circuit/VC 360 view of the required CEM circuit. |
Step 3 | In the
Test tab,
select the test direction, source and destination.
For easy understanding, the pictorial representation of the test in the circuit is displayed, once the source and destination are selected. |
Step 4 | To refresh the test data automatically for a defined time interval, in the Settings area, enter the time interval in minutes. |
Step 5 | Select the pattern from the BERT Pattern drop-down list. |
Step 6 | You can deliberately inject errors in the frame by specifying the value in Inject Errors field and then click Run Test. The test result is displayed in the Test Results area. See View and Export the Results of the Performance Test on Circuit Emulation Services |
Step 7 | To terminate the test, in the Settings area, click Stop and click Clear Countersto reset the values in the Test Results area. |
At a time, BERT performance test can be performed on any number of CEM circuits but only one test can be performed on a single CEM circuit. The results of the BERT performance test on a CEM circuit is displayed in the Test Results area.
At any point in time, the results of last run/currently running BERT performance test on a CEM circuit is displayed in the Test Results area in the Test tab.
If the Auto-refresh is enabled (ON), then the test results are auto-refreshed at the specified time period.
In the Test Results area:
Choose
. Here, only a single entry for each CEM circuit is available and it shows either the last run/currently running test on that CEM circuit. Select the required CEM circuit to view its test results.To view the historical records of BERT performance results for a specific CEM circuit, in the History tab, select the required test from the Test drop-down list to view the configuration and its result.
You can export the results of a BERT performance test by clicking the Export icon at the top right corner of the Test and History tabs of the BERT page (from the Circuit/VC 360 view, choose ).
An Optical Time Domain Reflectometer (OTDR) test enables you to remotely diagnose OTS link related issues (such as degraded devices, splices and bends in the cables) and supports troubleshooting. OTDR test can be initiated only on the OTS links that are connected to the OTDR port in the TNC card.
User Group |
Can view OTDR scan?1 |
Can run and analyze OTDR scan?2 |
Can configure OTDR scan?3 |
|
---|---|---|---|---|
Web GUI |
Root |
Yes |
Yes |
Yes |
Super Users |
Yes |
Yes |
Yes |
|
Admin |
Yes |
Yes |
Yes |
|
Config Managers |
Yes |
Yes |
Yes |
|
System Monitoring |
Yes |
Yes |
No |
1. Users who can only view the scan results are not allowed to run the scan or perform any configuration changes.
2. Users who can run and analyze the scan results are not allowed to set baseline or perform any configuration changes.
3. User who can configure the scan are allowed to perform all the actions such as viewing the scan results, setting baseline and so on.
The following procedures describe how to configure and run the OTDR test in the OTDR ports of the TNC cards:
Step 1 | Configure OTDR Port Values
|
Step 2 | Provision OTDR Scan Recurrence
|
Step 3 | Run the OTDR Test
|
Step 4 | Export the OTDR Scan Result
|
This task configures the OTDR equipment values on TNCS cards for each sector required for the OTDR scan.
Step 1 | From the left sidebar, choose . | ||
Step 2 | Select the
OTS link, click
Actions,
and then click
OTDR scan.
| ||
Step 3 | In the
Configure
tab, select a device from the
Device
drop-down list. A table is displayed listing all the sectors with the default
values for the following columns:
The OTDR measurement ranges are categorized based on the fiber spans defined for each sector. Following are the OTDR measurement sectors:
| ||
Step 4 | To modify the OTDR settings, click the Device OTDR Settings hyperlink. For more details on the OTDR settings, see the 'Configuring OTDR Auto Scan' section in Provision Optical Interfaces. | ||
Step 5 | To edit the sector parameters, select the required Distance Profile in the table, and click Edit. A popup window is displayed. | ||
Step 6 | In the popup
window:
To enable absolute threshold, you need to select Absolute Fiber Pass Fail Criteria check-box in the OTDR Settings page. | ||
Step 7 | Click Save. |
Follow the below procedure to set up OTDR scan recurrence on the selected ports:
Step 1 | In the Configure tab of the OTDR Scans page, from the Device drop-down list, select the port on which you want to provision a recurring scan. |
Step 2 | Select the appropriate distance profile, and click Edit. A popup window is displayed. |
Step 3 | In the Recurrence area, set the scan frequency by choosing one of the following: |
Step 4 | Select the desired day from the on drop-down list and enter the hours and minutes. |
Step 5 | Select the desired day range between 0 to 365 and enter the hours and minutes. |
Step 6 | Click Save. |
Follow the below procedure to run the OTDR test on an OTS Link:
Step 1 | In the
Scans tab,
from the
Direction
drop-down list, select one of the following:
| ||||||||||
Step 2 | Select the
appropriate sector from the
Distance
Profile drop-down list, and then click
Start Scan.
| ||||||||||
Step 3 | (Optional)Click Set Baseline to set an OTDR test baseline, setting a baseline helps you to compare with the last scan results. | ||||||||||
Step 4 | To export the scan results, see Export the OTDR Scan Result. |
You can export the scan results to your local.
Step 1 | Click Export Scans. |
Step 2 | The currently selected directions and the distance profile will be auto-populated. You can also select the directions and the distance profile for which you need to export the scan result. |
Step 3 | Click
Export. The exported file will be downloaded and
saved to your local machine.
The current version of Cisco EPN Manager supports only the .sor format. |
The Circuit/VC 360 view provides information about the circuit's recent history. Reports, on the other hand, can retrieve all historical data stored in the database. For real-time information, run a performance test (see Run a Performance Test on a Circuit/VC).
The Circuit/VC 360 view contains graphs showing various aspects of the circuit/VC performance. This view is helpful if you want to see, at-a-glance, if there are any major issues with circuit/VC performance. For more information, see Get Quick Information About a Circuit/VC: Circuit/VC 360 View.
To access the Circuit/VC 360 view:
Step 1 | From the left side bar, choose Visualize the Network Topology for a description of the Network Topology window and its functionality. . The network topology window opens. See |
Step 2 | In the Locations pane on the left, select the device group within which the required circuit/VC was created. |
Step 3 | In the Circuits/VCs pane, locate the required circuit/VC and click on the i icon next to the circuit/VC name. The Circuit/VC 360 view appears in a separate popup window. |
Cisco EPN Manager provides extensive reporting capabilities that enable you to retrieve in-depth performance information for optical circuits and EVCs. The Report Launch Pad provides access to all Cisco EPN Manager reports. From the Report Launch Pad, you can create and save new reports, view current reports, open specific types of reports, schedule a report to run later, and customize the results of a report.
Choose Reports > Report Launch Pad in the left navigation pane to access the reports and the reporting functionality.
For information about Carrier Ethernet performance reports, see Carrier Ethernet (CE) Performance Reports.
For information about Optical performance reports, see Optical Performance Reports.
Service Performance dashboard provides a collection of graphical and tabular representation of Performance measurement for the selected circuit/VC over time. This information is available in the form of customized dashlets. The dashboard menu provides access to all the available Cisco EPN Manager dashboards.
From Service Performance Dashboard, you must select a circuit/VC from the Circuits/VCs drop-down list to view the following information (dashlets):
To launch the dashboard for a specific service from its Circuit/VC 360 view, click
and then choose .For more information on the Service Performance dashboards and dashlets, see Service Performance Dashboard Overview.
For more information on managing dashboards and dashlets, see Get Started With Cisco EPN Manager.
Use the Multilayer Trace View to visualize a circuit in a graphical manner. This view displays the complete circuit span and service trace between two endpoints and can be used to trace the connectivity of a circuit by displaying the source node, the destination node, and any intermediate nodes in graphical format.
Note | The Multilayer Trace view is not supported for L3VPN services, Multipoint Carrier Ethernet circuits/VCs, and Serial services. |
Note | You can launch the Multilayer Trace view for optical circuits only when LMP is configured on the A end device and also between devices participating in the optical circuit. |
To trace and visualize the full route of a circuit :
Step 1 | From the left side bar, choose . | ||||
Step 2 | Click Device Groups and then select the location in which the required circuit/VC was created. | ||||
Step 3 | On the Network Topology page, click Circuits/VCs. The list of circuits/VCs associated with the selected device group is displayed. | ||||
Step 4 | Select a circuit/VC for which you want to view the full route. The overlay of the circuit is displayed on the map. | ||||
Step 5 | Use one of
the following ways to switch to the Multilayer Trace view:
The following figure shows the simplified view of a circuit/VC with the expand and collapse options.
For more information about the details displayed in a three-dimensional view, see Three-Dimensional View of a Circuit V/C Trace. To switch to the linear view, click Linear View. For more information about the details displayed in a linear view, see Linear View of a Circuit/VC Trace. |
Uses
high-level span information such as NEs and links to display the circuit trace.
Displays
logical high-level view where the circuit is traced on the map using logical
links. For example, OCHCC circuits use OCH trail links for the trace.
Displays
physical high-level view where the circuit is traced on the map using physical
links. For example, OCHCC circuits use OTS links for the trace.
Displays
badges on the devices that represent the most severe alarm on the device,
irrespective of the selected circuit. The alarm badges within the trace view
show the alarms on each entity (for example the link, node, or point).
Highlights
links according to the high-level view that you select.
Highlights the
layers with different shades and displays border lines that delineate the
different layers in the circuit. If a layer is not applicable for a device,
that layer appears in gray color
Displays a
collapsible legend that lists the different icons and descriptions of each icon
displayed in the Multilayer Trace view.
For optical
circuits, indicates whether the devices or links in the circuit have Shared
Risk Resource Groups (SRRGs) assigned to them. Click on the SRRG label on the
link or device to see a list of all the SRRGs on that link/device. The SRRGs
are color-coded based on whether they are the default on the device, assigned,
or yet to be assigned. Click on the question mark icon to see the legend.
If one or more devices participating in the circuit/VC is not part of your virtual domain, the Multilayer Trace will be partial. Instead of the inaccessible device, you will see an inaccessible device icon in the Multilayer Trace view (as shown in the figure below).
This is the default view. It displays a three-dimensional view of the full route of a circuit/VC. For information about how to access this view, see Trace and Visualize the Full Route of Circuits/VCs.
This view displays the different paths available for the selected circuit. For example, if an optical circuit has working path, protected path, and restoration path, the paths are color-coded and displayed in this view.
To know about the navigation controls in the three-dimensional view, click the help icon in the tool bar. The Navigation Controls data popup window shows the mouse, MAC Trackpad, and keyboard controls to pan, zoom, and rotate in this view.
Note | The MAC Trackpad controls are displayed only for MAC users. |
Using the linear view, you can trace and visualize the route of a circuit/VC in a two-dimensional view. For information about how to access this view, see Trace and Visualize the Full Route of Circuits/VCs.
This view displays only one path of the circuit at a time. Choose Route, and then select Working, Protected, or Restored to view the required path in the circuit trace. The path options will vary depending on the type of circuit/VC you selected.
You can do the following from the Multilayer Trace view:
Note | The check boxes vary depending on the type of circuit/VC you selected. |
You can view either the alarm status or the primary state of the ports. For a list of the port primary state icons and a description of the states, seePort and Interface States.
Note | The Cross Connection icon appears on the links where internal ports are used by the circuit/VC. The internal ports are not displayed in the Multilayer Trace view. |
Choose Protected Path to reroute the traffic through the working path or protected path defined for the circuit. See Reroute a Circuit (Optical).
or