cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1526
Views
0
Helpful
12
Replies

SG300 Vlanning Issue

martyn_jeffrey
Level 1
Level 1

Hi Guys

i was hoping someone could give me a pointer on a Vlan setup issue i am having.

Enviroment

Cisco S300-10 Switch (set to L3 Mode)

I have uploaded a newb drawing of my switch config in the hope it may help

From My Office Pc i see the following symptoms

1) I CAN ping Vlan 2's interface (which is 192.168.1.1)

2) I CANT however ping any of the machines inside Vlan 2 (such as 192.168.1.2)

3) I CANT ping Vlan 3's interface (which is 10.0.0.1)

Worth Mentioning as its not on the drawing i did but the office pc has additional ip addresses 192.168.1.200 & 10.0.0.200

From Vlan 2 I see the following symptoms

1) I CAN ping all other Vlan interfaces (such as 10.0.0.1 & 192.168.0.102)

2) I CAN ping all other machines inside Vlan 2

Vlan 2 Machines have the Vlan interface set as their gateway (i.e 192.168.1.1) I have been reading this link to get it as far as i have

https://supportforums.cisco.com/disc...r-vlan-routing



Any help would be greatly appreciated.



Thanks

Martyn

1 Accepted Solution

Accepted Solutions

On the router do you have routes back to the networks on the switch?

 

For Example:

 

ip 10.0.0.0 sm 255.255.255.0 gw 192.168.0.102

ip 192.168.1.0 sm 255.255.255.0 gw 192.168.0.102

 

And I'll assume that you have a default route on the switch to the router?

 

For Example:

ip 0.0.0.0 sm 0.0.0.0 gw 192.168.0.1

 

View solution in original post

12 Replies 12

phibertron
Level 1
Level 1

The first thing that comes to mind when looking at your drawing

is the potential for the this problem, The problems with asynchronous routing

take a look at this, http://networkguy.de/?p=409

 

Worth Mentioning as its not on the drawing i did

but the office pc has additional ip addresses 192.168.1.200 & 10.0.0.200

 

If your ping issues that your are seeing are being seen on the office pc

it is most likely because it cannot access 192.168.1.0 or the 10.0.0.0 networks

as from the drawing, those vlans are most likely not trunked between the switch and router

and the router would also have to be vlan aware to do this

and the pc would also have to have nic that do do tagging

 

as an example of a good setup

take a look at my last post with pictures in this thread

https://supportforums.cisco.com/discussion/12359971/no-internet-sg300-and-rv320

 

Hey phibertron Thanks so much for your reply.

 

"those vlans are most likely not trunked between the switch and router

and the router would also have to be vlan aware to do this

and the pc would also have to have nic that do do tagging"

 

Well that is true, the Router is not Vlan aware (as far as i know anyway, its only a Dlink ADSL router) although the PC NIC has a setting that says "Priority & VLAN Enabled" (not sure what that means.)

 

so with that in mind please excuse the following questions if they appear silly.

 

1) If the link between the switch and Office PC isnt trunked why can i ping the Vlan interface of Vlan2 but not Vlan3? shouldnt i be prevented from pinging both of them?

 

2) On the Vlan config sheet of my Sg300 all my Vlans are set to "trunked" and my ports set to "untagged".....Is this right?  Forgive my ignorance (i am a vmware and SAN admin so very rarely delve into networks) but my understanding was that if a Vlan was "trunked" it would only allow tagged Vlan's down that path but if it was set to "access" it would send any traffic down that path?

 

Thanks again for your help, it has already pointed me in the direction of solving my inability to png between Vlan 2 & Vlan 3 (Vlan 3 had the wrong gateway in it)

 

Martyn

On the router do you have routes back to the networks on the switch?

 

For Example:

 

ip 10.0.0.0 sm 255.255.255.0 gw 192.168.0.102

ip 192.168.1.0 sm 255.255.255.0 gw 192.168.0.102

 

And I'll assume that you have a default route on the switch to the router?

 

For Example:

ip 0.0.0.0 sm 0.0.0.0 gw 192.168.0.1

 

Hi 

i do have routes on my router to the other subnets

however i had them setup as 

10.0.0.0 sn 255.255.255.0 gw 10.0.0.1 (as i thought that gw would be the vlan ip)

