RFM-OWS2430-90802.11 a/g Wireless Mesh Type Networking Device

USER’SGUIDE Including Manager/One ® ACCESS/ONE ® NETWORK Indoor and Outdoor Wireless System Networks Without Wires ® Copyright © 2003 – 2007 Strix Systems, Inc. All Rights Reserved. February 8th, 2007 210-0007-02 Rev. E Front Matter Networks Without Wires ® Access/One ® Network Including Manager/One ® Copyright © 2003 – 2007 Strix Systems, Inc. 26610 Agoura Road Calabasas, CA 91302 USA www.strixsystems.com All rights reserved. This document may not be reproduced or disclosed in whole or in part by any means without the written consent of Strix Systems, Inc. Part Number: 210-0007-02 Revision E Copyright Notice Copyright © 2003 – 2007 Strix Systems, Inc. All rights reserved. This document may not be reproduced or disclosed in whole or in part by any means without the written consent of Strix Systems, Inc. Access/One Network is a registered trademark of Strix Systems, Inc. All other trademarks and brand names are marks of their respective holders. FCC Notice Strix wireless network devices comply with Part 15 of the FCC Rules. Operation is subject to the following two conditions: 1.The device may not cause harmful interference. 2.The device must accept any interference received, including interference that may cause undesired operation. Strix wireless network devices have been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. Strix wireless network devices generate, use, and radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If the wireless network device does cause harmful interference to radio or television reception, which can be determined by turning the wireless network device off and on, the user is encouraged to try to correct the interference by one or more of the following measures: ◗Reorient or relocate the receiving antenna. ◗Increase the separation between the wireless network device and the affected receiver. ◗Connect the wireless network device into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. Other Notices Industry Canada Notice This Class B digital apparatus complies with Canadian ICES-003. Cet appareil numérique de la classe B est conforme à la norme NMB-003 du Canada. VCCI Notice The Strix IWS and OWS products are Class B wireless network devices based on the standard of the Voluntary Control Council for Interference from Information Technology Equipment (VCCI). If the wireless network device is used near a radio or television receiver in a domestic environment, it may cause radio interference. Install and use the wireless network device according to the instruction manual. European Community (EC) Directives and Conformity Strix wireless network devices are in conformity with the Essential Requirements of R&TTE Directive 1999/5/EC of the European Union. Non-Modification Statement Unauthorized changes or modifications to Strix devices are not permitted. Modifications to Strix devices will void the warranty and may violate FCC regulations. RF Exposure Requirements To ensure compliance with FCC RF exposure requirements, the antenna used for Strix wireless network devices must be installed to provide a separation distance of a minimum of 2 meters (6.56 feet) or more from all persons, and must not be co- located or operated in conjunction with any other antenna or radio transmitter. Installers must follow these installation instructions. Safety Warnings (OWS only) The OWS (Outdoor Wireless System) product must be installed by a trained professional installer only. Read all safety warning before commencing an OWS installation. General Safety Warning Electrical Power Warning Lightning Activity Warning Explosive Device Proximity Warning ALWAYS BE AWARE OF ELECTRICAL POWER LINES! You can be killed if any antennas come near electrical power lines. Carefully read and follow all instructions in this manual. By performing these installation instructions, you may be exposed to hazardous environments and high voltage. Use caution when installing the Strix OWS product. The OWS product must be installed by a trained professional installer only. Read the installation instructions before you connect the wireless network device to its power source. Do not connect or disconnect cables during periods of lightning activity. For each antenna, a surge protective device meeting IEC 61000-4- 5, Level 4 or IEEE C 62.41 A3/B3 requirements must be used to prevent potential damage from very high surges (for example, surges caused by lightning). Do not operate your wireless network device near unshielded blasting caps or in an explosive environment. Antenna Placement Warning Ground Warning Power Cord Assembly Caution Battery Caution Do not locate any antenna near overhead power lines or other electric light or power circuits, or where the antenna can come into contact with such circuits. When installing antennas, take extreme care not to come into contact with such electrical circuits, as they can cause serious injury or death. For the correct installation and grounding of antennas, please refer to national and local codes (for example, US:NFPA 70, National Electrical Code, Article 810; in Canada: Canadian Electrical Code, Section 54). You must ALWAYS install an external grounding wire on the OWS product. The ground connection must be complete before connecting power to the OWS enclosure—a simple continuity check between the enclosure and the ground termination point can confirm this. Grounding of the OWS must comply with National Electrical Code (NEC) requirements, unless local codes in your area take precedence over the NEC code. An …

