LAB GUIDE

Campus Switching
Fundamentals
CX SWITCHING WORKSHOP
OBJECTIVE
At the end of this workshop, you will be able to implement and troubleshoot the fundamental technologies of a campus
switching infrastructure based on Aruba CX Switches, including VSF and VSX.

AOS-CX RELEASE 10.7

This lab guide requires AOS-CX 10.7.04 or later.

OVERVIEW
Lab Network Layout
This workshop is a lab activity that will allow you to implement the different components of the scenario described above,
including:

• Setup a CX 6300 VSF stack

• Configuring some fundamental access port features
• Implement a VSX high availability aggregation node composed of a pair of CX 8325 switches

Figure 1. Lab Layout

1
(*) IMPORTANT

• The port numbers of the 6300-B switch will change from 1/1/x to 2/1/x at the end of the VSF stack setup.
• Both 8325 switches have 48 25GbE SFP28 ports, however, all inter-switch connections are 10 GbE SFP+ DAC cables. To
enable these cables/transceivers, the speed on the ports will have to be changed to 10Gbps. On the 6300 switches, this
step is not necessary as they recognize SFP56, SFP28, and SFP+ automatically.

CONNECTING TO THE LAB ENVIRONMENT

To access the lab environment, go to 10and use the credentials provided by the instructor.

Note: if you are not using a US keyboard, use the “Keyboard” option to select the appropriate configuration.

Logging in will open a remote desktop session to the Win 10 client (see Figure 2).

This VM has four Ethernet adapters:

Adapter Name Purpose

DO NOT MODIFY This is the NIC that provides you RDP connection to the Win 10 Client

IMPORTANT: do not modify it!

2930 Not used in this lab

3810-OOBM Connection to the out-of-band network. It gives you access to:

• Each switch’s management port

• NetEdit Server
6300 Connection to port 1/1/1 on the 6300-A switch. You will use this interface to test
connectivity in the PREPARE the WINDOWS CLIENT section of the activity.

Once logged in open MTPuTTY or PuTTY open the console of the following devices: 6300-A, 6300-B, 8325-A and 8325-B.

Note: if while opening MTPuTTY you are prompted for the location of PuTTY, find it here: C:\Program Files\PuTTY

2
Exiting the lab environment
If at any point you need to close the session: Click on the X button located at the bottom on the left margin menu

These steps will guarantee that next time you connect you will be able to access the lab environment without difficulty.

INITIAL CONFIGURATION
All switches are preconfigured with the following parameters and states:

• Username: admin Password: admin

• CLI session expiration: disabled
• Management interface:
o Enabled
o IP Address: static in subnet 10.251.n.0 (where n is the User number)
o SSH Server and HTTPS server: enabled on the management VRF
o REST Interface: enabled in read/write mode

LAB ACTIVITY 1: SETTING UP VSF STACKING IN THE WIRING CLOSET

This activity assumes that you are familiar with the VSF technology.

To start:

• Open the consoles of the both 6300 switches

• Hit enter to get the login prompt
• Login using:
o User: admin and password: admin

Setup the VSF Stack

Figure 2. 6300 to 6300 Links

On the 6300-A console enter:

show lldp neighbor
LLDP Neighbor Information
=========================

Total Neighbor Entries : 2

Total Neighbor Entries Deleted : 0
Total Neighbor Entries Dropped : 0
Total Neighbor Entries Aged-Out : 0

LOCAL-PORT CHASSIS-ID PORT-ID PORT-DESC TTL SYS-NAME

-----------------------------------------------------------------------------------------------------------
1/1/25 88:3a:30:92:d5:00 1/1/26 1/1/26 120 PN2-6300-B
1/1/26 88:3a:30:92:c4:00 1/1/25 1/1/25 120 PN2-6300-B
mgmt 1c:98:ec:9e:6b:45 10 1/10 120 3810-Stk-OOBM

and verify that the connection is between the ports shown in figure 2.

The VSF auto-stacking process will be triggered by entering the CLI command on the 6300-A (the one with the largest VSF link-
candidate port number). However, VSF auto-stacking:
o requires that both switches are in default configuration
o however, as you have seen, they have an initial configuration
o the way to overcome this issue is different on the 6300-A and the 6300-B
o you will start by preparing the 6300-B to receive the VSF join message

