create
Use the create command to create a topology object. The create command is accessible from the topology context of the CLI.
create
topology name (b@ac
vlanid
port
port name
tag | untag) | (b@ap
vlanid
tag | untag) | (routed
A.B.C.D/0-32) | (physical
vlanid) port
port name
tag | untag> A.B.C.D./0-32)
Parameters
topology name |
Specifies the name of the topology. |
b@ac |
Specifies a Bridge Traffic locally at Controller topology. |
b@ap |
Specifies a Bridge Traffic locally at Access Point topology. |
routed |
Specifies a routed topology. |
physical |
Specifies a physical topology. |
vlanid |
VLAN ID assigned to this topology. Value can be in range 1-4094. |
tag |
untag |
Specifies tagged or untagged VLAN. |
port
port-name |
Specifies the name of the layer 2 port. |
A.B.C.D/0-32 |
Layer 3 IP address and mask assigned to this physical topology. |
Usage
The following are available
topology types:
- Admin — The
native, pre-defined topology of the Wireless Appliance management port. This topology
is named Admin. You cannot create topologies with the name Admin.
- B@AC — Bridge
Traffic Locally at controller. Requires Layer 2 configuration. May optionally have
Layer 3 configuration. Layer 3 configuration would be necessary if services (such as
DHCP) are required over the configured network segment, or if controller management
operations are intended to be done through the configured interface.
- B@AP — Bridge
Traffic Locally at AP. Requires Layer 2 configuration. Does not require Layer 3
configuration. Bridge Traffic at the AP topologies do not require the definition of a
corresponding IP address since all traffic for users in that topology will be
directly bridged by the Wireless AP at the local network point of attachment (VLAN at
AP port).
Note
IPv6 is supported for Layer 2 bridging for both B@AC and
B@AP topologies.
- Routed — Routed topology. Routed topologies do not need any Layer 2 configuration, but do require Layer 3 configuration.
- Physical —Physical Ethernet port topology. Physical topologies are not pre-defined; they must be created.
You can choose from four of the topology types (modes) when creating a topology:
- B@AC
- B@AP
- Routed
- Physical
Only B@AC, B@AP, and Routed topologies can be assigned to policies.
Example
The
following example creates a B@AC topology named bac1, with a VLAN ID of 2, using the
esa1 controller port:
EWC.extremenetworks.com:topology# create bac1 b@ac 2 port esa1