Aruba Cascaded DRNI Systems Configuration Guide

i

Contents

Example: Setting up two cascaded DR systems with directly attached multicast

source and receivers ····················································································· 2

Network configuration ········································································································································ 2

Applicable product matrix ··································································································································· 3

Analysis ······························································································································································ 3

Procedure summary ··································································································································· 4

Configuring DRNI ······································································································································· 4

Configuring the dual-active gateways ········································································································ 9

Configuring Layer 3 multicast ··················································································································· 10

Traffic forwarding models ································································································································· 12

Underlay traffic characteristics ················································································································· 12

Forwarding models ··································································································································· 12

Testing network convergence upon single points of failure ············································································· 13

Verifying the configuration································································································································ 14

Verifying the status of the DR system ······································································································ 14

Verifying multicast forwarding information ······························································································· 15

Upgrading the devices ····································································································································· 19

Checking the environment ······················································································································· 19

Upgrading the devices ····························································································································· 19

Verifying the traffic interruption time during the upgrade ········································································· 19

Verifying the upgrade result ····················································································································· 19

Replacing hardware ········································································································································· 20

Replacing a service module ····················································································································· 20

Replacing a switching fabric module ········································································································ 20

Replace a device ······································································································································ 21

Example: Setting up two cascaded DR systems with multicast source and

receivers attached via intermediate devices ················································ 22

Network configuration ······································································································································ 22

Applicable product matrix ································································································································· 24

Analysis ···························································································································································· 24

Procedure summary ································································································································· 25

Configuring DRNI ····································································································································· 25

Configuring the dual-active gateways ······································································································ 29

Configuring OSPF for establishing Layer 3 connectivity between DR member devices ·························· 31

Configuring Layer 3 multicast ··················································································································· 34

Traffic forwarding models ································································································································· 36

Underlay traffic characteristics ················································································································· 36

Forwarding models ··································································································································· 36

Testing network convergence upon single points of failure ············································································· 37

Verifying the configuration································································································································ 37

Verifying the status of the DR system ······································································································ 37

Verifying routing configuration ·················································································································· 39

Upgrading the devices ····································································································································· 44

Checking the environment ······················································································································· 44

Upgrading the devices ····························································································································· 44

Verifying the traffic interruption time during the upgrade ········································································· 44

Verifying the upgrade result ····················································································································· 44

Replacing hardware ········································································································································· 45

Replacing a service module ····················································································································· 45

Replacing a switching fabric module ········································································································ 45

Replace a device ······································································································································ 46

2

Example: Setting up two cascaded DR

systems with directly attached multicast

source and receivers

Network configuration

To improve network reliability, set up a two-tier cascaded DRNI structure to support Layer 3 multicast

services, as shown in Figure 1. The receivers receive video-on-demand traffic through multicast.

PIM protocol is enabled on each device interface, and the entire PIM domain uses SM

non-administrative domain mode.

Multicast receivers can be singlehomed to the receiver side DR member devices or be attached to

DR interfaces. The multicast source is connected to a DR system through DR interfaces.

Figure 1 Network diagram

Device

Interface

IP address

Peer device and interface

Device A

WGE1/0/11 IPv4: 221.1.2.1/24 Device B: WGE1/0/11

Vlan-int20 IPv4: 20.1.1.1/24 Receiver 2

Vlan-int21 IPv4: 21.1.1.1/24 Receiver 1

Loopback0 IPv4: 3.3.3.3/32 N/A

HGE1/0/28 IPv4: 11.2.1.2/24 Device C: HGE1/0/4

HGE1/0/29 IPv4: 12.2.1.2/24 Device D: HGE1/0/4

Device C

Receiver2

HGE1/0/30

HGE1/0/28

Keepalive

HGE1/0/26

WGE1/0/11

HGE1/0/26

Peer-link

Keepalive Device D

Device A Device B

Source

HGE1/0/29

HGE1/0/28

HGE1/0/29

HGE1/0/30

M-LAG

Peer-link

HGE1/0/4 HGE1/0/5

HGE1/0/4

HGE1/0/5

HGE1/0/6 HGE1/0/6

HGE1/0/8 HGE1/0/8

Vlan-int20

Vlan-int10

Receiver1

Vlan-int21

HGE1/0/7 HGE1/0/7

WGE1/0/1

DR

IPL

3

Device

Interface

IP address

Peer device and interface

Device B

WGE1/0/11 IPv4: 221.1.2.2/24 Device A: WGE1/0/11

Vlan-int20 IPv4: 20.1.1.1/24 Receiver 2

Loopback0 IPv4: 4.4.4.4/32 N/A

