05-08-2022 11:27 PM
I have two Cisco C93180YC-FX3 switches, I tried to set vrrp, but I found that if the server uses the same vlan as the upstream, its network speed will become very slow.
I have tried using only a single switch and found the result is the same.
My switch config and network structure are as below:
feature vrrp feature interface-vlan feature ssh int vlan 1 ip address 172.20.1.247 255.255.254.0 no shutdown vrrp 1 address 172.20.1.254 no shutdown ip route 0.0.0.0 0.0.0.0 172.20.0.21 int e1/1-2 switchport switchport mode access switchport access vlan 1 no shutdown
Network structure
speed test result
05-08-2022 11:56 PM - edited 05-08-2022 11:57 PM
is this vPC? ( as per the diagram looks like back to back ?) what speed does each switch connect interface? can you post the config of each witch and show interface x/x output?
05-09-2022 07:40 PM
No, it is back to back.
To determine if VRRP is the problem, I only use one Cisco Nexus C93180YC-FX3 and have no vpc set up.
sw1 is C93180YC-FX3 and sw2 is cisco 2960x, the relevant config and interface information are as below.
SW1
hostname SW1 feature vrrp feature interface-vlan feature ssh int vlan 1 ip address 172.20.1.247 255.255.254.0 no shutdown vrrp 1 address 172.20.1.254 no shutdown ip route 0.0.0.0 0.0.0.0 172.20.0.21 int e1/1-2 switchport switchport mode access switchport access vlan 1 no shutdown -------------------------------------------- SW1# show interface e1/1 Ethernet1/1 is up admin state is up, Dedicated Interface Hardware: 100/1000/10000/25000 Ethernet, address: 1859.f5ef.a998 (bia 1859.f5ef.a998) MTU 1500 bytes, BW 1000000 Kbit , DLY 10 usec reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, medium is broadcast Port mode is access full-duplex, 1000 Mb/s, media type is 1G Beacon is turned off Auto-Negotiation is turned on FEC mode is Auto Input flow-control is off, output flow-control is off Auto-mdix is turned off Rate mode is dedicated Switchport monitor is off EtherType is 0x8100 EEE (efficient-ethernet) : n/a admin fec state is auto, oper fec state is off Last link flapped 00:08:12 Last clearing of "show interface" counters never 1 interface resets Load-Interval #1: 30 seconds 30 seconds input rate 56 bits/sec, 0 packets/sec 30 seconds output rate 816 bits/sec, 1 packets/sec input rate 56 bps, 0 pps; output rate 816 bps, 1 pps Load-Interval #2: 5 minute (300 seconds) 300 seconds input rate 104 bits/sec, 0 packets/sec 300 seconds output rate 760 bits/sec, 1 packets/sec input rate 104 bps, 0 pps; output rate 760 bps, 1 pps RX 17 unicast packets 13 multicast packets 8 broadcast packets 38 input packets 5688 bytes 0 jumbo packets 0 storm suppression bytes 0 runts 0 giants 0 CRC 0 no buffer 0 input error 0 short frame 0 overrun 0 underrun 0 ignored 0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop 0 input with dribble 0 input discard 0 Rx pause TX 28 unicast packets 717 multicast packets 10 broadcast packets 755 output packets 57114 bytes 0 jumbo packets 0 output error 0 collision 0 deferred 0 late collision 0 lost carrier 0 no carrier 0 babble 0 output discard 0 Tx pause ------------------------------------------------------ SW1# show interface e1/2 Ethernet1/2 is up admin state is up, Dedicated Interface Hardware: 100/1000/10000/25000 Ethernet, address: 1859.f5ef.a999 (bia 1859.f5ef.a999) MTU 1500 bytes, BW 1000000 Kbit , DLY 10 usec reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, medium is broadcast Port mode is access full-duplex, 1000 Mb/s, media type is 1G Beacon is turned off Auto-Negotiation is turned on FEC mode is Auto Input flow-control is off, output flow-control is off Auto-mdix is turned off Rate mode is dedicated Switchport monitor is off EtherType is 0x8100 EEE (efficient-ethernet) : n/a admin fec state is auto, oper fec state is off Last link flapped 00:08:37 Last clearing of "show interface" counters never 1 interface resets Load-Interval #1: 30 seconds 30 seconds input rate 440 bits/sec, 0 packets/sec 30 seconds output rate 1024 bits/sec, 1 packets/sec input rate 440 bps, 0 pps; output rate 1.02 Kbps, 1 pps Load-Interval #2: 5 minute (300 seconds) 300 seconds input rate 216 bits/sec, 0 packets/sec 300 seconds output rate 896 bits/sec, 1 packets/sec input rate 216 bps, 0 pps; output rate 896 bps, 1 pps RX 228 unicast packets 10 multicast packets 3 broadcast packets 241 input packets 32763 bytes 0 jumbo packets 0 storm suppression bytes 0 runts 0 giants 0 CRC 0 no buffer 0 input error 0 short frame 0 overrun 0 underrun 0 ignored 0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop 0 input with dribble 0 input discard 0 Rx pause TX 121 unicast packets 769 multicast packets 7 broadcast packets 897 output packets 73515 bytes 0 jumbo packets 0 output error 0 collision 0 deferred 0 late collision 0 lost carrier 0 no carrier 0 babble 0 output discard 0 Tx pause
SW2
hostname SW2 vlan 30 int vlan 1 ip address 172.20.0.21 255.255.254.0 int vlan 30 ip address 192.168.30.31 255.255.255.0 ip routing ip route 172.20.0.0 255.255.254.0 172.20.1.254 int g1/0/1 switchport mode access switchport access vlan 1 no shutdown int g1/0/24 switchport mode access switchport access vlan 30 no shutdown ---------------------------------------------------- SW2#show interfaces gigabitEthernet 1/0/1 GigabitEthernet1/0/1 is up, line protocol is up (connected) Hardware is Gigabit Ethernet, address is 701f.53c7.ff81 (bia 701f.53c7.ff81) MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX input flow-control is off, output flow-control is unsupported ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:00, output 00:00:04, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 1034 packets input, 84323 bytes, 0 no buffer Received 905 broadcasts (898 multicasts) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 898 multicast, 0 pause input 0 input packets with dribble condition detected 282 packets output, 40156 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 unknown protocol drops 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier, 0 pause output 0 output buffer failures, 0 output buffers swapped out -------------------------------------------------- SW2#show interfaces gigabitEthernet 1/0/24 GigabitEthernet1/0/24 is up, line protocol is up (connected) Hardware is Gigabit Ethernet, address is 701f.53c7.ff98 (bia 701f.53c7.ff98) MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX input flow-control is off, output flow-control is unsupported ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:00, output 00:00:04, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 2000 bits/sec, 3 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 2066 packets input, 204444 bytes, 0 no buffer Received 1710 broadcasts (880 multicasts) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 880 multicast, 0 pause input 0 input packets with dribble condition detected 296 packets output, 49908 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 unknown protocol drops 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier, 0 pause output 0 output buffer failures, 0 output buffers swapped out
05-10-2022 06:34 AM
Hi,
If you are planning on keeping both switch-1 and 2 as layer-3, then you simply need to terminate vlan1 on switch-1 and vlan 30 on switch-2 and use a routed link or a vlan in access mode between the 2 switches.
server-vlan-1----switch-1------routed link------switch-2----vlan-30----client
If you are planning on keeping switch-1 as layer-2 only then you can extend vlan one all the way to switch-2 and use that switch to route between vlan-1 and vlan-30 and there is no need for a layer-3 link between the switches.
server-vlan-1----switch-1------vlan-1------switch-2----vlan-30----client
HTH
05-14-2022 05:12 PM
please check this doc.
there is some limitation in using InterVLAN bridge,check cisco recommend.
note:- example in doc. is for 6500 but still can apply to NSK.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide