thank you, Kevin S, and also thanks George
i did this command in the beginning of the time when i meet this
problem, and it failed because """sw-31(config)#vlan 105
VTP VLAN configuration not allowed when device is in CLIENT mode."""
meanwhile i'm guided to a wrong way by our network administrator
To: Salvatore Orlando
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [essex vlan]cannot ping vm on other compute node
thanks you for reply
special thanks to Aaron Rosen
the situation is that:
1) openstack is in vlan mode
2) switcher is in trunk mode, all vlan id is allowed
3) vlan in
Ajiva,
In your 'show interface fa 0/2[2,3] trunk' output I don't see vlan 105 and
this is most likely because it's not created. This might be why vlan 5
works and 105 doesn't.
Try:
> en
# conf t
# vlan 105
# exit
Thanks,
Kevin S
On 2/27/13 4:22 AM, "Ajiva Fan" wrote:
>thanks you for repl
thanks you for reply
special thanks to Aaron Rosen
the situation is that:
1) openstack is in vlan mode
2) switcher is in trunk mode, all vlan id is allowed
3) vlan in switcher's allowed list, active list and (not pruned) list
can communicate with each other. vlan only in allowed list but not in
th
I'm not sure I followed the thread correctly from the beginning, but I
read that you have configured you NIC for private VM networking, in
VLAN mode, on VLAN 105.
Is that correct?
In general trunking all your switch ports used for VM networking will
save you the hassle of adding the VLANs you are
thank you very much.
actullaly, i have already try these command yesterday, it does not work.
currently, i find that vlan id in active list and not pruned list can
be passed by switcher, vlan id not in the two list cannot will be
droped even they are in allowed list.
but the network administr
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 wro
since i notice that in switcher:
sw-31>show interface fastEthernet 0/22 trunk
PortMode Encapsulation StatusNative vlan
Fa0/22 on 802.1q trunking 1
Port Vlans allowed on trunk
Fa0/22 1-4094
PortVlans allowed and active in mana
thank you for your help
i guess you point a way to figure out whether the switcher is working
correctly or not
after i add a vlan 5 to eth1 and an ip addr to it, the switcher works
fine, ping get reply
so the switch trunk port seems no problem
but br105 got a 10.0.12.{4,6}/24 as well, and also v
inline
On Tue, Feb 26, 2013 at 10:51 PM, Ajiva Fan wrote:
> greeting, stackers
>
> i deploy essex with flatdhcp, it works for a long time, but currently
> i want to use vlan network, so i deploy a new environment everything
> is same as the previous one, just use vlan network.
>
> here is the pr
On Tue, Feb 26, 2013 at 11:02 PM, Aaron Rosen wrote:
> inline
>
> On Tue, Feb 26, 2013 at 10:51 PM, Ajiva Fan wrote:
>
>> greeting, stackers
>>
>> i deploy essex with flatdhcp, it works for a long time, but currently
>> i want to use vlan network, so i deploy a new environment everything
>> is s
greeting, stackers
i deploy essex with flatdhcp, it works for a long time, but currently
i want to use vlan network, so i deploy a new environment everything
is same as the previous one, just use vlan network.
here is the probelm:
i cannot ping vm on other compute node
control node (all-in-one)
12 matches
Mail list logo
