01-19-2022 05:13 PM
I attached the packet tracer file, but here are the configs for the two switches connected via layer 3 etherchannel. I have a computer attached to each switch on vlan 10 (f0/1), and they can't ping each other.
Switch1
Current configuration : 1754 bytes
!
version 12.2(37)SE1
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname Switch1
!
!
!
!
!
!
ip routing
!
!
!
!
!
!
!
!
!
!
!
!
!
ip domain-name jon.local
!
!
spanning-tree mode pvst
!
!
!
!
!
!
interface Loopback0
ip address 192.168.255.1 255.255.255.255
!
interface Port-channel1
no switchport
ip address 192.168.0.1 255.255.255.0
!
interface FastEthernet0/1
switchport access vlan 10
!
interface FastEthernet0/2
!
interface FastEthernet0/3
!
interface FastEthernet0/4
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
!
interface FastEthernet0/8
!
interface FastEthernet0/9
!
interface FastEthernet0/10
!
interface FastEthernet0/11
!
interface FastEthernet0/12
!
interface FastEthernet0/13
!
interface FastEthernet0/14
!
interface FastEthernet0/15
!
interface FastEthernet0/16
!
interface FastEthernet0/17
!
interface FastEthernet0/18
!
interface FastEthernet0/19
!
interface FastEthernet0/20
!
interface FastEthernet0/21
!
interface FastEthernet0/22
!
interface FastEthernet0/23
!
interface FastEthernet0/24
!
interface GigabitEthernet0/1
no switchport
no ip address
channel-group 1 mode active
duplex auto
speed auto
!
interface GigabitEthernet0/2
no switchport
no ip address
channel-group 1 mode active
duplex auto
speed auto
!
interface Vlan1
no ip address
shutdown
!
interface Vlan10
mac-address 0050.0fd3.9b02
ip address 192.168.10.1 255.255.255.0
!
router ospf 10
log-adjacency-changes
network 192.168.10.0 0.0.0.255 area 0
network 192.168.255.1 0.0.0.0 area 0
network 192.168.0.0 0.0.0.255 area 0
!
ip classless
!
ip flow-export version 9
!
!
!
!
!
!
!
!
line con 0
!
line aux 0
!
line vty 0 4
login
!
!
!
!
end
Switch2
Current configuration : 1754 bytes
!
version 12.2(37)SE1
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname Switch2
!
!
!
!
!
!
ip routing
!
!
!
!
!
!
!
!
!
!
!
!
!
ip domain-name jon.local
!
!
spanning-tree mode pvst
!
!
!
!
!
!
interface Loopback0
ip address 192.168.255.2 255.255.255.255
!
interface Port-channel1
no switchport
ip address 192.168.0.2 255.255.255.0
!
interface FastEthernet0/1
switchport access vlan 10
!
interface FastEthernet0/2
!
interface FastEthernet0/3
!
interface FastEthernet0/4
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
!
interface FastEthernet0/8
!
interface FastEthernet0/9
!
interface FastEthernet0/10
!
interface FastEthernet0/11
!
interface FastEthernet0/12
!
interface FastEthernet0/13
!
interface FastEthernet0/14
!
interface FastEthernet0/15
!
interface FastEthernet0/16
!
interface FastEthernet0/17
!
interface FastEthernet0/18
!
interface FastEthernet0/19
!
interface FastEthernet0/20
!
interface FastEthernet0/21
!
interface FastEthernet0/22
!
interface FastEthernet0/23
!
interface FastEthernet0/24
!
interface GigabitEthernet0/1
no switchport
no ip address
channel-group 1 mode active
duplex auto
speed auto
!
interface GigabitEthernet0/2
no switchport
no ip address
channel-group 1 mode active
duplex auto
speed auto
!
interface Vlan1
no ip address
shutdown
!
interface Vlan10
mac-address 000b.be0c.bd01
ip address 192.168.10.2 255.255.255.0
!
router ospf 10
log-adjacency-changes
network 192.168.10.0 0.0.0.255 area 0
network 192.168.255.2 0.0.0.0 area 0
network 192.168.0.0 0.0.0.255 area 0
!
ip classless
!
ip flow-export version 9
!
!
!
!
!
!
!
!
line con 0
!
line aux 0
!
line vty 0 4
login
!
!
!
!
end
01-19-2022 07:27 PM
Is there a neighborship between the 2 switches?
sh ip ospf nei
should show you that.
HTH
01-19-2022 07:44 PM
I agree that show ip ospf neighbor is a good starting point. It would also be helpful if there were some type of diagram which could clarify the relationships. And the output of show cdp neighbors might be helpful.
We are told that the switches are connected by EtherChannel. So I am surprised to see that both switches have a loopback interface in network 192.168.255.0. And surprised to see that both switches have a vlan 10 in network 192.168.10.0. So each switch has an interface in network 192.168.10.0. The switch will receive an OSPF advertisement for that network. But since there is a locally connected network that is what is inserted into the routing table and the OSPF advertised route is not inserted into the routing table.
This is a seriously flawed network design.
01-20-2022 02:25 AM
friend, since they share same VLAN which is VLAN 10 they need L2 connect, only connect both SW with one L2 link and your issue will be solve.
01-20-2022 02:15 PM
OSPF is fine and established adjacency and route is exchange. Problem is with IP addressing of PCs. it is the same
192.168.10.x /24 network. PC0 with 192.168.10.101 pings PC1 192.168.10.102. they are on the same network/subnet! no routing is needed! This is not going to work without NAT between them and NAT is not supported on switches; need router for NAT/PAT thing.
I would change one of PCs addressing to different subnet and corresponding switch vlan 10 to match PC subnet.
Regards, ML
**Please Rate All Helpful Responses **
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