Top Wireless Client Bandwidth Utilization on WCS?

Hi, there.
Can I get the top wireless client bandwidth utilization info / report from WCS? I would like to know how high they can reach, and how many are those 'power users', so far I only find "Busiest Clients" but not quite certain sure about the meanings of the "threshold" and "utilization' besides, the minimum interval is 1 hour, which seems to long for me, I would like to have some data like MRTG which is in 5 minutes range, thanks.
Leo

Welcome to the discussions!
There is no "relay" function in the "extend a wireless network" setup. Each AX that is set to extend communicates directly to the Time Capsule and not to another device that might be between it and the Time Capsule.
If you need the "relay" function, your only real option to setup the WDS configuration to see if that might work better in your circumstance.
When you say that you have one AX setup as a client only, this implies that it is set to "join a wireless network". In the "join" setting, the AX only receives a wireless signal, it does not "extend" or rebroadcast the wireless signal. You might want to try setting this device to "extend" to see if that might help the network performance.

Similar Messages

-1 (Minus One) Wireless Client Rate for networked PCs with Ariport Express

Trying to figure out connection problems...
Under Airport Utility > Advanced > Logs and Statistics > Wireless Clients...
My MBP gets a Rate 54Mbps when I am beside it in my room, but sometimes drops down to 11 or so and then goes back up. I think this is why I am losing my AirTunes connection.
Both PCs on the network are farther away but are showing a Rate of -1Mbps, even when they are brought into the same room as the APX.
Any thoughts.

1. How does the client device know which Airport to connect to?
The Mac computer will automatically connect to the wireless access point with the strongest signal...which is probably the closest AirPort. An iPhone or iPad may not do this and will tend to stay connected to one AirPort.
2. How can I tell which of the Airports the attached client device is using?
On a Mac, open Macintosh HD > Applications > Utilities > AirPort Utility. Click on one of AirPorts. In the area to the right, locate the AirPort ID and jot that down. Then do the same for your other AirPort.
Move your Mac near one of the AirPorts and log on to the wireless. Hold down the option key on the Mac while you click the fan shaped AirPort icon at the top of the screen. Look for the BSSID. That is the AirPort ID of the device to which you are connected.
If you are close to the "remote" AirPort, and you see the AIrPort ID of the "main" router when you are testing, then you know that the network is not configured correctly.
Can I use this second Airport Express to extend the wireless network via "Extended Wireless Network" while the other two are in "Roaming Netowrk" configuration? Without bogging down??
There will be a modest 10-15% bandwidth loss with the "extend" setup, assuming that the Express is located where it can receive a strong wireless signal from the AirPort to which it is associated. You can avoid the bandwidth loss if the Express is also connected via Ethernet as part of the roaming configuration.

Limit client bandwidth per SSID?

Is there away to limit each clients bandwidth at the AP per SSID?
Any help is greatly appreciated.

You can use QOS to do this. When you configure QoS on the access point, you can select specific network traffic, prioritize it, and use congestion-management and congestion-avoidance techniques to provide preferential treatment. Implementing QoS in your wireless LAN makes network performance more predictable and bandwidth utilization more effective. For more information on this read the document available at http://www.cisco.com/en/US/products/hw/wireless/ps430/products_configuration_guide_chapter09186a00804e7d2d.html

I cannot get my Airport Express to accept wireless clients.

I cannot get my Airport Express to accept wireless clients. After resetting to factory default and reconfiguring, it works briefly but then stops again.
The Airport Express is on the second floor of my house and is seen by Airport Utility. Using a LAN cable with the Express works no problem.
My network is created by an Airport Extreme (ground floor) and extended by a Time Capsule (first floor)
Have run through all settings repeatedly and as I said I can get it to work briefly by resetting and then reconfiguring, but after a short while again my iOS devices can no longer connect and revert to cellular.

I cannot get my Airport Express to accept wireless clients. After resetting to factory default and reconfiguring, it works briefly but then stops again.
The Airport Express is on the second floor of my house and is seen by Airport Utility. Using a LAN cable with the Express works no problem.
My network is created by an Airport Extreme (ground floor) and extended by a Time Capsule (first floor)
The issue is most likely due to the fact that the AirPort Express may be too far from the AirPort Extreme to properly extend it with enough bandwidth to be useful.
It is important to understand that with Apple 802.11n or 802.11ac base station an extended network works in a wheel-like fashion with the base station to be extended at the hub and each extending base station along one of the spokes. This type of configuration does not allow for daisy chaining the base stations. That is, in your case, both the Time Capsule and AirPort Express are attempting to extend the AirPort Extreme.
Each extending base station must be within a certain signal quality range in order to extend the network properly. Please check out the following AirPort User tip for details.

Apple TV bandwidth utilization

Have my ATV with wireless. What's the average bandwidth utilization (kbps) for Apple TV to project stuffs from ipad?

Nope.
Planning to use Apple TV in meeting room for presentation purpose. Worry that 1 Aruba 105 wireless access points might not be enough for 20 laptops (internet browsing & internal server access) and Apple TV use.
Any idea about what's the maximum bandwidth Apple TV will use when doing mirroring?

Wireless client disconnecting

