ENTERPRISE ROUTING: OSPF (USING EX SERIES ETHERNET SWITCHES AND MX SERIES 3D UNIVERSAL EDGE ROUTERS)

Transcription

1 IMPLEMENTATION GUIDE ENTERPRISE ROUTING: OSPF (USING EX SERIES ETHERNET SWITCHES AND MX SERIES 3D UNIVERSAL EDGE ROUTERS) 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. Copyright 2009, Juniper Networks, Inc. 1

2 Table of Contents Introduction Scope Design Considerations OSPF Areas IP Addressing and Summarization Route Selection Network Scalability Implementation Configuration Guidelines Verification Troubleshooting Implementation Example Network Topology Hardware Used for Validation Software Used for Validation Detailed Configurations Summary Appendix A: Conventions/Glossary Appendix B: Configurations EX-VC EX-VC EX-VC MX-B R About Juniper Networks Table of Figures Figure 1: OSPF Network Topology Copyright 2009, Juniper Networks, Inc.

3 Introduction The objective of this document is to provide an implementation guide for Layer 3 campus environments using OSPF. It is targeted for layer 3 deployments in campus networks where the Juniper Networks EX Series Ethernet Switches are used in the access layer while core and aggregation are collapsed into one layer using either the EX Series or Juniper Networks MX Series 3D Universal Edge Routers. This document provides general design considerations and configuration guidelines as well as verification and troubleshooting procedures. An implementation example is also included along with a detailed topology and configurations. Scope This guide focuses on implementing a campus network using OSPF. It does not discuss Layer 2 protocols implementation or designs including multiple Layer 3 protocols. These topics are discussed in separate documents. Targeted Audiences: This document is intended for network design and operation engineers or other technical audiences seeking implementation guidelines for Layer 3 campus deployments using the EX Series and MX Series. Design Considerations OSPF Areas Deciding which router should be included in each area and how areas are connected is a key step in implementing an OSPF design. The following aspects must be taken into consideration in regards to areas design: Redundancy: It is recommended to have redundancy in the backbone to avoid failure scenarios where a single link failure causes partition of the backbone area. When connecting individual areas to the backbone, it is recommended to have more than one area border router per area to minimize the chance of the area becoming disconnected from the backbone. Size: The size of OSPF areas should be kept small to increase stability. This is even more critical if some links are unstable or some old routers are present in the network. Contiguity: The OSPF backbone area must be contiguous. Non backbone areas should also be contiguous and must be physically connected to the backbone area. OSPF also includes the concept of virtual links. Since the stability of the virtual link depends on the transit area, it is recommended not to design an OSPF network to require the use of virtual links. Location of hosts: To create a stable environment and simplify future network expansions, hosts such as workstations or shared resources such as file servers should be kept out of the backbone area. IP Addressing and Summarization Route summarization in an OSPF network occurs between each area and the backbone area. Summarization increases scalability by reducing the routing table size. The effectiveness of route summarization depends highly on the addressing scheme implemented. Contiguity: Without a contiguous address space, it is not possible to implement route summarization. The addressing scheme should be configured so that the range of subnets assigned within an area is contiguous. Simplicity: When possible, subnets should be assigned according to simple octet boundaries to allow an addressing that is easy to remember. If this is not possible, the addressing scheme should be clearly defined and planned in advance so that changes can be implemented effectively. Flexibility: Address spaces should be chosen so that areas can be easily divided as the network grows. Because the addition of new routers creates a new topology, inserting new routers can impact performance when the OSPF topology is recomputed. Route summarization makes the design more flexible as changes to routes within one area does not affect the backbone or other areas. This way, new devices can be easily inserted as the network grows. Copyright 2009, Juniper Networks, Inc. 3