HGE1/0/28 IPv4: 11.3.1.2/24 Device C: HGE1/0/5

HGE1/0/29 IPv4: 12.3.1.2/24 Device D: HGE1/0/5

Device C

HGE1/0/6 IPv4: 220.1.1.1/24 Device D: HGE1/0/6

Vlan-int10 IPv4: 10.1.1.1/24 Source

Loopback0 IPv4: 1.1.1.1/32 N/A

HGE1/0/4 IPv4: 11.2.1.1/24 Device A: HGE1/0/28

HGE1/0/5 IPv4: 11.3.1.1/24 Device B: HGE1/0/28

Device D

HGE1/0/6 IPv4: 220.1.1.2/24 Device C: HGE1/0/6

Vlan-int10 IPv4: 10.1.1.1/24 Source

Loopback0 IPv4: 2.2.2.2/32 N/A

HGE1/0/4 IPv4: 12.2.1.1/24 Device A: HGE1/0/29

HGE1/0/5 IPv4: 12.3.1.1/24 Device B: HGE1/0/29

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 Not supported

HPE FlexFabric 5710 Switch Series Not supported

HPE FlexFabric 12900E Switch Series (Type K) Not supported

HPE FlexFabric 12900E Switch Series (Type X) R7624P08

Analysis

•

Set up one DR system with Device A and Device B and another with Device C and Device D.

•

Create one VLAN interface for the same VLAN on Device A and Device B, respectively. In this

example, create VLAN-interface 20. Allocate the same IPv4 addresses and MAC address to the

VLAN interfaces for them to act as gateway interfaces. Assign DR interfaces to the VLAN of the

VLAN interfaces.

•

Create one VLAN interface for the same VLAN on Device C and Device D, respectively. In this

example, create VLAN-interface 10. Allocate the same IPv4 addresses and MAC address to the

4

VLAN interfaces for them to act as gateway interfaces. Assign DR interfaces to the VLAN of the

VLAN interfaces.

•

Enable IP multicast forwarding and IGMP snooping on Device A through Device D. A device

with IGMP snooping enabled forwards multicast traffic of known multicast groups to the

designated receivers instead of broadcasting the multicast traffic. Configure PIM on interfaces

of the devices.

•

Create VLAN-interface 21 on Device A to accommodate Receiver 1, which is singlehomed to

the device.

Procedure summary

•

Configuring

•

Configuring the dual-active gateways

•

Configuring Layer 3 multicast

Configuring DRNI

Configuring Device A and Device B

Device A

Device B

Description

Remarks

drni system-mac 1-1-2 drni system-mac 1-1-2 Configure the DR

system MAC

address.

You must configure

the same DR

system MAC

address for devices

in the same DR

system.

drni system-number 1 drni system-number 2 Set the DR system

number.

You must set

different DR system

numbers for

devices in the same

DR system.

drni system-priority 122 drni system-priority 122 Set the DR system

priority.

You must set the

same DR system

priority for devices

in the same DR

system.

drni standalone enable drni standalone enable Enable DRNI

standalone mode. N/A

drni

keepalive ip destination

221.1.2.2 source 221.1.2.1 drni

keepalive ip destination

221.1.2.1 source 221.1.2.2

Configure the

destination and

source IP addresses

of keepalive

packets.

N/A

interface

Twenty-FiveGigE1/0/11 interface

Twenty-FiveGigE1/0/11

Enter the view of the

interface used for

setting up the

keepalive link.

N/A

port link-mode route port link-mode route

Configure the

keepalive link

interface to operate

in route mode as a

Layer 3 interface.

N/A

ip address 221.1.2.1 24 ip address 221.1.2.2 24

Assign an IP

N/A

5

address to the

keepalive link

interface.

quit quit

Return to system

view. N/A

drni

mad exclude interface

Twenty-FiveGigE1/0/11 drni

mad exclude interface

Twenty-FiveGigE1/0/11

Exclude the

interface used for

DR keepalive

detection from the

shutdown action by

DRNI MAD.

N/A

interface HundredGigE1/0/28 interface HundredGigE1/0/28

Enter Ethernet

interface view. N/A

port link-mode route port link-mode route

Configure the

Ethernet interface to

operate in route

mode as a Layer 3

interface.

N/A

ip address 11.2.1.2/24 ip address 11.3.1.2/24

Assign an IP

address to the

interface. N/A

quit quit

Return to system

view. N/A

interface HundredGigE1/0/29 interface HundredGigE1/0/29

Enter Ethernet

interface view. N/A

port link-mode route port link-mode route

Configure the

Ethernet interface to

operate in route