Hi All,
We have a WLAN setup with 1 AP 1230 assigned as a WDS, and the 16 APs configured as Infrastructure AP. Off late, I am experiencing a problem where all my clients are getting disconnected frequently. I have checked the logs and the logs indicate the follwoing:
%DOT11-4-TKIP_MIC_FAILURE: TKIP Michael MIC failure was detected on a packet (TSC=0x19B42) received from 0013.ced4.bd48.
Oct 24 12:45:42 172.20.166.22 5673: Oct 24 07:15:42.428: %DOT11-3-TKIP_MIC_FAILURE_REPEATED: Two TKIP Michael MIC failures were detected within 48 seconds on Dot11Radio0 interface. The interface will be put on MIC failure hold state for next 60 seconds.
Oct 24 12:45:42 172.20.166.22 5674: Oct 24 07:15:42.429: %DOT11-4-TKIP_MIC_FAILURE: TKIP Michael MIC failure was detected on a packet (TSC=0x19B43) received from 0013.ced4.bd48.
Oct 24 12:45:42 172.20.166.22 5675: Oct 24 07:15:42.430: %DOT11-4-TKIP_MIC_FAILURE: TKIP Michael MIC failure was detected on a packet (TSC=0x19B44) received from 0013.ced4.bd48.
Oct 24 12:45:42 172.20.166.22 5676: Oct 24 07:15:42.430: Too many MIC failures.
I need a solution to overcome this problems. Please let me know if you need any further information, to help me provide a solution.
regds,
Mahesh

Good afternoon Mahesh...
Similar to a CRC, TKIP uses Message Integrity Check(MIC) to ensure protection of the payload and headers. Presently the Michael algorithm is used to accomplish this function. Essentially these messages are early warning signs of RF interference, hardware failure and or an active attack.
The initial error message of TKIP_MIC_FAILURE is rather harmless, as there is no effect to surrounding clients. It simply states that the AP has received a packet which failed its integrity check. MIC replaced WEP's CRC-32 checksum for improved security. You will NOT see this issue in LEAP as it does not utilize MIC.
TKIP_MIC_FAILURE_REPEATED, however is another story. If you see this log entry on an access point, you will want to respond quickly. This is stating that a workstation has sent X number of MIC failures in a certain number of seconds. As stated by the 802.11i standard, the access point goes into a blackout period. ( Cisco's default is 60 second blackout period), what this does is disassociates all wireless clients associated with the access point and puts the radio in a type of hold where it does not allow any associations until the blackout is lifted.
The offending client and those associated with the access point do not receive any sort of error. All the user will notice, is that their laptop's wireless has been disconnected. If the user's laptop is able to access another AP it will attempt to connect to it, if behaving and configure correctly. What we have seen in at our facility is the offending client will continue to cause TKIP errors and bring down the AP it just connected to.
Is there a Band-Aid to this problem?
Interface dot11radio x
countermeasure tkip hold-time 0
This is NOT a solution, its simply a fix to keep your APs from going into blackout. Again I would only use this if you had a larger volume of laptops with malfunctioning nics than your local techsupport could handle.
There are two typical causes for these errors, hardware problems and RF issues. RF changes even at 5ft, if you are able to go to multiple areas of your facility (saying you have a large facility) and take still shoot out errors, you likly have a hardware issue. Replace the card and your good to go.
While upgrading to the latest IOS is always the best messure even when not facing problems you will likly not see a decrease/increase.
hope this helps.... Simply put , research if its a single laptop... If it is, attempt to replace the nic.. We had one laptop which even after reloading the IOS, swapping the cards, etc it kept commiting the units. We kept the harddrive and sent the laptop off and was RMA'd. New laptop came in, put the old hdd back in, no problems.
We have not noticed a link between driver version nor firmware...

Locate wireless client by IP address ?

Is there a easier way to locate a wireless client by ip addrss in a WISM controller or even via WCS ?
I now go to the home page of my controller and go to the client section and filter by mac address , AP names, etc. once I find that, I drill in and I can find the IP address listed then, but what if I have a wireless client IP only ? I'm running version 5.2.193.0 on the WISM controller. My WCS is a level 6.x.
I trying to locate a wireless client which I believe is sending spam but unless I go into every profile connection, how can I locate this client ?
Thanks all

Thanks for the quick response.
The first option sounds like I need some type of wireless software which at the moment I'm not utilizing so don't know how to do that.
option 2 also sounds foreign to me ! ;-)
Can you add some details or point me to any links you can ref me to so I can try to familiarize myself with these options ?
Regards
Mark

WRT600N Doesn't show any entries in the Wireless Client List

Hi, my WRT600N is on firmware 1.01.35 build 3. When I check the wireless client list from the Wireless MAC Filter page, it is empty, even though I know I have 3 clients connected. They are all using 802.11g, as I don't have any N devices yet. When I go to the Status page and check the DHCP Client Table, both of my wired clients are there, but only 1 wireless client appears. The DHCP Client Log file is useless, as it only appears to log the ip address it receives from my isp. There are no entries of the ip addresses it has given out. Is my WRT600N defective, or is there firmware in the works to correct this?

