How to troubleshoot Motorola Switch that does not boot up?
If your Motorola Switch doesn't power on, check the power cables, fuses, and UPS power. The front panel LEDs should light up when power is applied. If the problem persists, have a qualified electrician inspect the power source.
What to do if Motorola RFS does not obtain an IP address through DHCP?
First, ensure DHCP is enabled in the switch configuration. If it is, connect another DHCP-configured host to the same network to verify it obtains an address. Also, verify that DHCP is enabled for the specific Gigabit Ethernet interface connected to your external network using the CLI command or Web UI. Use a sniffer tool to confirm DHCP packets are being sent to the port. Finally, check that the switch is not configured with a static IP address on that port.
Why am I unable to connect to Motorola RFS Switch using Telnet or SSH?
First, verify that Telnet or SSH are enabled using the CLI or Web UI. Note that Telnet is disabled by default. Also, the maximum allowed sessions is 8 concurrent users connected to the switch, so verify that this threshold hasn't been reached. Finally, ensure that Telnet and SSH traffic is permitted on the primary VLAN.
How to fix Motorola RFS when access ports are not adopted?
First, verify the license key set in the switch. Ensure the country code is entered into the switch before adopting any Access Ports, as the switch isn't fully functional until this is set. Check that the Access Ports are connected to the network and powered on. Also, verify the switch isn't configured with an access control list that prevents Access Port adoption, and that Access Port adoption isn't set to “deny”. Ensure the Access Port adoption policy is added with a WLAN. Check the Motorola RF Series Switch ACL adoption list to ensure it doesn't include the Access Ports that are not being adopted. Finally, use a packet sniffer to look for 8375 (broadcast) packets and reset the Motorola RF Series Switch.
What to do if Motorola RFS Web UI is sluggish or not responding?
First, check the connection between the switch and the console system to ensure it is functioning normally. Verify the data packets are being sent to and from the switch using a sniffer tool. Set the country name for the switch, as it is set to “none” by default. Check Syslog for any type of packet storm. With large numbers of Access Ports, changing the configuration quickly may cause the switch to not refresh properly, at least immediately following configuration. Ensure you are using Sun Java JRE 1.5 or later. To successfully access the switch Web UI through a firewall, UDP port 161 must be open in order for the switch’s SNMP back end to function.
What to do if the console port on Motorola RFS is not responding?
Ensure that a console cable is connected from the console port to the host computer’s serial port. Verify a serial terminal emulation program, such as HyperTerminal, is in use on the host computer. Check the serial port settings in the serial terminal emulation program being used. The correct settings are: Terminal Type VT-100 Port Any COM port Terminal Settings 19200 bps transfer rate 8 data bits no parity 1 stop bit no flow control.
How to troubleshoot excessive memory leak on Motorola Switch?
Use the CLI or Web UI’s Diagnostics section to check the available virtual memory. If any one process displays an excessive amount of memory usage, that process could be one of the possible causes of the problem. Keep the maximum number of Telnet or SSH sessions low (6 or less), even though up to 8 sessions are allowed.
How to resolve traffic congestion with data traffic on Motorola RFS?
Maintain voice and data traffic on separate WLANs. Use a QoS Classifier to provide dedicated bandwidth if data and voice traffic are running on the same WLAN.
What causes Motorola RFS Sensor Port to frequently go up and down?
This may be caused by the sensor being unable to find its server. Ensure that the detection configuration is correct and that all cables are secure.
Why is Motorola MU not being associated after Access Port adoption?
Verify that the switch has adopted the Access Port with which the MU is trying to associate. Verify on the MU that the correct ESSID has been applied to the MU. Verify that the Ethernet port connected to the network and has a valid configuration. If DHCP is used, verify that the Ethernet cable is connected to the same NIC upon which DHCP services are enabled. Verify that the correct security settings are applied to a WLAN in which the MU is trying to associate.
To Next Page
General