3
On the 6300-B
• In the next steps you will
o Verify that the 6300-B is not eligible for VSF auto-join (it has a non-default configuration)
o Force eligibility
o Verify the change
Note: lines that start with “!” are comments in the CLI scripts and do not need to be entered in the console.
show vsf
Force Autojoin : Disabled
Autojoin Eligibility Status: Not Eligible
MAC Address : 88:3a:30:92:d5:00
Secondary :
Topology : Standalone
Status : No Split
Split Detection Method : None

Mbr Mac Address type Status

ID
--- ------------------- -------------- ---------------
1 88:3a:30:92:d5:00 JL668A Master
!
! force VSF auto-join
!
configure
vsf force-auto-join
!
! verify the change
!
show vsf
Force Autojoin : Enabled
Autojoin Eligibility Status: Eligible
MAC Address : 88:3a:30:92:d5:00
Secondary :
Topology : Standalone
Status : No Split
Split Detection Method : None

Mbr Mac Address type Status

ID
--- ------------------- -------------- ---------------
1 88:3a:30:92:d5:00 JL668A Master

Now the 6300-B is ready to join the stack when it receives the command from the 6300-A through its port 1/1/25.

On the 6300-A

The switch on which you will start the VSF process must be reset to the default configuration. Take the following steps:
!
! erase all non-VSF configurations
!
erase startup-config
!
! answer y at the prompt: Erase checkpoint startup-config?
!
! and reboot the switch
!
boot system primary
!
! at the following prompt
!

4
 ! Default boot image set to primary.
! Checking if the configuration needs to be saved...
! Do you want to save the current configuration (y/n)?
! answer n
!
! and then at the prompt
! This will reboot the entire switch and render it unavailable
! until the process is complete.
! Continue (y/n)?
! answer y
!
When the 6300-A completes the reboot process, you will notice that its prompt has changed to the default. Login using the
default credentials (username: admin, and no password). And without making any changes trigger the VSF auto-stack:
configure
vsf start-auto-stacking
!
! at the prompt answer y
!
The 6300-B will reboot and join the stack. Monitor the process by entering on the 6300-A:
end
show vsf link

VSF Member 1

Link Peer Peer

Link State Member Link Interfaces
---- ---------- ------- ------ ---------------------------
1 up 2 1 1/1/26
2 up 2 2 1/1/25

VSF Member 2

Link Peer Peer

Link State Member Link Interfaces
---- ---------- ------- ------ ---------------------------
1 up 1 1 2/1/25
2 up 1 2 2/1/26
The last command will repeat the previous one until you break the cycle with Ctrl-C (if you are using a MAC, use Command-C).

Once the stack is complete, with both switches running, complete the initial configuration:
auto-confirm
! The previous command automatically provides a “y” to any confirmation request prompt
configure
session-timeout 0
! in the next commands replace the x with your user number for consistency
user admin password
! at the prompt enter the new password admin twice
host PNx-6300-VSF
! configure the management port
interface mgmt
ip static 10.251.x.4/24
default-gateway 10.251.x.254
end
write memory

Configuring the uplink

• Configure the following elements: VLANs for the uplinks, uplink link aggregation group

5
Figure 3. VSF Stack Uplink

