Juniper JUNOS SPACE 2.0 - RELEASE NOTES, Руководство по установке

Страница: 23 / 64

Node Function Availability
In a fabric comprising two or more nodes, Junos Space provides failover when a node
functioning as the active server (load balancer server or database server) goes down. By
default, Junos Space marks a particular node down and routes failover requests to the
node that Junos Space designates as standby server. Junos Space uses a heartbeat
mechanism to check whether the nodes in the fabric are running. When a node functioning
as the active server fails (the appliance physically crashes or stops sending heartbeats),
the node functioning as the standby server takes over all resources that were managed
by the node functioning as active server.
Understanding How Junos Space Uses Ethernet Interfaces eth0 and eth3
Junos Space is designed to perform best using only eth0 if the managed devices are
routable, using in-bound management. Use eth3 for a device management subnet if the
managed devices are non-routable or on an out-of-band management subnet.
Table 2 on page 9 describes how Junos Space interfaces intentionally function:
Table 2: How Junos Space IP Addresses Function
Function /Interface
SSH and device management if eth3 is not configured (node IP) eth0
GUI interface with an instance of JBOSS running (GUI) eth0:0
Not supported eth1
Not supported eth2
Device management when managed devices are on a subnet and not reacheable
by way of eth0. eth3
Junos Space uses eth0 and eth3 interfaces as follows:
•
Secure Shell Daemon (sshd) is listening on all IP addresses.
• The web interface is only on the VIP, the same subnet as eth0.
• Device management, outbound (discover) and inbound (post-discovery), including
syslog and DMI, should be eth3, or eth0 if eth3 is not configured.
Related
Documentation
9 Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Installation Overview