← Back to team overview

openstack team mailing list archive

Re: [essex vlan]cannot ping vm on other compute node

 

Perhaps:

interface gigbbit 0/22
switchport mode trunk
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-4094
interface gigbbit 0/23
switchport mode trunk
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-4094



On Wed, Feb 27, 2013 at 12:02 AM, Ajiva Fan <aji.zqfan@xxxxxxxxx> wrote:
>
> since i notice that in switcher:
> sw-31>show interface fastEthernet 0/22 trunk
>
> Port        Mode         Encapsulation  Status        Native vlan
> Fa0/22      on           802.1q         trunking      1
>
> Port      Vlans allowed on trunk
> Fa0/22      1-4094
>
> Port        Vlans allowed and active in management domain
> Fa0/22      1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001
>
> Port        Vlans in spanning tree forwarding state and not pruned
> Fa0/22      1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001
>
> the vlan 5 is active in management domain but 105 is not, so i try the
> same workflow as before but change vlan id 5 to 110, ping gets no
> reply as vlan105
>
> so may be i should add vlan105 to active list ? sorry i'm a green hand
> to switcher and got confused.
> 1) what the different between the allowd list and active list
> 2) if i should add active list manually, so does the cloud admin, if
> he create a vlan for a tenant, he should add to switcher active list
> too? is there any way automatically recoginize the vlan tag and allow
> it pass?
> maybe add a range to active list, for example, 100-4000? it's ugly......


Follow ups

References