Another thing I've notice, is that the DHCP client table is showing the 2.4 wireless devices as LAN interfaces. Shouldn't it show the frequency, like it does my one 5GHz device? Things have changed, because the Wii is now showing in both the Wireless Client List, as well as the DHCP Client table. It shows as a LAN interface though, which is wrong, it should be 2.4GHz. My one pc that is a 5GHz N device, is also showing in both the Wireless Client List, & the DHCP Client table. Neither the wireless 2.4 gaming adapter, or the HR20 connected to it show up in either list. Neither does a laptop which is 2.4GHz. This is really a concern, because I've caught 2 neighbors stealing my bandwidth in the past, and I can't stop them if I can't see them.

Unknown Wireless client. How do I identify?

Hi,
I am checking my wireless clients and there's one in there that I don't recognize. I have WPA enabled, and have shut off everything I have that I know of that's wireless and it's still there.
I also checked the airport address and it doesn't appear to match. I don't see anything in Airport that's actually called a MAC address either, and the signal isn't moving when I use other devices.
Is there any sort of terminal command or anything that I can use to identify it? Would the airport show up in the Wireless Clients?
thanks,
Dave

Dave Taylor wrote:
just knowing that it's an apple device is not telling me which apple device. I have several and I've shut off WiFi on all of them, but still this device registers.
Is it possible that even with WiFi/Aiport off that I'm seeing a device?
That MAC assignment page isn't always helpful, but it can let someone identify a device they're not thinking about, such as a Wi-Fi printer or a cell phone "network extender". Do you have any other networking gear such as an AirPort Express?
A device that's truely off shouldn't appear. You seem to be aware that just pushing the button at the top of an iPhone doesn't really turn it off.
You might try configuring your AirPort base station for MAC address filtering to see what breaks.

Ipqos to monitor bandwidth utilization in zones?

I'd like to use IPQos and the extended accounting features in the global zone to monitor bandwidth utilization in my zones - ie, keep a simple count of amount of traffic each zone's IPs use.
I can't quite figure out how to do it, though. The IPQos docs are extensive, but complex.
Anyone got a simple 'howto' for it??

