Motorola RFS7000 Series Troubleshooting Manual
  1. Manuals
  2. Brands
  3. Motorola Manuals
  4. Switch
  5. RFS7000 Series
  6. Troubleshooting manual

Motorola RFS7000 Series Troubleshooting Manual

Rf switch
Hide thumbs Also See for RFS7000 Series:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual, Installation Manual
RFS7000 Series RF Switch
Troubleshooting Guide

Advertisement

Table of Contents
loading

Related Manuals for Motorola RFS7000 Series

Summary of Contents for Motorola RFS7000 Series

  • Page 1 RFS7000 Series RF Switch Troubleshooting Guide...
  • Page 2 MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. Symbol is a registered trademark of Symbol Technologies, Inc. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007. All rights reserved.

  • Page 3: Table Of Contents

    Contents Chapter 1. Overview Wireless Switch Issues ..........1-2 Switch Does Not Boot Up .
  • Page 4 RFS7000 Series RF Switch Troubleshooting Guide Out of Band Management Port Status LED ......2-6 Chapter 3.

  • Page 5: About This Guide

    Screens and windows pictured in this guide are samples and can differ from actual screens. Documentation Set The documentation set for the RFS7000 Series RF Switch is partitioned into the following guides to provide information for specific user needs. RFS7000 Installation Guide - describes the basic setup and configuration required to transition to more advanced •...

  • Page 6: Notational Conventions

    RFS7000 Series Switch System Reference Guide Notational Conventions The following additional notational conventions are used in this document: Italics are used to highlight the following: • Chapters and sections in this and related documents Dialog box, window and screen names...

  • Page 7: Chapter 1. Overview

    Overview This chapter describes common system issues and what to look for while diagnosing the cause of a problem. Wherever possible, it includes possible suggestions or solutions to resolve the issues. The following sections are included: • Wireless Switch Issues •...

  • Page 8: Wireless Switch Issues

    1.1.3 Switch Does Not Obtain an IP Address through DHCP The RFS7000 Series Switch requires a routable IP address for the administrator to manage it via Telnet, SSH or a Web browser. By default, the switch boots up with a non-routable static IP address on the Out-of-Band Management port.

  • Page 9: Unable To Connect To The Switch Using Telnet Or Ssh

    Contact Motorola Support. 1.1.4 Unable to Connect to the Switch using Telnet or SSH The RFS7000 Series Switch is physically connected to the network, but connecting to the switch using SSH or Telnet does not work. The table below provides suggestions to troubleshoot this issue.

  • Page 10: Console Port Is Not Responding

    Contact Motorola Support. 1.1.6 Console Port is Not Responding The RFS7000 Series Switch console port is connected to the host computer’s serial port, but pressing the [Enter] key gets no response from the switch. The table below provides suggestions to troubleshoot this issue.

  • Page 11: Ge Interface Loses Vlans After Reboot

    • Check the access port LEDs for “Loadme” message on start-up. • With a packet sniffer, look for 8375 (broadcast) packets • Reset the RFS7000 Series Switch. If the switch is hung, it may begin to adopt access ports properly once it has been reset.

  • Page 12: Mobile Unit Issues

    Possible Issue Suggestions to Correct All else... Contact Motorola Support. 1.3 Mobile Unit Issues This section describes various issues that may occur when working with the Mobile Units associated with the wireless switch or associated Access Ports. Possible issues include: •...

  • Page 13: Poor Voice Quality Issues

    Verify that a long preamble is used with Spectralink phones. Spectralink phones 1.4 Failover Issues This section describes various issues related to the failover capabilities of the RFS7000 Series Switch. 1.4.1 Switch is Not Failing Over Switch is not failing over (Hot Standby) as appropriate.

  • Page 14: Installation Issues

    All else... Contact Motorola Support. 1.6 Miscellaneous Issues This section describes various miscellaneous issues related to the RFS7000 Series Switch which don’t fall into any of the previously called out issue categories. Possible issues include: • Excessive Fragmented Data or Excessive Broadcast •...

  • Page 15: Excessive Memory Leak

    Contact Motorola Support. 1.7 System Logging Mechanism The RFS7000 Series Switch provides subsystem logging to a Syslog server. There are two Syslog systems, local and remote. Local Syslog records system information locally, on the switch. The remote Syslog sends messages to a remote host. All Syslog messages conform to the RFC 3164 message format.
  • Page 16 1-10 Overview...

  • Page 17: Chapter 2. Led Information

    LED Information The RFS7010 RF Switch has four vertically-stacked LEDs on its front panel. Each of the switch’s Gigabit Ethernet ports have two status LEDs. These LEDs display two colors (green & amber), and three lit states (solid, blinking, and off). The following tables decode the combinations of LED colors and states for the System Status LEDs and the Gigabit Ethernet LEDs.

  • Page 18: System Status Leds

    LED Information 2.1 System Status LEDs 2.1.1 Start Up / POST (Primary System or Redundant System) System Status 1 LED System Status 2 LED Event Power off Green Blinking Green Blinking Power On Self Test (POST) running Green Solid Green Blinking POST succeeded (Operating System Loading) Green Solid POST succeeded (Normal Operation)

  • Page 19: Switch Status (Redundant System)

    LED Information 2.1.3 Switch Status (Redundant System) System Status 1 LED System Status 2 LED Event Power off Green Solid No Redundancy Feature Enabled Redundant System failed over and adopting Green Blinking Green Solid ports Alternating Green Blinking Green Blinking Redundant System not failed over.

  • Page 20: Gigabit Ethernet Leds

    LED Information 2.4 RJ-45 Gigabit Ethernet LEDs 2.4.1 RJ-45 Port Speed LED Port Speed LED Event 10 Mbps Green Solid 100 Mbps Green Blinking 1000 Mbps Amber Blinking Port Fault 2.4.2 RJ-45 Port Status LED Port Status LED Event No Link or Administratively shut down Green Solid Link present Green Blinking...

  • Page 21: Sfp Gigabit Ethernet Leds

    LED Information 2.5 SFP Gigabit Ethernet LEDs 2.5.1 SFP Port Speed LED Port Speed LED Event Green Blinking 1000 Mbps Amber Blinking Module or Tx/Rx Fault Loss 2.5.2 SFP Port Status LED Port Status LED Event No Link or Administratively shut down Green Solid Link present / Operational Amber Blinking...

  • Page 22: Out Of Band Management Port Leds

    LED Information 2.6 Out of Band Management Port LEDs 2.6.1 Out of Band Management Port Speed LED Port Speed LED Event 10 Mbps Green Solid 100 Mbps Amber Blinking Port Fault 2.6.2 Out of Band Management Port Status LED Port Status LED Event No Link Green Solid...

  • Page 23: Chapter 3. Network Events & Kern Messages

    Network Events & Kern Messages This chapter includes two network event tables to provide detailed information and understanding of the RFS7000 Series RF Switch network events that can occur. These tables are: • Network Event Message/Parameter Description Lookup • Network Event Course of Action Lookup •...
  • Page 24 Network Events 3.1 Network Event Message/Parameter Description Lookup Event Message Parameters AP adopt failure This event and message is currently not Not applicable. [acl disallow] configured. It will be configured in the next service release. AP adopt failure Access port <XX> was not adopted because XX = MAC (xx:xx:xx:xx:xx:xx) address of the [limit exceeded] maximum limit has been reached.
  • Page 25 Network Events & Kern Messages 3.1 Network Event Message/Parameter Description Lookup Event Message Parameters 16 AP detected Detected a new access port <XX>. XX = MAC (xx:xx:xx:xx:xx:xx) address of the access port. 17 Device msg Dropping DeviceInfo message from <XX> XX = MAC (xx:xx:xx:xx:xx:xx) address of the dropped [info] whose parent is <YY>.
  • Page 26 Network Events 3.1 Network Event Message/Parameter Description Lookup Event Message Parameters 28 MU Kerberos auth MUs failed to authenticate with the KDC at [MAC address of MU] failed <MU_MAC_address> (Error code <code>). [MAC xx:xx:xx:xx:xx of Radius server] [port on Radius server] [radius error code] 29 MU Kerberos auth MUs failed authentication via Kerberos.
  • Page 27 Network Events & Kern Messages 3.1 Network Event Message/Parameter Description Lookup Event Message Parameters 40 KDC user [added] Adding KDC User:<username> [user name][ time:<timestamp>. timestamp] 41 KDC user Changed KDC User:<username> [user name] [changed] time:<timestamp>. [timestamp] 42 KDC user [deleted] Removed KDC User:<username>...

  • Page 28: Network Event Course Of Action Lookup

    Network Events 3.1 Network Event Message/Parameter Description Lookup Event Message Parameters 56 Miscellaneous Internal Failure, out of ethernet buffers. debug events The license key on a WS-Lite cannot be KerberosWlanAuth upgraded. Operation::OnStart WSLiteValidation:FAILURE:%s is invalid [XML error string(if any)] %d-port license for WS-Lite. [number of radios (APs) in-use] RADIO_TYPE_FH EtherPortManager::EnsureNoCollisions(FO...
  • Page 29 Network Events & Kern Messages 3.2 Network Event Course of Action Lookup (Continued) Event Description Possible Course of Action Packet discard When an access port is adopted, the switch The access port may have been [wrong NIC] remembers which Ethernet port the access port removed and reconnected to another was adopted from.
  • Page 30 Network Events 3.2 Network Event Course of Action Lookup (Continued) Event Description Possible Course of Action AP adopt failure Switch ran out of licenses and could not adopt There are more AP devices than there [license disallow] this AP. are licenses. Either remove the extra APs or purchase more licenses.
  • Page 31 Network Events & Kern Messages 3.2 Network Event Course of Action Lookup (Continued) Event Description Possible Course of Action 19 Ether port A previously disconnected Ethernet port was re- If you see excessive amounts of this connected connected. message you may have a cable or switch hardware problem.
  • Page 32 3-10 Network Events 3.2 Network Event Course of Action Lookup (Continued) Event Description Possible Course of Action 35 WLAN max MU This is an incorrect message. It is not really the count reached ACL that denied association; it is really that the 802.11 limit has been exceeded.

  • Page 33: Kern Messages

    3-11 Network Events & Kern Messages 3.2 Network Event Course of Action Lookup (Continued) Event Description Possible Course of Action 50 Standby auto- The Standby switch is auto-reverted from Active revert to Monitoring. This event is reported by the Standby switch. 51 Primary auto-revert The Primary wireless switch is auto-reverted from Halted to Connected.
  • Page 34 3-12 Network Events 3.3 KERN Messages (Continued) Module Message Description ccdev.c PKT_ERR( ""ccdev : %s bad Another program module tried cmd id : %d"", to set a command for a vlan __FUNCTION__, cmd->id ); device, but the command is not known to the packet driver.
  • Page 35 3-13 Network Events & Kern Messages 3.3 KERN Messages (Continued) Module Message Description crypt.c PKT_INFO( ""%s decrypt Detailed failure on WEB failure: ""MACSTR"" iv32 = decrypt failure. 0x%x iv16 = 0x%x\n"",); crypt.c PKT_INFO( ""TKIP Replay TKIP: Replay check failed for check fail ""MACSTR""...
  • Page 36 3-14 Network Events 3.3 KERN Messages (Continued) Module Message Description crypt.c PKT_INFO( ""qos admission The intended receiving station control verification failed\n"" has exceed its bandwidth use allocated by QOS. crypt.c PKT_ERR( ""unknown %s The WLAN has an encryption encryption type %d"",); type that is unknown to the packet driver.
  • Page 37 3-15 Network Events & Kern Messages 3.3 KERN Messages (Continued) Module Message Description flowctl.c PKT_WARN( ""fc:mu removed An ACK for WISP packet has before fc ack on prtl arrived, but the corresponding ""MACSTR,); receiving station has been deleted from system. flowctl.c PKT_WARN( ""fc:dropped An association response or...
  • Page 38 3-16 Network Events 3.3 KERN Messages (Continued) Module Message Description flowctl.c PKT_INFO( ""fc freed ack q pkt A packet pending ACK has seq %d, tx time %u, now been there for too long %u"",); (beyond 7 seconds ) and forcefully removed it.. flowctl.c PKT_INFO( ""fc q extract:seq Received a flow control...
  • Page 39 3-17 Network Events & Kern Messages 3.3 KERN Messages (Continued) Module Message Description flowctl.c PKT_INFO( MACSTR"" fc Attempt to send a managment mgmt q:failed"", MAC2STR( packet has failed. prtl_ptr->cfg.addr ) ); flowctl.c PKT_WARN( The wireless header and the ""mismatch(roam?): WISP header have dest=""MACSTR"", its mismatched radio mac seq=%d, prtl=""MACSTR"", its...
  • Page 40 3-18 Network Events 3.3 KERN Messages (Continued) Module Message Description flowctl.c PKT_ERR( ""psp update tim: Tried to send a WISP update alloc skb failed"" ); TIM, but failed to get a new buffer. gag.c PKT_WARN(""vlan out of Another program module try range""...
  • Page 41 3-19 Network Events & Kern Messages 3.3 KERN Messages (Continued) Module Message Description pal.c PKT_ERR( ""%s : 802.11 data Received a runt 802.11 pkt too small (%d bytes)"", packet. __FUNCTION__, skb->len ); pal.c PKT_ERR( ""%s: unknown Received unkown 802.11 frame type %x"", frame type.
  • Page 42 3-20 Network Events 3.3 KERN Messages (Continued) Module Message Description pal.c PKT_ERR( ""Multicast Detected that the swich is Flooding Detected, limiting making too many copies of a the segments in broadcast multicast packet that uses too domain to %d"", copy_limit ); much system bandwidth.
  • Page 43 3-21 Network Events & Kern Messages 3.3 KERN Messages (Continued) Module Message Description pal.c PKT_INFO( ""dropping wisp Drop an unicast WISP packet packets to another switch not destined for the switch. ""MACSTR,); pal.c PKT_INFO( ""dropping L2 wisp Received L2 WISP packet with packets in wrong direction, the wrong direction bit.
  • Page 44 3-22 Network Events 3.3 KERN Messages (Continued) Module Message Description ps_capwap.c PKT_WARN(""capwap skb The actual packet length is length underrun: received %d, smaller than what the capwap expected %d\n"", skb->len, header indicates. dlen ); ps_capwap.c PKT_ERR( ""%s : CC sending CC server is sending a data data pack to unknown MU"", packet to a station that the...
  • Page 45 3-23 Network Events & Kern Messages 3.3 KERN Messages (Continued) Module Message Description psp.c PKT_ERR( ""dtim poll: recvd Received a DTIM poll with bad bss index"" ); bad BSS index. psp.c PKT_WARN( ""pspoll: psp bit Received a PSP poll from the not set""...
  • Page 46 3-24 Network Events 3.3 KERN Messages (Continued) Module Message Description reassembly.c PKT_ERR( ""fragment too big Reassembed packets does not to copy:%d bytes"", skb->len ); fit into a single packet buffer. reassembly.c PKT_ERR( ""reassy:unknown Unknown WISP fragment type cmd type"" ); or command.

  • Page 47: Mobile Unit Disassociation Codes

    MU Disassociation Codes 4.1 802.11 Mobile Unit Disassociation Codes 802.11 or Motorola/WPA Reason Code Description REASON_CODE_80211_SUCCESS Reserved internally to indicate success. REASON_CODE_80211_UNSPECIFIED_ERROR Unspecified reason. DISASSOCIATION_REASON_CODE_STATION_LEAVING_ESS Deauthenticated because sending station has left or is leaving IBSS or ESS. DISASSOCIATION_REASON_CODE_INACTIVITY Disassociated due to inactivity.
  • Page 48 MU Disassociation Codes 4.1 802.11 Mobile Unit Disassociation Codes (Continued) 802.11 or Motorola/WPA Reason Code Description 17 DISASSOCIATION_REASON_CODE_4WAY_IE_DIFFERENCE Information element in 4-way handshake different from associated request/probe response/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.

  • Page 49: Chapter 5. Troubleshooting Snmp Issues

    Troubleshooting SNMP Issues The following SNMP-releated issued could require troubleshooting as SNMP issues are experienced with the RFS7000 switch. 5.1 MIB Browser not able to contact the agent General error messages on the MIB Browser: Timeout, No Response. The client IP where the MIB browser is present should be made known to the agent. Adding SNMP clients through CLI or Applet can do this.

  • Page 50: Not Getting Snmptraps

    Troubleshooting SNMP Issues 5.5 Not getting snmptraps Check whether snmp traps are enabled through CLI or Applet. Configure MIB browser to display notifications or traps. (This would generally be a check box in the MIB browser preferences). 5.6 Still Not Working Double check Managers' IP Address, community string, port number, read/write permissions, and snmp version.

  • Page 51: Chapter 6. Security Issues

    Security Issues This chapter describes the known troubleshooting techniques for the following data protection activities: • Switch Password Recovery • RADIUS Troubleshooting • Rogue AP Detection Troubleshooting • Troubleshooting Firewall Configuration Issues...

  • Page 52: Switch Password Recovery

    Security Issues 6.1 Switch Password Recovery If the switch Web UI password is lost, you cannot get passed the Web UI login screen for any viable switch configuration activity. Consequently, a password recovery login must be used that will default your switch back to its factory default configuration.
  • Page 53 Security Issues • Add a Radius client in Radius server configuration with the Switch’s VLAN interface, IP address and subnet, which have been marked as management • Save the current configuration • Ensure that the WLAN settings haves been set to use the on-board/local Radius server by entering the local IP address or the switch management VLAN IP address Radius Server is rejecting the user Ensure the following have been attempted:...

  • Page 54: Troubleshooting Radius Accounting Issues

    "enable" and should also the status of the configured detection scheme. • Check for the "Motorola AP" flag in rulelist context. If it is set to "enable", then all the detected APs will be added in approved list context.

  • Page 55: Troubleshooting Firewall Configuration Issues

    Security Issues 6.4 Troubleshooting Firewall Configuration Issues Motorola recommends adhereing to the following guidelines when dealing with problems related to RFS7000 Firewall configuration: A Wired Host (Host-1) or Wireless Host (Host-2) on the untrusted side is not able to connect to the Wired Host (Host-3) on the trusted side 1.
  • Page 56 Security Issues...

  • Page 57: Appendix A Customer Support

    Software type and version number • Motorola responds to calls by email, telephone or fax within the time limits set forth in support agreements. If you purchased your Enterprise Mobility business product from a Motorola business partner, contact that business partner for support.
  • Page 58 A - 2 RFS7000 Series RF Switch Troubleshooting Guide...
  • Page 60 MOTOROLA INC. 1303 E. ALGONQUIN ROAD SCHAUMBURG, IL 60196 http://www.motorola.com 72E-103892-01 Revision A January 2008...

Table of Contents