Installation Instructions
Table Of Contents
- Fluidmesh 1200 VOLO
- Table of Contents
- 1. HAZARDOUS CONDITION WARNINGS
- 2. Reporting mistakes and recommending improvements
- 3. Getting Started
- 4. Installing the radio
- 5. Hardware installation
- 5.1. Fluidmesh hardware installation
- 5.1.1. Installing the Fluidmesh 1200 VOLO
- 5.1.2. Best practice for shielded CAT5/6 connectors
- 5.1.3. Fluidmesh 1200 VOLO Status and link LEDs
- 5.1.4. Supplying power to the Fluidmesh 1200 VOLO
- 5.1.5. Rebooting the firmware and resetting the unit to factory defaults
- 5.1.6. Suitability for outdoor installation
- 5.2. Connecting the Fluidmesh 1200 VOLO to networking and communications hardware
- 5.1. Fluidmesh hardware installation
- 6. Using the Fluidmesh Partner Portal
- 7. Device configuration using the configurator interface
- 7.1. Software and hardware prerequisites
- 7.2. Accessing the Fluidmesh 1200 VOLO for device configuration
- 7.3. Switching between offline and online modes
- 7.4. General settings
- 7.5. Network control
- 7.6. Advanced settings
- 7.6.1. Advanced radio settings
- 7.6.2.
- 7.6.3. Static routes
- 7.6.4. Pass lists and Block lists
- 7.6.5. Multicast
- 7.6.6. SNMP configuration
- 7.6.7. Wireless access point configuration
- 7.6.8. RADIUS configuration
- 7.6.9. NTP Configuration
- 7.6.10. L2TP configuration
- 7.6.11. VLAN settings
- 7.6.12. Miscellaneous settings
- 7.7. Management settings
- 7.7.1. View Mode settings
- 7.7.2. Changing the Administrator username and password
- 7.7.3. Overwriting and upgrading the unit firmware
- 7.7.4. Plug-In management
- 7.7.5. The device status view
- 7.7.6. Saving and restoring the unit settings
- 7.7.7. Resetting the unit to factory defaults
- 7.7.8. Logging out
- 7.7.9. Viewing the end-user license agreement
- 8. Software Plug-Ins
- 9. Troubleshooting
- 9.1. I cannot get the Log-in screen
- 9.2. I cannot log in to the RACER interface
- 9.3. I forgot the Administrator password
- 9.4. The wireless link is poor or non-existent in Bridge mode
- 9.5. I purchased a Fluidmesh device, but it is not shown in RACER
- 9.6. I cannot connect my Fluidmesh device to the RACER interface
- 9.7. I applied configuration settings to the device using RACER, but I have lost connection to the device in RACER.
- 9.8. How do I connect an existing pre-RACER device to RACER?
- 10. Device specifications
- 11. PoE injector specifications
- 12. Electrical power requirements
- 13. Heat radiation data
- 14. Federal Communications Commission (FCC) radio interference statement
- 15. Fluidmesh end-user license agreement
- 15.1. Preamble
- 15.2. Notice
- 15.3. Definitions
- 15.4. License grant
- 15.5. Uses and restrictions on use
- 15.6. Open-source software
- 15.7. Termination
- 15.8. Feedback
- 15.9. Consent to use of data
- 15.10. Warranty disclaimer
- 15.11. Limitation of liability
- 15.12. Exclusion of liability for emergency services
- 15.13. Export control
- 15.14. General
- 16. Contact us
IMPORTANT
Source and destination values are always unit
ID numbers. Do not enter a unit's IP address
as a source or destination value.
The unit ID number is printed on the
identification label of each unit. This number
always takes the following form: 5.a.b.c
• The smaller the routing priority value, the greater the
routing priority.
• Block list syntax is the same as shown above, except for
one additional rule: Block lists do not include routing
priority numbers.
• Unit ID numbers and routing priority values are always
separated with commas (,) and never with spaces.
• To make sure that the packet flow is allowed or blocked in
both directions, the unit ID numbers for each link in a Pass
list or Block list must be listed in forward order and in
reverse order.
• If a wireless link is not specified in a Pass list, it will be
assigned the lowest routing priority, but will not be
completely excluded from routing.
3. Example 1: If you want to create a simple Pass list that includes
the link between unit ID numbers 5.2.22.136 and 5.29.252.213
(Figure 43 (page 91)), and give the link routing priority 0 (the
highest possible priority):
• Cell A1 of the *.CSV file would contain the parameter
5.2.22.136,5.29.252.213,0
• Cell A2 of the *.CSV file would contain the parameter
5.29.252.213, 5.2.22.136,0
Figure 43. Sample Pass list (Example 1)
4. Example 2: If you want to create a Pass list that includes the
links between unit ID numbers 5.2.22.136 and 5.29.252.213 (with
routing priority 0), and between unit ID numbers 5.29.252.213
and 5.155.105.128 (with routing priority 1) (Figure 44 (page 92)):
• Cell A1 of the *.CSV file would contain the parameter
5.2.22.136,5.29.252.213,0
Fluidmesh 1200 VOLO
© 2020 Cisco and/or its affiliates. All rights reserved. Page 91 of 169