Example network configuration with Access 3340 appliance
Support for multiple subnets was introduced at patch 7.4.2.200 and improved at patch 7.4.2.301. In the following scenarios patch 7.4.2.301 is assumed.
- Scenario 1. Bonding the public interfaces.
- Scenario 2. Configuring a VLAN.
- Scenario 3. Splitting existing configuration into management and data subnets
- Scenario 4. Configuring multiple subnets for public interfaces.
Scenario 1. Bonding the public interfaces.
Bonding can be configured during initial cluster configuration. In this example, bonding is configured after the cluster has been configured. The required bonding mode is 'active-backup'.
va742> network ip addr show
IP Netmask/Prefix Device Node Type Status
-- -------------- ------ ---- ---- ------
192.168.10.125 255.255.255.0 eth4 va742-01 Physical
192.168.10.126 255.255.255.0 eth5 va742-01 Physical
192.168.10.127 255.255.255.0 eth4 va742-02 Physical
192.168.10.128 255.255.255.0 eth5 va742-02 Physical
192.168.10.130 255.255.255.0 eth4 va742-01 Virtual ONLINE (Con IP)
192.168.10.140 255.255.255.0 eth4 va742-02 Virtual ONLINE
192.168.10.141 255.255.255.0 eth4 va742-01 Virtual ONLINE
192.168.10.142 255.255.255.0 eth5 va742-02 Virtual ONLINE
192.168.10.143 255.255.255.0 eth5 va742-01 Virtual ONLINE
va742> network bond create eth4,eth5 active-backup
va742> network ip addr show
IP Netmask/Prefix Device Node Type Status
-- -------------- ------ ---- ---- ------
192.168.10.125 255.255.255.0 bond0 va742-01 Physical
192.168.10.127 255.255.255.0 bond0 va742-02 Physical
192.168.10.126 255.255.255.0 ( unused ) Physical
192.168.10.128 255.255.255.0 ( unused ) Physical
192.168.10.130 255.255.255.0 bond0 va742-01 Virtual ONLINE (Con IP)
192.168.10.140 255.255.255.0 bond0 va742-01 Virtual ONLINE
192.168.10.141 255.255.255.0 bond0 va742-01 Virtual ONLINE
192.168.10.142 255.255.255.0 bond0 va742-02 Virtual ONLINE
192.168.10.143 255.255.255.0 bond0 va742-02 Virtual ONLINE
Tidy up the configuration by removing the unused physical IP addresses and the unwanted virtual IP addresses.
va742> network ip addr del 192.168.10.142
va742> network ip addr del 192.168.10.143
va742> network ip addr del 192.168.10.128
va742> network ip addr del 192.168.10.126
va742> network ip addr show
IP Netmask/Prefix Device Node Type Status
-- -------------- ------ ---- ---- ------
192.168.10.125 255.255.255.0 bond0 va742-01 Physical
192.168.10.127 255.255.255.0 bond0 va742-02 Physical
192.168.10.130 255.255.255.0 bond0 va742-01 Virtual ONLINE (Con IP)
192.168.10.140 255.255.255.0 bond0 va742-02 Virtual ONLINE
192.168.10.141 255.255.255.0 bond0 va742-01 Virtual ONLINE
Scenario 2. Configuring a VLAN.
A VLAN device can only be configured after the the initial cluster configuration. In this example a single subnet 192.168.10.0/24 has been configured and the requirement is to configure a VLAN device using physical device bond0 with a tag of 21. The VLAN uses a different subnet of 192.168.30.0/24
Initial network configuration:
va742> network ip addr show
IP Netmask/Prefix Device Node Type Status
-- -------------- ------ ---- ---- ------
192.168.10.125 255.255.255.0 bond0 va742-01 Physical
192.168.10.127 255.255.255.0 bond0 va742-02 Physical
192.168.10.130 255.255.255.0 bond0 va742-01 Virtual ONLINE (Con IP)
192.168.10.140 255.255.255.0 bond0 va742-02 Virtual ONLINE
192.168.10.141 255.255.255.0 bond0 va742-01 Virtual ONLINE
We must first add 2 new IP addresses on the new subnet to be used with the VLAN device
va742> network ip addr add 192.168.30.126 255.255.255.0 physical
va742> network ip addr add 192.168.30.128 255.255.255.0 physical
va742> network ip addr show
IP Netmask/Prefix Device Node Type Status
-- -------------- ------ ---- ---- ------
192.168.10.125 255.255.255.0 bond0 va742-01 Physical
192.168.10.127 255.255.255.0 bond0 va742-02 Physical
192.168.30.126 255.255.255.0 ( unused ) Physical
192.168.30.128 255.255.255.0 ( unused ) Physical
192.168.10.130 255.255.255.0 bond0 va742-01 Virtual ONLINE (Con IP)
192.168.10.140 255.255.255.0 bond0 va742-02 Virtual ONLINE
192.168.10.141 255.255.255.0 bond0 va742-01 Virtual ONLINE
Now add the VLAN device. The new device is configured with the 2 unused IP addresses.
va742> network vlan add bond0 21
va742> network ip addr show
IP Netmask/Prefix Device Node Type Status
-- -------------- ------ ---- ---- ------
192.168.10.125 255.255.255.0 bond0 va742-01 Physical
192.168.10.127 255.255.255.0 bond0 va742-02 Physical
192.168.30.126 255.255.255.0 bond0.21 va742-01 Physical
192.168.30.128 255.255.255.0 bond0.21 va742-02 Physical
192.168.10.130 255.255.255.0 bond0 va742-01 Virtual ONLINE (Con IP)
192.168.10.140 255.255.255.0 bond0 va742-02 Virtual ONLINE
192.168.10.141 255.255.255.0 bond0 va742-01 Virtual ONLINE
Check the routing table for this subnet. The following output is snipped to show only the relevant routing tableva742> network ip route show
IPv4 routing table: 1
=====================
Destination Gateway Genmask Flags MSS Window irtt Iface
============ ======= ============= ===== === ====== ==== ========
192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0.21
Add a default route for the new subnet
va742> network ip route add all 0.0.0.0 0.0.0.0 via 192.168.30.1 dev bond0.21 scope=local
va742> network ip route show
IPv4 routing table: 1
=====================
Destination Gateway Genmask Flags MSS Window irtt Iface
============ ============ ============= ===== === ====== ==== ========
0.0.0.0 192.168.30.1 0.0.0.0 UG 0 0 0 bond0.21
192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0.21
Add 2 virtual IP addresses using the new subnet:
va742> network ip addr add 192.168.30.140 255.255.255.0 virtual bond0.21
va742> network ip addr add 192.168.30.141 255.255.255.0 virtual bond0.21
va742> network ip addr show
IP Netmask/Prefix Device Node Type Status
-- -------------- ------ ---- ---- ------
192.168.10.125 255.255.255.0 bond0 va742-01 Physical
192.168.10.127 255.255.255.0 bond0 va742-02 Physical
192.168.30.126 255.255.255.0 bond0.21 va742-01 Physical
192.168.30.128 255.255.255.0 bond0.21 va742-02 Physical
192.168.10.130 255.255.255.0 bond0 va742-01 Virtual ONLINE (Con IP)
192.168.10.140 255.255.255.0 bond0 va742-02 Virtual ONLINE
192.168.10.141 255.255.255.0 bond0 va742-01 Virtual ONLINE
192.168.30.140 255.255.255.0 bond0.21 va742-01 Virtual ONLINE
192.168.30.141 255.255.255.0 bond0.21 va742-02 Virtual ONLINE
Scenario 3. Splitting existing configuration into management and data subnets.
This functionality was added with patch 7.4.2.100. See the patch release notes for more detailed examples.
Patch 7.4.2.100 readme
The initial network configuration:
eth1, eth4 and eth5 are on the same subnet 192.168.10.0/24 default gateway 192.168.10.1
Access cluster VIP is on eth4
It is required to split into separate management and data subnets:
management subnet using eth1 interface. 192.168.10.0/24 default gateway 192.168.10.1
Access cluster VIP should use eth1 interface
data subnet using eth4 and eth5. 192.168.30.0/24 default gateway 192.168.30.1
Initial Configuration:
va742-01.Network> Show Status
eth1 : 1Gb/s TP PLUGGED|UP 192.168.10.120 - No IPv6 -
va742-02.Network> Show Status
eth1 : 1Gb/s TP PLUGGED|UP 192.168.10.121 - No IPv6 -
va742> network ip addr show
IP Netmask/Prefix Device Node Type Status
-- -------------- ------ ---- ---- ------
192.168.10.125 255.255.255.0 eth4 va742-01 Physical
192.168.10.126 255.255.255.0 eth5 va742-01 Physical
192.168.10.127 255.255.255.0 eth4 va742-02 Physical
192.168.10.128 255.255.255.0 eth5 va742-02 Physical
192.168.10.130 255.255.255.0 eth4 va742-01 Virtual ONLINE (Con IP)
192.168.10.140 255.255.255.0 eth4 va742-02 Virtual ONLINE
192.168.10.141 255.255.255.0 eth4 va742-01 Virtual ONLINE
192.168.10.142 255.255.255.0 eth5 va742-02 Virtual ONLINE
192.168.10.143 255.255.255.0 eth5 va742-01 Virtual ONLINE
Add eth1 interface to Access Cluster configuration
va742> network device add eth1
va742> network ip addr show
IP Netmask/Prefix Device Node Type Status
-- -------------- ------ ---- ---- ------
192.168.10.121 255.255.255.0 eth1 va742-02 Physical
192.168.10.120 255.255.255.0 eth1 va742-01 Physical
192.168.10.125 255.255.255.0 eth4 va742-01 Physical
192.168.10.126 255.255.255.0 eth5 va742-01 Physical
192.168.10.127 255.255.255.0 eth4 va742-02 Physical
192.168.10.128 255.255.255.0 eth5 va742-02 Physical
192.168.10.130 255.255.255.0 eth4 va742-01 Virtual ONLINE (Con IP)
192.168.10.140 255.255.255.0 eth4 va742-02 Virtual ONLINE
192.168.10.141 255.255.255.0 eth4 va742-01 Virtual ONLINE
192.168.10.142 255.255.255.0 eth5 va742-02 Virtual ONLINE
192.168.10.143 255.255.255.0 eth5 va742-01 Virtual ONLINE
Move Console VIP to eth1 interface
va742> network ip addr modify 192.168.10.130 192.168.10.130 255.255.255.0 eth1
va742> network ip addr show
IP Netmask/Prefix Device Node Type Status
-- -------------- ------ ---- ---- ------
192.168.10.121 255.255.255.0 eth1 va742-02 Physical
192.168.10.120 255.255.255.0 eth1 va742-01 Physical
192.168.10.125 255.255.255.0 eth4 va742-01 Physical
192.168.10.126 255.255.255.0 eth5 va742-01 Physical
192.168.10.127 255.255.255.0 eth4 va742-02 Physical
192.168.10.128 255.255.255.0 eth5 va742-02 Physical
192.168.10.130 255.255.255.0 eth1 va742-02 Virtual ONLINE (Con IP)
192.168.10.140 255.255.255.0 eth4 va742-02 Virtual ONLINE
192.168.10.141 255.255.255.0 eth4 va742-01 Virtual ONLINE
192.168.10.142 255.255.255.0 eth5 va742-02 Virtual ONLINE
192.168.10.143 255.255.255.0 eth5 va742-01 Virtual ONLINE
Move physical IP's for eth4 and eth5 interfaces to the new subnet
va742> network ip addr modify 192.168.10.125 192.168.30.125 255.255.255.0
va742> network ip addr modify 192.168.10.126 192.168.30.126 255.255.255.0
va742> network ip addr modify 192.168.10.127 192.168.30.127 255.255.255.0
va742> network ip addr modify 192.168.10.128 192.168.30.128 255.255.255.0
Move Virtual IP's for eth4 and eth5 interfaces to the new subnet
va742> network ip addr modify 192.168.10.140 192.168.30.140 255.255.255.0
va742> network ip addr modify 192.168.10.141 192.168.30.141 255.255.255.0
va742> network ip addr modify 192.168.10.142 192.168.30.142 255.255.255.0
va742> network ip addr modify 192.168.10.143 192.168.30.143 255.255.255.0
va742> network ip addr show
IP Netmask/Prefix Device Node Type Status
-- -------------- ------ ---- ---- ------
192.168.10.121 255.255.255.0 eth1 va742-02 Physical
192.168.10.120 255.255.255.0 eth1 va742-01 Physical
192.168.30.125 255.255.255.0 eth4 va742-01 Physical
192.168.30.126 255.255.255.0 eth5 va742-01 Physical
192.168.30.127 255.255.255.0 eth4 va742-02 Physical
192.168.30.128 255.255.255.0 eth5 va742-02 Physical
192.168.10.130 255.255.255.0 eth1 va742-02 Virtual ONLINE (Con IP)
192.168.30.140 255.255.255.0 eth4 va742-01 Virtual ONLINE
192.168.30.141 255.255.255.0 eth4 va742-01 Virtual ONLINE
192.168.30.142 255.255.255.0 eth5 va742-01 Virtual ONLINE
192.168.30.143 255.255.255.0 eth5 va742-01 Virtual ONLINE
Check routing table. Note the output is snipped to only show the relevant routing tables
va742> network ip route show
IPv4 routing table: 5
=====================
Destination Gateway Genmask Flags MSS Window irtt Iface
============ ======= ============= ===== === ====== ==== =====
192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5
IPv4 routing table: 4
=====================
Destination Gateway Genmask Flags MSS Window irtt Iface
============ ======= ============= ===== === ====== ==== =====
192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4
Add the required default route for the new subnet
va742> network ip route add all 0.0.0.0 0.0.0.0 via 192.168.30.1 dev any scope=local
va742> network ip route show
IPv4 routing table: 5
=====================
Destination Gateway Genmask Flags MSS Window irtt Iface
============ ============ ============= ===== === ====== ==== =====
0.0.0.0 192.168.30.1 0.0.0.0 UG 0 0 0 eth5
192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5
IPv4 routing table: 4
=====================
Destination Gateway Genmask Flags MSS Window irtt Iface
============ ============ ============= ===== === ====== ==== =====
0.0.0.0 192.168.30.1 0.0.0.0 UG 0 0 0 eth4
192.168.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4
Scenario 4. Configuring multiple subnets for public interfaces.
This functionality was added with patch 7.4.2.200. See the patch release notes for more detailed examples.
Patch 7.4.2.200 readme
The initial network configuration:
eth4 and eth5 are on the same data subnet 192.168.30.0/24 default gateway 192.168.30.1
eth1 is on a separate management subnet 192.168.10.0/24 default gateway 192.168.10.1
Access console VIP uses eth1 interface and is on the management subnet.
It is required to split the data subnet into two. The original subnet will be used on the eth4 interface whilst a new subnet will use eth5 interface. The new subnet will be 192.168.20.0/24 default gateway 192.168.20.1
Initial Configuration:
va742> network ip addr show
IP Netmask/Prefix Device Node Type Status
-- -------------- ------ ---- ---- ------
192.168.10.121 255.255.255.0 eth1 va742-02 Physical
192.168.10.120 255.255.255.0 eth1 va742-01 Physical
192.168.30.125 255.255.255.0 eth4 va742-01 Physical
192.168.30.126 255.255.255.0 eth5 va742-01 Physical
192.168.30.127 255.255.255.0 eth4 va742-02 Physical
192.168.30.128 255.255.255.0 eth5 va742-02 Physical
192.168.10.130 255.255.255.0 eth1 va742-02 Virtual ONLINE (Con IP)
192.168.30.140 255.255.255.0 eth4 va742-01 Virtual ONLINE
192.168.30.141 255.255.255.0 eth4 va742-01 Virtual ONLINE
192.168.30.142 255.255.255.0 eth5 va742-01 Virtual ONLINE
192.168.30.143 255.255.255.0 eth5 va742-01 Virtual ONLINE
Move the required physical IP's to the new subnet
va742> network ip addr modify 192.168.30.126 192.168.20.126 255.255.255.0
va742> network ip addr modify 192.168.30.128 192.168.20.128 255.255.255.0
Move the required virtual IP's to the new subnet
va742> network ip addr modify 192.168.30.142 192.168.20.142 255.255.255.0
va742> network ip addr modify 192.168.30.143 192.168.20.143 255.255.255.0
Check routing table. Note the output is snipped to only show the relevant routing tables
va742> network ip route show
IPv4 routing table: 1
=====================
Destination Gateway Genmask Flags MSS Window irtt Iface
============ ======= ============= ===== === ====== ==== =====
192.168.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5
Add the required default route for the new subnet
va742> network ip route add all 0.0.0.0 0.0.0.0 via 192.168.20.1 dev eth5 scope=local
va742> network ip route show
IPv4 routing table: 1
=====================
Destination Gateway Genmask Flags MSS Window irtt Iface
============ ============ ============= ===== === ====== ==== =====
0.0.0.0 192.168.20.1 0.0.0.0 UG 0 0 0 eth5
192.168.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth5
War dieser Inhalt hilfreich?
Übersetzter Inhalt
Bitte beachten Sie, dass dieses Dokument aus dem Englischen übersetzt wurde und es sich möglicherweise um eine Maschinenübersetzung handelt. Es ist möglich, dass nach Übersetzung und Veröffentlichung dieses Dokuments Aktualisierungen der ursprünglichen Version vorgenommen wurden. Veritas übernimmt keine Garantie für die Genauigkeit hinsichtlich der Vollständigkeit der Übersetzung. Sie können auch die englische Version dieses Supportdatenbank-Artikels heranziehen, um aktuelle Informationen zu erhalten.