Start Free Trial

asked on

Route VLAN's on Procurve 3400cl

Configuring Procurve 3400 to route several VLAN's.
Test environment two vlans one station in each.
Routing is not happening between VLAN 1 and VLAN 20.
From switch cannot ping station on 192.168.221.23 (VLAN 20)
From switch can ping anything on 192.168.0.x (VLAN 1)
stations on VLAN 1 and VLAN 20 cannot ping each other
Fairly new to routing, detail steps for solution is needed.
Thank You
Current CONFIG
; J4906A Configuration Editor; Created on release #M.10.76

hostname "ProCurve Switch 3400cl-48G"
snmp-server contact " "
snmp-server location " "
fastboot
ip default-gateway 192.168.0.1
sntp server 192.168.0.26 4
ip routing
timesync sntp
sntp unicast
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged 1-32,45-48
ip address 192.168.0.221 255.255.255.0
no untagged 33-44
exit
vlan 20
name "Stations"
untagged 33-44
ip address 192.168.221.1 255.255.255.0
exit
ip route 0.0.0.0 0.0.0.0 192.168.0.1
password manager
password operator

What ports are the devices connected to and what are their IP addresses?

Clients should have IP of the vlan as default gateway.

so PC1 on say port1 in vlan1 could have IP 192.168.0.100 mask 255.255.255.0 dgw 192.168.0.221

and PC2 on say port 33 vlan 20 could have IP 192.168.221.100 mask 255.255.255.0 dgw 192.168.221.1

HTH

ASKER

My apology for not including:

Config of station on VLAN 1
IP 192.168.0216/24
GW: 192.168.0.1
connected on port: 32

config of station on VLAN 20
IP 192.168.221.23/24
GW: 192.168.221.1
connected on port: 35

Default gateway for Station 1 should be 192.168.0.1

Beyond that, can each Station ping it's default gateway?

ASKER

I am interpreting Station 1 to be station on VLAN 1...and it is.

station on VLAN 1 can ping its gateway.

station on VLAN 20 cannot ping its gateway.

switch can ping station on VLAN 1
switch cannot ping station on VLAN 20

I'd start looking at layer 1 and layer 2 issues. The config of the switch looks good. The IP address of the VLAN 20 device looks good.

Unless there's typo in the IP addressing, it's going to have to be a bad cable, loose connector, etc.

ASKER

would a show tech all be of any help?

I'd start with "show interfaces brief".

ASKER

I revisited each of the settings:
I had set station in VLAN 20 to DHCP
I set static ip and gateway.
Now station on VLAN 20 can ping its gateway 192.168.221.1
switch shows station and gateway in arp table.
switch still cannot ping station on 221.23 and VLAN 20 station cannot pin out of vlan.

Can the VLAN 1 station ping 192.168.221.1?

Can the VLAN 20 station ping 192.168.0.221?

ASKER

interfaces brief:

Status and Counters - Port Status

