Aruba JG802A Configuration Guide

JG802A
Aruba
Brand
Aruba
Model
JG802A
Category
Networking
Type
Configuration Guide
1
Contents
Example: Configuring DRNI and VRRP ························································· 1
Network configuration ········································································································································ 1
Analysis ······························································································································································ 3
Applicable product matrix ··································································································································· 3
Configuration procedure····································································································································· 4
Procedure summary ··································································································································· 4
Configuring DRNI ······································································································································· 4
Deploying a VRRP gateway on the DR member devices ·········································································· 7
Configuring the links between the DR member devices and the Layer 3 virtualization server ·················· 7
Configuring the links between the DR member devices and core devices ················································ 8
Configuring BGP between the DR member devices and core devices ······················································ 8
Configuring BGP between the DR member devices and the server ························································ 10
Configuring OSPF between the DR member devices and the server ······················································ 11
Configuring the links between the core devices and DR member devices ·············································· 11
Configuring the links between the core devices and the service network ················································ 12
Configuring BGP on the core devices for communication with the DR member devices ························· 12
Configuring OSPF on the core devices for communication with the service network ······························ 13
Traffic forwarding models ································································································································· 14
Underlay traffic forwarding models ··········································································································· 14
Verifying the configuration································································································································ 15
Verification commands ····························································································································· 15
Procedure ················································································································································· 15
Testing network convergence ·························································································································· 17
Testing network convergence upon single points of failure ····································································· 17
Upgrading the devices ····································································································································· 17
Upgrading the DR member devices ········································································································· 17
Expanding the network····································································································································· 18
Expanding the DR system ························································································································ 18
Replacing hardware ········································································································································· 19
Replacing a service module ····················································································································· 19
Replacing a switching fabric module ········································································································ 19
1
Example: Configuring DRNI and VRRP
Network configuration
In the underlay network as shown in Figure 1, deploy DRNI at the access layer to provide high
availability and load balancing services for access devices. Deploy VRRP to provide gateway
redundancy and ensure user service continuity. You can achieve the following purposes on the
server through the VRRP gateway:
•
To implement Layer 2 connectivity, the server can communicate with the service network at
Layer 2 through the DR system.
•
Use the secondary IP addresses of the VLAN interfaces created on the DR member devices to
set up Layer 3 links between the server and the core devices, and configure BGP or OSPF to
achieve Layer 3 connectivity.
Figure 1 Network diagram
Device role Interface IP address Remarks
DRNI 1 WGE1/0/1 N/A Member port of a DR
interface.
Connected to the server.
HGE1/0/3
HGE1/0/2
HGE1/0/1
HGE1/0/3
HGE1/0/1
HGE1/0/2
HGE1/0/28
HGE1/0/27
HGE1/0/25~HGE1/0/26
HGE1/0/27
HGE1/0/28
WGE1/0/2 WGE1/0/2
WGE1/0/1
WGE1/0/1
BAGG 1
Server
M-LAG 1 M-LAG 2
Core 1 Core 2
Service network
HGE1/0/25~HGE1/0/26
Peer link
Keepalive
Access layer
Distribution layer
VRRP Virtual
BAGG 1024
IPL
DR 1 DR 2
2
Device role Interface IP address Remarks
WGE1/0/2 100.100.100.5/30 Connected to WGE1/0/2
on DRNI 2 to establish
the DR keepalive link.
HGE1/0/25 N/A Member port the IPP.
Connected to
HGE1/0/25 on DRNI 2.
HGE1/0/26 N/A Member port the IPP.
Connected to
HGE1/0/26 on DRNI 2.
HGE1/0/27 10.39.245.13/31 Connected to HGE1/0/2
on Core 2.
HGE1/0/28 10.39.244.13/31 Connected to HGE1/0/1
on Core 1.
Vlan-interface100
10.40.196.61/26
Secondary IP address:
100.127.128.253/24
Virtual IP address of the
VRRP group:
10.40.196.1
10.40.196.1
Connected to the server.
Vlan-interface4094 100.100.100.1/30 Connects two DR
member devices over a
Layer 3 link.
Bridge-Aggregation 1 N/A DR interface.
Connected to the server.
Bridge-Aggregation
1024 N/A IPP.
Connected to the IPL.
DRNI 2
WGE1/0/1 N/A Member port of the DR
interface.
Connected to the server.
WGE1/0/2 100.100.100.6/30 Connected to WGE1/0/2
on DRNI 1.
HGE1/0/25 N/A Member port of the IPP.
Connected to
HGE1/0/25 on DRNI 1.
HGE1/0/26 N/A Member port of the IPP.
Connected to
HGE1/0/26 on DRNI 1.
HGE1/0/27 10.39.244.45/31 Connected to HGE1/0/2
on Core 1.
HGE1/0/28 10.39.245.45/31 Connected to HGE1/0/1
on Core 2.
Vlan-interface100
10.40.196.62/26
Secondary IP address:
100.127.128.254/24
Virtual IP address of the
VRRP group:
Connected to the server.
3
Device role Interface IP address Remarks
10.40.196.1
10.40.196.1
Vlan-interface4094 100.100.100.2/30 Connects two DR
member devices over a
Layer 3 link.
Bridge-Aggregation 1 N/A DR interface.
Connected to the server.
Bridge-Aggregation
1024 N/A IPP.
Connected to the IPL.
Core 1
HGE1/0/1 10.39.244.12/31 Connected to
HGE1/0/28 on DRNI 1.
HGE1/0/2 10.39.244.44/31 Connected to
HGE1/0/27 on DRNI 2.
HGE1/0/3 22.22.1.1/24 Connected to the
service network.
Core 2
HGE1/0/1 10.39.245.44/31 Connected to
HGE1/0/28 on DRNI 2.
HGE1/0/2 10.39.245.12/31 Connected to
HGE1/0/27 on DRNI 1.
HGE1/0/3 12.12.1.1/24 Connected to the
service network.
Analysis
•
Deploy link aggregation between DRNI 1 and the server and between DRNI 2 and the server.
•
Deploy DRNI for DRNI 1 and DRNI 2 at the access layer. Configure a VRRP group and specify
its virtual IP address as the gateway address of the server.
•
Core 1 and Core 2 are Layer 3 devices connected to the service network.
•
Create VLAN interfaces on the DR interfaces of the DR member devices, and configure the
primary and secondary IP addresses.
Set up Layer 3 links between the DR member devices and the core devices, and configure
BGP between them to achieve Layer 3 connectivity.
Use the secondary IP address of the VLAN interfaces created on the DR interfaces to set
up Layer 3 links to the server, and configure BGP or OSPF to achieve Layer 3 connectivity.
Applicable product matrix
IMPORTANT:
In addition to running an applicable software version, you must also install the most recent patch, if
any.
Device Software version
HPE FlexFabric 5944 & 5945 Switch Series R6710
HPE FlexFabric 5940 Switch Series R6710
4
Device Software version
HPE FlexFabric 5710 Switch Series R6710
HPE FlexFabric 12900E Switch Series (Type K) R5210
HPE FlexFabric 12900E Switch Series (Type X) R7624P08
Configuration procedure
Procedure summary
•
Configuring DRNI
•
Deploying a VRRP gateway on the DR member devices
•
Configuring the links between the DR member devices and the Layer 3 virtualization server
•
Configuring the links between the DR member devices and core devices
•
Configuring BGP between the DR member devices and core devices
•
Configure BGP or OSPF between the DR member devices and the server (perform one of the
following tasks):
(Optional.) Configuring BGP between the DR member devices and the server
(Optional.) Configuring OSPF between the DR member devices and the server
•
Configuring the links between the core devices and DR member devices
•
Configuring the links between the core devices and the service network
•
Configuring BGP on the core devices for communication with the DR member devices
•
Configuring OSPF on the core devices for communication with the service network
Configuring DRNI
DRNI 1 DRNI 2 Description Remarks
interface
Bridge-Aggregation
1024
interface
Bridge-Aggregation
1024
Create Layer 2
aggregate interface
Bridge-Aggregation
1024.
N/A
link-aggregation mode
dynamic link-aggregation mode
dynamic
Configure
Bridge-Aggregation
1024 to operate in
dynamic mode, and
enable LACP.
N/A
quit quit N/A N/A
interface range
HundredGigE1/0/25
HundredGigE1/0/26
interface range
HundredGigE1/0/25
HundredGigE1/0/26
Enter IPL physical port
view. N/A
port link-aggregation
group 1024 port link-aggregation
group 1024
Assign the physical
ports to Layer 2
aggregation group 1024. N/A
quit quit N/A N/A
interface
Bridge-Aggregation interface
Bridge-Aggregation102 Enter the view of
Bridge-Aggregation
N/A
5
DRNI 1 DRNI 2 Description Remarks
1024
4
1024 to be used as IPP.
port drni intra-portal-port
1 port drni intra-portal-port
1
Configure
Bridge-Aggregation
1024 as the IPP. N/A
port link-type trunk port link-type trunk Set the link type of the
physical port to trunk. N/A
port trunk permit vlan all port trunk permit vlan all Assign the port to all
VLANs. N/A
undo mac-address static
source-check enable undo mac-address static
source-check enable Disable the static source
check feature.
This configuration
avoids cross-IPL Layer 3
traffic forwarding failure.
quit quit N/A N/A
vlan 4094 vlan 4094 Create VLAN 4094. N/A
quit quit N/A N/A
interface Vlan-interface
4094 interface Vlan-interface
4094 Create VLAN-interface
4094. N/A
ip address
100.100.100.1
255.255.255.252
ip address
100.100.100.2
255.255.255.252
Assign an IP address to
the interface for
establishing IBGP peer
connection on the IPL.
N/A
quit quit N/A N/A
interface
Bridge-Aggregation 1
interface
Bridge-Aggregation 1 Enter the view of
Bridge-Aggregation 1. N/A
link-aggregation mode
dynamic link-aggregation mode
dynamic
Configure
Bridge-Aggregation 1 to
operate in dynamic
mode, and enable
LACP.
N/A
lacp edge-port lacp edge-port Configure the aggregate
interface as an edge
aggregate interface. N/A
port drni group 1 port drni group 1 Assign the aggregate
interface to a DR group. N/A
quit quit N/A N/A
ip vpn-instance
drni-keepalive ip vpn-instance
drni-keepalive Create VPN instance
drni-keepalive. N/A
route-distinguisher
100:1 route-distinguisher
100:1 Configure the RD of the
VPN instance. N/A
vpn-target 1:1 vpn-target 1:1 Configure the RT of the
VPN instance. N/A
quit quit N/A N/A
interface
Twenty-FiveGigE1/0/2 interface
Twenty-FiveGigE1/0/2
Enter the view of
interface
Twenty-FiveGigE 1/0/2. N/A
port link-mode route port link-mode route Configure the Ethernet
interface to work in
Layer 3 mode. N/A
6
DRNI 1 DRNI 2 Description Remarks
ip binding vpn-instance
drni-keepalive ip binding vpn-instance
drni-keepalive
Associate the interface
with VPN instance
drni-keepalive. N/A
ip address
100.100.100.5
255.255.255.252
ip address
100.100.100.6
255.255.255.252
Configure the IP
address for the
keepalive link. N/A
quit quit N/A N/A
drni role priority 10000 drni role priority 40000 Set the DR role priority
of the device. N/A
drni system-mac
8465-6958-e2c4 drni system-mac
8465-6958-e2c4 Configure the DR
system MAC address. N/A
drni system-number 1 drni system-number 2 Set the DR system
number. N/A
drni system-priority
10000 drni system-priority
10000 Set the DR system
priority. N/A
drni standalone enable drni standalone enable Enable DRNI
standalone mode. N/A
drni keepalive ip
destination
100.100.100.6 source
100.100.100.5
vpn-instance
drni-keepalive
drni keepalive ip
destination
100.100.100.5 source
100.100.100.6
vpn-instance
drni-keepalive
Configure DR keepalive
packet parameters. N/A
drni mad exclude
interface
Twenty-FiveGigE1/0/2
drni mad exclude
interface
Twenty-FiveGigE1/0/2
Configure DRNI MAD to
not shut down the
interface attached to the
keepalive link.
N/A
drni mad exclude
interface Vlan-interface
4094
drni mad exclude
interface Vlan-interface
4094
Configure DRNI MAD to
not shut down the Layer
3 interconnection
interface for fast entry
synchronization upon
recovery of the DR
interface from a failure.
N/A
drni restore-delay 300 drni restore-delay 300
Set the data restoration
interval for more data
synchronization time
and faster convergence.
N/A
stp instance 0 root
primary stp instance 0 root
primary
Configure the DR
member device as the
root bridge. N/A
stp global enable stp global enable Enable the spanning
tree feature globally. N/A
stp tc-protection stp tc-protection
Enable TC-BPDU attack
guard for the device to
avoid frequent deletion
of MAC address entries
and ARP entries.
N/A
stp bpdu-protection stp bpdu-protection Enable BPDU guard
globally. N/A
7
Deploying a VRRP gateway on the DR member devices
DRNI 1 DRNI 2 Description Remarks
vlan 100 vlan 100
Configure the VLAN
used to communicate
with a virtualization
server.
N/A
quit quit N/A N/A
interface Vlan-interface
100 interface Vlan-interface
100 Create VLAN-interface
100. N/A
ip address 10.40.196.61
255.255.255.192
ip address
100.127.128.253
255.255.255.0 sub
ip address 10.40.196.62
255.255.255.192
ip address
100.127.128.254
255.255.255.0 sub
Assign the primary and
secondary IP addresses
to VLAN-interface 100. N/A
vrrp vrid 1 virtual-ip
10.40.196.1 vrrp vrid 1 virtual-ip
10.40.196.1
Configure the virtual IP
address of a VRRP
group. N/A
vrrp vrid 1 priority 200 vrrp vrid 1 priority 100 Configure the priority of
the device in the VRRP
group.
VRRP determines the
role (master or backup)
of each router in a
VRRP group by priority.
A router with higher
priority is more likely to
become the master.
quit quit N/A N/A
drni mad exclude
interface Vlan-interface
100
drni mad exclude
interface Vlan-interface
100
Configure DRNI MAD to
not shut down the
interface connected to
the server for fast entry
synchronization upon
recovery of the DR
interface from a failure.
As a best practice, do
not configure this
command for an 12900E
device (Type X). If you
configure this command
for the device, the fault
recovery time might
exceed 500
milliseconds.
Configuring the links between the DR member devices and
the Layer 3 virtualization server
DRNI 1 DRNI 2 Description Remarks
vlan 2 to 1000 vlan 2 to 1000 Create VLANs. N/A
quit quit N/A N/A
interface
Twenty-FiveGigE1/0/1 interface
Twenty-FiveGigE1/0/1
Configuring the interface
used to connect to the
Layer 3 virtualization
server.
N/A
port link-aggregation
group 1 port link-aggregation
group 1
Assign the physical port
to Layer 2 aggregation
group 1. N/A
8
DRNI 1 DRNI 2 Description Remarks
quit quit N/A N/A
interface
Bridge-Aggregation 1 interface
Bridge-Aggregation 1 Enter the view of
Bridge-Aggregation 1. N/A
port link-type trunk port link-type trunk Set the link type of the
physical port to trunk. N/A
port trunk permit vlan 2
to 1000 port trunk permit vlan 2
to 1000 Assign the port to VLAN
2 through VLAN 1000. N/A
port trunk pvid vlan 100 port trunk pvid vlan 100 Set the PVID for the
trunk port to 100. N/A
quit quit N/A N/A
Configuring the links between the DR member devices and
core devices
DRNI 1 DRNI 2 Description Remarks
interface
HundredGigE1/0/27 interface
HundredGigE1/0/28
Enter view of the
interface connected to
Core 2. N/A
port link-mode route port link-mode route Configure the Ethernet
interface to work in
Layer 3 mode. N/A
ip address 10.39.245.13
255.255.255.254 ip address 10.39.245.45
255.255.255.254 Assign an IP address to
the interface. N/A
quit quit N/A N/A
interface
HundredGigE1/0/28 interface
HundredGigE1/0/27
Enter view of the
interface connected to
Core 1. N/A
port link-mode route port link-mode route Configure the Ethernet
interface to work in
Layer 3 mode. N/A
ip address 10.39.244.13
255.255.255.254
ip address 10.39.244.45
255.255.255.254 Assign an IP address to
the interface. N/A
quit quit N/A N/A
Configuring BGP between the DR member devices and core
devices
DRNI 1 DRNI 2 Description Remarks
bgp 65115 bgp 65115 Enable the specified
BGP instance and enter
its view. N/A
bgp update-delay
on-startup 120 bgp update-delay
on-startup 120 Configure BGP to delay
sending route updates The DR member
devices learn route
9
DRNI 1 DRNI 2 Description Remarks
on reboot, and set the
delay timer to 120
seconds.
entries after
synchronizing MAC
address entries and
ARP entries.
non-stop-routing non-stop-routing Enable BGP nonstop
routing (NSR).
Avoid forwarding
interruption on the DR
member devices.
router-id 10.41.254.140 router-id 10.41.254.141 Specify the router ID for
the BGP instance. N/A
group DRNI internal group DRNI internal Create an IBGP peer
group named DRNI. N/A
peer DRNI
route-update-interval 0 peer DRNI
route-update-interval 0
Specify the interval for
sending the same
update to the peer group
as 0.
Enable the device to fast
send update to the peer
group upon route
changes to speed up
route convergence after
a DR primary/secondary
switchover occurs.
peer DRNI timer
keepalive 10 hold 30 peer DRNI timer
keepalive 10 hold 30
Set the keepalive
interval and hold time for
the peer group to 10
seconds and 30
seconds, respectively.
N/A
group core external group core external Create an EBGP peer
group to connect to the
core device. N/A
peer core as-number
65105 peer core as-number
65105
Configure the AS
number of the EBGP
peer group. N/A
peer core
route-update-interval 0 peer core
route-update-interval 0
Specify the interval for
sending the same
update to the peer group
as 0.
Enable the device to fast
send update to the peer
group upon route
changes to speed up
route convergence after
a DR primary/secondary
switchover occurs.
peer core timer
keepalive 10 hold 30 peer core timer
keepalive 10 hold 30
Set the keepalive
interval and hold time for
the peer group to 10
seconds and 30
seconds, respectively.
N/A
peer 10.39.244.12 group
core peer 10.39.244.44 group
core Add Core 1 as a peer to
peer group core. N/A
peer 10.39.245.12 group
core peer 10.39.245.44 group
core Add Core 2 as a peer to
peer group core. N/A
peer 100.100.100.2
group DRNI peer 100.100.100.1
group DRNI
Add the other DRNI as a
peer to peer group
DRNI. N/A
address-family ipv4
unicast address-family ipv4
unicast Enter BGP IPv4 unicast
address family view. N/A
balance 8 balance 8 Enable load balancing
and set the maximum
number of BGP ECMP
N/A
10
DRNI 1 DRNI 2 Description Remarks
routes as 8 for load
balancing.
preference 180 200 130 preference 180 200 130
Set preferences for
EBGP, IBGP, and local
routes to 180, 200, and
130, respectively.
Adjust the possibility of
selecting BGP routes as
optimal routes.
import-route direct import-route direct Redistribute direct
routes. N/A
import-route ospf import-route ospf
Redistribute OSPF
routes between the DR
member device and
server.
N/A
peer core enable peer core enable
Enable BGP to
exchange routing
information with peer
group core.
N/A
peer core
advertise-community peer core
advertise-community
Advertise the
COMMUNITY attribute
to peer group core. N/A
peer DRNI enable peer DRNI enable
Enable BGP to
exchange routing
information with peer
group DRNI.
N/A
peer DRNI
next-hop-local peer DRNI
next-hop-local
Set the local router as
the next hop for routes
sent to peer group
DRNI.
N/A
Configuring BGP between the DR member devices and the
server
Perform this task or the task in "Configuring OSPF between the DR member devices and the
server."
DRNI 1 DRNI 2 Description Remarks
bgp 65115 bgp 65115 Enable the specified
BGP instance and enter
its view.
Use BGP to implement
Layer 3 connectivity
between the DR
member devices and the
server.
group docker_host
external group docker_host
external
Create an EBGP peer
group to connect to the
server. N/A
peer docker_host
as-number 60000 peer docker_host
as-number 60000
Configure the AS
number of the EBGP
peer group. N/A
peer 100.127.128.3
group docker_host peer 100.127.128.3
group docker_host
Add the server (with IP
address 100.127.128.3)
to peer group
docker_host.
N/A
11
DRNI 1 DRNI 2 Description Remarks
address-family ipv4
unicast address-family ipv4
unicast Enter BGP IPv4 unicast
address family view. N/A
peer docker_host
enable peer docker_host
enable
Enable BGP to
exchange routing
information with peer
group docker_host.
Establish EBGP peer
with the Layer 3
virtualization server.
peer docker_host
route-limit 5000 peer docker_host
route-limit 5000
Set the maximum
number of routes that
can be received from a
peer group.
N/A
Configuring OSPF between the DR member devices and the
server
Perform this task or the task in "Configuring BGP between the DR member devices and the server."
DRNI 1 DRNI 2 Description Remarks
ospf 1 ospf 1 Enable OSPF and enter
OSPF view.
Use OSPF to implement
Layer 3 connectivity
between the DR
member devices and the
server.
stub-router include-stub
on-startup 900 stub-router include-stub
on-startup 900
Specify the cost of the
stub links (link type 3) in
Router LSAs to the
maximum value 65535,
in order to speed up
convergence.
N/A
import-route direct import-route direct Redistribute direct
routes into the OSPF
routing table. N/A
import-route bgp import-route bgp Redistribute BGP routes
into the OSPF routing
table. N/A
area 0.0.0.0 area 0.0.0.0 Enter OSPF area view. N/A
network 100.127.128.0
0.0.0.255 network 100.127.128.0
0.0.0.255
Configure OSPF to
advertise the local
network route. N/A
quit quit Exit OSPF area view. N/A
Configuring the links between the core devices and DR
member devices
Core 1 Core 2 Description Remarks
interface
HundredGigE1/0/1 interface
HundredGigE1/0/2
Enter the view of the
interface connected to
DRNI 1. N/A
12
Core 1 Core 2 Description Remarks
port link-mode route port link-mode route Configure the interface
to work in Layer 3 mode. N/A
ip address 10.39.244.12
255.255.255.254 ip address 10.39.245.12
255.255.255.254 Assign an IP address to
the interface. N/A
quit quit N/A N/A
interface
HundredGigE1/0/2 interface
HundredGigE1/0/1
Enter the view of the
interface connected to
DRNI 2. N/A
port link-mode route port link-mode route Configure the interface
to work in Layer 3 mode. N/A
ip address 10.39.244.44
255.255.255.254 ip address 10.39.245.44
255.255.255.254 Assign an IP address to
the interface. N/A
quit quit N/A N/A
Configuring the links between the core devices and the
service network
Core 1 Core 2 Description Remarks
interface
HundredGigE1/0/3 interface
HundredGigE1/0/3
Enter the view of the
interface connected to
the service network. N/A
port link-mode route port link-mode route Configure the interface
to work in Layer 3 mode. N/A
ip address 22.22.1.1
255.255.255.0 ip address 12.12.1.1
255.255.255.0 Assign an IP address to
the interface. N/A
quit quit Exit interface view. N/A
Configuring BGP on the core devices for communication with
the DR member devices
Core 1 Core 2 Description Remarks
bgp 65105 bgp 65105 Enable the specified
BGP instance and enter
its view. N/A
group DRNI external group DRNI external Create an EBGP peer
group named DRNI. N/A
peer DRNI as-number
65115 peer DRNI as-number
65115
Specify an AS number
for EBGP peer group
DRNI. N/A
peer 10.39.244.45 group
DRNI peer 10.39.245.45 group
DRNI Add DRNI2 as a peer to
peer group DRNI. N/A
peer 10.39.244.13 group
DRNI peer 10.39.245.13 group
DRNI Add DRNI1 as a peer to
peer group DRNI. N/A
13
Core 1 Core 2 Description Remarks
address-family ipv4
unicast address-family ipv4
unicast Enter BGP IPv4 unicast
address family view. N/A
balance 8 balance 8
Enable load balancing
and set the maximum
number of BGP ECMP
routes for load
balancing.
N/A
preference 180 200 130 preference 180 200 130
Set preferences for
EBGP, IBGP, and local
routes to 180, 200, and
130, respectively.
N/A
import-route direct import-route direct Redistribute direct
routes into the BGP
routing table. N/A
import-route ospf import-route ospf Redistribute OSPF
routes into the BGP
routing table. N/A
peer DRNI enable peer DRNI enable
Enable BGP to
exchange routing
information with peer
group DRNI.
N/A
peer DRNI
preferred-value 60000 peer DRNI
preferred-value 60000
Set preferred value
60000 for routes
received from peer
group DRNI.
Enable the routes
received from the peer
group to become the
optimal routes.
quit quit Exit BGP view. N/A
Configuring OSPF on the core devices for communication
with the service network
Core 1 Core 2 Description Remarks
ospf 1 ospf 1 Enable OSPF and enter
OSPF view. N/A
stub-router include-stub
on-startup 900 stub-router include-stub
on-startup 900
Specify the cost of the
stub links (link type 3) in
Router LSAs to the
maximum value 65535,
in order to speed up
convergence.
N/A
import-route direct import-route direct Redistribute direct
routes into the OSPF
routing table. N/A
import-route bgp import-route bgp Redistribute BGP routes
into the OSPF routing
table. N/A
area 0.0.0.0 area 0.0.0.0 Enter OSPF area view. N/A
network 22.22.1.0
0.0.0.255 network 12.12.1.0
0.0.0.255
Configure OSPF to
advertise the service
network route. N/A
14
Core 1 Core 2 Description Remarks
quit quit Exit OSPF area view. N/A
Traffic forwarding models
Underlay traffic forwarding models
Traffic type: Known IPv4 unicast, Layer 2 unicast, and unknown unicast.
Direction: South to north, north to south, east to west across the DR system, and west to east
across the DR system.
Forwarding path: Server > DR system > core devices > service network, service network > core
devices > DR system > server, DRNI 2 > DRNI 1, and DRNI 1 > DRNI 2.
Traffic simulation: Send packets by using the tester.
Load: Light load (less than 1000 flows).
Traffic direction to firewalls/LB: N/A
Traffic
type Direction Forwarding
path Traffic
simulation Load Traffic
direction to
firewalls/LB Remarks
Known IPv4
unicast South to
north
Server > DR
system > core
devices >
service
network
Tester Light N/A N/A
Known IPv4
unicast North to
south
Service
network >
core devices >
DR system >
server
Tester Light N/A N/A
Known IPv4
unicast
East to
west
across the
DR system
DRNI 2 >
DRNI 1 Tester Light N/A N/A
Known IPv4
unicast
West to
east
across the
DR system
DRNI 1 >
DRNI 2 Tester Light N/A N/A
Layer 2
unicast South to
north Server > DR
system Tester Light N/A N/A
Layer 2
unicast North to
south DR system >
server Tester Light N/A N/A
Layer 2
unicast
East to
west
across the
DR system
DRNI 2 >
DRNI 1 Tester Light N/A N/A
Layer 2
unicast
West to
east
across the
DR system
DRNI 1 >
DRNI 2 Tester Light N/A N/A
15
Traffic
type Direction Forwarding
path Traffic
simulation Load Traffic
direction to
firewalls/LB Remarks
Unknown
unicast South to
north Server > DR
system Tester Light N/A N/A
Unknown
unicast North to
south DR system >
server Tester Light N/A N/A
Unknown
unicast
East to
west
across the
DR system
DRNI 2 >
DRNI 1 Tester Light N/A N/A
Unknown
unicast
West to
east
across the
DR system
DRNI 1 >
DRNI 2 Tester Light N/A N/A
Verifying the configuration
Verification commands
DRNI 1 DRNI 2 Description
display drni summary
display drni summary Displays summary information about
DR interfaces.
display drni system
Displays the DR system settings.
display drni
keepalive
Displays DR keepalive packet
statistics.
display drni role
Displays DR role information.
display drni
consistency { type1 |
type2 }
consistency { type1 |
Displays information about the
configuration consistency check done
by DRNI.
display drni
consistency-check
status
consistency-check
Displays the configuration
consistency check status.
display interface
Bridge-Aggregation
[ brief
]
Bridge-Aggregation
Displays information about aggregate
interfaces.
Procedure
# Display the DR system settings on DRNI 1 to verify that DRNI 1 and DRNI 2 has established a DR
system.
[DRNI1] display drni system
System information
Local system number: 1 Peer system number: 2
Local system MAC: 8465-6958-e2c4 Peer system MAC: 8465-6958-e2c4
16
Local system priority: 10000 Peer system priority: 10000
Local bridge MAC: 0068-5116-5101 Peer bridge MAC: 90e7-1062-5371
Local effective role: Primary Peer effective role: Secondary
Health level: 0
Standalone mode on split: Enabled
In standalone mode: No
System timer information
Timer State Value (s) Remaining time (s)
Auto recovery Disabled - -
Restore delay Disabled 300 -
Consistency-check delay Disabled 150 -
Standalone delay Disabled - -
Role to None delay Disabled 60 -
# View summary information about DR interfaces on DRNI 1.
[DRNI1] display drni summary
Flags: A -- Aggregate interface down, B -- No peer DR interface configured
C -- Configuration consistency check failed
IPP: BAGG1024
IPP state (cause): UP
Keepalive link state (cause): UP
DR interface information
DR interface DR group Local state (cause) Peer state Remaining down time(s)
BAGG1 1 UP UP -
# View DR role information on DRNI 1.
[DRNI1] display drni role
Effective role information
Factors Local Peer
Effective role Primary Secondary
Initial role Primary Secondary
MAD DOWN state No Yes
Health level 0 0
Role priority 10000 40000
Bridge MAC 0068-5116-5101 90e7-1062-5371
Effective role trigger: IPL calculation
Effective role reason: MAD status
Configured role information
Factors Local Peer
Configured role Primary Secondary
Role priority 10000 40000
Bridge MAC 0068-5116-5101 90e7-1062-5371
# View information about the aggregate interfaces on DRNI 1.
[DRNI1] display interface Bridge-Aggregation brief
Brief information on interfaces in bridge mode:
Link: ADM - administratively down; Stby - standby
17
Speed: (a) - auto
Duplex: (a)/A - auto; H - half; F - full
Type: A - access; T - trunk; H - hybrid
Interface Link Speed Duplex Type PVID Description
BAGG1 UP 25G(a) F(a) T 100
BAGG1024 UP 200G(a) F(a) T 1
Testing network convergence
Testing network convergence upon single points of failure
Table 1 Network convergence upon single points of failure
Device Failure type Traffic interruption time
DR member device
Link failure. ≤ 500 ms
Node failure.
Fixed-port device: < 500 ms
Modular device:
• Device replacement: < 1000
ms
• Switching fabric module
replacement: 0 ms
• Service module
replacement: < 500 ms
Upgrading the devices
Upgrading the DR member devices
Checking the environment
Execute the commands in "Verification commands" and the following commands to verify that the
device is available for an upgrade.
DRNI 1 DRNI 2 Description
display device
display device
Displays device information.
display boot-loader display boot-loader Displays current software images and
startup software images.
display version
display version
Displays system version information.
Upgrading the device
1. Use the display version command to verify the current BootWare image version and
startup software version.
2. Use the release notes for the upgrade software version to evaluate the upgrade impact on your
network and verify the following items:
Software and hardware compatibility.
Version and size of the upgrade software.
18
Compatibility of the upgrade software with the current BootWare image and startup
software image.
3. Use the dir command to verify that the device has sufficient storage space for the upgrade
images. If the storage space is not sufficient, delete unused files by using the delete
command. Verify that each MPU in the system has sufficient storage space.
4. Use FTP or TFTP to transfer the upgrade image file to the root directory of a file system.
5. Upgrade the device according to the configuration guides for the device.
Verifying the traffic interruption time during the upgrade
Verify that the traffic interruption time is shorter than 500 ms during a switchover and shorter than
150 ms during fallback. For more information, see "Testing network convergence."
Verifying the upgrade result
Execute the commands in "Verification commands" and the following commands to verify that the
device is upgraded successfully.
DRNI 1 DRNI 2 Description
display device
display device
Displays device information.
display boot-loader display boot-loader Displays current software images and
startup software images.
display version
display version
Displays system version information.
Expanding the network
An expansion operation adds two leaf devices.
Expanding the DR system
Checking the environment
Execute the commands in "Verification commands" and the following commands to verify that the
device is available for an expansion.
DRNI 1 DRNI 2 Description
display device
display device
Displays device information.
display boot-loader display boot-loader Displays current software images and
startup software images.
display version
display version
Displays system version information.
Adding the device to the DR system
1. Disconnect the device from network management systems.
2. Upgrade the software of the device as needed.
3. Preconfigure the device.
4. Connect the device to network management systems.
5. Incorporate the device on the controller.
Verifying the traffic interruption time
For more information, see "Testing network convergence."
19
Verifying the expansion result
Execute the following commands to verify that the device is added successfully.
DRNI 1 DRNI 2 Description
display device
display device
Displays device information.
display boot-loader display boot-loader Displays current software images and
startup software images.
display version
display version
Displays system version information.
Replacing hardware
Replacing a service module
Checking the environment
Execute the commands in "Verification commands" and the following commands to verify that the
target device is available for a replacement.
DRNI 1 DRNI 2 Description
display device
display device
Displays device information.
display boot-loader display boot-loader Displays current software images and
startup software images.
display version
display version
Displays system version information.
Replacing a service module
1. Switch service and management traffic on the target service module to other service modules.
2. Power off the device and replace the service module, or replace the service module when the
device is running. For more information, see the installation guides for the service module.
Verifying the traffic interruption time
For more information, see "Testing network convergence."
Verifying the replacement result
Execute the commands in "Checking the environment."
Replacing a switching fabric module
Checking the environment
Execute the commands in "Verification commands" and the following commands to verify that the
target device is available for a replacement.
DRNI 1 DRNI 2 Description
display device
display device
Displays device information.
display boot-loader display boot-loader Displays current software images and
startup software images.
Page is loading ...
  • 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

Aruba JG802A Configuration Guide

JG802A
Aruba
Brand
Aruba
Model
JG802A
Category
Networking
Type
Configuration Guide
Download PDF
report

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

Finding information in a document is now easier with AI

Related papers

Other documents