Routing between 3750 issue

[cmeljak]

Hi Everybody,

Let me introduce you to my configuration first:
I have two 3750s interconnected via L3 port channel (second switch will be placed on WAN after finished additional config).
I have RIP enabled for subnets on both sides, everything seems to be working perfectly fine, routing is OK...etc.

The problem I have been experiencing is:
1. Let's say VLAN1 is 10.0.0.1/24 (on switch_1) and VLAN1 L3 interface is not present on switch_2.
I can get from hosts on both sides to each other, that is not an issue, but when TRYING TO get to FTP/TFTP server from switch_2 (residing on VLAN1), IT TIMES OUT!?!

2. When do "trace 10.0.0.253(TFTP)" I am getting response from destination
When I ping TFTP IP address from switch_2, getting request time outs...

I suppose it is probably just silly mistake I may have overlooked, but I just can't find it...

I am attaching configuration files from both switches fopr your review, plus routing tables. Please let me know if you need more info.

Any help with this issue will be highly appreciated!

Best regards,

Ed

Config:

Switch_1:
version 12.2
no service pad
service timestamps debug uptime
service timestamps log datetime
service password-encryption
service sequence-numbers
!
hostname CONWSR01
!
enable secret 5 $1$h9wf$.cJtwCNlr0VeAVhpT1/DI1
!
aaa session-id common
clock timezone EST -5
clock summer-time EDT recurring
switch 1 provision ws-c3750g-24ps
switch 2 provision ws-c3750g-24ps
switch 3 provision ws-c3750g-24ps
system mtu routing 1500
no ip subnet-zero
ip routing
no ip domain-lookup
!
interface Port-channel10
no switchport
ip address 10.10.10.2 255.255.255.252
!
interface Vlan1
ip address 10.0.0.1 255.255.255.0
no ip redirects
!
interface Vlan100
ip address 10.192.3.1 255.255.255.0
!
interface Vlan101
ip address 10.192.1.1 255.255.255.0
!
interface Vlan102
ip address 10.192.2.1 255.255.255.0
!
interface Vlan103
description DRHPMGMT
no ip address
!
interface Vlan104
description DRORCLDRPINT
no ip address
!
interface Vlan105
description COADINT
ip address 10.192.5.1 255.255.255.0
!
interface Vlan110
description Thin_Client network
ip address 10.192.10.1 255.255.255.0
no ip redirects
!
interface Vlan120
description HelpDesk
ip address 10.192.20.1 255.255.255.0
!
interface Vlan149
description Wireless 2
ip address 10.192.101.1 255.255.255.0
!
interface Vlan150
description WLAN_10.192.100
ip address 10.192.100.1 255.255.255.0
!
interface Vlan151
description VLAN198.73.51.0
ip address 198.73.51.1 255.255.255.0
no ip redirects
!
interface Vlan200
description VideoConf
ip address 10.192.200.1 255.255.255.0
!
interface Vlan600
no ip address
shutdown
!
interface Vlan601
description COORCLDEVPUB
ip address 10.192.4.1 255.255.255.0
!
interface Vlan602
description DRORCLDRPPUB
no ip address
!
interface Vlan900
description Internet VLAN
ip address 192.168.1.2 255.255.255.0
!
router rip
version 2
network 10.0.0.0
network 198.73.51.0
network 198.73.52.0
!
ip default-gateway 198.73.52.1
ip classless
ip route 0.0.0.0 0.0.0.0 198.73.52.1
ip route 10.10.10.0 255.255.255.252 10.10.10.1
ip http server
ip http secure-server

end

CONWSR01#sho ip rout
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, 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, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 198.73.52.1 to network 0.0.0.0

C 10.1.0.0/24 is directly connected, Vlan151
10.0.0.0/8 is variably subnetted, 13 subnets, 2 masks
C 10.192.200.0/24 is directly connected, Vlan200
C 10.10.10.0/30 is directly connected, Port-channel10
C 10.192.100.0/24 is directly connected, Vlan150
C 10.192.101.0/24 is directly connected, Vlan149
C 10.192.10.0/24 is directly connected, Vlan110
C 10.192.2.0/24 is directly connected, Vlan102
C 10.192.3.0/24 is directly connected, Vlan100
C 10.192.1.0/24 is directly connected, Vlan101
R 10.196.2.0/24 [120/1] via 10.10.10.1, 00:00:21, Port-channel10
R 10.196.3.0/24 [120/1] via 10.10.10.1, 00:00:21, Port-channel10
C 10.192.4.0/24 is directly connected, Vlan601
R 10.196.1.0/24 [120/1] via 10.10.10.1, 00:00:21, Port-channel10
C 10.192.20.0/24 is directly connected, Vlan120
C 10.0.0.0/24 is directly connected, Vlan1
C 192.168.1.0/24 is directly connected, Vlan900
S* 0.0.0.0/0 [1/0] via 198.73.52.1
-----------------------------------------------------------