| Intrusion MDI Flow Bcast
Port Type | Alert Enabled Status Mode Mode Ctrl Limit
----- --------- + --------- ------- ------ ---------- ----- ----- ------
1 100/1000T | No Yes Down 1000FDx MDIX off 0
2 100/1000T | No Yes Down 1000FDx MDIX off 0
3 100/1000T | No Yes Down 1000FDx MDIX off 0
4 100/1000T | No Yes Up 100FDx MDI off 0
5 100/1000T | No Yes Down 1000FDx MDI off 0
6 100/1000T | No Yes Down 1000FDx MDIX off 0
7 100/1000T | No Yes Down 1000FDx MDI off 0
8 100/1000T | No Yes Down 1000FDx MDI off 0
9 100/1000T | No Yes Down 1000FDx MDI off 0
10 100/1000T | No Yes Down 1000FDx MDI off 0
11 100/1000T | No Yes Down 1000FDx MDIX off 0
12 100/1000T | No Yes Down 1000FDx MDIX off 0
13 100/1000T | No Yes Down 1000FDx MDIX off 0
14 100/1000T | No Yes Down 1000FDx MDI off 0
15 100/1000T | No Yes Down 1000FDx MDI off 0
16 100/1000T | No Yes Down 1000FDx MDI off 0
17 100/1000T | No Yes Down 1000FDx MDI off 0
18 100/1000T | No Yes Down 1000FDx MDIX off 0
19 100/1000T | No Yes Down 1000FDx MDIX off 0
20 100/1000T | No Yes Down 1000FDx MDI off 0
21 100/1000T | No Yes Down 1000FDx MDIX off 0
22 100/1000T | No Yes Down 1000FDx MDIX off 0
23 100/1000T | No Yes Down 1000FDx MDIX off 0
24 100/1000T | No Yes Down 1000FDx MDI off 0
25 100/1000T | No Yes Down 1000FDx MDI off 0
26 100/1000T | No Yes Down 1000FDx MDI off 0
27 100/1000T | No Yes Down 1000FDx MDIX off 0
28 100/1000T | No Yes Down 1000FDx MDIX off 0
29 100/1000T | No Yes Down 1000FDx MDIX off 0
30 100/1000T | No Yes Down 1000FDx MDI off 0
31 100/1000T | No Yes Down 1000FDx MDIX off 0
32 100/1000T | No Yes Up 1000FDx MDI off 0
33 100/1000T | No Yes Down 1000FDx MDI off 0
34 100/1000T | No Yes Down 1000FDx MDI off 0
35 100/1000T | No Yes Up 1000FDx MDI off 0
36 100/1000T | No Yes Down 1000FDx MDIX off 0
37 100/1000T | No Yes Down 1000FDx MDI off 0
38 100/1000T | No Yes Down 1000FDx MDI off 0
39 100/1000T | No Yes Down 1000FDx MDI off 0
40 100/1000T | No Yes Down 1000FDx MDIX off 0
41 100/1000T | No Yes Down 1000FDx MDIX off 0
42 100/1000T | No Yes Down 1000FDx MDIX off 0
43 100/1000T | No Yes Down 1000FDx MDIX off 0
44 100/1000T | No Yes Down 1000FDx MDI off 0
45 100/1000T | No Yes Down 1000FDx MDI off 0
46 100/1000T | No Yes Down 1000FDx MDI off 0
47 100/1000T | No Yes Down 1000FDx MDI off 0
48 100/1000T | No Yes Down 1000FDx MDIX off 0

ASKER

vlan 1 station cannot ping 192.168.221.1
vlan 20 station can ping 192.168.0.221

ASKER CERTIFIED SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

I made that change.

vlan 1 station can ping 192.168.221.1 and 192.168.0.221 and 192.168.0.1
vlan 1 station cannot ping 192.168.221.23

vlan 20 station cannot ping 192.168.0.1 or 192.168.0.216

It seems that vlan 20 is still isolated and cannot see out. is there a router entry to give vlan 20 access to vlan 1?

Thanks

ASKER

i have been trying pings from switch and both workstations

station in vlan 20 can now ping 192.168.0.216 and cannot ping 192.168.0.1

Is your latest information since you corrected the default gateway of the vlan 1 station?

At noon (CDT), you state: vlan 1 station cannot ping 192.168.221.1

And most recently, you state: vlan 1 station can ping 192.168.221.1

Please provide the following (verified) information:

1) IP address, mask, default gateway and connected switchport of VLAN 1 station.
2) IP address, mask, default gateway and connected switchport of VLAN 20 station.
3) Current config of switchports connected to vlan 1 and 20 stations.

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

vlan 1 station
IP: 192.168.0.216/24
GW 192.168.0.221

vlan 20 station
IP: 192.168.221.23/24
GW: 192.168.221.1

vlan 1 station can ping 192.168.221.1 and 192.168.221.23 and anything in 0.x subnet

