Routing problem between switch 2960s and vlans

[Vangelis Komninos]

Dear colleagues,

I appreciate your valuable help on this:
I can ping from switch 2960S-1 the ip 192.168.250.26 but i cannot do it from switch 2960S-2 or my pc.
I can also ping 192.168.50.1 from switch 2960S-2 or my pc.
The routing at switch 2960S-2 seems ok for 192.168.250.26. Where is the problem ?



OVERVIEW ------------------------
(client with Cisco client 192.168.250.26)
  \/
 (cisco asa 192.168.50.1)
  \/
(switch 2960S-1 192.168.50.250 / 192.168.1.79 trunk port g1/0/1)
  \/ (trunking)
(switch 2960S-2 192.168.1.78 trunk port g1/0/1)
  \/
(my pc 192.168.1.189)

DETAILS -----------------------------
- Client connected with cisco client (192.168.250.26 and gateway same)

- cisco asa (192.168.50.1)

- switch 2960S-1:
interface FastEthernet0
 ip address 10.10.10.2 255.255.255.0
 no ip route-cache cef
 no ip route-cache
!
interface GigabitEthernet1/0/1
 switchport trunk allowed vlan 1-100
 switchport mode trunk
 spanning-tree portfast
!
interface GigabitEthernet1/0/2
 switchport access vlan 2
 switchport mode access
!
interface GigabitEthernet1/0/3
 switchport access vlan 2
 switchport mode access
!
interface Vlan1
 ip address 192.168.1.79 255.255.255.0
!
interface Vlan2
 ip address 192.168.50.250 255.255.255.0
!
ip route 192.168.250.0 255.255.255.0 192.168.50.1



-swtich 2960S-2:
spanning-tree mode pvst
spanning-tree extend system-id
!
!
!
!
vlan internal allocation policy ascending
!
!
!
interface FastEthernet0
 ip address 10.10.10.1 255.255.255.0
 no ip route-cache cef
 no ip route-cache
!
interface GigabitEthernet1/0/1
 switchport trunk allowed vlan 1-100
 switchport mode trunk
 spanning-tree portfast
!
interface GigabitEthernet1/0/2
!
interface GigabitEthernet1/0/3
!
interface GigabitEthernet1/0/4
!
!
interface Vlan1
 ip address 192.168.1.78 255.255.255.0
!
!
ip route 192.168.10.222 255.255.255.255 192.168.6.254
ip route 192.168.50.0 255.255.255.0 192.168.1.79
ip route 192.168.250.0 255.255.255.0 192.168.50.1
!

Best Regards

Vangelis

[acampbell]

Hi Vangelis,

Switch 2 is using Vlan 1 for its Ip routing

So just as a test can you remove all the static routes and
replace them with a default route pointing at switch 1 as
its next hop.

!
no ip route 192.168.10.222 255.255.255.255 192.168.6.254
no ip route 192.168.50.0 255.255.255.0 192.168.1.79
no ip route 192.168.250.0 255.255.255.0 192.168.50.1
!
!
ip route 0.0.0.0 0.0.0.0 192.168.1.79
!

Retest

To revert

!
ip route 192.168.10.222 255.255.255.255 192.168.6.254
ip route 192.168.50.0 255.255.255.0 192.168.1.79
ip route 192.168.250.0 255.255.255.0 192.168.50.1
!
!
no ip route 0.0.0.0 0.0.0.0 192.168.1.79
!

Regards
Alex

[Vangelis Komninos]

Hi Alex,

Thank you for your reply. Unfortunately is not working.

When I tracing the ip 192.168.250.26 from switch 2, it reaches the 192.168.1.79 (which is switch 1) so there is no problem reaching the 'other side'.

The problem for me is inside the switch 2, but I'm stack.

Regards

Vanfgelis

[Jon Marshall]

On switch 2 try -

"ip default-gateway 192.168.1.79"

and make sure your PC has it's default gateway set to the same IP.

Jon

[Vangelis Komninos]

Hello John and thanks for your effort.

Bad news. Although I enter the gateway still cannot ping the other side.

An important detail:

I am testing to ping the requested ip 192.168.250.26 from switch-2.

When I ping the 192.168.50.1 (which is the asa, just one hop away) from switch-2, i am getting a successful ping.

Also when I ping the 192.168.250.26 from switch-1 the ping is ok.

Thanks again

Vangelis

[Jon Marshall]

Then it must be the ASA setup.

Jon