Designing and Implementing a Junos Node Unifier Network

More documents

Recommendations

Info

JNU 1.2 Design and Implementation Guide JNU Management Network 8 The JNU architecture provides a private management plane for JNU that is separate from the control plane and the data plane. This design provides maximum performance and reliability and the ability to efficiently scale the JNU network. Figure 2 on page 8 shows a basic JNU management network. This network is created during the JNU initialization process. Figure 2: JNU Management Network Controller NMS, Syslog, NTP Secure session between controller and satellites (NETCONF SSH) Private IP subnet Private VLAN Satellites Private Management Plane for JNU on private routing instance g041394 Copyright © 2013, Juniper Networks, Inc.
The JNU management network is created during the JNU initialization process. The process creates a private network for in-band management, and the configuration is placed in a configuration group on the controller and on each satellite device. The management network has the following characteristics: • Ethernet interfaces are used for the connection between the controller and the satellites and between the controller and network management systems (NMSs). A private VLAN between the controller and the satellite devices is used to separate JNU management traffic from data plane traffic. During the initialization process, you specify the physical interfaces, VLAN IDs, and IP addresses to be used in the management network for the downlink connection from the controller to the satellites, and for the uplink connection from the satellites to the controller. By default the software places the Ethernet interfaces into an aggregated Ethernet bundle. If you specify only one physical interface during initialization, you have the option to not use aggregated Ethernet. • The following private routing instances are created on the controller during the initialization process. These routing instances are not visible outside of the JNU Network. • A private VPN routing and forwarding (VRF) routing instance to provide address for Layer 3 VPNs. The VRF routing instance makes it possible to reuse the management network IP addresses in the data plane. • A private virtual-switch routing instance is created on the controller for the Layer 2 VPN. The virtual-switch routing instances makes it possible to reuse the VLAN IDs in the data plane. An integrated routing and bridging (IRB) interface is created that is used to provide IP addresses to the virtual switch. • If supported, a routing instance is created on the satellite device that contains the uplink configuration from the satellite to the controller. • A secure NETCONF-over-SSH connection is created between the controller and the satellite device. Network Management in the Management Plane Copyright © 2013, Juniper Networks, Inc. During the controller initialization process, you have the option of setting up SNMP, system logging, and NTP. If you choose to set up these features, the initialization process creates a network configuration over an Ethernet interface to the NMS servers. The configuration includes static routes to these servers in the VPN routing and forwarding (VRF) routing instance on the controller. The initialization process creates a Network Address Translation (NAT) configuration that is used to translate the source address of the traffic sent to the SNMP or syslog server so that all network management traffic from the satellite devices originates from a source address on the controller. Chapter 2: Understanding the JNU Architecture You do not need a license to use NAT with the JNU management plane. 9
Page 1 and 2: Junos ® OS Designing and Implement
Page 3 and 4: Table of Contents Part 1 Introducti
Page 5 and 6: PART 1 Introduction to Junos Node U
Page 7 and 8: CHAPTER 1 Introduction to Junos Nod
Page 9 and 10: Basic Architecture of a JNU Network
Page 11: CHAPTER 2 Understanding the JNU Arc
Page 15 and 16: Related Documentation Copyright ©
Page 17 and 18: PART 2 Planning a JNU Implementatio
Page 19 and 20: CHAPTER 3 Planning Overview • Pla
Page 21 and 22: PART 3 Implementing JNU Copyright
Page 23 and 24: CHAPTER 4 Best Practices for Config
Page 25 and 26: CHAPTER 5 Getting Started with the
Page 27 and 28: Copyright © 2013, Juniper Networks
Page 35 and 36: Table 2: JNU Satellite Initializati
Page 45 and 46: CHAPTER 6 Configuring Junos OS Feat
Page 47 and 48: Configuring Junos Features with JNU
Page 49 and 50: CHAPTER 7 Committing Configurations
Page 51 and 52: Returning to a Previously Committed
Page 53 and 54: CHAPTER 8 JNU Operational Mode Comm
Page 55 and 56: config-template-name Syntax op conf
Page 57 and 58: jnu-commit Syntax op jnu-commit Rel
Page 59 and 60: Table 3: jnu-initialize-controller
Page 61 and 62: Table 3: jnu-initialize-controller
Page 63 and 64:
Copyright © 2013, Juniper Networks
Page 65 and 66:
jnu-remote Syntax op jnu-remote com
Page 67 and 68:
jnu-rollback Syntax op jnu-rollback
Page 69 and 70:
jnu-show-satellites jnu-show-satell
Page 71 and 72:
Page 73 and 74:
op Syntax op config-free-form devic
Page 75 and 76:
CHAPTER 9 Setting Up a Basic JNU Im
Page 77 and 78:
Table 5: Configuration Components U
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Step-by-Step Procedure routing-opti
Page 85 and 86:
Verification Step-by-Step Procedure
Page 87 and 88:
PART 4 Monitoring and Troubleshooti
Page 89 and 90:
CHAPTER 10 Monitoring in the JNU Ne
Page 91 and 92:
SNMP Get Process in the JNU Network
Page 93 and 94:
System Logging in the JNU Network R
Page 95 and 96:
Configuring the JNU Controller as a
show all

Designing and Implementing a Junos Node Unifier Network

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?