vlan 20 station can ping 192.168.0.221, 192.168.0.216, 192.168.221.1 and nothing else in 0,x subnet

switchport configs have not changed

I have added a return route from the sonicwall at 192.168.0.1 to 192.168.221.x with GW of 192.168.221.1

As you may have noticed my primary LAN subnet is 192.168.0.x
I have set another host in that subnet with a GW of 192.168.0.221 and the station in vlan 20 can ping that host.
SO.. if the host in vlan 1 shares the gateway of the procurve switch vlan 20 can ping that host in 0.x subnet.
the host in vlan 1 cannot ping 192.168.221.23 even if they share the procurve as a gateway.

Am i cluttering up the water for you to isolate a solution?...if so let me know.

ASKER

Took me a bit to get the tftp server running again
Port Configs:

Status and Counters - Port Counters for port 4

Name :
Link Status : Up
Totals (Since boot or last clear) :
Bytes Rx : 122,817,312 Bytes Tx : 25,079,558
Unicast Rx : 217,608 Unicast Tx : 163,273
Bcast/Mcast Rx : 69,967 Bcast/Mcast Tx : 15,743
Errors (Since boot or last clear) :
FCS Rx : 0 Drops Rx : 0
Alignment Rx : 0 Collisions Tx : 0
Runts Rx : 0 Late Colln Tx : 0
Giants Rx : 0 Excessive Colln : 0
Total Rx Errors : 0 Deferred Tx : 0
Rates (5 minute weighted average) :
Total Rx (bps) : 608016            Total Tx (bps) : 520192
Unicast Rx (Pkts/sec) : 10      Unicast Tx (Pkts/sec) : 6
B/Mcast Rx (Pkts/sec) : 1       B/Mcast Tx (Pkts/sec) : 0
Utilization Rx : 00.60 %            Utilization Tx : 00.52 %

Status and Counters - Port Counters for port 32

Name :
Link Status : Up
Totals (Since boot or last clear) :
Bytes Rx : 21,644,751 Bytes Tx : 123,186,683
Unicast Rx : 120,614 Unicast Tx : 175,216
Bcast/Mcast Rx : 14,645 Bcast/Mcast Tx : 64,494
Errors (Since boot or last clear) :
FCS Rx : 0 Drops Rx : 0
Alignment Rx : 0 Collisions Tx : 0
Runts Rx : 0 Late Colln Tx : 0
Giants Rx : 0 Excessive Colln : 0
Total Rx Errors : 0 Deferred Tx : 0
Rates (5 minute weighted average) :
Total Rx (bps) : 5012440             Total Tx (bps) : 5154080
Unicast Rx (Pkts/sec) : 11      Unicast Tx (Pkts/sec) : 14
B/Mcast Rx (Pkts/sec) : 0       B/Mcast Tx (Pkts/sec) : 2
Utilization Rx : 00.50 %            Utilization Tx : 00.51 %

Status and Counters - Port Counters for port 35

Name :
Link Status : Up
Totals (Since boot or last clear) :
Bytes Rx : 99,927 Bytes Tx : 94,942
Unicast Rx : 478 Unicast Tx : 115
Bcast/Mcast Rx : 362 Bcast/Mcast Tx : 470
Errors (Since boot or last clear) :
FCS Rx : 0 Drops Rx : 0
Alignment Rx : 0 Collisions Tx : 0
Runts Rx : 0 Late Colln Tx : 0
Giants Rx : 0 Excessive Colln : 0
Total Rx Errors : 0 Deferred Tx : 0
Rates (5 minute weighted average) :
Total Rx (bps) : 353496            Total Tx (bps) : 1088336
Unicast Rx (Pkts/sec) : 0       Unicast Tx (Pkts/sec) : 0
B/Mcast Rx (Pkts/sec) : 0       B/Mcast Tx (Pkts/sec) : 0
Utilization Rx : 00.03 %            Utilization Tx : 00.10 %

Did you try on your 192.168.0.1 router make a route back to
192.168.221.0/24 via gateway 192.168.0.221 ?

