Hide Navigation Pane
Show Navigation Pane
Feedback
Download
SHA1
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 8 describes how Junos Space interfaces intentionally function:
Table 8: How Junos Space IP Addresses Function
/Interface | Function |
|---|---|
eth0 | SSH and device management if eth3 is not configured (node IP) |
eth0:0 | GUI interface with an instance of JBOSS running (GUI) |
eth1 | Not supported |
eth2 | Not supported |
eth3 | Device management when managed devices are on a subnet and not reacheable by way of eth0. |
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.
