- play_arrow Introduction to the NorthStar Controller
- play_arrow NorthStar Controller Overview
- play_arrow NorthStar Controller Web UI Introduction
-
- play_arrow NorthStar Controller Features
- play_arrow Interactive Network Topology
- Topology View Overview
- Navigation Functions in the Topology View
- Interactive Map Features
- Manage Layouts
- Configuration Viewer
- Applications Menu Overview
- Group and Ungroup Selected Nodes
- Distribute Nodes
- Reset Topology by Latitude and Longitude
- Left Pane Options
- Network Information Table Overview
- Sorting and Filtering Options in the Network Information Table
- Network Information Table Bottom Tool Bar
- Push Configuration to Network Devices from Within the NorthStar Application
- Topology Filter
- play_arrow LSP Management
- Understanding Label-Switched Paths on the NorthStar Controller
- Understanding the Behavior of Delegated Label-Switched Paths
- Provision LSPs
- Provision Diverse LSP
- Provision Multiple LSPs
- Configure LSP Delegation
- Bandwidth Management
- Templates for Netconf Provisioning
- Provision and Manage P2MP Groups
- Bandwidth Calendar
- Creating Templates to Apply Attributes to PCE-Initiated Label-Switched Paths
- Creating Templates with Junos OS Groups to Apply Attributes to PCE-Initiated Label-Switched Paths
- play_arrow Path Computation and Optimization
- play_arrow Working with Transport Domain Data
- play_arrow High Availability
- play_arrow System Monitoring
- play_arrow Network Monitoring
- play_arrow Data Collection and Analytics
- NorthStar Analytics Raw and Aggregated Data Retention
- Device Profile and Connectivity Testing
- Introduction to the Task Scheduler
- Scheduling Device Collection for Analytics
- Viewing Analytics Data in the Web UI
- Netconf Persistence
- Data Collection Using SNMP
- Support for Cisco Model Driven Telemetry
- Link Latency Collection
- LDP Traffic Collection
- Collection Tasks to Create Network Archives
- Netflow Collector
- NorthStar Integration with HealthBot
- LSP Routing Behavior
-
NorthStar Controller Troubleshooting Overview
In the Web UI, the Dashboard View and Event View (Applications>Event View) provide information that can help with troubleshooting.
For additional information to help identify and troubleshoot issues with the Path Computation Server (PCS) or NorthStar Controller application, you can access the log files.
If you are unable to resolve a problem with the NorthStar Controller, we recommend that you forward the debug files generated by the NorthStar Controller debugging utility to JTAC for evaluation. Currently all debug files are located in subdirectories under the u/wandl/tmp directory.
To collect debug files, log in to the NorthStar Controller CLI, and execute the command u/wandl/bin/system-diagnostic.sh filename.
The output is generated and available from the /tmp directory in the filename.tbz2 debug file.
Table 1 lists the NorthStar Controller log files most commonly used to identify and troubleshoot issues with the PCS and PCE. All log files are located under the /opt/northstar/logs directory, with one exception. The pcep_server.log file is located in /var/log/jnc.
| Log Files | Description |
cassandra.msg | Log events related to the cassandra database. |
configServer.msg | Log files related to maintaining LSP configuration states in NorthStar Controller. LSP configuration states are updated by collecting show commands and NETCONF provisioning. |
ha_agent.msg | HA coordinator log. |
mlAdaptor.log | Interface to transport controller log. |
netconfd.msg | Log files related to communication between NorthStar Controller and devices via NETCONF sessions. |
net_setup.log | Configuration script log. |
nodejs.msg | Log events related to nodejs. |
pcep_server.log | Located in /var/log/jnc. Log files related to communication between the PCC and the PCE in both directions. |
pcs.log | Log files related to the PCS, which includes any event received by PCS from Toposerver and any event from Toposerver to PCS including provisioning orders. This log also contains any communication errors as well as any issues that prevent the PCS from starting up properly. |
rest_api.log | Logs files of REST API requests. |
toposerver.log | Log files related to the topology server. Contains the record of the events between the PCS and topology server, the topology server and NTAD, and the topology server and the PCE server Note: Any message forwarded to the pcshandler.log file is also forwarded to the pcs.log file. |