ASKER

A correction to my above info:

vlan 1 station can ping 192.168.221.1 and 192.168.221.23 and anything in 0.x subnet
this is not true... vlan 1 station can ping 192.168.221.1 but cannot ping 221.23 and can ping 0.x subnt

my bad!

ASKER

sonicwall at 192.168.0.1 can ping 192.168.0.221 but cannot ping 221.1 or 221.23
It can ping anyting on the 0.x subnet

ASKER

I changed the gateway on the sonicwall 192.168.0.1 on the route to 192.168.221.0/24 to 192.168.0.221 and now the vlan 20 station can get to 192.168.0.1 and the internet and to anything on the 0.x subnet.

vlan 1 station and all stations on the 0.x subnet cannot ping 192.168.221.23

any ideas?

>Am i cluttering up the water for you to isolate a solution?...if so let me know.

Yes!

Troubleshooting should be performed methodically.

Now we're back to square one.

So let's start back at the beginning.

Please provide the following information:

1) IP address, mask, default gateway and connected switchport of VLAN 1 station.
2) IP address, mask, default gateway and connected switchport of VLAN 20 station.
3) Current config of switchports connected to vlan 1 and 20 stations.
4) Can VLAN 1 station ping it's default gateway?
5) Can VLAN 20 station ping it's default gateway?
6) Can VLAN 1 station ping 192.168.221.1?
7) Can VLAN 20 station ping 192.168.0.221?
8) Can VLAN 1 station ping VLAN 20 Station?

ASKER

1) IP address, mask, default gateway and connected switchport of VLAN 1 station.
2) IP address, mask, default gateway and connected switchport of VLAN 20 station.
3) Current config of switchports connected to vlan 1 and 20 stations.
VLAN 1 Station Port 35:

Status and Counters - Port Counters for port 35

Name :
Link Status : Up
Totals (Since boot or last clear) :
Bytes Rx : 189,462 Bytes Tx : 216,515
Unicast Rx : 884 Unicast Tx : 475
Bcast/Mcast Rx : 400 Bcast/Mcast Tx : 607
Errors (Since boot or last clear) :
FCS Rx : 0 Drops Rx : 0
Alignment Rx : 0 Collisions Tx : 0
Runts Rx : 0 Late Colln Tx : 0
Giants Rx : 0 Excessive Colln : 0
Total Rx Errors : 0 Deferred Tx : 0
Rates (5 minute weighted average) :
Total Rx (bps) : 456400            Total Tx (bps) : 1186976
Unicast Rx (Pkts/sec) : 0       Unicast Tx (Pkts/sec) : 0
B/Mcast Rx (Pkts/sec) : 0       B/Mcast Tx (Pkts/sec) : 0
Utilization Rx : 00.04 %            Utilization Tx : 00.11 %

VLAN 20 station port 32:

Status and Counters - Port Counters for port 32

Name :
Link Status : Up
Totals (Since boot or last clear) :
Bytes Rx : 28,013,310 Bytes Tx : 167,808,662
Unicast Rx : 158,709 Unicast Tx : 241,955
Bcast/Mcast Rx : 17,578 Bcast/Mcast Tx : 76,018
Errors (Since boot or last clear) :
FCS Rx : 0 Drops Rx : 0
Alignment Rx : 0 Collisions Tx : 0
Runts Rx : 0 Late Colln Tx : 0
Giants Rx : 0 Excessive Colln : 0
Total Rx Errors : 0 Deferred Tx : 0
Rates (5 minute weighted average) :
Total Rx (bps) : 4792464             Total Tx (bps) : 5013752
Unicast Rx (Pkts/sec) : 2       Unicast Tx (Pkts/sec) : 2
B/Mcast Rx (Pkts/sec) : 0       B/Mcast Tx (Pkts/sec) : 2
Utilization Rx : 00.47 %            Utilization Tx : 00.50 %

