Trouble routing between VLANS and internet - CLOSED

[Walt48316]

I believe hte Internet part will handle itself, once the issue with the vlans is handle.

We had an issue with a switch and needed to recover, the config we loaded may have been out dated and therefore causing us grief.  We have one Switch which functions as a main switch and defines the IP Addresses for the VLANS, there are 3 other switches which handle voice and other devices.  From the CLI within the switches I can ping all of the gateways of the VLANS, including the IP Address of our firewall, which serves as the default gateway to the mail switch.  The default gateway on the other switches is the IP Address of the main switch.  I cannot ping any of the server which have and IP Address of 192.168.21.x from any of hte switches.

I will paste the running config of the main switch and the switch with the servers.  I belive the issues resides onthe switch with the servers, since that is the one that took a dive

FYI, I have not configured all of the VLANs on the second switch, since I am stuck on seeing devices within the 21.x subnet.  On top of this, the performace is very slow

A cable is connecting port 26 on the main switch with port 24 of the second.

Main Switch running config:

MDF-L3-MAIN# sh run                

Running configuration:

; J9087A Configuration Editor; Created on release #R.11.112

hostname "MDF-L3-MAIN"
snmp-server location "Auburn Hills, MI"
max-vlans 10
time timezone -300
mirror-port 10
console inactivity-timer 30
interface 24
   name "USWAP001"
exit
interface 25
   name "Trunk"
exit
interface 26
   name "USFRW001"
   speed-duplex auto-1000
exit
interface 27
   flow-control
exit
trunk 25 Trk1 Trunk
trunk 26 Trk2 Trunk
trunk 27 Trk3 Trunk
ip default-gateway 192.168.20.4
ip routing
no timesync
snmp-server community "katcon" Unrestricted
vlan 1
   name "DEFAULT_VLAN"
   untagged 28,Trk2
   ip address 192.168.29.1 255.255.255.0
   tagged Trk1,Trk3
   no untagged 1-24
   exit
vlan 22
   name "AH-Voice"
   ip address 192.168.22.1 255.255.255.0
   ip helper-address 192.168.21.19
   tagged 1-23,Trk1-Trk3
   exit
vlan 24
   name "AH-PC"
   untagged 1-23
   ip address 192.168.24.1 255.255.255.0
   ip helper-address 192.168.21.19
   tagged Trk1-Trk3
   exit
vlan 25
   name "AH-Wireless"
   ip address 192.168.25.1 255.255.255.0
   ip helper-address 192.168.21.19
   tagged Trk1-Trk3
   exit
vlan 21
   name "AH-Server"
   ip address 192.168.21.1 255.255.255.0
   ip helper-address 192.168.21.19
   tagged Trk1-Trk3
   exit
vlan 20
   name "AH-Network"
   untagged 24
   ip address 192.168.20.1 255.255.255.0
   ip helper-address 192.168.21.19
   tagged Trk1-Trk3
   exit
vlan 23
   name "AH-Video"
   ip address 192.168.23.1 255.255.255.0
   ip helper-address 192.168.21.19
   tagged Trk1-Trk3
   exit
vlan 26
   name "AH-Periphera"
   ip address 192.168.26.1 255.255.255.0
   ip helper-address 192.168.21.19
   tagged Trk1-Trk3
   exit
ip route 0.0.0.0 0.0.0.0 192.168.20.4
primary-vlan 20
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree Trk3 priority 4
password manager

Second Switch:

MDF-L2-SW2# sh run

Running configuration:

; J9299A Configuration Editor; Created on release #J.15.09.0026
; Ver #06:04.08.00.01.14.05:1a
hostname "MDF-L2-SW2"
power-over-ethernet pre-std-detect
ip default-gateway 192.168.20.1
snmp-server community "public" unrestricted
vlan 1
   name "DEFAULT_VLAN"
   no untagged 1-20
   untagged 21-24
   no ip address
   exit
vlan 20
   name "VLAN20"
   tagged 24
   ip address 192.168.20.5 255.255.255.0
   exit
vlan 21
   name "VLAN21"
   tagged 24
   no ip address
   exit
vlan 22
   name "VLAN22"
   tagged 1-20,24
   no ip address
   voice
   exit
vlan 24
   name "PCs"
   untagged 1-20
   tagged 24
   no ip address
   exit
primary-vlan 20

Thanks

Walt

[Walt48316]

The config the client provided for the restore was old, a newer one was found and there were 2 trunks 11-12 and 13-14 which were not in this config.  Uploaded that config and all is much better.

We now have a number of collisions on the network, but that is another issue to tackle.

Thanks for takine a look

[Vince-Whirlwind]

If you have collisions on your netwoprk, 99% of ther time it's because somebody has disabled auto-negotiation somewhere and needs to be punished.

I notice this in your config:

interface 26
   name "USFRW001"
   speed-duplex auto-1000

The Gb ethernet standards specifically mandate auto-negotiation needs to be enabled - disabling it has the potential to screw with the clocking-rate on the physical medium.