PC6224 Trunking/routing

Hi,

The other switches only need to be aware of the VLANs that are directly connected to them. Anything that it doesn’t know where to send it should go out the default route, which should send the traffic to the 6224 and that should route it to the correct VLAN. Can the switches ping the 6224? If you run show ip route on the 6224 does it show the correct ports for the VLANs. What type of switches are the other switches?

PC->6248->2910->6224

This is correct.  Everything there is on VLAN 1 and untagged.  I did not trunk the port on the 2910.  When I set the 6224 port as trunk I couldn't even access VLAN 1.  VLAN 1 will continue to be untagged, and the other VLANs will be tagged.  I will see if I can get a PC plugged into it directly, but that would be an untagged/VLAN 1 PC right now.

So it is PC->6248->2910->6224? What VLAN is that on? That is all the same VLAN through the 2910? Is it a trunk port between the 2910 and the 6224? Is all of the traffic tagged between those two switches, you might want to change the port type of the 6224 to trunk instead of general if it is and see if that works better. Are you able to plug a PC directly into the 6224 and make sure routing works there?

I can ping the management IP of the 6224, but not the VLAN IPs.  Show IP Route on the switch does show all of the networks as directly connected.  

My PC is connected to a PC 6248 (no configuration), and there are some PC 2848s as well.  They all uplink through an HP 2910AL.

can the management IP be on the same subnet as the untagged VLAN?

VLAN 1 is the management VLAN by default and is not routable. You can move the management VLAN or can use a different VLAN for your untagged traffic. Use the following command to change the management vlan. console(config)# ip address vlan 999

Whichever VLAN is the management VLAN can’t be routed. However you can still manage the switch from the VLAN IP address. So if you moved the management VLAN to something else and VLAN 1 was then routable you could access the switch from the IP address assigned to VLAN 1

Current config after attempting to trunk uplink port:

console#show running-config

!Current Configuration:

!System Description "PowerConnect 6224, 3.3.2.3, VxWorks 6.5"

!System Software Version 3.3.2.3

!Cut-through mode is configured as disabled

!

configure

vlan database

vlan 110-119,999

vlan routing 110 1

vlan routing 111 2

vlan routing 112 3

vlan routing 113 4

vlan routing 114 5

vlan routing 115 6

vlan routing 116 7

vlan routing 117 8

vlan routing 118 9

vlan routing 119 10

vlan routing 1 11

exit

stack

member 1 1

exit

ip address none

ip address vlan 999

ip routing

interface vlan 1

routing

ip address 10.1.0.110 255.255.252.0

exit

interface vlan 110

routing

ip address 10.1.10.1 255.255.255.0

exit

interface vlan 111

routing

ip address 10.1.11.1 255.255.255.0

exit

interface vlan 112

routing

ip address 10.1.12.1 255.255.255.0

exit

username "admin" password  level 15 encrypted

ip ssh server

management access-list "SSH"

permit ip-source 10.1.0.0 mask 255.255.252.0 ethernet 1/g1 service ssh priority 1

exit

!

interface ethernet 1/g1

spanning-tree portfast

switchport mode trunk

exit

!

interface ethernet 1/g2

spanning-tree portfast

switchport mode general

switchport general allowed vlan add 110-119 tagged

exit

!

interface ethernet 1/g3

spanning-tree portfast

switchport mode general

switchport general allowed vlan add 110-119 tagged

exit

!

As soon as I created and did the ip address for VLAN 999, I lost config access.

is 10.1.0.110  not pingable from the PC?

correct, although it was before vlan 999 (though as you can see, it was not specific to vlan 1, but the switch IP at that time).  I moved it to vlan 1 to try to get it to work.  The HP2910 is also now trunked for the uplink port to try to get it to work.

Leave the ip address on vlan 1 and just have vlan 999 have nothing configured.  

Ok, switched port back to general and that's got it up and running with the pvid.  Should I be able to ping the IPs of the other VLANs as is?  (also added other vlan: switchport general allowed vlan add 110 tagged)

interface ethernet 1/g1
spanning-tree portfast
switchport mode general
switchport general allowed vlan add 110 tagged
exit

ok, so ping from PC>6248>2910>6224 VLAN 110 does not currently work. Do I need to create the VLANs on the 2910 and assign them to the 6224 uplink port (or just create them since the port is trunked)?

yes the 6224 should be able to route to to the other vlans.