This post is more than 5 years old
22 Posts
0
2420
September 10th, 2019 04:00
unable to connect from main building to colo location using point to point
i need some help setting up a point to point connection between our main building and the colo location.
we leased a 1gig fiber from century link, there is a link between the two locations, but i cant access the switch in the colo location.
VLANs in both location: 10,11,50,100
here is the config in both locations
main building: im using a force10 S4810 , port 33
here is the config
interface TenGigabitEthernet 0/33
description Connection to COLO
no ip address
switchport
flowcontrol rx on tx off
sflow enable
sflow polling-interval 60
sflow sample-rate 1024
no shutdown
interface Vlan 100
ip address 10.100.0.10/24
untagged TenGigabitEthernet 0/33,46
no shutdown
interface Vlan 10
ip address 10.10.10.1/24
tagged TenGigabitEthernet 0/1,32,41
untagged Port-channel 1-7
no shutdown
!
interface Vlan 11
ip address 10.10.1.1/24
tagged TenGigabitEthernet 0/32
tagged Port-channel 1-7
no ip proxy-arp
no shutdown
!
interface Vlan 50
ip address 10.10.50.1/24
no shutdown
Colo Location:
im using a N4032F dell switch, port 24
and here is the config
interface Te1/0/24
speed auto 1000
switchport mode trunk
switchport general allowed vlan add 10-11
switchport trunk native vlan 10
switchport trunk allowed vlan 10-11,50
interface vlan 10
ip address 10.100.10.1 255.255.255.0
exit
interface vlan 11
ip address 10.100.1.1 255.255.255.0
exit
interface vlan 50
ip address 10.100.50.1 255.255.255.0
exit
interface vlan 100
ip address 10.100.0.100 255.255.255.0
is the configuration correct?
please help
bealdrid2
1 Rookie
•
117 Posts
1
September 13th, 2019 11:00
For the laptop connected to S4810:
1. That gateway isn't in the same subnet as the IP.
2. That port doesn't appear to be in any vlan.
For the laptop connected to N3048P:
1. The port looks like it should be in VLAN11 instead of VLAN100.
2. On N3048P, VLAN11 looks like it should have an IP address of "10.100.1.1"
Double check IP addresses of all VLAN interfaces and make sure the laptop ports are in the right vlan and their gateway IP corresponds to the VLAN Interface IP.
bealdrid2
1 Rookie
•
117 Posts
0
September 10th, 2019 05:00
My first question would be are you looking to do a L3 point to point (routed) connection, or are you wanting to trunk L2 and have those VLANs on both sides? It seems like maybe you want the L3 connection, as I see VLAN100 is the same subnet on both sides, but all other VLANs are different subnets. Is VLAN100 supposed to be the p2p vlan? You could shrink that to a /30 instead of a /24 if you wanted.
If L3 only, I would only allow VLAN100 on the link as the transit vlan, and tag it:
S4810:
interface Vlan 100
ip address 10.100.0.10/24
tagged TenGigabitEthernet 0/33
untagged TenGigabitEthernet 0/46
no shutdown
N4032F:
interface Te1/0/24
speed auto 1000
switchport mode general
switchport general allowed vlan add 100 tagged
houstoniaman
22 Posts
0
September 10th, 2019 06:00
thanks for the quick response.
and you are right, it's a L3 P2P, and what i want to be able to accomplish is access all 3 vlans on the Colo location, we have servers that are on 10.100.1.x, and 10.100.10.x.
the N4032F ip is 10.100.1.1 and im able to access it from the main building S4810
also i can ping anything on 10.100.1.x, but not the 10.100.10.1 do you think its a routing issue ?
here is the IP route on both ends?
N4032F:
Default Gateway is 10.100.1.250
S *0.0.0.0/0 [253/0] via 10.100.1.250, Vl11
C *10.100.0.0/24 [0/1] directly connected, Vl100
C *10.100.1.0/24 [0/1] directly connected, Vl11
C *10.100.10.0/24 [0/1] directly connected, Vl10
C *10.100.50.0/24 [0/1] directly connected, Vl50
S *10.100.70.0/24 [1/0] via 10.100.0.10, Vl100
S *198.46.70.0/24 [1/0] via 10.100.0.10, Vl100
S *198.46.72.0/24 [1/0] via 10.100.0.10, Vl100
S4810 ip route:
*S 0.0.0.0/0 via 198.46.70.4, Vl 70 1/0 12w4d
S 10.0.1.0/24 via 198.46.70.4, Vl 70 1/0 12w4d
S 10.0.1.224/27 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.0.111.0/24 via 198.46.70.4, Vl 70 1/0 12w4d
S 10.1.87.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.1.167.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.1.168.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.1.169.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.1.170.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.2.125.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.2.169.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.2.170.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.2.172.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.5.20.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.5.22.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
C 10.10.1.0/24 Direct, Vl 11 0/0 12w4d
C 10.10.10.0/24 Direct, Vl 10 0/0 12w4d
C 10.10.88.0/22 Direct, Vl 90 0/0 12w4d
C 10.10.92.0/22 Direct, Vl 92 0/0 12w4d
C 10.10.250.0/24 Direct, Vl 250 0/0 12w4d
S 10.30.10.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.30.22.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.30.27.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.30.32.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.30.33.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.30.96.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 10.167.1.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
C 10.210.209.0/24 Direct, Vl 209 0/0 3w0d
S 12.0.29.128/25 via 198.46.70.4, Vl 70 1/0 12w4d
S 172.20.0.0/16 via 10.210.209.1, Vl 209 1/0 3w0d
S 172.21.0.0/16 via 10.210.209.1, Vl 209 1/0 3w0d
S 172.22.0.0/16 via 10.210.209.1, Vl 209 1/0 3w0d
S 172.22.0.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 192.9.202.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 192.168.1.0/24 via 10.10.10.68, Vl 10 1/0 12w4d
S 192.168.50.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 192.168.51.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 192.168.52.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 192.168.53.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 192.168.54.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 192.168.55.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 192.168.56.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
C 192.168.101.0/24 Direct, Vl 101 0/0 12w4d
C 192.168.102.0/24 Direct, Vl 102 0/0 12w4d
C 192.168.103.0/24 Direct, Vl 103 0/0 12w4d
C 192.168.104.0/24 Direct, Vl 104 0/0 5w6d
C 192.168.105.0/24 Direct, Vl 105 0/0 12w4d
C 192.168.107.0/24 Direct, Vl 107 0/0 12w4d
C 192.168.108.0/24 Direct, Vl 108 0/0 12w4d
C 192.168.110.0/24 Direct, Vl 110 0/0 12w4d
C 192.168.115.0/24 Direct, Vl 115 0/0 12w4d
C 192.168.121.0/24 Direct, Vl 121 0/0 12w4d
C 192.168.122.0/24 Direct, Vl 122 0/0 12w4d
C 192.168.123.0/24 Direct, Vl 123 0/0 12w4d
C 192.168.124.0/24 Direct, Vl 124 0/0 5w6d
C 192.168.125.0/24 Direct, Vl 125 0/0 12w4d
C 192.168.127.0/24 Direct, Vl 127 0/0 12w4d
C 192.168.128.0/24 Direct, Vl 128 0/0 12w4d
S 192.168.141.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 192.168.142.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 192.168.143.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 192.168.144.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
S 192.168.148.0/24 via 10.210.209.1, Vl 209 1/0 3w0d
C 198.46.70.0/24 Direct, Vl 70 0/0 12w4d
C 198.46.72.0/24 Direct, Vl 72 0/0 12w4d
Thank you
bealdrid2
1 Rookie
•
117 Posts
0
September 10th, 2019 06:00
It does look like a routing issue to me. From the S4810 side, there is no route, other than the default that matches the subnets on the N4032 side. So my guess is it's just taking the default route. Are you running any routing protocol like OSPF? You could just use static routes.
Like on the S4810:
ip route 10.100.10.0 /24 10.100.0.100
ip route 10.100.1.0/24 10.100.0.100
ip route 10.100.50.0/24 10.100.0.100
Then you also need return routes on the N4032 for the subnets on the 4810.
Really though, I would just use a dedicated p2p (/30) subnet between the two devices. I.e. nothing else is in that subnet, just the two switches. It seems like the p2p network is currently shared with other servers. I wouldn't do that..
houstoniaman
22 Posts
0
September 10th, 2019 06:00
how can i use a dedicated p2p (30) between the two devices, meaning how do i configure it on both switches?
to answer your question , we're using RIP
router rip
network 10.0.0.0
network 192.168.10.0
network 192.168.101.0
network 192.168.102.0
network 192.168.103.0
network 192.168.104.0
network 192.168.105.0
network 192.168.106.0
network 192.168.107.0
network 192.168.108.0
network 192.168.110.0
network 192.168.115.0
network 192.168.121.0
network 192.168.122.0
network 192.168.123.0
network 192.168.124.0
network 192.168.125.0
network 192.168.126.0
network 192.168.127.0
network 192.168.128.0
network 198.46.70.0
network 198.46.72.0
network 198.46.76.0
thanks
bealdrid2
1 Rookie
•
117 Posts
0
September 10th, 2019 07:00
Say we want to use VLAN254 as the transit p2p vlan:
On the S4810, you could use a routed port but for simplicity, lets just use this transit vlan
interface vlan 254
ip address 10.254.254.1 /30
no shutdown
tagged TenGigabitEthernet 0/33
On the N4032, you can't even use a routed port, you have to use a VLAN interface:
interface vlan 254
ip address 10.254.254.2 255.255.255.252
no shutdown
Then on the N4032 actual port you'd just have:
interface Te1/0/24
speed auto 1000
switchport mode general
switchport general allowed vlan add 254 tagged
At that point the p2p connection is setup and 10.254.254.1 and 10.254.254.2 should be able to ping each other. Now you need to get routing going between all the other subnets. I'm not familiar with RIP, so I can't really help much, but for OSPF I would basically just announce the subnets on both sides into OSPF, and ensure both sides form a neighborship adjacency with each other over the p2p vlan. If you're interested in setting up OSPF I could help with that, but please be careful before ditching RIP if it's configured throughout your environment.
Alternatively you can use static routes, as mentioned before. This may be the safe option.
S4810:
ip route 10.100.10.0/24 10.254.254.2
ip route 10.100.1.0/24 10.254.254.2
ip route 10.100.50.0/24 10.254.254.2
N4032:
ip route 10.10.10.0/24 10.254.254.1
... and so on
You need to decide where the VLAN100 (10.100.0.0/24) needs to exist. Was this intended to be the p2p vlan, or are there other servers in this subnet? If there are servers in this subnet at both sites, this complicates things, and makes it sound like you really need a L2 connection between sites.
houstoniaman
22 Posts
0
September 10th, 2019 09:00
yes there are servers on both ends, we're using the P2P for replication,and backup.
houstoniaman
22 Posts
0
September 11th, 2019 11:00
thanks for your help, but i tried all the solutions you suggested, but im still having the same issue, cannot connect.
im setting up a lab , and try different configurations, and see if i can get them to talk to each other.
thanks again
bealdrid2
1 Rookie
•
117 Posts
0
September 12th, 2019 07:00
If you do need some subnets to be present on both sides, you can do a hybrid Layer 2/Layer 3 setup. Basically on the link between the buildings you would trunk the vlans that need to be on both sides, then you would also trunk the dedicated p2p /30 vlan for your routing. I understand you have servers in both locations. The question is, are they in the same subnet on both locations? Which subnet is that, if so.
houstoniaman
22 Posts
0
September 13th, 2019 02:00
houstoniaman
22 Posts
0
September 13th, 2019 09:00
S4810
HOU-RTR-CORE01#show ip route
Gateway of last resort is not set
Destination Gateway Dist/Metric Last Change
----------- ------- ----------- -----------
C 10.100.0.0/24 Direct, Vl 100 0/0 01:01:54
S4810
!
interface Vlan 1
!untagged TenGigabitEthernet 0/27,33,39,41
!
interface Vlan 10
ip address 10.10.10.1/24
tagged TenGigabitEthernet 0/32,41
untagged Port-channel 1-6
no shutdown
!
interface Vlan 11
ip address 10.10.1.1/24
tagged TenGigabitEthernet 0/31-32
tagged Port-channel 1-6
no shutdown
!
interface Vlan 50
ip address 10.10.50.1/24
no shutdown
!
interface Vlan 100
ip address 10.100.0.10/24
tagged TenGigabitEthernet 0/46
no shutdown
Laptop port config
interface TenGigabitEthernet 0/35
no ip address
portmode hybrid
switchport
no shutdown
N3048P
SA-SW-DIST01#show ip route
Default Gateway is 10.100.1.250
S *0.0.0.0/0 [253/0] via 10.100.1.250, 01h:05m:57s, Vl11
S *10.10.0.0/16 [1/0] via 10.100.0.10, Vl100
C *10.100.0.0/24 [0/0] directly connected, Vl100
C *10.100.1.0/24 [0/0] directly connected, Vl11
C *10.100.10.0/24 [0/0] directly connected, Vl10
C *10.100.50.0/24 [0/0] directly connected, Vl50
S *192.168.0.0/16 [1/0] via 10.100.0.10, Vl100
S *192.168.0.0/24 [1/0] via 10.100.0.10, Vl100
S *198.46.70.0/24 [1/0] via 10.100.0.10, Vl100
S *198.46.72.0/24 [1/0] via 10.100.0.10, Vl100
Laptop port config
interface Gi1/0/20
switchport access vlan 100
exit
houstoniaman
22 Posts
0
September 13th, 2019 09:00
laptop connected to S4810
ip 10.100.0.200
subnet mask 255.255.255.0
Gateway 10.0.100.1
laptop connected to N3048P
ip 10.100.1.30
subnet mask 255.255.255.0
gateway 10.100.1.1
bealdrid2
1 Rookie
•
117 Posts
0
September 13th, 2019 09:00
If you can share "show ip route" from both switches, as well as the interface config for the ports the laptops are plugged into I may be able to help. And for the S4810, "show ru int vlan". Also what are the ip addresses, gateways, and netmask for the laptops?
houstoniaman
22 Posts
0
September 18th, 2019 06:00
houstoniaman
22 Posts
0
September 18th, 2019 09:00
good news, everything is working as it's suppose to, found out the firewall was blocking the ping between the two laptops.
thank you so much for your help