configure
! vlan 10 is the device management VLAN
! vlan 20 will be assigned to the Windows 10 client
! and its SVI will connect to VRF20
vlan 10
name Acc-mgmt
vlan 20
name Client-20
interface vlan 10
ip address 10.0.10.10/24
ip mtu 2048
exit
! Create a layer 2 LAG (#10) and map the VLANs and the uplink ports to it
interface lag 10
no shutdown
no routing
lacp mode active
vlan trunk allowed 10,20
exit
! use an interface range to simplify assigning ports to LAG 10
! use an L2 MTU of 2048 Bytes to accommodate for tunneling if necessary
interface 1/1/27,1/1/28,2/1/27,2/1/28
no shutdown
mtu 2048
lag 10
exit
• Add ports 1/1/1 and 2/1/1 to VLAN 20 to provide connectivity to the client
interface 1/1/1,2/1/1
! check the default configuration
show running current
! notice that factory default of the port is “no routing” and “vlan access 1”
no shutdown
vlan access 20
exit
• Add a default route pointing to 10.0.10.1 (gateway on VLAN 10)
ip route 0.0.0.0/0 10.0.10.1

• Verify that spanning tree is enabled and check the default STP mode: MSTP? RPVST+?
Notes
o As the uplink is a single LAG, STP will only be used as a loop protection mechanism running on Instance 0
show spanning-tree
• Save
end
write memory
• Validate the LAG configuration by entering the following commands and checking that LAG member port and transceivers
match
show lacp interfaces
show interface transceiver

6
 Note: the interfaces of the LAG will be all down as the LAG is not configured/enabled on the core VSX

Explore other show lacp commands

LAB ACTIVITY 2: SETTING UP VSX HIGH AVAILABILITY IN THE CORE/AGGREGATION

This activity assumes that you are familiar with the VSX technology.

Preparing the 8325 ports to support the SFP+ transceivers

• On each 8325, start by changing the port speed from 25G to 10G to enable support for the existing 10G SFP+
transceivers/DACs.
Note: these 8325 models (JL635A) have 48 25GbE SFP28 ports divided into 4 interface-groups of 12 ports each. To adjust
their speed, a whole group must be configured, in other words, all ports in an interface-group will operate at the same
speed.
A similar configuration must be used on the 8400 25GbE modules to support 10GbE transceivers.
!
! verify speed mismatch – by entering:
show interface brief
! and identifying those ports that report:
! 1/1/xx -- routed SFP+DAC1 no down Group speed mismatch --
!
auto-confirm
configure
! Disable the console session timeout
session-timeout 0
system interface-group 1 speed 10g
system interface-group 4 speed 10g
• Display the interfaces again and verify that those ports are shown now as Administratively down instead of Group
speed mismatch

Setting up the VSX infrastructure

Figure 4. 8325 to 8325 links

• Repeat the link validation process used on the 6300s to verify that your 8325s are connected according to Figure 2. Use
the show interface transceiver command. If necessary, change the port numbers use throughout this activity.
On both 8325 switches:

• Create VLANs 10 and 20 – Setup vsx-sync on these vlans

• Setup LAG 256 for the VSX Inter-Switch Link (ISL) – use port 1/1/46 for this purpose
Notes
o The IP interfaces for these VLANs will be configured later to include the Active Gateway. At that same time, OSPF will be
setup.
o This LAG will consist of a single physical link, but, following best practices, will be ready for future expansion
configure
vlan 10
name Acc-mgmt
vsx-sync
vlan 20
name Client-20
vsx-sync
interface lag 256
no shutdown

7
 no routing
lacp mode active
vlan trunk allowed all
! use the “show run current” command to validate the LAG configuration
! Note: use the full word show
interface 1/1/46
no shutdown
mtu 2048
lag 256
end
write memory
• Create an L3 link for the VSX Keepalive using port 1/1/47. Place it in VRF KA.
Important: the keepalive only requires Layer 3 connectivity. In this case, a direct L3 link is used for this purpose. It is placed
in a dedicated VRF to isolate it from any routing issues. Notice that if the VSX pair is connected via L3 links to a core, the
keepalive can be configured using the Loopback addresses.

Note: use the following IP addresses

o 8325-A: 172.16.1.1/30
o 8325-B: 172.16.1.2/30
configure
vrf KA
exit
interface 1/1/47
no shutdown
vrf attach KA
ip address <see note above>
end
! after configuring interface 1/1/47 on both switches validate from the 8325-A
console
ping 172.16.1.2 vrf KA
! save
write memory
• Configure VSX base parameters
Include a system-MAC for LACP stability
Note: use the following VSX roles
o 8325-A: primary
o 8325-B: secondary
configure
vsx
system-mac 02:00:00:00:10:01
role <see note above>
inter-switch-link lag 256
!
! configure the keepalive on the primary/8325-A –
! DO NOT forget to include the VRF parameter
keepalive peer 172.16.1.2 source 172.16.1.1 vrf KA
!
! configure the keepalive on the secondary/8325-B
keepalive peer 172.16.1.1 source 172.16.1.2 vrf KA
• While in the VSX context, explore the VSX-Sync options and configure some of them
vsx-sync ?
! on the 8325-A configure vsx-sync for
! vsx-global commands, stp enablement, mclag interfaces and OSPF
vsx-sync vsx-global stp-global mclag-interfaces ospf
! on the 8325-B run the “show running current” command

8
 ! and verify that this last command has been synchronized (copied)
!
! verify the VSX infrastructure by running the following show commands:
!
show vsx brief
show vsx status
show vsx lacp configuration
show vsx config-consistency
! explore other show vsx commands
! save
end
write memory
Create the VSX LAG downlink (to the 6300 VSF Stack)

Figure 5. VSX Downlink

On both 8325 switches: create LAG 10

configure
interface lag 10 multi-chassis
no shutdown
vlan trunk allowed 10,20
! validate configuration and check the defaults
show running current
! notice that by default a “multi-chassis” LAG is a layer 2 interface
! and LACP is in active mode
exit
• Add the ports
interface 1/1/1,1/1/2
no shutdown
mtu 2048
lag 10
exit
• Verify the status of VSX and the multi-chassis LAG. Run the following commands
show vsx lacp aggregates lag10
show lacp interfaces
• Notice the Port IDs in the Partner Details (2nd) table. How are the ports of the VSF secondary numbered?
• On the 8325-A ONLY enable MSTP as a loop protection mechanism (MST 0 only) with a low priority to ensure the VSX pair
is the root
spanning-tree priority 2
spanning-tree
end
write memory
• Verify the STP state – on the 8325-A and 8325-B
show spanning-tree
Notice:

VSX-Sync copied the Spanning Tree priority from the primary to the secondary and enabled it on the secondary

9
 o STP is using the VSX system MAC as the bridge ID
o The VSX pair is the root
o LAG 256 (the ISL) has the lowest cost possible
MAC-Address: 02:00:00:00:10:01
This bridge is the root
• Confirm by running the same command (show spanning-tree) on the 6300 stack and check the root’s Bridge ID, and
notice that LAG 10 is a root port
On the 6300-A (VSF Stack)

• Verify the uplink state

show lacp interfaces
• Notice the Port IDs in the Partner Details (2nd) table. How are the ports of the VSX secondary numbered?

LAB ACTIVITY 3: CONNECT THE CORE CREATING A MULTI-VRF ENVIRONMENT

Create the LAG between the 8320-Core and 8325-Aggregation-VSX
In this part of the lab you will connect the 8320-core to the 8325-VSX pair. In this case, you will implement

VRF Default VRF20

Access VLAN 10 20
Transit VLAN 3010 3020

Figure 6. VSX Uplink

On the 8320: configure basic parameters and the LAG to the VSX pair
auto-confirm
configure
session-timeout 0
vlan 3010
name TRANSIT-VRF-DEFAULT
vlan 3020
name TRANSIT-VRF-20
!
interface lag 20
no shutdown
no routing
lacp mode active
vlan trunk allowed 3010,3020
!
interface 1/1/1,1/1/2
no shutdown
mtu 2048
lag 20
end
write memory
On both 8325 switches: create LAG 20
configure
vlan 3010
name TRANSIT-VRF-DEFAULT
vlan 3020

10
 name TRANSIT-VRF-20
!
interface lag 20 multi-chassis
no shutdown
vlan trunk allowed 3010,3020
exit
!
interface 1/1/48
no shutdown
mtu 2048
lag 20
end
write memory
• Verify the status of the Core-Aggregation LAG. On each core and aggregation switch:
show lacp interface

Enter the Layer 3 configuration on the 8325 switches

In this part of the lab you will implement the layer 3 connection between the 8320-core to the 8325-VSX pair.

On the 8320-Core

VRF Default VRF20

Transit VLAN 3010 3020
OSPF Router 1 2
OSPF 1 Router ID 10.210.1.1
Loopback 0 10.210.1.1/32
Interface VLAN 3010 10.30.10.1/24
OSPF 2 Router ID 10.220.1.1
Loopback 2 10.220.1.1/32
Interface VLAN 3020 10.30.20.1/24

!
configure
!
! VRF Default
!
router ospf 1
router-id 10.210.1.1
area 0
passive-interface default
!
interface loopback 0
ip address 10.210.1.1/32
ip ospf 1 area 0
!
interface vlan 3010
ip mtu 2048
ip address 10.30.10.1/24
ip ospf 1 area 0
no ip ospf passive
exit
!
! VRF20
!
vrf VRF20
!
router ospf 2 vrf VRF20

11
 router-id 10.220.1.1
area 0
passive-interface default
!
interface loopback 2
vrf attach VRF20
ip address 10.220.1.1/32
ip ospf 2 area 0
!
interface vlan 3020
vrf attach VRF20
ip mtu 2048
ip address 10.30.20.1/24
ip ospf 2 area 0
no ip ospf passive
end
write memory

On the 8325-A

VRF Default VRF20

Access VLAN 10 20
Transit VLAN 3010 3020
OSPF Router 1 2
OSPF 1 Router ID 10.210.2.1
Loopback 0 10.210.2.1/32
Interface VLAN 10 10.0.10.2/24
Active Gateway VLAN 10 10.0.10.1
Interface VLAN 3010 10.30.10.2/24
OSPF 2 Router ID 10.220.2.1
Loopback 2 10.220.2.1/32
Interface VLAN 20 10.0.20.2/24
Active Gateway VLAN 20 10.0.20.1
Interface VLAN 3020 10.30.20.2/24

configure
!
! VRF Default
!
router ospf 1
router-id 10.210.2.1
area 0
passive-interface default
!
interface loopback 0
ip address 10.210.2.1/32
ip ospf 1 area 0
exit
!
no ip icmp redirect
!
interface vlan 10
vsx-sync active-gateways
ip mtu 2048

12
 ip address 10.0.10.2/24
active-gateway ip mac 02:00:00:00:00:01
active-gateway ip 10.0.10.1
ip ospf 1 area 0
!
interface vlan 3010
vsx active-forwarding
ip mtu 2048
ip address 10.30.10.2/24
ip ospf 1 area 0
no ip ospf passive
!
! VRF20
!
vrf VRF20
router ospf 2 vrf VRF20
router-id 10.220.2.1
area 0
passive-interface default
!
interface loopback 2
vrf attach VRF20
ip address 10.220.2.1/32
ip ospf 2 area 0
!
interface vlan 20
vrf attach VRF20
vsx-sync active-gateways
ip mtu 2048
ip address 10.0.20.2/24
active-gateway ip mac 02:00:00:00:00:01
active-gateway ip 10.0.20.1
ip ospf 2 area 0
!
interface vlan 3020
vrf attach VRF20
vsx active-forwarding
ip mtu 2048
ip address 10.30.20.2/24
ip ospf 2 area 0
no ip ospf passive
!
end
write memory

13
On the 8325-B

VRF Default VRF20

Access VLAN 10 20
Transit VLAN 3010 3020
OSPF Router 1 2
OSPF 1 Router ID 10.210.2.2
Loopback 0 10.210.2.2/32
Interface VLAN 10 10.0.10.3/24
Active Gateway VLAN 10 sync
Interface VLAN 3010 10.30.10.3/24
OSPF 2 Router ID 10.220.2.2
Loopback 2 10.220.2.2/32
Interface VLAN 20 10.0.20.3/24
Active Gateway VLAN 20 sync
Interface VLAN 3020 10.30.20.3/24

configure
!
! VRF Default
!
router ospf 1
router-id 10.210.2.2
area 0
passive-interface default
!
interface loopback 0
ip address 10.210.2.2/32
ip ospf 1 area 0
exit
!
! IP ICMP Redirect is mutually exclusive with Active Forwarding
!
no ip icmp redirect
!
interface vlan 10
ip mtu 2048
ip address 10.0.10.3/24
active-gateway ip mac 02:00:00:00:00:01
active-gateway ip 10.0.10.1
ip ospf 1 area 0
!
interface vlan 3010
vsx active-forwarding
ip mtu 2048
ip address 10.30.10.3/24
ip ospf 1 area 0
no ip ospf passive
!
! VRF20
!
vrf VRF20
router ospf 2 vrf VRF20
router-id 10.220.2.2
area 0

14
 passive-interface default
!
interface loopback 2
vrf attach VRF20
ip address 10.220.2.2/32
ip ospf 2 area 0
!
interface vlan 20
vrf attach VRF20
ip mtu 2048
ip address 10.0.20.3/24
active-gateway ip mac 02:00:00:00:00:01
active-gateway ip 10.0.20.1
ip ospf 2 area 0
!
interface vlan 3020
vrf attach VRF20
vsx active-forwarding
ip mtu 2048
ip address 10.30.20.3/24
ip ospf 2 area 0
no ip ospf passive
!
end
write memory

LAB ACTIVITY 4: VALIDATING THE CONFIGURATION

On the 6300-stack – validate connectivity through the VRF default

• Run the following commands

show lldp neighbor-info
• Do you see lldp neighbors on 1/1/25, 1/1/26, 2/1/25, 2/1/26?
show lacp interfaces
• Are all ports up?
Notice the port IDs of the partner on 1/1/26 and 2/1/26 – what does that mean?
Refer back to the LLDP information to answer the question
show ip route static
• Ping the active gateway of VLANs 10 (VRF Default)
ping 10.0.10.1
• Ping the ip address of the loopback interface 0 the 8320 and on each 8325 (VRF Default)
ping 10.210.1.1
ping 10.210.2.1
ping 10.210.2.2
Note: notice that some pings are on a different VRF
• Create a configuration checkpoint to be able to roll back to this point if necessary
copy running-config checkpoint COMPLETE
• Save the configuration
write memory
On the Windows Client

Identify the different adapters:

15
The Ethernet Adapter “6300” is connected to the 6300 Stack port 1/1/1.

Configure the 6300 adapter and a route to the 10.0.0.0 network.

• Open the Network and Sharing Center, and open the details of the “6300” adapter.
• Assign the IP address: 10.0.20.100 with mask: 255.255.255.0 and NO Default gateway.
• Open a command prompt window in Administrator mode (start by entering cmd in the search box – bottom left, and right
click on the Command Prompt option and select Run as administrator)
• Enter cmd in the search box – bottom left
• Right click on the Command Prompt option
• Select Run as administrator

• Create a persistent route (this route points to VRF20)

C:\>route -p add 10.0.0.0 mask 255.0.0.0 10.0.20.1
Test

• Ping VLAN 20’s active gateway

C:\>ping 10.0.20.1
The output should be:
Pinging 10.0.20.1 with 32 bytes of data:
Reply from 10.0.20.1: bytes=32 time<1ms TTL=64
Reply from 10.0.20.1: bytes=32 time<1ms TTL=64

16
 Reply from 10.0.20.1: bytes=32 time<1ms TTL=64
Reply from 10.0.20.1: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.20.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
• Ping the 8320’s loopback 0 address:
C:\>ping 10.210.1.1
What happened? Did it work or fail? Why?

Try:
C:\>tracert 10.210.1.1
• Ping the 8320’s loopback 2 address:
C:\>ping 10.220.1.1
What happened? Did it work or fail? Why?

Try:
C:\>tracert 10.220.1.1

LAB ACTIVITY 5: VSX LIVE UPGRADE

• On the Windows client run:
C:\>ping 10.220.1.1 -t
• On the 8325-A (VSX Primary), display the software version
show version
• And run the following command:
vsx update-software tftp://10.253.1.254/GL_10_07_0001.swi vrf mgmt
Answer “y” at both prompts and observe the process in details. In particular monitor the following information
VSX Primary Software Update Status : Waiting for VSX sync to complete
VSX Secondary Software Update Status : Image updated successfully
VSX ISL Status : Up
Progress
[###########################################.......................................
........]
• Monitor the ping replies
• When the primary completes the reboot process, log back in and verify the new software version
• Repeat the process to bring the switches back to 10.07.0004
vsx update-software tftp://10.253.1.254/GL_10_07_0004.swi vrf mgmt
• When the primary completes the reboot process, log back in and verify the new software version

17
LAB ACTIVITY 6 (OPTIONAL): TROUBLESHOOTING - BREAK AND FIX
Take your time to run these failure scenarios. Take notes.

IMPORTANT: this is your opportunity to gather information that will be crucial for troubleshooting.

On the VSF stack (6300-A)

• On the 6300-A console: shutdown ports 1/1/25 and 1/1/26 (VSF links on 6300-A)
• Go to the 6300-B console and observe what happens
Did it reboot?
If it is in a boot loop, break it with CTRL-C and login

Check the prompt

Check what commands are available

• Use different show vsf commands on the VSF stack
• Run different LACP commands on the VSX pair
Restore:
• On the 6300-A, re-enable port 1/1/25 and 1/1/26 (VSF links on 6300-A) and observe what happens on the 6300-B console
Does the secondary reboot to re-join the stack?
On the VSX pair
• Repeat the previous operation for VSX, by shutting down LAG 256 (VSX inter-switch link) on the 8325-A.
• Run different show vsx commands to identify the impact
• Observe what happens with the ports on the 8325-B
• Run show lacp commands on the VSF stack (6300-A) and the core (8320)
Restore
• On the 8325-A reenable the VSX ISL
• Did any of these devices reboot?
On any LAG
Shut down one port and analyze the impact on the 8320, 8325s VSX, and 6300 VSF stack.

END OF LAB

18
www.arubanetworks.com
3333 Scott Blvd. Santa Clara, CA 95054
1.844.472.2782 | T: 1.408.227.4500 | FAX: 1.408.227.4550 | [email protected]
19