Unsolved
This post is more than 5 years old
4 Posts
0
4961
August 25th, 2016 12:00
Dell S4810 switch as a default gateway
Hello,
I have two Dell S4810 switches bonded with 40G for redundancy and i have 3 clients directly plugged into the switches also bonded. All of the clients are on the same 192.168.1 network. I have a server on 10.1.1 network and a both switches have interface configured on that network. I'm trying to setup the switches as default gateways for clients so they can reach the server by creating a VLAN with 192.168.1.1 address, assigning client into the VLAN and use it as default gateway but i'm not getting any luck. I cant even ping 192.168.1.1 from the clients.
Any ideas what i'm missing? Here is a sample of the config:
protocol spanning-tree rstp
no disable
bridge-priority 36864
!
vlt domain 999
peer-link port-channel 100
primary-priority 36864
unit-id 1
!
stack-unit 0 provision S4810
!
interface TenGigabitEthernet 0/1
description CLIENT 1
no ip address
mtu 9200
flowcontrol rx on tx off
no shutdown
!
interface TenGigabitEthernet 0/2
description CLIENT 2
no ip address
mtu 9200
flowcontrol rx on tx off
no shutdown
!
interface TenGigabitEthernet 0/3
description CLIENT 3
no ip address
mtu 9200
flowcontrol rx on tx off
no shutdown
!
interface TenGigabitEthernet 0/10
ip address 10.1.1.10/24
no shutdown
!
interface fortyGigE 0/56
no ip address
mtu 9200
flowcontrol rx on tx off
no shutdown
!
interface fortyGigE 0/60
no ip address
mtu 9200
flowcontrol rx on tx off
no shutdown
!
interface ManagementEthernet 0/0
ip address 10.1.2.10/24
no shutdown
!
interface Port-channel 1
description lag for CLIENT 1
no ip address
mtu 9200
switchport
channel-member TenGigabitEthernet 0/1
vlt-peer-lag port-channel 1
no shutdown
!
interface Port-channel 2
description lag for CLIENT 2
no ip address
mtu 9200
switchport
channel-member TenGigabitEthernet 0/2
vlt-peer-lag port-channel 2
no shutdown
!
interface Port-channel 3
description lag for CLIENT 3
no ip address
mtu 9200
switchport
channel-member TenGigabitEthernet 0/3
vlt-peer-lag port-channel 3
no shutdown
!
interface Port-channel 100
no ip address
mtu 9216
channel-member fortyGigE 0/56,60
no shutdown
!
interface VLAN 10
ip address 192.168.1.1/24
untagged port-channel 1
untagged port-channel 2
untagged port-channel 3
no shutdown
!
route-map route-map permit 10
!
management route 0.0.0.0/0 10.1.2.1
!
ip route 0.0.0.0/0 10.1.1.1
markosha
4 Posts
0
August 26th, 2016 05:00
Thanks for the reply.
The second switch has identical configuration, port channels are up and i can ping between the clients, i also can ping from the switch to the server, but the clients cant ping the server nor default gateway which is vlan ip on the switch. It was supposed to be a simple setup, not sure what i'm missing
VLT Domain Brief
------------------
Domain ID: 999
Role: Secondary
Role Priority: 36864
ICL Link Status: Up
HeartBeat Status: Not Established
VLT Peer Status: Up
Local Unit Id: 1
Version: 6(5)
Local System MAC address: 00:01:e8:d8:f3:83
Remote System MAC address: 00:01:e8:d8:f3:59
Remote system version: 6(5)
Delay-Restore timer: 90 seconds
Delay-Restore Abort Threshold: 60 seconds
Peer-Routing : Disabled
Peer-Routing-Timeout timer: 0 seconds
Multicast peer-routing timeout: 150 seconds
markosha
4 Posts
0
August 26th, 2016 08:00
Yes, vlan is up and shows up in arp, i can ping the switch from the server but not from clients to the switch
Show ip int vlan 10
Vlan 10 is up, line protocol is up
Internet address is 192.168.1.1/24
Broadcast address is 192.168.1.255
Address determined by user input
IP MTU is 1500 bytes
Directed broadcast forwarding is disabled
Proxy ARP is enabled
Split Horizon is enabled
Poison Reverse is disabled
ICMP redirects are not sent
ICMP unreachables are not sent
show arp
Protocol Address Age(min) Hardware Address Interface VLAN CPU
-----------------------------------------------------------------------------------------
Internet 10.1.1.2 9 e4:c7:22:69:9d:43 Te 0/10 - CP
Internet 10.1.1.17 222 28:80:23:a1:98:8d Te 0/10 - CP
Internet 10.1.1.18 229 28:80:23:a1:76:51 Te 0/10 - CP
Internet 10.1.1.34 - 00:01:e8:d8:f3:85 Te 0/10 - CP
Internet 10.1.2.1 76 00:00:0c:9f:f1:f5 Ma 0/0 - CP
Internet 10.1.2.2 1 e4:c7:22:69:9d:43 Ma 0/0 - CP
Internet 10.1.2.3 1 e4:c7:22:69:8e:c3 Ma 0/0 - CP
Internet 192.168.1.1 - 00:01:e8:d8:f3:85 - Vl 10 CP
markosha
4 Posts
0
August 26th, 2016 09:00
I have re-wired all the clients and also created a vrrp group with one virtual ip for both switches and use the virtual ip as default gateway. I can not ping the default gateway from clients and also ping 10.1.1.10 which is port interface going to the server. But i still cant reach the server so something is a miss with the routing
Switch 1:
interface Vlan 10
ip address 192.168.1.3/24
untagged TenGigabitEthernet 0/4-6,8
untagged Port-channel 1-3
!
vrrp-group 10
priority 150
virtual-address 192.168.1.1
no shutdown
Switch 2:
interface Vlan 10
ip address 192.168.1.3/24
untagged TenGigabitEthernet 0/4-6,8
untagged Port-channel 1-3
!
vrrp-group 10
priority 150
virtual-address 192.168.1.1
no shutdown
show ip route
Codes: C - connected, S - static, R - RIP,
B - BGP, IN - internal BGP, EX - external BGP,LO - Locally Originated,
O - OSPF, IA - OSPF inter area, N1 - OSPF NSSA external type 1,
N2 - OSPF NSSA external type 2, E1 - OSPF external type 1,
E2 - OSPF external type 2, i - IS-IS, L1 - IS-IS level-1,
L2 - IS-IS level-2, IA - IS-IS inter area, * - candidate default,
> - non-active route, + - summary route
Gateway of last resort is not set
Destination Gateway Dist/Metric Last Change
----------- ------- ----------- -----------
C 10.1.1.0/24 Direct, Te 0/10 0/0 2w5d
C 192.168.1.0/24 Direct, Vl 10 0/0 00:31:16
traceroute 10.1.1.2
traceroute to 10.1.1.2 (10.1.1.2), 64 hops max, 52 byte packets
1 192.168.1.3 (192.168.1.3) 0.271 ms 0.161 ms 0.169 ms
2 * * *
support_circula
1 Message
0
August 29th, 2016 03:00
Hi,
maybe it's just a typo - but you have the same 'physical' IP address for VLAN 10 on both switches (192.16.1.3). Please change the IP on Switch2 (or 1, it doesn't really matter).
Best regards
Ralf