mode as a Layer 3

interface.

N/A

ip address 12.2.1.2/24 ip address 12.3.1.2/24

Assign an IP

address to the

interface. N/A

quit quit

Return to system

view. N/A

drni

mad exclude interface

HundredGigE1/0/28 drni

mad exclude interface

HundredGigE1/0/28

Exclude an

interface-

facing a

peer DR system

from the shutdown

action by DRNI

MAD.

N/A

drni

mad exclude interface

HundredGigE1/0/29 drni

mad exclude interface

HundredGigE1/0/29

Exclude an

interface-

facing a

peer DR system

from the shutdown

action by DRNI

MAD.

N/A

interface bridge-aggregation

1000 interface bridge-aggregation

1000

Create the Lay

er 2

aggregate interface

to be used as the

IPP and enter Layer

2 aggregate

interface view.

N/A

quit quit

Return to system

view. N/A

6

Interface HundredGigE

1/0/26 interface HundredGigE

1/0/26

Enter the view of a

physical interface

used for setting up

the IPL.

N/A

port link-

aggregation group

1000 port link-

aggregation group

1000

Assign the physical

interface to the

aggregation group

of the IPL.

N/A

quit quit

Return to system

view. N/A

interface bridge-aggregation

1000 interface bridge-aggregation

1000

Enter the view of the

aggregation group

for the IPL. N/A

undo mac-

address static

source-check enable undo mac-

address static

source-check enable

Disable source MAC

check on the

interface. N/A

link-

aggregation mode

dynamic link-

aggregation mode

dynamic

Configure the IPL

aggregate interface

to operate in

dynamic mode.

N/A

port drni intra-portal-port 1 port drni intra-portal-port 1

Specify the

aggregate interface

as the IPP. N/A

quit quit

Return to system

view. N/A

interface bridge-aggregation

1 interface bridge-aggregation

1

Create an

aggregate interface. N/A

link-

aggregation mode

dynamic link-

aggregation mode

dynamic

Configure the

aggregate interface

to operate in

dynamic mode.

N/A

port drni group 1 port drni group 1

Assign the

aggregate interface

to DR group 1. N/A

quit quit

Return to system

view. N/A

interface HundredGigE1/0/30 interface HundredGigE1/0/30

Enter Ethernet

interface view. N/A

port link-aggregation group 1 port link-aggregation group 1

Assign the interface

to the aggregation

group of

a DR

interface.

N/A

quit quit

Return to system

view. N/A

Configuring Device C and Device D

Device C

Device D

Description

Remarks

drni system-mac 1-1-1 drni system-mac 1-1-1 Configure the DR

system MAC

address.

You must configure

the same DR

system MAC

address for

devices in the

7

same DR system.

drni system-number 1 drni system-number 2 Set the DR system

number.

You must set

different DR

system numbers

for devices in the

same DR system.

drni system-priority 121 drni system-priority 121 Set the DR system

priority.

You must set the

same DR system

priority for devices

in the same DR

system.

drni standalone enable drni standalone enable Enable DRNI

standalone mode. N/A

drni keepalive ip destination

220.1.1.2 source 220.1.1.1 drni keepalive ip destination

220.1.1.1 source 220.1.1.2

Configure the

destination and

source IP addresses

of keepalive

packets.

N/A

interface HundredGigE1/0/6 interface HundredGigE1/0/6

Enter the view of the

interface used for

setting up the

keepalive link.

N/A

port link-mode route port link-mode route

Configure the

keepalive link

interface to operate

in route mode as a

Layer 3 interface.

N/A

ip address 220.1.1.1 24 ip address 220.1.1.2 24

Assign an IP

address to the

keepalive link

interface.

N/A

quit quit

Return to system

view. N/A

drni

mad exclude interface

HundredGigE1/0/6 drni

mad exclude interface

HundredGigE1/0/6

Exclude the

interface used for

DR keepalive

detection from the

shutdown action by

DRNI MAD.

N/A

interface HundredGigE1/0/4 interface HundredGigE1/0/4

Enter Ethernet

interface view. N/A

port link-mode route port link-mode route

Configure the

Ethernet interface to

operate in route

mode as a Layer 3

interface.

N/A

ip address 11.2.1.1/24 ip address 11.3.1.1/24

Assign an IP

address to the

interface. N/A

quit quit

Return to system

view. N/A

interface HundredGigE1/0/5 interface HundredGigE1/0/5

Enter Ethernet

interface view. N/A

port link-mode route port link-mode route

Configure the

N/A

8

Ethernet interface to

operate in route

mode as a Layer 3

interface.

ip address 12.2.1.1/24 ip address 12.3.1.1/24

Assign an IP

address to the

interface. N/A

quit quit

Return to system

view. N/A

drni

mad exclude interface

HundredGigE1/0/4 drni

mad exclude interface

HundredGigE1/0/4

Exclude an

interface-

facing a

peer DR system

from the shutdown

action by DRNI

MAD.

N/A

drni

mad exclude interface

HundredGigE1/0/5 drni

mad exclude interface

HundredGigE1/0/5

Exclude an

interface-

facing a

peer DR system

from the shutdown

action by DRNI

MAD.

N/A

interface bridge-aggregation

1000 interface bridge-aggregation

1000

Create the Layer 2

aggregate interface

to be used as the

IPP and enter Layer

2 aggregate

interface view.

N/A

quit quit

Return to system

view. N/A

Interface HundredGigE 1/0/8 interface HundredGigE 1/0/8

Enter the view of a

physical interface

used for setting up

the IPL.

N/A

port link-

aggregation group

1000 port link-

aggregation group

1000

Assign the physical

interface to the

aggregation group

of the IPL.

N/A

quit quit

Return to system

view. N/A

interface bridge-aggregation

1000 interface bridge-aggregation

1000

Enter the view of the

aggregation group

for the IPL. N/A

undo mac-address static

source-check enable undo mac-

address static

source-check enable

Disable source MAC

check on the

interface. N/A

link-

aggregation mode

dynamic link-

aggregation mode

dynamic

Configure the IPL

aggregate interface

to operate in

dynamic mode.

N/A

port drni intra-portal-port 1 port drni intra-portal-port 1 Configure the

aggregate interface

as the IPP. N/A

quit quit

Return to system

view. N/A

9

interface bridge-aggregation

1 interface bridge-aggregation

1 Create an aggregate

interface. N/A

link-

aggregation mode

dynamic link-

aggregation mode

dynamic

Configure the

aggregate interface

to operate in

dynamic mode.

N/A

port drni group 1 port drni group 1

Assign the

aggregate interface

to DR group 1. N/A

quit quit

Return to system

view. N/A

interface HundredGigE 1/0/7 interface HundredGigE 1/0/7

Enter Ethernet

interface view. N/A

port link-aggregation group 1 port link-aggregation group 1

Assign the interface

to the aggregation

group of

a DR

interface.

N/A

quit quit

Return to system

view. N/A

Configuring the dual-active gateways

Configuring Device A and Device B

Device A

Device B

Description

vlan 20 vlan 20 Create VLAN 20.

interface bridge-aggregation 1 interface bridge-aggregation 1 Enter aggregate interface view.

port link-type trunk port link-type trunk

Set the link type of the Layer 2

aggregate interface to trunk.

port trunk permit vlan 20 port trunk permit vlan 20 Assign the interface to VLAN 20.

undo port trunk permit vlan 1 undo port trunk permit vlan 1 Remove the interface from VLAN

1.

quit quit Return to system view.

interface vlan-interface 20 interface vlan-interface 20 Create VLAN-interface 20.

ip address 20.1.1.1 255.255.255.0 ip address 20.1.1.1 255.255.255.0

Assign an IPv4 address to

VLAN-interface 20.

mac-address 0020-0020-0020 mac-address 0020-0020-0020

Assign a MAC address to

VLAN-interface 20.

quit quit Return to system view.

drni

mad exclude interface

Vlan-interface20 drni

mad exclude interface

Vlan-interface20

Exclude VLAN-interface 20 from

the shutdown action by DRNI

MAD.

vlan 21 - Create VLAN 21.

interface Twenty-FiveGigE1/0/1 - Enter Ethernet interface view.

port link-type trunk - Set the link type of the interface

to trunk.

port trunk permit vlan 21 - Assign the interface to VLAN 21.

10

Device A

Device B

Description

undo port trunk permit vlan 1 - Remove the interface from VLAN

1.

quit - Return to system view.

interface vlan-interface 21 - Create VLAN-interface 21.

ip address 21.1.1.1 255.255.255.0 -

Assign an IPv4 address to

VLAN-interface 21.

mac-address 0020-0020-0021 -

Assign a MAC address to

VLAN-interface 21.

quit - Return to system view.

drni

mad exclude interface

Vlan-interface21 - Exclude VLAN-interface 21 from

the shutdown action by DRNI

MAD.

Configuring Device C and Device D

Device C

Device D

Description

vlan 10 vlan 10 Create VLAN 10.

interface bridge-aggregation 1 interface bridge-aggregation 1 Enter aggregate interface view.

port link-type trunk port link-type trunk

Set the link type of the Layer 2

aggregate interface to trunk.

port trunk permit vlan 10 port trunk permit vlan 10 Assign the interface to VLAN 10.

undo port trunk permit vlan 1 undo port trunk permit vlan 1 Remove the interface from VLAN 1.

quit quit Return to system view.

interface vlan-interface 10 interface vlan-interface 10 Create VLAN-interface 10.

ip address 10.1.1.1

255.255.255.0 ip address 10.1.1.1

255.255.255.0

Assign an IPv4 address to

VLAN-interface 10.

mac-address 0010-0010-0010 mac-address 0010-0010-0010 Assig

n a MAC address to

VLAN-interface 10.

quit quit Return to system view.

drni

mad exclude interface

Vlan-interface10 drni

mad exclude interface

Vlan-interface10 Exclude VLAN-interface 10 from the

shutdown action by DRNI MAD.

Configuring Layer 3 multicast

Configuring Device A and Device B

Device A

Device B

Description

multicast routing multicast routing Enable IP multicast routing.

igmp-snooping igmp-snooping Enable IGMP snooping.

Vlan 20 Vlan 20 Enter VLAN view.

igmp-snooping enable igmp-snooping enable Enable IGMP snooping in the VLAN.

interface Vlan-interface20 interface Vlan-interface20 Enable VLAN interface view.

pim sm pim sm Enable PIM SM.

11

Device A

Device B

Description

igmp enable igmp enable Enable IGMP.

pim distributed-dr pim distributed-dr Configure

the interface as a DR

interface to forward multicast traffic.

quit quit Return to the upper-level view.

interface Vlan-interface21 - Enable VLAN interface view.

pim sm - Enable PIM SM.

igmp enable - Enable IGMP.

quit - Return to the upper-level view.

interface HundredGigE1/0/28 interface HundredGigE1/0/28 Enter Ethernet interface view.

pim sm pim sm Enable PIM SM.

quit quit Return to the upper-level view.

interface HundredGigE1/0/29 interface HundredGigE1/0/29 Enter Ethernet interface view.

pim sm pim sm Enable PIM SM.

quit quit Return to the upper-level view.

interface LoopBack0 interface LoopBack0 Enter loopback interface view.

pim sm pim sm Enable PIM SM.

quit quit Return to the upper-level view.

interface

Twenty-FiveGigE1/0/11 interface

Twenty-FiveGigE1/0/11 Enter Ethernet interface view.

pim sm pim sm Enable PIM SM.

quit quit Return to the upper-level view.

pim pim Enter PIM view.

static-rp 4.4.4.4 static-rp 4.4.4.4 Configure a static RP.

Configuring Device C and Device D

Device C

Device D

Description

multicast routing multicast routing Enable IP multicast routing.

igmp-snooping igmp-snooping Enable IGMP snooping.

Vlan 10 Vlan 10 Enter VLAN view.

igmp-snooping enable igmp-snooping enable Enable IGMP snooping in the VLAN.

quit quit Return to the upper-level view.

interface Vlan-interface10 interface Vlan-interface10 Enable VLAN interface view.

pim sm pim sm Enable PIM SM.

pim distributed-dr pim distributed-dr

Configure the interface as a DR

interface to forward multicast traffic.

quit quit Return to the upper-level view.

interface HundredGigE1/0/4 interface HundredGigE1/0/4 Enter Ethernet interface view.

pim sm pim sm Enable PIM SM.

12

Device C

Device D

Description

quit quit Return to the upper-level view.

interface HundredGigE1/0/5 interface HundredGigE1/0/5 Enter Ethernet interface view.

pim sm pim sm Enable PIM SM.

quit quit Return to the upper-level view.

interface LoopBack0 interface LoopBack0 Enter loopback interface view.

pim sm pim sm Enable PIM SM.

quit quit Return to the upper-level view.

interface HundredGigE1/0/6 interface HundredGigE1/0/6 Enter Ethernet interface view.

pim sm pim sm Enable PIM SM.

quit quit Return to the upper-level view.

pim pim Enter PIM view.

static-rp 4.4.4.4 static-rp 4.4.4.4 Configure a static RP.

Traffic forwarding models

Underlay traffic characteristics

The forwarding model matrix provides the following characteristics of underlay traffic:

•

No.—Traffic number in the U-X-XXX format:

 U—Underlay traffic.

 X—Protocol number, which can be 4 (IPv4)

 XXX—Traffic sequence number.

•

Traffic type—Type of underlay traffic, which can only be IPv4 known multicast

•

Direction—Direction of underlay traffic. The value is south-north, which indicates traffic from