192.168.1.0 sn 255.255.255.0 gw 192.168.1.1 (again as i thought the gateway would be the ip of the vlan)

Let me change these and i will let you know the outcomes 

***EDIT.... Ok after adding the correct info into the router (i.e the gateway on both routes set to 192.168.0.102) i can now ping the 10.0.0.1 Vlan. i still cant ping past that though into the actual hosts within that Vlan.

i have not specifically set a default route on the switch, i have tried to view what the default route is on the switch but i cant seem to find a command or see a section in the gui.

 

***EDIT.....Ok after adding the 192.168.0.1 as the gateway for the switch all of my vlans can now get out via my router to the internet (awesome)  I can also now ping into Vlan3 (so can ping 192.168.1.2 or 3 etc) 

The only thing i cant do now is ping into Vlan2 (my 10.0.0.1 ISCSI) network, but this isnt crucial as its only a storage network and all of the hosts connect to the switch from other Vlans can ping it no problem.

 

i will set it though and let you know

 

thanks again

 

Your Welcome, glad to see you made progress

 

Can you not still ping into the 10.0.0.0 network?

 

Hey Phibertron

 

No unfortunatly not, not from the office pc but i can from the switch and from inside the 192.168.1.x network

"Worth Mentioning as its not on the drawing i did but the office pc has additional ip addresses 192.168.1.200 & 10.0.0.200"

 

what does the route table on the office pc show?

 


IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1      192.168.0.3    266
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.0.0    255.255.255.0         On-link       192.168.0.3    266
      192.168.0.3  255.255.255.255         On-link       192.168.0.3    266
    192.168.0.255  255.255.255.255         On-link       192.168.0.3    266
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link       192.168.0.3    266
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link       192.168.0.3    266
===========================================================================

 

so i guess it sends it to office pc gateway (192.168.0.1) which then should send it to the static route i have in place.

 

Thing is i can ping the 10.0.0.1 interface (vlan 2 interface) so the static route on the gateway is working but i just cant get beyond that Vlan 2 interface into the hosts (2 ESX vmk_)

 

weird

can the esx hosts ping your pc?

are the esx hosts gateways correct?

how is the vswitch on the esx hosts setup?

 

 

Hi Mate

The Esx host can ping the office on Vmk0

 

~ # vmkping -I vmk0 192.168.0.3
PING 192.168.0.3 (192.168.0.3): 56 data bytes
64 bytes from 192.168.0.3: icmp_seq=0 ttl=128 time=1.737 ms
64 bytes from 192.168.0.3: icmp_seq=1 ttl=128 time=3.200 ms
64 bytes from 192.168.0.3: icmp_seq=2 ttl=128 time=6.276 ms

 

not from either of the 10.x Vmk interface i cant ping the office pc

 

~ # vmkping -I vmk1 192.168.0.3
PING 192.168.0.3 (192.168.0.3): 56 data bytes

--- 192.168.0.3 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
~ #
~ #
~ #
~ # vmkping -I vmk2 192.168.0.3
PING 192.168.0.3 (192.168.0.3): 56 data bytes

--- 192.168.0.3 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
~ #
~ #
~ #
~ #
~ # esxcfg-route
VMkernel default gateway is 10.0.0.1

Interface  Port Group/DVPort   IP Family IP Address                              Netmask         Broadcast       MAC Address       MTU     TSO MSS   Enabled Type
vmk0       Management Network  IPv4      192.168.0.153                           255.255.255.0   192.168.0.255   90:e2:ba:0e:cc:20 1500    65535     true    STATIC
vmk1       ISCSI 1 10.0.0.x    IPv4      10.0.0.2                                255.255.255.0   10.0.0.255      00:50:56:60:65:1a 1500    65535     true    STATIC
vmk2       ISCSI 2 10.0.0.x    IPv4      10.0.0.3                                255.255.255.0   10.0.0.255      00:50:56:60:e9:07 1500    65535     true    STATIC

 

Vswitches are just standard vswitches, no vlanning etc.

 

 

 

does the esx host have multiple nics?

Hi Mate

 

yes it has multiple.

 

2 for guest traffic

2 for iscsi traffic

2 for management