Text truncated - open the document above for the full version.

Access / One ® Network Getting Started23 2 Getting Started This chapter defines the prerequisites for deploying your Access/One Network and instructions for how to install the Manager/One plug-in. Host Network Requirements Your Access/One Network requires the presence of several network servers and services in the host wired network, including: ◗DHCP Server (see also “Non-DHCP Server Environment” on page 25) ◗FTP Server ◗Internet Browser (Internet Explorer, version 6.0 and above) DHCP Server A DHCP server is necessary to distribute IP addresses and ancillary information to your Access/One Network. Many routers contain DHCP servers and allow the specification of DHCP options necessary to provide network information that would otherwise be configured manually. Strix recommends that each module is given a DHCP reservation allowing it to obtain the same IP address whenever it’s required. The reservation is based on MAC address and may allow system administrators to specify options unique to a module as well as a network. Because modules within Access/One Network change their addresses frequently (due to the network’s dynamic self-configuration capability), the DHCP server must support IP address persistence. Without IP address persistence different addresses will be assigned every time, resulting in invalid self-configurations and network topologies. Access / One ® Network 24Getting Started 2 To prevent any interruption in service, the DHCP lease time should be set to infinite whenever possible, though Strix recommends configuring a reservation for each Access/One Network module regardless of the lease time. Doing so will avoid any unanticipated problems and maintain management consistency. All modules within your Access/One Network require the following RFC 2132 option numbers to be specified: Examples of DHCP servers include (but are not limited to): ◗Windows 200X Server ◗Cisco IOS ◗Linux ◗Sun OS OptionTitleDescription 1Subnet MaskNetwork subnet mask, as applied to the given IP address. 2Time OffsetNumber of hours the DHCP client will add or subtract from SNTP time. 3Default RouterSpecifies the default gateway for this network segment. 6DNS ServerSpecifies one or two DNS servers (by priority). 12Host NameSpecifies the unique system name of the module. 15Domain NameSpecifies the domain name for this network. This is used to fully qualify any hostname operations that the module may generate (for example, ping node1 = ping node1.strixsystems.com). This applies to module operations only and does not affect users. 42NTP ServerSpecifies the NTP server IP address (local or Internet). Access / One ® Network Getting Started25 2 Non-DHCP Server Environment In the absence of a DHCP server, Strix modules utilize zero configuration networking protocols to allocate IP addresses. In this case, modules will automatically select unique and non-conflicting IP addresses, enabling users to statically configure the modules and manage the Strix network effectively. FTP Server An FTP (or secure FTP) server is required to transfer firmware and configuration data from distribution media to Access/One Network modules. Software distribution via an FTP server relies on user accounts to maintain security. Access/One Network modules are capable of specifying a user name and password (including anonymous) to log into an FTP server. Directory access may be configurable based on the FTP server software, so files related to your Access/One Network may be available only to Access/One Network modules. TFTP is not currently supported. Some examples of FTP servers include: ◗Windows 200X Server ◗Linux ◗Sun OS ◗Many shareware/freeware implementations For Access/One Network to operate properly in the automatic mode, IP gateway, DNS server or DHCP server IP addresses must be configured correctly. Access/One Network firmware and configuration files must be transferred and distributed throughout your Access/One Network from the Manager/One interface, using the FTP configuration parameters you provide. Any other method for transferring and distributing files is not supported by Strix Systems. Access / One ® Network 26Getting Started 2 Internet Browser Access/One Network and the Manager/One interface are supported in Windows Internet Explorer, version 6.0 and above. Figure 7. Windows Task Manager Screen Resolution Manager/One uses detailed graphical designs within its interface. The quality and relative sizes of the screen images generated by Manager/One will depend on the preferences you have set for your screen resolution. For best results, Strix recommends using a screen resolution of 1280 x 1024 pixels. Privacy settings for Internet Explorer must be set to medium or low for interoperability with Manager/One. Also, Internet Explorer may stop responding if connectivity to the network server is interrupted for extended periods (this does not apply to normal network reboots or outages). In this case, use the Windows Task Manager to manually end the task. (Ctrl + Alt + Del). Do not leave Internet Explorer running unless you are actively managing the network server. Access / One ® Network Getting Started27 2 About Manager/One Manager/One is a graphical management interface that runs on Internet Explorer, version 6.0 or above. It allows you to view, monitor, configure and manage your Access/One Network at any level (network, subnet, node, or individual module) from your Web browser. Figure 8 shows an example of the Manager/One interface at the subnet level, where network nodes and the individual modules contained within each node are displayed. Figure 8. Manager/One Interface (Subnet Level) Installing the Manager/One Plug-In The Manager/One plug-in for Internet Explorer must be installed on your PC to facilitate discovery and management of your Access/One Network and all of its individual elements. Once installed, the Manager/One plug-in performs an automatic self-discovery procedure, effectively capturing an accurate and detailed image …

