Routing vlan traffic out from SGE2000P

[jsotocisco]

We have one SGE2000P switch that we are testing in Layer 3. We have a very simple configuration with some vlans that we want to route to our corporate network, but I want to test if there is actually traffic coming out from the up-link port first.

1- Created the vlans:

VLAN1:     10.10.1.12 /16 (native)

VLAN10: 172.16.10.1 /24

VLAN20:  192.168.0.1 /24

2- Assigned ports to VLans:

Port g3 is in Vlan 10

Port g22 is in Vlan 20

Port g1 is by default on Vlan 1 (native)

3 - Connected PCs to Vlans:

PC connected at g3 has Vlan 10 IP as gateway (172.16.10.1)

PC connected at g22 has Vlan 20 IP as gateway (192.168.0.1)

4 - Looks like intervlan routing is working 'cause both PCs can ping each other.

5 - I added a default route to another testing machine's IP, ie, 0.0.0.0 /0 10.10.0.1 connected to port g1, but the ping doesn't work.

Now the questions:

1 - How can I test if there is traffic being routed to port g1 from the vlans ???

2 - What else do I need to add in the switch config to take traffic out from the vlans to Port g1 ???

For reference, the sw's running-config:

console# show running-config

vlan database

vlan 10,20

exit

interface ethernet g3

switchport access vlan 10

exit

interface ethernet g22

switchport access vlan 20

exit

interface vlan 1

ip address 10.10.1.12 255.255.0.0          

exit

interface vlan 10

ip address 172.16.10.1 255.255.255.0

exit

interface vlan 20

ip address 192.168.0.1 255.255.255.0

exit

ip route 0.0.0.0 0.0.0.0 10.10.0.1 

console#

Any help / comment is much appreciated.

Thanks in advance,

jose

[rocater]

Hello Jose,

In order for a vlan to be active, you will have to have something connected to a port on that vlan. In this case you should be able to add a PC to port g1 and set it to be 10.10.1.1 with gateway of 10.10.1.12.

If you are looking to add a router in place as the main way out to the internet, you will:

have to have the router IP be 10.10.1.1

add a static route in the router for each subnet pointing back to 10.10.1.12

With the ip route already in there for 0.0.0.0 to 10.10.1.1, you should be able to get online.