create

Use the create command to create a topology object. The create command is accessible from the topology context of the CLI.

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 (Virtual LAN) 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.
fabric	The Fabric Attach topology type allows an AP to attach to a Shortest Path Bridging (Fabric Connect) Network. The client component on the AP communicates directly with the server on an edge switch (or it can communicate with the server through a proxy) to allow the AP to request VLAN to I-SID (backbone Service Identifier [IEEE 802.1 ah] mappings). The Fabric Attach topology type is similar to B@AP with the added I-SID parameter. Fabric Attach can be configured on a controller anywhere a B@AP topology can be configured.
`isid`	I-SID (Service Identifier [IEEE 802.1 ah])

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 (Dynamic Host Configuration Protocol)) 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.
Fabric Attach — A topology type that allows an AP to attach to a Shortest Path Bridging (Fabric Connect) Network. The Fabric Attach topology type is similar to B@AP with the added I-SID parameter. Fabric Attach can be configured on a controller anywhere a B@AP topology can be configured.

You can choose from the following topology types (modes) when creating a topology:

Only B@AC, B@AP, Fabric, and Routed topologies can be assigned to policies.

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

The following example creates a fabric attach topology named fabric1:

EWC.extremenetworks.com:topology# create fabric1 fabric 1234 tag isid 12

Published May 2018prev | next