<div>
Also to note, First time using VOIP as well (have around 30 phones connected, no QoS is configured yet). The only VOIP phones are connected to the Dell N1548P, and workstations connected to the Phone switch which hands out an IP on VLAN100.
</div>


<div>
How are you measuring the latency? &nbsp;How long does it last?<br />
<br />
Some things to look at:<br />
<br />
Run a traceroute during times of good performance and bad performance. &nbsp;This can highlight routing issues.<br />
<br />
Check port utilization during times of good performance and bad performance. &nbsp;This can highlight congestion issues.
</div>


<div>
Basically, i had users complain about the speed of one of their applications. When i began to ping that server from inside VLAN100 (server is on VLAN300), pings came back ranging &nbsp;from 200-800ms.<br />
<br />
As a temporary fix, i just put the server on VLAN100, but long term i want to find out what the &nbsp;issue is.
</div>


<div>
I had another person in a similar situation, and it ended up being a bad port on the switch.<br />
<br />
I suggest you test other machines on the same subnet, and see whether the issue is with that server, or with the entire subnet.
</div>


<div>
From topology itself and your description I guess there could not be definite answer. <br />
My guess is that you either have some network loop or wrong switch is root bridge (if topology is L2).<br />
If there is a network loop CPU is overloaded, so check CPU usage on switches. <br />
Lower STP priority on a switch that should be core of your network (again if that is L2 topology). Just notice that in this case there will be 30-50 seconds of downtime until STP reconverges.
</div>


<div>
Hi JAntkiller,<br />
<br />
Kindly confirm if the latency is faced for a specific server in vlan 300 from a specific server in vlan 100 or is it random.<br />
Install ping plotter on your local workstation to ping a server in vlan 300 and configure the settings such that a notification is sent in case of any abrupt increase.<br />
Verify the source based traceroute and corresponding vlan interfaces / port errors,CRC's and utilization to isolate the cause.
</div>


<div>
Hi,<br />
<br />
<br />
The latency issue is not related to a specific server.<br />
<br />
And the tracert shows only 1 hop.
</div>


<div>
Hi <br />
<br />
Does the trace get completed?
</div>


<div>
Are the servers still in the same VLAN?
</div>


<div>
Negative all of the servers are on a sperate VLAN (for the time being however, i did put one of my servers on the vlan that is having issues, and that did solve the latency problem for the clients within that vlan.)
</div>


<div>
After more investigation, i found a few things out.<br />
<br />
1. The Sonicwall is experiencing high CPU utilization during file transfers to different VLAN's<br />
2. The Primary backbone switches (Dell 5524P's are L2 Switches)<br />
<br />
Do i need a layer 3 switch?
</div>


<div>
<div class="content wysiwyg-content">
Hello All,<br />
<br />
I am experiencing latency issues with my VLANS.<br />
<br />
Users on VLAN100 are experiencing occasional high latency to servers on VLAN300.<br />
<br />
<br />
I feel as though its a configuration issue, but am not sure...i fee like packets are being routed incorrectly, but I am a newb and not sure how to diagnose this issue.<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/03_w10/1084765/networkissue.jpg" target="_blank" title="Diagram of Switch Layout (80 KB)"><img alt="Diagram of Switch Layout" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2016/03_w10/800_1084765/networkissue.jpg" /></a>
</div>
</div>


networkissue.jpg

Hello All,

I am experiencing latency issues with my VLANS.

Users on VLAN100 are experiencing occasional high latency to servers on VLAN300.


I feel as though its a configuration issue, but am not sure...i fee like packets are being routed incorrectly, but I am a newb and not sure how to diagnose this issue.



Inter VLAN Latency

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.

Network Architecture

A switch is a device that filters and forwards packets of data between LAN segments. Switches operate at the data link layer or the network layer of the Open Systems Interconnection (OSI) Reference Model and therefore support any packet protocol. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs. A hub is a connection point for devices in a network. Hubs are commonly used to connect segments of a LAN. A hub contains multiple ports; when a packet arrives at one port, it is copied to the other ports so that all segments of the LAN can see all packets.

Switches / Hubs

A router is a networking device that forwards data packets between computer networks. Routers perform the "traffic directing" functions on the Internet. The most familiar type of routers are home and small office cable or DSL routers that simply pass data, such as web pages, email, IM, and videos between computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, use of software-based routers has grown increasingly common.

Routers

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.