4) Can VLAN 1 station ping it's default gateway? Yes
5) Can VLAN 20 station ping it's default gateway? Yes
6) Can VLAN 1 station ping 192.168.221.1? Yes
7) Can VLAN 20 station ping 192.168.0.221? Yes
8) Can VLAN 1 station ping VLAN 20 Station? No

ASKER

1) IP address, mask, default gateway and connected switchport of VLAN 1 station.
IP: 192.168.0.216/24
GW: 192.1680.221

2) IP address, mask, default gateway and connected switchport of VLAN 20 station.
192.168.221.23/24
GW: 192.168.221.1

Why are you posting the counters for ports 32 and 35?

ASKER

VLAN 1 station is connected to port 32

VLAN 20 station is connected to port 35

I posted 8 questions. None of them asking for traffic counters on switchports.

ASKER

Perhaps this is what you are needing... If not, please be more instructive.
Port Settings

Port Type | Enabled Mode Flow Ctrl MDI
----- --------- + ------- ------------ --------- ----
1 100/1000T | Yes Auto Disable Auto
2 100/1000T | Yes Auto Disable Auto
3 100/1000T | Yes Auto Disable Auto
4 100/1000T | Yes Auto Disable Auto
5 100/1000T | Yes Auto Disable Auto
6 100/1000T | Yes Auto Disable Auto
7 100/1000T | Yes Auto Disable Auto
8 100/1000T | Yes Auto Disable Auto
9 100/1000T | Yes Auto Disable Auto
10 100/1000T | Yes Auto Disable Auto
11 100/1000T | Yes Auto Disable Auto
12 100/1000T | Yes Auto Disable Auto
13 100/1000T | Yes Auto Disable Auto
14 100/1000T | Yes Auto Disable Auto
15 100/1000T | Yes Auto Disable Auto
16 100/1000T | Yes Auto Disable Auto
17 100/1000T | Yes Auto Disable Auto
18 100/1000T | Yes Auto Disable Auto
19 100/1000T | Yes Auto Disable Auto
20 100/1000T | Yes Auto Disable Auto
21 100/1000T | Yes Auto Disable Auto
22 100/1000T | Yes Auto Disable Auto
23 100/1000T | Yes Auto Disable Auto
24 100/1000T | Yes Auto Disable Auto
25 100/1000T | Yes Auto Disable Auto
26 100/1000T | Yes Auto Disable Auto
27 100/1000T | Yes Auto Disable Auto
28 100/1000T | Yes Auto Disable Auto
29 100/1000T | Yes Auto Disable Auto
30 100/1000T | Yes Auto Disable Auto
31 100/1000T | Yes Auto Disable Auto
32 100/1000T | Yes Auto Disable Auto
33 100/1000T | Yes Auto Disable Auto
34 100/1000T | Yes Auto Disable Auto
35 100/1000T | Yes Auto Disable Auto
36 100/1000T | Yes Auto Disable Auto
37 100/1000T | Yes Auto Disable Auto
38 100/1000T | Yes Auto Disable Auto
39 100/1000T | Yes Auto Disable Auto
40 100/1000T | Yes Auto Disable Auto
41 100/1000T | Yes Auto Disable Auto
42 100/1000T | Yes Auto Disable Auto
43 100/1000T | Yes Auto Disable Auto
44 100/1000T | Yes Auto Disable Auto
45 100/1000T | Yes Auto Disable Auto
46 100/1000T | Yes Auto Disable Auto
47 100/1000T | Yes Auto Disable Auto
48 100/1000T | Yes Auto Disable Auto

ASKER

Or perhaps the previous brief listing.

Status and Counters - Port Status

