Catalyst 3560 Inter-VLAN routing

Hello. I'm trying to figure out how to get a 3560 to route between its VLANs. I have the following:

ip routing

interface Vlan6
 ip address

interface Vlan49
 ip address

sho ip route shows this:

Gateway of last resort is not set is subnetted, 3 subnets
C is directly connected, Vlan49
C is directly connected, Vlan6

I can ping a device on vlan 49 but if I source it from vlan 6 I get no responses.

Does the 3560 not automatically route between connected interfaces when "ip routing" is enabled? I'm missing something basic, I know.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

That should be enough to make intervalan routing work.
Check default gateways on hosts. - should be set as default gateway for hosts in Vlan49 - should be set as default gateway for hosts in Vlan6

For switch part, what is output whe you issue
# show ip interface brief

Try to ping SVI for local VLAN (VLAN49), try to ping SVI for destination VLAN(VLAN6), and then try to ping host in VLAN6.

Try to traceroute to see where ping dies :)
jconklin-ansinc-netAuthor Commented:
Right now I'm just pinging from the switch. The gateway on the device is It responds to ping unless I source it from vlan 49.

PING (device on VLAN 49, its gateway is

Sending 5, 100-byte ICMP Echos to, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/4/9 ms


SW#ping source vlan 6

Sending 5, 100-byte ICMP Echos to, timeout is 2 seconds:
Packet sent with a source address of
Success rate is 0 percent (0/5)

Protocol [ip]:
Target IP address:
Source address:
Tracing the route to

  1  *  *  *
  2  *  *  *


Interface              IP-Address      OK? Method Status                Protoco
Vlan1                  unassigned      YES NVRAM  administratively down down
Vlan6                 YES NVRAM  up                    up
Vlan499           YES manual up                    up
Does not make any sense, that should work.
Try to reload switch.
# reload
Save configuration before reload (you will be prompt).

Can you paste your current config?
And check ports assigned to hosts.

Also issue and paste results here
# sh vlan
Become a Microsoft Certified Solutions Expert

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

What is your IOS version and licence type? LAN base licence don't support intervlan traffic.
# sh version
# show license detail

As a rule of thumb, any newer 3560-E, 3560-X, 3750-E or 3750-X switches must be purchased with the IP Base license in order to support InterVLAN routing. The LAN Base license will allow Switched Virtual Interfaces (VLANs) to be created, however, it does not support InterVLAN routing or IP routing.
jconklin-ansinc-netAuthor Commented:
The license is C3560-IPBASE-M.  "IP routing" command is enabled.

I thought with both subnets showing as "directly connected" that routing between them would be automatic. Is that accurate?
Yes it is.

You did not paste output from show commands, so I am in the dark here...
You mention in posts and # sh ip route
displays VLAN 49 and VLAN 6 as connected interfaces,
BUT  outputs from # sh ip interf brief     and # sh ip route      are inconsistent

C is directly connected, Vlan49

Vlan499           YES manual up                    up

Again Check # sh vlan
for ports assign to VLANs :)

It is possible that vlan.dat files is corrupted.
My suggestion would be reset switch

# erase startup-config           <-- or # write erase
# reload
# delete flash:vlan.dat

Don't save configuration during reload(s), and configure switch again.
Also, just in case ... create VLANs before creating interfaces for VLANs.
jconklin-ansinc-netAuthor Commented:
I ended up using a router as the gateway instead of the switch as this was taking too long.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jconklin-ansinc-netAuthor Commented:
This thread became moot as I needed to provide an alternative solution.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Architecture

From novice to tech pro — start learning today.