Enabling Junos Fusion Enterprise on an

Enabling Junos Fusion Enterprise on an
Network Configuration Example
Enabling Junos Fusion Enterprise on an Enterprise
Campus Network
Modified: 2016-12-21
Copyright © 2016, Juniper Networks, Inc.
Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Copyright © 2016, 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.
Network Configuration Example Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Copyright © 2016, 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 © 2016, Juniper Networks, Inc.
Table of Contents
Chapter 1
Enabling Junos Fusion Enterprise on an Enterprise Campus Network . . . . . 5
About This Network Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Use Case Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Technical Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Aggregation and Satellite Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Dual Aggregation Device Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Satellite Device Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
FPC Identifiers in a Junos Fusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Satellite Software Upgrade Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Cascade, Uplink, and Extended Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Configuration Synchronization on Aggregation Devices . . . . . . . . . . . . . . . . . . 11
Example: Enabling Junos Fusion Enterprise on an Enterprise Campus
Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Copyright © 2016, Juniper Networks, Inc.
iii
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
iv
Copyright © 2016, Juniper Networks, Inc.
CHAPTER 1
Enabling Junos Fusion Enterprise on an
Enterprise Campus Network
•
About This Network Configuration Example on page 5
•
Use Case Overview on page 5
•
Technical Overview on page 7
•
Example: Enabling Junos Fusion Enterprise on an Enterprise Campus Network on page 12
About This Network Configuration Example
The purpose of this network configuration example is to show how to configure a complex
Junos Fusion Enterprise and how to configure features on an operational Junos Fusion
Enterprise.
The Junos Fusion Enterprise topology in this example uses many features commonly
deployed in a complex, large-scale Junos Fusion Enterprise, including dual aggregation
devices and satellite device clustering.
Junos Fusion Enterprise is optimized to support large-scale Enterprise campus networks
that provide network access for hundreds or thousands of end-user devices. One Junos
Fusion Enterprise can support up to 6,000 access interfaces. The topology used in this
network configuration example is valid but is also intentionally down-scaled for illustrative
purposes. A typical Junos Fusion Enterprise supports more end-user devices than the
topology presented in this network configuration example.
Use Case Overview
Large-scale Enterprise campus networks are notoriously difficult to install and maintain.
IT departments often have to wrestle with a variety of networking equipment that was
purchased incrementally over several years and frequently from different vendors, creating
a network that is difficult to manage because each device has its own hardware and
software requirements as well as its own management point. Complexity is also a
problem, since the large number of devices in the Enterprise campus network can increase
hop counts and management overhead. Enterprise campus network behavior can also
be unpredictable, since interconnecting devices running different software from different
vendors often introduces unforeseen consequences. As an Enterprise campus network
Copyright © 2016, Juniper Networks, Inc.
5
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
grows, the issues around installing and maintaining the Enterprise campus network only
continue to compound.
Junos Fusion Enterprise addresses the installation and maintenance needs of the
next-generation large-scale Enterprise campus network.
Junos Fusion Enterprise provides an architecture that simplifies Enterprise network
management and topologies by allowing a large number of switches—one Junos Fusion
Enterprise can support up to 6,000 access interfaces—to interconnect and be managed
as a single device. The single device—the Junos Fusion Enterprise—simplifies the network
topology by functioning as one large, port-dense device that supports up to 6,000 access
interfaces, runs Junos OS, appears to the larger network as a single switch, and is managed
from a single point using as few as one management IP address.
Other advantages of Junos Fusion Enterprise include investment protection because you
can build a Junos Fusion Enterprise with equipment that you may have previously
purchased for other networking purposes, enhanced scalability because switches providing
additional access ports can be easily added to the Junos Fusion Enterprise as your
Enterprise campus network grows, and preservation of address space since you can
assign one management IP address to the entire Junos Fusion Enterprise instead of
assigning management IP addresses to multiple standalone switches.
In this network configuration example, an Enterprise network with two large campus
buildings and one remote branch office uses a Junos Fusion Enterprise to unite the
enterprise network architecture into a single, easy-to-manage topology that appears to
the larger network as one device. The Junos Fusion Enterprise topology includes a dual
aggregation device setup that uses satellite device clustering in the two main campus
buildings to provide an illustration of how to configure dual aggregation devices and
satellite device clusters in a Junos Fusion Enterprise. A branch office that is not
participating in the Junos Fusion Enterprise is also included in the Enterprise campus
topology, to show how a device not participating in the Junos Fusion Enterprise topology
can still participate as an access switch in an Enterprise campus network.
Junos Fusion Enterprise is typically used in large-scale Enterprise campus networks that
support a large number of networking devices. The topology used in this network
configuration example would only support a limited number of networking devices and
would be smaller in scale than a typical Junos Fusion Enterprise setup. This smaller-scale
topology was designed intentionally for readability purposes; we felt we could best
exemplify the configuration concepts and procedures of a sample Junos Fusion Enterprise
in a smaller-scale topology.
Related
Documentation
6
•
Junos Fusion Enterprise Feature Guide
•
Junos Fusion Enterprise Day One Poster
•
Technical Overview on page 7
•
Example: Enabling Junos Fusion Enterprise on an Enterprise Campus Network on
page 12
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Technical Overview
This section of the network configuration example provides an overview of the major
components of a Junos Fusion Enterprise, and a brief description of how each component
is applied in this network configuration example.
Aggregation and Satellite Devices
The two primary building blocks of any Junos Fusion topology are aggregation devices
and satellite devices.
Aggregation devices:
•
provide the point of management for all interfaces and devices in the Junos Fusion
Enterprise. All configuration in a Junos Fusion Enterprise is done from the aggregation
device.
•
run Junos OS software.
•
are one or two EX9200 switches in a Junos Fusion Enterprise.
•
have at least one connection to each satellite device.
•
are able to simultaneously provide ports to devices that are and are not participating
in the Junos Fusion Enterprise.
In this network configuration example, two EX9208 switches act as aggregation devices
in the Junos Fusion Enterprise topology.
Satellite devices:
•
provide access interfaces in a Junos Fusion Enterprise.
•
run satellite software that has the built-in intelligence to extend features on the Junos
OS software running on the aggregation device onto the satellite device interfaces.
•
have at least one connection to each aggregation device.
Figure 1 on page 7 provides an illustration of a basic Junos Fusion Enterprise topology
and labels the aggregation device and satellite device in the topology.
Figure 1: Basic Junos Fusion Enterprise Topology
Copyright © 2016, Juniper Networks, Inc.
7
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
In this network configuration example, EX4300-48T and EX4300-48P switches are used
as satellite devices to provide access interfaces to the various buildings.
See Understanding Junos Fusion Enterprise Components for additional information on
aggregation and satellite devices.
Dual Aggregation Device Topology
Junos Fusion Enterprise supports dual aggregation device topologies.
The advantages of a dual aggregation device topology include:
•
Load balancing. Traffic traversing the Junos Fusion Enterprise can be load balanced
across both aggregation devices.
•
Redundancy. The Junos Fusion Enterprise can pass traffic even in the unexpected event
of an aggregation device failure.
A Junos Fusion Enterprise supports multiple aggregation devices using Multichassis Link
Aggregation (MC-LAG) groups and the Inter-Chassis Control Protocol (ICCP). A Junos
Fusion Enterprise with dual aggregation devices is configured as an MC-LAG with one
redundancy group. The redundancy group includes two peer chassis IDs—the aggregation
devices—and all satellite devices in the Junos Fusion Enterprise. The aggregation devices
are connected using an interchassis link (ICL) in the MC-LAG topology.
Figure 2 on page 9 provides an illustration of a complex Junos Fusion Enterprise setup
that uses dual aggregation device topology.
The topology provided in this network configuration example is a dual aggregation device
topology, using two EX9208 switches as aggregation devices.
See Understanding Junos Fusion Enterprise Components for additional information on dual
aggregation device topologies.
Satellite Device Clusters
Satellite device clustering allows you to connect up to ten satellite devices into a single
cluster, and connect the satellite device cluster to the aggregation device as a single
group instead of as individual satellite devices.
Satellite device clustering is particularly useful in scenarios where optical cabling options
between buildings are limited and in scenarios where you want to preserve optical
interfaces for other purposes. If you have, for instance, two buildings that have limited
optical interfaces between each other and you want to put an aggregation device in one
building and ten satellite devices in the other building, you can group the ten satellite
devices into a cluster and connect the cluster to the aggregation device with a single
cable.
Figure 2 on page 9 provides an illustration of a more complex Junos Fusion Enterprise
topology that uses satellite device clustering and dual aggregation devices.
8
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Figure 2: Junos Fusion Topology with Dual Aggregation Devices and
Satellite Device Clusters
Aggregation
Device
Aggregation
Device
ICL
Satellite Devices
Satellite Device
Cluster
Satellite Device
Cluster
g043013
Satellite Device
In this network configuration example, building 1 uses a satellite device cluster with six
member satellite devices and building 2 uses a satellite device cluster with three member
satellite devices. The building 1 satellite device cluster has two member satellite devices
with uplinks to both aggregation devices; the building 2 satellite device cluster has one
member satellite device with uplinks to both aggregation devices.
See Understanding Satellite Device Clustering in a Junos Fusion for additional information
on satellite device clustering.
FPC Identifiers in a Junos Fusion
In a Junos Fusion, each satellite device—including each member satellite device in a
satellite device cluster—must have a Flexible PIC Concentrator identifier (FPC ID). The
FPC ID is in the range of 64-254, and is used for Junos Fusion configuration, monitoring,
and maintenance. Interface names—which are identified using the type-fpc / pic / port
format—use the FPC ID as the fpc variable when the satellite device is participating in a
Junos Fusion. For instance, built-in port 2 on PIC 0 of a satellite device—a Gigabit Ethernet
interface on a satellite device that is using 101 as its FPC ID— uses ge-101/0/2 as its
interface name.
See Understanding Junos Fusion Enterprise Components for additional information on FPC
ID numbers in a Junos Fusion Enterprise.
Satellite Software Upgrade Groups
A satellite software upgrade group is a group of satellite devices that are designated to
upgrade to the same satellite software version using the same satellite software package.
The two most common methods of installing satellite software—autoconverting a device
into a satellite device when it is cabled to an aggregation device and manually converting
Copyright © 2016, Juniper Networks, Inc.
9
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
a device that is cabled into an aggregation device into a satellite device—require the
presence of a configured satellite software upgrade group.
For standalone satellite devices—satellite devices that are not part of a satellite device
cluster—you must configure a satellite software upgrade group and add the standalone
satellite device or devices to the satellite software upgrade group.
For satellite devices in satellite device clusters, a software upgrade group matching the
name of the satellite device cluster is automatically created.
In this network configuration example, the two satellite device clusters each have their
own automatically-created satellite device software upgrade group while a user-created
satellite software upgrade group is created for the satellite device in branch office 1.
Autoconversion—which installs satellite software onto a satellite device when it is
connected into the Junos Fusion using a properly-enabled cascade port—is used to install
satellite software in this network configuration example.
See Understanding Software in a Junos Fusion Enterprise for additional information for
satellite software upgrade groups.
Software Requirements
Junos Fusion Enterprise was introduced in Junos OS Release 16.1R1. All aggregation devices
in a Junos Fusion Enterprise must run Junos OS Release 16.1R1 or later.
All satellite devices in a Junos Fusion Enterprise must run satellite software version 2.0R1
or later. The switches must be running Junos OS Release 14.1X53-D35 or later before
installing satellite software.
Both aggregation devices in this network configuration example run Junos OS Release
16.1R1, and all satellite devices run satellite software version 2.0R1. This network
configuration example does not provide an example of upgrading Junos OS software on
the aggregation devices, but does provide the instructions for installing the satellite
software onto each satellite device.
See Understanding Junos Fusion Enterprise Software and Hardware Requirements for
detailed information regarding hardware and software support in a Junos Fusion
Enterprise.
Cascade, Uplink, and Extended Ports
A cascade port is a port on an aggregation device that sends and receives control and
network traffic from an attached satellite device or satellite device cluster. All traffic
passed between a satellite device or cluster and the aggregation device in a Junos Fusion
traverses the cascade port.
An uplink port is a port on a satellite device that connects a satellite device or a satellite
device cluster to an aggregation device.
An extended port in a Junos Fusion Enterprise is an access port—a port that connects an
end user device such as a PC, phone, wireless access point (WAP), or other endpoint
device—on a satellite device.
10
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Figure 3 on page 11 illustrates the location of these ports in a Junos Fusion Enterprise.
Figure 3: Junos Fusion Enterprise Ports
Aggregation
Device
Cascade Ports
Uplink Ports
Extended
Ports
Extended
Ports
Extended
Ports
Extended
Ports
g043012
Satellite Devices
In this network configuration example, an EX9200-6QS line card (6-port 40-Gigabit
Ethernet QSFP+, 24-port 10-Gigabit Ethernet SFP+ line card) is installed in slot 0 of each
aggregation device. All of the cascade ports on both aggregation devices are on this line
card. The uplink ports for satellite device cluster building1 are on the satellite devices
using FPC 102 and 105. The uplink ports for satellite device cluster building 2 are on FPC
112. FPC 121 is a standalone satellite device that has its own uplink port to the aggregation
devices.
See Understanding Junos Fusion Enterprise Components for additional information on
cascade, uplink, and extended ports.
Configuration Synchronization on Aggregation Devices
In a Junos Fusion Enterprise using a dual aggregation device topology, either aggregation
device can be used to configure features on extended ports.
The configuration of extended ports in a Junos Fusion Enterprise should always match
between aggregation devices in order to prevent unpredictable or unwanted network
behavior on an extended port.
You can ensure configuration synchronization between aggregation devices by manually
entering each extended port configuration command on each aggregation device. In this
network configuration example, Power over Ethernet (PoE), Link Layer Discovery Protocol
(LLDP), and Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) are
all configured manually on each aggregation device.
A more efficient method of ensuring extended port configuration synchronization is
configuration groups. You can, for instance, configure the aggregation devices as commit
peers and synchronize all configurations in groups to both aggregation devices, which
allows you to configure the extended port configuration once instead of manually
repeating the configuration on each aggregation device.
The available group configuration options are beyond the scope of this document; see
Understanding MC-LAG Configuration Synchronization and Synchronizing and Committing
MC-LAG Configurations for additional information on using group configurations in an
MC-LAG topology and Network Configuration Example: Configuring MC-LAG on EX9200
Switches in the Core for Campus Networks for a detailed example of an MC-LAG topology
Copyright © 2016, Juniper Networks, Inc.
11
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
that uses group configurations. This network configuration example provides one method
of using groups to synchronize configuration between aggregation devices. See Configuring
Aggregation Devices as Peers for Configuration Synchronization, and also note that the
VLAN configuration in this network configuration example uses the configuration group
to synchronize VLAN configuration to both aggregation devices.
Related
Documentation
•
Junos Fusion Enterprise Feature Guide
•
About This Network Configuration Example on page 5
•
Use Case Overview on page 5
•
Example: Enabling Junos Fusion Enterprise on an Enterprise Campus Network on
page 12
Example: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
This network configuration example illustrates how to:
•
Configure a complex Junos Fusion Enterprise for an Enterprise network with satellite
devices that provide access interfaces at multiple sites and branch offices.
•
Configure commonly-used features for the Enterprise network—VLANs, Power over
Ethernet, and LLDP—in the Junos Fusion Enterprise.
This topic covers:
•
Requirements on page 12
•
Overview and Topology on page 13
•
Configuring the Junos Fusion Enterprise on page 19
•
Connecting the EX9200 Switch to the EX3300 Access Switch That is Not Participating
in the Junos Fusion Enterprise on page 31
•
Configuring Features on the Junos Fusion Enterprise on page 34
•
Verification on page 41
Requirements
This example uses the following hardware and software components for the Junos Fusion
Enterprise:
12
•
Two EX9208 switches as aggregation devices, each running Junos OS Release 16.1R1.
•
Ten total satellite devices in three different buildings, all running satellite software
version 2.0R1.
•
Building 1: satellite device cluster with six member satellite devices.
•
Building 2: satellite device cluster with three member satellite devices.
•
Branch office 1: a single standalone satellite device.
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
•
One EX3300 switch in branch office 2, running Junos OS Release 12.3R2 and connected
to one of the EX9208 aggregation device switches without participating in the Junos
Fusion Enterprise topology.
Overview and Topology
In this example, a Junos Fusion Enterprise is used to provide access ports for a campus
network that includes two main buildings—one main building with six total switches and
a second main building with three total switches—and a small branch office location
that supports a single switch. All switches in the Junos Fusion Enterprise are dual-homed
to two EX9208 switches acting as aggregation devices.
The enterprise network topology includes a second branch office that uses an EX3300
switch that isn’t participating in the Junos Fusion Enterprise—the EX3300 switch runs
Junos OS software, not satellite software—to connect its users to the network. The
EX3300 switch supports a limited number of users in branch office 2, and connects to
aggregation device 2 only to simplify the network and save on cabling costs. The EX3300
switch can connect to this EX9200 switch because EX9200 switches are able to
simultaneously provide ports to devices that are and are not part of a Junos Fusion.
The Junos Fusion Enterprise topology provides redundancy through a dual aggregation
device topology where both aggregation devices are in separate off-campus buildings.
Satellite device clusters are used for the satellite devices in the two main campus buildings
to minimize cabling requirements and costs for aggregation device to satellite device
connections.
The EX4300-48P and EX4300-48T switches in building 1, building 2, and branch office
1 provide access interfaces for users in those buildings. Power over Ethernet, LLDP, and
LLDP-MED are enabled on all access interfaces in the Junos Fusion Enterprise. The Junos
Fusion Enterprise also has one VLAN—v10—that includes three interfaces from different
sites within the topology.
Figure 4 on page 14 shows a high-level overview of the topology used in this example.
Copyright © 2016, Juniper Networks, Inc.
13
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Figure 4: Enterprise Network Topology
EX9208
Aggregation Device 1
EX9208
Aggregation Device 2
ICL
FPC ID: 101
FPC ID: 111
EX4300-48P
EX4300-48P
FPC ID: 102
FPC ID: 112
EX4300-48P
EX4300-48P
FPC ID: 103
FPC ID: 113
EX4300-48P
EX4300-48P
FPC ID: 104
EX4300-48T
SD Cluster: building2
Software: Satellite 2.0R1
BUILDING 2
FPC ID: 105
FPC ID: 121
EX4300-48T
EX4300-48P
FPC ID: 106
Software: Satellite 2.0R1
EX4300-48T
BRANCH OFFICE 1
BUILDING 1
Software: Junos OS Release 12.3R2
BRANCH OFFICE 2
g004173
EX3300
SD Cluster: building1
Software: Satellite 2.0R1
Both aggregation devices in this topology are EX9208 switches with an EX9200-6QS
(6-port 40-Gigabit Ethernet QSFP+, 24-port 10-Gigabit Ethernet SFP+) line card installed
in slot 0. The aggregation devices are interconnected using an interchassis link (ICL)
configured on interface et-0/3/2 on both switches. Both aggregation devices are running
Junos OS Release 16.1R1.
14
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Table 1: Aggregation Devices
Hostname
Switch Model
Line Cards
Cascade Ports
Interchassis link
(ICL) Ports
Junos OS
version
ad1-ex9208
EX9208
Slot 0:
EX9200-6QS
(6-port 40-Gigabit
Ethernet QSFP+,
24-port 10-Gigabit
Ethernet SFP+ line
card)
et-0/2/0: FPC 102
(building1 cluster)
et-0/3/2:
Aggregation Device 2
16.1R1
et-0/3/2:
Aggregation Device 1
16.1R1
et-0/2/1: FPC 105
(building1 cluster)
et-0/2/2: FPC 112
(building2 cluster)
xe-0/0/0: FPC 121
ad2-ex9208
EX9208
Slot 0:
EX9200-6QS
(6-port 40-Gigabit
Ethernet QSFP+,
24-port 10-Gigabit
Ethernet SFP+ line
card)
et-0/2/0: FPC 102
(building1 cluster)
et-0/2/1: FPC 105
(building1 cluster)
et-0/2/2: FPC 112
(building2 cluster)
xe-0/0/0: FPC 121
The Junos Fusion Enterprise topology includes three sites—building 1, building 2, and
branch office 1—with satellite devices that provide access ports to end users. Building 1
includes six total satellite devices interconnected into a satellite device cluster. Two
satellite devices in the cluster—FPC ID 102 and 105—use 40-Gbps+ QSFP connections
to connect to each aggregation device. Building 2 includes three satellite devices
interconnected into a satellite device cluster that connect to the aggregation devices
through FPC ID 112. Branch office 1 includes one satellite device—FPC ID 121—configured
as a standalone satellite device.
The satellite device connections are presented in Figure 5 on page 16 and
Figure 6 on page 16. Figure 6 on page 16 also shows the connections that connect the
EX3300 switch running Junos OS in branch office 2 to the EX9208 switch that also
functions as aggregation device 2, although the EX3300 switch is not a satellite device
in the Junos Fusion Enterprise.
Copyright © 2016, Juniper Networks, Inc.
15
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Figure 5: Satellite Devices to Aggregation Device 1 Connections
0/0
2/2
EX9200-6QS
Line Card
2/0
FPC ID: 111
2/1
EX4300 Series (Rear)
FPC ID: 101
1/0
FPC ID: 112
EX4300 Series (Rear)
EX4300 Series (Rear)
1/0
FPC ID: 102
FPC ID: 113
EX4300 Series (Rear)
EX4300 Series (Rear)
FPC ID: 103
EX4300 Series (Rear)
EX9208
Aggregation Device 1
SD Cluster: building2
Software: Satellite 2.0R1
BUILDING 2
FPC ID: 104
EX4300 Series (Rear)
1/0
FPC ID: 105
EX4300 Series (Rear)
FPC ID: 106
FPC ID: 121
1/0
EX4300 Series (Rear)
BUILDING 1
g004174
EX4300 Series (Front)
SD Cluster: building1
Software: Satellite 2.0R1
Software: Satellite 2.0R1
BRANCH OFFICE 1
Figure 6: Satellite Devices to Aggregation Device 2 Connections
0/1
0/2
2/2
EX9200-6QS
Line Card
0/0
2/0
2/1
FPC ID: 111
FPC ID: 101
EX4300 Series (Rear)
1/1
FPC ID: 102
EX4300 Series (Rear)
FPC ID: 103
EX9208
Aggregation Device 2
EX4300 Series (Rear)
FPC ID: 104
EX4300 Series (Rear)
1/1
FPC ID: 112
EX4300 Series (Rear)
FPC ID: 113
EX4300 Series (Rear)
SD Cluster: building2
Software: Satellite 2.0R1
BUILDING 2
EX4300 Series (Rear)
FPC ID: 121
1/1
FPC ID: 105
EX4300 Series (Rear)
1/1
EX4300 Series (Front)
Software: Satellite 2.0R1
BRANCH OFFICE 1
FPC ID: 106
1/0
1/1
EX4300 Series (Rear)
BUILDING 1
16
Junos OS Software 12.3R2
BRANCH OFFICE 2
g004175
EX3300 (Front)
SD Cluster: building1
Software: Satellite 2.0R1
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
The satellite devices in the Junos Fusion topology are all in building 1, building 2, or branch
office 1. All satellite devices in the topology are EX4300-48P or EX4300-48T switches
running satellite software version 2.0R1. In building 1, all satellite devices in the satellite
device cluster pass traffic to the aggregation device through FPC 102 or FPC 105, which
are the two switches with uplink port connections to the aggregation devices. In building
2, all traffic is passed to the aggregation devices through FPC 112, which is the only device
in the cluster with uplink port connections to the aggregation devices. FPC 121 is a
standalone satellite device to provide access ports to branch office 1.
Table 2: Satellite Devices
FPC ID
Switch Model
System ID
Uplink Ports
Clustering Ports
Satellite
Software
Version
00:00:5E:00:53:A1
No uplink ports
xe-0/1/2: FPC 106
2.0R1
Satellite Device Cluster building1
101
EX4300-48P
xe-0/1/3: FPC 102
102
EX4300-48P
00:00:5E:00:53:A2
et-0/1/0:
Aggregation
Device 1
xe-0/1/2: FPC 101
2.0R1
xe-0/1/3: FPC 103
et-0/1/1:
Aggregation
Device 2.
103
EX4300-48P
00:00:5E:00:53:A3
No uplink ports
xe-0/1/2; FPC 102
2.0R1
xe-0/1/3: FPC 104
104
EX4300-48T
00:00:5E:00:53:A4
No uplink ports
xe-0/1/2; FPC 103
2.0R1
xe-0/1/3: FPC 105
105
EX4300-48T
00:00:5E:00:53:A5
et-0/1/0:
Aggregation
Device 1
xe-0/1/2; FPC 104
2.0R1
xe-0/1/3: FPC 106
et-0/1/1:
Aggregation
Device 2.
106
EX4300-48T
00:00:5E:00:53:A6
No uplink ports
xe-0/1/2; FPC 105
2.0R1
xe-0/1/3: FPC 101
Satellite Device Cluster: building2
111
EX4300-48P
00:00:5E:00:53:B1
No uplink ports
xe-0/1/2: FPC 113
2.0R1
xe-0/1/3: FPC 112
Copyright © 2016, Juniper Networks, Inc.
17
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Table 2: Satellite Devices (continued)
112
EX4300-48P
00:00:5E:00:53:B2
et-0/1/0:
Aggregation
Device 1
xe-0/1/2: FPC 111
2.0R1
xe-0/1/3: FPC 113
et-0/1/1:
Aggregation
Device 2.
113
EX4300-48P
00:00:5E:00:53:B3
No uplink ports
xe-0/1/2; FPC 112
2.0R1
xe-0/1/3: FPC 111
Branch Office 1: Standalone Satellite Device
121
EX4300-48P
00:00:5E:00:53:C1
xe-0/1/0:
Aggregation
Device 1
Not applicable
2.0R1
xe-0/1/1:
Aggregation
Device 2.
The satellite device clusters are shown in Figure 7 on page 18.
Figure 7: Building 1 and 2 Satellite Device Clusters
FPC ID: 101
1/3
FPC ID: 102
EX4300-48P
FPC ID: 103
EX4300-48P
1/3
SD Cluster: building1
BUILDING 1
FPC ID: 111 1/2
EX4300-48P
1/2
1/3
FPC ID: 106
EX4300-48T
1/2
1/3
FPC ID: 105
EX4300-48T
1/2
1/3
FPC ID: 104
EX4300-48T
1/2
1/3
FPC ID: 112
EX4300-48P
1/2
1/3
1/3
FPC ID: 113
EX4300-48P
1/2
1/3
SD Cluster: building2
BUILDING 2
1/2
g004176
EX4300-48P
1/2
The Enterprise campus topology also includes one standalone switch that is not
participating in the Junos Fusion Enterprise, an EX3300 switch running Junos OS Release
12.3R2 that provides access ports to branch office 2. The EX3300 is connected to the
EX9208 switch acting as aggregation device 2 using an aggregated Ethernet bundle.
18
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Table 3: Standalone Switches
Hostname
Switch Model
Interface connections
Junos OS Release
branch-office2-ex3300
EX3300
Aggregated ethernet bundle connection
to aggregation device 2:
12.3R2
ae0:
•
xe-0/1/0 (member link 1)
•
xe-0/1/1 (member link 2)
Configuring the Junos Fusion Enterprise
This section provides the steps for configuring the Junos Fusion Enterprise on both
aggregation devices.
It includes the following sections:
•
Assigning FPC ID Numbers to Satellite Devices, Configuring the Satellite Device Clusters,
and Enabling Automatic Satellite Conversion on page 19
•
Creating the Cascade Ports on page 23
•
Managing the Satellite Software Upgrade Groups on page 24
•
Configuring Dual Aggregation Device Support on page 27
•
Preparing the Satellite Devices on page 30
Assigning FPC ID Numbers to Satellite Devices, Configuring the Satellite Device
Clusters, and Enabling Automatic Satellite Conversion
CLI Quick
Configuration
To quickly configure this example, copy the following commands, paste them in a text
file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level of
the specified aggregation device, and then enter commit from configuration mode.
Aggregation device 1:
[edit]
set chassis satellite-management cluster building1 cluster-id 1
set chassis satellite-management cluster building2 cluster-id 2
set chassis satellite-management cluster building1 fpc 101 member-id
00:00:5E:00:53:A1
set chassis satellite-management cluster building1 fpc 102 member-id
00:00:5E:00:53:A2
set chassis satellite-management cluster building1 fpc 103 member-id
00:00:5E:00:53:A3
set chassis satellite-management cluster building1 fpc 104 member-id
00:00:5E:00:53:A4
set chassis satellite-management cluster building1 fpc 105 member-id
00:00:5E:00:53:A5
set chassis satellite-management cluster building1 fpc 106 member-id
00:00:5E:00:53:A6
set chassis satellite-management cluster building2 fpc 111 member-id
00:00:5E:00:53:B1
set chassis satellite-management cluster building2 fpc 112 member-id
00:00:5E:00:53:B2
Copyright © 2016, Juniper Networks, Inc.
1 system-id
2 system-id
3 system-id
4 system-id
5 system-id
6 system-id
1 system-id
2 system-id
19
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
set chassis satellite-management cluster building2 fpc 113 member-id 3 system-id
00:00:5E:00:53:B3
set chassis satellite-management fpc 121 system-id 00:00:5E:00:53:C1
set chassis satellite-management cluster building1 cascade-ports [et-0/2/0
et-0/2/1]
set chassis satellite-management cluster building2 cascade-ports et-0/2/2
set chassis satellite-management fpc 121 cascade-ports xe-0/0/0
set chassis satellite-management auto-satellite-conversion satellite 101-121
Aggregation device 2:
[edit]
set chassis satellite-management cluster building1 cluster-id 1
set chassis satellite-management cluster building2 cluster-id 2
set chassis satellite-management cluster building1 fpc 101 member-id 1 system-id
00:00:5E:00:53:A1
set chassis satellite-management cluster building1 fpc 102 member-id 2 system-id
00:00:5E:00:53:A2
set chassis satellite-management cluster building1 fpc 103 member-id 3 system-id
00:00:5E:00:53:A3
set chassis satellite-management cluster building1 fpc 104 member-id 4 system-id
00:00:5E:00:53:A4
set chassis satellite-management cluster building1 fpc 105 member-id 5 system-id
00:00:5E:00:53:A5
set chassis satellite-management cluster building1 fpc 106 member-id 6 system-id
00:00:5E:00:53:A6
set chassis satellite-management cluster building2 fpc 111 member-id 1 system-id
00:00:5E:00:53:B1
set chassis satellite-management cluster building2 fpc 112 member-id 2 system-id
00:00:5E:00:53:B2
set chassis satellite-management cluster building2 fpc 113 member-id 3 system-id
00:00:5E:00:53:B3
set chassis satellite-management fpc 121 system-id 00:00:5E:00:53:C1
set chassis satellite-management cluster building1 cascade-ports [et-0/2/0
et-0/2/1]
set chassis satellite-management cluster building2 cascade-ports et-0/2/2
set chassis satellite-management fpc 121 cascade-ports xe-0/0/0
set chassis satellite-management auto-satellite-conversion satellite 101-121
Step-by-Step
Procedure
To assign FPC ID numbers to satellite devices, configure the satellite device clusters, and
enable automatic satellite conversion:
1.
Create the satellite device clusters, and associate each satellite device cluster with
a cluster ID:
Aggregation device 1:
[edit chassis satellite-management]
user@ad1-ex9208# set cluster building1 cluster-id 1
user@ad1-ex9208# set cluster building2 cluster-id 2
Aggregation device 2:
[edit chassis satellite-management]
user@ad2-ex9208# set cluster building1 cluster-id 1
user@ad2-ex9208# set cluster building2 cluster-id 2
2.
Associate each satellite device in the building1 cluster with a cluster member ID
number and an FPC ID:
Aggregation device 1:
[edit chassis satellite-management]
20
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
user@ad1-ex9208#
user@ad1-ex9208#
user@ad1-ex9208#
user@ad1-ex9208#
user@ad1-ex9208#
user@ad1-ex9208#
set cluster building1 fpc 101 member-id 1 system-id 00:00:5E:00:53:A1
set cluster building1 fpc 102 member-id 2 system-id 00:00:5E:00:53:A2
set cluster building1 fpc 103 member-id 3 system-id 00:00:5E:00:53:A3
set cluster building1 fpc 104 member-id 4 system-id 00:00:5E:00:53:A4
set cluster building1 fpc 105 member-id 5 system-id 00:00:5E:00:53:A5
set cluster building1 fpc 106 member-id 6 system-id 00:00:5E:00:53:A6
Aggregation device 2:
[edit chassis satellite-management]
user@ad2-ex9208# set cluster building1 fpc 101 member-id 1 system-id 00:00:5E:00:53:A1
user@ad2-ex9208# set cluster building1 fpc 102 member-id 2 system-id 00:00:5E:00:53:A2
user@ad2-ex9208# set cluster building1 fpc 103 member-id 3 system-id 00:00:5E:00:53:A3
user@ad2-ex9208# set cluster building1 fpc 104 member-id 4 system-id 00:00:5E:00:53:A4
user@ad2-ex9208# set cluster building1 fpc 105 member-id 5 system-id 00:00:5E:00:53:A5
user@ad2-ex9208# set cluster building1 fpc 106 member-id 6 system-id 00:00:5E:00:53:A6
3.
Associate each satellite device in the building2 cluster with a cluster member ID
number and an FPC ID:
Aggregation device 1:
[edit chassis satellite-management]
user@ad1-ex9208# set cluster building2 fpc 111 member-id 1 system-id 00:00:5E:00:53:B1
user@ad1-ex9208# set cluster building2 fpc 112 member-id 2 system-id 00:00:5E:00:53:B2
user@ad1-ex9208# set cluster building2 fpc 113 member-id 3 system-id 00:00:5E:00:53:B3
Aggregation device 2:
[edit chassis satellite-management]
user@ad2-ex9208# set cluster building2 fpc 111 member-id 1 system-id 00:00:5E:00:53:B1
user@ad2-ex9208# set cluster building2 fpc 112 member-id 2 system-id 00:00:5E:00:53:B2
user@ad2-ex9208# set cluster building2 fpc 113 member-id 3 system-id 00:00:5E:00:53:B3
4.
Create an FPC ID for the standalone satellite switch in branch office 1:
Aggregation device 1:
[edit chassis satellite-management]
user@ad1-ex9208# set fpc 121 system-id 00:00:5E:00:53:C1
Aggregation device 2:
[edit chassis satellite-management]
user@ad2-ex9208# set fpc 121 system-id 00:00:5E:00:53:C1
5.
Associate each satellite device cluster or standalone satellite device with a cascade
port or ports.
Aggregation device 1:
[edit chassis satellite-management]
user@ad1-ex9208# set cluster building1 cascade-ports [et-0/2/0 et-0/2/1]
user@ad1-ex9208# set cluster building2 cascade-ports et-0/2/2
user@ad1-ex9208# set fpc 121 cascade-ports xe-0/0/0
Aggregation device 2:
[edit chassis satellite-management]
user@ad2-ex9208# set cluster building1 cascade-ports [et-0/2/0 et-0/2/1]
user@ad2-ex9208# set cluster building2 cascade-ports et-0/2/2
user@ad2-ex9208# set fpc 121 cascade-ports xe-0/0/0
Copyright © 2016, Juniper Networks, Inc.
21
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
NOTE: This step associates standalone satellite devices or satellite
device clusters with cascade ports. The procedure for configuring
interfaces into cascade ports is provided later in this network
configuration example.
6.
Enable automatic satellite conversion for all configured satellite devices:
Aggregation device 1:
[edit chassis satellite-management]
user@ad1-ex9208# set auto-satellite-conversion satellite 101-121
Aggregation device 2:
[edit chassis satellite-management]
user@ad2-ex9208# set auto-satellite-conversion satellite 101-121
Results
From configuration mode, confirm your configuration by entering the show chassis
satellite-management command individually on each aggregation device.
Output for aggregation device 1 only is provided below. The show chassis
satellite-management output on aggregation device 2 should match this output.
user@ad1-ex9208# show chassis satellite-management
cluster building1 {
cluster-id 1;
cascade-ports [ et-0/2/0 et-0/2/1 ];
fpc 101 {
member-id 1;
system-id 00:00:5e:00:53:a1;
}
fpc 102 {
member-id 2;
system-id 00:00:5e:00:53:a2;
}
fpc 103 {
member-id 3;
system-id 00:00:5e:00:53:a3;
}
fpc 104 {
member-id 4;
system-id 00:00:5e:00:53:a4;
}
fpc 105 {
member-id 5;
system-id 00:00:5e:00:53:a5;
}
fpc 106 {
member-id 6;
system-id 00:00:5e:00:53:a6;
}
}
cluster building2 {
cluster-id 2;
cascade-ports et-0/2/2;
fpc 111 {
member-id 1;
system-id 00:00:5e:00:53:b1;
22
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
}
fpc 112 {
member-id
system-id
}
fpc 113 {
member-id
system-id
}
2;
00:00:5e:00:53:b2;
3;
00:00:5e:00:53:b3;
}
fpc 121 {
system-id 00:00:5e:00:53:c1;
cascade-ports xe-0/0/0;
}
auto-satellite-conversion {
satellite [ 101-121 ];
}
Enter show chassis satellite-management on aggregation device 2 to confirm the
configuration on aggregation device 2.
Creating the Cascade Ports
CLI Quick
Configuration
To quickly configure this example, copy the following commands, paste them in a text
file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Aggregation device 1:
[edit]
set interfaces et-0/2/0 cascade-port
set interfaces et-0/2/1 cascade-port
set interfaces et-0/2/2 cascade-port
set interfaces xe-0/0/0 cascade-port
cascade-to-branch-office1-fpc121
description cascade-to-building1-fpc102
description cascade-to-building1-fpc105
description cascade-to-building2-fpc112
description
Aggregation device 2:
[edit]
set interfaces et-0/2/0 cascade-port
set interfaces et-0/2/1 cascade-port
set interfaces et-0/2/2 cascade-port
set interfaces xe-0/0/0 cascade-port
cascade-to-branch-office1-fpc121
Copyright © 2016, Juniper Networks, Inc.
description cascade-to-building1-fpc102
description cascade-to-building1-fpc105
description cascade-to-building2-fpc112
description
23
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Step-by-Step
Procedure
To create the cascade ports:
1.
Configure the cascade ports.
Aggregation device 1:
[edit interfaces]
user@ad1-ex9208# set et-0/2/0 cascade-port description cascade-to-building1-fpc102
user@ad1-ex9208# set et-0/2/1 cascade-port description cascade-to-building1-fpc105
user@ad1-ex9208# set et-0/2/2 cascade-port description cascade-to-building2-fpc112
user@ad1-ex9208# set xe-0/0/0 cascade-port description cascade-to-branch-office1-fpc121
Aggregation device 2:
[edit interfaces]
user@ad2-ex9208# set et-0/2/0 cascade-port description cascade-to-building1-fpc102
user@ad2-ex9208# set et-0/2/1 cascade-port description cascade-to-building1-fpc105
user@ad2-ex9208# set et-0/2/2 cascade-port description cascade-to-building2-fpc112
user@ad2-ex9208# set xe-0/0/0 cascade-port description cascade-to-branch-office1-fpc121
Results
From configuration mode, confirm your configuration by entering the show interfaces
command individually on each aggregation device.
Output for aggregation device 1 only is provided below. The show interfaces output on
aggregation device 2 should match this output.
user@ad1-ex9208# show interfaces
xe-0/0/0 {
description cascade-to-branch-office1-fpc121;
cascade-port;
}
et-0/2/0 {
description cascade-to-building1-fpc102;
cascade-port;
}
et-0/2/1 {
description cascade-to-building1-fpc105;
cascade-port;
}
et-0/2/2 {
description cascade-to-building2-fpc112;
cascade-port;
}
Managing the Satellite Software Upgrade Groups
CLI Quick
Configuration
To quickly configure this example, copy the following commands, paste them in a text
file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level:
Aggregation device 1:
[edit]
set chassis satellite-management upgrade-groups standalone-satellite-devices
satellite 121
commit and-quit synchronize
Aggregation device 2:
[edit]
24
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
set chassis satellite-management upgrade-groups standalone-satellite-devices
satellite 121
commit and-quit synchronize
To complete this quick configuration, copy the following commands, paste them in a
text file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the operational mode prompt
(>):
Aggregation device 1:
request system software add /var/tmp/satellite-2.0R1.2-signed.tgz upgrade-group
building1
request system software add /var/tmp/satellite-2.0R1.2-signed.tgz upgrade-group
building2
request system software add /var/tmp/satellite-2.0R1.2-signed.tgz upgrade-group
standalone-satellite-devices
Aggregation device 2:
request system software add /var/tmp/satellite-2.0R1.2-signed.tgz upgrade-group
building1
request system software add /var/tmp/satellite-2.0R1.2-signed.tgz upgrade-group
building2
request system software add /var/tmp/satellite-2.0R1.2-signed.tgz upgrade-group
standalone-satellite-devices
Step-by-Step
Procedure
Satellite software upgrade groups that inherit the name of the satellite device cluster
are automatically created for satellite device clusters. Satellite software upgrade groups
must be created for standalone satellite devices.
This procedure associates satellite software with the automatically-created software
upgrade groups for the satellite device clusters, and creates a new satellite software
upgrade group for all standalone satellite devices in the topology.
Before you begin:
•
Copy the satellite software 2.0R1 image onto the EX9208 switches.
File copying options are beyond the scope of this network configuration example. These
instructions assume a satellite software image has been installed to the var/tmp
directory on each aggregation device.
1.
Create a satellite software upgrade group named standalone-satellite-devices and
associate FPC ID 121—the only standalone satellite device in the topology—with the
satellite software upgrade group:
Aggregation device 1:
[edit chassis satellite-management]
user@ad1-ex9208# set upgrade-groups standalone-satellite-devices satellite 121
Aggregation device 2:
[edit chassis satellite-management]
user@ad2-ex9208# set upgrade-groups standalone-satellite-devices satellite 121
2.
Commit the configuration to both Routing Engines:
Aggregation device 1:
Copyright © 2016, Juniper Networks, Inc.
25
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
[edit]
user@ad1-ex9208# commit and-quit synchronize
Aggregation device 2:
[edit]
user@ad2-ex9208# commit and-quit synchronize
3.
Start the upgrade by associating all satellite software upgrade groups with the
satellite software version 2.0R1 image:
NOTE: These instructions assume the satellite software has already
been downloaded to the /var/tmp folder on each EX9208 switch.
Aggregation device 1:
user@ad1-ex9208> request system software add /var/tmp/satellite-2.0R1.2-signed.tgz
upgrade-group building1
user@ad1-ex9208> request system software add /var/tmp/satellite-2.0R1.2-signed.tgz
upgrade-group building2
user@ad1-ex9208> request system software add /var/tmp/satellite-2.0R1.2-signed.tgz
upgrade-group standalone-satellite-devices
Aggregation device 2:
user@ad2-ex9208> request system software add /var/tmp/satellite-2.0R1.2-signed.tgz
upgrade-group building1
user@ad2-ex9208> request system software add /var/tmp/satellite-2.0R1.2-signed.tgz
upgrade-group building2
user@ad2-ex9208> request system software add /var/tmp/satellite-2.0R1.2-signed.tgz
upgrade-group standalone-satellite-devices
Results
From configuration mode, confirm the user-configured satellite software upgrade group
is configured by entering the show chassis satellite-management upgrade-groups command
individually on each aggregation device.
user@ad1-ex9208# show chassis satellite-management upgrade-groups
standalone-satellite-devices {
satellite 121;
}
user@ad2-ex9208# show chassis satellite-management upgrade-groups
standalone-satellite-devices {
satellite 121;
}
Verify that the satellite software installation was successful for each software upgrade
group by entering the show chassis satellite software command to confirm the running
satellite software: versions:
26
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
NOTE: The show chassis satellite software command generates output only
after the satellite software upgrades are complete. If you enter the show
chassis satellite software command and no output is generated, consider
re-entering the command in a few minutes.
user@ad1-ex9208> show chassis satellite software
Version
Platforms
2.0R1.1
i386 ppc
user@ad2-ex9208> show chassis satellite software
Version
Platforms
2.0R1.1
i386 ppc
Group
building1
building2
standalone-satellite-devices
Group
building1
building2
standalone-satellite-devices
Configuring Dual Aggregation Device Support
CLI Quick
Configuration
To quickly configure this example, copy the following commands, paste them in a text
file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Aggregation device 1:
[edit]
delete chassis satellite-management single-home
set chassis satellite-management redundancy-groups chassis-id 1
set chassis satellite-management redundancy-groups enterprise-campus-network
redundancy-group-id 1
set chassis satellite-management redundancy-groups enterprise-campus-network
peer-chassis-id 2 inter-chassis-link et-0/3/2
set chassis satellite-management redundancy-groups enterprise-campus-network
cluster building1
set chassis satellite-management redundancy-groups enterprise-campus-network
cluster building2
set chassis satellite-management redundancy-groups enterprise-campus-network
satellite 121
set interfaces et-0/3/2 unit 0 family ethernet-switching interface-mode trunk
set interfaces et-0/3/2 unit 0 family ethernet-switching vlan members all
Aggregation device 2:
[edit]
delete chassis satellite-management single-home
set chassis satellite-management redundancy-groups
set chassis satellite-management redundancy-groups
redundancy-group-id 1
set chassis satellite-management redundancy-groups
peer-chassis-id 1 inter-chassis-link et-0/3/2
set chassis satellite-management redundancy-groups
cluster building1
set chassis satellite-management redundancy-groups
cluster building2
Copyright © 2016, Juniper Networks, Inc.
chassis-id 2
enterprise-campus-network
enterprise-campus-network
enterprise-campus-network
enterprise-campus-network
27
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
set chassis satellite-management redundancy-groups enterprise-campus-network
satellite 121
set interfaces et-0/3/2 unit 0 family ethernet-switching interface-mode trunk
set interfaces et-0/3/2 unit 0 family ethernet-switching vlan members all
Step-by-Step
Procedure
This procedure explains how to configure dual aggregation device support
1.
(Optional unless single-home was previously configured) Delete single home
configuration mode on each EX9208 switch to ensure single-home configuration
is disabled:
Aggregation device 1:
[edit chassis satellite-management]
user@ad1-ex9208# delete single-home
Aggregation device 2:
[edit chassis satellite-management]
user@ad2-ex9208# delete single-home
2.
Define the chassis ID number of each aggregation device:
Aggregation device 1:
[edit chassis satellite-management redundancy-groups]
user@ad1-ex9208# set chassis-id 1
Aggregation device 2:
[edit chassis satellite-management redundancy-groups]
user@ad2-ex9208# set chassis-id 2
3.
Create the satellite management redundancy group:
Aggregation device 1:
[edit chassis satellite-management redundancy-groups]
user@ad1-ex9208# set enterprise-campus-network redundancy-group-id 1
Aggregation device 2:
[edit chassis satellite-management redundancy-groups]
user@ad2-ex9208# set enterprise-campus-network redundancy-group-id 1
4.
Define the peer chassis ID number—the chassis ID number of the other aggregation
device—and interface to use for the ICL on each aggregation device:
Aggregation device 1:
[edit chassis satellite-management redundancy-groups]
user@ad1-ex9208# set enterprise-campus-network peer-chassis-id 2 inter-chassis-link
et-0/3/2
Aggregation device 2:
[edit chassis satellite-management redundancy-groups]
user@ad2-ex9208# set enterprise-campus-network peer-chassis-id 1 inter-chassis-link
et-0/3/2
5.
Define the satellite devices and satellite device clusters that are part of the
redundancy group.
Aggregation device 1:
[edit chassis satellite-management redundancy-groups]
user@ad1-ex9208# set enterprise-campus-network cluster building1
user@ad1-ex9208# set enterprise-campus-network cluster building2
user@ad1-ex9208# set enterprise-campus-network satellite 121
28
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Aggregation device 2:
[edit chassis satellite-management redundancy-groups]
user@ad2-ex9208# set enterprise-campus-network cluster building1
user@ad2-ex9208# set enterprise-campus-network cluster building2
user@ad2-ex9208# set enterprise-campus-network satellite 121
6.
Configure the interface on each side of the ICL as a trunk interface, and make each
interface a member of all VLANs.
Aggregation device 1:
[edit]
user@ad1-ex9208# set interfaces et-0/3/2 unit 0 family ethernet-switching interface-mode
trunk
user@ad1-ex9208# set interfaces et-0/3/2 unit 0 family ethernet-switching vlan members
all
Aggregation device 2:
[edit]
user@ad2-ex9208# set interfaces et-0/3/2 unit 0 family ethernet-switching interface-mode
trunk
user@ad2-ex9208# set interfaces et-0/3/2 unit 0 family ethernet-switching vlan members
all
Results
From configuration mode, confirm your configuration by entering the show chassis
satellite-management redundancy-groups command on each aggregation device.
Aggregation device 1:
user@ad1-ex9208# show chassis satellite-management redundancy-groups
chassis-id 1;
enterprise-campus-network {
redundancy-group-id 1;
peer-chassis-id 2 {
inter-chassis-link et-0/3/2;
}
satellite 121;
cluster building1;
cluster building2;
}
Aggregation device 2:
user@ad2-ex9208# show chassis satellite-management redundancy-groups
chassis-id 2;
enterprise-campus-network {
redundancy-group-id 1;
peer-chassis-id 1 {
inter-chassis-link et-0/3/2;
}
satellite 121;
cluster building1;
cluster building2;
}
Confirm the trunk mode interface configuration by entering the show interfaces et-0/3/2
command on each aggregation device.
Copyright © 2016, Juniper Networks, Inc.
29
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Aggregation device 1:
user@ad1-ex9208# show interfaces et-0/3/2
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members all;
}
}
}
Aggregation device 2:
user@ad2-ex9208# show interfaces et-0/3/2
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members all;
}
}
}
Preparing the Satellite Devices
CLI Quick
Configuration
To complete this quick configuration, copy the following commands, paste them in a
text file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the command into the CLI at the operational mode prompt
(>) of each individual satellite device:
request system zeroize
After the switch reboots:
request
request
request
request
Step-by-Step
Procedure
virtual-chassis
virtual-chassis
virtual-chassis
virtual-chassis
vc-port
vc-port
vc-port
vc-port
delete
delete
delete
delete
pic-slot
pic-slot
pic-slot
pic-slot
1
1
1
1
port
port
port
port
0
1
2
3
To prepare the EX4300-48T and EX4300-48P switches to become satellite devices,
perform the following steps:
NOTE: These instructions assume each EX4300-48T and EX4300-48P
switch is already running Junos OS Release 14.1X53-D35. See Installing
Software on an EX Series Switch with a Single Routing Engine (CLI Procedure)
for instructions on upgrading Junos OS software.
1.
Log into each switch’s console port, and zeroize it.
NOTE: Perform this procedure from the console port connection. A
management connection will be lost when the switch is rebooted to
complete the zeroizing procedure.
30
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
The following sample output shows how to perform this procedure on the satellite
device using FPC ID 101. Repeat this procedure for each satellite device.
user@sd101-con> request system zeroize
NOTE: The devices reboot to complete the zeroizing procedure.
2.
After the switches reboot, convert the built-in 40-Gbps interfaces with QSFP+
transceivers from Virtual Chassis ports (VCPs) into network ports on each switch:
The following sample output shows how to perform this procedure on the satellite
device using FPC ID 101. Repeat this procedure for each satellite device.
user@sd101-con>
user@sd101-con>
user@sd101-con>
user@sd101-con>
3.
request virtual-chassis vc-port delete pic-slot 1 port 0
request virtual-chassis vc-port delete pic-slot 1 port 1
request virtual-chassis vc-port delete pic-slot 1 port 2
request virtual-chassis vc-port delete pic-slot 1 port 3
Cable each switch into the Junos Fusion Enterprise, if you haven’t already done so.
Because automatic satellite conversion is enabled and the satellite software upgrade
groups have been configured, the satellite software installation process starts for
each satellite device when it is cabled into the Junos Fusion Enterprise.
NOTE: If the satellite software installation does not begin, log onto the
aggregation devices and ensure the configurations added in previous
steps have been committed.
Connecting the EX9200 Switch to the EX3300 Access Switch That is Not Participating in the
Junos Fusion Enterprise
CLI Quick
Configuration
To quickly configure this example, copy the following commands, paste them in a text
file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Aggregation device 2:
[edit]
set interfaces ae0 aggregated-ether-options minimum-links 1
set interfaces ae0 aggregated-ether-options link-speed 10g
set interfaces xe-0/0/1 ether-options 802.3ad ae0
set interfaces xe-0/0/2 ether-options 802.3ad ae0
set interfaces ae0 unit 0 family ethernet-switching interface-mode trunk vlan
members all
set interfaces ae0 aggregated-ether-options lacp active
set chassis aggregated-devices ethernet device-count 10
Branch office switch 2:
[edit]
set interfaces ae0 aggregated-ether-options minimum-links 1
Copyright © 2016, Juniper Networks, Inc.
31
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
set interfaces ae0 aggregated-ether-options link-speed 10g
set interfaces xe-0/1/0 ether-options 802.3ad ae0
set interfaces xe-0/1/1 ether-options 802.3ad ae0
set interfaces ae0 unit 0 family ethernet-switching interface-mode trunk vlan
members all
set interfaces ae0 aggregated-ether-options lacp active
set chassis aggregated-devices ethernet device-count 3
Step-by-Step
Procedure
To connect the EX3300 access switch in branch office 2 that is not participating in the
Junos Fusion Enterprise to the EX9208 switch acting as aggregation device 2:
1.
Configure the aggregated Ethernet interface on the EX9208 switch side of the
connection:
[edit interfaces]
user@ad2-ex9208# set ae0 aggregated-ether-options minimum-links 1
user@ad2-ex9208# set ae0 aggregated-ether-options link-speed 10g
2.
Specify the aggregated Ethernet bundle member interfaces on the EX9208 switch
side of the connection:
[edit interfaces]
user@ad2-ex9208# set xe-0/0/1 ether-options 802.3ad ae0
user@ad2-ex9208# set xe-0/0/2 ether-options 802.3ad ae0
3.
Specify the bundle into the ethernet switching family, set the interface mode to
trunk, and configure it to be a member of all VLANs:
[edit interfaces]
user@ad2-ex9208# set ae0 unit 0 family ethernet-switching interface-mode trunk vlan
members all
4.
Enable LACP:
[edit interfaces]
user@ad2-ex9208# set ae0 aggregated-ether-options lacp active
5.
Specify the maximum number of aggregated Ethernet interfaces that can be created
on the switch:
[edit chassis]
user@ad2-ex9208# set aggregated-devices ethernet device-count 10
6.
Perform the same procedure for the EX3300 switch side of the connection:
[edit]
user@branch-office2-ex3300# set interfaces ae0 aggregated-ether-options minimum-links
1
user@branch-office2-ex3300# set interfaces ae0 aggregated-ether-options link-speed
10g
user@branch-office2-ex3300# set interfaces xe-0/1/0 ether-options 802.3ad ae0
user@branch-office2-ex3300# set interfaces xe-0/1/1 ether-options 802.3ad ae0
user@branch-office2-ex3300# set interfaces ae0 unit 0 family ethernet-switching
interface-mode trunk vlan members all
user@branch-office2-ex3300# set interfaces ae0 aggregated-ether-options lacp active
user@branch-office2-ex3300# set chassis aggregated-devices ethernet device-count 3
Results
32
From configuration mode, confirm your aggregated ethernet interface settings by entering
the show interfaces statement and the show chassis aggregated-devices from aggregation
device 2 and the EX3300 switch.
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Aggregation device 2:
user@ad2-ex9208# show interfaces
xe-0/0/1 {
ether-options {
802.3ad ae0;
}
}
xe-0/0/2 {
ether-options {
802.3ad ae0;
}
}
ae0 {
aggregated-ether-options {
minimum-links 1;
link-speed 10g;
lacp {
active;
}
}
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members all;
}
}
}
<some show interfaces output removed for brevity>
user@ad2-ex9208# show chassis aggregated-devices
ethernet {
device-count 10;
}
Branch office 2:
user@branch-office2-ex3300# show interfaces
xe-0/1/0 {
ether-options {
802.3ad ae0;
}
}
xe-0/1/1 {
ether-options {
802.3ad ae0;
}
}
ae0 {
aggregated-ether-options {
minimum-links 1;
link-speed 10g;
lacp {
active;
}
}
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members all;
Copyright © 2016, Juniper Networks, Inc.
33
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
}
}
}
<some show interfaces output removed for brevity>
user@branch-office2-ex3300# show chassis aggregated-devices
ethernet {
device-count 3;
}
Configuring Features on the Junos Fusion Enterprise
This section provides the steps for configuring some commonly-used features on the
Junos Fusion Enterprise.
It includes the following sections:
•
Configuring Aggregation Devices as Peers for Configuration Synchronization on page 34
•
Configuring VLANs on page 36
•
Enabling Power over Ethernet, LLDP, and LLDP-MED on page 39
Configuring Aggregation Devices as Peers for Configuration Synchronization
CLI Quick
Configuration
In a Junos Fusion Enterprise using dual aggregation devices, configuration synchronization
can be used to ensure that configuration done in a configuration group is applied on both
aggregation devices when committed. Configuration synchronization simplifies
administration of a Junos Fusion Enterprise by allowing users to enter commands once
in a configuration group and apply the configuration group to both aggregation devices
rather than repeating a configuration procedure manually on each aggregation device.
To quickly configure this example, copy the following commands, paste them in a text
file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
WARNING: The password password is used in this procedure for illustrative
purposes only. Use a more secure password in your switch configuration.
Aggregation device 1:
[edit]
set system commit peers ad2-ex9208 user user2 authentication “password”
set system commit peers-synchronize
set system services netconf ssh
commit
Aggregation device 2:
[edit]
set system commit peers ad1-ex9208 user user1 authentication “password”
set system commit peers-synchronize
set system services netconf ssh
commit
34
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Step-by-Step
Procedure
To configure the aggregation devices as peers for group configuration synchronization:
1.
Configure each aggregation device so that the other aggregation device is identified
as a commit peer. Enter the authentication credentials of each peer aggregation
device to ensure group configurations on one aggregation device are committed to
the other aggregation device.
WARNING: The password password is used in this configuration step
for illustrative purposes only. Use a more secure password in your device
configuration.
NOTE: This step assumes a user with an authentication password has
already been created on each EX9200 switch acting as an aggregation
device. For instructions on configuring username and password
combinations, see Connecting and Configuring an EX9200 Switch (CLI
Procedure).
Aggregation device 1:
[edit system commit]
user@ad1-ex9208# set peers ad2-ex9208 user user2 authentication “password”
Aggregation device 2:
[edit system commit]
user@ad2-ex9208# set peers ad1-ex9208 user user1 authentication “password”
2.
Enable automatic peer synchronization to ensure group configurations are
synchronized between the peer aggregation devices:
Aggregation device 1:
[edit system commit]
user@ad1-ex9208# set peers-synchronize
Aggregation device 2:
[edit system commit]
user@ad2-ex9208# set peers-synchronize
3.
Enable the Network Configuration (Netconf) protocol over SSH:
Aggregation device 1:
[edit system services]
user@ad1-ex9208# set netconf ssh
Aggregation device 2:
[edit system services]
user@ad2-ex9208# set netconf ssh
4.
Commit the configuration:
Aggregation device 1:
[edit]
user@ad1-ex9208# commit
Copyright © 2016, Juniper Networks, Inc.
35
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Aggregation device 2:
[edit]
user@ad2-ex9208# commit
Results
From configuration mode, confirm your group configuration synchronization settings by
entering the show system commit and show system services statements from each
aggregation device.
Aggregation device 1:
user@ad1-ex9208# show system commit
peers-synchronize;
peers {
ad2-ex9208 {
user user2;
authentication "$ABC123"; ## SECRET-DATA
}
}
user@ad1-ex9208# show system services
netconf {
ssh;
}
Aggregation device 2:
user@ad2-ex9208# show system commit
peers-synchronize;
peers {
ad1-ex9208 {
user user1;
authentication "$ABC123"; ## SECRET-DATA
}
}
user@ad2-ex9208# show system services
netconf {
ssh;
}
Configuring VLANs
CLI Quick
Configuration
To quickly configure this example, copy the following commands, paste them in a text
file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Aggregation device 1:
[edit]
set groups vlans-config when peers [ad1-ex9208 ad2-ex9208]
set groups vlans-config vlans v10 vlan-id 10
set groups vlans-config interfaces ge-101/0/0 unit 0 family ethernet-switching
interface-mode access vlan members v10
set groups vlans-config interfaces ge-111/0/0 unit 0 family ethernet-switching
interface-mode access vlan members v10
set groups vlans-config interfaces ge-121/0/0 unit 0 family ethernet-switching
interface-mode access vlan members v10
set apply-groups vlans-config
36
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
commit
Step-by-Step
Procedure
To configure VLANs on both aggregation devices on the Junos Fusion topology using
configuration groups:
1.
Create and name the configuration group, and configure the group to apply to the
peer aggregation devices:
[edit]
user@ad1-ex9208# set groups vlans-config when peers [ad1-ex9208 ad2-ex9208]
2.
Create a VLAN—VLAN ID 10—by assigning it a name and a VLAN ID:
[edit]
user@ad1-ex9208# set groups vlans-config vlans v10 vlan-id 10
3.
Configure three extended port interfaces—ge-101/0/0, ge-111/0/0, and
ge-121/0/0—into vlan v10.
[edit]
user@ad1-ex9208# set groups vlans-config interfaces ge-101/0/0 unit 0 family
ethernet-switching interface-mode access vlan members v10
user@ad1-ex9208# set groups vlans-config interfaces ge-111/0/0 unit 0 family
ethernet-switching interface-mode access vlan members v10
user@ad1-ex9208# set groups vlans-config interfaces ge-111/0/0 unit 0 family
ethernet-switching interface-mode access vlan members v10
4.
Apply the configuration group:
[edit]
user@ad1-ex9208# set apply-groups vlans-config
5.
Commit the configuration:
[edit]
user@ad1-ex9208# commit
The configuration commits to both aggregation devices, because automatic peer
synchronization is enabled.
Results
Confirm the VLANs are configured by entering the show groups vlans-config command
in configuration mode and are operational by entering the show vlans command in
operational mode. The commands must be entered on both aggregation devices in order
to confirm the group configuration applied the VLAN configuration to both aggregation
devices.
Aggregation device 1:
user@ad1-ex9208# show groups vlans-config
when {
peers [ ad1-ex9208 ad2-ex9208 ];
}
interfaces {
ge-101/0/0 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members v10;
}
}
}
}
Copyright © 2016, Juniper Networks, Inc.
37
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
ge-111/0/0 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members v10;
}
}
}
}
ge-121/0/0 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members v10;
}
}
}
}
}
vlans {
v10 {
vlan-id 10;
}
}
user@ad1-ex9208> show vlans
Routing instance
VLAN name
default-switch
v10
Tag
10
Interfaces
ge-101/0/0.0
ge-111/0/0.0
ge-121/0/0.0
Aggregation device 2:
user@ad2-ex9208# show groups vlans-config
when {
peers [ ad1-ex9208 ad2-ex9208 ];
}
interfaces {
ge-101/0/0 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members v10;
}
}
}
}
ge-111/0/0 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members v10;
}
}
}
}
ge-121/0/0 {
38
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members v10;
}
}
}
}
}
vlans {
v10 {
vlan-id 10;
}
}
user@ad2-ex9208> show vlans
Routing instance
VLAN name
default-switch
v10
Tag
10
Interfaces
ge-101/0/0.0
ge-111/0/0.0
ge-121/0/0.0
Enabling Power over Ethernet, LLDP, and LLDP-MED
CLI Quick
Configuration
To quickly configure this example, copy the following commands, paste them in a text
file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Aggregation device 1:
[edit]
set poe interface all-extended
set protocols lldp interface all
set protocols lldp-med interface all
Aggregation device 2:
[edit]
set poe interface all-extended
set protocols lldp interface all
set protocols lldp-med interface all
Step-by-Step
Procedure
This procedure shows how to enable Power over Ethernet (PoE), LLDP, and LLDP-MED
for this topology, without using configuration groups.
1.
Enable PoE on all extended ports that support PoE:
Aggregation device 1:
[edit]
user@ad1-ex9208# set poe interface all-extended
Aggregation device 2:
[edit]
user@ad2-ex9208# set poe interface all-extended
The default values for PoE - class management mode, 30W of maximum power
per PoE interface, 0 W reserved for guard band - are unchanged in this configuration.
Copyright © 2016, Juniper Networks, Inc.
39
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
2.
Enable LLDP on all extended ports:
Aggregation device 1:
[edit]
user@ad1-ex9208# set protocols lldp interface all
Aggregation device 2:
[edit]
user@ad2-ex9208# set protocols lldp interface all
NOTE: LLDP is enabled by default. This configuration step is added to
ensure LLDP is enabled on all extended ports.
3.
Enable LLDP-MED on all extended ports:
Aggregation device 1:
[edit]
user@ad1-ex9208# set protocols lldp-med interface all
Aggregation device 2:
[edit]
user@ad2-ex9208# set protocols lldp-med interface all
NOTE: LLDP-MED is enabled by default. This configuration step is added
to ensure LLDP-MED is enabled on all extended ports.
Results
From configuration mode, confirm your PoE configuration by entering the show poe
statement from each aggregation device.
Aggregation device 1:
user@ad1-ex9208# show poe
interface all-extended;
Aggregation device 2:
user@ad2-ex9208# show poe
interface all-extended;
Confirm your LLDP and LLDP-MED configuration by entering the show protocols statement
from each aggregation device.
Aggregation device 1:
user@ad1-ex9208# show protocols
lldp {
interface all;
}
lldp-med {
interface all;
}
<some output removed for brevity>
40
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Aggregation device 2:
user@ad2-ex9208# show protocols
lldp {
interface all;
}
lldp-med {
interface all;
}
<some output removed for brevity>
Verification
Confirm that the configuration is working properly.
•
Verifying that the Satellite Devices are Online on page 41
•
Verifying that PoE is Enabled on page 41
•
Verifying that LLDP and LLDP-MED are Enabled on page 42
•
Verifying that VLANs are Operational on page 42
•
Verifying the Aggregated Ethernet Interface Connecting Aggregation Device 2 to Branch
Office 2 is Online on page 43
Verifying that the Satellite Devices are Online
Purpose
Action
Verify that the satellite devices in the Junos Fusion are active.
Enter the show chassis satellite command from either aggregation device:
user@ad1-ex9208> show chassis satellite
Device
Alias
Slot
State
_sd101
101
Online
Meaning
_sd102
102
Online
_sd103
103
Online
_sd104
104
Online
_sd105
105
Online
_sd106
106
Online
_sd111
_sd112
_sd113
_sd121
111
112
113
121
Online
Online
Online
Online
Cascade
Ports
et-0/2/0
et-0/2/1
et-0/2/0
et-0/2/1
et-0/2/0
et-0/2/1
et-0/2/0
et-0/2/1
et-0/2/0
et-0/2/1
et-0/2/0
et-0/2/1
et-0/2/2
et-0/2/2
et-0/2/2
xe-0/0/0
Port
State
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
online
Extended Ports
Total/Up
48/48
48/48
48/48
48/48
48/48
48/48
48/48
48/48
48/48
48/48
48/48
48/48
48/48
48/48
48/48
48/48
The Junos Fusion Enterprise topology is properly configured. The device state for each
satellite device in the Junos Fusion Enterprise topology is online, as is the port state for
each cascade port.
Verifying that PoE is Enabled
Purpose
Verify that PoE is enabled on the satellite device’s extended ports
Copyright © 2016, Juniper Networks, Inc.
41
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Action
Confirm PoE is enabled on individual interfaces by entering the show poe interface
command from either aggregation device.
user@ad1-ex9208> show poe interface
Interface
Admin
Oper
Max
Priority
status
status power
ge-101/0/0 Enabled
OFF
0.0W
Low
ge-101/0/1 Enabled
OFF
0.0W
Low
ge-101/0/2 Enabled
OFF
0.0W
Low
ge-101/0/3 Enabled
OFF
0.0W
Low
<some output removed for brevity>
ge-102/0/0 Enabled
OFF
0.0W
Low
ge-102/0/1 Enabled
OFF
0.0W
Low
ge-102/0/2 Enabled
OFF
0.0W
Low
ge-102/0/3 Enabled
OFF
0.0W
Low
<additional output removed for brevity>
Meaning
Power
consumption
0.0W
0.0W
0.0W
0.0W
Class
0.0W
0.0W
0.0W
0.0W
not-applicable
not-applicable
not-applicable
not-applicable
not-applicable
not-applicable
not-applicable
not-applicable
The show poe interface output confirms that the admin status is Enabled for all interfaces
on the satellite devices. The satellite device interfaces can be identified by the FPC ID
number; in this output, the PoE status for interfaces on FPC 101 and 102 is shown.
Verifying that LLDP and LLDP-MED are Enabled
Purpose
Action
Verify that LLDP and LLDP-MED are enabled.
Confirm LLDP and LLDP-MED are enabled by entering the show lldp command on either
aggregation device:
user@ad1-ex9208> show lldp
LLDP
Advertisement interval
Transmit delay
Hold timer
Notification interval
Config Trap Interval
Connection Hold timer
:
:
:
:
:
:
:
LLDP MED
MED fast start count
: Enabled
: 3 Packets
Enabled
30 seconds
2 seconds
120 seconds
5 Second(s)
0 seconds
300 seconds
Port ID TLV subtype
: locally-assigned
Port Description TLV type : interface-alias (ifAlias)
Interface
all
Meaning
Parent Interface
-
LLDP
Enabled
LLDP-MED
Enabled
Power Negotiation
Enabled
The output confirms that LLDP and LLDP-MED are enabled.
Verifying that VLANs are Operational
Purpose
42
Verify the VLANs exist and are associated with the correct interfaces.
Copyright © 2016, Juniper Networks, Inc.
Chapter 1: Enabling Junos Fusion Enterprise on an Enterprise Campus Network
Action
Enter the show vlans command on either aggregation device:
user@ad1-ex9208> show vlans
Routing instance
VLAN name
default-switch
v10
Tag
10
Interfaces
ge-101/0/0.0
ge-111/0/0.0
ge-121/0/0.0
Meaning
The output confirms that VLAN v10 is present on the aggregation device, and the correct
interfaces are associated with the VLAN.
Verifying the Aggregated Ethernet Interface Connecting Aggregation Device 2 to
Branch Office 2 is Online
Purpose
Action
Verify that the aggregated ethernet interface connecting aggregation device 2 to branch
office 2 is up and operational.
Confirm the aggregated ethernet interface is up by entering the show interfaces ae0
brief command:
user@ad2-ex9208> show interfaces ae0 brief
Physical interface: ae0, Enabled, Physical link is Up
Link-level type: Ethernet, MTU: 1514, Speed: 200Mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Disabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Logical interface ae0.0
Flags: SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
eth-switch
Meaning
Related
Documentation
The output confirms that the aggregated ethernet interface is enabled and that the
physical link is up.
•
About This Network Configuration Example on page 5
•
Use Case Overview on page 5
•
Technical Overview on page 7
Copyright © 2016, Juniper Networks, Inc.
43
Enabling Junos Fusion Enterprise on an Enterprise Campus Network
44
Copyright © 2016, Juniper Networks, Inc.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising