Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Although Juniper Networks has attempted to provide accurate information in this guide, Juniper Networks does not warrant or guarantee the accuracy of the information provided herein. Third party product descriptions and related technical details provided in this document are for information purposes only and such products are not supported by Juniper Networks. All information provided in this guide is provided as is, with all faults, and without warranty of any kind, either expressed or implied or statutory. Juniper Networks and its suppliers hereby disclaim all warranties related to this guide and the information contained herein, whether expressed or implied of statutory including, without limitation, those of merchantability, fitness for a particular purpose and noninfringement, or arising from a course of dealing, usage, or trade practice.
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Design Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 QFabric basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Node Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 QFabric Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Defining Node Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Example 1: sNG configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Example 2: rsNG configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Example 3: NNG configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Interface Naming Conventions for QFabric Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Interface Type Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Access Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Trunk Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 routed Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Layer 3 LAG Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Trunk Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Design Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Connecting Layer 3 Device to QFabric Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 route Lookup and Forwarding Decisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 QFabric and VrrP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 Layer 3 Design Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Use Case 1: static Default route Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Use Case 2: Putting QFabric Architecture into an OsPF Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Use Case 3: Putting QFabric Architecture into OsPF stub Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Use Case 4: Connecting One-Armed srX series Device as Active/Active with QFabric Architecture . . . . . . . . . . . . . . . 22 Use Case 5: Connecting One-Armed srX series as Active/backup with QFabric Architecture . . . . . . . . . . . . . . . . . . . . . 25 Use Case 6: Connecting One-Armed srX series Gateway to QFabric Architecture (VrF-based steering Mode) . . . 28 Use Case 7: QFabric Architecture back-to-back Extension with L3 LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 About Juniper Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
Table of Figures
Figure 1: Junipers data center solution with QFabric architecture, MX series, srX series, vGw Virtual Gateway, and Junos space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Figure 2: QFabric logical and physical configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Figure 3: LAG support between node groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Figure 4: Different types of redundancy for rack servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Figure 5: Different deployment scenarios with embedded blade switches in blade chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Figure 6: Layer 3 devices can be located anywhere in the QFabric architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 Figure 7: NNG connecting to MX series with LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Figure 8: QFabric technology in OsPF area0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Figure 9: srX series one-armed deployment in a two-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Figure 10: One-armed srX series active/active deployment with QFabric technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 11: One-armed srX series active/active deployment with QFabric architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Figure 12: Applying security policy to inter-VrF routing on QFabric architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Figure 13: back-to-back extension with LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
Introduction
As people become more adept at employing virtualization technologies, and as applications become more efficient, the need for a high-performance and scalable data center infrastructure becomes increasingly critical. Todays data center network architecture has too many layers and is too rigid to meet those requirements. Juniper has developed a new technology called Juniper Networks QFabric architecture that addresses the inefficiencies of legacy data center networks. QFabric technology eliminates network complexity by reducing the number of switch layers and managed devices, while providing optimal network utilization and a pay-as-you-grow model that doesnt compromise overall network performance.
Scope
This document will discuss the design of a data center network where QFabric architecture acts as the Layer 3 switch. It will describe the overall network topology and provide relevant configuration templates for QFabric solutions. The target audiences for this document are architects, network engineers or operators, and individuals who require technical knowledge, although every effort has been made to make this document appeal to the widest possible audience. It is assumed that the reader is familiar with Juniper Networks Junos operating system and is knowledgeable about the QFabric family of products. Also, reading the Designing a Layer 2 Data Center Network with the QFabric Architecture implementation guide is highly recommended.
Design Considerations
One of the biggest challenges with todays data center is keeping the network simple while enabling it to grow without making uncomfortable trade-offs. Adding new switches is the typical response to network growth, but that means more devices to manage and, more importantly, a potentially negative impact on network performance due to switch locations. Juniper Networks has introduced QFabric technology to address these challenges. QFabric technology has the unique ability to reduce complexity by flattening the network to a single tier, providing any-to-any connectivity that ensures every device is no more than a single hop away from any other device. Increasing port counts with QFabric architecture does not increase complexity or add devices to manage, since all QFabric solution components are managed as a single device.
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
MX Series
SRX5800
SRX Series
Servers
NAS
FC Storage
Figure 1: Junipers data center solution with QFabric architecture, MX Series, SRX Series, vGW Virtual Gateway, and Junos Space.
QFabric Basics
Juniper Networks QFabric architecture is composed of three components: QFabric Director, QFabric Interconnect, and QFabric Node. Each component plays a vital role. The QFabric Director functions as a routing Engine (rE) in a modular switch, where it is responsible for managing the overall QFabric system as well as distributing forwarding tables to the QFabric Nodes and QFabric Interconnects. The QFabric Interconnect is equivalent to a fabric, acting like the backplane of the switch and providing a simple, high-speed transport that interconnects all of the QFabric Nodes in a full-mesh topology to provide any-to-any port connectivity. The QFabric Node is equivalent to a line card, providing an intelligent edge that can perform routing and switching between connected devices.
QFabric Interconnect
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
Node Groups
A node group is nothing more than an abstraction of a single or set of QFabric Nodes that are logically grouped with similar attributes. Node groups are not bound by physical location but by common traits. There are three different types of QFabric Nodes: server node group (sNG), redundant server node group (rsNG), and network node group (NNG). sNG is a single QFabric Node that is connected to servers, blade chassis, and storage devices (it may also be referred to as host-facing ports). Typically, host devices require a subset of protocols1 such as Link Aggregation Control Protocol (LACP) and Link Layer Discovery Protocol (LLDP). Therefore, sNGs will only need to support host type protocols. Layer 2 or Layer 3 networking protocols2 such as spanning Tree Protocol (xsTP) and OsPF are not supported and cannot be configured on sNG ports. rsNG is similar to sNG with a couple of differences. First, an rsNG requires two QFabric Nodes to be grouped. second, it can support cross-member (node) link aggregation groups (LAGs), as shown in Figure 3. NNG is a set of QFabric Nodes connected to wAN routers, other networking devices, or service appliances such as firewalls or server load balancers. because such devices will be connected to an NNG, all protocol stacks are available on these ports. The QFabric architecture requires at least one QFabric Node to be a member of an NNG (up to eight devices are allowed). while defined as an NNG, it does not limit connections to service appliances or networking devices; server and/or storage devices can also connect to an NNG.
SNG QFabric Node RSNG QFabric Node QFabric Node NNG QFabric Node QFabric Node QFabric Node
Figure 3: LAG support between node groups Table 1: Node Groups Support Matrix
NoDe GRoupS MAX. NuMBeR oF MeMBeRS peR NoDe GRoup MAX. NuMBeR oF NoDe GRoupS WIThIN The QFABRIC ARChITeCTuRe SAMe MeMBeR LAG CRoSS-MeMBeR LAG (ACTIVe/ ACTIVe) SuppoRT hoST-FACING pRoToCoLS 3 SuppoRT NeTWoRkINGFACING pRoToCoLS 4
single node group (sNG) redundant server node group (rsNG) Network node group (NNG)
127
63
QFabric Configuration
This document will not go over the deployment or bring-up of the system. It is assumed that the QFabric architecture has already been brought up by a certified specialist and is ready to be configured. This section will cover how to define node groups and how to configure port types (access or trunk), VLANs, LAGs, and VLAN membership. All management and configuration is done through the QFabric Director. There is no need to go into individual QFabric devices and configure them. The entire QFabric architecture can be managed from a single IP address that is shared by the QFabric Directors.
host-facing protocols are LLDP, LACP, Address resolution Protocol (ArP), Internet Group Management Protocol (IGMP) snooping, Data Center bridging (DCbx). Network-facing protocols are xsTP, OsPF, L3 unicast and multicast protocols, and IGMP. host-facing protocols are LLDP, LACP, ArP, IGMP snooping, DCbx. 4 Network-facing protocols are xsTP, L3 unicast and multicast protocols, and IGMP.
1 2 3
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
netadmin@qfabric> show fabric administration inventory node-devices Item Identifier Connection Configuration Node device row1-rack1 ABCD1230 Connected Configured row1-rack2 ABCD1231 Connected Configured row1-rack3 ABCD1232 Connected Configured row21-rack1 ABCD1233 Connected Configured
QFabric Nodeseven single devicesneed to be assigned to a node group. Any arbitrary name can be assigned to an xsNG. NNG is the exception to this rule, as it already has a name (Nw-NG-0) which cannot be changed. A QFabric Node can only be part of one node group type; it cannot be part of two different node groups. Typically members within node groups are close in proximity, but that is not a requirement. Members of a node group can be in different parts of the data center.
[edit fabric] netadmin@qfabric# set resources node-group RSNG-1 node-device row1-rack2 netadmin@qfabric# set resources node-group RSNG-1 node-device row1-rack3
Note: Up to two QFabric Nodes can be part of an rsNG.
[edit fabric] netadmin@qfabric# set resources node-group NW-NG-0 network-domain netadmin@qfabric# set resources node-group NW-NG-0 node-device row21-rack1
Note: Up to eight QFabric Nodes can be part of an NNG.
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
A corresponding show command, shown below, provides overall node group membership and status.
netamdin@qfabric> show fabric administration inventory node-groups Item Identifier Connection Configuration Node group NW-NG-0 Connected Configured row21-rack1 ABCD1233 Connected Configured RSNG-1 Connected Configured row1-rack2 ABCD1231 Connected Configured row1-rack3 ABCD1232 Connected Configured SNG-1 Connected Configured row1-rack1 ABCD1230 Connected Configured
Another helpful command, show fabric administration inventory, combines both node device and node groups.
netadmin@qfabric> show interfaces row1-rack1:xe-0/0/10 Physical interface: row1-rack1:xe-0/0/10, Enabled, Physical link is Up Interface index: 49182, SNMP ifIndex: 7340572 Link-level type: Ethernet, MTU: 1514, Speed: 10Gbps, Duplex: Full-Duplex, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled Interface flags: Internal: 0x0 CoS queues : 12 supported, 12 maximum usable queues Current address: 84:18:88:d5:b3:42, Hardware address: 84:18:88:d5:b3:42 Last flapped : 2011-09-06 21:10:51 UTC (04:20:44 ago) Input rate : 0 bps (0 pps) Output rate : 0 bps (0 pps)
Note: This interface naming convention only applies to physical interfaces. For logical interfaces such as LAGs, it is node-group:interface_name-fpc/pic/slot. routed VLAN interfaces (rVIs) follow the standard naming convention used by Juniper Networks EX series Ethernet switches: vlan.x.
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
Access port
netadmin@qfabric> show ethernet-switching interfaces row1-rack1:xe-0/0/0 detail Interface: row1-rack1:xe-0/0/0.0, Index: 82, State: up, Port mode: Access Ether type for the interface: 0x8100 VLAN membership: default, untagged, unblocked Number of MACs learned on IFL: 0
Trunk port
netadmin@qfabric> show ethernet-switching interfaces row1-rack1:xe-0/0/1 detail Interface: LC2:xe-0/0/1.0, Index: 89, State: down, Port mode: Trunk Ether type for the interface: 0x8100 Number of MACs learned on IFL: 0
Routed Interface
As mentioned earlier, routed interfaces can either be rVI or Layer 3 ports on NNG. rVI provides routing between VLANs as well as between physical routed interfaces on the NNG. The following example shows physical Layer 3 interface configurations on both NNG and rVI. example 1: L3 routed port on NNG
netadmin@qfabric> show interfaces row21-rack1:xe-0/0/0 Physical interface: row1-rack4:xe-0/0/0, Enabled, Physical link is Up Interface index: 131, SNMP ifIndex: 1311224 Link-level type: Ethernet, MTU: 1514, Speed: 10Gbps, Duplex: Full-Duplex, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled Interface flags: Internal: 0x4000 CoS queues : 12 supported, 12 maximum usable queues Current address: 84:18:88:d5:e7:0c, Hardware address: 84:18:88:d5:e7:0c Last flapped : 2011-09-07 12:53:59 UTC (00:21:30 ago) Input rate : 0 bps (0 pps) Output rate : 0 bps (0 pps) Logical interface row21-rack1:xe-0/0/0.0 (Index 86) (SNMP ifIndex 1311280)
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
Flags: 0x4000 Encapsulation: ENET2 Input packets : 0 Output packets: 1 Protocol inet, MTU: 1500 Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255
example 2: RVI step 1. Configuring the rVI interface
root@qfabric> show interfaces vlan Physical interface: vlan, Enabled, Physical link is Up Interface index: 128, SNMP ifIndex: 1311221 Type: VLAN, Link-level type: VLAN, MTU: 1518, Speed: 1000mbps Link type : Full-Duplex Current address: 84:18:88:d5:ee:05, Hardware address: 00:1f:12:31:7c:00 Last flapped : Never Input packets : 0 Output packets: 0 Logical interface vlan.1250 (Index 88) (SNMP ifIndex 2622001) Flags: 0x4000 Encapsulation: ENET2 Input packets : 0 Output packets: 1 Protocol inet, MTU: 1500 Destination: 10.83.100/24, Local: 10.83.100.1, Broadcast: 10.83.100.255
Layer 3 LAG Configuration
Link aggregation provides link redundancy as well as increases bandwidth. QFabric architecture supports both static and dynamic LAGs, which can be configured on any QFabric Node. There are two typical LAG deploymentssame member and cross member. same member LAGs are where all of the LAG child members are terminated on the same QFabric Node. Cross member LAGs are where child member LAGs are split between node group members. As discussed in the Defining Node Groups section, same member LAGs can be configured on any node group, while cross member LAGs are only supported on rsNGs and NNGs.
3 3 3 3 3
10
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
example 1: Same member LAG configuration step 1. Define number of supported LAGs per node group while the example below is for an sNG named sNG-1, the same configuration is applicable to rsNG or NNGthe configuration will just need to reflect the correct node group name. All node groups support the same member LAG configuration.
[edit interfaces] netadmin@qfabric# set row1-rack1:xe-0/0/46 ether-options 802.3ad ae0 netadmin@qfabric# set row1-rack1:xe-0/0/47 ether-options 802.3ad ae0
step 3. Configure the LAG interface All common LAG parameters across child LAG members such as LACP, speed, duplex, and so on are centralized to the LAG interface itself. while the example below is for a Layer 2 interface, for Layer 3 the family needs to change from ethernet-switching to inet (L3 is only supported on NNG). For static LAGs, omit the LACP configuration. One thing to note is that the node identifier is the node group, not the QFabric Node.
[edit interfaces] netadmin@qfabric# set SNG-1:ae0 aggregated-ether-options lacp active netadmin@qfabric# set SNG-1:ae0 unit 0 family ethernet-switching port-mode trunk
some relevant commands for LAG: show lacp ## applicable to dynamic LAG only ## show interface terse | match node_group:interface_name ## example sNG-1:ae0 ## show interface node_group:interface_name step 4. Assign IP address to LAG interface example 2: Cross member LAG configuration step 1. Define the number of supported LAGs per network node group
[edit interfaces] netadmin@qfabric# set row1-rack2:xe-0/0/0 ether-options 802.3ad ae0 netadmin@qfabric# set row1-rack3:xe-0/0/0 ether-options 802.3ad ae0
11
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
step 3. Configure the LAG interface and assign it an IP address All common LAG parameters across child LAG members such as LACP, speed, duplex, and so on are centralized to the LAG interface itself. while the example below is for a Layer 2 interface, for Layer 3 the family needs to change from ethernet-switching to inet (L3 is only supported on NNG). For static LAGs, omit the LACP configuration. One thing to note is that the node identifier is the node group and not the QFabric Node.
[edit interfaces] netadmin@qfabric# set NW-NG-0:ae0 aggregated-ether-options lacp active netadmin@qfabric# set NW-NG-0:ae0 unit 0 family ethernet-switching port-mode trunk
some relevant commands for LAG: show lacp ## applicable to dynamic LAG only ## show interface terse | match node_group:interface_name ## example Nw-NG-0:ae0 ## show interface node_group:interface_name Once the LAG interface is configured for Layer 2 link, change the family to inet and assign an IP address.
netadmin@qfabric> show vlans Name Tag Interfaces default 1 row1-rack1:xe-0/0/0.0*, row1-rack1:xe-0/0/0.1*, row1rack2:xe-0/0/3.0*, RSNG-1:ae0.0*, NW-NG-0:ae0.0*
step 2. VLAN port membership If VLAN membership is not explicitly configured on the access ports, then it reverts back to the default VLAN. For trunk ports, explicit configuration is required. There are two methods for assigning a port to a VLANport centric and VLAN centric. Either method is valid, but if interface range or group profile isnt being used, then for ease of VLAN management, Juniper recommends that VLAN membership for the access port should be done under the VLAN method and under the port method for the trunk port.
12
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
[edit interfaces] netadmin@qfabric# set row1-rack1:xe-0/0/0.0 family ethernet-switching port-mode trunk vlan members [1-10 21 50-100]
In the above configuration, all VLANs are tagged on the interface. For hybrid trunks, untagged and tagged traffic use the native-vlan-id keyword for untagged. below is an example trunk interface configured for VLAN 1 to be untagged and VLANs 2-25 to be tagged. Note that VLAN 1 is not part of the vlan members configuration.
[edit interfaces] netadmin@qfabric# set row1-rack1:xe-0/0/0.0 family ethernet-switching port-mode trunk native-vlan-id 1 vlan members [2-25]
some helpful VLAN membership commands are: show vlans show vlans vlan-name detail show ethernet-switching interfaces brief show ethernet-switching interfaces node_identifier:interface_name-fpc/pic/port below is an example of the media access control (MAC) address table for the QFabric:
netadmin@qfabric> show ethernet-switching table Ethernet-switching table: 3 entries, 1 learned VLAN MAC address Type default * Flood default 00:10:db:ff:a0:01 Learn default 84:18:88:d5:ee:05 Static
Additional useful MAC address table commands include: show ethernet-switching table summary
13
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
Single-attached
Table 3: Node Group Selection Matrix for Rack Servers or Blade Switches with pass-Through Modules
ACTIVe/pASSIVe ACTIVe/ACTIVe
14
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
Network redundancy is not specific to TOr deployment, as it also exists for MOr or EOr. The same deployment principles apply to TOr, EOr, and MOr, with minor exceptions for MOr or EOr where, in a dual-homed connection scenario using modular switches, the second link can be connected to either a different module or a different chassis, depending on cost and rack space. In the case where blade chassis are used instead of rack servers, physical connectivity may vary depending on the blade chassis intermediary connection, pass-through module, or blade switches. Juniper recommends the passthrough module as it provides a direct connection between the servers and the QFabric architecture. This direct connection eliminates any oversubscription and the additional switching layer that is seen with blade switches. The deployment options for pass-through are exactly the same as described for rack servers. As for blade switches, depending on the vendor, they all have one thing in commonthey represent another device to manage, which adds complexity to the overall switching topology. Figure 5 shows the common network deployment between blade switches and access switches.
Single-homed
Dual-homed Active/Backup
Dual-homed Active/Active
Figure 5: Different deployment scenarios with embedded blade switches in blade chassis
Single-homed: Each blade switch has a LAG connection into a single access switch. In this deployment, there are no Layer 2 loops to worry about or manage. Dual-homed (active/backup): In this deployment, each access switch is a standalone device. since there are potential Layer 2 loops, the blade switch should support some sort of Layer 2 loop prevention sTP or active/backuplike technology, which will effectively block any redundant link to break the Layer 2 loop. Dual-homed (active/active): This deployment provides the most optimized deployment, as all links between the blade and access switches are active and forwarding and provide network resiliency. The connection between the blade switch and access switch is a LAG, which means the external switches must support either multichassis LAG or some form of stacking technology. since LAG is a single logical link between the blade and external switches, there are no Layer 2 loops to worry about or manage. Note: Figure 5 assumes that blade switches are separate entities and are not daisy-chained or logically grouped through a stacking technology. since QFabric architecture is a distributed system that acts as a single logical switch, the two most likely deployments are single-homed or dual-homed (active/active). The QFabric Nodes will be configured as sNG for single-homed and rsNG for dual-homed (active/active).
Table 4: Node Group Selection Matrix for Blade Chassis with embedded Blade Switches
ACTIVe/pASSIVe ACTIVe/ACTIVe
15
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
In this document, the first hop router is the QFabric architecture. Use cases where a wAN edge router such as one of Juniper Networks MX series 3D Universal routers, a security device such as one of Juniper Networks srX series services Gateways, or any other service layer devices (load balancer, wAN optimizer, service gateway) connect to the QFabric architecture as Layer 3 devices are discussed below.
SRX Series
WX Series
NNG
Junos Pulse Gateway SNG
SNG
Load Balancer
16
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
NNG
VLAN1100
VLAN1104
VLAN1101
VLAN1103
VLAN1102
[edit fabric] netadmin@qfabric# set aliases node-device ABCD1252 row21-rack1 netadmin@qfabric# set aliases node-device ABCD1253 row21-rack2 netadmin@qfabric# set aliases node-device ABCD1254 row21-rack3 netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# set set set set resources resources resources resources node-group node-group node-group node-group NW-NG-0 NW-NG-0 NW-NG-0 NW-NG-0 network-domain node-device row21-rack1 node-device row21-rack2 node-device row21-rack3
17
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
[edit] netadmin@qfabric# set chassis node-group NW-NG-0 aggregated-devices ethernet device-count 24 [edit interfaces] netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# set set set set set set set set interface-range interface-range interface-range interface-range interface-range interface-range interface-range interface-range LAG-ae0 LAG-ae0 LAG-ae0 LAG-ae0 LAG-ae1 LAG-ae1 LAG-ae1 LAG-ae1 member row21-rack1:xe-0/0/[0-1] member row21-rack2:xe-0/0/[0-1] member row21-rack3:xe-0/0/[0-1] ether-options 802.3ad ae0 member row21-rack1:xe-0/0/[2-3] member row21-rack2:xe-0/0/[2-3] member row21-rack3:xe-0/0/[2-3] ether-options 802.3ad ae0
netadmin@qfabric# set NW-NG-0:ae0 aggregated-ether-options lacp active netadmin@qfabric# set NW-NG-0:ae1 aggregated-ether-options lacp active
step 4. Assign IP address to LAG interfaces
[edit interfaces] netadmin@qfabric# set NW-NG-0:ae0.0 family inet address 192.168.0.1/24 netadmin@qfabric# set NW-NG-0:ae1.0 family inet address 192.168.0.2/24
step5: Configure rVI for five VLANs
step 7. Configure default routes to the MX series [Assumes that 192.168.0.254 is the address of the MX series Virtual Chassis configuration]
[edit routing-option] netadmin@qfabric# set routing-options static route 0.0.0.0/0 next-hop 192.168.0.254
18
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
netadmin@qfabric> show route terse inet.0: 16 destinations, 16 routes (16 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both A * * * * * * * * * * * * Destination 0.0.0.0/0 10.84.100.0/24 10.84.100.1/32 10.85.100.0/24 10.85.100.1/32 10.86.100.0/24 10.86.100.1/32 10.87.100.0/24 10.87.100.1/32 10.88.100.0/24 10.88.100.1/32 192.168.0.0/24 L P Prf S 5 D L D L D L D L D L D 0 L 0 0 Metric 1 0 0 0 0 0 0 0 0 0 0 Metric 2 Next hop AS path 192.168.0.254 NW-NG-0:vlan.1100 Local NW-NG-0:vlan.1101 Local NW-NG-0:vlan.1102 Local NW-NG-0:vlan.1103 Local NW-NG-0:vlan.1104 Local NW-NG-0:ae0.0 NW-NG-0:ae1.0 Local Local
* 192.168.0.1/32 * 192.168.0.2/32
Note: The MX series Virtual Chassis configuration will not be covered, since it is out of the scope of this document. Please visit www.juniper.net for more information about Virtual Chassis technology.
NNG
VLAN1100
VLAN1104
VLAN1101
VLAN1103
VLAN1102
OSPF Area0
19
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
[edit fabric] netadmin@qfabric# set aliases node-device ABCD1252 row21-rack1 netadmin@qfabric# set aliases node-device ABCD1253 row21-rack2 netadmin@qfabric# set aliases node-device ABCD1254 row21-rack3 netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric#
step 2. Define five VLANs
[edit] netadmin@qfabric# set chassis node-group NW-NG-0 aggregated-devices ethernet device-count 24 [edit interfaces] netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# set set set set set set set set interface-range interface-range interface-range interface-range interface-range interface-range interface-range interface-range LAG-ae0 LAG-ae0 LAG-ae0 LAG-ae0 LAG-ae1 LAG-ae1 LAG-ae1 LAG-ae1 member row21-rack1:xe-0/0/[0-1] member row21-rack2:xe-0/0/[0-1] member row21-rack3:xe-0/0/[0-1] ether-options 802.3ad ae0 member row21-rack1:xe-0/0/[2-3] member row21-rack2:xe-0/0/[2-3] member row21-rack3:xe-0/0/[2-3] ether-options 802.3ad ae0
netadmin@qfabric# set NW-NG-0:ae0 aggregated-ether-options lacp active netadmin@qfabric# set NW-NG-0:ae1 aggregated-ether-options lacp active
step 4. Assign IP address to LAG interfaces
[edit interfaces] netadmin@qfabric# set NW-NG-0:ae0.0 family inet address 192.168.0.2/30 netadmin@qfabric# set NW-NG-0:ae1.0 family inet address 192.168.1.2/30
step 5. Configure rVI for five VLANs
[edit interfaces] netadmin@qfabric# set netadmin@qfabric# set netadmin@qfabric# set netadmin@qfabric# set netadmin@qfabric# set
20
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
step 7. Enable OsPF and include LAG interface and rVI to area 0
[edit] root@SV-POC-QF> show ospf neighbor Address Interface 192.168.0.3 NW-NG-0:ae0.0 192.168.0.4 NW-NG-0:ae1.0
step 9. Verify routing table
ID 13.13.13.1 12.12.12.1
Dead 36 31
netadmin@qfabric> show route terse inet.0: 12 destinations, 12 routes (12 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both A * * * * * * * * * * * Destination 10.84.100.0/24 10.84.100.1/32 10.85.100.0/24 10.85.100.1/32 10.86.100.0/24 10.86.100.1/32 10.87.100.0/24 10.87.100.1/32 10.88.100.0/24 10.88.100.1/32 192.168.0.0/24 P Prf D L D L D L D L D L D 0 0 0 10 1 1 0 0 0 0 0 0 0 0 0 0 Metric 1 Metric 2 Next hop AS path NW-NG-0:vlan.1100 Local NW-NG-0:vlan.1101 Local NW-NG-0:vlan.1102 Local NW-NG-0:vlan.1103 Local NW-NG-0:vlan.1104 Local NW-NG-0:ae0.0 NW-NG-0:ae1.0 Local Local >192.168.0.3 MultiRecv
10
21
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
stub no-summaries interface NW-NG-0:ae0.0 interface NW-NG-0:ae1.0 interface vlan.1100 interface vlan.1101 interface vlan.1102 interface vlan.1103 interface vlan.1104
use Case 4: Connecting one-Armed SRX Series Device as Active/Active with QFabric Architecture
It is frequently required to connect firewalls to the core/aggregation device. The next two use cases will discuss how srX series services Gateways can be deployed with QFabric solutions. The diagram below shows a typical deployment in which two Juniper Networks srX5800 services Gateway devices running in active/active mode connect to an EX series/MX series device in a onearmed fashion.
Core/Edge Tier
SRX5800_A
EX Series/MX Series
SRX5800_B
VLAN 1000
VLAN 1001
22
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
when a customer migrates to the QFabric architecture, the one-armed deployment will appear as in Figure 10. There is no need to change the configuration on the srX5800 side. The fundamental QFabric solution configuration is the same as on the EX series/MX series devices in Figure 9.
SRX5800_A
to WAN Edge
SRX5800_B
VLAN 500, 1001, 1003, 1005 VLAN 600, 1000, 1002, 1004 VLAN 1000 VLAN 1001
Figure 10: one-armed SRX Series active/active deployment with QFabric technology
In this example, srX5800_A and srX5800_b connect to the QFabric solution as one-armed devices, deployed as an active/active cluster. The first VLAN trunk is handling VLANs 500, 1001, 1003, and 1005, while the second trunk handles VLANs 600, 1000, 1002, and 1004. This VLAN traffic will be distributed to the srX5800 cluster srX5800_A and srX5800_b. A solid line denotes the primary link for the given VLAN, while a dotted line indicates the backup. with the virtual router functions of QFabric architecture, inter-VLAN routing wont ensure that these two groups are totally isolated at the Layer 3 level. This is feasible in a multi-tenant environment. VLANs 500 and 600 will be used for uplink connections to the wAN edge router from the srX series under the set security zones security-zone uplink interface stanza. here the first VLAN trunk is in virtual router instance 10 (Vr10) while the second VLAN trunk is in Vr20. In addition, rVI VLANs 500 and 600 will be in Core Vr to provide uplink connection to the wAN edge routers. servers just need to send packets to the VrrP address on the srX series gateway in each rVI VLAN (1000 through 1005). Note that srX series configuration details are not covered since they are out of scope for this document. The following configuration examples focus on network node group configuration. Please review previous use case or the L2 design guide for server node group configuration information. step 1. Define QF/Node alias and NNG
[edit fabric] netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric#
aliases node-device ABCD1252 aliases node-device ABCD1253 aliases node-device ABCD1254 aliases node-device ABCD1255 resources node-group NW-NG-0 resources node-group NW-NG-0 resources node-group NW-NG-0 resources node-group NW-NG-0 resources node-group NW-NG-0
row21-rack1 row21-rack2 row21-rack3 row21-rack4 network-domain node-device row21-rack1 node-device row21-rack2 node-device row21-rack3 node-device row21-rack4
23
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
[edit vlans] netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric#
v500 vlan-id 500 v600 vlan-id 600 v1000 vlan-id 1000 v1001 vlan-id 1001 v1002 vlan-id 1002 v1003 vlan-id 1003 v1004 vlan-id 1004 v1005 vlan-id 1005
set interfaces trunk set interfaces members v1000 set interfaces members v1002 set interfaces members v1004 set interfaces members v500 set interfaces trunk set interfaces members v1001 set interfaces members v1003 set interfaces members v1005 set interfaces members v600
row21-rack3:xe-0/0/20 unit 0 family ethernet-switching port-mode row21-rack3:xe-0/0/20 unit 0 family ethernet-switching vlan row21-rack3:xe-0/0/20 unit 0 family ethernet-switching vlan row21-rack3:xe-0/0/20 unit 0 family ethernet-switching vlan row21-rack3:xe-0/0/21 unit 0 family ethernet-switching vlan row21-rack4:xe-0/0/20 unit 0 family ethernet-switching port-mode row21-rack4:xe-0/0/20 unit 0 family ethernet-switching vlan row21-rack4:xe-0/0/20 unit 0 family ethernet-switching vlan row21-rack4:xe-0/0/20 unit 0 family ethernet-switching vlan row21-rack4:xe-0/0/21 unit 0 family ethernet-switching vlan
[edit interfaces] netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric#
v500 l3-interface vlan.500 v600 l3-interface vlan.600 v1000 l3-interface vlan.1000 v1001 l3-interface vlan.1001 v1002 l3-interface vlan.1002 v1003 l3-interface vlan.1003 v1004 l3-interface vlan.1004 v1005 l3-interface vlan.1005
[edit interfaces] netadmin@qfabric# set vlan500.0 family inet address 10.84.100.1/24 netadmin@qfabric# set vlan600.0 family inet address 10.84.101.1/24
24
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
Configuring VR10 netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# interface all Configuring VR20 netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# interface all Configuring CoreVR netadmin@qfabric# netadmin@qfabric# rack1:xe-0/0/10.0 netadmin@qfabric# rack1:xe-0/0/11.0 netadmin@qfabric# rack2:xe-0/0/10.0 netadmin@qfabric# rack2:xe-0/0/11.0 netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# interface all
instance-type virtual-router interface vlan.1001 interface vlan.1003 interface vlan.1005 protocols ospf area 0.0.0.0
instance-type virtual-router interface vlan.1000 interface vlan.1002 interface vlan.1004 protocols ospf area 0.0.0.0
set routing-instances core instance-type virtual-router set protocols ospf area 0.0.0.0 interface row21set protocols ospf area 0.0.0.0 interface row21set protocols ospf area 0.0.0.0 interface row21set protocols ospf area 0.0.0.0 interface row21set routing-instances core interface vlan.500 set routing-instances core interface vlan.600 set routing-instances core protocols ospf area 0.0.0.0
use Case 5: Connecting one-Armed SRX Series as Active/Backup with QFabric Architecture
The srX series can also be deployed in an active/backup manner. Again, the configuration is simple with QFabric technology because it uses the same approach as the EX series switches. Users simply need to create a VLAN for terminating server connections, create an rVI (VLAN 100 in this case as shown in Figure 11) for uplink connection, and put rVI in L3 routing. The srX series devices are configured as the primary security gateway for their respective VLANs, so servers just need to send packets to the VrrP address of the srX series in each VLAN.
25
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
SRX5800_A
to WAN Edge
SRX5800_B
VLAN 1001, 1003, 1005 VLAN 1000, 1002, 1004 VLAN 100
Figure 11: one-armed SRX Series active/active deployment with QFabric architecture
step 1. Define QF/Node alias and NNG
[edit fabric] netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric#
step 2. Define VLANs
aliases node-device ABCD1252 aliases node-device ABCD1253 aliases node-device ABCD1254 aliases node-device ABCD1255 resources node-group NW-NG-0 resources node-group NW-NG-0 resources node-group NW-NG-0 resources node-group NW-NG-0 resources node-group NW-NG-0
row21-rack1 row21-rack2 row21-rack3 row21-rack4 network-domain node-device row21-rack1 node-device row21-rack2 node-device row21-rack3 node-device row21-rack4
v100 vlan-id 100 v1000 vlan-id 1000 v1001 vlan-id 1001 v1002 vlan-id 1002 v1003 vlan-id 1003 v1004 vlan-id 1004 v1005 vlan-id 1005
26
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
set interfaces trunk set interfaces members v1000 set interfaces members v1002 set interfaces members v1004 set interfaces members v100 set interfaces trunk set interfaces members v1001 set interfaces members v1003 set interfaces members v1005 set interfaces members v100
row21-rack3:xe-0/0/20 unit 0 family ethernet-switching port-mode row21-rack3:xe-0/0/20 unit 0 family ethernet-switching vlan row21-rack3:xe-0/0/20 unit 0 family ethernet-switching vlan row21-rack3:xe-0/0/20 unit 0 family ethernet-switching vlan row21-rack3:xe-0/0/21 unit 0 family ethernet-switching vlan row21-rack4:xe-0/0/20 unit 0 family ethernet-switching port-mode row21-rack4:xe-0/0/20 unit 0 family ethernet-switching vlan row21-rack4:xe-0/0/20 unit 0 family ethernet-switching vlan row21-rack4:xe-0/0/20 unit 0 family ethernet-switching vlan row21-rack4:xe-0/0/21 unit 0 family ethernet-switching vlan
[edit] netadmin@qfabric# rack1:xe-0/0/10.0 netadmin@qfabric# rack1:xe-0/0/11.0 netadmin@qfabric# rack2:xe-0/0/10.0 netadmin@qfabric# rack2:xe-0/0/11.0 netadmin@qfabric#
set protocols ospf area 0.0.0.0 interface row21set protocols ospf area 0.0.0.0 interface row21set protocols ospf area 0.0.0.0 interface row21set protocols ospf area 0.0.0.0 interface row21set protocols ospf area 0.0.0.0 interface vlan.100
27
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
use Case 6: Connecting one-Armed SRX Series Gateway to QFabric Architecture (VRF-Based Steering Mode)
If a customer would like to create a security zone per VrF basis and apply those security policies to inter-VrF traffic, QFabric needs to act as the first hop router, and the srX series will be used for services delivery only. with this model, it is important to note that the QFabric solution routes a significantly higher volume of traffic that doesnt need services, so that needs to be taken into consideration to avoid capacity or scaling problems. For example, Figure 12 shows that intra-VrF traffic (vlan.1001) wont hit the srX series, while inter-VrF traffic (vlan.1000 and vlan.1004) will.
SRX5800_A
to WAN Edge
SRX5800_B
VLAN 500, 1001, 1003, 1005 VLAN 600, 1000, 1002, 1004 VLAN 1000 VLAN 1001 VLAN 1004
netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# 0.0.0.0/0 next-hop netadmin@qfabric# interface all
set routing-instances set routing-instances set routing-instances set routing-instances set routing-instances x.x.x.x [VRRP address set routing-instances
VR-ZONE-A instance-type virtual-router VR-ZONE-A interface vlan.1000 VR-ZONE-A interface vlan.1001 VR-ZONE-A interface vlan.1002 VR-ZONE-A routing-options static route of each RVI on SRX] VR-ZONE-A protocols ospf area 0.0.0.0
28
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
Configuring Vr-ZONE-b
netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# 0.0.0.0/0 next-hop netadmin@qfabric# interface all
Configuring Core Vr
set routing-instances set routing-instances set routing-instances set routing-instances set routing-instances x.x.x.x [VRRP address set routing-instances
VR-ZONE-B instance-type virtual-router VR-ZONE-B interface vlan.1003 VR-ZONE-B interface vlan.1004 VR-ZONE-B interface vlan.1005 VR-ZONE-B routing-options static route of each RVI on SRX] VR-ZONE-B protocols ospf area 0.0.0.0
netadmin@qfabric# netadmin@qfabric# rack1:xe-0/0/10.0 netadmin@qfabric# rack1:xe-0/0/11.0 netadmin@qfabric# rack2:xe-0/0/10.0 netadmin@qfabric# rack2:xe-0/0/11.0 netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# interface all
set routing-instances core instance-type virtual-router set protocols ospf area 0.0.0.0 interface row21set protocols ospf area 0.0.0.0 interface row21set protocols ospf area 0.0.0.0 interface row21set protocols ospf area 0.0.0.0 interface row21set routing-instances core interface vlan.500 set routing-instances core interface vlan.600 set routing-instances core protocols ospf area 0.0.0.0
QFabric Director
160Gbps Fabric/ QFabric Node 8x10GbE LAG 8x10GbE LAG 8x10GbE LAG 8x10GbE LAG 8x10GbE LAG 8x10GbE LAG 8x10GbE LAG 8x10GbE LAG QFabric_1
QFabric Director
QFabric_2
29
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
[edit fabric] netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric# netadmin@qfabric#
set set set set set set set set set set set set set set
node-device node-device node-device node-device node-device node-device node-device node-device node-group node-group node-group node-group node-group node-group
ABCD1252 ABCD1253 ABCD1254 ABCD1255 ABCD1256 ABCD1257 ABCD1258 ABCD1259 NW-NG-0 NW-NG-0 NW-NG-0 NW-NG-0 NW-NG-0 NW-NG-0
row21-rack1 row21-rack2 row21-rack3 row21-rack4 row21-rack5 row21-rack6 row21-rack7 row21-rack8 network-domain node-device row21-rack1 node-device row21-rack2 node-device row21-rack3 node-device row21-rack4 node-device row21-rack5
netadmin@qfabric# set resources node-group Nw-NG-0 node-device row21-rack6 netadmin@qfabric# set resources node-group Nw-NG-0 node-device row21-rack7 netadmin@qfabric# set resources node-group Nw-NG-0 node-device row21-rack8
step 2. LAG configuration NNG connecting to QFabric 2 [edit] netadmin@qfabric# set chassis node-group Nw-NG-0 aggregated-devices ethernet device-count 24
[edit interfaces] netadmin@qfabric# set interface-range LAG-ae0 member row21-rack1:xe-0/0/[0-7] netadmin@qfabric# set interface-range LAG-ae0 ether-options 802.3ad ae0 netadmin@qfabric# set interface-range LAG-ae1 member row21-rack2:xe-0/0/[0-7] netadmin@qfabric# set interface-range LAG-ae1 ether-options 802.3ad ae0 netadmin@qfabric# set interface-range LAG-ae2 member row21-rack3:xe-0/0/[0-7] netadmin@qfabric# set interface-range LAG-ae2 ether-options 802.3ad ae0 netadmin@qfabric# set interface-range LAG-ae3 member row21-rack4:xe-0/0/[0-7] netadmin@qfabric# set interface-range LAG-ae3 ether-options 802.3ad ae0 netadmin@qfabric# set interface-range LAG-ae4 member row21-rack5:xe-0/0/[0-7] netadmin@qfabric# set interface-range LAG-ae4 ether-options 802.3ad ae0 netadmin@qfabric# set interface-range LAG-ae5 member row21-rack6:xe-0/0/[0-7] netadmin@qfabric# set interface-range LAG-ae5 ether-options 802.3ad ae0 netadmin@qfabric# set interface-range LAG-ae6 member row21-rack7:xe-0/0/[0-7] netadmin@qfabric# set interface-range LAG-ae6 ether-options 802.3ad ae0 netadmin@qfabric# set interface-range LAG-ae7 member row21-rack8:xe-0/0/[0-7] netadmin@qfabric# set interface-range LAG-ae7 ether-options 802.3ad ae0
30
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
netadmin@qfabric# set Nw-NG-0:ae0 aggregated-ether-options lacp active netadmin@qfabric# set Nw-NG-0:ae1 aggregated-ether-options lacp active netadmin@qfabric# set Nw-NG-0:ae2 aggregated-ether-options lacp active netadmin@qfabric# set Nw-NG-0:ae3 aggregated-ether-options lacp active netadmin@qfabric# set Nw-NG-0:ae4 aggregated-ether-options lacp active netadmin@qfabric# set Nw-NG-0:ae5 aggregated-ether-options lacp active netadmin@qfabric# set Nw-NG-0:ae6 aggregated-ether-options lacp active netadmin@qfabric# set Nw-NG-0:ae7 aggregated-ether-options lacp active netadmin@qfabric# set Nw-NG-0:ae8 aggregated-ether-options lacp active step 3. Add IP address to LAG interfaces [edit interfaces] netadmin@qfabric# set Nw-NG-0:ae0.0 family inet address 192.168.0.1/24 netadmin@qfabric# set Nw-NG-0:ae1.0 family inet address 192.168.1.1/24 netadmin@qfabric# set Nw-NG-0:ae2.0 family inet address 192.168.2.1/24 netadmin@qfabric# set Nw-NG-0:ae3.0 family inet address 192.168.3.1/24 netadmin@qfabric# set Nw-NG-0:ae4.0 family inet address 192.168.4.1/24 netadmin@qfabric# set Nw-NG-0:ae5.0 family inet address 192.168.5.1/24 netadmin@qfabric# set Nw-NG-0:ae6.0 family inet address 192.168.6.1/24 netadmin@qfabric# set Nw-NG-0:ae7.0 family inet address 192.168.7.1/24
Summary
The exponential data center demands exponential power, flexibility, and control, along with exponential reductions in energy consumption and TCO. The QFabric architecture with provides just such a flexible solution for deploying a fabric across the data center, enabling unique network designs that fundamentally simplify while maintaining any-to-any connectivity, reducing the number of managed devices and connections, and centralizing data center management. by following this design and implementation guide, Layer 3 QFabric architecture can be successfully deployed. The designs suggested in this document will help establish complete data center solutions by integrating MX series, srX series, and Juniper Networks Virtual Gateway products in a way that not only solves the increasing problems of scale and data center economics, but has the potential to enable dramatic new levels of computing for years to come.
31
IMPLEMENTATION GUIDE - Designing a Layer 3 Data Center Network with the QFabric Architecture
Corporate and Sales headquarters Juniper Networks, Inc. 1194 North Mathilda Avenue sunnyvale, CA 94089 UsA Phone: 888.JUNIPEr (888.586.4737) or 408.745.2000 Fax: 408.745.2100 www.juniper.net
ApAC headquarters Juniper Networks (hong kong) 26/F, Cityplaza One 1111 kings road Taikoo shing, hong kong Phone: 852.2332.3636 Fax: 852.2574.7803
eMeA headquarters Juniper Networks Ireland Airside business Park swords, County Dublin, Ireland Phone: 35.31.8903.600 EMEA sales: 00800.4586.4737 Fax: 35.31.8903.601
To purchase Juniper Networks solutions, please contact your Juniper Networks representative at 1-866-298-6428 or authorized reseller.
Copyright 2011 Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, Junos, Netscreen, and screenOs are registered trademarks of Juniper Networks, Inc. in the United states and other countries. All other trademarks, service marks, registered marks, 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.
8010083-001-EN
Nov 2011
32