WSLM with BBSM

Can the WLSM be used with the BBSM to aggregate public wireless access from a number of locations (using the mGRE functionality of the WLSM), with the traffic policy routed towards the BBSM?

This document discusses some of the scenarios supported by the mGRE funcationality,
http://www.cisco.com/en/US/netsol/ns340/ns394/ns431/ns434/networking_solutions_implementation_guide09186a008038906c.html

Similar Messages

HTTPS with BBSM

Hi
I have a BBSM 5.3 SP2 at a customer site. When the customer wants to contact an https site on internet, then he gets an error. After reading the manuals, I found that an SSL certificate is necessary. I'm a bit confused now. I thought the SSL certificate was only necessary if I want to make an https session to the management page of the BBSM. Can somebody confirm if I need the SSL certificate to contact no matter what https site on internet? Do I need to create an SSL welcome page also?
Thanks in advance
Erwin

Check this
http://www.cisco.com/en/US/products/sw/netmgtsw/ps533/products_user_guide_chapter09186a00801da1ec.html

Access Point 1240 Support for BBSM5.3

Hello,
I have 3 ap 1240 for install with bbsm 5.3, but when I add the access-point to the bbsm , the bbsm does not recognise has a valid access-point.
Does any one know in what version of bbsm is supported ap1240.
Thanks

Hello there,
I have a customer who has a BBSM 5.3A which is running the latest patch (5332) and it cannot discover 1242 series AP's as valid network elements. They get the following:
2009/01/07 12:01:53 Pinging X.X.X.X...
2009/01/07 12:01:53 X.X.X.X is ACTIVE
2009/01/07 12:02:18 X.X.X.X: not a Network Element or SNMP password is not ******
2009/01/07 12:02:18
2009/01/07 12:02:18 Pinging X.X.X.X...
2009/01/07 12:02:23 X.X.X.X: no response
2009/01/07 12:02:23
2009/01/07 12:02:23 Pinging X.X.X.X...
2009/01/07 12:02:23 X.X.X.X is ACTIVE
2009/01/07 12:02:47 X.X.X.X: not a Network Element or SNMP password is not ******
2009/01/07 12:02:47
2009/01/07 12:02:47 Pinging X.X.X.X...
2009/01/07 12:02:47 X.X.X.X is ACTIVE
2009/01/07 12:03:12 X.X.X.X: not a Network Element or SNMP password is not ******
2009/01/07 12:03:12
2009/01/07 12:03:12 Pinging X.X.X.X...
2009/01/07 12:03:12 X.X.X.X is ACTIVE
2009/01/07 12:03:37 X.X.X.X: not a Network Element or SNMP password is not ******
They have assured me that the SNMP info is correct as they have checked it several times but the BBSM still doesn't recognise the 1242's. I know that the document link above specifies that 1200's are supported but don't Cisco class the old 1200's, 1230's and 1242's as different? Also, the BBSM didn't recognise some of their 2960-24 switches as valid network elements either but they selected the object type themselves from the list.
Thanks in advance.
Leigh

[solved] problems with pacman after upgrading to 2.6.27-ARCH

i'm not sure if my problem is related with the new version of software or the fact that i ran out of space during the upgrade. but once i restarted after the upgrade i was not able to boot into the system and the error i would get was:
ERROR: Failed to parse block device name for '/dev/sda3'
unknown
ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter.
i followed what some other people did and i booted with livecd, chrooted and regenerated mkinitcpio. since i saw some other people having the same problems here is what i used:
http://wiki.archlinux.org/index.php/Boo … omplicated
http://wiki.archlinux.org/index.php/Mki … ng_presets
and just for good measure i decided to run fsck:
http://wiki.archlinux.org/index.php/Fsck
i was still seeing some segmentation faults so i decided to re-install all of the packages installed:
http://wiki.archlinux.org/index.php/Pac … re_Restore
now everything seems to work OK except when i run pacman. here is what i get:
/sbin/ldconfig: /usr/lib/libgettextpo.so is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libwiretap.so.0.0.1 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libasprintf.so.0 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libasprintf.so.0.0.0 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libsigc-2.0.so is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libasprintf.so is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libwiretap.so is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libgettextpo.so.0.4.0 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libgettextsrc.so is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libsigc-2.0.so.0 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libgettextsrc-0.17.so is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libgettextpo.so.0 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libgettextlib-0.17.so is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libsigc-2.0.so.0.0.0 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libwiretap.so.0 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib/libgettextlib.so is not an ELF file - it has the wrong magic bytes at the start.
packages are still installed but i would like to get to the bottom of this and get it fixed. any ideas what went wrong (well... besides me running out of disk space!) and how to get it fixed?
Last edited by djidji (2008-10-24 17:49:14)

