Creating new L3 vLAN on S4810

Question

Hi All,

I have two core Switches S4810, S5000 and some N2024 and N2048 switches.

Both cores are connected via LAG, Port-Channel created to connect each Access Switches / S5000 switches.

I created a new vLAN on both Cores and tagged the POs as well as the te0/xx ports correctly, but what I noticed when I initiate a continues ping from any existing vLAN to the new vLAN and I shutdown one the vLAN in one of the Core Switches, the ping stops;;

Can anyone please suggest something; below the configuration I made;

New vLAN Created;

CORE-1(conf-if-vl-33)#show config
!
interface Vlan 33
description Student-WiFi
ip address 10.10.24.3/21
tagged TenGigabitEthernet 0/5,19
tagged Port-channel 24,56
!
vrrp-group 33
priority 150
virtual-address 10.10.24.1
ip helper-address 192.168.10.190
no shutdown

======================

CORE-2(conf-if-vl-33)#show config
!
interface Vlan 33
description Student-WiFi
ip address 10.10.24.2/21
tagged TenGigabitEthernet 0/19
tagged Port-channel 24,56
!
vrrp-group 33
virtual-address 10.10.24.1
ip helper-address 192.168.10.190
no shutdown
CORE-2(conf-if-vl-33)#

======================

When I ping from those vLANs below, and I shutdown vLAN 33 the ping stops in either Core-1 or Core-2

CORE-1(conf-if-vl-10)#show config
!
interface Vlan 10
description SERVERS
ip address 192.168.10.3/24
tagged TenGigabitEthernet 0/5
tagged Port-channel 13,24,46,50,55-56,58,60
untagged TenGigabitEthernet 0/27
!
vrrp-group 10
priority 150
virtual-address 192.168.10.1
ip helper-address 192.168.10.190
no shutdown

===============================

CORE-1(conf-if-vl-33)#shutdown
CORE-1(conf-if-vl-33)#do ping 10.10.24.1

Type Ctrl-C to abort.

Sending 5, 100-byte ICMP Echos to 10.10.24.1, timeout is 2 seconds:
.

Success rate is 0.0 percent (0/2)
CORE-1(conf-if-vl-33)#exit
CORE-1(conf)#exit
CORE-1#ping 10.10.24.1 source vlan 10

Type Ctrl-C to abort.

Sending 5, 100-byte ICMP Echos to 10.10.24.1 from 192.168.10.3, timeout is 2 seconds:
.....
Success rate is 0.0 percent (0/5)
CORE-1#ping 10.10.24.1 source vlan 12

Type Ctrl-C to abort.

Sending 5, 100-byte ICMP Echos to 10.10.24.1 from 192.168.12.3, timeout is 2 seconds:
.....
Success rate is 0.0 percent (0/5)
CORE-1#ping 10.10.24.1 source vlan 11

Type Ctrl-C to abort.

Sending 5, 100-byte ICMP Echos to 10.10.24.1 from 10.10.8.3, timeout is 2 seconds:
.....
Success rate is 0.0 percent (0/5)
CORE-1#

========================================

CORE-2#ping 10.10.24.1 source vlan 10

Type Ctrl-C to abort.

Sending 5, 100-byte ICMP Echos to 10.10.24.1 from 192.168.10.2, timeout is 2 seconds:
!!!!!
Success rate is 100.0 percent (5/5), round-trip min/avg/max = 0/0/0 (ms)
CORE-2#ping 10.10.24.1 source vlan 12

Type Ctrl-C to abort.

Sending 5, 100-byte ICMP Echos to 10.10.24.1 from 192.168.12.2, timeout is 2 seconds:
!!!!!
Success rate is 100.0 percent (5/5), round-trip min/avg/max = 0/0/0 (ms)
CORE-2#ping 10.10.24.1 source vlan 13

Type Ctrl-C to abort.

Sending 5, 100-byte ICMP Echos to 10.10.24.1 from 192.168.13.2, timeout is 2 seconds:
!!!!!
Success rate is 100.0 percent (5/5), round-trip min/avg/max = 0/0/0 (ms)
CORE-2#

=========================

Appreciate if anyone can help on this..!!!

Regards,

Habibalby · Answer

@Anonymous wrote:

By shutting down VLAN 33, Are you trying to test VRRP?

Yes, to test core-switch availability.

Can you show us the output from the following commands:

#Show vrrp

I think I found the issue;

Vl 21 IPv4 21 100 Y Master 10.10.24.3 10.10.24.1

This should be 150 to be same as existing vrrp-groups;

#show track

No result of this command..?

What are the test results if pinging from a client on the network and not the switch itself?

When I ping from my Machine, and I shutdown vLAN in Core-1, the ping stops when I shutdown the sane vLAN on Core-2 the ping continues.

Do the other VLANs respond the same way?

I tested with other vLAN and unfortunately, I found the same behavior when I shutdown either vLAN in one of the Core.

Hi Daniel,

Please refer to my reply above.

Regards,

Habibalby · Answer

I have read this quote

how-to-configure-virtual-router-redundancy-protocol-vrrp-on-dell-networking-force10-switches

If two routers in a VRRP group come up at the same time and have the same priority value, the interface's physical IP addresses are used as a tie-breaker to decide which is MASTER. The router with the higher IP address becomes MASTER.

Habibalby · Answer

Hi Daniel, I modified  the vrrp-group priority to 150 but still same issue. Regards,

Habibalby · Answer

Hi Daniel,

here's the output of vrrp-group 21;

Core-1

Vlan 21, IPv4 VRID: 21, Version: 2, Net: 10.10.24.3
VRF: 0 default
State: Master, Priority: 150, Master: 10.10.24.3 (local)
Hold Down: 0 sec, Preempt: TRUE, AdvInt: 1 sec
Adv rcvd: 1373, Bad pkts rcvd: 0, Adv sent: 248227, Gratuitous ARP sent: 8
Virtual MAC address:
00:00:5e:00:01:15
Virtual IP address:
10.10.24.1
Authentication: (none)

Core-2

Vlan 21, IPv4 VRID: 21, Version: 2, Net: 10.10.24.2
VRF: 0 default
State: Backup, Priority: 100, Master: 10.10.24.3
Hold Down: 0 sec, Preempt: TRUE, AdvInt: 1 sec
Adv rcvd: 246501, Bad pkts rcvd: 0, Adv sent: 1577, Gratuitous ARP sent: 7
Virtual MAC address:
00:00:5e:00:01:15
Virtual IP address:
10.10.24.1
Authentication: (none)

Regards,

Networking General

Creating new L3 vLAN on S4810

Was this post helpful?