cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1635
Views
0
Helpful
4
Replies

Really need help with c3560 vlans and routing

lemon1985
Level 1
Level 1

Hi Guys,

I am having a bit of trouble configuring a c3560 switch at the moment. Basically I work for a small business, and I am in the process of a big upgrade including servers/storage/networking. Networking is not really my strong point, I will admit that at the outset.

So I have 2 server racks setup in my server room, the old and the new. The new rack has in it a c3560 switch I purchased as I would like to (eventually) be using this as our new core switch. It goes back to 3x IBM x3850 M2 servers running VMware with 4x nic ports each. Then 4x Cat cables from each ESX host running into the c3560 switch. I then have a seperate HP 2626 switch for iSCSI host/array traffic, but that I am not too worried about.

Our existing network is 172.16.2.X 255.255.254.0

Basically what I want to achieve is mutiple VLAN's on the c3560 for stuff like VMware vMotion and Console traffic. I will then tag the ports on the Virtual switchports from within vmware. That's all well and good and I have done that before, my main problem is getting communication happening between VLAN 1 and VLAN 2, it's just not happing.

Our current switch in the old server rack is a layer 2 HP 1800 series. So far I have:

Ran a cable from the old 1800 to the new c3560 switch. The c3560 then gets a 172.16.2.145 DHCP address on vlan1. I can hit the web interface from my machine.

I hooked a serial cable up to a PC so I can console in as well. I created VLAN 2 called (Servers) and gave it IP 10.1.10.1 255.255.0.0

Then on one ESX host I gave it an IP of 10.1.10.10 and DG 10.1.10.1 with corresponding mask. Now how do I get to the point where I can ping the ESX host on 10.1.10.10 from my work machine on 172.16.2.89?

There are HP switches in between, do I need to do config on these? My machine goes back to DW 172.16.2.254 which is a sonicwall firewall device. Is the config only done on the c3560 for this to happen?

Any info you need let me know.

Cheers,

James.

1 Accepted Solution

Accepted Solutions

Hi Jame,

all you need to do for inter-vlan routing is, to enabel ip routing on ur switch as Ameya wrote up there and make sure all your vlan interfaces (SVI) in the c3560 has a fixed ip address that wont change, and setup ur stations in different vlans with correspoding default gateway (respective SVI ip's).

layer 2 switches with default configuration (no VLAN settings) shouldn't be a problem in the network.

Hope it Helps,

Soroush.

Hope it Helps!

Soroush.

View solution in original post

4 Replies 4

lemon1985
Level 1
Level 1

By the way the ESX host can ping DW OK on 10.1.10.1

It can also ping the switch IP on 172.16.2.145 from the ESX host on 10.1.10.10. I cannot get anything on the 172.16.2.X range, hooked up to the c3560 to ping anything on VLAN 2, ie 10.1.10.X range. The ESX host also cannot get out past the switch, ie it can ping the switch on 172.16.2.145, but nothing outside of the switch itself.

I think I need static routes in place, I jsut don't know how to do it.

Cheers.

HI,

On 3560 go to configuration mode and enable "ip routing" command.

Check if you can ping between Vlans.

RTR(conft)#ip routing

Ameya Oke

Hi Jame,

all you need to do for inter-vlan routing is, to enabel ip routing on ur switch as Ameya wrote up there and make sure all your vlan interfaces (SVI) in the c3560 has a fixed ip address that wont change, and setup ur stations in different vlans with correspoding default gateway (respective SVI ip's).

layer 2 switches with default configuration (no VLAN settings) shouldn't be a problem in the network.

Hope it Helps,

Soroush.

Hope it Helps!

Soroush.

Thanks both for your help guys. I was doing something really n00b. The PC that I was testing on had a 172.16.2.X address given out by DHCP and was directly connected to the our new Cisco c3560 switch with IP 172.16.2.129. I then had the ESX server on 10.1.10.10 but could not ping from the PC to ESX.

In short, even though the PC could ping the c3560 at 172.16.2.129, intervlan routing was not working because it had pulled a DHCP lease with DG as 172.16.3.254. This device is a sonicwall firewall which had no routes defined.

Changed the PC to static IP on 172.16.2.X with DG as the cisco switch on 172.16.2.129 and ping went OK to 10.1.10.10

Lesson learnt, always check DG's!!!!!!!!

Cheers.

Review Cisco Networking products for a $25 gift card