the south to north.

•

Forwarding path—Nodes that underlay traffic traverses.

•

Traffic simulation—Traffic simulation method. Typically, a tester is used to simulate server

traffic.

•

Load—Traffic size, which can be light (less than 1000 flows) and heavy (more than 1000 flows).

•

Traffic direction to firewalls/LB—No firewalls or LBs are used in this example. This field is not

involved.

Forwarding models

No. Traffic type Direction Forwarding path Traffic

simulation Load

Traffic

direction

to

firewalls/

LB

U-4-10

1

IPv4 known

multicast South-north 100 multicast groups

Source >

Device C and

Device D > Device A and

Tester Light N/A

13

Device B > Receiver 2

U-4-10

2

IPv4 known

mutlicsat South-north

100 multicast groups

Source >

Device C and

Device D > Device A and

Device B > Receiver 1

Tester Light N/A

Testing network convergence upon single points

of failure

Table 1 Network convergence upon single points of failure

Device Failure type Traffic interruption time

(U-4-101/U-4-102)

DRNI

Multicast source-

side single point of

failure on DR member links ≤ 100 ms

Multicast source-

side single point of

failure restored on DR member links ≤ 100 ms

Multicast source-side IPL failure ≤ 500 ms

Multicast source-side IPL failure

restored ≤ 100 ms

Multicast source-side k

eepalive link

failure 0 ms

Multicast source-side k

eepalive link

failure restored 0 ms

Multicast source-side keepalive link and

IPL failure ≤ 500 ms

Multicast source-side keepalive link and

IPL failure restored ≤ 500 ms

Single ECMP link failure between the

DR systems ≤ 500 ms/1000 ms

Single ECMP link restored between the

DR systems ≤ 100 ms

Multicast-receiver side s

ingle point of

failure on DR member links ≤ 100 ms/0 ms

Multicast-receiver side s

ingle point of

failure restored on DR member links ≤ 100 ms/0 ms

Multicast-receiver side IPL failure ≤ 100 ms/0 ms

Multicast-receiver side IPL failure

restored ≤ 100 ms/0 ms

Multicast-receiver side k

eepalive link

failure 0 ms

Multicast-receiver side k

eepalive link

failure restored 0 ms

Multicast-receiver side k

eepalive link

and IPL failure ≤ 500 ms/0 ms

Multicast-receiver side keepalive link

≤ 500 ms/0 ms

14

Device Failure type Traffic interruption time

(U-4-101/U-4-102)

and IPL restored

Upgrade ≤ 10000 ms (upgrade the DR member devices

one after another)

Hardware replacement Fixed-port device replacement: ≤ 10000 ms

Verifying the configuration

Verifying the status of the DR system

Verify that the DR system is working correctly on Device A and Device B. Use Device A as an

example. The verification procedure is the same for Device B, Device C, and Device D.

# Display summary information about the IPP and DR interface.

[Device A]display drni summary

Flags: A -- Aggregate interface down, B -- No peer DR interface configured

C -- Configuration consistency check failed

IPP: BAGG1000

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 -

# Verify that keepalive link is working correctly.

[Device A]display drni keepalive

Neighbor keepalive link status (cause): Up

Neighbor is alive for: 256 s 620 ms

Keepalive packet transmission status:

Sent: Successful

Received: Successful

Last received keepalive packet information:

Source IP address: 221.1.2.2

Time: 2023/06/13 05:00:51

Action: Accept

DR keepalive parameters:

Destination IP address: 221.1.2.2

Source IP address: 221.1.2.1

Keepalive UDP port : 6400

Keepalive VPN name : N/A

Keepalive interval : 1000 ms

Keepalive timeout : 5 sec

Keepalive hold time: 3 sec

# Display the DR system information.

15

[Device A]display drni system

System information

Local system number: 1 Peer system number: 2

Local system MAC: 0001-0001-0002 Peer system MAC: 0001-0001-0002

Local system priority: 122 Peer system priority: 122

Local bridge MAC: dcda-8037-2bc0 Peer bridge MAC: bc22-4720-d5b9

Local effective role: Secondary Peer effective role: Primary

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 60 -

Consistency-check delay Disabled 30 -

Standalone delay Disabled 0 -

Role to None delay Disabled 60 -

# Display detailed information about the IPP and DR interfaces.

[Device A]display drni verbose

Flags: A -- Home_Gateway, B -- Neighbor_Gateway, C -- Other_Gateway,

D -- IPP_Activity, E -- DRCP_Timeout, F -- Gateway_Sync,

G -- Port_Sync, H -- Expired

IPP/IPP ID: BAGG1000/1