thanks for the reply. i tried finding out what packages these libraries beling to but for every single one of these listed i get an error saying that "No packages owns...". could it be something with ldconfig?
EDIT:
so i figured out that one of the files was related to wireshark. i tried re-installing wireshark and here is what i got:
: sudo pacman -Sy wireshark
:: Synchronizing package databases...
core 31.4K 229.6K/s 00:00:00 [#############################################################################################] 100%
extra 413.1K 508.9K/s 00:00:01 [#############################################################################################] 100%
community 356.3K 298.9K/s 00:00:01 [#############################################################################################] 100%
resolving dependencies...
looking for inter-conflicts...
Targets (1): wireshark-1.0.4-1
Total Download Size: 11.89 MB
Total Installed Size: 51.80 MB
Proceed with installation? [Y/n]
:: Retrieving packages from extra...
wireshark-1.0.4-1-i686 11.9M 455.5K/s 00:00:27 [#############################################################################################] 100%
checking package integrity...
(1/1) checking for file conflicts [#############################################################################################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
wireshark: /usr/bin/capinfos exists in filesystem
wireshark: /usr/bin/dftest exists in filesystem
wireshark: /usr/bin/dumpcap exists in filesystem
wireshark: /usr/bin/editcap exists in filesystem
wireshark: /usr/bin/idl2wrs exists in filesystem
wireshark: /usr/bin/mergecap exists in filesystem
wireshark: /usr/bin/randpkt exists in filesystem
wireshark: /usr/bin/rawshark exists in filesystem
wireshark: /usr/bin/text2pcap exists in filesystem
wireshark: /usr/bin/tshark exists in filesystem
wireshark: /usr/bin/wireshark exists in filesystem
wireshark: /usr/lib/libwireshark.so exists in filesystem
wireshark: /usr/lib/libwireshark.so.0 exists in filesystem
wireshark: /usr/lib/libwireshark.so.0.0.1 exists in filesystem
wireshark: /usr/lib/libwiretap.so exists in filesystem
wireshark: /usr/lib/libwiretap.so.0 exists in filesystem
wireshark: /usr/lib/libwiretap.so.0.0.1 exists in filesystem
wireshark: /usr/share/man/man1/capinfos.1 exists in filesystem
wireshark: /usr/share/man/man1/dumpcap.1 exists in filesystem
wireshark: /usr/share/man/man1/editcap.1 exists in filesystem
wireshark: /usr/share/man/man1/idl2wrs.1 exists in filesystem
wireshark: /usr/share/man/man1/mergecap.1 exists in filesystem
wireshark: /usr/share/man/man1/rawshark.1 exists in filesystem
wireshark: /usr/share/man/man1/text2pcap.1 exists in filesystem
wireshark: /usr/share/man/man1/tshark.1 exists in filesystem
wireshark: /usr/share/man/man1/wireshark.1 exists in filesystem
wireshark: /usr/share/man/man4/wireshark-filter.4 exists in filesystem
wireshark: /usr/share/wireshark/AUTHORS-SHORT exists in filesystem
wireshark: /usr/share/wireshark/COPYING exists in filesystem
wireshark: /usr/share/wireshark/capinfos.html exists in filesystem
wireshark: /usr/share/wireshark/cfilters exists in filesystem
wireshark: /usr/share/wireshark/colorfilters exists in filesystem
wireshark: /usr/share/wireshark/dfilters exists in filesystem
wireshark: /usr/share/wireshark/diameter/Ericsson.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/TGPPGmb.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/TGPPSh.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/chargecontrol.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/dictionary.dtd exists in filesystem
wireshark: /usr/share/wireshark/diameter/dictionary.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/etsie2e4.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/gqpolicy.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/imscxdx.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/mobileipv4.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/nasreq.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/sip.xml exists in filesystem
wireshark: /usr/share/wireshark/diameter/sunping.xml exists in filesystem
wireshark: /usr/share/wireshark/dtds/dc.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/itunes.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/mscml.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/pocsettings.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/presence.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/reginfo.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/rlmi.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/rss.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/smil.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/watcherinfo.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/xcap-caps.dtd exists in filesystem
wireshark: /usr/share/wireshark/dtds/xcap-error.dtd exists in filesystem
wireshark: /usr/share/wireshark/dumpcap.html exists in filesystem
wireshark: /usr/share/wireshark/editcap.html exists in filesystem
wireshark: /usr/share/wireshark/help/capture_filters.txt exists in filesystem
wireshark: /usr/share/wireshark/help/capturing.txt exists in filesystem
wireshark: /usr/share/wireshark/help/display_filters.txt exists in filesystem
wireshark: /usr/share/wireshark/help/faq.txt exists in filesystem
wireshark: /usr/share/wireshark/help/getting_started.txt exists in filesystem
wireshark: /usr/share/wireshark/help/overview.txt exists in filesystem
wireshark: /usr/share/wireshark/help/toc exists in filesystem
wireshark: /usr/share/wireshark/idl2wrs.html exists in filesystem
wireshark: /usr/share/wireshark/manuf exists in filesystem
wireshark: /usr/share/wireshark/mergecap.html exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.3com exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.3gpp exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.3gpp2 exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.acc exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.alcatel exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.alteon exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.altiga exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.aptis exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.ascend exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.bay exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.bintec exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.bristol exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cablelabs exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cabletron exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cisco exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cisco.bbsm exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cisco.vpn3000 exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cisco.vpn5000 exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.colubris exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.columbia_university exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.compat exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.cosine exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.ericsson exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.erx exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.extreme exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.foundry exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.freeradius exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.gandalf exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.garderos exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.gemtek exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.itk exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.juniper exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.karlnet exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.livingston exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.localweb exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.merit exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.microsoft exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.mikrotik exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.navini exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.netscreen exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.nokia exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.nomadix exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.propel exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.quintum exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.redback exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.redcreek exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.shasta exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.shiva exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.sonicwall exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.springtide exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.t_systems_nova exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.telebit exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.trapeze exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.tunnel exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.unisphere exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.unix exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.usr exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.valemount exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.versanet exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.wispr exists in filesystem
wireshark: /usr/share/wireshark/radius/dictionary.xedia exists in filesystem
wireshark: /usr/share/wireshark/rawshark.html exists in filesystem
wireshark: /usr/share/wireshark/services exists in filesystem
wireshark: /usr/share/wireshark/smi_modules exists in filesystem
wireshark: /usr/share/wireshark/text2pcap.html exists in filesystem
wireshark: /usr/share/wireshark/tpncp/tpncp.dat exists in filesystem
wireshark: /usr/share/wireshark/tshark.html exists in filesystem
wireshark: /usr/share/wireshark/wimaxasncp/dictionary.dtd exists in filesystem
wireshark: /usr/share/wireshark/wimaxasncp/dictionary.xml exists in filesystem
wireshark: /usr/share/wireshark/wireshark-filter.html exists in filesystem
wireshark: /usr/share/wireshark/wireshark.html exists in filesystem
wireshark: /usr/share/wireshark/ws.css exists in filesystem
Errors occurred, no packages were upgraded.
i'm hoping there is a way to sort this out. i'm loving the way my laptop is set up and would have re-install everything...
Last edited by djidji (2008-10-24 01:27:00)

BBSM and RADIUS Authenticated Session Limits

I have setup a BBSM System with RADIUS authentication, the authentication traffic is passed to a seperate RSA Box to authenticate user using fobs and everything works fine.
My question is how do I limited the time a user can have a onnection to the BBSM without having to re-authentication

If you are using the 'Access Code' pageset, when the 'Stop Date and Time' of the Access
Code is reached, all currently connected users who have used that Access Code, are
disconnected.
When you define an Access Code, you define a 'Start Date and Time' and a 'Stop Date and
Time' for the Access Code. All users who have Connected by using that Access Code will be disconnected when that Date/Time is reached.
Please refer to
http://www.cisco.com/en/US/products/sw/netmgtsw/ps533/products_user_guide_ch
apter09186a0080192294.html#1038530
for more information on Access Codes.
HTH,
-Joe

Limiting bandwidth on client side with Camera.setQuality() inconsistent?

After successful bandwidthCheck() limiting bandwidth to setQuality(75000, 100)
leads to the desired result of publishing the stream with max bitrate of 75000 byte/s.
On other locations the same setting results in publishing the stream with max bitrate of
approx. 13107 byte/s. If I change bandwidth to setQuality(400000, 100) i am reaching the desired
bandwidth limit of 75000 byte/s.
Stream is published with h264Settings.setProfileLevel(H264Profile.MAIN, H264Level.LEVEL_5_1).
Any clues?
These behaviour only occurs with outStream.videoStreamSettings = h264Settings;
If videoStreamSettings is not set to h264Settings all things are doing well as expected.

Here's a link that explains what BBSM is all about:
http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps533/index.html

NAC and BBSM access code management

Hello,
An organization has a network infrastructure in which a BBSM generates access codes for limited authorized time periods to allow Internet web access to wireless guests. If a guest exhausts the period he must request a new access code.
Now, if a Clean Access Server is deployed for admission control, a possible option could be to bypass posture assessment for those guest users and leave the the BBSM operation unchanged: with access code management for control and accountability purposes.
My doubt is if i could deploy some access code management capabilities in the NAC appliance, in order to move to it the access code mgmt functionality from the BBSM.
I would really appreciate any comment about that.
Thanks in advance.

Hi,
Check table 3 of the link below,
http://www.cisco.com/en/US/products/sw/netmgtsw/ps533/prod_eol_notice0900aecd805aeb23.html
Scrap that BBSM. You should be able to provide guest access w/ NAC. checkout this link
http://www.cisco.com/application/pdf/en/us/guest/products/ps6128/c1031/cdccont_0900aecd805b8b5c.pdf
Regards,
arburt

802.1x and BBSM

Hi,
Does anyone know if you can setup 802.1x with the Cisco BBSM?
The reason I ask this question, anyone in a wireless hotspot will be able to sniff your data.
regds
Johnny

I do not think the BBSM currently supports 802.1x, even the Data sheet for the product does not mention any such thing
http://www.cisco.com/en/US/products/sw/netmgtsw/ps533/products_data_sheet09186a00801df72b.html

Wireless guest access with Airspace

I understand the Airspace products have some guest access capability built into them. I have a hotel customer that has the following requirments.
First, he will have an AP in each conference room. He would have each AP set up with a different SSID. The guest username password used for logging in would be assigned to the SSID and be different for each conference room. I've been told this is not possible. While you can have more than one guest username/password they are not associated with any one AP or SSID.
Secondly, he would also like to be able to control the amount of bandwidth each conference room/group is assigned.
Can the Airspace stuff do this, or even something close to it?

Yeah - no.
The Airespace guest functionality is basic - you define an SSID which has 'WEb Auth' set on it, and users are prompted for a username/password that is auth'd against radius.
The sort of granular stuff you are looking for isn't there - maybe look at BBSM or something similar, although I don't know how well that interfaces with AireSpace if at all..
Regards
Aaron
Please rate helpful posts.

BBSM - Basic design for Wireless

I am designing a wireless/BBSM network for a customer. The will have AP's available with both a guest SSID and an Employee SSID. They have non-cisco switches. Can I still use BBSM for guest wireless access?

As long as the BBSM has IP/SNMP connectivity to the Aironet APs you should not have a problem. I would recommend you use the AP settings with packet inactivity timer in network elements.

BBSM content filtering

Hi,
We are keen to introduce wlan hotspots in our libraries to allow the public access to the internet, however we really require content filtering. Has anyone out there managed to filter content while using the BBSM? Can the BBSM perform content filtering at all or is the functionality limited to the "walled garden" feature? Can a proxy running Webmarshal or similar be used along with the BBSM?
Any help would be greatly appreciated.
Thanks,
Scott

Hi Scott,
We use a product called SurfControl on a Windows box to filter web traffic that flows through the BBSM. We set up a SPAN (or monitor) session on the switch to which both the BBSM and SurfControl Server are connected. I have not tried the built-in ISA feature in the BBSM, but it is my understanding the you can do filtering and monitoring with this feature enabled.
-Dave

PEAP VLAN With Great Instability

Hello,
I have a network running PEAP for user authentication and dynamic WEP keys generation (AP1231G, ACS 3.3 and Windows 2000 Certificate Services). All users are Windows XP or Windows 2000, with Aironet and non-Aironet Wireless cards.
Regardless the card used, the PEAP VLAN is running too unstable. Users authenticate, but very often (in periods of some few minutes) they are suddenly unauthenticated and connection goes off. I have an open VLAN, running with no WEP, before a BBSM authentication, which works very nice (connection is quite stable).
So, it seems problem is not on Access Points, but in something related to EAP authentication, once I have also noticed the same symptoms in an LEAP network, previously, and open VLANs work well.
Has someone faced such or a similar issue? Do you have any hint for solving this connection instability?
Thanks in advance,
Leonidas

We experenced similar symptoms. Our problem resulted from us entering an encryption key for the vlan on the AP. When we removed the encryption key and left encryption vlan XX mode wep mandatory
our problem ceased and the connection became stable. The AP and the ACS negotiate the WEP key automatically.
Hope this helps

Cisco BBSM CPU High

I dont if someone can help me in BBSM which is out of support but i say my problem.
When clients from rooms and
AP try to connect after username and password take a message"SendActivateSessionfailed" so
in Windows Task Manager the services atdial.exe and Atevent.exe have 95% of Server CPU
with the result a very very slow windows server.

First of All, Thanks for your reply.
If you have L2 loops on your network why not configure BPDU guard on your access layer?...I assume it is users causing the loops?!
We have M/W transmission Nodes connected to this router which run their own RSTP, so BPDU do come to our router, I don't think we can use BPDU Guard in this situation, or do I ?
...in particular look at rate-limiting APR packets:
This feature look good, but I have few doubts:
Can I use this ARP rate limit on sub-interfaces ?
If I do use ARP rate-limit on sub-interface, then in case rate of incoming ARP packets exceeds the configured limit, the router will place the sub-interface/VLAN interface to err-disabled mode or, will place whole interface in err-disabled mode.??
I think if I can configure this rate limit on sub-interface level then it will pretty much solve my issue as it will put particular sub-interface on err-disabled mode, and we will also get to know the source VLAN for our further diagnosis.

Hot Spot Printer for BBSM Server

Hello
We have ordered a BBSM Server and are now looking for a Hot Spot Printer which we can install at our reception. Does anyone no if there is a printer that is compatible with the BBSM Server. Here a example of what I mean / want:
http://www.dlink.ch/?go=jN7uAYLx/oIJaWVUDLYZU93ygJVYKOhST9vhLPG3yV3oUYh3jqltbNlwaaRp7D0sAmu5j3cf/YEPBM7n1aXnLEkZtuLQ
Thanks for any help.
Greets Erich

Hi,
You'll need to edit the jvm.cfg file, located into %JAVA_HOME%\jre\lib
Move the "-server" to the top of the list.
Hope this helps,
Kurt.

BBSM in an hub environment

Hello,
In a routed BBSM network, can we use BBSM for a network, behind a router, clients connected to hubs? Or do we need to have switches in the LAN?

In a routed environment, if you create a new switch with ip address 0.0.0.0 and type of "Null/directly connects to router", all clients can be connected.
I have no problem about that config.

WSLM with BBSM

Similar Messages

Maybe you are looking for