| Intrusion MDI Flow Bcast
Port Type | Alert Enabled Status Mode Mode Ctrl Limit
----- --------- + --------- ------- ------ ---------- ----- ----- ------
1 100/1000T | No Yes Down 1000FDx MDIX off 0
2 100/1000T | No Yes Down 1000FDx MDIX off 0
3 100/1000T | No Yes Down 1000FDx MDIX off 0
4 100/1000T | No Yes Up 100FDx MDI off 0
5 100/1000T | No Yes Down 1000FDx MDI off 0
6 100/1000T | No Yes Down 1000FDx MDIX off 0
7 100/1000T | No Yes Down 1000FDx MDI off 0
8 100/1000T | No Yes Down 1000FDx MDI off 0
9 100/1000T | No Yes Down 1000FDx MDI off 0
10 100/1000T | No Yes Down 1000FDx MDI off 0
11 100/1000T | No Yes Down 1000FDx MDIX off 0
12 100/1000T | No Yes Down 1000FDx MDIX off 0
13 100/1000T | No Yes Down 1000FDx MDIX off 0
14 100/1000T | No Yes Down 1000FDx MDI off 0
15 100/1000T | No Yes Down 1000FDx MDI off 0
16 100/1000T | No Yes Down 1000FDx MDI off 0
17 100/1000T | No Yes Down 1000FDx MDI off 0
18 100/1000T | No Yes Down 1000FDx MDIX off 0
19 100/1000T | No Yes Down 1000FDx MDIX off 0
20 100/1000T | No Yes Down 1000FDx MDI off 0
21 100/1000T | No Yes Down 1000FDx MDIX off 0
22 100/1000T | No Yes Down 1000FDx MDIX off 0
23 100/1000T | No Yes Down 1000FDx MDIX off 0
24 100/1000T | No Yes Down 1000FDx MDI off 0
25 100/1000T | No Yes Down 1000FDx MDI off 0
26 100/1000T | No Yes Down 1000FDx MDI off 0
27 100/1000T | No Yes Down 1000FDx MDIX off 0
28 100/1000T | No Yes Down 1000FDx MDIX off 0
29 100/1000T | No Yes Down 1000FDx MDIX off 0
30 100/1000T | No Yes Down 1000FDx MDI off 0
31 100/1000T | No Yes Down 1000FDx MDIX off 0
32 100/1000T | No Yes Up 1000FDx MDI off 0
33 100/1000T | No Yes Down 1000FDx MDI off 0
34 100/1000T | No Yes Down 1000FDx MDI off 0
35 100/1000T | No Yes Up 1000FDx MDI off 0
36 100/1000T | No Yes Down 1000FDx MDIX off 0
37 100/1000T | No Yes Down 1000FDx MDI off 0
38 100/1000T | No Yes Down 1000FDx MDI off 0
39 100/1000T | No Yes Down 1000FDx MDI off 0
40 100/1000T | No Yes Down 1000FDx MDIX off 0
41 100/1000T | No Yes Down 1000FDx MDIX off 0
42 100/1000T | No Yes Down 1000FDx MDIX off 0
43 100/1000T | No Yes Down 1000FDx MDIX off 0
44 100/1000T | No Yes Down 1000FDx MDI off 0
45 100/1000T | No Yes Down 1000FDx MDI off 0
46 100/1000T | No Yes Down 1000FDx MDI off 0
47 100/1000T | No Yes Down 1000FDx MDI off 0
48 100/1000T | No Yes Down 1000FDx MDIX off 0

ASKER

It now seems to be working the way it should. I did not make any changes since the last posting.
Perhaps it needed to clear cache..or something.

I thank you for your assistance and apologize for the frustration caused.
I will continue adding other vlans and preparing for this to go live.

May i follow with other issues i may encounter?

Tom

>Perhaps this is what you are needing... If not, please be more instructive.

Really?

8 questions and other than two, you need MORE instructions?

3) Current config of switchports connected to vlan 1 and 20 stations.
From the switch, type in "show running-config"
4) Can VLAN 1 station ping it's default gateway?
From the computer that is in vlan 1, type "ping 192.168.0.221" then post here whether the ping
was successful.

And so on...

ASKER

Thank you gentleman for you assistance and patience.
Have a great 4th.