4 Route Selection OSPF metrics: Each interface running OSPF is assigned a cost, which is a unitless number that is inversely proportional to the bandwidth. The metric of a link can also be tuned by manual configuration to alter the route selection. When OSPF exports route information from external ASs, it includes an external metric in the route. There are two types of external metrics: Type 1 and Type 2. The difference between the two is in the way the cost of the route is calculated. The cost of a type 2 route is always the external cost, irrespective of the interior cost to reach that route. A type 1 cost is calculated by adding the external cost and the internal cost used to reach that route. A type 1 route is always preferred over a type 2 route for the same destination. Load Balancing: When multiple routes to the same destination exist with equal metrics, OSPF performs Equal-Cost Multipath (ECMP) load balancing between these routes. Routing Policies: Routing policies can be applied to OSPF to accommodate route redistribution, route tagging, and metric manipulation at autonomous systems boundary routers ASBRs. Network Scalability Controlling Inter-Area Traffic: OSPF areas can be configured as stub, totally-stub, and not-so-stubby areas to control inter-area traffic. This allows filtering at area border routers which reduces the size of the database and the amount of memory required on devices inside of theses areas. Stub areas do not carry AS external advertisements (Type 5 LSAs). When an area border router is configured for stub area operation, a default route can be generated to provide reachability to external destinations. Totally stubby areas block not only type 5 LSAs but also Type 3 summary LSAs. Not-So-Stubby areas allow Type 7 external routes to be flooded within the area and advertised to other areas. NSSA do not receive external from other areas. Memory: Memory utilization can be high on routers running OPSF as they must store link states for all of the areas that they are member of, in addition to summary and external LSAs. Route summarization and the use of stub areas are recommended to reduce memory use. CPU: Every time that a link state change occurs, routers running OPSF use CPU to compute the link state database. As discussed previously, it is recommended to reduce the size of areas and apply route summarization to minimize CPU usage and increase the stability of network. Implementation Configuration Guidelines This section shows how to implement an OSPF campus design using EX Series and MX Series configuration examples Interface and VLAN Configuration: The examples bellow shows two methods of assigning a VLAN to an interface: the first method consists into adding the VLAN under the interface stanza while the second one adds the interface under the VLAN stanza. EX: interfaces{ ge-0/0/23 { family ethernet-switching { port-mode access; members HR; 4 Copyright 2009, Juniper Networks, Inc.

5 EX: vlans { HR { vlan-id 100; interface { ge-0/0/23.0; Some users may be more familiar with the first configuration. The second configuration is more aligned with Juniper Networks Junos operating system configuration on other platforms as functionalities are grouped by feature rather than by interface. From a software perspective, both configurations are the same. RVI Configuration: The example below shows a Routed VLAN Interface (RVI) configuration on the EX Series. An l3-interface is added to the VLAN configuration and an IP address is assigned to the VLAN under the interface stanza. EX: vlans { HR { l3-interface vlan.100; interfaces{ unit 100 { address /24; Aggregated Ethernet Configuration: Below is an example of static configuration of an AE interface. Note that Aggregated Ethernet interfaces are created starting from ae0 upwards. For example, if the chassis Aggregated Ethernet device count is set to 2, interfaces ae0 and ae1 are created. It is therefore recommended to number the interfaces continuously starting from 0. The maximum number of aggregated Ethernet interfaces per EX 4200 and EX3200 chassis is 64 and 32 respectively. EX: chassis { aggregated-devices { ethernet { device-count 1; ge-1/1/0 { ether-options { 802.3ad ae0; ge-1/1/1 { ether-options { 802.3ad ae0; Copyright 2009, Juniper Networks, Inc. 5

6 interfaces { ae0 { address /30; OSPF Protocol Configuration: The example below shows OSPF configuration on an EX Series with one area. In this case, the Aggregated Ethernet interfaces are included in area 1. The loopback and VLAN interfaces are passive OSPF interfaces: they do not run OSPF but are advertised. Finally, the disable option ensures that the management interface excluded from OPSF. EX: routing-options { router-id ; interfaces { lo0 { address /32; protocols { ospf { area { interface lo0.0 { interface vme.0 { disable; interface vlan.100 { interface ae0.0; interface ae1.0; The router id is set manually under the routing-option hierarchy level. This is optional as Junos OS uses one of the router s IP addresses as router id in the absence of explicit configuration. If it is configured with an IP address, the loopback address is chosen first. 6 Copyright 2009, Juniper Networks, Inc.

7 The second example shows an ABR OSPF configuration on an MX Series: MX: routing-options { router-id ; interfaces { lo0 { unit 100 { address /32; protocols { ospf { area { interface ae0.0; interface ae1.0; area { interface ae2.0; interface ae3.0; area { interface ge-1/2/0.0; interface ge-1/2/1.0; interface lo0.100 { Route Redistribution: Route redistribution is performed by creating a policy statement and applying it to the OSPF routing instance. Below is an example where a static route redistribution policy is applied to OSPF. The static route with destination address /24 was defined to point to reject so that traceroutes to this address return a destination unreachable message. This is done for verification purpose. Note: The terms export and import in the ospf protocol configuration imply the direction of data flow with respect to the routing table. An export statement means that routes are exported from the routing table to the dynamic routing protocol it is applied to. Similarly, an import statement results in routes being imported into the routing table from the dynamic routing protocol. In the example below, the static route is being exported from the routing table into ospf, hence redistribution of the static route into OSPF. MX: policy-options { policy-statement stat { from protocol static; then accept; routing-options { static { Copyright 2009, Juniper Networks, Inc. 7

8 route /24 reject; protocols { ospf { export stat; Route Summarization: Route summarization is configured using the area-range statement under the ospf area hierarchy level as shown in the example below: MX: protocols { ospf { area { area-range /22; Stub Areas: In the example below, area 2 is configured as a stub area with a default route of metric equal to 10. Note that the stub area statement must be added to all routers that are in the area. EX: protocols { ospf { area { stub default-metric 10; GRES: Graceful Routing Engine Switchover is enabled at the chassis redundancy hierarchy level. Once GRES is enabled, the commit synchronize command must be issued so that the master and backup routing engines are synchronized. EX: chassis { redundancy { graceful-switchover; Protocol Graceful Restart: Graceful Restart is disabled by default. It is enabled globally for all routing protocols under the routing-options hierarchy level as shown below. Note that each neighbor of the restarting router must also support Graceful Restart. EX: routing-options { graceful-restart; 8 Copyright 2009, Juniper Networks, Inc.

9 Bidirectional Forwarding Detection: To enable BFD, the bfd-liveness-detection statement is added at the protocol interface configuration level. The minimum-interval parameter indicates the minimum time interval (in milliseconds) between hello packets sent to and received from a neighbor with which a BFD session has been established. Below is a BFD configuration example with OSPF: EX: protocols { ospf { interface ae0.0 { minimum-interval 100; interface ae1.0 { minimum-interval 100; Simple Password Authentication: The example below shows simple password authentication applied to OSPF: area 1 was configured with simple-password authentication with a password of juniper1. MX: protocols { ospf { area { interface ae0.0 { simple-password $9$2AoZjmfzCtOHqtO1RlegoJGHq ; ## SECRET-DATA Message Digest Authentication: The example below shows message digest authentication applied to OSPF: the backbone area was configured with MD5 authentication using juniper0 as key and 10 as key-id. MX: protocols { ospf { area { interface ge-1/2/0.0 { md5 10 key $9$KEAWX-YgJHqfVwqfTzCAvWLXdb ; ## SECRET-DATA Copyright 2009, Juniper Networks, Inc. 9

10 Load Balancing: Per-Prefix load balancing is enabled by default and does not require additional configuration. Configuration of per-flow load balancing can be done by including the load-balance per-packet action in a then statement in a routing policy and applying the policy as export to the forwarding table under routing-options forwarding-table stanza. An example is shown below: routing-options { forwarding-table { export PPpolicy; policy-options { policy-statement PPpolicy { then { load-balance per-packet; accept; Note: The configuration above results into per-flow behavior even though it refers to the per-packet action. This is because historically, platforms with Internet Processor I ASIC applied per-packet load balancing which introduced the potential that packets arrive out of order at the destination because of differential delay within the network. Newer Juniper Networks platforms apply per-flow load balancing. Verification Below are some of the commands that can be used to verify the OSPF setup: show ospf route show ospf database show ospf interface show ospf overview show ospf neighbor show ospf statistics show ospf io-statistics show ospf log traceroute The following command can be used to restart the RPD (Routing Protocol Process) and verify graceful restart: restart routing One of the following commands can be used for testing purpose to cause a routing engine switchover: request chassis routing-engine master switch request system reboot member <member> The following procedure can be followed to verify if the backup RE is ready for GRES: request session member <id> show system switchover start shell sysctl a grep gres exit 10 Copyright 2009, Juniper Networks, Inc.

11 Troubleshooting The following commands can be used for troubleshooting: clear ospf database clear ospf neighbors set protocols ospf traceoptions file <filename> set protocols ospf traceoptions flag error detail set protocols ospf traceoptions flag lsa-update detail set protocols ospf traceoptions flag hello detail set protocols ospf traceoptions flag state monitor start monitor stop show log messages match to Down show log mastership show system core-dumps show log ksyncd Copyright 2009, Juniper Networks, Inc. 11

12 Implementation Example Network Topology OSPF Area ge-0/0/ /30 M7i-R1 orange ge-0/0/ /30 ge-1/2/ /30 ge-1/2/ /30 ge-1/2/ /30 ge-1/2/ /30 MX-B aveo ae0 ge-1/0/0, ge-1/0/ /30 ae1 ge-1/0/1, ge-1/0/ /30 ae3 ge-1/0/3, ge-1/0/ /30 ae2 ge-1/0/2, ge-1/0/ /30 ae0 ge-1/0/0, ge-1/0/ /30 ae1 ge-1/0/1, ge-1/0/ /30 MX-A sumo ae3 ge-1/0/3, ge-1/0/ /30 ae2 ge-1/0/2, ge-1/0/ /30 Area-range: / /22 OSPF Area Stub, Default route OSPF Area Stub, Default route Area-range: / /22 ae0 ge-0/1/0, ge-1/1/ /30 ae1 ae0 ge-0/1/1, ge-1/1/1 ge-0/1/0, ge-1/1/ / /30 ae1 ae0 ge-0/1/1, ge-1/1/1ge-0/1/0, ge-1/1/ / /30 ae1 ae0 ge-0/1/1, ge-1/1/1ge-0/1/0, ge-1/1/ / /30 ae1 ge-0/1/1, ge-1/1/ /30 EX-VC-4, Backup EX-VC-7, LC1 EX-VC-10, LC1 EX-FC-2 ge-0/0/19 EX-VC-13, ge-0/0/0 LC1 ge-0/0/1 EX-VC-3, LC2 Virtual Chassis A EX-VC-6, backup Virtual Chassis B EX-VC-9, Backup Virtual Chassis C EX-VC-12, Backup Virtual Chassis D EX-VC-2, LC1 EX-VC-5, Master EX-VC-8, Master EX-VC-11, Master ge-2/0/23 ge-0/0/0 ge-2/0/23 ge-2/0/0 ge-2/0/23 ge-0/0/0 ge-0/0/1 EX-VC-1, Master VLAN 100 ge-0/0/0 VLAN 200 ge-0/0/1 VLAN ge-0/0/23 VLAN 300 VLAN 300 VLAN 400 VLAN 400 VLAN VLAN 500 VLAN /1 201/3 Agilent N2X tester 201/4 201/2 Figure 1: OSPF Network Topology 12 Copyright 2009, Juniper Networks, Inc.

13 RVIS Virtual Chassis A: vlan.100: /24 vlan.200: /24 Virtual Chassis B: vlan.300: /24 Virtual Chassis C: vlan.400: /24 Virtual Chassis D: vlan.500: /24 vlan.700: /24 LOOPBACKS MX-A: EX-VC-11: R1: MX-B: EX-VC-1: EX-VC-5: EX-VC-8: STATIC ROUTES MX-A and MX-B: / /24 AUTHENTICATION Area0: Area1: Area2: MD5 Key=juniper0, key-id=10 Text password = juniper1 Text password = juniper2 N2X TRAFFIC STREAMS 201/1 <-> 201/2 201/3 <-> 201/4 Hardware Used for Validation EQUIPMENT COMPONENTS 13 x Juniper Networks EX4200 Ethernet Switch 8 x 4-port uplink 1GbE module (EX-UM-4SFP) 16 SFPs 13 x VCP cables 1 x Juniper Networks MX480 Ethernet Services Router 1 x Juniper Networks MX240 Ethernet Services Router Juniper Networks M7i Multiservice Edge Router Agilent N2X tester 2 x 40-port 1GbE L2/L3 DPCs (DPCE-R-40GE-SFP or DPCE-R- Q-40GE-SFP) 20 SFPs 1 x 4 port GbE FPC 2 SFPs 4 x 10/100/1000Mb ports Software Used for Validation EQUIPMENT COMPONENTS EX Series, MX Series and M Series Junos OS 9.1 Copyright 2009, Juniper Networks, Inc. 13

14 Detailed Configurations The detailed configurations for EX-VC-1 and MX-A are listed below. The rest of the configurations is included in Appendix B. EX-VC-1 truncated MX-A truncated chassis { redundancy { graceful-switchover; aggregated-devices { ethernet { device-count 2; interfaces { ge-0/0/0 { family ethernet-switching { port-mode access; members HR; ge-0/0/1 { family ethernet-switching { port-mode access; members ENG; ge-0/0/23 { family ethernet-switching { port-mode access; members HR; ge-0/1/0 { ether-options { 802.3ad ae0; ge-0/1/1 { ether-options { 802.3ad ae1; chassis { aggregated-devices { ethernet { device-count 4; interfaces { ge-1/0/0 { 802.3ad ae0; ge-1/0/1 { 802.3ad ae1; ge-1/0/2 { 802.3ad ae2; ge-1/0/3 { 802.3ad ae3; ge-1/0/4 { 802.3ad ae0; ge-1/0/5 { 802.3ad ae1; ge-1/0/6 { 802.3ad ae2; ge-1/0/7 { 802.3ad ae3; ge-1/2/0 { 14 Copyright 2009, Juniper Networks, Inc.

15 ge-1/1/0 { ether-options { 802.3ad ae0; ge-1/1/1 { ether-options { 802.3ad ae1; ae0 { address /30; ae1 { address /30; lo0 { address /32; unit 100 { address /24; unit 200 { address /24; vme { address /24; routing-options { graceful-restart; router-id ; protocols { ospf { traceoptions { file ospf; address /30; ge-1/2/1 { address /30; ae0 { address /30; ae1 { address /30; ae2 { address /30; ae3 { address /30; fxp0 { address /24; lo0 { address /32; routing-options { graceful-restart; static { route /24 reject; route /24 reject; Copyright 2009, Juniper Networks, Inc. 15

16 flag error detail; flag lsa-update detail; flag hello detail; area { stub default-metric 10; interface lo0.0 { interface vme.0 { disable; interface vlan.100 { interface vlan.200 { interface ae0.0 { simple-password $9$KRdWX-YgJHqfVwqfTzCAvWLxVw ; ## SECRET- DATA interface ae1.0 { simple-password $9$pUpQOIcKMXbs4yls4aZkquO1Ryl ; ## SECRET- DATA vlans { ENG { vlan-id 200; l3-interface vlan.200; HR { vlan-id 100; l3-interface vlan.100; virtual-chassis { preprovisioned; /* ex-vc-1 */ member 0 { role routing-engine; serial-number BM ; /* ex-vc-4 */ member 1 { router-id ; protocols { ospf { traceoptions { file ospf; flag error detail; flag lsa-update detail; flag hello detail; export stat; area { stub default-metric 10; area-range /28; area-range /22; interface ae0.0 { simple-password $9$jbkmT69pRhrz3hrev7Nik.Pz3 ; ## SECRET- DATA interface ae1.0 { simple-password $9$9qB3t0IylMNdsEcds24DjCtuOEc ; ## SECRET- DATA area { stub default-metric 10; area-range /28; area-range /22; interface ae2.0 { simple-password $9$XAqNVYJGifT3goT369OBxNdw4a ; ## SECRET- DATA interface ae3.0 { simple-password $9$IMPhyKX7V4aUM8aUjH5TRhSlWL ; ## SECRET- DATA 16 Copyright 2009, Juniper Networks, Inc.

17 role routing-engine; serial-number BP ; /* ex-vc-2 */ member 2 { role line-card; serial-number BR ; /* ex-vc-3 */ member 3 { role line-card; serial-number BR ; area { interface ge-1/2/0.0 { md5 10 key $9$twQ401hevLVwgSrwgoJHkp0B1cy ; ## SECRET- DATA interface ge-1/2/1.0 { md5 10 key $9$S-TlvLdb2GDkxNDk.P3nylKvX7 ; ## SECRET-DATA interface lo0.0 { interface fxp0.0 { disable; policy-options { policy-statement stat { from protocol static; then accept; Summary In layer 2 environments, network administrators are faced with the task of preventing and possibly troubleshooting loops and broadcast storms. The EX Series offer OSPF as part of the base Junos OS. This makes OSPF a compelling alternative for campus deployments. This document provided configuration, verification and troubleshooting procedures for a routed campus network using the EX Series for access and the EX Series or MX Series for aggregation and OSPF as the routing protocol. An implementation example with a detailed network topology and device configurations is also included. Juniper customers can take advantage of the implementation example provided in this document to integrate the EX Series into their campus network and implement a design that provides optimal performance and flexibility as the business requirements of their network infrastructure evolve. Copyright 2009, Juniper Networks, Inc. 17

18 Appendix A: Conventions/Glossary AS BFD DPC ECMP GRES LAG LSA LSDB Autonomous System Bi-Directional Forwarding Detection Dense Port Concentrator Equal Cost Multi-Path Graceful Routing Engine Switchover Link Aggregation Group Link State Advertisement Link State Database MD5 Message Digest 5 OSPF RE RVI OSI SFP VC VLAN VoIP XFP Open Shortest Path First Routing Engine Routed VLAN Interface Open Systems Interconnection Small Form-factor Pluggable Virtual Chassis Virtual LAN Voice Over IP 10 Gigabit Small Form-factor Pluggable Appendix B: Configurations EX-VC-5 truncated chassis { aggregated-devices { ethernet { device-count 2; interfaces { ge-0/0/0 { family ethernet-switching { port-mode access; members SALES; ge-2/0/23 { family ethernet-switching { port-mode access; members SALES; 18 Copyright 2009, Juniper Networks, Inc.

19 ae0 { address /30; ae1 { address /30; lo0 { address /32; unit 300 { address /24; vme { address /24; routing-options { graceful-restart; router-id ; protocols { ospf { traceoptions { file ospf; flag error detail; flag lsa-update detail; flag hello detail; area { stub default-metric 10; interface ae0.0 { simple-password $9$PTF/uORlK8CtK8X7sYfTz3Ct ; ## SECRET-DATA Copyright 2009, Juniper Networks, Inc. 19

20 interface ae1.0 { simple-password $9$d4w2ajHmFnCZUnCtuEhVwYgZU ; ## SECRET-DATA interface vme.0 { disable; interface vlan.300 { interface lo0.0 { vlans { SALES { vlan-id 300; l3-interface vlan.300; virtual-chassis { preprovisioned; /* ex-vc-5*/ member 0 { role routing-engine; serial-number BP ; /* ex-vc-6 */ member 1 { role routing-engine; serial-number BQ ; /* ex-vc-7 */ member 2 { role line-card; serial-number BP ; poe { interface all; 20 Copyright 2009, Juniper Networks, Inc.

21 EX-VC-8 truncated chassis { redundancy { graceful-switchover; aggregated-devices { ethernet { device-count 2; interfaces { ge-0/0/0 { family ethernet-switching { port-mode access; members SUPPORT; ge-2/0/23 { family ethernet-switching { port-mode access; members SUPPORT; ae0 { address /30; ae1 { address /30; lo0 { address /32; unit 400 { address /24; Copyright 2009, Juniper Networks, Inc. 21

22 vme { address /24; routing-options { graceful-restart; router-id ; protocols { ospf { traceoptions { file ospf; flag error detail; flag lsa-update detail; flag hello detail; area { stub default-metric 10; interface ae0.0 { simple-password $9$XwxNVYJGifT3goT369OBxNdw4a ; ## SECRET-DATA interface ae1.0 { simple-password $9$Ku5WX-YgJHqfVwqfTzCAvWL7bs ; ## SECRET-DATA interface vlan.400 { interface vme.0 { disable; interface lo0.0 { vlans { SUPPORT { vlan-id 400; l3-interface vlan.400; virtual-chassis { 22 Copyright 2009, Juniper Networks, Inc.

23 preprovisioned; /* ex-vc-8 */ member 0 { role routing-engine; serial-number BN ; /* ex-vc-9 */ member 1 { role routing-engine; serial-number BP ; /* ex-vc-10 */ member 2 { role line-card; serial-number BP ; poe { interface all; Copyright 2009, Juniper Networks, Inc. 23

24 EX-VC-11 truncated chassis { redundancy { graceful-switchover; aggregated-devices { ethernet { device-count 2; interfaces { ge-0/0/0 { family ethernet-switching { port-mode access; members FINANCE; ge-0/0/1 { family ethernet-switching { port-mode access; members MARKETING; ge-1/1/0 { ether-options { 802.3ad ae0; ge-1/1/1 { ether-options { 802.3ad ae1; ge-2/0/23 { family ethernet-switching { port-mode access; members FINANCE; ae0 { address /30; 24 Copyright 2009, Juniper Networks, Inc.

25 ae1 { address /30; lo0 { address /32; unit 500 { address /24; unit 700 { address /24; vme { address /24; routing-options { graceful-restart; router-id ; protocols { ospf { traceoptions { file ospf; flag error detail; flag lsa-update detail; flag hello detail; area { stub default-metric 10; interface ae0.0 { simple-password $9$BQYRcl8X-24ZKM4ZUjPf1RhyvW ; ## SECRET-DATA interface ae1.0 { Copyright 2009, Juniper Networks, Inc. 25

26 simple-password $9$qPT3ApBSrv69rvWLVb.P5z/C ; ## SECRET-DATA interface vme.0 { disable; interface vlan.500 { interface vlan.700 { interface lo0.0 { vlans { FINANCE { vlan-id 500; l3-interface vlan.500; MARKETING { vlan-id 700; l3-interface vlan.700; virtual-chassis { preprovisioned; /* ex-vc-11 */ member 0 { role routing-engine; serial-number BP ; /* ex-vc-12 */ member 1 { role routing-engine; serial-number BP ; /* ex-vc-13 */ member 2 { role line-card; serial-number BP ; 26 Copyright 2009, Juniper Networks, Inc.

27 MX-B truncated chassis { aggregated-devices { ethernet { device-count 4; interfaces { ge-1/0/0 { 802.3ad ae0; ge-1/0/1 { 802.3ad ae1; ge-1/0/2 { 802.3ad ae2; ge-1/0/3 { 802.3ad ae3; ge-1/0/4 { 802.3ad ae0; ge-1/0/5 { 802.3ad ae1; ge-1/0/6 { 802.3ad ae2; ge-1/0/7 { 802.3ad ae3; ge-1/2/0 { address /30; ge-1/2/1 { Copyright 2009, Juniper Networks, Inc. 27

28 address /30; ae0 { address /30; ae1 { address /30; ae2 { address /30; ae3 { address /30; lo0 { address /32; routing-options { graceful-restart; static { route /24 reject; route /24 reject; router-id ; protocols { ospf { export stat; area { stub default-metric 10; area-range /28; area-range /22; interface ae0.0 { simple-password $9$gMaGiP5FApBk.pBIEeK4aZUk. ; ## SECRET-DATA 28 Copyright 2009, Juniper Networks, Inc.

29 interface ae1.0 { simple-password $9$sVgaUqmT/CujHCuO1yrYgoJjH ; ## SECRET-DATA area { stub default-metric 10; area-range /28; area-range /22; interface ae2.0 { simple-password $9$r8cKWxbs4Di.Ndi.P56/lKML-V ; ## SECRET-DATA interface ae3.0 { simple-password $9$H.fz9A0hSe36SevW-dk.PTn/ ; ## SECRET-DATA area { interface ge-1/2/0.0 { md5 10 key $9$TF6ABIcvWxp0WxNdg4QFn6tu ; ## SECRET-DATA interface ge-1/2/1.0 { md5 10 key $9$bFY4ZHqfn/tUj/tuOcSwYg4GD ; ## SECRET-DATA interface lo0.0 { interface fxp0.0 { disable; policy-options { policy-statement stat { from protocol static; then accept; Copyright 2009, Juniper Networks, Inc. 29

30 R1 truncated interfaces { ge-0/0/2 { address /30; ge-0/0/3 { address /30; lo0 { unit 100 { address /32; protocols { ospf { area { interface ge-0/0/2.0 { md5 10 key $9$yl2eMXVwgUjq7-jqmfn6revMxN ; ## SECRET-DATA interface ge-0/0/3.0 { md5 10 key $9$pL8MOIcKMXbs4yls4aZkquO1ISr ; ## SECRET-DATA interface lo0.100 { routing-options { graceful-restart; router-id ; 30 Copyright 2009, Juniper Networks, Inc.

31 About Juniper Networks Juniper Networks, Inc. is the leader in high-performance networking. Juniper offers a high-performance network infrastructure that creates a responsive and trusted environment for accelerating the deployment of services and applications over a single network. This fuels high-performance businesses. Additional information can be found at Corporate and Sales Headquarters APAC Headquarters EMEA Headquarters To purchase Juniper Networks solutions, Juniper Networks, Inc North Mathilda Avenue Sunnyvale, CA USA Phone: 888.JUNIPER ( ) or Fax: Juniper Networks (Hong Kong) 26/F, Cityplaza One 1111 King s Road Taikoo Shing, Hong Kong Phone: Fax: Juniper Networks Ireland Airside Business Park Swords, County Dublin, Ireland Phone: EMEA Sales: Fax: please contact your Juniper Networks representative at or authorized reseller. Copyright 2009 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 EN Dec 2009 Printed on recycled paper Copyright 2009, Juniper Networks, Inc. 31