My ProCurve Wireless Edge Services xl Module isn’t succeeding at Layer 3 adoption of my radio ports. What could be wrong?
Radio ports that were manufactured or adopted by a ProCurve Wireless Edge Services xl Module running WS.01.xx software will require an update to their bootloader code prior to their successful adoption at Layer 3. If you recently updated from WS.01.xx to WS.02.xx, it is important to prepare your radio port for Layer 3 adoption by first adopting the radio port in the same Layer 2 domain, either by connecting it directly to the Wireless Services-Enabled 5300xl switch or by connecting to an infrastructure switch in the same Layer 2 domain. The adoption time is extended slightly as the new bootloader code loads. When the radio port has been adopted, (the radio port LEDs flash about once every five seconds) the correct radio port bootloader code is installed. You may now finish the process for adopting the radio port at Layer 3 (see “Radio Port Adoption” in the Wireless Edge Services xl Module Management and Configuration Guide). If you continue to have difficulty adopting the radio port at
Related Questions
- I created an "allow any" ACL on my ProCurve Wireless Edge Services xl Module, and now even the communication I intended to allow is not getting through. What could be wrong?
- My ProCurve Wireless Edge Services xl Module isnt succeeding at Layer 3 adoption of my radio ports. What could be wrong?
- My ProCurve zl Wireless Edge Services Module isn’t succeeding at adoption of my radio ports. What could be wrong?
