NorthStar Controller Getting Started Guide
Release
1.0.0
Modified: 2015-08-01
Copyright © 2015, Juniper Networks, Inc.
Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Copyright © 2015, Juniper Networks, Inc. All rights reserved.
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
NorthStar Controller Getting Started Guide
1.0.0
Copyright © 2015, Juniper Networks, Inc.
All rights reserved.
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the
year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks
software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of
that EULA.
ii
Copyright © 2015, Juniper Networks, Inc.
Table of Contents
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Chapter 1
NorthStar Controller Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Understanding the NorthStar Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Architecture and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Interaction Between PCC and PCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Dynamic Path Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
NorthStar Controller Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
NorthStar Controller Installation and Configuration Overview . . . . . . . . . . . . . . . . 21
Chapter 2
Downloading and Installing the NorthStar Controller Software . . . . . . . . . 23
Downloading the ISO Image for the NorthStar Controller and Creating a Bootable
USB or DVD Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Installing the ISO Image and NorthStar Controller Software from a USB or DVD
Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Connecting an x86 Network Appliance to the Network . . . . . . . . . . . . . . . . . . . . . 25
Chapter 3
Configuring Topology Acquisition and Connectivity Between the NorthStar
Controller and Path Computation Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Understanding Network Topology Acquisition on the NorthStar Controller . . . . . . 31
Configuring PCEP on a PE Router (from CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Mapping a Management IP Address for Path Computation Clients . . . . . . . . . . . 35
Configuring Connectivity for BGP-LS Topology Acquisition . . . . . . . . . . . . . . . . . . 36
Configuring BGP-LS Topology Acquisition on the NorthStar Controller . . . . . 37
Configuring Topology Acquisition on the PCC Routers . . . . . . . . . . . . . . . . . . 38
Configuring Connectivity for OSPF Topology Acquisition . . . . . . . . . . . . . . . . . . . . 38
Configuring OSPF on the NorthStar Controller . . . . . . . . . . . . . . . . . . . . . . . . 39
Configuring OSPF Over GRE on the NorthStar Controller . . . . . . . . . . . . . . . . 39
Configuring Connectivity for IS-IS Topology Acquisition . . . . . . . . . . . . . . . . . . . . 40
Configuring IS-IS on the NorthStar Controller . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring IS-IS Over GRE on the NorthStar Controller . . . . . . . . . . . . . . . . . 41
Chapter 4
Accessing the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
NorthStar Controller User Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
NorthStar Controller User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Menu Options for the NorthStar Controller User Interface . . . . . . . . . . . . . . . 45
Copyright © 2015, Juniper Networks, Inc.
iii
NorthStar Controller Getting Started Guide
RSVP Live Util Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Customizing Nodes and Links in the Map Legends . . . . . . . . . . . . . . . . . . . . . 46
Logging In to the NorthStar Controller User Interface . . . . . . . . . . . . . . . . . . . . . . 47
Logging Out of the NorthStar Controller User Interface . . . . . . . . . . . . . . . . . . . . . 50
Logging In as the NorthStar Controller Administrator . . . . . . . . . . . . . . . . . . . . . . 50
Chapter 5
Troubleshooting the NorthStar Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
NorthStar Controller Troubleshooting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Troubleshooting the NorthStar Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Accessing System Log Files for the NorthStar Controller . . . . . . . . . . . . . . . . 55
Accessing Information about System Processes Running on the NorthStar
Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Viewing Debug Trace Files for the NorthStar Controller . . . . . . . . . . . . . . . . . 56
FAQs for Troubleshooting the NorthStar Controller . . . . . . . . . . . . . . . . . . . . . . . . 57
Chapter 6
Managing Services on the NorthStar Controller . . . . . . . . . . . . . . . . . . . . . . . 61
Managing the Path Computation Server (PCS) and Path Computation Element
(PCE) Services on the NorthStar Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Chapter 7
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
iv
Copyright © 2015, Juniper Networks, Inc.
List of Figures
Chapter 1
NorthStar Controller Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 1: PCCD Is Relay/Message Translator Between PCE and RPD . . . . . . . . . . . 17
Chapter 2
Downloading and Installing the NorthStar Controller Software . . . . . . . . . 23
Figure 2: Interfaces and Addresses Preconfigured on the x86 Appliance . . . . . . . 27
Figure 3: NorthStar Controller Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 3
Configuring Topology Acquisition and Connectivity Between the NorthStar
Controller and Path Computation Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 4: Selecting a PCC to Map a Management IP Address . . . . . . . . . . . . . . . . 35
Chapter 4
Accessing the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 5: NorthStar Controller Initial Landing Page . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 6: NorthStar Controller Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 7: NorthStar Controller User Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 8: NorthStar Controller Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 9: Update Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 10: NorthStar Controller Administrator Login Dialog Box . . . . . . . . . . . . . . . 51
Chapter 5
Troubleshooting the NorthStar Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 11: System Log Files for the NorthStar Controller . . . . . . . . . . . . . . . . . . . . . 55
Figure 12: System Processes Running on the NorthStar Controller . . . . . . . . . . . . 56
Copyright © 2015, Juniper Networks, Inc.
v
NorthStar Controller Getting Started Guide
vi
Copyright © 2015, Juniper Networks, Inc.
List of Tables
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Chapter 4
Accessing the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 3: Menu Options for the NorthStar User Interface . . . . . . . . . . . . . . . . . . . . 45
Chapter 5
Troubleshooting the NorthStar Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 4: NorthStar Controller Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 5: Description of the System Process Fields . . . . . . . . . . . . . . . . . . . . . . . . . 56
Copyright © 2015, Juniper Networks, Inc.
vii
NorthStar Controller Getting Started Guide
viii
Copyright © 2015, Juniper Networks, Inc.
About the Documentation
•
Documentation and Release Notes on page ix
•
Documentation Conventions on page ix
•
Documentation Feedback on page xi
•
Requesting Technical Support on page xii
Documentation and Release Notes
®
To obtain the most current version of all Juniper Networks technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
If the information in the latest release notes differs from the information in the
documentation, follow the product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject
matter experts. These books go beyond the technical documentation to explore the
nuances of network architecture, deployment, and administration. The current list can
be viewed at http://www.juniper.net/books.
Documentation Conventions
Table 1 on page x defines notice icons used in this guide.
Copyright © 2015, Juniper Networks, Inc.
ix
NorthStar Controller Getting Started Guide
Table 1: Notice Icons
Icon
Meaning
Description
Informational note
Indicates important features or instructions.
Caution
Indicates a situation that might result in loss of data or hardware damage.
Warning
Alerts you to the risk of personal injury or death.
Laser warning
Alerts you to the risk of personal injury from a laser.
Tip
Indicates helpful information.
Best practice
Alerts you to a recommended use or implementation.
Table 2 on page x defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
Convention
Description
Examples
Bold text like this
Represents text that you type.
To enter configuration mode, type the
configure command:
user@host> configure
Fixed-width text like this
Italic text like this
Italic text like this
x
Represents output that appears on the
terminal screen.
user@host> show chassis alarms
•
Introduces or emphasizes important
new terms.
•
•
Identifies guide names.
A policy term is a named structure
that defines match conditions and
actions.
•
Identifies RFC and Internet draft titles.
•
Junos OS CLI User Guide
•
RFC 1997, BGP Communities Attribute
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
No alarms currently active
Configure the machine’s domain name:
[edit]
root@# set system domain-name
domain-name
Copyright © 2015, Juniper Networks, Inc.
About the Documentation
Table 2: Text and Syntax Conventions (continued)
Convention
Description
Examples
Text like this
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy levels;
or labels on routing platform
components.
•
To configure a stub area, include the
stub statement at the [edit protocols
ospf area area-id] hierarchy level.
•
The console port is labeled CONSOLE.
< > (angle brackets)
Encloses optional keywords or variables.
stub <default-metric metric>;
| (pipe symbol)
Indicates a choice between the mutually
exclusive keywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
broadcast | multicast
# (pound sign)
Indicates a comment specified on the
same line as the configuration statement
to which it applies.
rsvp { # Required for dynamic MPLS only
[ ] (square brackets)
Encloses a variable for which you can
substitute one or more values.
community name members [
community-ids ]
Indention and braces ( { } )
Identifies a level in the configuration
hierarchy.
; (semicolon)
Identifies a leaf statement at a
configuration hierarchy level.
(string1 | string2 | string3)
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
GUI Conventions
Bold text like this
Represents graphical user interface (GUI)
items you click or select.
> (bold right angle bracket)
Separates levels in a hierarchy of menu
selections.
•
In the Logical Interfaces box, select
All Interfaces.
•
To cancel the configuration, click
Cancel.
In the configuration editor hierarchy,
select Protocols>Ospf.
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can provide feedback by using either of the following
methods:
•
Online feedback rating system—On any page at the Juniper Networks Technical
Documentation site at http://www.juniper.net/techpubs/index.html, simply click the
stars to rate the content, and use the pop-up form to provide us with information about
your experience. Alternately, you can use the online feedback form at
https://www.juniper.net/cgi-bin/docbugreport/.
Copyright © 2015, Juniper Networks, Inc.
xi
NorthStar Controller Getting Started Guide
•
E-mail—Send your comments to [email protected]. Include the document
or topic name, URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or Partner Support Service
support contract, or are covered under warranty, and need post-sales technical support,
you can access our tools and resources online or open a case with JTAC.
•
JTAC policies—For a complete understanding of our JTAC procedures and policies,
review the JTAC User Guide located at
http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
•
Product warranties—For product warranty information, visit
http://www.juniper.net/support/warranty/.
•
JTAC hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with the
following features:
•
Find CSC offerings: http://www.juniper.net/customers/support/
•
Search for known bugs: http://www2.juniper.net/kb/
•
Find product documentation: http://www.juniper.net/techpubs/
•
Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
•
Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
•
Search technical bulletins for relevant hardware and software notifications:
http://kb.juniper.net/InfoCenter/
•
Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
•
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
xii
•
Use the Case Management tool in the CSC at http://www.juniper.net/cm/.
•
Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
Copyright © 2015, Juniper Networks, Inc.
About the Documentation
For international or direct-dial options in countries without toll-free numbers, see
http://www.juniper.net/support/requesting-support.html.
Copyright © 2015, Juniper Networks, Inc.
xiii
NorthStar Controller Getting Started Guide
xiv
Copyright © 2015, Juniper Networks, Inc.
CHAPTER 1
NorthStar Controller Overview
•
Understanding the NorthStar Controller on page 15
•
NorthStar Controller Features on page 18
•
NorthStar Controller Installation and Configuration Overview on page 21
Understanding the NorthStar Controller
The Juniper Networks NorthStar Controller is an SDN network controller that enables
granular visibility and control of IP/MPLS flows in large service provider and enterprise
networks. Network operators can use the NorthStar Controller to optimize their network
infrastructure through proactive monitoring, planning, and explicit routing of large traffic
loads dynamically based on user-defined constraints.
The NorthStar Controller provides network managers with a powerful and flexible traffic
engineering solution and the following features:
•
Complex inter-domain path computation and network optimization
•
Comprehensive network planning, capacity, and topology analysis
•
Ability to address multilayer optimization with multiple user-defined constraints
•
Specific ordering and synchronization of paths signaled across routed network elements
•
Global view of the network state for monitoring, management, and proactive planning
The NorthStar Controller relies on PCEP to instigate a path between the PCC routers.
The path setup itself is performed through RSVP-TE signaling, which is enabled in the
network and allows labels to be assigned from an ingress router to the egress router.
Signaling is triggered by ingress routers in the core of the network. The PCE client runs
®
on the routers by using a version of the Junos operating system (Junos OS) that supports
PCE.
The NorthStar Controller provisions PCEP in all PE devices (PCCs) and uses PCEP to
retrieve the current status of the existing tunnels (LSPs) that run in the network. By
providing a view of the global network state and bandwidth demand in the network, the
NorthStar Controller is able to compute optimal paths and provide the attributes that
the PCC uses to resignal the LSP.
Copyright © 2015, Juniper Networks, Inc.
15
NorthStar Controller Getting Started Guide
The following sections describe the architecture, components, and functionality of the
NorthStar Controller:
•
Architecture and Components on page 16
•
Interaction Between PCC and PCE on page 17
•
Dynamic Path Provisioning on page 17
Architecture and Components
Based on the Path Computation Element (PCE) architecture as defined in RFC 5440,
the NorthStar Controller provides a stateful PCE that computes the network paths or
routes based on a network graph and applies computational constraints. A Path
Computation Client (PCC) is a client application that requests the PCE perform path
computations for the PCC’s external label-switched paths (LSPs). The Path Computation
Element Protocol (PCEP) enables communication between a PCC and the NorthStar
Controller to learn about the network and LSP path state and communicate with the
PCCs. The PCE entity in the NorthStar Controller calculates paths in the network on
behalf of the PCCs, which request path computation services. The PCCs receive and then
apply the paths in the network.
The stateful PCE implementation in the NorthStar Controller provides the following
functions:
•
Allows offline LSP path computation
•
Triggers LSP reroute when there is a need to reoptimize the network
•
Changes LSP bandwidth when an application demands an increase in bandwidth
•
Modifies other LSP attributes on the router, such as explicit route object (ERO), setup
priority, and hold priority
A TCP-based PCEP session connects a PCC to an external PCE. The PCC initiates the
PCEP session and stays connected to the PCE for the duration of the PCEP session.
During the PCEP session, the PCC requests LSP parameters from the stateful PCE. When
receiving one or more LSP parameters from the PCE, the PCC resignals the TE LSP. When
the PCEP session is terminated, the underlying TCP connection is closed immediately,
and the PCC attempts to reestablish the PCEP session.
The PCEP functions include the following:
16
•
LSP tunnel state synchronization between a PCC and a stateful PCE— When an active
stateful PCE connection is detected, a PCC synchronizes an LSP state with the PCE.
PCEP enables a fast and timely synchronization of the LSP state to the PCE.
•
Delegation of control over LSP tunnels to a stateful PCE—An active stateful PCE
controls one or more LSP attributes for computing paths, such as bandwidth, path
(ERO), and priority (setup and hold). PCEP enables such delegation of LSPs for path
computation.
•
Stateful PCE control of timing and sequence of path computations within and across
PCEP sessions—An active stateful PCE modifies one or more LSP attributes, such as
bandwidth, path (ERO), and priority (setup and hold). PCEP communicates these new
Copyright © 2015, Juniper Networks, Inc.
Chapter 1: NorthStar Controller Overview
LSP attributes from the PCE to the PCC, after which the PCC re-signals the LSP in the
specified path.
Interaction Between PCC and PCE
For the NorthStar Controller, the PCC runs in a new Junos OS daemon, the path
computation client process (PCCD), which interacts with the PCE and with the routing
protocol process (RPD) through an internal Junos OS IPC mechanism. Figure 1 on page 17
shows the interaction between the PCE, PCCD, and RPD.
Figure 1: PCCD Is Relay/Message Translator Between PCE and RPD
The PCCD is stateless so it does not keep any state other than current outstanding
requests, and does not remember any state for established LSPs. The PCCD requests
the state after the response comes back from the PCE and then forwards the response
to the RPD. Because the PCCD is stateless, the RPD only needs to communicate with
the PCCD when the LSP is first created. After the RPD receives the results from the PCCD,
the results are stored (even across RPD restarts), and the RPD does not need to
communicate with the PCCD again until the LSP is rerouted (when the LSP configuration
is changed or the LSP fails).
Dynamic Path Provisioning
To provide dynamic path provisioning, each ingress label-edge router (LER) must be
configured as a Path Computation Client (PCC). Through PCEP, each PCC informs the
NorthStar Controller (PCE server) asynchronously about the state of LSPs, including LSP
operational state, admin state, and protection in-use events. The LSP state update and
LSP provisioning depend on the TCP/PCEP connection state. If the TCP connection goes
down as a result of connection flaps or PCC failure, the NorthStar Controller waits
approximately 60 seconds for PCC reconnection then removes the LSP state.
Related
Documentation
•
Understanding Network Topology Acquisition on the NorthStar Controller on page 31
•
NorthStar Controller Features on page 18
Copyright © 2015, Juniper Networks, Inc.
17
NorthStar Controller Getting Started Guide
NorthStar Controller Features
The NorthStar Controller software provides traffic-engineering based solutions for WAN
and Edge (data center edge and WAN edge) networks. After the NorthStar Controller
has connected to the network and dynamic topology acquisition is performed to provide
a real-time routing view of the network topology, you can view the network model from
the NorthStar Controller user interface. You can then plan, analyze, and assess the impact
of network changes you want to make before implementing them.
The NorthStar Controller supports the following use cases and features:
•
Dynamic topology acquisition—Use routing protocols (IS-IS, OSPF, and BGP-LS) to
obtain real-time topology updates.
•
Label-switched path (LSP) reporting—Label edge routers (LERs) use PCEP reports to
report all types of LSPs (PCC_controlled, PCC_delegated, and PCE_initiated) to the
NorthStar Controller.
•
LSP provisioning—Create LSPs from the NorthStar Controller or update LSPs that have
been delegated to the NorthStar Controller.
•
Bidirectional LSPs—Design a pair of LSPs so that the LSP from the ingress LER to the
egress LER follows the same path as the LSP from the egress LER to the ingress LER.
•
Diverse LSPs—From the NorthStar Controller user interface, design two LSPs so that
the paths are either node, link, or SRLG diverse from each other.
NOTE: The NorthStar Controller supports diverse point-to-point diverse
LSPs. The provisioning of diverse point-to-multipoint diverse LSPs is not
supported.
•
18
Standby and secondary LSPs—Provide an alternate route in the event the primary
route fails. The tunnel ID, from node, to node, and IP address of a secondary or standby
LSP are identical to that of the primary LSP. However, secondary and standby LSPs
have the following differences:
•
A secondary LSP is not signaled until the primary LSP fails.
•
A standby LSP is signaled regardless of the status of the primary LSP.
•
Time-based LSP scheduling—Schedule the creation of LSPs based on future
requirements by using time-based calendaring. You can schedule an LSP as a one-time
event or recurring daily event for a specified period of time to schedule setup,
modification, and tear down of LSPs based on the traffic load, bandwidth, and setup
and hold priority requirements of your network over time. The scheduling of an LSP is
configured on the primary path, and the scheduled time applies to all paths (primary,
secondary, and standby).
•
LSP templates—Create LSP templates to define a set of LSP attributes to apply to all
PCE-initiated LSPs that provide a name match with the regular expression (regex)
name specified in the template. By associating LSPs (through regex name matching)
Copyright © 2015, Juniper Networks, Inc.
Chapter 1: NorthStar Controller Overview
with an LSP template, you can automatically enable or disable LSP attributes across
any LSPs that provide a name match with the regex name that is specified in the
template.
•
Auto-bandwidth LSPs—Auto-bandwidth support for Path Computation Element
(PCE)-controlled (PCE-initiated or PCC-delegated) LSPs—Path Computation Clients
(PCCs) can automatically adjust the required bandwidth based on the traffic load on
the LSP. Auto-bandwidth parameters must be configured from the PCC, even when
the LSP has been delegated to the NorthStar Controller. However, you can enable
auto-bandwidth parameters by way of a template so that any PCE-controlled LSP
that provides a name match with a regular expression (regex) name defined in a
template inherits the LSP attributes specifed in that template.
Auto-bandwidth behavior varies depending on the LSP type:
•
Router-controlled LSPs—The NorthStar Controller must learn about router-controlled
LSPs. The PCC performs statistical accounting of LSP bandwidth and LSP resizing
is driven by bandwidth threshold triggers. The NorthStar Controller is updated
accordingly.
•
NorthStar Controller managed (Delegated) LSPs —The PCC performs bandwidth
accounting for these LSPs. When bandwidth thresholds are reached, a PCReq
message is sent to the NorthStar Controller’s Path Computation Server (PCS) to
compute the Explicit Route Object (ERO). The PCC determines how to resize the
LSP while the PCS provides the ERO that meets the constraints. These LSPs are
delegated as usual, and PCRpt messages are sent with the Delegation bit set.
When bandwidth threshold triggers are reached on the PCC, a PCReq message is
sent to the PCE to request a path with new bandwidth. The following conditions
apply:
•
•
If a new path is available, make-before-break (MBB) signaling is attempted and
a new path is signaled. The PCRpt message from the PCC to PCE reports the
updated path.
•
If a new path is not found, the process described above is repeated whenever the
adjust interval timer is triggered.
NorthStar Controller created LSPs—When an LSP is created from the NorthStar
Controller user interface, a template defines the autobandwidth attributes associated
with the LSP, which allows the PCC to treat the LSP as an auto-bandwidth LSP. All
other LSP behavior is the same as the NorthStar Controller managed LSP (as
described above).
•
LSP optimization—Analyze and optimize LSPs that have been delegated to the
NorthStar Controller. You can use the Path Analysis feature to manually trigger path
optimization from the NorthStar Controller user interface or use the Path Optimization
feature to automatically optimize paths based on user-defined time intervals.
•
Enable and disable LSP provisioning from the NorthStar Controller— You can enable
passive monitor mode from the NorthStar Controller CLI to globally disable provisioning
of LSPs for all NorthStar Controller users. You can also enable and disable LSP
provisioning (locally or globally) from the NorthStar Controller user interface. A
Copyright © 2015, Juniper Networks, Inc.
19
NorthStar Controller Getting Started Guide
NorthStar Controller administrator can disable provisioning of LSPs for all users by
navigating to the Tools > Options menu and selecting the Disable Provisioning check
box. A NorthStar Controller user with full access privileges can also disable provisioning
(for local user only) by navigating to the Tools > Options menu and selecting the Disable
Provisioning check box.
•
Schedule maintenance events—Select nodes and links for maintenance. When you
schedule a maintenance event on nodes or links, the NorthStar Controller routes
delegated LSPs around those nodes and links that are scheduled for maintenance.
After completion of the maintenance event, delegated LSPs are reverted back to
optimal paths.
•
Run simulations for scheduled maintenance events—Run simulations from the
NorthStar Controller on scheduled maintenance events for different failure scenarios
to test the resilience of your network, or run simulations before the event occurs.
Network simulation is based on the current network state for the selected maintenance
events at the time the simulation is initiated. Simulation does not simulate the
maintenance event for a future network state or simulate elements from other
concurrent maintenance events. You can run network simulations based on selected
elements for maintenance or extended failure simulations, with the option to include
exhaustive failures.
•
TE++ LSPs—A TE++ LSP includes a set of paths that are configured as a specific
container statement and individual LSP statements, called sub-LSPs, which all have
equal bandwidth.
For TE++ LSPs, a normalization process occurs that resizes the LSP when either of the
following two triggers initiates the normalization process:
•
A periodic timer
•
Bandwidth thresholds are met
When either of the preceding triggers are fired, one of the following events can occur:
•
No change is required
•
LSP splitting—add another LSP and distribute bandwidth across all the LSPs
•
LSP merging—delete an LSP and distribute bandwidth across all the LSPs
For a TE++ LSP, the NorthStar Controller displays a single LSP with a set of paths, and
the LSP name is based on the matching prefix name of all members. The correlation
between TE-LSPs is based on association, and the LSP is deleted when there is no
remaining TE LSP.
NOTE: TE++ is supported on PCC (router) controlled LSPs and delegated
LSPs, but TE++ LSPs cannot be created on the NorthStar Controller.
Related
Documentation
20
•
Understanding the NorthStar Controller on page 15
•
Understanding Network Topology Acquisition on the NorthStar Controller on page 31
Copyright © 2015, Juniper Networks, Inc.
Chapter 1: NorthStar Controller Overview
NorthStar Controller Installation and Configuration Overview
You can install the Juniper Networks NorthStar Controller ISO image on any bare-metal
x86 64-bit network appliance. Installing the NorthStar Controller for the first time requires
that you download and install the Juniper Networks SCL 6.5R3.0 and the JunosVM/PCS
RPM package, both of which are included in the NorthStar Controller ISO image.
After you successfully install the NorthStar Controller software on an x86 appliance, you
must establish a connection between the NorthStar Controller and the network, by
configuring Path Computation Element Protocol (PCEP) on each PE router to configure
the router as a Path Computation Client (PCC). A PCC supports the configurations related
to the Path Computation Element (PCE) and communicates with the NorthStar Controller
(PCE), which by default is configured to accept a PCEP connection from any source
address. After you have established communication between the NorthStar Controller
and the PCCs, you can configure topology acquisition using BGP-LS. For BGP-LS topology
acquisition, you must configure both the NorthStar Controller and the PCC routers.
NOTE:
We recommend that you use BGP-LS instead of IGP adjacency for topology
acquisition for the following reasons:
Related
Documentation
•
The OSPF and IS-IS database has a lifetime timer, and if the OSPF or IS-IS
neighbor is down, the OSPF or IS-IS database is not removed immediately,
and the NorthStar Controller will not be able to determine whether the
topology is valid or not.
•
Using BGP-LS will minimize the risk of making the JunosVM a transit router
between AS areas if the GRE metric is not properly configured.
•
Typically, the NorthStar Controller is located in a Network Operations
Center (NOC) Data Center and multihops away from the backbone routers
and MPLS TE routers.
•
Downloading the ISO Image for the NorthStar Controller and Creating a Bootable USB
or DVD Installer on page 23
•
Installing the ISO Image and NorthStar Controller Software from a USB or DVD Drive
on page 24
•
Connecting an x86 Network Appliance to the Network on page 25
Copyright © 2015, Juniper Networks, Inc.
21
NorthStar Controller Getting Started Guide
22
Copyright © 2015, Juniper Networks, Inc.
CHAPTER 2
Downloading and Installing the NorthStar
Controller Software
•
Downloading the ISO Image for the NorthStar Controller and Creating a Bootable USB
or DVD Installer on page 23
•
Installing the ISO Image and NorthStar Controller Software from a USB or DVD
Drive on page 24
•
Connecting an x86 Network Appliance to the Network on page 25
Downloading the ISO Image for the NorthStar Controller and Creating a Bootable USB
or DVD Installer
Complete the following steps to download and install the ISO image, which includes the
Juniper Networks SCL 6.5R3.0 and JunosVM/PCS RPM package.
1.
Access the hybrid ISO image at
https://www.juniper.net/beta/junos/beta4/NorthStar_01.00.00_150413_233420.iso,
and create a bootable USB flash drive or DVD that is at least 4 GB or larger.
The following tools are recommended:
•
To create a bootable USB flash drive:
•
For Windows installation, choose one of the following options:
•
Use Rawrite32 for Windows, which is available at
http://www.netbsd.org/~martin/rawrite32/help/rawrite32-en.htm
•
•
Use dd for Windows, which is available at http://www.chrysocome.net/dd
For Linux or OSX installation (from CLI):
dd if=northstar_usb4g_.xxxx.img of=/dev/sdX bs=1m conv=notrunc,noerror,sync
•
To create a DVD installer:
a. Use any ISO to DVD burning tool.
b. Select “Burn ISO”.
Copyright © 2015, Juniper Networks, Inc.
23
NorthStar Controller Getting Started Guide
NOTE: Do not mistakenly copy the ISO file to DVD, or the DVD will
not be bootable.
2. When the USB drive or DVD media has been prepared with the ISO image, place the
drive in an available slot on the x86 64-bit machine for installation and boot the
system.
Make sure that the system boots from the USB or DVD, and not from the existing
operating system.
CAUTION: If you select the wrong sdX or target device, you might
accidentally destroy your local hard drive.
3. Choose the appropriate media installation (USB or DVD), and if the installation is
performed using a serial console, choose the appropriate option.
Related
Documentation
•
Installing the ISO Image and NorthStar Controller Software from a USB or DVD Drive
on page 24
Installing the ISO Image and NorthStar Controller Software from a USB or DVD Drive
You can install the NorthStar Controller ISO image and KVM-related software on any
x86 64-bit network appliance.
Before you install the NorthStar Controller ISO image, complete the steps described in
“Downloading the ISO Image for the NorthStar Controller and Creating a Bootable USB
or DVD Installer” on page 23.
To install the ISO image on the x86 network appliance from a USB drive:
1.
Power on the x86 network appliance.
The northstar login prompt is displayed after you power on the appliance.
2. To break in to the BIOS, press the F11 key to invoke the boot menu.
The “Please select boot device” screen is displayed.
3. Use the Up/Down arrow keys on the keyboard to select the appropriate boot device
option (USB or CDROM) and press Enter.
4. Plug in the USB or DVD drive with the ISO image and NorthStar package to the x86
appliance.
5. When the “Welcome to SCL 6.5.R3.0” screen is displayed, select the appropriate Boot
option (the default is Install NorthStar from USB), and press Enter to start the NorthStar
Controller installation.
During this stage of the installation process, the Formatting screen is displayed.
24
Copyright © 2015, Juniper Networks, Inc.
Chapter 2: Downloading and Installing the NorthStar Controller Software
After approximately 14 minutes, the post installation scripts run for a few minutes and
displays the screen “Running post-installation scripts”.
When the package installation completes, the screen displays package installation
is 100% and that all packages are completed.
If the installation completes without any errors, the installer automatically shuts down
the server.
6. Disconnect the USB flash drive or DVD drive that is connected to the x86 network
appliance.
7. Power on the x86 network appliance.
The system requires a few minutes to power on, then the northstar login prompt is
displayed.
8. From the northstar login prompt, enter user root and password northstar to log in to
the NorthStar Controller CLI.
9. After the installation of the NorthStar Controller software completes, run each of the
following commands to verify that the JunosVM and Path Computation Server (PCS)
processes are running and that key directories were successfully installed:
a. As root user, run the virsh list command to verify that JunosVM is running.
b. Run the ps-ef | grep PCS command to verify that the PCS is running on specific
ports.
Related
Documentation
•
Connecting an x86 Network Appliance to the Network on page 25
Connecting an x86 Network Appliance to the Network
To establish basic TCP connectivity to the network, you must connect your x86 64-bit
network appliance (running the NorthStar Controller software) directly to a switch or
router.
Before configuring the x86 appliance to connect to the network:
Download the ISO image (which includes the NorthStar RPM package) as described
in “Downloading the ISO Image for the NorthStar Controller and Creating a Bootable
USB or DVD Installer” on page 23.
1.
2. Install the ISO image on the x86 64-bit machine that you will use to connect to the
network as described in “Installing the ISO Image and NorthStar Controller Software
from a USB or DVD Drive” on page 24.
After installing the ISO image, the following default settings apply:
•
Host machine:
•
User=root
•
Password=northstar
Copyright © 2015, Juniper Networks, Inc.
25
NorthStar Controller Getting Started Guide
•
IP addresses:
•
external0=dhcp
•
host mgmt0=172.16.17.1/24
•
host management:internal network=172.16.16.1/24
NOTE: The Path Computation Server (PCS) runs native on the host
machine, and the host address is the PCS.
•
JunosVM:
•
User=northstar
•
Password=northstar
•
Root Password=northstar
•
IP addresses:
•
em0=172.16.16.2/24
•
em1=none
•
em2=172.16.17.2/24
NOTE:
The following default values are also configured for the JunosVM
configuration:
•
JunosVM internal IP address: 172.16.16.2
•
JunosVM internal netmask: 255.255.255.0
NOTE: The JunosVM internal IP and netmask should not be
changed.
•
JunosVM management IP address: 172.16.17.2
•
JunosVM default gateway: 192.25.152.1
NOTE: For network security, by default, JunosVM SSH and telnet access is
restricted and available only from the host server (PCS server) via the
172.16.16.2 IP address. To remove this restriction, you can manually remove
the firewall filter on the JunosVM lo0 (loopback) configuration.
Figure 2 on page 27 shows the default interfaces and preconfigured addresses on the
x86 appliance.
26
Copyright © 2015, Juniper Networks, Inc.
Chapter 2: Downloading and Installing the NorthStar Controller Software
Figure 2: Interfaces and Addresses Preconfigured on the x86 Appliance
To establish basic connectivity between the x86 network appliance and a switch or
router:
1.
Power on the x86 network appliance.
2. Use one of the following options to access the x86 console:
•
Use a serial cable to connect to the serial console.
You can use an SSH client (hypertem, minicom, or securecrt) to connect to the
serial console.
NOTE: To set up the serial port connection, refer to your hardware
manual.
NOTE: The serial port setting should be 9600-8-N-1 with hardware
control enabled.
Copyright © 2015, Juniper Networks, Inc.
27
NorthStar Controller Getting Started Guide
•
If your network appliance has two or more Ethernet ports, use an Ethernet cable to
connect to the x86 appliance management interface.
a. Connect an Ethernet cable from a laptop computer to 1 GE port 1 on the x86
appliance.
b. Configure the IP address on your laptop to 172.16.17.10/24.
c. Using an SSH client, connect to the x86 appliance at 172.16.17.1.
3. On the network appliance, connect a 1 GbE or 10 GbE port to the LAN switch or router
that you will use to access the network.
NOTE: The Ethernet interface on the switch or router must be configured
in access/untagged mode.
4. From the northstar prompt, log in to the x86 system with the username root and
password northstar.
5. To configure the required network settings, access the Main Menu:
[root@northstar ~]# /opt/northstar_junosvm/net_setup.sh
The Main Menu, shown in Figure 3 on page 28, displays the options that you can select
to configure the host and JunosVM settings, verify network settings, perform
maintenance and troubleshooting, and collect trace and log files.
Figure 3: NorthStar Controller Main Menu
NOTE: To establish connectivity between the x86 network appliance and
a switch or router, the host IP and JunosVM IP addresses (including
netmask and default gateway) must be from the same subnet.
a. To create the host configuration:
28
Copyright © 2015, Juniper Networks, Inc.
Chapter 2: Downloading and Installing the NorthStar Controller Software
NOTE: You must provide settings for the host external IP address, host
external netmask, and host default gateway. All other host settings
are optional.
1.
Type A at the prompt and press Enter to update the host configuration.
The current NorthStar Controller host configuration settings are displayed.
2. For each host setting you want to configure, enter the number that corresponds
to the specific host parameter (host external IP address, host external netmask,
host management IP address, host default gateway, and so forth), and enter
the appropriate value.
3. After you configure the required host settings, type B to apply the host settings.
b. To create the JunosVM configuration:
NOTE: You must provide settings for the JunosVM external IP address,
JunosVM external netmask, JunosVM default gateway, and BGP AS
number. All other JunosVM settings are optional.
1.
Type B at the prompt and press Enter to update the NorthStar JunosVM
configuration.
The current JunosVM configuration settings are displayed.
2. For each JunosVM setting you want to configure, enter the number that
corresponds to the specific JunosVM parameter (JunosVM external IP address,
JunosVM external netmask, JunosVM management IP address, JunosVM default
gateway, and BGP AS number), and enter the appropriate value.
Copyright © 2015, Juniper Networks, Inc.
29
NorthStar Controller Getting Started Guide
3. After configuring the required JunosVM settings, type C to apply the JunosVM
settings.
6. Verify the host and JunosVM configurations and deploy.
a. Type C at the prompt and press Enter to view all current host configuration and
JunosVM configuration settings.
b. To apply all updated host and JunosVM configuration settings to the NorthStar
Controller, type Y and press Enter.
NOTE:
The NorthStar Controller requires the following TCP ports:
Related
Documentation
30
•
TCP 179 for BGP (between network devices and NorthStar Controller)
•
TCP 4189 for PCEP (between network devices and NorthStar Controller)
•
TCP 3389, TCP 7000, TCP 7003, TCP 8091, TCP 8443 for the NorthStar
Controller user interface
•
Configuring Connectivity for BGP-LS Topology Acquisition on page 36
•
Configuring Connectivity for OSPF Topology Acquisition on page 38
•
Configuring Connectivity for IS-IS Topology Acquisition on page 40
Copyright © 2015, Juniper Networks, Inc.
CHAPTER 3
Configuring Topology Acquisition and
Connectivity Between the NorthStar
Controller and Path Computation Clients
•
Understanding Network Topology Acquisition on the NorthStar Controller on page 31
•
Configuring PCEP on a PE Router (from CLI) on page 33
•
Mapping a Management IP Address for Path Computation Clients on page 35
•
Configuring Connectivity for BGP-LS Topology Acquisition on page 36
•
Configuring Connectivity for OSPF Topology Acquisition on page 38
•
Configuring Connectivity for IS-IS Topology Acquisition on page 40
Understanding Network Topology Acquisition on the NorthStar Controller
After you use BGP-LS to establish BGP peering between the NorthStar Controller and a
Path Computation Client (PCC) in the network, the NorthStar Controller acquires real-time
topology changes, which are recorded in the traffic engineering database (TED). To
compute optimal paths through the network, the NorthStar Controller requires a
consolidated view of the network topology. This routing view of the network includes the
nodes, links, and their attributes (metric, link utilization bandwidth, and so forth) that
comprise the network topology. Thus, any router CLI configuration changes to IGP metric,
RSVP bandwidth, Priority/Hold values, and so forth are instantly available from the
NorthStar Controller user interface topology view.
To provide a network view, the NorthStar Controller runs Junos in a virtual machine
(JunosVM) that uses routing protocols to communicate with the network and dynamically
learn the network topology. To provide real-time updates of the network topology, the
JunosVM, which is based on a virtual Route Reflector (vRR), establishes a BGP-LS peering
session with one or more routers from the existing MPLS TE backbone network. A router
from the MPLS TE backbone advertises its traffic engineering database (TED) in BGP-LS.
The NorthStar Controller JunosVM receives real-time BGP-LS updates and forwards this
topology data into the Network Topology Abstractor Daemon (NTAD), which is a server
daemon that runs in the JunosVM.
The NorthStar Controller stores network topology data in the following routing tables:
•
lsdist.0—stores the network topology from TED
Copyright © 2015, Juniper Networks, Inc.
31
NorthStar Controller Getting Started Guide
•
lsdist.1—stores the network topology from IGP database
NTAD then forwards a copy of the updated topology information to the Path Computation
Server (PCS), which displays the live topology update from the NorthStar Controller user
interface.
To provide a real-time topology update of the network, you can configure direct ISIS/OSPF
adjacency between NorthStar Controller and an existing MPLS TE backbone router, but
Juniper recommends that you use BGP-LS rather than direct IGP adjacency or IGP
adjacency over GRE.
NOTE:
The current BGP-LS implementation only considers TED information, and
some IGP-specific attributes might not be forwarded during topology
acquisition. The following IGP attributes are not forwarded:
•
ISIS area
•
ISIS host name
•
Link net mask
•
IGP metric (TED provides TE metric only).
In some cases, using ISIS or OSPF adjacency instead of BGP-LS might produce
stale data because ISIS and OSPF have a database lifetime period that is
not automatically cleared when the adjacency is down. In this case, NTAD
will export all information in the OSPF or ISIS database to the NorthStar Path
Computation Server (PCS), so the NorthStar Controller might show incorrect
topology.
Related
Documentation
32
•
Understanding the NorthStar Controller on page 15
•
Configuring Connectivity for BGP-LS Topology Acquisition on page 36
•
Configuring Connectivity for IS-IS Topology Acquisition on page 40
•
Configuring PCEP on a PE Router (from CLI) on page 33
•
Configuring Connectivity for OSPF Topology Acquisition on page 38
Copyright © 2015, Juniper Networks, Inc.
Chapter 3: Configuring Topology Acquisition and Connectivity Between the NorthStar Controller and Path Computation Clients
Configuring PCEP on a PE Router (from CLI)
A Path Computation Client (PCC) supports the configurations related to the Path
Computation Element (PCE) and communicates with the NorthStar Controller, which
by default is configured to accept a Path Computation Element Protocol (PCEP)
connection from any source address. However, you must configure PCEP on each PE
router to configure the router as a PCC and establish a connection between the PCC and
the NorthStar Controller. A PCC initiates path computation requests, which are then
executed by the NorthStar Controller.
The following requirements apply for each PCC in the network that the NorthStar
Controller can access:
•
Junos OS Release 14.2X1 (jinstall 32 bit) runs on the router
•
JSDN package (with PCE protocol support) is installed on the router
NOTE: You must boot the PCC router with the Junos OS 14.2 image, and then
boot the router a second time with the JSDN image. After the router boots
up a second time, the router (functioning as a PCC) is able to support the
configurations related to the PCE and communicate with the NorthStar
Controller.
NOTE: For a PCEP connection, the PCC can connect to the NorthStar
Controller using an in-band or out-of-band management network, provided
that IP connectivity is established between the Path Computation Server
(PCS) and the specified PCEP local-address. In some cases, an additional
static route might be required from the NorthStar Controller to reach the
PCC, if the IP address is unreachable from the NorthStar Controller default
gateway.
To configure a PE router as a PCC:
1.
Enable external control of LSPs from the PCC router to the NorthStar Controller.
[edit protocols]
user@PE1# set mpls lsp-external-controller pccd
2. Specify the loopback address of the PCC router as the local address, for example:
[edit protocols]
user@PE1# set pcep pce northstar1 local-address 10.0.0.101
NOTE: As a best practice, the router ID is usually the loopback address,
but is not necessarily configured this way.
Copyright © 2015, Juniper Networks, Inc.
33
NorthStar Controller Getting Started Guide
3. Specify the NorthStar Controller (northstar1) as the PCE that the PCC connects to,
and specify the NorthStar Controller host external IP address as the destination
address.
[edit protocols]
user@PE1# set pcep pce northstar1 destination-ipv4-address 10.99.99.1
4. Configure the destination port for the PCC router that connects to the NorthStar
Controller (PCE server) using the TCP-based PCEP.
[edit protocols]
user@PE1# set pcep pce northstar1 destination-port 4189
5. Configure the PCE type.
[edit protocols]
user@PE1# set pcep pce northstar1 pce-type active
user@PE1# set pcep pce northstar1 pce-type stateful
6. Enable LSP provisioning.
[edit protocols]
user@PE1# set pcep pce northstar1 lsp-provisioning
7. To verify that PCEP has been configured on the router, open a telnet session to access
the router, and run the following commands:
user@PE1> show configuration protocols mpls
Sample output:
lsp-external-controller pccd;
user@PE1> show configuration protocols pcep
Sample output:
pce northstar1 {
local-address 10.0.0.101;
destination-ipv4-address 10.99.99.1;
destination-port 4189;
pce-type active-stateful;
lsp-provisioning;
}
Related
Documentation
34
•
Configuring Connectivity for BGP-LS Topology Acquisition on page 36
•
Configuring Connectivity for IS-IS Topology Acquisition on page 40
•
Mapping a Management IP Address for Path Computation Clients on page 35
Copyright © 2015, Juniper Networks, Inc.
Chapter 3: Configuring Topology Acquisition and Connectivity Between the NorthStar Controller and Path Computation Clients
Mapping a Management IP Address for Path Computation Clients
You can access the Management IP Mapping window to map a management IP address
for a Path Computation Client (PCC) directly from the NorthStar Controller user interface.
A PCC supports the configurations related to the Path Computation Element (PCE) and
communicates with the NorthStar Controller, which by default is configured to accept
a PCEP connection from any source address.
Before you begin, you must perform the configuration steps described in “Configuring
PCEP on a PE Router (from CLI)” on page 33 to configure the PE router as a PCC and
establish a connection between the PCC and the NorthStar Controller.
To map a management IP address for a Path Computation Client (PCC) to the NorthStar
Controller:
1.
From the NorthStar Controller landing page, select Management IP Mapping.
The Management IP Mapping window is displayed.
2. To import the IP addresses of all routers configured as PCCs that are connected to
the NorthStar Controller, select Import IP from Server.
The router ID of each PCC for which connectivity has been established with the
NorthStar Controller is displayed from the Management IP Mapping main window.
3. Double-click on the row that lists the PCC on which you want to map a management
IP address.
The table row of the PCC that you selected is highlighted, as shown in
Figure 4 on page 35.
Figure 4: Selecting a PCC to Map a Management IP Address
4. In the Management IP field, enter a management IP address for the PCC.
5. In the Host name field, enter a name for the PCC.
6. Click OK to continue.
Copyright © 2015, Juniper Networks, Inc.
35
NorthStar Controller Getting Started Guide
7. Repeat Steps 3 through 6 for each PCC for which you want to map a Management IP
address.
8. Click Push Update to apply the mapping changes to the NorthStar Controller.
The Management IP Mapping window includes the following options:
•
Import IP from Server—Imports the router-id of each PCC
•
Reload—Loads the current Management IP Mapping settings
•
Push Update—Applies the settings in the table to the NorthStar Controller.
•
Add a Router—Allows a user to manually add an individual router, if it cannot be
imported from the server.
•
Remove Router—Removes the router entry from the Management IP Mapping table,
but requires that you use the Push Update option to apply the changes to the table.
•
Ping Routers—Pings the routers in the table. The Connectivity icon color indicates
whether or not the router is reachable.
•
Clear Table—Removes all router entries from the table, but you must select Push Update
to apply the changes to the table.
Related
Documentation
•
Configuring PCEP on a PE Router (from CLI) on page 33
Configuring Connectivity for BGP-LS Topology Acquisition
After you have successfully established a connection between the NorthStar Controller
and the network, you can configure topology acquisition using Border Gateway Protocol
Link State (BGP-LS). For BGP-LS topology acquisition, you must configure both the
NorthStar Controller and the PCC routers.
NOTE:
We recommend that you use BGP-LS instead of IGP adjacency for the
following reasons:
36
•
The OSPF and IS-IS databases have a lifetime timer, and if the OSPF or
IS-IS neighbor is down, the OSPF or IS-IS database is not removed
immediately, and the NorthStar Controller will not be able to determine
whether the topology is valid or not.
•
Using BGP-LS minimizes the risk of making the JunosVM a transit router
between AS areas if the GRE metric is not properly configured.
•
Typically, the NorthStar Controller is located in a NOC Data Center and
multihops away from the backbone routers and MPLS TE routers.
Copyright © 2015, Juniper Networks, Inc.
Chapter 3: Configuring Topology Acquisition and Connectivity Between the NorthStar Controller and Path Computation Clients
NOTE: If BGP-LS is used, JunosVM is configured to automatically accept any
I-BGP session from, in this example, 0.0.0.0/0. However, you must verify
that JunosVM is correctly configured and that it has IP reachability to the
peering router.
Before you begin, complete the following tasks:
•
Verify IP connectivity between a switch (or router) and the x86 appliance on which
NorthStar Controller software is installed.
•
Make sure that PCEP is configured on each PE router in the network topology.
To configure BGP-LS topology acquisition, see:
•
Configuring BGP-LS Topology Acquisition on the NorthStar Controller on page 37
•
Configuring Topology Acquisition on the PCC Routers on page 38
Configuring BGP-LS Topology Acquisition on the NorthStar Controller
To configure BGP-LS on the NorthStar Controller for topology acquisition, perform the
following configuration steps from the NorthStar JunosVM:
1.
Initiate an SSH or telnet session to the JunosVM external IP or management IP address.
2. Specify the autonomous system (AS) number for the node (BGP peer).
[edit routing-options]
user@northstar_junosvm# set autonomous-system AS_number
3. Specify the BGP group name and type for the node.
[edit protocols bgp]
user@northstar_junosvm# set group group_1 type internal
4. Specify a description for the BGP group for the node.
[edit protocols bgp group group_1]
user@northstar_junosvm# set description “NorthStar BGP-TE Peering”
5. Specify the address of the local end of a BGP session.
This is the IP address for the JunosVM external IP address which is used to accept
incoming connections to the JunosVM peer and to establish connections to the remote
peer.
[edit protocols bgp group group_1]
user@northstar_junosvm# set local-address <junosVM IP address>
6. Enable the traffic engineering features for the BGP routing protocol.
[edit protocols bgp group group_1]
user@northstar_junosvm# set family traffic-engineering unicast
7. Specify the IP address for the neighbor router that connects with the NorthStar
Controller.
[edit protocols bgp group group_1]
Copyright © 2015, Juniper Networks, Inc.
37
NorthStar Controller Getting Started Guide
user@northstar_junosvm# set neighbor <router loopback IP address>
NOTE: You can specify the router loopback address if it is reachable by
the BGP peer on the other end. But for loopback to be reachable, usually
some IGP has to be enabled between the NorthStar JunosVM and the peer
on the other end.
Configuring Topology Acquisition on the PCC Routers
To enable the NorthStar Controller to discover the network, you must add the following
configuration on each each router that peers with the NorthStar Controller. The NorthStar
JunosVM must peer with at least one router from each area (autonomous system).
To configure topology acquisition, initiate a telnet session to each PCC router and add
the following configuration:
1.
Configure a policy to import TED into BGP.
[edit policy-options]
user@PE1# set policy-statement policy_1 term 1 from protocol isis
user@PE1# set policy-statement policy_1 term 1 then accept
NOTE: You can specify IS-IS or OSPF in the from protocol statement.
2. Import the policy into the traffic-engineering database.
[edit protocols mpls traffic-engineering database]
user@PE1# set import policy policy_1
3. Configure a BGP group by specifying the IP address of the router that peers with the
NorthStar Controller as the local address (typically the loopback address) and the
JunosVM external IP address as the neighbor.
[edit protocols bgp group group_1]
user@PE1# set type internal
user@PE1# set description “NorthStar BGP-TE Peering”
user@PE1# set local-address <router-IP-address>
user@PE1# set family traffic-engineering unicast
user@PE1# set export policy_1
user@PE1# set neighbor <JunosVM IP-address>
Related
Documentation
•
Configuring PCEP on a PE Router (from CLI) on page 33
•
Configuring Connectivity for IS-IS Topology Acquisition on page 40
•
Configuring Connectivity for OSPF Topology Acquisition on page 38
Configuring Connectivity for OSPF Topology Acquisition
If BGP-LS is not being used, one of the IGP protocols must be configured on the NorthStar
Controller. To enable OSPF on NorthStar, beore you begin, verify IP connectivity between
38
Copyright © 2015, Juniper Networks, Inc.
Chapter 3: Configuring Topology Acquisition and Connectivity Between the NorthStar Controller and Path Computation Clients
a switch (or router) and the x86 appliance on which NorthStar Controller software is
installed.
To configure OSPF topology acquisition, see:
•
Configuring OSPF on the NorthStar Controller on page 39
•
Configuring OSPF Over GRE on the NorthStar Controller on page 39
Configuring OSPF on the NorthStar Controller
To configure OSPF on the NorthStar Controller:
1.
Add the traffic engineering policy to import OSPF data to the NorthStar Controller.
[edit protocols ospf]
user@northstar_junosvm# set traffic-engineering
2. Configure an interface in OSPF passive traffic engineering mode to enable dynamic
discovery of OSPF AS boundary routers, and add the interfaces that you configured
to the OSPF area.
[edit protocols ospf]
user@northstar_junosvm# set area 0.0.0.0 interface lo0.0 passive
user@northstar_junosvm# set area 0.0.0.0 interface em2.0
Configuring OSPF Over GRE on the NorthStar Controller
To configure OSPF over GRE on the NorthStar Controller:
1.
Initiate an SSH or telnet session using the IP address for the NorthStar JunosVM
external IP address.
2. Enable OSPF traffic engineering on the JunosVM.
[edit protocols ospf]
user@northstar_junosvm# set traffic-engineering
3. Configure the OSPF area and interfaces.
NOTE: The area does not have to be 0.0.0.0.
[edit protocols ospf]
user@northstar_junosvm# set area 0.0.0.0 interface em2.0
user@northstar_junosvm# set area 0.0.0.0 interface gre.0 metric 65530
4. Configure the GRE tunnel interfaces by including the unit statements.
[edit interfaces gre]
user@northstar_junosvm# set unit 0 tunnel source 10.105.199.2
user@northstar_junosvm# set unit 0 tunnel destination 10.0.0.101
user@northstar_junosvm# set unit 0 family inet address 10.110.199.2/30
5. Configure the family inet and address.
[edit interfaces gre]
user@northstar_junosvm# set unit 0 family inet address 10.110.199.2/30
Copyright © 2015, Juniper Networks, Inc.
39
NorthStar Controller Getting Started Guide
6. Configure the MPLS family.
[edit interfaces gre]
user@northstar_junosvm# set unit 0 family mpls
7. Import the policy into the traffic-engineering database.
[edit protocols mpls]
user@northstar_junosvm# set traffic-engineering database import policy ospf_te
8. Configure the GRE interfaces.
[edit interfaces gre]
user@northstar_junosvm# set interface lo0.0
user@northstar_junosvm# set interface gre.0
9. Configure the OSPF GRE policy.
[edit policy-options ]
user@northstar_junosvm# set policy-statement ospf_te
user@northstar_junosvm# set term 1 from protocol ospf
user@northstar_junosvm# set term 1 to family traffic-engineering
user@northstar_junosvm# set term 1 then accept
Related
Documentation
•
Configuring Connectivity for BGP-LS Topology Acquisition on page 36
•
Configuring Connectivity for IS-IS Topology Acquisition on page 40
•
Configuring PCEP on a PE Router (from CLI) on page 33
Configuring Connectivity for IS-IS Topology Acquisition
If BGP-LS is not being used, you must configure one of the IGP protocols on the NorthStar
Controller. To enable IS-IS on the Northstar Controller, before you begin, complete the
following tasks:
1.
Verfiy IP connectivity between a switch (or router) and the x86 appliance on which
NorthStar Controller software is installed.
2. Configure interfaces on the JunosVM for IS-IS routing, for example:
[edit]
user@northstar_junosvm# set interfaces em0 unit 0 family inet address 172.16.16.2/24
user@northstar_junosvm# set interfaces em1 unit 0 family inet address
192.168.179.117/25
user@northstar_junosvm# set interfaces em0 unit 0 family inet address 172.16.16.2/24
user@northstar_junosvm# set interfaces em2 unit 0 family mpls
user@northstar_junosvm# set interfaces lo0 unit 0 family inet address 88.88.88.88/32
primary
user@northstar_junosvm# set routing-options static route 0.0.0.0/0 next-hop
192.168.179.126
user@northstar_junosvm# set routing-options autonomous-system 1001
To configure IS-IS topology acquisition, see:
40
•
Configuring IS-IS on the NorthStar Controller on page 41
•
Configuring IS-IS Over GRE on the NorthStar Controller on page 41
Copyright © 2015, Juniper Networks, Inc.
Chapter 3: Configuring Topology Acquisition and Connectivity Between the NorthStar Controller and Path Computation Clients
Configuring IS-IS on the NorthStar Controller
To configure IS-IS topology acquisition and enable IS-IS routing, perform the following
steps on the NorthStar JunosVM:
1.
Initiate an SSH or telnet session using the IP address for the NorthStar JunosVM
gateway (JunosVM eternal IP address).
Enable the NTAD daemon and propogate entries in the lsdist.0 table to the NorthStar
Controller.
[edit protocols]
user@northstar_junosvm# set topology-export
2. Configure interface-specific IS-IS properties on the JunosVM interfaces.
[edit protocols isis]
user@northstar_junosvm# set interface em2.0
user@northstar_junosvm# set interface lo0.0
3. Configure the interface in passive mode.
[edit protocols isis]
user@northstar_junosvm# set interface em2.0 passive
user@northstar_junosvm# set interface lo0.0 passive
Configuring IS-IS Over GRE on the NorthStar Controller
To configure IS-IS over GRE topology acquisition and enable IS-IS routing, perform the
following steps on the NorthStar JunosVM:
1.
Initiate an SSH or telnet session using the IP address for the NorthStar JunosVM
external IP address.
2. Configure the GRE tunnel interface by including the unit statements.
[edit interfaces gre]
user@northstar_junosvm# set unit 0 tunnel source 10.105.199.2
user@northstar_junosvm# set unit 0 tunnel destination 10.0.0.101
3. Configure the family inet and address.
[edit interfaces gre]
user@northstar_junosvm# set unit 0 family inet address 10.110.199.2/30
4. Configure the MPLS family.
[edit interfaces gre]
user@northstar_junosvm# set unit 0 family mpls
5. Configure the IS-IS properties.
[edit protocols isis]
user@northstar_junosvm# set level 1 disable
user@northstar_junosvm# set level 2 wide-metrics-only
6. Configure interface-specific IS-IS properties.
[edit protocols isis]
user@northstar_junosvm# set interface gre.0 point-to-point
Copyright © 2015, Juniper Networks, Inc.
41
NorthStar Controller Getting Started Guide
user@northstar_junosvm# set interface gre.0 level 2 metric 65535
user@northstar_junosvm# set interface lo0.0
7. Configure interface-specific IS-IS properties on the loopback interface.
[edit protocols isis]
user@northstar_junosvm# set interface lo0.0 passive
Related
Documentation
42
•
Connecting an x86 Network Appliance to the Network on page 25
•
Configuring Connectivity for BGP-LS Topology Acquisition on page 36
•
Configuring Connectivity for OSPF Topology Acquisition on page 38
•
Configuring PCEP on a PE Router (from CLI) on page 33
Copyright © 2015, Juniper Networks, Inc.
CHAPTER 4
Accessing the User Interface
•
NorthStar Controller User Interface Overview on page 43
•
Logging In to the NorthStar Controller User Interface on page 47
•
Logging Out of the NorthStar Controller User Interface on page 50
•
Logging In as the NorthStar Controller Administrator on page 50
NorthStar Controller User Interface Overview
In this release, only a single user can launch the NorthStar Controller user interface client
to view the live network. Multiple concurrent users can access NorthStar Simulation (an
offline model) but cannot access the NorthStar Controller live view. All users have access
to the same information, but only a NorthStar administrator can perform tasks in the
NorthStar Controller user interface. This topic describes some of the elements displayed
from the main window from which all NorthStar Controller software application windows
are launched or opened.
•
NorthStar Controller User Interface on page 43
•
Menu Options for the NorthStar Controller User Interface on page 45
•
RSVP Live Util Legend on page 46
•
Customizing Nodes and Links in the Map Legends on page 46
NorthStar Controller User Interface
To access the NorthStar Controller user interface, in the address bar of your browser
window, type the host external IP address, followed by port number 8091.
Figure 5 on page 44 shows the initial landing page for the NorthStar Controller, from
which you can log in to the NorthStar Controller to view the network topology and perform
tasks.
Copyright © 2015, Juniper Networks, Inc.
43
NorthStar Controller Getting Started Guide
Figure 5: NorthStar Controller Initial Landing Page
After you log in to the NorthStar Controller, the NorthStar Controller main window shows
the Map, Console, and Network Info panes, as shown in Figure 6 on page 45. However,
many standard functions and features do not become available until a network topology
is loaded. This includes some of the menus as well as the topology view from the Map.
44
Copyright © 2015, Juniper Networks, Inc.
Chapter 4: Accessing the User Interface
Figure 6: NorthStar Controller Main Window
NOTE: To refresh the network view, click Update at the top left corner of the
window under the toolbar.
Menu Options for the NorthStar Controller User Interface
Table 3 on page 45 describes the options available from the main window.
Table 3: Menu Options for the NorthStar User Interface
Menu Option
Description
Application
The Application menu shows a calendar view of maintenance events and provides path optimization
information.
File
The File menu contains network file functions such as opening the File Manager, loading network files,
and exiting the user interface.
Help
The Help menu provides basic system information, including NorthStar product version, server version
and IP address, operating system information, and Java virtual machine (JVM) details.
Network
The Network menu includes network summary information (network elements, LSP placement, LSP
types, Hop counts, and LSP bandwidth).
Copyright © 2015, Juniper Networks, Inc.
45
NorthStar Controller Getting Started Guide
Table 3: Menu Options for the NorthStar User Interface (continued)
Tools
The Tools menu includes general options to monitor network progress, show login/logout activities,
configure the interval between keep-alive messages, and specify network map preferences.
An Admin user can also connect to the NorthStar server and perform NorthStar user administration
tasks.
Windows
The Windows menu provides options to display, hide, or reset the Map, Console, and Network Info
windows of the NorthStar user interface.
RSVP Live Util Legend
Notice in the left pane that there is a drop-down menu to configure the map view. By
default, the RSVP Live Util legend is displayed. The RSVP (Live) Util view allows you to
configure the link color based on utilization. The scale of colors can be configured in this
section. By default, 0% to 25% RSVP utilization appears as dark blue, 25% to 50%
appears as light blue, 50% to 75% appears as green, 75% to 90% appears as magenta,
and 90% to 100% appears as red. Both the colors and the range of utilization can be
changed and added. A right click on the scale provides access to the menu for configuring
the scale (Edit Color, Add Divider, and so forth).
Notice that some of the links are solid in color and some of them are half one color and
half another color. The presence of two different colors indicates that the utilization in
one direction (A->Z) is different from the utilization in the other direction (Z->A). The
half of the link originating from a certain node is colored according to the link utilization
in the direction from that node to the other node.
On the color bar, drag the separator between two colors up and down to move the
separator and release it at the desired position. The number to the right of the separator
indicates the utilization percentage corresponding to the selected position. For example,
move the separator between the dark-blue segment and light-blue segment of the bar
(currently at 25.0%) up to 40.0% and notice that some formerly light-blue links will
change to dark-blue if there are some links of utilization between 25% and 40%, and
that the color for that portion of the bar is changed.
Customizing Nodes and Links in the Map Legends
From the RSVP Util drop-down menu, you can use the following four submenus (Filters,
Network Elements, Utilization Legends, and Subviews).
46
•
Select Subviews > Types. Select the drop-down menu a second time and notice that
the Subviews submenu is now shown with the selected option button on its left, and
the items underneath it are provided as a shortcut to other menu items in the same
category. To view other information such as the vendor and media information, click
the relevant item from the list.
•
Note that each legend has its own color settings. Some legends, such as “RSVP Util”,
change link colors, but leave the node colors the same as for the previous legend. Other
legends change the node colors, but not the link colors. Others, such as “Types”, change
both.
Copyright © 2015, Juniper Networks, Inc.
Chapter 4: Accessing the User Interface
Related
Documentation
•
Colors can be changed by clicking the button next to the type of element you want to
change.
•
In addition to colors, node icons and line styles (for example, solid vs. dotted) can be
changed by right-clicking one of the buttons for nodes or links. For node icons, the
menu is Set This Icon and for link styles it is Set Line Style. The setting applies when
the particular legend in which you set the line style is open.
•
Right-click a node or link icon in the left pane. Notice that the menu item Highlight
These Items can be used to highlight all nodes (or links) of a particular type.
•
Understanding the NorthStar Controller on page 15
•
Logging In to the NorthStar Controller User Interface on page 47
Logging In to the NorthStar Controller User Interface
You connect to the NorthStar Controller from your Web browser. The Microsoft Internet
Explorer, Mozilla Firefox, and Google Chrome Web browsers are supported.
WARNING: To avoid a Browser Exploit Against SSL/TLS (BEAST) attack,
whenever you log in to NorthStar Controller through a browser tab or window,
make sure that the tab or window was not previously used to surf a
non-HTTPS website. A best practice is to close your browser and relaunch
it before logging in to the NorthStar Controller.
NOTE: A user who is idle and has not performed any actions (keystrokes or
mouse clicks) is automatically logged out of the NorthStar Controller.
NOTE: The NorthStar Controller supports single-user sign on that provides
one user with access to all features of the NorthStar Controller user interface.
To log in to the NorthStar Controller user interface:
1.
In the address bar of your browser window, type the host external IP address, followed
by port number 8091, for example:
http://172.25.153.29:8091
The initial landing page for the NorthStar Controller user interface is displayed.
2. From the initial page, select Launch NorthStar to log in to the NorthStar Controller
user interface.
Copyright © 2015, Juniper Networks, Inc.
47
NorthStar Controller Getting Started Guide
NOTE: To log in as the NorthStar administrator, at the top right corner of
the window , select Admin to log in as the NorthStar administrator. An
administrator can perform all tasks from the network topology, view
system logs, view system processes, collect debug traces, and map router
management IP addresses.
3. From the Launch Java Client screen, select Run NorthStar.
NOTE: The NorthStar Controller application takes a minute or more to
load.
The Juniper NorthStar Controller User Login screen is displayed as shown in
Figure 7 on page 48.
Figure 7: NorthStar Controller User Login
4. Type admin for both the User ID and Password fields, and click Login.
NOTE: You can change the default login password from the User
Administration window.
By default, the NorthStar Controller main window displays the Map, Console, and
Network Info views, as shown in Figure 8 on page 49. However, many functions and
features do not become available until a network topology is loaded. This includes
some of the menus as well as the topology window.
48
Copyright © 2015, Juniper Networks, Inc.
Chapter 4: Accessing the User Interface
Figure 8: NorthStar Controller Main Window
5. a. (Optional) Refresh the network view at any time by clicking Update at the top left
under the toolbar.
The Update Options dialog box is displayed, as shown in Figure 9 on page 49.
Figure 9: Update Options Dialog Box
b. Select the appropriate update option and click OK.
Copyright © 2015, Juniper Networks, Inc.
49
NorthStar Controller Getting Started Guide
The network topology is updated, and information in the Map view and Network
Info tables are refreshed.
Related
Documentation
•
Logging Out of the NorthStar Controller User Interface on page 50
•
Logging In as the NorthStar Controller Administrator on page 50
•
NorthStar Controller User Interface Overview on page 43
Logging Out of the NorthStar Controller User Interface
After you have finished working in the NorthStar Controller user interface, log out to
prevent unauthorized users from accessing your network data.
To log out of the NorthStar Controller user interface:
1.
Select File > Exit.
The Confirm Exit screen is displayed.
2. Click Yes to exit the NorthStar user interface.
Related
Documentation
•
Logging In to the NorthStar Controller User Interface on page 47
•
Logging In as the NorthStar Controller Administrator on page 50
Logging In as the NorthStar Controller Administrator
To perform administrative tasks on the NorthStar Controller, you must log in using the
administrator role. As administrator, you can perform the following tasks:
•
Access and view system log files and system processes the NorthStar Controller.
•
Collect debug traces to identify issues with the NorthStar Controller software.
•
Disable provisioning of label-switched paths.
•
Configure a management IP address for each Path Computation Client (PCC) that has
IP connectivity established with the NorthStar Controller.
To log in to the NorthStar Controller as the administrator:
1.
In the address bar of your Web browser window, type the host external IP address
followed by port number 8091, for example:
http://172.25.153.29:8091
2. Select Admin at the top right corner of the main window.
The Login screen is displayed, as shown in Figure 10 on page 51.
50
Copyright © 2015, Juniper Networks, Inc.
Chapter 4: Accessing the User Interface
Figure 10: NorthStar Controller Administrator Login Dialog Box
3. In the User Name field, type admin.
4. In the Password field, type admin.
5. Click Submit.
By default, NorthStar system log files are displayed.
As administrator, you can perform the following actions:
•
View system log files.
•
View information about system processes (NPAT,NODEJS, LDAP, PCSERVER,
TOPOSERVER, APPMONITOR, RABITMQ, REST, PCE SERVER, RADIUS SERVER)
including CPU usage, memory, and virtual memory.
•
Map management IP addresses of Path Computation Clients (PCCs) to the
NorthStar Controller:
•
Collect log and Debug traces for support.
•
Run the NorthStar Web client.
6. To log out of the NorthStar administrator role and return to the NorthStar main window,
select Logout.
Related
Documentation
•
Logging In to the NorthStar Controller User Interface on page 47
•
Logging Out of the NorthStar Controller User Interface on page 50
Copyright © 2015, Juniper Networks, Inc.
51
NorthStar Controller Getting Started Guide
52
Copyright © 2015, Juniper Networks, Inc.
CHAPTER 5
Troubleshooting the NorthStar Controller
•
NorthStar Controller Troubleshooting Overview on page 53
•
Troubleshooting the NorthStar Controller on page 54
•
FAQs for Troubleshooting the NorthStar Controller on page 57
NorthStar Controller Troubleshooting Overview
When you are logged in to the NorthStar Controller user interface, by default, the Server
Status view from the Console screen displays the status for topology acquisition
(connected to Network Topology Abstractor Daemon (NTAD) or down) and the Path
Computation Element (PCE) server (up or down). 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.
NOTE: If you are unable to resolve any problem you encounter 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.
You can use either of the following methods to collect debug files:
•
Log in to the NorthStar Controller as administrator and click Collect Debug
Traces. The NorthStar Controller generates a debug file, for example,
NS-Trace-2015-04-10T22-18-55.919.tbz.
•
Log in to the NorthStar Controller CLI, and execute the command
u/wandl/bin/system-diagnostic.sh filename.
The output will be generated and available from the /tmp directory in the
filename.tbz2 debug file.
Table 4 on page 54 lists the NorthStar Controller log files that you can access to identify
and troubleshoot issues with the PCS and PCE. All log files are located under the
/opt/pcs/log directory.
Copyright © 2015, Juniper Networks, Inc.
53
NorthStar Controller Getting Started Guide
Table 4: NorthStar Controller Log Files
Log Files
Description
appmonitor.log
Contains log events related to the application monitor.
cassandra.log
Contains log events related to the cassandra database.
nodejs.log
Contains log events related to nodejs.
npatlogfile
Log files related to the NPAT server. NPAT handles user support for NorthStar simulation.
pcep_server.log
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.
radius.log
Log files related to the RADIUS server.
rest_api.log
Logs any REST API request.
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.
Related
Documentation
•
Troubleshooting the NorthStar Controller on page 54
•
FAQs for Troubleshooting the NorthStar Controller on page 57
Troubleshooting the NorthStar Controller
The Console window displays detailed information about operations on the NorthStar
Controller, including operation failures and their cause. To view additional information
about specific operational failures on the NorthStar Controller, you can access the system
log files, view debug trace files, and view details about the system processes running on
the NorthStar Controller.
54
•
Accessing System Log Files for the NorthStar Controller on page 55
•
Accessing Information about System Processes Running on the NorthStar
Controller on page 55
•
Viewing Debug Trace Files for the NorthStar Controller on page 56
Copyright © 2015, Juniper Networks, Inc.
Chapter 5: Troubleshooting the NorthStar Controller
Accessing System Log Files for the NorthStar Controller
To access the system log files for information to help troubleshoot issues with the
NorthStar Controller:
1.
Log in as the NorthStar Controller administrator.
2. Select the System Logs tab.
The list of NorthStar system log files and message files is displayed, as shown in
Figure 11 on page 55.
Figure 11: System Log Files for the NorthStar Controller
3. Select the log file or message file that you want to view.
The log file is displayed.
4. To exit the log file and return to the System Logs view, click the X icon from the top
right corner of the log view screen.
Accessing Information about System Processes Running on the NorthStar Controller
To access information about the system processes running on the NorthStar Controller:
1.
Log in as the NorthStar administrator.
2. Select the System Processes tab.
The current CPU, memory, and virtual memory usage for each system process, and
related command options are displayed for each system process running on the
NorthStar Controller, as shown in Figure 12 on page 56.
Copyright © 2015, Juniper Networks, Inc.
55
NorthStar Controller Getting Started Guide
Figure 12: System Processes Running on the NorthStar Controller
Table 5 on page 56 describes each field displayed in the System Processes table view.
Table 5: Description of the System Process Fields
Field
Description
Process
The name of the NorthStar Controller process.
PID
The Process ID number.
User
The NorthStar Controller user permissions required to access information about this process.
Group
NorthStar Controller user group permissions required to access information about this process.
CPU%
Displays current percentage of CPU currently in use by this process.
Memory
Displays current percentage of memory currently in use by this process.
Virtual Memory
Displays current Virtual memory in use by this process.
CPU Time
The amount of time the CPU was used for processing instructions for the process
CMD
Displays the specific command options for the system process.
Viewing Debug Trace Files for the NorthStar Controller
To view trace files to help troubleshoot issues with the NorthStar Controller:
1.
Log in as the NorthStar Controller administrator.
2. Select the Collect Debug Traces option in the top right corner of the navigation bar.
3. Use an appropriate file utility to view the debug files, which use the *.tbz2 TAR file
format.
NOTE: You can also run the /u/wandl/bin/system-diagnostic.sh command
from the NorthStar Controller CLI to view trace files to help troubleshoot
issues with the NorthStar Controller. This utility performs the same functions
as the Collect Debug Traces option.
56
Copyright © 2015, Juniper Networks, Inc.
Chapter 5: Troubleshooting the NorthStar Controller
Related
Documentation
•
NorthStar Controller Troubleshooting Overview on page 53
•
FAQs for Troubleshooting the NorthStar Controller on page 57
FAQs for Troubleshooting the NorthStar Controller
The following frequently asked questions (FAQs) are provided to help answer questions
you might have about NorthStar Controller features, functionality, and behavior.
•
Should I use an "in-band" or "out-of-band" management interface for the PCEP session?
We recommend in-band management, but if in-band is not an option, out-of-band
management will work with some limitations. If you to use out-of-band management
interface as protocol PCEP local address, each PCC must have at least one locally
configured LSP in "Up" state. Currently PCEP does not support mapping TE router ID
that is acquired through TE Database (TED) and the PCEP session source IP. If there
is at least one LSP that is UP from the same PCC, the PCS is able to map the PCC
management IP with the LSP source address.
NOTE: We also recommend that you use the router loopback IP address
as protocol pcep local-address with the assumption that the loopback IP
address is also the TE router ID.
•
What is an "ethernet” node and why is “ethernet" node shown even though there are only
two routers on that link?
Ethernet node represents a switch or hub in the broadcast environment. Unless explicitly
configured, by default, OSPF and IS-IS will perform adjacency in broadcast mode. By
displaying this "ethernet" in the network topology you are able to detect which part of
the network has non-explicit point-to-point Interior Gateway Protocol (IGP)
configuration.
•
Why don’t the nodes and links display correctly from the topology map view?
From the Console, check the Server Status tab to make sure “Topology Acquisition” is
connected. From the Update button, select Update Display. This option will attempt
to sync the data between the NorthStar Controller server and GUI client. If this first
option doesn’t resolve the problem, from the Update button, select Reinitialize PCS.
This second option removes the live data from the PCS database, and sends a request
for the full topology to both the topology acquisition server and Path Computation
Server (PCS).
•
The Update button has three options. What does each option do?
•
Update display—The PCS recomputes the soft-state based on the current databases.
This option is recommended after a new planned node is added or if the topology
display or routing seems incorrect. Selecting this option will recalculate the topology
state after changes are made to links, nodes, or LSPs on the NorthStar Controller,
or anytime the topology display appears to be incorrect.
Copyright © 2015, Juniper Networks, Inc.
57
NorthStar Controller Getting Started Guide
•
Reinitialize PCS—The PCS relearns the network state (Topology and LSP) and
Planning data is preserved. Use this option when you suspect the NorthStar model
is out of sync with the actual network, which can happen when there is a
communication problem between the PCC routers and NorthStar Controller. For
example, packet drops, where NorthStar misses some Withdraw/Update message)
or after user has created or modified LSPs, links, or nodes in the NorthStar Controller
but has not yet provisioned these changes and wants to preserve this information .
•
Delete Planning Data—PCS will delete all network changes in planned state; all
planning configuration will be lost. This option is usually required when you connect
the PCS to a completely different topology and want to completely reset the PCS
database.
•
Why doesn’t SRLG information doesn’t show up in the Link > Misc column?
Verify that SRLG is configured correctly and consistently on every router in the network.
If SRLG is configured on one of the routers in the network but has not been configured
on the router that has a BGP-LS peering session with the NorthStar Controller, the
SRLG information may not be forwarded to the NorthStar Controller.
•
The OSPF Broadcast link doesn't sync up, and the NorthStar Controller user interface
displays an isolated router and an isolated ethernet node. What is the problem here?
Verify that each router's interface that is connected to the isolated subnet is configured
with family mpls enable statement. (For router’s running JunOS)
•
The PCEP session between the PCC and PCE stays in "connecting" state. Why isn't the
connection established?
Verify the PE router has been correctly configured as a PCC, for example:
•
Enable external control of LSPs from the PCC router to the NorthStar Controller:
[edit protocols]
user@PE1# set mpls lsp-external-controller pccd
•
Specify the NorthStar Controller (northstar1) as the PCE that the PCC connects to,
and specify the NorthStar Controller host external IP address as the destination
address:
[edit protocols]
user@PE1# set pcep pce northstar1 destination-ipv4-address 10.99.99.1
•
Configure the destination port for the PCC router that connects to the NorthStar
Controller (PCE server) using the TCP-based PCEP:
[edit protocols]
user@PE1# set pcep pce northstar1 destination-port 4189
•
•
You must also make sure no firewall (or anything else) is blocking the traffic.
Why does the Server Status tab in the NorthStar Controller user interface indicate that
the PCE is unreachable?
Check each of the following possible causes:
•
58
The PCE server daemon is down or unreachable.
Copyright © 2015, Juniper Networks, Inc.
Chapter 5: Troubleshooting the NorthStar Controller
To restart the PCE server run the following command from the NorthStar Controller
CLI:
[root@northstar ]# service jnc restart"
•
RabbitMQ server is down or hung.
To restart: run "service rabbitmq-server additional info, please refer to: General
Northstar Troubleshooting run the following command from the NorthStar Controller
CLI:
[root@northstar ]# service rabbitmq-server restart
•
Does the NorthStar Controller user interface show the LSP and topology events in real
time?
In most cases, the LSP and topology events display in real time. However, the PCS can
perform some event aggregation to reduce protocol communication between the
server and client if the PCS receives too many events from the network.
•
The /var/log/jnc/pcep_server.log file does not contain any information. How can I get
more verbose PCEP logging?
1.
From the NorthStar Controller CLI, run pcep_cli.
2. Type set log-level all
3. Type CTRL-C to exit.
Related
Documentation
•
Troubleshooting the NorthStar Controller on page 54
•
NorthStar Controller Troubleshooting Overview on page 53
Copyright © 2015, Juniper Networks, Inc.
59
NorthStar Controller Getting Started Guide
60
Copyright © 2015, Juniper Networks, Inc.
CHAPTER 6
Managing Services on the NorthStar
Controller
•
Managing the Path Computation Server (PCS) and Path Computation Element (PCE)
Services on the NorthStar Controller on page 61
Managing the Path Computation Server (PCS) and Path Computation Element (PCE)
Services on the NorthStar Controller
To perform administrative tasks, you can run commands from the NorthStar Controller
CLI to stop, start, or restart PCS or PCE services that run on the NorthStar Controller.
We recommend that you run the PCS restart command when encountering either of the
following scenarios
•
If you suspect that the network model is out-of-sync—for example, when LSP’s are
still displayed from the user interface but the LSPs are no longer on the router.
•
If the admin status of LSPs appear to be stuck in “PENDING” when you attempt to
provision LSPs—From the NorthStar Controller user interface, the LSPs display as
PENDING and are not provisioned to router.
To manage services on the NorthStar Controller:
1.
From the CLI, log in to the NorthStar Controller PCS, for example:
[northstar_manager-bash-4.1]$ ssh [email protected]
2. From the prompt, enter username root and password northstar.
Copyright © 2015, Juniper Networks, Inc.
61
NorthStar Controller Getting Started Guide
3. Perform any of the following steps to manage the NorthStar Controller PCS or PCE:
a. To manage the PCS on the NorthStar Controller:
•
To stop the PCS service:
[root@pcs~]# service pcs stop
•
To start the PCS service:
[root@pcs~]# service pcs start
•
To restart the PCS service:
[root@pcs~]# service pcs restart
b. To manage the PCE on the NorthStar Controller:
•
To stop the PCE service:
[root@pcs~]# service jnc stop
•
To start the PCE service:
[root@pcs~]# service jnc start
•
To restart the PCE service:
[root@pcs~]# service jnc restart
Related
Documentation
62
•
NorthStar Controller Troubleshooting Overview on page 53
•
FAQs for Troubleshooting the NorthStar Controller on page 57
•
Troubleshooting the NorthStar Controller on page 54
Copyright © 2015, Juniper Networks, Inc.
CHAPTER 7
Index
•
Index on page 65
Copyright © 2015, Juniper Networks, Inc.
63
NorthStar Controller Getting Started Guide
64
Copyright © 2015, Juniper Networks, Inc.
F
font conventions........................................................................x
H
Index
Symbols
#, comments in configuration statements.....................xi
( ), in syntax descriptions.......................................................xi
< >, in syntax descriptions.....................................................xi
[ ], in configuration statements...........................................xi
{ }, in configuration statements..........................................xi
| (pipe), in syntax descriptions............................................xi
A
administrator
logging in from user interface...................................50
B
BGP-LS
topology acquisition, configuring.............................36
braces, in configuration statements..................................xi
brackets
angle, in syntax descriptions........................................xi
square, in configuration statements.........................xi
C
comments, in configuration statements.........................xi
conventions
text and syntax...................................................................x
curly braces, in configuration statements.......................xi
customer support....................................................................xii
contacting JTAC...............................................................xii
D
debug trace files......................................................................56
viewing...............................................................................56
See also system log files
default settings
host machine...................................................................25
JunosVM............................................................................26
documentation
comments on....................................................................xi
E
external path computation
PCE......................................................................................33
Copyright © 2015, Juniper Networks, Inc.
host external IP address
accessing NorthStar Controller user
interface.........................................................................47
configuring for x86 network appliance.................29
using to access the NorthStar Controller user
interface........................................................................43
I
installation See NorthStar Controller ISO image
ISO image...........................................................................21
overview..............................................................................21
IS-IS over GRE
configuring.........................................................................41
IS-IS topology acquisition
configuring.......................................................................40
ISO image See NorthStar Controller ISO image
J
Junos VM
password settings, default.........................................26
JunosVM configuration
configuring for x86 network appliance.................29
JunosVM default settings....................................................26
L
label-switched path (LSP)
auto-bandwidth parameters, enabling from a
template........................................................................19
bidirectional......................................................................18
diverse.................................................................................18
enabling attributes from templates........................18
optimizing..........................................................................19
provisioning
disabling....................................................................19
enabling.....................................................................19
reporting.............................................................................18
secondary..........................................................................18
standby...............................................................................18
time-based scheduling.................................................18
log files See system log files
NorthStar Controller.....................................................53
logging in See user interface
as NorthStar administrator........................................50
NorthStar Controller user interface.........................47
x86 network appliance................................................28
65
NorthStar Controller Getting Started Guide
logging out
NorthStar user interface.............................................50
LSP connection state See Path Computation Client
(PCC)
M
maintenance events
running simulations for scheduled events...........20
management IP address
mapping for Path Computation Client
(PCC).............................................................................35
manuals
comments on....................................................................xi
N
network topology abstractor daemon (NTAD)............31
network topology discovery
overview..............................................................................31
NorthStar Controller
default settings after installation.............................25
features...............................................................................18
log files...............................................................................53
logging in to CLI...............................................................25
overview..............................................................................15
services, starting and stopping .................................61
TCP ports required........................................................30
troubleshooting.......................................................54, 57
troubleshooting overview...........................................53
NorthStar Controller installation
connecting an x86 network appliance to the
network..........................................................................25
verifying..............................................................................25
NorthStar Controller ISO image
downloading....................................................................23
installing............................................................................24
NorthStar Controller user interface.................................43
See also user interface
path computation
overview.............................................................................16
Path Computation Client (PCC)
configuring PCEP............................................................33
configuring router...........................................................33
LSP connection state.....................................................17
mapping a management IP address......................35
path setup between routers.......................................15
Path Computation Client daemon (PCCD)
interaction with Path Computation Element
(PCE)...............................................................................17
Path Computation Element (PCE)
architecture.................................................................15, 16
delegation of control over LSPs................................16
functions in the NorthStar Controller.....................16
stateful................................................................................16
Path Computation Element Protocol (PCEP)
establishing a path between PCC routers.............16
for MPLS RSVP-TE........................................................33
role in client-side implementation of stateful
PCE architecture.........................................................16
Path Computation Server (PCS)......................................26
password settings, default.........................................25
verifying PCS is running on ports..............................25
See also host IP address
R
RSVP-TE signaling..................................................................15
S
OSPF over GRE
configuring........................................................................39
OSPF topology acquisition
configuring........................................................................38
services
starting and stopping on the NorthStar
Controller.......................................................................61
simulations
running for scheduled maintenance
events............................................................................20
stateful PCE...............................................................................16
support, technical See technical support
syntax conventions...................................................................x
system log files
accessing...........................................................................55
system processes
accessing information..................................................55
P
T
parentheses, in syntax descriptions..................................xi
password settings
JunosVM............................................................................26
PCS......................................................................................25
TCP ports
required for the NorthStar Controller.....................30
technical support
contacting JTAC...............................................................xii
O
66
Copyright © 2015, Juniper Networks, Inc.
Index
templates
enabling LSP attributes................................................18
time-based scheduling See label-switched path
(LSP)
topology See network topology discovery
topology acquisition
BGP-LS..............................................................................36
IS-IS....................................................................................40
OSPF...................................................................................38
trace files See debug trace files
troubleshooting See NorthStar Controller
NorthStar Controller.....................................................54
overview.............................................................................53
U
user interface
accessing...........................................................................43
customizing views.........................................................46
logging in............................................................................47
logging out........................................................................50
main window...........................................................44, 48
menu options..................................................................45
overview.............................................................................43
RSVP Live Util legend...................................................46
updating network topology view.............................49
X
x86 network appliance
connecting to switch or router...................................27
connecting to the network..........................................25
logging in...........................................................................28
Copyright © 2015, Juniper Networks, Inc.
67
NorthStar Controller Getting Started Guide
68
Copyright © 2015, Juniper Networks, Inc.