The concept of VLAN's are the same on Layer 2 and Layer 3 switches. Wheras on a layer 2 switch, intervlan configuration cannot be performed and an additional device like a router is required for the same. On a layer 3 switch, you can enable intervlan communication on the switch itself and an additional device like a router is not required. So devices on vlan 1 can communicate on devices on different vlan's provide the necessary configuration /devices are available on a layer 2 and layer 3 switch.

q's
1 gateway is a 3750 - i just did a sh ip route - and there is no route to the PHONE VOICE VALN

2 is the device connected to the same switch as the PC and phone connected switch - no not physically - the switch is in a floor rack - the 3750 is in server room - their may be an uplink to the 3750 - im not at work - so cant physically check

Hi,
Ok just an idea: could it be that not the phone is answering when you do your tracert?
Could it be another device? Check for the mac address to make sure. Perhaps one ip adress is set to fixed ip on a device where dhcp should be used, so it comes to an adress conflict.

Perhaps one ip adress is set to fixed ip on a device where dhcp should be used, so it comes to an adress conflict. - hi - not sure what you mean here? - in any case I have pinged several phones on the phone vlan and can ping them all - does that rule out what you are suggesting? - thanks

The 2760 switch should be connected to the 3750 using a trunk link. The PC is on a port on 2760 which belongs to vlan 202. The phone is also on 2760 and is on a port which belongs to vlan 101. 3750 would be configured with IP addresses for respective vlans 202 and 101.

Assuming that the IP address of VLAN 101 is 192.168.1.1/24 and that of vlan 202 is 192.168.2.1/24

Perform the following test

1.

ping the IP address of vlan 101 (192.168.1.1) from the PC. If you are able to get a response, this implies that routing is happening on the 3750 due to which you are getting a response.
Could be because " ip routing" command is provided on the 3750 switch.

2.

Also when you type the command "show ip route" do you see the VLAN IP addresses displayed as directly connected networks ? ( 192.168.1.0/24 and 192.168.2.0/24).

Hi,
When you ping or do a tracert on the given ip-address it could be that another machine answers for that ip. Perhaps someone set it to a fixed ip on some machine which is exactly the ip of your phone. To rule this out look up the mac-address of your ipphone and find the mac of the machine you are looking at in the other vlan. You could use nmap for thatWww.nmap.org

Actually turning off my phone is a very good step to troubleshoot - Can I turn off my phone and still ping another "on" phone from my pc? The cisco engineer thought that maybe my phone was routing somehow. Thanks that gives me something to work on tomorrow.

Well even if there is no hop shown there is some kind of a bridge between both networks.
If you turn one phone off and you cant ping that ip no more it means there is some bridging for sure. If you still get a reply then another device answers for this ip... Then still make a nmap scan of your whole network to see all assigned ips and the corresponding mac-addresses.

If the PC has a 2nd address on the same subnet as the phone and the switch port is trunked,then when you ping the phone, the OS will use the source IP address for the one that is on the same IP subnet.

If you do ipconfig /print then you should see a route for the "phone subnet" that uses the PC's IP address on that subnet.

Beyond its intended purpose of configuring trunk links between switches, ISL is often used in other ways. For example, it is possible to purchase network interface cards that support ISL. If a server were configured with an ISL-capable network card, it could be connected to an ISL port on a switch. This would allow a server to be made part of multiple VLANs simultaneously, the benefit being that hosts from different broadcast domains could then access the server without the need for their packets to be routed. While this may seem like a perfect solution, you need to remember than the server would now see all traffic from these VLANs, which could negatively impact performance.

A more common alternative use for ISL is to connect a Cisco router to a switch in order to facilitate the routing of traffic between VLANs. For example, if you wanted to route traffic between VLANs 1 and 99 in a non-ISL environment with one switch, you would need to connect the router to both a port on VLAN 1 and a port on VLAN 99, as shown below.

Today you will see more and more switch port's configured as trunks for the sole purpose of VIOP. Instead of running two LAN stations to each cube, there is one LAN station that the computer and VOIP traffic share. However, you need to isolate the traffic so you use VLAN's.

Typically the VOIP traffic will have tagged traffic and the computer will have untag'ed.

Notice I said VOIP traffic and not phone. This is because the VOIP traffic can either be a phone or software running on the computer.

It sounds like you have access to the switch config, so see if the switch config for that port has:

switchport trunk native vlan ###

Where ### is either 201 or 202. If it has this, then the VLAN number specified is un'tagged. If it does NOT have this, then the native VLAN is defaulting to VLAN 1 and both 201 and 202 would be tagged VLANs.

Meet the world's only “Transparent Cloud™” from Superb Internet Corporation. Now, you can experience firsthand a cloud platform that consistently outperforms Amazon Web Services (AWS), IBM’s Softlayer, and Microsoft’s Azure when it comes to CPU and …

After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail. The methods are covered in more detail in o…