Switch_2:

version 12.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname CODRPSW
!
interface Port-channel10
no switchport
ip address 10.10.10.1 255.255.255.252
!
interface Vlan1
no ip address
!
interface Vlan103
ip address 10.196.3.1 255.255.255.0
!
interface Vlan104
ip address 10.196.2.1 255.255.255.0
!
interface Vlan602
ip address 10.196.1.1 255.255.255.0
!
interface Vlan999
ip address 192.168.10.1 255.255.255.252
!
router rip
version 2
network 10.0.0.0
network 192.168.10.0
no auto-summary
!
ip default-gateway 10.10.10.1
ip classless
ip route 0.0.0.0 0.0.0.0 10.10.10.2
ip route 198.73.52.0 255.255.255.0 198.73.52.164
ip http server
ip http secure-server

end

CODRPSW#sho ip rout
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, 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, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 10.10.10.2 to network 0.0.0.0

R 10.1.0.0/24 [120/1] via 10.10.10.2, 00:00:12, Port-channel10
10.0.0.0/8 is variably subnetted, 13 subnets, 2 masks
R 10.192.200.0/24 [120/1] via 10.10.10.2, 00:00:12, Port-channel10
C 10.10.10.0/30 is directly connected, Port-channel10
R 10.192.100.0/24 [120/1] via 10.10.10.2, 00:00:12, Port-channel10
R 10.192.101.0/24 [120/1] via 10.10.10.2, 00:00:12, Port-channel10
R 10.192.10.0/24 [120/1] via 10.10.10.2, 00:00:12, Port-channel10
R 10.192.2.0/24 [120/1] via 10.10.10.2, 00:00:12, Port-channel10
R 10.192.3.0/24 [120/1] via 10.10.10.2, 00:00:12, Port-channel10
R 10.192.1.0/24 [120/1] via 10.10.10.2, 00:00:12, Port-channel10
C 10.196.2.0/24 is directly connected, Vlan104
C 10.196.3.0/24 is directly connected, Vlan103
R 10.192.4.0/24 [120/1] via 10.10.10.2, 00:00:12, Port-channel10
C 10.196.1.0/24 is directly connected, Vlan602
R 10.192.20.0/24 [120/1] via 10.10.10.2, 00:00:12, Port-channel10
R 10.0.0.0/24 [120/1] via 10.10.10.2, 00:00:12, Port-channel10
S* 0.0.0.0/0 [1/0] via 10.10.10.2
------------------------------------------------------------

 

[VinceWhirlwind]

When you put port-channel to VLAN "x" and as access ports only, routing cannot work at all."

Why do you want them to be access ports? The VLAN interface becomes your routable interface, just like any other VLAN interface is routed by the switch. The etherchannel is a trunk - *you* decide what VLANs are on it and it goes without saying that you wouldn't put any VLANs on this trunk that belong on the edge.

Anyway - back to the pinging that doesn't work : your switch_2 is generating a ping with a source IP address you're not expecting. Have you captured any packets to see what they look like?
Notice for example that you have the 192.168.10.x subnet on switch_2 with no corresponding route for it on switch_1.

 

[cmeljak]

Vince,

Yes, but I don't want to use L2 interface between switches, I would have done it at the first place...

To your questions:

I have done some additional testing, here are the results:

1. Ping from switch_2:
ping 10.0.0.1 source 10.196.1/2/3.1 replies
ping 10.0.0.x source 10.196.1/2/3.1 replies

ping 10.0.0.x timed out ;-)

ping from host 10.196.1/2/3.2 to 10.0.0.x replies as well

2. Ping from switch_1:
ping 10.196.1/2/3.x source 10.192.1/2/3.1 replies

ping 10.196.1/2/3.x source 10.0.0.1 replies

ping from host 10.0.0.x to 10.192.1/2/3.1 replies as well

Findings:
- when pinging from switch_2 to any network on switch_1 with specified "source" getting replies.
- when pinging from hosts, it works as well
- But when pinging from switch_2 without source IP, getting time outs

Regards,

Ed