J1mb08agg1n5

Any particular reason why wireless devices may become severely bandwidth throttled, but not wired? Currently managing 25 Ruckus R510 11ac Wave 2 access points controlled by a ZoneDirector 1200 and randomly sometimes , internal connection speed on a wireless connection becomes severely degraded to about <1Mbps. I have carried out multiple iPerf tests on a wireless and wired connection to our main DC and with it being hardwired it's fine, but on wireless it's not. It's temperamental and intermittent. Tested on multiple devices and the issue seems to only pertain to wireless devices. For troubleshooting, I attached my laptop to an AP that connects into a Cisco SG350-28P as well as hardwiring in into the same port and again, connected wirelessly it's severely degraded but hardwired it's not. I even connected my laptop into the passthrough port on the R510 and it was fine. I can't explain it. My only thought is possibly the wireless system struggling with encryption and decryption so I was going to test this on an open network. My fall back option would to factory reset it and rebuild it from the ground up. I can't imagine it being a physical issue but maybe wrong. Just seems like it's being throttled massively somewhere or by something. There are no network policies or configurations in place that should be causing this. Any troubleshooting ideas, steps, testing I may be able to carry out to identify what on what might be causing this would be very much appreciated.

Experiencing a weird issue that I'm struggling to explain or fathom, wondering if someone would be able to explain or at least point me in the right direction. Small mobile that is connected to the main building via a single CAT5E cable. It has very minimal device usage with 1 desktop 2 laptops per room and one AP to service both areas. One PC and laptop are completely fine but the other PC and laptop that are in the other room, dead slow. They are both identical in spec and cables go into the same switch and traffic traverses the same uplink into the main building which contains servers, firewall and router. Changed over to a brand new switch as well as patch cables and still same. Also checked 802.1Q VLAN tags on switch ports and all is fine. It is quite a simple VLAN segmentation for wired and wireless devices, they obtain IP addresses fine from DHCP. Cisco L3 switch acting as the gateway for any inter-VLAN routing. External FTTC line and router are a few hops away from main server. Internal and external speed tests show one PC and laptop operates at a crawl, whereas the other is completely fine. Other areas are also OK, it's just this one particular area. From a physical standpoint, the uplink is truncated to an old Netgear switch which when I was doing MTR, iPerf and PathPing tests to it's static IP, it was dropping packets so potentially an issue here but still can't explain why one set of devices have an issue and and another set doesn't. Only thing I can think of is if there is bandwidth limiting or QoS being employed somewhere. Any help would be greatly appreciated.

Hi all. Have a small issue trying to deploy one particular Yealink SIP-T30P. Network is VLAN'd, for simplicity default VLAN is 1, voice VLAN is 50. L3 switch is configured as the default gateway and IP helper is pointing towards DHCP server situated in VLAN1. It can acquire IP in VLAN1 but not for VLAN50. Initial thought was checking that ports are configured correctly which I have verified that they are. As I test, I unplugged a working phone and plugged the cable into the non-working phone, still no IP which I can't fathom why. Port hasn't been changed and settings on the phone are the same, so can't explain why one works and one doesn't but it will work when I assign it to VLAN1. Any suggestions or troubleshooting ideas?

Currently in the process of carrying out a simple VLAN'ing task by separating a small businesses IP phones away from their main network. They currently have a Draytek 2862 router, 2 x TP-Link T1600G-52TS, Cisco 7800 series IP phones and a server running Server 2012 R2 that supplies DHCP to the entire site. The topology is simple and looks like this; Server + IP Phones <----> TP-Link SW1 <----> TP-Link SW2 <----> Router Main network has an IP address scheme of 10.13.166.0/24 that is by default VLAN1 and I want to create a 10.13.170.0/24 network set as VLAN50 for the IP phones. Idea was to create a separate scope within DHCP, use the Draytek for L3 routing and gateway for both VLANs , trunk the switch ports that carry the link with the appropriate VLAN IDs, then set whatever ports the IP phones are connected to the correct VLAN. I thought this would be quite simple but I just can't get it to work. This is what I have done so far: DHCP Created scope for VLAN50 labelled Voice with a scope of 10.13.170.0/24 Enabled distribution from .10 - .254 DHCP options - router set as 10.13.170.1. DNS as 10.13.166.12, this is the server IP. Secondary as 8.8.8.8 Draytek Enabled VLANs. Created LAN2 with a gateway IP of 10.13.170.1 and subnet 255.255.255.0. LAN1 is already created with gateway IP of 10.13.166.1 and subnet 255.255.255.0 Enabled DHCP relay on LAN2 to point to the DHCP server on 10.13.166.12 residing on LAN1. Also done this for DNS with a secondary as 8.8.8.8 Enabled InterVLAN Routing so that IP phones in VLAN50 can communicate with DHCP and DNS in VLAN1. Routes have been created for both LANs, verified in routing table Set VLAN0 across all 4 ports for LAN1. This indicates all untagged traffic belonging to default VLAN1 Set VLAN1 only on port 1 set as LAN2 with PVID enabled and set as 50, as in VLAN50. P1 is the port that links or is cabled into SW2 Switches Created VLAN1 and VLAN50 on both switches Set ports as trunked. This includes the link between both switches, server and router port as untagged 1 and tagged 50. Set them to point to DHCP server IP in VLAN1 Know this isn't actually necessary but created a static IP on both switches for VLAN50 I haven't set the ports for the IP phones yet as I wanted to carry out a simple test with my laptop first. So what I have done is set a spare port on SW2 as access port with a PVID as 50 to make sure that when I plug my laptop in, I should get an IP from the VLAN50 scope but I don't, I just get 169 address, and this is what is confusing me. Obviously not communicating with DHCP but thought I'd set everything correctly for it to do so. Honestly, you can call me stupid as it might be glaringly obvious but I was scratching my head for a couple of hours until I decided I needed to walk away and come back with a clear head. Any help would be appreciated it. I am just going over it all again right now but thought I'd ask as another pair of eyes might be handy.

Yes the are on the same subnet. Attached is a spreadsheet I have managed to put together that lists all the network details I have been able to gather, so not exactly a map but I have listed all IP schemes, IPs, trunk ports etc. that hopefully might better explain what I am dealing with. Today, for a brief moment, the switch in the small centre (.118 in the attached sheet) was able to communicate with everything over in the main complex but then stopped and ping tests went back to "request timed out". Don't know what happened there. I also re-configured STP on both switches and it elected the correct root bridge according to all the other switches in the main complex, so communication must be there as it managed to learn the correct one and select the trunk port as the root port. Bit of a head scratcher so far but I do really appreciate all the responses so far, regardless of how small. Network Details.xlsx

Took another visual look at the truncation today and the activity on the switch port LEDs did seem very erratic to the point that they are constant. Was mainly looking at Cisco switches so don't know if that's how they usually behave but did seem a little full on. Could I be looking at a potential network loop somewhere or do you think I am clutching at straws? Any other suggestions or troubleshooting roads I could go down as I am starting to run out of ideas.

Also here is a very quick and basic network topology, if you need me to go in more depth then I can, it's just what I could muster up in the time. Like I said, all devices have static IP's within VLAN1 IP scope. I am positive I have checked all truncated ports to ensure they are trunks with VLAN1 untagged and all other VLANs tagged.

I will whip up a diagram when I get the chance. Just walked into this issue this morning with scarce documentation apart from a list of switch credentials and truncated ports so I have the outlay of the network in list form. DC01, DC02 and the main centre switch all have static IP's within VLAN1 IP scope and connected switch ports are set to access with VLAN1 as untagged. The link is a single strand fibre that connects into a ADVA FSP150CP optical fibre access switch on either end which are then connected by multimode fiber into a SFP switch port. These switch ports are set to trunk with VLAN1 untagged and all other VLANs tagged. Below is the diagram for it: https://ibb.co/mDkXGMn

The VOIP install happened on both sites plus a Voice VLAN was already in place, so all they needed to change was switch port VLAN assignment. I'll have to get their contact details to double check but as far as I am aware and can see, the supplied phones were set to acquire addressing via DHCP. The only anomaly that I can see is they run out of POE switch ports in the cab where the leased line comes in, so they supplied the site with a temporary switch. It is a managed Netgear but I have no clue of how it was setup and unfortunately don't have the credentials to check. As far as I am told, the link port on this switch was only set to access the voice VLAN and is linked into the exact switch that the multimode fiber is patched in for the leased line to the small centre. There are a bunch of POE phones plugged into it at the moment but they are all working. I am tempted to remove the link to this switch to see what happens but would have to do it out of hours.

Yeah it's strange. It was apparently all working 3 weeks ago and the only thing that changed is VOIP installers came in 2 weeks ago, so that's why I think it maybe potential VLAN tag related as they might have been messed up some of the tagging. Also checked variables on DHCP on both DC01 and DC02 and can confirm they are correct or as they should.

Just inherited a problem at a site that has a main building complex then a small centre about a 1KM away that's physically linked by a dedicated leased line. The overall issue is that the centre has no network connectivity, whereas the main complex is fine. The entire network is logically segmented into VLANs . Everything in the centre is configured to feed off the main complex (i.e DHCP, DNS, WiFi, Internet etc.) where all of the core devices reside. Core devices (servers, switches, router etc.) sit within VLAN1 on a 10.12.12.0/24 network. Backbone consists a mixture of Cisco SMB, TP-Link and Netgear switches all with static IP's. RSTP has been enabled on all switches. A L3 Cisco SG300 is set as the gateway and carries out the inter-VLAN routing Gateway IP exisits for each VLAN and DHCP helper has been enabled and set to the main DC. The main DC (DC01) is situated within another cabinet in the main complex away from where the link between both buildings comes in, so at present, there are several truncated switches in between to the main DC. This handles all VLAN addressing. They do have a failover DC (DC02) that is situated at the centre. Both have static IPs. Now, I can ping DC01 to DC02 and vice versa and I can also remote into DC01 and RDP over to DC02, so I know for sure that the physical link is intact. However, I can't ping or access the centre switch IPs from DC01, however, I can ping and access any switch for the whole site from DC02. I don't see how I can ping and remote from DC to DC but can't ping the centre switches from the other side as I thought that by default, all untagged packets would be associated on VLAN1, where all the core devices sit plus traffic must go through switches on either side or order for me to connect from DC to DC. This might need some clarification on how this works. Today was just a fact finding mission so I should have the tools and access to troubleshoot going forward. What I have checked so far is making sure all switches and truncated ports are set correctly, set to trunk then VLAN1 as untagged with all other VLANs as tagged. What I would like to test is where traffic is potentially being dropped and/or if VLAN ID's are traversing across the leased line correctly. Traceroute doesn't work for anything internal as it either drops straight away or shows me 1 hop which i would expect. Be interesting to know if anyone has had experience with Wireshark to set this up and point out what I would be looking for. Also below is a basic visual representation of the ping tests I have carried out: DC01 <----> DC02 - OK DC01 <----> Main Centre Switch - Unreachable DC02 <---> Any Switch - OK Like I said, main complex is fine but for some reason, no devices connected to the switches in the centre can obtain a DHCP address from it's respective VLAN, even when connecting to a port I've set to VLAN1, but I can communicate from DC to DC. Just wanted to brainstorm potential causes and ideas on where and what to troubleshoot to see if I can find anything glaring or missing. Any tips and/or explanations would be greatly appreciated.