manual
Table Of Contents
- Introduction
- Scope
- Design Considerations—Connectivity at the Branch Office
- Branch-Office Connectivity over IPsec VPN
- Design Recommendations
- Routing Information Protocol
- Traffic Load Balancing for Type B and Type C Branch Deployments
- Using Border Gateway Protocol for Large Networks
- Using OSPF for Small Number of Branch Offices
- Using Auto Connect VPN to Create Branch-to-Branch IPsec Tunnels
- High Availability for the Branch Office
- High Availability Requirement Levels (Link, Device, Device, and Link Levels)
- High Availability Functionalities
- High Availability for Branch Office Type A
- VPN Security Zone Configuration for Type A
- High Availability for Branch Office Type B
- Using Secure Services Gateway for Type B
- High Availabilty for Branch Office Type C
- Connectivity at the Data Center
- Implementing a High Availability Enterprise Network at the Data Center
- Quality of Service Design Requirements
- WX Design Requirements
- Summary
- Appendix A Related Documents
- Appendix B Naming Conventions
- Appendix C Products
- About Juniper Networks
- Figure 1: Connecting branch offices, campus locations, and data centers over a single converged network
- Figure 2: Branch office reference architecture
- Figure 3: Multi-tiered/layered network architecture
- Figure 4: Two-tier network design for data centers
- Figure 5: Branch with dual internet connections (load balancing using ECMP)
- Figure 6: BGP routing design
- Figure 7: Star topology – connecting branches to central hub
- Figure 8: AC VPN provisioned tunnels between branches in the same region
- Figure 9: Multi-tier topology
- Figure 10: HA configuration for Type A
- Figure 11: VPN security zone configuration for Type A
- Figure 12: Type B optimized – HA configuration
- Figure 13: Type B – security zones
- Figure 14: Type C – HA configuration
- Figure 15: Intra-branch using OSPF
- Figure 16: Branch Type C – security zones
- Figure 17: Enterprise network for the data center
- Figure 18: M Series Multiservice Edge Routers
- Figure 19: Internet firewalls
- Figure 20: VPN firewalls
- Figure 21: VPN firewall IPS policy
- Figure 2: Branch office reference architecture
32 Copyright © 2010, Juniper Networks, Inc.
APPLICATION NOTE - Branch Office Connectivity Guide
Appendix B Naming Conventions
M Series and J Series Interface Naming Conventions
The following provides the naming conventions used for all of the interfaces on the M Series and J Series routers.
M Series Interface Names
On the M Series Multiservice Edge Routers, when you display information about an interface, you specify the
interface type, the slot in which the FPC is installed, the slot on the FPC in which the PIC is located, and the
configured
port number.
In the physical part of the interface name, a hyphen (-) separates the media type from the FPC number, and a slash
(/) separates the FPC, PIC, and port numbers:
type-fpc/pic/port
Logical Part of an Interface Name (M Series Routers)
The logical unit part of the interface name corresponds to the logical unit number, which can be a number from 0
through 16384. In the virtual part of the name, a period (.) separates the port and logical unit numbers:
type-fpc/pic/port.logical
Example: “ge-0/1/0.0” indicates a Gigabit Ethernet connection - FPC 0, PIC 1, Physical Port 0.Logical Unit 0
J Series Interface Names
On the J Series Services Routers, when you display information about an interface, you specify the interface type, the
slot in which the Physical Interface Module (PIM) is installed, 0, and the configured port number.
In the physical part of the interface name, a hyphen (-) separates the media type from the PIM number, and a slash
(/) separates the PIM, 0, and port numbers:
type-pim/0/port
Example: “fe-0/1/0.0” indicates a Fast Ethernet connection - PIM 0 Slot 1/0/Physical Port 0.Logical Unit 0
SSG Series and ISG Series Interfaces
The SSG Series and ISG Series devices include integrated 10/100/1000 interfaces. It does not use a modifier to
indicate the distinction between 10/100 and Gigabit Ethernet connections. The SSG Series and ISG Series naming
convention is simplified as shown in the following:
Example: “ethernet0/0” indicates Ethernet interface 0/port 0