State: UP

Cause: -

Local DRCP flags/Peer DRCP flags: ABDFG/ABDFG

Local Selected ports (index): HGE1/0/26 (30)

Peer Selected ports indexes: 225

DR interface/DR group ID: BAGG1/1

Local DR interface state: UP

Peer DR interface state: UP

DR group state: UP

Local DR interface down cause: -

Remaining DRNI DOWN time: -

Local DR interface LACP MAC: Config=N/A, Effective=0001-0001-0002

Peer DR interface LACP MAC: Config=N/A, Effective=0001-0001-0002

Local DR interface LACP priority: Config=32768, Effective=122

Peer DR interface LACP priority: Config=32768, Effective=122

Local DRCP flags/Peer DRCP flags: ABDFG/ABDFG

Local Selected ports (index): HGE1/0/30 (50)

Peer Selected ports indexes: 245

Verifying multicast forwarding information

# Verify that PIM neighbor relationships are established correctly.

16

[Device A]display pim neighbor

Total Number of Neighbors = 3

Neighbor Interface Uptime Expires DR-Priority Mode

221.1.2.2 WGE1/0/11 00:06:12 00:01:37 1 P

11.2.1.1 HGE1/0/28 2d:00h 00:01:44 1 P

12.2.1.1 HGE1/0/29 00:15:52 00:01:44 1 P

[Device B]display pim neighbor

Total Number of Neighbors = 3

Neighbor Interface Uptime Expires DR-Priority Mode

221.1.2.1 WGE1/0/11 00:06:40 00:01:35 1 P

11.3.1.1 HGE1/0/28 2d:00h 00:01:44 1 P

12.3.1.1 HGE1/0/29 2d:00h 00:01:32 1 P

[Device C]display pim neighbor

Total Number of Neighbors = 3

Neighbor Interface Uptime Expires DR-Priority Mode

11.2.1.2 HGE1/0/4 2d:00h 00:01:42 1 P

11.3.1.2 HGE1/0/5 2d:00h 00:01:27 1 P

220.1.1.2 HGE1/0/6 00:19:34 00:01:37 1 P

[Device D]display pim neighbor

Total Number of Neighbors = 3

Neighbor Interface Uptime Expires DR-Priority Mode

12.2.1.2 HGE1/0/4 00:16:32 00:01:26 1 P

12.3.1.2 HGE1/0/5 2d:00h 00:01:20 1 P

220.1.1.1 HGE1/0/6 00:19:38 00:01:26 1 P

# Verify that multicast forwarding entries are created correctly.

[Device A]dis igmp group

IGMP groups in total: 200

Vlan-interface20(20.1.1.1):

IGMP groups reported in total: 100

Group address Last reporter Uptime Expires

225.0.0.1 20.1.1.2 00:07:34 00:03:04

225.0.0.2 20.1.1.2 00:07:26 00:03:03

225.0.0.3 20.1.1.2 00:07:30 00:03:07

225.0.0.98 20.1.1.2 00:07:28 00:03:07

225.0.0.99 20.1.1.2 00:07:27 00:03:10

225.0.0.100 20.1.1.2 00:07:26 00:03:06

Vlan-interface21(21.1.1.1):

IGMP groups reported in total: 100

Group address Last reporter Uptime Expires

226.0.0.1 21.1.1.2 00:32:50 00:04:17

226.0.0.2 21.1.1.2 00:32:50 00:02:12

226.0.0.3 21.1.1.2 00:32:50 00:02:12

17

226.0.0.98 21.1.1.2 00:32:50 00:04:15

226.0.0.99 21.1.1.2 00:32:50 00:04:18

226.0.0.100 21.1.1.2 00:32:50 00:02:11

# Verify that PIM routing entries are created correctly.

[Device A]dis pim routing-table

Total 200 (*, G) entries; 200 (S, G) entries

(*, 225.0.0.1)

RP: 4.4.4.4

Protocol: pim-sm, Flag: WC

UpTime: 00:08:57

Upstream interface: HundredGigE1/0/29

Upstream neighbor: 12.2.1.1

RPF prime neighbor: 12.2.1.1

Downstream interface information:

Total number of downstream interfaces: 1

1: Vlan-interface20

Protocol: igmp, UpTime: 00:08:57, Expires: -

(10.1.1.2, 225.0.0.1)

RP: 4.4.4.4

Protocol: pim-sm, Flag: SPT ACT 2MVPN

UpTime: 00:41:07

Upstream interface: HundredGigE1/0/29

Upstream neighbor: 12.2.1.1

RPF prime neighbor: 12.2.1.1

Downstream interface information:

