Aruba JG408A Installation guide

Category
Networking
Type
Installation guide
HPE FlexNetwork MSR3000 Routers
Comware 7 High Availability Configuration Guide
Software
version: CMW710-R6728
Document version: 6W100-20220322
© Copyright 2022 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
i
Contents
Configuring interface backup ········································································· 1
About interface backup ······································································································································ 1
Compatible interfaces ································································································································ 1
Backup modes ··········································································································································· 1
Restrictions and guidelines: Interface backup configuration ·············································································· 3
Interface backup tasks at a glance····················································································································· 3
Prerequisites for configuring interface backup ··································································································· 3
Explicitly specifying backup interfaces without traffic thresholds ······································································· 4
Using interface backup with the Track module ·································································································· 4
Configuring load-shared interface backup ········································································································· 5
Display and maintenance commands for interface backup ··············································································· 6
Interface backup configuration examples ·········································································································· 6
Example: Configuring strict active/standby interface backup ····································································· 6
Example: Configuring strict active/standby interface backup with the Track module ································· 8
Example: Configuring load-shared interface backup ················································································· 9
Configuring CFD ·························································································· 12
About CFD ······················································································································································· 12
Basic CFD concepts ································································································································· 12
CFD levels ················································································································································ 12
Packet processing of MEPs ····················································································································· 14
CFD functions ·········································································································································· 14
Port collaboration ····································································································································· 16
Collaboration between CFD and Track ···································································································· 17
Protocols and standards ·························································································································· 17
Restrictions and guidelines: CFD configuration ······························································································· 17
CFD tasks at a glance ······································································································································ 18
Prerequisites for CFD······································································································································· 18
Configuring basic CFD settings ······················································································································· 18
Enabling CFD ··········································································································································· 18
Configuring service instances ·················································································································· 19
Configuring MEPs ···································································································································· 19
Configuring CFD functions ······························································································································· 20
Configuring CC ········································································································································· 20
Configuring LB ········································································································································· 21
Configuring LT ·········································································································································· 21
Configuring AIS ········································································································································ 22
Configuring LM ········································································································································· 22
Configuring one-way DM ·························································································································· 23
Configuring two-way DM ·························································································································· 23
Configuring TST ······································································································································· 23
Configuring threshold alarm ····················································································································· 24
Configuring port collaboration ·························································································································· 24
Display and maintenance commands for CFD ································································································ 26
CFD configuration examples ···························································································································· 27
Configuring DLDP ························································································ 34
About DLDP ····················································································································································· 34
Application scenario ································································································································· 34
Basic concepts ········································································································································· 35
How DLDP works ····································································································································· 36
Restrictions and guidelines: DLDP configuration ····························································································· 38
DLDP tasks at a glance···································································································································· 39
Enabling DLDP················································································································································· 39
Setting the interval to send advertisement packets ························································································· 39
Setting the DelayDown timer···························································································································· 39
Setting the global port shutdown mode ············································································································ 40
ii
Configuring DLDP authentication ····················································································································· 40
Display and maintenance commands for DLDP ······························································································ 41
DLDP configuration examples ························································································································· 41
Example: Configuring the auto port shutdown mode ··············································································· 41
Example: Configuring the manual port shutdown mode ·········································································· 44
Configuring VRRP ······················································································· 49
About VRRP ····················································································································································· 49
VRRP standard mode ······································································································································ 50
VRRP networking ····································································································································· 50
Virtual IP address and IP address owner ································································································· 50
Router priority in a VRRP group ··············································································································· 50
Preemption ··············································································································································· 50
Authentication method ····························································································································· 51
VRRP timers ············································································································································ 51
Master election ········································································································································· 52
VRRP tracking ·········································································································································· 52
VRRP application ····································································································································· 52
VRRP load balancing mode ····························································································································· 54
Virtual MAC address assignment ············································································································· 54
Virtual forwarder ······································································································································· 56
Protocols and standards ·································································································································· 58
Configuring IPv4 VRRP···································································································································· 58
Restrictions and guidelines: IPv4 VRRP configuration ············································································ 58
IPv4 VRRP tasks at a glance ··················································································································· 58
Specifying an IPv4 VRRP operating mode ······························································································ 58
Specifying the IPv4 VRRP version ··········································································································· 59
Configuring an IPv4 VRRP group ············································································································ 59
Specifying an IPv4 VRRP control VLAN ·································································································· 61
Configuring IPv4 VRRP packet attributes ································································································ 62
Configuring VF tracking ···························································································································· 63
Enabling SNMP notifications for VRRP ···································································································· 64
Display and maintenance commands for IPv4 VRRP ·············································································· 64
Configuring IPv6 VRRP···································································································································· 64
Restrictions and guidelines: IPv6 VRRP configuration ············································································ 64
IPv6 VRRP tasks at a glance ··················································································································· 64
Specifying an IPv6 VRRP operating mode ······························································································ 65
Configuring an IPv6 VRRP group ············································································································ 65
Specifying an IPv6 VRRP control VLAN ·································································································· 67
Configuring VF tracking ···························································································································· 68
Configuring IPv6 VRRP packet attributes ································································································ 69
Display and maintenance commands for IPv6 VRRP ·············································································· 70
IPv4 VRRP configuration examples ················································································································· 70
Example: Configuring a single VRRP group ···························································································· 70
Example: Configuring multiple VRRP groups ·························································································· 73
Example: Configuring VRRP load balancing···························································································· 75
IPv6 VRRP configuration examples ················································································································· 83
Example: Configuring a single VRRP group ···························································································· 83
Example: Configuring multiple VRRP groups ·························································································· 86
Example: Configuring VRRP load balancing···························································································· 88
Troubleshooting VRRP ···································································································································· 97
An error prompt is displayed ···················································································································· 97
Multiple masters appear in a VRRP group ······························································································· 97
Fast VRRP state flapping ························································································································· 98
Configuring the Layer 3 connection keepalive feature ································· 99
About Layer 3 connection keepalive ················································································································ 99
Restrictions and guidelines: Layer 3 connection keepalive configuration ························································ 99
Layer 3 connection keepalive tasks at a glance ······························································································ 99
Configuring the Layer 3 connection keepalive feature ··················································································· 100
Display and maintenance commands for Layer 3 connection keepalive ······················································· 100
Layer 3 connection keepalive configuration examples ·················································································· 100
iii
Example: Configuring the Layer 3 connection keepalive feature ··························································· 100
Configuring error code detection ································································ 102
About error code detection ····························································································································· 102
Error code detection fundamentals ················································································································ 102
Interface error code detection ················································································································ 102
Link quality detection ······························································································································ 102
Error code detection deployment ··················································································································· 103
Restrictions and guidelines: Error code detection configuration ···································································· 103
Configuring interface error code detection ····································································································· 104
Configuring link quality detection ··················································································································· 104
Configuring the bit error ratio calculation factors for an interface ·································································· 105
Display and maintenance commands for error code detection ······································································ 105
Configuring the HA group ·········································································· 107
About the HA group········································································································································ 107
Application scenario ······························································································································· 107
Basic HA group concepts ······················································································································· 108
Operating modes of the HA group ········································································································· 108
HA data synchronization ························································································································ 110
HA group member switchover mechanisms ··························································································· 112
Associating the HA group with VRRP ···································································································· 112
Associating the HA group with routing protocols ···················································································· 114
Transparent in-path deployment of the HA group ·················································································· 115
Restrictions: Hardware compatibility with the HA group ················································································ 116
Restrictions and guidelines: HA group configuration ····················································································· 117
Member device restrictions and guidelines ···························································································· 117
Interface restrictions and guidelines······································································································· 117
HA channel restrictions and guidelines ·································································································· 117
HA group deployment restrictions and guidelines ·················································································· 117
Feature compatibility restrictions············································································································ 118
Hardware environment consistency ······································································································· 118
Software environment consistency ········································································································ 119
Network interconnection restrictions ······································································································ 119
HA group configuration flow ··························································································································· 119
HA group tasks at a glance ···························································································································· 120
Configuring the HA role ·································································································································· 121
Configuring the HA control channel ··············································································································· 121
Configuring the HA data channel ··················································································································· 122
Enabling service entry hot backup ················································································································· 122
Configuring HA configuration synchronization ······························································································· 123
Enabling traffic switchover upon failure recovery ··························································································· 124
Configuring the active/standby mode ············································································································· 124
Configuring the dual-active mode ·················································································································· 124
Associating the HA group with VRRP ············································································································ 125
Associating the HA group with routing protocols···························································································· 125
Configuring HA group transparent in-path deployment ·················································································· 126
Enabling the HA group to monitor interfaces ························································································· 126
Enabling the HA group to monitor VLANs ······························································································ 126
Associating the HA group with Track ············································································································· 127
Performing an active/standby switchover ······································································································ 127
Configuring service features on the HA group ······························································································· 128
NAT on the HA group ····························································································································· 128
HA group support for SSL VPN ·············································································································· 130
HA group support for DPI services ········································································································· 131
HA group deployment schemes ····················································································································· 131
Routed in-path deployment in active/standby mode ·············································································· 131
Routed in-path deployment in dual-active mode ···················································································· 133
Transparent in-path deployment in active/standby mode ······································································ 134
Transparent in-path deployment in dual-active mode ············································································ 135
Display and maintenance commands for the HA group ················································································· 136
HA group configuration examples (IPv4) ······································································································· 137
iv
Example: Configuring the HA group in active/standby mode in collaboration with VRRP ····················· 137
Example: Configuring the HA group in dual-active mode in collaboration with VRRP ··························· 142
Example: Configuring the HA group in active/standby mode in collaboration with a routing protocol ··· 146
Example: Configuring the HA group in dual-active mode in collaboration with a routing protocol ········· 150
Example: Configuring a transparent in-path HA group in active/standby mode····································· 154
Example: Configuring a transparent in-path HA group in dual-active mode ·········································· 158
Example: Configuring NAT on the HA group in active/standby mode in collaboration with VRRP ········ 161
Example: Configuring NAT on the HA group in dual-active mode in collaboration with VRRP ·············· 163
HA group configuration examples (IPv6) ······································································································· 166
Example: Configuring the HA group in active/standby mode in collaboration with VRRP ····················· 166
Example: Configuring the HA group in dual-active mode in collaboration with a routing protocol ········· 171
Configuring BFD ························································································ 177
About BFD······················································································································································ 177
Single-hop detection and multihop detection ························································································· 177
BFD session modes ······························································································································· 177
Supported features ································································································································· 178
Protocols and standards ························································································································ 178
Restrictions and guidelines: BFD configuration ····························································································· 179
Configuring BFD sessions in echo packet mode ··························································································· 179
About this task ········································································································································ 179
Restrictions and guidelines ···················································································································· 179
Creating a static BFD session ················································································································ 179
Configuring BFD session parameters for single-hop detection ······························································ 181
Configuring BFD session parameters for multihop detection ································································· 181
Configuring BFD sessions in control packet mode ························································································ 181
About BFD session creation methods ···································································································· 181
Restrictions and guidelines ···················································································································· 182
Configuring a static BFD session ··········································································································· 182
Configuring BFD session parameters for single-hop detection ······························································ 184
Configuring BFD session parameters for multihop detection ································································· 184
Enabling the echo function ····························································································································· 185
Associating the interface state with BFD········································································································ 186
Configuring a BFD template ··························································································································· 187
Enabling SNMP notifications for BFD ············································································································ 187
Display and maintenance commands for BFD ······························································································· 188
Configuring SBFD ······················································································ 189
About SBFD ··················································································································································· 189
Restrictions and guidelines: SBFD configuration ··························································································· 189
SBFD tasks at a glance·································································································································· 189
Configuring the initiator ·································································································································· 189
Restrictions and guidelines ···················································································································· 189
Configuring the initiator for SRv6 TE policy detection ············································································ 190
Configuring the reflector ································································································································· 191
Configuring a BFD template ··························································································································· 191
Display and maintenance commands for SBFD ···························································································· 192
Configuring process placement ································································· 193
About process placement······························································································································· 193
Process ·················································································································································· 193
Node ······················································································································································· 193
Process redundancy ······························································································································ 193
Process placement ································································································································· 193
Default process placement policy ·········································································································· 193
Process placement affinities ·················································································································· 194
Process placement optimization ············································································································ 194
Restrictions: Hardware compatibility with process placement ······································································· 194
Restrictions and guidelines: process placement configuration ······································································ 195
Process placement tasks at a glance············································································································· 195
Configuring process placement policy ··········································································································· 195
Configuring a location affinity ················································································································· 195
v
Configuring a location type affinity ········································································································· 196
Configuring a process affinity ················································································································· 196
Configuring a self affinity ························································································································ 196
Optimizing process placement ······················································································································· 197
Display and maintenance commands for process placement ········································································ 197
Configuring Track ······················································································ 199
About Track ···················································································································································· 199
Collaboration mechanism ······················································································································· 199
Supported detection modules ················································································································ 200
Supported application modules ·············································································································· 200
Restrictions and guidelines: Track configuration···························································································· 200
Collaboration application example ················································································································· 201
Track tasks at a glance ·································································································································· 201
Associating Track with a detection module object ························································································· 202
Associating Track with NQA ··················································································································· 202
Associating Track with BFD ··················································································································· 202
Associating Track with CFD ··················································································································· 203
Associating Track with interface management······················································································· 203
Associating Track with route management ···························································································· 204
Associating Track with a tracked list ·············································································································· 205
Associating Track with a Boolean list ····································································································· 205
Associating Track with a percentage threshold list ················································································ 205
Associating Track with a weight threshold list ························································································ 206
Associating the Track module with an application module············································································· 207
Prerequisites for associating the Track module with an application module ····································· 207
Associating Track with VRRP ················································································································ 207
Associating Track with static routing ······································································································ 208
Associating Track with PBR ··················································································································· 210
Associating Track with interface backup ································································································ 212
Associating Track with VPLS ················································································································· 212
Associating Track with VXLAN ··············································································································· 213
Associating Track with MPLS L2VPN ···································································································· 213
Associating Track with EAA ··················································································································· 214
Display and maintenance commands for Track ····························································································· 215
Track configuration examples ························································································································ 215
Example: Configuring VRRP-Track-NQA collaboration ········································································· 215
Example: Configuring BFD for a VRRP backup to monitor the master ·················································· 219
Example: Configuring BFD for the VRRP master to monitor the uplink ················································· 222
Example: Configuring static routing-Track-NQA collaboration ······························································· 225
Example: Configuring static routing-Track-BFD collaboration ······························································· 230
Example: Configuring VRRP-Track-interface management collaboration ············································· 233
Example: Configuring VRRP-Track-route management collaboration ··················································· 236
Document conventions and icons ······························································ 239
Conventions ··················································································································································· 239
Network topology icons ·································································································································· 240
Support and other resources ····································································· 241
Accessing Hewlett Packard Enterprise Support····························································································· 241
Accessing updates ········································································································································· 241
Websites ················································································································································ 242
Customer self repair ······························································································································· 242
Remote support ······································································································································ 242
Documentation feedback ······················································································································· 242
Index ·········································································································· 244
1
Configuring interface backup
About interface backup
Interface backup enables you to configure multiple backup interfaces for a Layer 3 interface to
increase link availability. When the primary interface fails or is overloaded, its backup interfaces can
take over or participate in traffic forwarding.
Compatible interfaces
Table 1 Interfaces that support interface backup
Category
Interfaces
Remarks
Ethernet Layer 3 Ethernet interfaces/subinterfaces
Layer 3 VE interfaces
WLAN-ETHERNET interfaces N/A
WAN
IMA-group interfaces
POS interfaces
Serial interfaces (asynchronous,
synchronous)
Eth-channel interfaces
The IMA-group interfaces can only
work as backup interfaces. All the
other interfaces can work as both
primary and backup interfaces.
An asynchronous serial interface
cannot work as the primary interface if
DDR is configured on it.
Others Dialer interfaces
MP-group interfaces
Tunnel interfaces
A dialer interface can be used as the
primary interface only when it is a
PPPoE client in permanent session
mode.
Backup modes
The primary interface and its backup interfaces can operate in strict active/standby mode or load
sharing mode.
•
Strict active/standby mode—Only one interface transmits traffic. All the other interfaces are in
STANDBY state.
•
Load sharing mode—Backup interfaces participate in traffic forwarding when the amount of
traffic on the primary interface reaches the upper threshold. They are activated and deactivated
depending on the amount of traffic.
In strict active/standby mode, traffic loss occurs when the active interface is overloaded. Load
sharing mode improves link efficiency and reduces the risk of packet loss.
Strict active/standby mode
In strict active/standby mode, the primary interface always has higher priority than all backup
interfaces.
•
When the primary interface is operating correctly, all traffic is transmitted through the primary
interface.
•
When the primary interface fails, the highest-priority backup interface takes over. If the
highest-priority backup interface also fails, the second highest-priority backup interface takes
over, and so forth.
2
NOTE:
If two backup interfaces have the same priority, the one configured first has preference.
An active backup interface is always preempted by the primary interface. However, a higher-priority
backup interface cannot preempt a lower-priority backup interface that has taken over the primary
interface.
•
The primary interface takes over when it recovers from a failure condition.
•
The higher-priority backup interface cannot take over when it recovers from a failure condition
while the primary interface is still down.
As shown in Figure 1, Port A on Router A is the primary interface. Port B (with a priority of 30) and
Port C (with a priority of 20) are its backup interfaces.
•
When Port A is operating correctly, all traffic is transmitted through Port A.
•
When Port A fails, Port B takes over because it has higher priority than Port C. If Port B also fails,
Port C takes over.
•
When Port A is recovered, it preempts the active backup interface because it is the primary
interface. If Port B is recovered while Port A is still down, Port B cannot preempt Port C to
forward traffic.
Figure 1 Strict active/backup mode
Load sharing mode
In load sharing mode, the backup interfaces are activated to transmit traffic depending on the traffic
load on the primary interface.
•
When the amount of traffic on the primary interface exceeds the upper threshold, the backup
interfaces are activated in descending order of priority. This action continues until the traffic
drops below the upper threshold.
•
When the total amount of traffic on all load-shared interfaces decreases below the lower
threshold, the backup interfaces are deactivated in ascending order of priority. This action
continues until the total amount of traffic exceeds the lower threshold.
•
When the primary interface fails (in DOWN state), the strict active/standby mode applies. Only
one backup interface can forward traffic.
The upper and lower thresholds are user configurable.
NOTE:
•
"Traffic" on an interface refers to the amount of incoming or outgoing traffic, whichever is higher.
• If two backup interfaces have the same priority, the one configured first has preference.
As shown in Figure 2, Port A on Router A is the primary interface. Port B (with a priority of 30) and
Port C (with a priority of 20) are its backup interfaces.
Port B
Port A
Port C
Router A
Router B
LAN
100%
3
•
When the amount of traffic on Port A exceeds the upper threshold, Port B is activated, because
it has higher priority than Port C. If the amount of traffic on Port A still exceeds the upper
threshold, Port C is activated.
•
When the total amount of traffic on all load-shared interfaces decreases below the lower
threshold, Port C is first deactivated, because its priority is lower than Port B. If the total amount
of traffic on Port A and Port B is still below the lower threshold, Port B is deactivated.
Figure 2 Load sharing mode
Restrictions and guidelines: Interface backup
configuration
When you configure interface backup, follow these restrictions and guidelines:
•
The device supports up to 10 primary interfaces.
•
An interface can be configured as a backup only for one interface.
•
An interface cannot be both a primary and backup interface.
•
The strict active/standby mode and load sharing mode cannot be configured at the same time.
Interface backup tasks at a glance
To configure interface backup, perform the following tasks:
•
Configuring strict active/standby interface backup
Choose one of the following tasks:
ï‚¡ Explicitly specifying backup interfaces without traffic thresholds
Use this method if you want to monitor the interface state of the primary interface for a
switchover to occur.
ï‚¡ Using interface backup with the Track module
Use this method if you want to monitor any other state, such as the link state of the primary
interface.
•
Configuring load-shared interface backup
Prerequisites for configuring interface backup
Make sure the primary and backup interfaces have routes to the destination network.
Port B
Port A
Port C
Router A
Router B
LAN
A%
B%
C%
A
=
B
=
C
A
+
B
+
C = 100
4
Explicitly specifying backup interfaces without
traffic thresholds
About this task
Perform this task if you want to monitor the interface state of the primary interface for a switchover to
occur. For the primary and backup interfaces to operate in strict active/standby mode, do not specify
the traffic thresholds on the primary interface. If the traffic thresholds are configured, the interfaces
will operate in load sharing mode.
You can assign priority to backup interfaces. When the primary interface fails, the backup interfaces
are activated in descending order of priority, with the highest-priority interface activated first. If two
backup interfaces have the same priority, the one configured first has preference.
To prevent link flapping from causing frequent interface switchovers, you can configure the following
switchover delay timers:
•
Up delay timer—Number of seconds that the primary or backup interface must wait before it
can come up.
•
Down delay timer—Number of seconds that the active primary or backup interface must wait
before it is set to down state.
When the link of the active interface fails, the interface state does not change immediately. Instead, a
down delay timer starts. If the link recovers before the timer expires, the interface state does not
change. If the link is still down when the timer expires, the interface state changes to down.
Procedure
1. Enter system view.
system-view
2. Enter interface view.
interface interface-type interface-number
This interface must be the primary interface.
3. Specify a backup interface.
backup interface interface-type interface-number [ priority ]
By default, an interface does not have any backup interfaces.
Repeat this command to specify up to three backup interfaces for the interface.
4. Set the switchover delay timers.
backup timer delay up-delay down-delay
By default, the up and down delay timers are both 5 seconds.
Using interface backup with the Track module
About this task
Perform this task if you want to monitor any other state, such as the link state of the primary interface.
To use interface backup with the Track module to provide strict active/standby backup for a primary
interface:
•
Configure a track entry to monitor state information of the primary interface. For example,
monitor its link state.
•
Associate the track entry with a backup interface.
Interface backup changes the state of the backup interface in response to the track entry state, as
shown in Table 2.
5
Table 2 Action on the backup interface in response to the track entry state change
State of the monitored primary link
Action on the backup interface
Positive The primary link is operating correctly. Places the backup interface in
STANDBY state.
Negative The primary link has failed. Activates the backup interface to
take over.
NotReady
The primary link is not monitored.
This situation occurs when the track module
or the monitoring module is not ready, for
example, because the Track module is
restarting or the monitoring settings are
incomplete. In this situation, interface
backup cannot obtain information about the
primary link from the track module.
• If the track entry state stays in
NotReady state after it is
created, interface backup does
not change the state of the
backup interface.
• If the track entry state changes
to NotReady from Positive or
Negative, the backup interface
changes back to the forwarding
state before it was used for
interface backup.
For more information about configuring a track entry, see "Configuring Track."
Restrictions and guidelines
•
You can associate an interface with only one track entry.
•
You can create the associated track entry before or after the association. The association takes
effect after the track entry is created.
•
To maintain performance, limit the number of associations to 64.
Procedure
1. Enter system view.
system-view
2. Enter interface view.
interface interface-type interface-number
This interface must be the interface you are using as a backup.
3. Associate the interface with a track entry.
backup track track-entry-number
By default, an interface is not associated with a track entry.
Configuring load-shared interface backup
About this task
To implement load-balanced interface backup, you must configure the traffic thresholds on the
primary interface. Interface backup regularly compares the amount of traffic with the thresholds to
determine whether to activate or deactivate a backup interface. The traffic polling interval is user
configurable.
You can assign priority to backup interfaces.
•
When the amount of traffic on the primary interface exceeds the upper threshold, the backup
interfaces are activated in descending order of priority.
•
When the total amount of traffic on all load-shared interfaces decreases below the lower
threshold, the backup interfaces are deactivated in ascending order of priority.
If two backup interfaces have the same priority, the one configured first has preference.
6
If a traffic flow has a fast forwarding entry, all packets of the flow will be forwarded out of the outgoing
interface in the entry. The packets of the flow will not be distributed between interfaces when the
upper threshold is reached. For more information about fast forwarding, see Layer 3—IP Services
Configuration Guide.
Procedure
1. Enter system view.
system-view
2. Enter interface view.
interface interface-type interface-number
You must enter the view of the primary interface.
3. Configure a backup interface for the interface.
backup interface interface-type interface-number [ priority ]
By default, an interface does not have any backup interfaces.
Repeat this command to specify up to three backup interfaces.
4. Set backup load sharing thresholds.
backup threshold upper-threshold lower-threshold
By default, no traffic thresholds are configured.
5. Set the traffic polling interval.
backup timer flow-check interval
The default interval is 30 seconds.
Display and maintenance commands for interface
backup
Execute display commands in any view.
Task
Command
Display traffic statistics for load-shared interfaces.
display
interface-backup
statistics
Display the status of primary and backup interfaces.
display
interface-backup
state
Interface backup configuration examples
Example: Configuring strict active/standby interface backup
Network configuration
As shown in Figure 3:
•
Specify GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 on Router A to back up
GigabitEthernet 1/0/1.
•
Assign GigabitEthernet 1/0/2 a higher priority than GigabitEthernet 1/0/3.
•
Set the up and down delay timers to 10 seconds for the backup interfaces.
7
Figure 3 Network diagram
Procedure
1. Assign IP addresses to the interfaces, as shown in Figure 3. (Details not shown.)
2. Configure static routes:
# On Router A, configure static routes to 192.168.2.0/24 through the primary and backup
interfaces.
<RouterA> system-view
[RouterA] ip route-static 192.168.2.0 24 gigabitethernet 1/0/1 1.1.1.2
[RouterA] ip route-static 192.168.2.0 24 gigabitethernet 1/0/2 2.2.2.2
[RouterA] ip route-static 192.168.2.0 24 gigabitethernet 1/0/3 3.3.3.2
# On Router B, configure static routes to 192.168.1.0/24.
<RouterB> system-view
[RouterB] ip route-static 192.168.1.0 24 gigabitethernet 1/0/1 1.1.1.1
[RouterB] ip route-static 192.168.1.0 24 gigabitethernet 1/0/2 2.2.2.1
[RouterB] ip route-static 192.168.1.0 24 gigabitethernet 1/0/3 3.3.3.1
3. On Router A, configure backup interfaces and switchover delays:
# Specify GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 to back up GigabitEthernet 1/0/1,
and assign them a priority of 30 and 20, respectively.
[RouterA] interface gigabitethernet 1/0/1
[RouterA-GigabitEthernet1/0/1] backup interface gigabitethernet 1/0/2 30
[RouterA-GigabitEthernet1/0/1] backup interface gigabitethernet 1/0/3 20
# Set both up and down delay timers to 10 seconds.
[RouterA-GigabitEthernet1/0/1] backup timer delay 10 10
Verifying the configuration
# Display states of the primary and backup interfaces.
[RouterA-GigabitEthernet1/0/1] display interface-backup state
Interface: GE1/0/1
UpDelay: 10 s
DownDelay: 10 s
State: UP
Backup interfaces:
GE1/0/2 Priority: 30 State: STANDBY
GE1/0/3 Priority: 20 State: STANDBY
The output shows that GigabitEthernet 1/0/1 is in UP state and the two backup interfaces are in
STANDBY state.
GE1/0/2
2.2.2.1/24
GE1/0/1
1.1.1.1/24
GE1/0/3
3.3.3.1/24
GE1/0/1
1.1.1.2/24
GE1/0/2
2.2.2.2/24
GE1/0/3
3.3.3.2/24
Router A Router B
Host A Host B
192.168.1.2/24 192.168.2.2/24
GE1/0/4
192.168.1.1/24 GE1/0/4
192.168.2.1/24
8
# Shut down the primary interface GigabitEthernet 1/0/1.
[RouterA-GigabitEthernet1/0/1] shutdown
# Verify that the backup interface GigabitEthernet 1/0/2 comes up 10 seconds after the primary
interface goes down.
[RouterA-GigabitEthernet1/0/1] display interface-backup state
Interface: GE1/0/1
UpDelay: 10 s
DownDelay: 10 s
State: DOWN
Backup interfaces:
GE1/0/2 Priority: 30 State: UP
GE1/0/3 Priority: 20 State: STANDBY
Example: Configuring strict active/standby interface backup
with the Track module
Network configuration
As shown in Figure 4, configure a track entry to monitor the link state of GigabitEthernet 1/0/1. When
the link of GigabitEthernet 1/0/1 fails, the backup interface GigabitEthernet 1/0/2 comes up to take
over.
Figure 4 Network diagram
Procedure
1. Assign IP addresses to the interfaces, as shown in Figure 4. (Details not shown.)
2. Configure static routes:
# On Router A, configure static routes to 192.168.2.0/24 through the primary and backup
interfaces.
<RouterA> system-view
[RouterA] ip route-static 192.168.2.0 24 gigabitethernet 1/0/1 1.1.1.2
[RouterA] ip route-static 192.168.2.0 24 gigabitethernet 1/0/2 2.2.2.2
# On Router B, configure static routes to 192.168.1.0/24.
<RouterB> system-view
[RouterB] ip route-static 192.168.1.0 24 gigabitethernet 1/0/1 1.1.1.1
[RouterB] ip route-static 192.168.1.0 24 gigabitethernet 1/0/2 2.2.2.1
3. On Router A, configure Track settings:
GE1/0/2
2.2.2.1/24
GE1/0/1
1.1.1.1/24 GE1/0/1
1.1.1.2/24
GE1/0/2
2.2.2.2/24
Router A Router B
Host A Host B
192.168.1.2/24 192.168.2.2/24
GE1/0/4
192.168.1.1/24 GE1/0/4
192.168.2.1/24
9
# Configure track entry 1 to monitor the link state of GigabitEthernet 1/0/1.
[RouterA] track 1 interface gigabitethernet 1/0/1
# Associate track entry 1 with the backup interface GigabitEthernet 1/0/2.
[RouterA] interface gigabitethernet 1/0/2
[RouterA-GigabitEthernet1/0/2] backup track 1
[RouterA-GigabitEthernet1/0/2] quit
Verifying the configuration
# Verify that the backup interface GigabitEthernet 1/0/2 is in STANDBY state while the primary link is
operating correctly.
[RouterA] display interface-backup state
IB Track Information:
GE1/0/2 Track: 1 State: STANDBY
# Shut down the primary interface GigabitEthernet 1/0/1.
[RouterA] interface gigabitethernet 1/0/1
[RouterA-GigabitEthernet1/0/1] shutdown
# Verify that the backup interface GigabitEthernet 1/0/2 comes up after the primary link goes down.
[RouterA-GigabitEthernet1/0/1] display interface-backup state
IB Track Information:
GE1/0/2 Track: 1 State: UP
Example: Configuring load-shared interface backup
Network configuration
As shown in Figure 5:
•
Configure GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 on Router A to back up the primary
interface GigabitEthernet 1/0/1.
•
Assign GigabitEthernet 1/0/2 higher priority than GigabitEthernet 1/0/3.
•
On the primary interface:
ï‚¡ Specify the interface bandwidth used for traffic load calculation.
ï‚¡ Set the upper and lower thresholds to 80 and 20, respectively.
Figure 5 Network diagram
Procedure
1. Assign IP addresses to the interfaces, as shown in Figure 5. (Details not shown.)
2. Configure static routes:
GE1/0/2
2.2.2.1/24
GE1/0/1
1.1.1.1/24
GE1/0/3
3.3.3.1/24
GE1/0/1
1.1.1.2/24
GE1/0/2
2.2.2.2/24
GE1/0/3
3.3.3.2/24
Router A Router B
Host A Host B
192.168.1.2/24 192.168.2.2/24
GE1/0/4
192.168.1.1/24 GE1/0/4
192.168.2.1/24
10
# On Router A, configure static routes to 192.168.2.0/24 through the primary and backup
interfaces.
<RouterA> system-view
[RouterA] ip route-static 192.168.2.0 24 gigabitethernet 1/0/1 1.1.1.2
[RouterA] ip route-static 192.168.2.0 24 gigabitethernet 1/0/2 2.2.2.2
[RouterA] ip route-static 192.168.2.0 24 gigabitethernet 1/0/3 3.3.3.2
# On Router B, configure static routes to 192.168.1.0/24.
<RouterB> system-view
[RouterB] ip route-static 192.168.1.0 24 gigabitethernet 1/0/1 1.1.1.1
[RouterB] ip route-static 192.168.1.0 24 gigabitethernet 1/0/2 2.2.2.1
[RouterB] ip route-static 192.168.1.0 24 gigabitethernet 1/0/3 3.3.3.1
3. On Router A, configure backup interfaces and traffic thresholds:
# Specify GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 to back up GigabitEthernet 1/0/1,
and assign them with a priority of 30 and 20, respectively.
[RouterA] interface gigabitethernet 1/0/1
[RouterA-GigabitEthernet1/0/1] backup interface gigabitethernet 1/0/2 30
[RouterA-GigabitEthernet1/0/1] backup interface gigabitethernet 1/0/3 20
# Set the expected bandwidth to 10000 kbps on the primary interface.
[RouterA-GigabitEthernet1/0/1] bandwidth 10000
# Set the upper and lower thresholds to 80 and 20, respectively.
[RouterA-GigabitEthernet1/0/1] backup threshold 80 20
Verifying the configuration
# Display traffic statistics for load-shared interfaces.
[RouterA-GigabitEthernet1/0/1] display interface-backup statistics
Interface: GigabitEthernet1/0/1
Statistics interval: 30 s
Bandwidth: 10000000 bps
PrimaryTotalIn: 102 bytes
PrimaryTotalOut: 108 bytes
PrimaryIntervalIn: 102 bytes
PrimaryIntervalOut: 108 bytes
Primary used bandwidth: 28 bps
TotalIn: 102 bytes
TotalOut: 108 bytes
TotalIntervalIn: 102 bytes
TotalIntervalOut: 108 bytes
Total used bandwidth: 28 bps
The output shows that the upper traffic threshold has not been exceeded. All traffic is transmitted
through the primary interface GigabitEthernet 1/0/1.
# Verify that both backup interfaces are in STANDBY state because the upper threshold has not
been exceeded.
[RouterA-GigabitEthernet1/0/1] display interface-backup state
Interface: GE1/0/1
UpDelay: 5 s
DownDelay: 5 s
Upper threshold: 80
Lower threshold: 20
State: UP
11
Backup interfaces:
GE1/0/2 Priority: 30 State: STANDBY
GE1/0/3 Priority: 20 State: STANDBY
# Increase the incoming or outgoing traffic rate to be higher than 8000 kbps (80% of the specified
bandwidth) on the primary interface. (Details not shown.)
# Verify that the backup interface GigabitEthernet 1/0/2 comes up to participate in traffic forwarding,
because it has higher priority than GigabitEthernet 1/0/3.
[RouterA-GigabitEthernet1/0/1] display interface-backup state
Interface: GE1/0/1
UpDelay: 5 s
DownDelay: 5 s
Upper threshold: 80
Lower threshold: 20
State: UP
Backup interfaces:
GE1/0/2 Priority: 30 State: UP
GE1/0/3 Priority: 20 State: STANDBY
12
Configuring CFD
About CFD
Connectivity Fault Detection (CFD), which conforms to IEEE 802.1ag Connectivity Fault
Management (CFM) and ITU-T Y.1731, is an end-to-end link layer OAM mechanism. CFD is used for
link connectivity detection, fault verification, and fault location in Ethernet networks.
Basic CFD concepts
Maintenance domain
A maintenance domain (MD) defines the network or part of the network where CFD plays its role. An
MD is identified by its MD name.
Maintenance association
A maintenance association (MA) is a part of an MD. You can configure multiple MAs in an MD as
needed. An MA is identified by the MD name + MA name.
In an Ethernet network, an MA serves the specified VLAN or no VLAN. An MA that serves a VLAN is
considered to be carrying VLAN attribute. An MA that serves no VLAN is considered to be carrying
no VLAN attribute.
Maintenance association end point
An MEP is configured on a port and belongs to an MA.
MEPs define the boundary of the MA. Each MEP is identified by a MEP ID.
The MA to which a MEP belongs defines the VLAN of packets sent by the MEP.
MEPs include inward-facing MEPs and outward-facing MEPs:
•
An inward-facing MEP does not send packets to its host port. Rather, it sends packets to other
ports on the device. The packets are broadcast in the VLAN that the MA of the MEP serves.
Inward-facing MEPs are not supported in the current software version.
•
An outward-facing MEP sends packets to its host port.
MEP list
A MEP list is a collection of local MEPs allowed to be configured and the remote MEPs to be
monitored in the same MA. It lists all the MEPs configured on different devices in the same MA. The
MEPs all have unique MEP IDs. When a MEP receives from a remote device a continuity check
message (CCM) carrying a MEP ID not in the MEP list of the MA, it drops the message.
The local device must send CCM messages carrying the Remote Defect Indication (RDI) flag bits.
Otherwise, the peer device cannot sense certain failures. When a local MEP has not learned all
remote MEPs in the MEP list, the MEPs in the MA might not carry the RDI flag bits in CCMs.
CFD levels
MD levels
To accurately locate faults, CFD introduces eight levels (from 0 to 7) to MDs. The bigger the number,
the higher the level and the larger the area covered. Domains can touch but cannot intersect or nest.
MD levels facilitate fault location and make fault location more accurate. As shown in Figure 6, MD_A
in light blue touches MD_B in dark blue. If a connectivity fault is detected on the link between Device
A and Device D, any of these four devices might fail. If a connectivity fault is also detected at the
13
boundary of MD_B, the failure points can be any of Device B through Device D. If the devices in
MD_B can operate correctly, at least Device C is operational.
Figure 6 Two touched MDs
CFD exchanges messages and performs operations on a per-domain basis. By planning MDs
correctly in a network, you can use CFD to rapidly locate failure points.
MA and MEP levels
The level of an MA equals the level of the MD to which the MA belongs.
The level of a MEP equals the level of the MD to which the MEP belongs.
CFD grading example
Figure 7 demonstrates a grading example of the CFD module. Four levels of MDs (0, 2, 3, and 5) are
designed. The bigger the number, the higher the level and the larger the area covered. MPs are
configured on the ports of Device A through Device F. Port A of Device B is configured with the
following MPs:
•
A level 5 MIP.
•
A level 3 inward-facing MEP.
•
A level 2 inward-facing MEP.
•
A level 0 outward-facing MEP.
Port A2
Port A1 Port A3
Port A4
Device A
Port B2
Port B1 Port B3
Port B4
Device B
Port C2
Port C1 Port C3
Port C4
Device C
Port D2
Port D1 Port D3
Port D4
Device D
Port E2
Port E1 Port E3
Port E4
Device E
MD_A
MD_B
Port
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57
  • Page 58 58
  • Page 59 59
  • Page 60 60
  • Page 61 61
  • Page 62 62
  • Page 63 63
  • Page 64 64
  • Page 65 65
  • Page 66 66
  • Page 67 67
  • Page 68 68
  • Page 69 69
  • Page 70 70
  • Page 71 71
  • Page 72 72
  • Page 73 73
  • Page 74 74
  • Page 75 75
  • Page 76 76
  • Page 77 77
  • Page 78 78
  • Page 79 79
  • Page 80 80
  • Page 81 81
  • Page 82 82
  • Page 83 83
  • Page 84 84
  • Page 85 85
  • Page 86 86
  • Page 87 87
  • Page 88 88
  • Page 89 89
  • Page 90 90
  • Page 91 91
  • Page 92 92
  • Page 93 93
  • Page 94 94
  • Page 95 95
  • Page 96 96
  • Page 97 97
  • Page 98 98
  • Page 99 99
  • Page 100 100
  • Page 101 101
  • Page 102 102
  • Page 103 103
  • Page 104 104
  • Page 105 105
  • Page 106 106
  • Page 107 107
  • Page 108 108
  • Page 109 109
  • Page 110 110
  • Page 111 111
  • Page 112 112
  • Page 113 113
  • Page 114 114
  • Page 115 115
  • Page 116 116
  • Page 117 117
  • Page 118 118
  • Page 119 119
  • Page 120 120
  • Page 121 121
  • Page 122 122
  • Page 123 123
  • Page 124 124
  • Page 125 125
  • Page 126 126
  • Page 127 127
  • Page 128 128
  • Page 129 129
  • Page 130 130
  • Page 131 131
  • Page 132 132
  • Page 133 133
  • Page 134 134
  • Page 135 135
  • Page 136 136
  • Page 137 137
  • Page 138 138
  • Page 139 139
  • Page 140 140
  • Page 141 141
  • Page 142 142
  • Page 143 143
  • Page 144 144
  • Page 145 145
  • Page 146 146
  • Page 147 147
  • Page 148 148
  • Page 149 149
  • Page 150 150
  • Page 151 151
  • Page 152 152
  • Page 153 153
  • Page 154 154
  • Page 155 155
  • Page 156 156
  • Page 157 157
  • Page 158 158
  • Page 159 159
  • Page 160 160
  • Page 161 161
  • Page 162 162
  • Page 163 163
  • Page 164 164
  • Page 165 165
  • Page 166 166
  • Page 167 167
  • Page 168 168
  • Page 169 169
  • Page 170 170
  • Page 171 171
  • Page 172 172
  • Page 173 173
  • Page 174 174
  • Page 175 175
  • Page 176 176
  • Page 177 177
  • Page 178 178
  • Page 179 179
  • Page 180 180
  • Page 181 181
  • Page 182 182
  • Page 183 183
  • Page 184 184
  • Page 185 185
  • Page 186 186
  • Page 187 187
  • Page 188 188
  • Page 189 189
  • Page 190 190
  • Page 191 191
  • Page 192 192
  • Page 193 193
  • Page 194 194
  • Page 195 195
  • Page 196 196
  • Page 197 197
  • Page 198 198
  • Page 199 199
  • Page 200 200
  • Page 201 201
  • Page 202 202
  • Page 203 203
  • Page 204 204
  • Page 205 205
  • Page 206 206
  • Page 207 207
  • Page 208 208
  • Page 209 209
  • Page 210 210
  • Page 211 211
  • Page 212 212
  • Page 213 213
  • Page 214 214
  • Page 215 215
  • Page 216 216
  • Page 217 217
  • Page 218 218
  • Page 219 219
  • Page 220 220
  • Page 221 221
  • Page 222 222
  • Page 223 223
  • Page 224 224
  • Page 225 225
  • Page 226 226
  • Page 227 227
  • Page 228 228
  • Page 229 229
  • Page 230 230
  • Page 231 231
  • Page 232 232
  • Page 233 233
  • Page 234 234
  • Page 235 235
  • Page 236 236
  • Page 237 237
  • Page 238 238
  • Page 239 239
  • Page 240 240
  • Page 241 241
  • Page 242 242
  • Page 243 243
  • Page 244 244
  • Page 245 245
  • Page 246 246
  • Page 247 247
  • Page 248 248
  • Page 249 249
  • Page 250 250
  • Page 251 251
  • Page 252 252
  • Page 253 253
  • Page 254 254
  • Page 255 255
  • Page 256 256
  • Page 257 257
  • Page 258 258
  • Page 259 259
  • Page 260 260
  • Page 261 261
  • Page 262 262
  • Page 263 263
  • Page 264 264
  • Page 265 265
  • Page 266 266
  • Page 267 267
  • Page 268 268

Aruba JG408A Installation guide

Category
Networking
Type
Installation guide

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI