Fluidmesh Network Addressing; Bridge Ip Addressing; Unit Identification And Addressing; Mesh-Capable Gateway Identification - Cisco FM1000 Gateway Installation And Configuration Manual

Ultra-reliable wireless backhaul
Hide thumbs Also See for FM1000 Gateway:
Table of Contents

Advertisement

IMPORTANT
The Cisco FM1000 Gateway features exclusive support for
Prodigy 2.0. The unit does not support Prodigy 1.0.
Also note that Prodigy 1.0 and Prodigy 2.0 are not compatible
with each other. Do not implement the two protocol versions
within the same network.
If you are expanding an existing network using a Cisco
FM1000 Gateway Gateway, make sure all components that are
part of the network are compatible with the Gateway by:

3.3. Fluidmesh network addressing

3.3.1. Bridge IP addressing

As shipped from the factory, the wired ethernet ports of all Fluidmesh
hardware components are assigned the same default IP address of
192.168.0.10/24.
No default IP address is associated with the wireless interface.

3.3.2. Unit identification and addressing

Mesh-capable gateway identification

In contrast to Fluidmesh products that can be set in Mesh Point and Mesh
End modes as needed, the Cisco FM1000 Gateway can only be set as a
Mesh End point.
Regardless of its configuration and operating mode, every Fluidmesh
device is shipped from the factory with a unique mesh identification (ID)
number (also called the Mesh ID). This number always takes the following
form:
5.a.b.c
The triplet a.b.c uniquely identifies the individual physical hardware unit.
The Mesh ID number is used to identify the physical hardware units within
the configurator interface that is used for configuration of the unit. Mesh ID
numbers cannot be changed.
Simplified network diagrams demonstrating the relationship between a
wired LAN and a linked mesh radio network containing a mesh end unit
and mesh point units are shown below.
typical Layer 2 network, while
network.
© 2021 Cisco and/or its affiliates. All rights reserved.
1. Upgrading all Fluidmesh radio transceivers within the
network to firmware version 6.5 or higher, and:
2. Configuring all Fluidmesh radio transceivers within the
network to operate using Prodigy 2.0.
Figure 2 (page 17)
Getting Started
Figure 1 (page 16)
shows a
shows a typical Layer 3
Page 15 of 138

Advertisement

Table of Contents
loading

Table of Contents