Total number of downstream interfaces: 1

1: Vlan-interface20

Protocol: pim-sm, UpTime: 00:08:57, Expires: -

(*, 226.0.0.1)

RP: 4.4.4.4

Protocol: pim-sm, Flag: WC

UpTime: 00:34:27

Upstream interface: HundredGigE1/0/29

Upstream neighbor: 12.2.1.1

RPF prime neighbor: 12.2.1.1

Downstream interface information:

Total number of downstream interfaces: 1

1: Vlan-interface21

Protocol: igmp, UpTime: 00:34:27, Expires: -

(10.1.1.2, 226.0.0.1)

RP: 4.4.4.4

Protocol: pim-sm, Flag: SPT ACT 2MVPN

UpTime: 00:37:01

Upstream interface: HundredGigE1/0/29

18

Upstream neighbor: 12.2.1.1

RPF prime neighbor: 12.2.1.1

Downstream interface information:

Total number of downstream interfaces: 1

1: Vlan-interface21

Protocol: pim-sm, UpTime: 00:34:27, Expires: -

[Device B]display pim routing-table

Total 200 (*, G) entries; 201 (S, G) entries

(*, 225.0.0.1)

RP: 4.4.4.4 (local)

Protocol: pim-sm, Flag: WC

UpTime: 00:15:09

Upstream interface: Register-Tunnel0

Upstream neighbor: NULL

RPF prime neighbor: NULL

Downstream interface information:

Total number of downstream interfaces: 2

1: HundredGigE1/0/29

Protocol: pim-sm, UpTime: 00:10:02, Expires: 00:03:28

2: Vlan-interface20

Protocol: igmp, UpTime: 00:15:09, Expires: -

(10.1.1.2, 225.0.0.1)

RP: 4.4.4.4 (local)

Protocol: pim-sm, Flag: SPT 2MSDP ACT 2MVPN

UpTime: 00:44:11

Upstream interface: HundredGigE1/0/29

Upstream neighbor: 12.3.1.1

RPF prime neighbor: 12.3.1.1

Downstream interface information:

Total number of downstream interfaces: 1

1: Vlan-interface20

Protocol: pim-sm, UpTime: 00:15:09, Expires: -

(*, 226.0.0.1)

RP: 4.4.4.4 (local)

Protocol: pim-sm, Flag: WC

UpTime: 00:23:10

Upstream interface: Register-Tunnel0

Upstream neighbor: NULL

RPF prime neighbor: NULL

Downstream interface information:

Total number of downstream interfaces: 1

1: HundredGigE1/0/29

Protocol: pim-sm, UpTime: 00:20:31, Expires: 00:02:58

19

(10.1.1.2, 226.0.0.1)

RP: 4.4.4.4 (local)

Protocol: pim-sm, Flag: RPT 2MSDP ACT 2MVPN

UpTime: 00:45:34

Upstream interface: Register-Tunnel0

Upstream neighbor: NULL

RPF prime neighbor: NULL

Downstream interface information: None

Upgrading the devices

Checking the environment

Execute the commands in "Verifying the configuration" and the following commands to verify that the

devices are available for an upgrade.

DRNI 1

DRNI 2

Description

display device

Displays device information.

display boot-loader display boot-loader Displays current software images and

startup software images.

display version

Displays system version information.

Upgrading the devices

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.

 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

See "Testing network convergence upon single points of failure."

Verifying the upgrade result

Execute the commands in "Verifying the configuration" and the following commands to verify that the

device is upgraded successfully.

20

DRNI 1

DRNI 2

Description

display device

Displays device information.

display boot-loader display boot-loader Displays current software images and

startup software images.

display version

Displays system version information.

Replacing hardware

Replacing a service module

Checking the environment

Execute the commands in "Verifying the configuration" and the following commands to verify that the

device is available for a replacement.

DRNI 1

DRNI 2

Description

display device

Displays device information.

display boot-loader display boot-loader Displays current software images and

startup software images.

display version

Displays system version information.

Replacing hardware

Switch service and management traffic on the target service module to other service modules.

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 upon single points of failure."

Verifying the replacement result

Execute the commands in "Checking the environment."

Replacing a switching fabric module

Checking the environment

Execute the commands in "Verifying the configuration" and the following commands to verify that the

device is available for a replacement.

DRNI 1

DRNI 2

Description

display device

Displays device information.

display boot-loader display boot-loader Displays current software images and

startup software images.

display version

Displays system version information.

Page is loading ...

Aruba Cascaded DRNI Systems Configuration Guide

Aruba Cascaded DRNI Systems Configuration Guide

Related papers

Other documents