not really using ipqos, but i have a dtrace script that tracks socket traffic per pid and uid, you can probably change it to meet your needs.
#!/usr/sbin/dtrace -Cs
/* like top but tracks pid's network transfers */
/* By James Dickens [email protected] */
#pragma D option quiet
#include<sys/uio.h>
int DR; /* Data READ */
int DW; /* Data WROTE */
int DRL; /* Data Read in the last second */
int DWL; /* Data Wrote in the last second */
int new_data; /* set when there is new data to print */
dtrace:::BEGIN { printf("Waiting for data...\n"); }
fbt:sockfs:socktpi_write:entry
self->registry=1;
self->uiop = (struct uio *) arg1;
self->request = self->uiop->uio_resid; /* MAX amount of data to send *
fbt:sockfs:socktpi_read:entry
self->registry=1;
self->uiop = (struct uio *) arg1;
self->request = self->uiop->uio_resid; /* MAX amount of data to recieve
fbt:sockfs:socktpi_read:return
/arg0 != 0 && self->registry/ /* don't grab data if an error was returned. */
size = self->request - self->uiop->uio_resid; /* update the data read *
DR +=size;
DRL += size;
@data[uid,pid, "rcv'd" ] = sum(size);
@datac[uid,pid,"rcv'd" ] = sum(size);
self->request=0;
self->registry=0;
self->uiop=0;
new_data=1 ;
fbt:sockfs:socktpi_write:return
/arg0 != 0 && self->registry / /* don't grab data if an error was returned. */
size = self->request - self->uiop->uio_resid ; /* update amount of data
sent */
DW += size;
DWL += size;
@data[uid, pid, "sent" ]= sum(size);
@datac[uid,pid,"sent" ] = sum(size);
self->request=0;
self->registery=0;
self->uiop=0;
new_data=1;
tick-1s
/new_data /
new_data=0;
printf("\nwalltime : %Y\nStats for the active last Second\nUID\tPID\tdi
retion\tBytes\n", walltimestamp);
printa("%d\t%d\t%8s\t%@d\n",@data);
printf("Totals for this second\nData Rcv'd ==%d Data Sent == %d TOTAL %d
\n",
DRL, DWL, DRL+DWL);
printf("TOTALS\nData Rcv'd == %d Data Sent ==%d Total TRANSFERRED == %d\
n",
DR , DW, DR + DW) ;
trunc(@data,0);
DRL=0; DWL=0;
dtrace:::END {
printf("\nGrand Totals\n");
printf("UID\tPID\tdiretion\tBytes\n");
printa("%d\t%d\t%8s\t%@d\t\n",@datac);
printf("TOTALS\n");
printf("Data Rcv'd == %d Data Sent ==%d TOTAL TRANSFERRED == %d", DR , D
W, DR + DW) ;
}

Monitoring IPSec Tunnel Bandwidth Utilization

We have a Cisco ASA 5520 supporting multiple VPNs - both remote-access and Lan-to-Lan. We would like to monitor the bandwidth utilization of the IPSec Lan-to-Lan tunnels. How can we do that?
Thanks,
Spr

Hi Spr,
Check out VPNTTG (VPN Tunnel Traffic Grapher) is a software for SNMP monitoring and measuring the traffic load for IPsec (Site-to-Site, Remote Access) and SSL (With Client, Clientless) VPN tunnels on a Cisco ASA. It allows the user to see traffic load on a VPN tunnel over time in graphical form.
Advantage of VPNTTG over other SNMP based monitoring software's is following: Other (commonly used) software's are working with static OID numbers, i.e. whenever tunnel disconnects and reconnects, it gets assigned a new OID number. This means that the historical data, gathered on the connection, is lost each time. However, VPNTTG works with VPN peer's IP address and it stores for each VPN tunnel historical monitoring data into the Database.
For more information about VPNTTG please visit www.vpnttg.com

3750 Bandwidth Utilization

Hello,
Is there a way to look at the bandwidth utilization on a per port basis on the 3750 switches? Trying to track down a possible issue remote;y and nothing like WireShark is onsite.
Thanks in advance.
All replies rated.

You can enter "show interface summary" to see the tx rate and rx rate for each port. Very easy to read format.
To use wireshark remotely, you could always use ERSPAN, which would send the monitor session to a remote switch. If I'm not sure of the commands I'm entering on a remote switch, I normally do a "reload in 15". In case I lose connectivity, it will reload in x number of minutes to restore service. Save you a commute to the remote site to restore service. Just don't forget to cancel the reload when you are finished.
https://supportforums.cisco.com/document/139236/understanding-spanrspanand-erspan#comment-10119266
If you have network monitoring software, it should show the top talker along with the ip address.
show arp | i x.x.xx
this will return the mac
then enter show mac address-table address xxxx.xxxx.xxxx
this will show the interface that learned the mac.
show cdp neigh to verify the port isn't connected to another switch.
Keep entering sh mac and sh cdp until you locate the port with the mac of the top talker.
You can shut the port and see if the trouble goes away.
Just be careful when shutting ports. Its easy to shut the wrong port and lose connectivity.

Extending wireless network - allow wireless clients or not?

Hi,
sorry if this is a stupid question but I cannot find the answer on the internet.
I have a setup with 3 level house, 3 airport extremes, the one in the middle connected via ethernet to router and acting as DHCP server.
The other two are setup to 'extend network'
Question I have is should I check "allow wireless clients" or not because when I do it seems to make the main AP extreme a client of the other two as well. This seems strange to me. any help would be appreciated.

do you work in entertainment industry at all? I know a bob timmons...
That would not be me.
any ideas why my extension airport extremes see the main DHCP extreme as clients?
This is normal. The "main" base station is a client of the "extending" Airport....and the "extending" AirPort is a client of the "main" base station. You would not have any extension if they were not clients of each other. In simple terms, they are communicating with each other at all times.
also any idea of the actual range of the AP extremes?
They usually check out at about 45-50 meters or 150 feet or so....but range measurements are made in "free air" in a large space....like an airplane hangar......with no obstructions in the signal path. Most homes are laid out a bit differently.
I've seen installations where the signal would barely go through one wall to a computer that was no more than 10 feet away from the router. The wall was metal lathe and plaster, so in effect the very weak signal was being asked to power though metal. Not much signal was getting through.
In very general terms, a typical wall of sheetrock or wallboard and 2 x 4s will absorb on average 15-20% of the wireless signal. A ceilng will absorb much more because it is much thicker. In most homes, after 3 or 4 walls, or a ceiling and a wall, there won't be much signal left.
Now, if you have adobe walls or cement walls or ceilings, everything changes dramatically. You get the idea.
My home is about 2400 sq ft, single level, of typical construction. I use 3 AirPort Extremes....all connected by Ethernet....not wireless....to get full speed, fast coverage virtually everywhere. I use an AirPort Express to "extend"....using wireless only....if I want to take my laptop out on the patio.
Older iPhones can connect at maximum 54 Mbps if they are literally right on top of the router. Typically,they might be at 25-35 Mbps or so with a good signal in the next room. The 180 and 270 numbers signify that these connections are 5 GHz...probably a newer Mac laptop or iMac.
If you have a Mac laptop and don't mind a $3 investment to get a good utility, WiFi Explorer can reveal some very useful things about your network. Post back if you are interested and we will take this up on Thursday.

Some Wireless clients won't authenticate to 887VA-W

Hi folks
I've swapped over a few months ago from an 877w router to an 887VAw which has a separate AP in-built, and there are a few wireless clients that had no problem authenticating to the 877w but just refuse to communicate to the 887VA-W.
The clients in question are set top box type devices : (1)Now TV and (2) Sky Wireless Adapter.
They have no problem seeing the SSID's being broadcast, and for troubleshooting I've setup an open test SSID without any encryption, but the clients still won't authenticate and grab an ip address, or more accurately they just don't get a dhcp ip address so I don't think authentication is really the issue. I don't know why these clients aren't happy with dhcp on the guest vlan (vlan2) where other clients get an ip address and work fine. Perhaps the fact I'm using vlan1 (being used for the Eap-Fast home wlan) as the native untagged vlan might have something to do with it? If I use a static ip address on the guest vlan (vlan 2 / ip 10.1.1.n ) then the Sky Wireless Adapter can send and receive packets across the wlan.
Can anybody please suggest some debugs or config changes to try and nail the problem? The relevant configs from the AP is pasted below, and the router below that.
Brgds, Tim
aaa new-model
aaa group server radius rad_eap
server name rs-local
aaa authentication login default local
aaa authentication login eap_methods group rad_eap
aaa authentication ppp default local
aaa authorization exec default local
dot11 ssid home
   vlan 1
   authentication open eap eap_methods
   authentication network-eap eap_methods
   authentication key-management wpa version 2
dot11 ssid guest
   vlan 2
   authentication open
   authentication key-management wpa
   mbssid guest-mode
   wpa-psk ascii 7 abcdef123
dot11 ssid test
   vlan 3
   authentication open
   mbssid guest-mode
interface Dot11Radio0
no ip address
no ip route-cache
encryption vlan 1 mode ciphers aes-ccm
encryption vlan 2 mode ciphers aes-ccm
broadcast-key vlan 1 change 30
broadcast-key vlan 2 change 43200
ssid home
ssid guest
ssid test
antenna gain 0
mbssid
speed basic-1.0 basic-2.0 basic-5.5 basic-11.0 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
packet retries 64 drop-packet
no preamble-short
station-role root
interface Dot11Radio0.1
encapsulation dot1Q 1 native
no ip route-cache
no cdp enable
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Dot11Radio0.2
encapsulation dot1Q 2
no ip route-cache
no cdp enable
bridge-group 2
bridge-group 2 subscriber-loop-control
bridge-group 2 spanning-disabled
bridge-group 2 block-unknown-source
no bridge-group 2 source-learning
no bridge-group 2 unicast-flooding
interface Dot11Radio0.3
encapsulation dot1Q 3
no ip route-cache
no cdp enable
bridge-group 3
bridge-group 3 subscriber-loop-control
bridge-group 3 spanning-disabled
bridge-group 3 block-unknown-source
no bridge-group 3 source-learning
no bridge-group 3 unicast-flooding
interface GigabitEthernet0
description the embedded AP GigabitEthernet 0 is an internal interface connecting AP with the host router
no ip address
no ip route-cache
interface GigabitEthernet0.1
encapsulation dot1Q 1 native
no ip route-cache
bridge-group 1
bridge-group 1 spanning-disabled
no bridge-group 1 source-learning
interface GigabitEthernet0.2
encapsulation dot1Q 2
no ip route-cache
bridge-group 2
bridge-group 2 spanning-disabled
no bridge-group 2 source-learning
interface GigabitEthernet0.3
encapsulation dot1Q 3
no ip route-cache
bridge-group 3
bridge-group 3 spanning-disabled
no bridge-group 3 source-learning
interface BVI1
ip address 172.27.44.2 255.255.255.0
no ip route-cache
ip default-gateway 172.27.44.1
****Router Config****
interface Wlan-GigabitEthernet0
description Internal switch interface connecting to the embedded AP
switchport mode trunk
no ip address
interface wlan-ap0
description Service module interface to manage the embedded AP
ip unnumbered BVI1

Hi Sebastian
Please see ip dhcp debug from 887VA-W showing the Sky client requesting an ip address but failing to get one. Also a debug from an 877-W showing successful dhcp assignment. Also the dhcp config as requested.The successful trace shows 2 mac addresses from the Sky wireless adapter/ Sky box each getting a dhcp address. I don't know whether the failure is a bug in the 887 dhcp code or some config in the embedded AP that needs tweaking.
Bregs, Tim
The Sky wired adapter (I think it's the mac of the sky box lan port) mac is 00:19:FB:A4:B2:1A
The Sky wireless mac is 18:28:61:99:7B:A8
887VA-W Debug - Failure:
887#term mon
887#sh deb
DHCP server packet debugging is on.
887#
887#
000141: Dec 16 07:03:02.082 London: DHCPD: ARP entry exists (10.1.1.10, e0c9.7ad6.24ee).
000142: Dec 16 07:03:02.082 London: DHCPD: unicasting BOOTREPLY to client e0c9.7ad6.24ee (10.1.1.10).
Denham_887#
000143: Dec 16 07:05:25.536 London: DHCPD: client's VPN is .
000144: Dec 16 07:05:25.536 London: DHCPD: No option 125
000145: Dec 16 07:05:25.536 London: DHCPD: DHCPDISCOVER received from client 0019.fba4.b21a on interface BVI1.
000146: Dec 16 07:05:25.536 London: DHCPD: Allocate an address without class information (10.1.1.0)
000147: Dec 16 07:05:25.536 London: DHCPD: Saving workspace (ID=0x4000009)
Denham_887#
000148: Dec 16 07:05:27.536 London: DHCPD: Reprocessing saved workspace (ID=0x4000009)
000149: Dec 16 07:05:27.536 London: DHCPD: DHCPDISCOVER received from client 0019.fba4.b21a on interface BVI1.
000150: Dec 16 07:05:27.536 London: DHCPD: Sending DHCPOFFER to client 0019.fba4.b21a (10.1.1.12).DHCPD: Setting only requested parameters
000151: Dec 16 07:05:27.536 London: DHCPD: no option 125
000152: Dec 16 07:05:27.536 London: DHCPD: broadcasting BOOTREPLY to client 0019.fba4.b21a.
Denham_887#
000153: Dec 16 07:05:32.468 London: DHCPD: New packet workspace 0x123EC554 (ID=0xC700000A)
000154: Dec 16 07:05:32.468 London: DHCPD: client's VPN is .
000155: Dec 16 07:05:32.468 London: DHCPD: No option 125
000156: Dec 16 07:05:32.468 London: DHCPD: DHCPDISCOVER received from client 0118.2861.997b.a8 on interface BVI1.
000157: Dec 16 07:05:32.468 London: DHCPD: Allocate an address without class information (10.1.1.0)
000158: Dec 16 07:05:32.472 London: DHCPD: Saving workspace (ID=0xC700000A)
Denham_887#
000159: Dec 16 07:05:34.080 London: DHCPD: New packet workspace 0x1240A47C (ID=0x5500000B)
000160: Dec 16 07:05:34.080 London: DHCPD: client's VPN is .
000161: Dec 16 07:05:34.080 London: DHCPD: No option 125
000162: Dec 16 07:05:34.080 London: DHCPD: DHCPDISCOVER received from client 0019.fba4.b21a on interface BVI1.
000163: Dec 16 07:05:34.080 London: DHCPD: Sending DHCPOFFER to client 0019.fba4.b21a (10.1.1.12).DHCPD: Setting only requested parameters
000164: Dec 16 07:05:34.080 London: DHCPD: no option 125
000165: Dec 16 07:05:34.080 London: DHCPD: broadcasting BOOTREPLY to client 0019.fba4.b21a.
Denham_887#
000166: Dec 16 07:05:34.468 London: DHCPD: Reprocessing saved workspace (ID=0xC700000A)
000167: Dec 16 07:05:34.468 London: DHCPD: DHCPDISCOVER received from client 0118.2861.997b.a8 on interface BVI1.
000168: Dec 16 07:05:34.468 London: DHCPD: Sending DHCPOFFER to client 0118.2861.997b.a8 (10.1.1.13).DHCPD: Setting only requested parameters
000169: Dec 16 07:05:34.468 London: DHCPD: no option 125
000170: Dec 16 07:05:34.468 London: DHCPD: broadcasting BOOTREPLY to client 1828.6199.7ba8.
Denham_887#
000171: Dec 16 07:05:35.476 London: DHCPD: client's VPN is .
000172: Dec 16 07:05:35.476 London: DHCPD: No option 125
000173: Dec 16 07:05:35.476 London: DHCPD: DHCPDISCOVER received from client 0118.2861.997b.a8 on interface BVI1.
000174: Dec 16 07:05:35.476 London: DHCPD: Sending DHCPOFFER to client 0118.2861.997b.a8 (10.1.1.13).DHCPD: Setting only requested parameters
000175: Dec 16 07:05:35.476 London: DHCPD: no option 125
000176: Dec 16 07:05:35.476 London: DHCPD: broadcasting BOOTREPLY to client 1828.6199.7ba8.
Denham_887#
000177: Dec 16 07:05:37.520 London: DHCPD: client's VPN is .
000178: Dec 16 07:05:37.520 London: DHCPD: No option 125
000179: Dec 16 07:05:37.520 London: DHCPD: DHCPDISCOVER received from client 0118.2861.997b.a8 on interface BVI1.
000180: Dec 16 07:05:37.520 London: DHCPD: Sending DHCPOFFER to client 0118.2861.997b.a8 (10.1.1.13).DHCPD: Setting only requested parameters
000181: Dec 16 07:05:37.524 London: DHCPD: no option 125
000182: Dec 16 07:05:37.524 London: DHCPD: broadcasting BOOTREPLY to client 1828.6199.7ba8.
Denham_887#
000183: Dec 16 07:05:40.532 London: DHCPD: client's VPN is .
000184: Dec 16 07:05:40.532 London: DHCPD: No option 125
000185: Dec 16 07:05:40.532 London: DHCPD: DHCPDISCOVER received from client 0118.2861.997b.a8 on interface BVI1.
000186: Dec 16 07:05:40.532 London: DHCPD: Sending DHCPOFFER to client 0118.2861.997b.a8 (10.1.1.13).DHCPD: Setting only requested parameters
000187: Dec 16 07:05:40.532 London: DHCPD: no option 125
000188: Dec 16 07:05:40.532 London: DHCPD: broadcasting BOOTREPLY to client 1828.6199.7ba8.
Denham_887#
000189: Dec 16 07:05:43.540 London: DHCPD: client's VPN is .
000190: Dec 16 07:05:43.540 London: DHCPD: No option 125
000191: Dec 16 07:05:43.540 London: DHCPD: DHCPDISCOVER received from client 0118.2861.997b.a8 on interface BVI1.
000192: Dec 16 07:05:43.540 London: DHCPD: Sending DHCPOFFER to client 0118.2861.997b.a8 (10.1.1.13).DHCPD: Setting only requested parameters
000193: Dec 16 07:05:43.540 London: DHCPD: no option 125
000194: Dec 16 07:05:43.540 London: DHCPD: broadcasting BOOTREPLY to client 1828.6199.7ba8.
Denham_887#
000195: Dec 16 07:05:48.884 London: DHCPD: client's VPN is .
000196: Dec 16 07:05:48.884 London: DHCPD: No option 125
000197: Dec 16 07:05:48.884 London: DHCPD: DHCPDISCOVER received from client 0019.fba4.b21a on interface BVI1.
000198: Dec 16 07:05:48.884 London: DHCPD: Sending DHCPOFFER to client 0019.fba4.b21a (10.1.1.12).DHCPD: Setting only requested parameters
000199: Dec 16 07:05:48.884 London: DHCPD: no option 125
000200: Dec 16 07:05:48.884 London: DHCPD: broadcasting BOOTREPLY to client 0019.fba4.b21a.
887VA-W dhcp config:
887#sh run | section dhcp
no ip dhcp use vrf connected
ip dhcp binding cleanup interval 10
no ip dhcp conflict logging
ip dhcp pool home
network 172.27.44.0 255.255.255.0
dns-server 208.67.222.222 208.67.220.220
default-router 172.27.44.1
ip dhcp pool test
import all
network 11.1.1.0 255.255.255.0
default-router 11.1.1.1
dns-server 208.67.222.222 208.67.220.220
ip dhcp pool guest
import all
network 10.1.1.0 255.255.255.0
default-router 10.1.1.1
dns-server 208.67.222.222 208.67.220.220
877-W Debug - Success:
877#deb ip dhcp se
877#deb ip dhcp server pa
DHCP server packet debugging is on.
877#deb ip dhcp server ev
DHCP server event debugging is on.
877#
000258: *Jun 23 22:20:07.087 BST: DHCPD: checking for expired leases.
000259: *Jun 23 22:20:14.684 BST: %DOT11-6-ASSOC: Interface Dot11Radio0, Station   1828.6199.7ba9 Associated SSID[guest] AUTH_TYPE[OPEN] KEY_MGMT[WPAv2 PSK]
000260: *Jun 23 22:20:16.289 BST: DHCPD: Sending notification of DISCOVER:
000261: *Jun 23 22:20:16.289 BST:   DHCPD: htype 1 chaddr 1828.6199.7ba8
000262: *Jun 23 22:20:16.289 BST:   DHCPD: remote id 020a00000a010101f2000000
000263: *Jun 23 22:20:16.289 BST:   DHCPD: circuit id 00000000
000264: *Jun 23 22:20:16.289 BST: DHCPD: DHCPDISCOVER received from client 0118.2861.997b.a8 on interface BVI2.
000265: *Jun 23 22:20:16.289 BST: DHCPD: Seeing if there is an internally specified pool class:
000266
*Jun 23 22:20:16.289 BST:   DHCPD: htype 1 chaddr 1828.6199.7ba8
000267: *Jun 23 22:20:16.289 BST:   DHCPD: remote id 020a00000a010101f2000000
000268: *Jun 23 22:20:16.289 BST:   DHCPD: circuit id 00000000
000269: *Jun 23 22:20:16.289 BST: DHCPD: Sending DHCPOFFER to client 0118.2861.997b.a8 (10.1.1.9).
000270: *Jun 23 22:20:16.289 BST: DHCPD: broadcasting BOOTREPLY to client 1828.6199.7ba8.
000271: *Jun 23 22:20:16.493 BST: DHCPD: DHCPREQUEST received from client 0118.2861.997b.a8.
000272: *Jun 23 22:20:16.493 BST: DHCPD: Sending notification of ASSIGNMENT:
000273: *Jun 23 22:20:16.493 BST: DHCPD: address 10.1.1.9 mask 255.255.255.0
000274: *Jun 23 22:20:16.493 BST:   DHCPD: htype 1 chaddr 1828.6199.7ba8
000275: *Jun 23 22:20:16.493 BST:   DHCPD: lease time remaining (secs) = 86400
000276: *Jun 23 22:20:16.493 BST: DHCPD: Appending system default domain
000278: *Jun 23 22:20:16.493 BST: DHCPD: Sending DHCPACK to client 0118.2861.997b.a8 (10.1.1.9).
000279: *Jun 23 22:20:16.493 BST: DHCPD: broadcasting BOOTREPLY to client 1828.6199.7ba8.
000280: *Jun 23 22:20:17.089 BST: DHCPD: checking for expired leases.
000281: *Jun 23 22:20:18.097 BST: %SYS-5-CONFIG_I: Configured from console by vty0
Denham#
000282: *Jun 23 22:20:21.314 BST: DHCPD: Sending notification of DISCOVER:
000283: *Jun 23 22:20:21.314 BST:   DHCPD: htype 1 chaddr 0019.fba4.b21a
000284: *Jun 23 22:20:21.314 BST:   DHCPD: remote id 020a00000a010101f2000000
000285: *Jun 23 22:20:21.314 BST:   DHCPD: circuit id 00000000
000286: *Jun 23 22:20:21.314 BST: DHCPD: DHCPDISCOVER received from client 0019.fba4.b21a on interface BVI2.
000287: *Jun 23 22:20:21.314 BST: DHCPD: Seeing if there is an internally specified pool class:
000288: *
Jun 23 22:20:21.314 BST:   DHCPD: htype 1 chaddr 0019.fba4.b21a
000289: *Jun 23 22:20:21.314 BST:   DHCPD: remote id 020a00000a010101f2000000
000290: *Jun 23 22:20:21.314 BST:   DHCPD: circuit id 00000000
000291: *Jun 23 22:20:21.314 BST: DHCPD: Sending DHCPOFFER to client 0019.fba4.b21a (10.1.1.8).
000292: *Jun 23 22:20:21.314 BST: DHCPD: broadcasting BOOTREPLY to client 0019.fba4.b21a.
000293: *Jun 23 22:20:21.406 BST: DHCPD: DHCPREQUEST received from client 0019.fba4.b21a.
000294: *Jun 23 22:20:21
406 BST: DHCPD: Sending notification of ASSIGNMENT:
000295: *Jun 23 22:20:21.406 BST: DHCPD: address 10.1.1.8 mask 255.255.255.0
000296: *Jun 23 22:20:21.406 BST:   DHCPD: htype 1 chaddr 0019.fba4.b21a
000297: *Jun 23 22:20:21.406 BST:   DHCPD: lease time remaining (secs) = 86400
000298: *Jun 23 22:20:21.406 BST: DHCPD: Can't find any hostname to update
000299: *Jun 23 22:20:21.406 BST: DHCPD: Sending DHCPACK to client 0019.fba4.b21a (10.1.1.8).
000300: *Jun 23 22:20:21.406 BST: DHCPD: broadcasting
BOOTREPLY to client 0019.fba4.b21a.
000302: *Jun 23 22:20:33.049 BST: DHCPD: Sending notification of DISCOVER:
000303: *Jun 23 22:20:33.049 BST:   DHCPD: htype 1 chaddr 1828.6199.7ba8
000304: *Jun 23 22:20:33.049 BST:   DHCPD: remote id 020a00000a010101f2000000
000305: *Jun 23 22:20:33.049 BST:   DHCPD: circuit id 00000000
000306: *Jun 23 22:20:33.049 BST: DHCPD: DHCPDISCOVER received from client 0118.2861.997b.a8 on interface BVI2.
000307: *Jun 23 22:20:33.049 BST: DHCPD: Seeing if there is an internally specified pool class:
000308
Denham#: *Jun 23 22:20:33.049 BST:   DHCPD: htype 1 chaddr 1828.6199.7ba8
000309: *Jun 23 22:20:33.049 BST:   DHCPD: remote id 020a00000a010101f2000000
000310: *Jun 23 22:20:33.049 BST:   DHCPD: circuit id 00000000
000311: *Jun 23 22:20:33.049 BST: DHCPD: Sending DHCPOFFER to client 0118.2861.997b.a8 (10.1.1.9).
000312: *Jun 23 22:20:33.053 BST: DHCPD: broadcasting BOOTREPLY to client 1828.6199.7ba8.
000313: *Jun 23 22:20:33.081 BST: DHCPD: DHCPREQUEST received from client 0118.2861.997b.a8.
000314: *Jun 23
Denham# 22:20:33.081 BST: DHCPD: Sending notification of ASSIGNMENT:
000315: *Jun 23 22:20:33.081 BST: DHCPD: address 10.1.1.9 mask 255.255.255.0
000316: *Jun 23 22:20:33.081 BST:   DHCPD: htype 1 chaddr 1828.6199.7ba8
000317: *Jun 23 22:20:33.081 BST:   DHCPD: lease time remaining (secs) = 86400
000318: *Jun 23 22:20:33.081 BST: DHCPD: Appending system default domain
000319: *Jun 23 22:20:33.085 BST: DHCPD: Using hostname 'skywirelessconnector.indahouse.dyndns.org.' for dynamic update (from hostname opti
indahouse#uon)
000320: *Jun 23 22:20:33.085 BST: DHCPD: Sending DHCPACK to client 0118.2861.997b.a8 (10.1.1.9).
000321: *Jun 23 22:20:33.085 BST: DHCPD: broadcasting BOOTREPLY to client 1828.6199.7ba8.

Why are so many wireless clients seen when using airport utility?

When I open up the Airport Utility, I can see upwards of a dozen "wireless clients" connected to each of the two Airport Extremes that I have on my network. Some of these are known computers and iOS devices, but many of them have names that are IP addresses (like 10..0.0.3) or hexadecimal numbers (like 9C:FE:94:4B:75:FE). Not sure what these are. Can they slow down the network?

Take a few moments and count up the total number of wireless devices that you have.
In addition to computers, be sure to include printers, iPhones, iPads, Apple TVs, other Airport routers, other mobile devices, baby monitors, thermostats, etc......anything that uses a wireless signal from your network.
Some devices will be displayed by their name, others by assigned IP address and others by their MAC Address with 12 characters and colons.
Every device that is connected to your network uses up a certain amount of bandwidth, so the more devices that you have connected at one time, the slower the network will operate.
Unless you are lucky enough to have a very fast Internet connection plan with your provider, you may likely notice that browsing, email and other activities on the the wireless slow down when multiple devices are using the Internet, or you are copying files from one device to another over the network.
When you are ready, open AirPort Utility. Hold down the option key while you double click on your AirPort icon.
A window displaying wireless clients will be displayed. Compare the total of devices to your count. If you see more devices than you have, you may have an unwanted guest on your network. Change your wireless network password immediately.
Another thing that you can do is power off all of the wireless devices and then start them up one at a time while you are checking AirPort Utility.

Top Wireless Client Bandwidth Utilization on WCS?

Similar Messages

Maybe you are looking for