Difference between tag and untag in topology creation

[Saiprasad_Rao_R]

What is the Difference between tag and untag in topology creation..... Say suppose 6 topologies ( Bridge @ AP) with different vlans are created on same interface and that interface also has mgmt IP on it and will be the only interface used connected to lan(switch)...... will all 6 topolies be created as tagged or untagged.......

[Rahman_Duran1]

Also note that If you use B@AP topology you don't need to tag the vlans on your core switch which is connected to controller interface. But you need to tag that vlans on switch ports which the APs connected.

[Sai_Prasad_Rao_]

OK ....... so what you'll be doing is create one physical topology (untag) with ip, 6 B@ AP toplogies for end users (tagged) . make sure the switch port connecting controller will have only one vlan(part of physical toplogy IP/subnet) as untag........ on switchport to which ap is connected: configure 2 vlans (ap vlan as untagged & user can as tagged (as defined B@AP topology).........

[Gareth_Mitchell]

please correct me, say if I create a topology with l3 ip address with mode "physical" with vlan 10 as untagged, port being say esa0, that L3 ip address will be used for management of controller from network...right?

Assuming the management radio button is selected for that topology, yes.

Is defining the port as esa0 for the toplogies mandatory for B@AP or vlan id is enough?

In the topology definition for B@AP there is no interface to configure.

can i use the same port esa0 for all the toplogies and will it be tagged?

If you're using B@AP then this is not required.

-> If it is tagged, then configuring the port on switch to which controller is connected as "untag" only for vlan 10 do the job as B@AP.

If your management vlan is 10 then this would be ok, assuming your AP's are registering to this interface also then you would need Management and AP Registration radio buttons checked.

[Saiprasad_Rao_R]

please correct me, say if I create a topology with l3 ip address with mode "physical" with vlan 10 as untagged, port being say esa0, that L3 ip address will be used for management of controller from network...right?

now say i create 10 topologies (B@AP on the same port esa0) which are mapped to multiple WLAN Services mapping to different vlans, now here's the dilemma

-> Is defining the port as esa0 for the toplogies mandatory for B@AP or vlan id is enough?

-> can i use the same port esa0 for all the toplogies and will it be tagged?

-> If it is tagged, then configuring the port on switch to which controller is connected as "untag" only for vlan 10 do the job as B@AP.