pvlan configuration

[Alexander Proskurnin]

I wonder why when configuring pvlan feature we need to map secondary vlan to primary vlan 2 times.

sw(config)# vlan 201
sw(config-vlan)# private-vlan isolated
sw(config)# vlan 202
sw(config-vlan)# private-vlan community
sw(config-vlan)# vlan 100
sw(config-vlan)# private-vlan primary
sw(config-vlan)# private-vlan association 201,202
sw(config-vllan)# interface fastethernet 0/24
sw(config-if)# switchport mode private-vlan promiscuous
sw(config-if)# switchport private-vlan mapping 100 201,202
sw(config-if)# interface range fastethernet 0/1 - 2
sw(config-if)# switchport mode private-vlan host
sw2(config-if)# switchport private-vlan host-association 100 202        <---- i already did the association of 202 to 100, why do this again?
sw(config-if)# interface range fastethernet 0/3 - 4
sw(config-if)# switchport mode private-vlan host
sw2(config-if)# switchport private-vlan host-association 100 201        <---- same here

Is it just a command syntax or there is some in-depth logic about this? Maybe someone could post a complex example of pvlan configuration where those commands make sense?

Thanks!

[Reza Sharifi]

From you output, the first association is for interface 0/1-2 and the second one is for interface 0/3-4

So, they are for different ports.

HTH

[Alexander Proskurnin]

Sorry for my explanation. I mean why do we have command

switchport private-vlan host-association 100 202

and not

switchport private-vlan host-association 202