Michael McNamara
technology, networking and IP telephony
WS5100 v3.x Getting Started
0November 7, 2007
The following document is provided as a basic guide on how to configure the Motorola WS5100 Wireless LAN Switch with release 3.x software. You should use the initial username of “cli” at the login prompt. At the username/password prompts you should use “admin” and “superuser” respectively.
You should connect to the console port a serial cable (null) with 19200,8,N,1.
The example below will configure Ethernet 2 as a trunk port with the management interface in VLAN 200 (10.107.255.199/24) and the default gateway as 10.107.255.1. The order of the commands is very important when you start to trunk the interface.
Please press Enter to activate this console. WS5100 release 3.0.3.0-003R Login as 'cli' to access CLI. WS5100 login: cli User Access Verification Username: admin Password: ********* Welcome to CLI WS5100> WS5100> enable WS5100# configure terminal WS5100(config)# interface eth2 WS5100(config-if)# switchport mode trunk WS5100(config-if)# switchport trunk native vlan 200 WS5100(config-if)# switchport trunk native tagged WS5100(config-if)# switchport trunk allowed vlan none WS5100(config-if)# switchport trunk allowed vlan add 200 WS5100(config-if)# exit WS5100(config)#interface vlan 200 WS5100(config-if)# ip address 10.107.255.199/24 WS5100(config-if)# management WS5100(config-if)# exit WS5100(config)# interface vlan 1 WS5100(config-if)# no ip address WS5100(config-if)# shutdown WS5100(config-if)# exit WS5100(config)# ip default-gateway 10.107.255.1 WS5100(config)# end WS5100# write memory
Once you’ve complete those steps you should be able to ping the device. At that point you can connect to the web based console to complete the configuration.
https://10.107.255.199
You should of course substitute the IP addresses above with your own addresses.
Cheers!
802.11 Dissassociation Codes
4November 7, 2007
These codes can be extremely useful in troubleshooting wireless issues.
Value | 802.11 or Symbol/WPA Reason Code | Description |
0 | REASON_CODE_80211_SUCCESS | Reserved internally to indicate success |
1. | REASON_CODE_80211_UNSPECIFIED_ERROR | Unspecified Reason |
3. | DISASSOCIATION_REASON_CODE_STATION_LEAVING_ESS | Deauthenticated because sending station has left or is leaving IBSS or ESS |
4. | DISASSOCIATION_REASON_CODE_INACTIVITY | Disassociated due to inactivity |
5. | DISASSOCIATION_REASON_CODE_STATION_LIMIT_EXCEEDED | Disassociated because AP is unable to handle all currently associated stations |
6. | DISASSOCIATION_REASON_CODE_CLASS_2_PKT_FROM_NON_AUTH | Class 2 frame received from non-authenticated station |
7. | DISASSOCIATION_REASON_CODE_CLASS_3_PKT_FROM_NON_ASSOC | Class 3 frame received from non-associated station |
8. | DISASSOCIATION_REASON_CODE_STATION_LEAVING_BSS | Disassociated because sending station has left or is leaving BSS |
9. | DISASSOCIATION_REASON_CODE_STATION_NOT_AUTHENTICATED | Station requesting re-association is not authenticated with responding station |
13. | DISASSOCIATION_REASON_CODE_INVALID_INFORMATION_ELEMENT | Invalid Information Element |
14. | DISASSOCIATION_REASON_CODE_MIC_FAILURE | Michael MIC failure |
15. | DISASSOCIATION_REASON_CODE_4WAY_HANDSHAKE_TIMEOUT | 4-Way Handshake timeout |
16. | DISASSOCIATION_REASON_CODE_GROUP_KEY_UPDATE_TIMEOUT | Group key update timeout |
17. | DISASSOCIATION_REASON_CODE_4WAY_IE_DIFFERENCE | Information element in 4-Way Handshake different from Re-associated request/Proberesponse/Beacon |
18. | DISASSOCIATION_REASON_CODE_MULTICAST_CIPHER_INVALID | Multicast Cipher is not valid |
19. | DISASSOCIATION_REASON_CODE_UNICAST_CIPHER_INVALID | Unicast Cipher is not valid |
20. | DISASSOCIATION_REASON_CODE_AKMP_NOT_VALID | AKMP is not valid |
21. | DISASSOCIATION_REASON_CODE_UNSUPPORTED_RSNE_VERSION | Unsupported RSN IE version |
22. | DISASSOCIATION_REASON_CODE_INVALID_RSNE_CAPABILITIES | Invalid RSN IE Capabilities |
23. | DISASSOCIATION_REASON_CODE_8021X_AUTHENTICATION_FAILED | IEEE 802.1X Authentication failed |
44. | DISASSOCIATION_REASON_CODE_PSP_TX_PKT_BUFFER_EXCEEDED | Symbol defined (non 802.11 standard) code. The Wireless Switch has exceeded it’s time limit in attempting to deliver buffered PSP frames to the Mobile Unit without receiving a single 802.11 PS Poll or NULL data frame. The Wireless Switch begins the timer when it sets the Mobile Unit’s bit in the TIM section of the 802.11 beacon frame for the BSS. The time limit is at least 15 seconds. The Mobile Unit is probably gone (or may be faulty). |
77. | DISASSOCIATION_REASON_CODE_TRANSMIT_RETRIES_EXCEEDED | Symbol defined (non 802.11 standard) codes. The Wireless Switch has exceeded it’s retry limit in attempting to deliver a 802.1x EAP message to the Mobile Unit without receiving a single 802.11 ACK. The retry limit varies according to traffic type but is at least 64 times. The Mobile Unit is either gone or has incorrect 802.1x EAP authentication settings. |
Motorola Wireless LAN
0November 6, 2007
I’ve worked primarily with Motorola (formerly Symbol) since the early 802.11b FHSS (Frequency Hopping Spread Spectrum) days. When 802.11b DSSS (Direct Sequence Spread Spectrum) came to the forefront I worked with the Symbol 4121/4131 Access Points (some of which were OEM’d for Nortel Networks at the time). The Access Points were very versatile and had a very extensive SNMP mib. I was able to write several Perl scripts to help manage the large number of Access Points that we had deployed at numerous locations and facilities.
Symbol was th
e industry’s first company to design a switched-wireless networking architecture, pioneering the thin or lightweight Access Points (or Access Ports as they would come to be known as). The Symbol WS5000 Wireless LAN Switch was driven by LynuxWorks operating system. Later software releases of the WS5000 and later the WS5100 would use an internally developed version of Linux (I know their using Linux I’m just not 100% sure who’s developing it for them). The primary wireless design constraint with the Motorola WS5100 is the maximum 48 port Access Port adoption limit. The hardware can only support 48 simultaneous Access Ports in a single switch. At one hospital we have over 200 Access Ports and over 18 WS5100s deployed, 9 primary WS5100s and 9 standby WS5100s .
Motorola has just recently released the RFS7000 Wireless LAN Switch that promises to support up to 256 Access Ports. I won’t go into all the features, I’ll let you find that out from Motorola’s web site. Motorola’s recent Wi-NG software release (v3.x) also offers clustering options allowing around 2,500 Access Ports within a single cluster. In previous releases you needed to have a primary and standby WS51000 for every switch, with clustering you can now have N+1 redundancy within the cluster. The new software also sports a very Cisco like command line interface which is great step up from the previous CLI interface in their v2.x software release. Network administrators will also be happy to know that the same version of software will now run on all “Motorola Wireless LAN Infrastructure”, including the WS2000, WS5100, RFS7000 and AP5131. I’ve worked with all three types of thin Access Ports currently available from Motorola; the AP100 (802.11b), the Ap200 (802.11a/b), and the latest AP300 (802.11a/b/g). We’ve deployed these Access Ports using Nortel ES460, ERS5520 switches providing Power over Ethernet (PoE).
The web based console on the early (v2.x software) releases was a Java based application that was horrible to work with from a configuration and troubleshooting perspective. It was slow and would continually crash and lockup. In order to alleviate this problem I wrote a web based application so our network engineers and help desk could monitor the wireless network without having to launch the Java application. I wrote the application in Perl at the time because that was the language I was most familiar with and the most comfortable. The application uses SNMP to query the wireless LAN switch and then outputs the data to the user.
You can find the source code along with some additional details on my website under the Perl section. The application will only work against v2.x software releases. Motorola completely re-designed their software in their v3.x software release along with the associated SNMP mibs.
I just recently started looking a Meru Networks as an alternative solution to Motorola.