Text truncated - open the document above for the full version.

Access / One ® Network Managing the Network73 5 After inputting data (or making selections), click on the Update button to update this page, then click on the Apply Configuration tab to propagate your changes across the network. If necessary, you can click on the factory default (FD) button in the toolbar to reset all data on this page to its factory default state. Network Management General This command allows you to define the level of security for the various management interface options used to manage your Access/One Network, and provides options for enabling or disabling SNMP Management and FTP server functionality. Figure 56. General Management Interface Security The following options are available with this command: ◗Shell ChooseClear & Secure to allow network management via an unsecured Telnet connection and a Secure SHell (SSH) connection, or choose Secure Only to restrict management to an SSH connection only. Alternatively, you can choose None to prevent access from either option. Access / One ® Network 74Managing the Network 5 If you are allowing access via Telnet or SSH, enter a value—in seconds—in the Shell Timeout field to define how long the connection will remain open during idle periods. Setting the shell timeout value to 0 (zero) will disable the timer and keep the session open, even when idle. ◗Web ChooseClear & Secure to allow network management from your Web browser via HTTP (clear) and HTTPS (secure), or choose Secure Only to restrict management via a secure HTTPS connection only. Alternatively, you can choose None to prevent all Web management access. ◗CIMS (Cloud Infrastructure Management System) ChooseClear & Secure to allow network management via CIMS, where security levels are controlled automatically. Alternatively, you can define the security level manually by choosing Secure Only or Clear Only. ◗SNMP Management Check this box to enable network management via an SNMP (Simple Network Management Protocol) management console. Your Access/One Network supports the 802.11 MIB (Management Information Base), as well as Strix proprietary MIBs. Any MIB I or MIB II compliant SNMP management console (such as CiscoWorks or HP OpenView) can be used to manage your network remotely. ◗FTP Server Check this box to enable FTP server functionality (this box must be checked if you want to update your firmware or transfer system configuration files). After inputting data (or making selections), click on the Update button to update this page, then click on the Apply Configuration tab to propagate your changes across the network. If necessary, you can click on the factory default (FD) button in the toolbar to reset all data on this page to its factory default state. Access / One ® Network Managing the Network75 5 SNMP This command allows you to define the SNMP Communities, the SNMP System, and any specific SNMP Trap Managers. With SNMP enabled and the settings on this page defined, your Access/One Network will support most common SNMP management consoles. The system also supports Syslog (System Logging) via an SNMP manager (in parallel with basic Syslog services) where Syslog text information is encoded in an SNMP trap message and presented to the operator. SNMP (Simple Network Management Protocol is a standard protocol that regulates network management over the Internet. SNMP uses TCP/IP to communicate with a management platform, and offers a standard set of commands that make multi- vendor operability possible. SNMP uses a standard set of definitions, known as a MIB (Management Information Base), which can be supplemented with Enterprise- specific extensions. Strix provides its own proprietary MIBs. For more information about Strix MIBs, contact Strix technical support. Figure 57. Configuring Access/One Network for SNMP Access / One ® Network 76Managing the Network 5 The following options are available with this command: ◗SNMP Communities Enter your GET Community (read), SET Community (write) and TRAP Community in the corresponding fields. The defaults for these fields are: •GET Community: public •SET Community: netman •TRAP Community: public ◗SNMP System Enter the Contact and Location information for the person managing your Access/One Network. ◗SNMP Trap Managers Enter a valid IP address for any SNMP Trap Manager you intend to use. The SNMP Trap Manager you choose must be enabled, so ensure that the appropriate box is checked. If you have multiple SNMP Trap Managers assigned, you can delete a manager by clicking on the X icon associated with each manager. ◗Traps ChooseOpen to expand the primary elements of the SNMP Trap Manager tree. From here you can make management selections by checking (or unchecking) the appropriate check boxes. When finished making your selections, choose Close to collapse the tree. After inputting data (or making selections), click on the Update button to update this page, then click on the Apply Configuration tab to propagate your changes across the network. If necessary, you can click on the factory default (FD) button in the toolbar to reset all data on this page to its factory default state. Figure 58. Managing Traps Access / One ® Network Managing the Network77 5 Trusted IP Addresses This command allows you to enable or disable the Trusted Mode and assign specific trusted IP addresses. When this mode is enabled, only addresses assigned here will be trusted by the network for management at any network module. Figure 59. Assigning Trusted IP Addresses The following options are available with this command: ◗Trusted Mode You can only enable this option if you have added at least one trusted IP address. Once a trusted IP has been added, check this box to enable the trusted mode (or uncheck the box if you want to disable this feature). ◗IP Address You must add at least one IP address if you want to enable the trusted mode feature. To add an address, simply enter a valid IP address in this field then click on the Add button (the new address is listed below …

Text truncated - open the document above for the full version.

Access / One ® Network Managing the Network123 5 Rogue Monitor The Rogue Monitor provides a snapshot in table form of all rogue devices detected on a selected subnet. Figure 99. Rogue Monitor Although the displayed data is different, the organization of tables in all monitors is the same. For information about how to define the sort criteria within the Rogue Monitor table, see Figure 94. And similar to the Network Connect Monitor and the Wireless Client Query Monitor, the Rogue Monitor also includes the information button (i) in the top right corner of the window. Clicking on this button generates the RSSI Legend pop-up window (see Figure 96). Scan Use this command if you want to initiate an active scan for rogue devices. Active scans can take up to one minute to complete and network traffic will be disrupted during the scanning process. Results from the scan are reported in the Rogue Monitor table (see Figure 99). Ignore All Use this command to refresh the Rogue Monitor table with all detected rogue devices ignored. All ignored devices are grayed out. Include All Use this command to refresh the Rogue Monitor table with all detected rogue devices included. Access / One ® Network 124Managing the Network 5 The Apply Configuration Function This function is used to apply any configuration changes that have been made at either the network or subnet level. When BLUE, click on this tab to propagate and apply your changes to all nodes and wireless modules within your Access/One Network or a specific subnet. Figure 100. Apply Configuration Important Notes About Apply Configuration The following notes are important considerations when using the Apply Configuration function. For changes to be applied at the network or subnet level, you must reboot the network after clicking on the Apply Configuration tab, otherwise your changes will not be implemented. The Apply Configuration function is not available when configuring individual modules, because configuration changes at the module level are applied automatically when you click on the Update button. Apply Configuration Access / One ® Network Managing the Network125 5 Enabling Communication Between Remote Subnets Your Access/One Network can be configured to enable communication between network servers on remote subnets, allowing you to manage subnets from any network server on the network, regardless of its location. For example, remote subnets in New York and Los Angeles can be configured and managed from the same Manager/One interface. Example Los Angeles and New York each have their own network: ◗Los Angeles (LA): 172.20.0.0 ◗New York (NY): 192.152.1.0) You want both networks to be managed by the same Manager/One interface, and you can assume that a network server in Los Angeles (172.20.0.50) is the primary server for the Access/One Network. See also, “Starting a New Network” on page 32. It is recommended that you complete all of your configuration changes before using the Apply Configuration command to propagate your changes throughout the network. Once the Apply Configuration command has been initiated, you cannot make any further changes until the command cycle has been completed. It is strongly recommended that customers use an NTP (Network Time Protocol) server to synchronize Access/One Network to one clock. This will ensure that the system's internal Syslog time-stamping process is maintained correctly. See also, “Enabling Windows 2000 Servers for NTP Requests” on page 33. Without an NTP server (no universal clock), each network server will use its own internal clock and stamp times accordingly. Access / One ® Network 126Managing the Network 5 Procedure Configure a single remote network server for each subnet (NY: 192.162.1.22) on the LA server. Within a few minutes, Strix’s mesh topology feature will cause all of the remote subnets to automatically appear in each network server. Your Access/One Network is now manageable from any of the network servers in the network. Removing the NS to NS Feature To remove the NS to NS communication feature, delete all of the remote server entries on the LA server. When done, click on the Update button, then click on the Apply Configuration tab and reboot the network (to apply your changes). Managing Remote Subnets from Manager/One In most cases, configuration of your Access/One Network will apply to all subnets to maintain an homogeneous network. There are a few commands which can only be applied at the subnet level. The following commands apply to the network level only (regardless of what view is currently displayed): ◗Load Firmware on Network ◗The Apply Configuration Function The following commands apply at the network or subnet level (depending on what view is currently displayed): ◗Reboot Network (network only) ◗Reboot... (subnet / network) The following commands are applicable only at the subnet level: ◗Update Network Membership ◗Update Node Names Access / One ® Network Managing Subnets and Nodes127 6 Managing Subnets and Nodes This chapter covers management tasks at the subnet and node levels—you can only manage a subnet or node (you cannot configure subnets or nodes independent of the network). If you are managing your Access/One Network at the network level, or managing an individual module (for example, a wireless module or network server), go to the relevant chapter: ◗“Managing the Network” on page 65. ◗“Managing Modules” on page 133. The following graphic shows the subnet (subcloud) view in Manager/One’s main window. The subnet view displays all nodes within the selected subnet and provides interface features that are not available at the network level. All tasks in this chapter are performed at the subnet or node levels. Figure 101. Subnet (Subcloud) View IP Address Details PaneSubnet (Subcloud) Views Discovery Options Access / One ® Network 128Managing Subnets and Nodes 6 Interface Features in the Subnet View The interface features that are unique to the subnet view have already been discusse…

Text truncated - open the document above for the full version.

Access / One ® Network 173 B Syslog Messages Format The following format is used for all Access/One Network syslog messages: <recv-time> <code> <ip> <seqNumber:time-stamp, CloudName, subcloudName, StackId, Module, sysName, subSystem> <source> <sw-version> <syslog message> Subsystems Syslog messages are assigned to the following subsystems: ◗Wireless ◗Security ◗Management ◗Others ElementDefinition recv-timeTime when the syslog message is received. codeAs defined by RFC for syslog daemons. ipSender's IP address. seqNumberInternal sequence number (generated for all syslog messages). time-stampTime when the message is generated. ModuleModule type. sourceInternal source information, containing event-module & event-type. sw-versionSoftware build version number Syslog messageFormat is a string of ASCII text delimited by separators. Access / One ® Network 174 B Severity Levels The following severity levels are assigned to syslog messages (shown here in descending order from the most severe): ◗EMERGENCY ◗ALERT ◗CRITICAL ◗ERROR ◗WARNING ◗NOTICE ◗INFORM ◗DEBUG Assigning a severity level informs the system to automatically log all messages in that level, and all messages above that level (messages below the assigned level are not logged). Message Listing The following tables list syslog messages by subsystem. Security Subsystem SeveritySyslog Message ALERTTelnet local authentication failed. WARNINGSuper user login failed, invalid character. WARNINGSuper user login failed, invalid password. WARNINGTelnet login failed, invalid password. WARNINGCLI login failed, invalid password. WARNINGTelnet login failed, invalid password. Access / One ® Network 175 B Wireless Subsystem WARNINGCLI login failed, invalid password. WARNINGToo many invalid login attempts. NOTICETelnet user logged in, user:XXXXX. NOTICECLI user logged in, user:XXXXX. NOTICETelnet user logged out, user:XXXXX. NOTICECLI user logged out, user:XXXXX. NOTICESuper user logged in. SeveritySyslog Message EMERGENCYFailed to start the radio. EMERGENCYAP/STA features not enabled. EMERGENCYError while starting the module. Wireless services disabled. EMERGENCYRadio interference detected on selected channel. WARNINGBackhaul key mismatch. Putting it in RESTRICTED mode,mac:xx.xx.xx.xx.xx.xx. ALERTRadius authentication failed, mac:xx.xx.xx.xx.xx.xx. ERRORAssociation fails, can't find station in table, ssid:XXXXX,vlan:[id=x tag=x], mac:xx.xx.xx.xx.xx.x. ERRORReassociation fails, can't find station in table, ssid:XXXXX, vlan:[id=x tag=x], mac:xx.xx.xx.xx.xx.x. ERRORAssociation fails, not authenticated, ssid:XXXXX,vlan:[id=x tag=x], mac:xx.xx.xx.xx.xx.xx. SeveritySyslog Message Access / One ® Network 176 B ERRORReassociation fails, not authenticated, ssid:XXXXX,vlan:[id=x tag=x], mac:xx.xx.xx.xx.xx.xx. ERRORAssociation fails, already associated, ssid:XXXXX,vlan:[id=x tag=x], mac:xx.xx.xx.xx.xx.xx. ERRORReassociation fails, already associated, ssid:XXXXX,vlan:[id=x tag=x], mac:xx.xx.xx.xx.xx.xx. ERRORAssociation fails, can't authenticate during scan, ssid:ssid:XXXXX, vlan:[id=x tag=x], mac:xx.xx.xx.xx.xx.xx. ERRORReassociation fails, can't authenticate during scan, ssid:ssid:XXXXX, vlan:[id=x tag=x], mac:xx.xx.xx.xx.xx.xx. ERRORAssociation fails, reason:xxxx, wlanmode:xxxx, ssid:XXXXXX, vlan:[Id=x Tag=x],mac:xx:xx:xx:xx:xx:xx. ERRORReassociation fails, reason:xxxx, wlanmode:xxxx, ssid:XXXXXX, vlan:[Id=x Tag=x],mac:xx:xx:xx:xx:xx:xx. ERRORBad authentication transaction sequence, number:XX, type=XXXXX, mac:xx.xx.xx.xx.xx.xx. ERRORAuthentication[1] fails, can't find station in table, mac:xx.xx.xx.xx.xx.xx. ERRORAuthentication[1] fails, can't authenticate in scan mode, mac:xx.xx.xx.xx.xx.xx. ERRORAuthentication[3] fails, can't find station in table, mac:xx.xx.xx.xx.xx.xx. ERRORAuthentication[3] done, error in Tx, wlanmode:X, mac:xx.xx.xx.xx.xx.xx. ERRORDeauthentication requested, can't find station in table, mac:xx.xx.xx.xx.xx.xx. SeveritySyslog Message Access / One ® Network 177 B ERRORAssociation fails, module is not ready, mac:xx:xx:xx:xx:xx:xx. ERRORReassociation fails, module is not ready, mac:xx:xx:xx:xx:xx:xx. WARNINGAuthentication[3] fails, auth:shared, wlanmode:X, mac:xx.xx.xx.xx.xx.xx. WARNINGUnsupported 802.11 authentication request, auth:LEAP, wlanmode:X, mac:xx.xx.xx.xx.xx.xx. WARNINGUnsupported 802.11 authentication request, auth:x(hex), wlanmode:X, mac:xx.xx.xx.xx.xx.xx. WARNINGDeauthentication fails, incorrect source, mac:xx.xx.xx.xx.xx.xx. WARNINGDeauthentication fails, unknown source, mac:xx.xx.xx.xx.xx.xx. WARNINGAssociation fails, wrong ssid, ssid:XXXXX, vlan:[id=x tag=x], mac:xx.xx.xx.xx.xx.xx. WARNINGReassociation fails, wrong ssid, ssid:XXXXX, vlan:[id=x tag=x], mac:xx.xx.xx.xx.xx.xx. WARNINGNC-sel approves RESTRICTED Mode. WARNINGBackhaul [mac:xx:xx:xx:xx:xx:xx] at if=XXXX is put to RESTRICTED mode. WARNINGLoop is detected at if=XX. Mac:xx:xx:xx:xx:xx:xx. NOTICENC-sel approves OPEN Mode. NOTICEBackhaul is using default cloud name. Putting it in RESTRICTED mode,mac:xx.xx.xx.xx.xx.xx. NOTICEAP has put backhaul in RESTRICTED mode. SeveritySyslog Message Access / One ® Network 178 B NOTICEStack ID is available, stackId:XXXXXX. NOTICEThe unit/Radio x will operate as - Network Connect. NOTICEThe unit/Radio x will operate as - Client Connect. NOTICEThe unit/Radio x will switch to - Client Connect. NOTICEAdded station, mac:xx.xx.xx.xx.xx.xx. NOTICEDeauthentication completed, mac:xx.xx.xx.xx.xx.xx. NOTICEAssociation with AP done, response NOT sent, wlanmode:X, ssid:XXXX, mac:xx:xx:xx:xx:xx:xx. NOTICEReassociation with AP done, response NOT sent, wlanmode:X, ssid:XXXX, mac:xx:xx:xx:xx:xx:xx. NOTICELoop is cleared at if=XX. mac:xx:xx:xx:xx:xx:xx. NOTICEWLNC link [if=XX] state is up. SSID=XX, BSSID=xx:xx:xx:xx:xx:xx:xx, Channel=XX, Wireless Mode=XXXX. NOTICEWLNC link [if=XX] state is down. NOTICEAccess Point state is up. NOTICEAccess Point state is down NOTICEAssociation done, ssid:XXXX, vlan:[Id=x Tag=x], mac:xx:xx:xx:xx:xx:xx:xx. NOTICEReassociation…

Text truncated - open the document above for the full version.