heartbeat failure max-failures
max-failures (2-10) is the number of consecutive dropped heartbeats to tolerate before declaring a failure.
bstnA(cfg-if-vlan-ron-tnl[25~toPortland])# heartbeat failure 6
heartbeat interval seconds
seconds (1-30) is the number of seconds between heartbeats.
bstnA(cfg-if-vlan-ron-tnl[25~toPortland])# heartbeat interval 15
Use the no form of the command to remove a legacy RON interface. See the Guidelines, below.
interface ron if-name
no interface ron if-name
if-name (1-32 characters) identifies the legacy RON interface.
This command is deprecated, and exists only to edit the configuration of legacy RON interfaces and tunnels. Use ron tunnel to create a new RON tunnel, which terminates at an in-band (VLAN) management IP instead of an additional RON IP address. If possible, use ron tunnel to duplicate all legacy RON tunnels, go to the remote switch(es) and run the peer address command with the new RON-tunnel address, then use no interface ron to remove the legacy tunnels.
This command places you in cfg-ron mode. From there, use the ip address (cfg-ron) command to edit the local IP address, and the peer address command to change the peers address. You can optionally tune the tunnels health-check parameters by setting the heartbeat interval and the threshold for consecutive heartbeat failure events before declaring the link OFFLINE. Use shutdown to disable the interface.
To view the current state and configuration of all tunnels, use show ron. For a full view of Link-State Advertisements from all switches connected via RON, use show ron database.
If the tunnel is connected and you use no interface ron, the CLI prompts you before disconnecting it. Enter yes to continue.
bstnA(cfg)# interface ron haPeer
bstnA(cfg)# no interface ron toPhilidelphia
ip address address mask [vlan vlan-id]
address is the IP address you choose for the RON interface (for example, 10.1.99.78).
mask defines the network part of the address (for example, 255.255.255.0).
vlan vlan-id (optional; 1-4096) specifies a VLAN to carry the tunnel.
Note: This command is unique to a legacy RON interface, which is deprecated in favor of the new ron tunnel. Whenever possible, duplicate all legacy RON interfaces as RON tunnels, go to the remote switch(es) and run the peer address command with the new RON-tunnel address, then return to the local switch to delete the RON interfaces. (RON tunnels re-use an in-band-management IP, whereas RON interfaces require an additional IP address.)
This address must also be configured at the other end of the RON tunnel as the peer address; the tunnel is not functional until the configurations match at both switches.
bstnA(cfg-ron[toProv])# ip address 192.168.25.50 255.255.255.0
prtlndB(cfg-ron[test])# ip address 192.168.74.73 255.255.255.0 vlan 96
Two switches in a RON are said to have a conflict if their private IP subnets are the same. Use this command to reassign a private subnet to the current switch and reboot it.
Use the show ron or show ron conflicts command to confirm that this switch has a private subnet that conflicts with another.
bstnA(cfg)# ip private subnet reassign
peer address remote-address
remote-address is the remote IP address (for example, 10.1.33.8) for the in-band (VLAN) interface at the other end of the tunnel.
Each end of the RON tunnel terminates at an in-band (VLAN) management interface, created with the interface vlan command. This command identifies the management interfaces ip address (cfg-if-vlan) at the other end of the tunnel. At the other end of the tunnel, the peer address points back to the local in-band-management IP.
prtlndA(cfg-if-vlan-ron-tnl[74~toBoston])# peer address 192.168.25.5
Use the rconsole command to start a new CLI session on an ARX at the other end of a RON tunnel.
rconsole hostname [username]
hostname (1-128 characters) is the remote switch name.
username - the administrative account you used to log into the local CLI.
The rconsole command starts a new CLI session on a remote ARX. This occurs through a Secure Shell (SSH). The other switch must be reachable using a RON tunnel, and the name of the switch must be known to RON. To see the current switch names available through RON, use the show ron command. Those switches showing the connection status ONLINE are available through the rconsole command.
The remote CLI prompts you for a password. This is the password for the username account on the remote switch; administrative accounts are configured independently at every switch in the RON (see user). Passwords are not guaranteed to be consistent throughout a RON.
bstnA# rconsole prtlndA admin
ron evict host-name
host-name (1-128 characters) is the name of the switch to remove from the RON.
If the switch is to be replaced, we recommend that you avoid this command. The show ron command shows the UUID for the former RON member, and this number is very important for a smooth switch replacement.
The switch must be offline to be evicted. This means that there can be no working RON tunnels to the switch. The show ron command shows whether or not the switch is offline.
bstnA# ron evict pawtucket
Use this command to create one end of a resilient overlay network (RON) tunnel. RON tunnels are used for communication between two or more ARXes.
Use the no form of the command to remove a RON-tunnel interface (see Guidelines below).
ron tunnel name
no ron tunnel name
name (1-32 characters) is a name you choose for the RON tunnel.
Use this command to begin the configuration at one end of a RON tunnel. A RON tunnel terminates at an in-band (VLAN) management interface; use interface vlan to create such an interface. The in-band-management IP is the IP address of the RON tunnels local end.
This command places you in cfg-if-vlan-ron-tnl mode. From there, use the peer address command to identify the peers address (that is, the IP address of the peers in-band management interface). You can optionally tune the tunnels health-check parameters by setting the heartbeat interval and the threshold for consecutive heartbeat failure events before declaring the tunnel OFFLINE. Then use no shutdown (cfg-if-vlan-ron-tnl) to enable the tunnel interface. To start traffic on the tunnel, repeat this process (reversing the IP addresses) at the other end.
After you connect two switches with a RON tunnel, you can access the peer switchs CLI through the rconsole command.
The show ron command shows a high-level status for the entire RON. To view the current state and configuration of a tunnel, use show ron tunnel. For a full view of Link-State Advertisements from all switches connected via RON, use show ron database. Use show ron conflicts to see which switches (if any) have a private-subnet conflict; to resolve a conflict, use ip private subnet reassign.
bstnA(cfg)# interface vlan 89
bstnA(cfg-if-vlan)# ron tunnel toEllesworth
bstnA(cfg-if-vlan)# no ron tunnel toPhilidelphia
show ron [member]
member (optional, 1-128 characters) specifies the hostname for one member of the RON. If you omit this, the command shows all RON members.
This command displays a two-line entry for each member of the RON. The first line identifies the switch and its high-level status.
Switch Name identifies the member switch.
HA Peer Switch for the switch, if there is one. This is the switchs redundant peer.
Uptime is the time since the switchs last reboot.
Status is ONLINE, OFFLINE, SUBNET CONFLICT, or unknown. The SUBNET CONFLICT status indicates that the private subnet is the same as some other switch in the RON; use show ron conflicts to find which switches conflict with which.
UUID is the Universally-Unique ID for the switch. All of the shares owned by this switch are marked with this UUID. In a redundant pair, a share is owned by a switch when its volumes volume-group is set at the switch. You set a switchs UUID during installation.
Management Addr is the Out-of-band MGMT interface, if configured. Otherwise, it is the address of the in-band (VLAN) management interface of the lowest-numbered VLAN.
If you choose one member, the output focuses on that host only. The fields are the same, presented in a different format.
prtlndA# show ron
prtlndA# show ron prtlndB
Two switches in a RON are said to have a conflict if their private IP subnets are the same. The show ron conflicts command shows all conflicting switches in the current RON.
This shows a table of RON conflicts, one row per conflicting switch. The Accessible Switch is available from the local switch, and the Conflicting Switch is not; some other switch in the RON might show the same conflict with the switch roles reversed. Each of these switches can only communicate with a limited number of peers in the RON, if any. To correct the problem and bring conflicting switches fully into the RON, go to one conflicting switch and use ip private subnet reassign.
prtlndA> show ron conflicts
You can connect one ARX to another with a RON tunnel: use this command to show routing information and statistics for each ARX connected to the current switch. The output displays one table per host switch. Each table contains the following information:
Status is Current, Stale, or ERROR. This represents the status of the peers Link-State Advertisement (LSA). Peers exchange periodic LSAs with information about the tunnel state(s); this table expresses the latest LSA received from the Hostname.
ERROR indicates that this peer has the same private subnet as another peer in the RON. This is an unsupportable configuration. An ERROR message at the bottom of the output shows which peers have the conflict. Go to either switchs CLI and use ip private subnet reassign to change its subnet.
Serial # is the serial number for the peers latest LSA. This number increments whenever the switch receives a new LSA from this peer.
Age is the number of seconds since the last LSA was received from the remote peer.
Private Subnet(s) is the hosts private subnet. If the host is part of a redundant pair, this also shows the private subnet for the hosts peer.
A sub table shows all tunnels configured for the host. Each tunnel appears in one row with the following information:
Peer is the host switch at the other end of the tunnel. You can change this with the cfg-if-vlan-ron-tnl peer address command.
State is Down, Connecting, Connected, Shutdown, or Unknown. A new tunnel transitions from Shutdown to Connecting to Connected. Down indicates link failure: too many consecutive heartbeats were dropped (see heartbeat failure and heartbeat interval). Shutdown indicates that the tunnel was disabled with the shutdown (cfg-if-vlan-ron-tnl) command.
RTT(ms) is the average Round-Trip Time (RTT) through the tunnel, in milliseconds.
Loss(%) is the percentage of packets lost in the tunnel.
TCP (Kb/s) is the estimated TCP throughput (in Kilobits per second) on the tunnel.
Loss*RTT is reserved for future use.
prtlndA# show ron database
Destination is the host name of the peer switch at the other end of the tunnel.
Subnet is the private-IP subnet of the peer switch.
Via Tunnel is tunnel for sending packets to the Subnet.
Milliseconds is average round-trip time, through the tunnel and back.
prtlndA> show ron route
show ron tunnel [name | redundancy | all]
name (optional, 1-32 characters) identifies a particular RON tunnel to display. If you omit this, the command shows a summary of all RON tunnels.
redundancy (optional) is the name of an automatically-generated tunnel. This only appears on an ARX-1500 or ARX-2500 with a redundant peer. This tunnel carries redundancy-related traffic over the redundancy link that connects the redundant pair. The ARX creates this tunnel when you enter the redundancy command to join a redundant pair.
all shows details for all RON tunnels on the ARX.
A Resilient Overlay Network (RON) connects multiple ARX devices. One RON tunnel connects two of them; use the ron tunnel command to create a RON tunnel. This command shows the configuration and state of RON tunnels.
The show ron tunnel command (without a specific tunnel or the all keyword) shows a table of all RON tunnels. Each row summarizes the tunnel configuration and state:
State is Shutdown, Connecting, Connected, Unreachable, No Response, Mismatch, Error, or Unknown. A new tunnel transitions from Shutdown to Connecting to Connected. The error states are listed here.
Interface shows the in-band management interface that serves as the local end of the tunnel (created with interface vlan).
Remote Addr is the IP address of the peers end of the tunnel. Use the peer address command to change this. (The local address is the address of the tunnels in-band management interface, set with ip address (cfg-if-vlan).)
Up Time is the amount of time that the RON tunnel has been Connected.
Include the interface name (or all) to display details for the tunnel(s):
Name is the tunnel name.
Peer is the host name of the remote peer.
Tunnel State is the same as State in the summary version.
Uptime shows how long the tunnels state has been Connected.
Interface shows the in-band management interface that serves as the local end of the tunnel (created with interface vlan).
Remote Address is the IP addresses at the other end of the tunnel. Use peer address to change the remote address.
Security Policy is reserved for future use.
Ping Fail Limit is the number of consecutive heartbeat failures to tolerate before declaring the Tunnel State No response. Use heartbeat failure to change this threshold.
Round Trip Time is the average number of milliseconds for a packet to go through the tunnel and back.
Packet Lost Rate is the percentage of packets lost in the tunnel.
TCP Throughput is the tunnels estimated throughput in bytes per second.
Loss RTT Product is reserved for future use.
RON Packets In and RON Packets Out counts the packets that are directly-related to RON, such as heartbeats and Link-State Advertisements (LSAs).
Data Packets In and Data Packets Out counts all other packets, including shadow-copy data.
Data Bytes In and Data Bytes Out is the total bytes (of Data Packets) exchanged.
Last Error Code is 0 (zero), an error number, Network Unreachable, or Host Unreachable. If an error number appears here, contact F5 for interpretation.
Control Errors is the number of errors from RON control packets, such as RON heartbeats and LSAs.
Data Errors is the number of failed data packets. These are packets unrelated to RON control, such as replicated files.
prtlndA> show ron tunnel
displays a summary of all configured RON tunnels. See Figure 14.5 for sample output.
prtlndA> show ron tunnel toBoston
prtlndA> show ron tunnel all
stoweA> show ron tunnel redundancy
Use the no form of the command to open the local end of the RON tunnel.
bstnA(cfg-if-vlan-ron-tnl[toLA])# no shutdown