← Back to team overview

fuel-dev team mailing list archive

Re: Management IP of Compute is not reachable from Controller node and vice versa

 

Greetings Gandhi,

For your configuration, described in your mail message the recommended
settings are the following:

1.
You should set all the switch ports, connected to eth0 to the trunk mode
and allow VLANs 101, 102, 103 and all the additional VLAN numbers,
configured in Private network settings.
By default it is VLAN number range 1000 - 1030, so 31 VLAN total.

Additionally, you must allow promiscuous mode for this ports, since Neutron
requires it.

2.
It is recommended to leave all the ports, connected to Admin network (eth1)
in access mode.


Unfortunately, we (at least everybody around me) are not familiar with
Fabric mode and, in this case, may advice incorrectly.
Since your VDX switch is set to Fabric mode - please ask somebody, who is
familiar with Fabric configuration, to review your network switch settings.

Kind regards,
Miroslav


On Fri, Jun 27, 2014 at 7:35 AM, Gandhirajan Mariappan (CW) <
gmariapp@xxxxxxxxxxx> wrote:

> Few more details -
>
> *Controller / Cinder node:*
>
> Eth0 -> Private (VLAN 103), Public, Storage (VLAN 102), Management (VLAN
> 101)
>
> Eth1 -> Admin (PXE)
>
>
>
> *Compute Node :*
>
> Eth0 -> Private (VLAN 103), Public, Storage (VLAN 102), Management (VLAN
> 101)
>
> Eth1 -> Admin (PXE)
>
>
>
> *Note:* our default VLAN (management) is 1.
>
>
>
> Also, Kindly let us know which ports should be configured with access mode
> (with VLAN IDs) and which ports should be configured with trunk mode (with
> VLAN ids)
>
>
>
> Thanks and Regards,
>
> Gandhi Rajan
>
>
>
> *From:* Gandhirajan Mariappan (CW)
> *Sent:* Thursday, June 26, 2014 7:05 PM
> *To:* fuel-dev@xxxxxxxxxxxxxxxxxxx
> *Cc:* 'Evgeniya Shumakher'; Andrey Danin; 'izinovik@xxxxxxxxxxxx' (
> izinovik@xxxxxxxxxxxx); Karthi Palaniappan (CW); Nataraj Mylsamy (CW);
> Harsha Ramamurthy; Prakash Kaligotla; Raghunath Mallina (CW)
> *Subject:* Management IP of Compute is not reachable from Controller node
> and vice versa
>
>
>
> Hi Fuel-Dev,
>
>
>
> While deploying the slave nodes, we had below configuration in VCS device.
> Only if we have below configuration, deployment is getting successful and I
> can able to launch Horizon.
>
>
>
> *VCS Configuration – Access mode: - Used this configuration while
> deploying from Fuel UI*
>
> *interface TenGigabitEthernet 133/0/7*
>
> *fabric isl enable*
>
> *fabric trunk enable*
>
> *switchport*
>
> *switchport mode access*
>
> *switchport access vlan 1*
>
> *spanning-tree shutdown*
>
> *no shutdown*
>
> *!*
>
> *interface TenGigabitEthernet 133/0/13*
>
> *fabric isl enable*
>
> *fabric trunk enable*
>
> *switchport*
>
> *switchport mode access*
>
> *switchport access vlan 1*
>
> *spanning-tree shutdown*
>
> *no shutdown*
>
> *!*
>
> *interface TenGigabitEthernet 133/0/21*
>
> *fabric isl enable*
>
> *fabric trunk enable*
>
> *switchport*
>
> *switchport mode access*
>
> *switchport access vlan 1*
>
> *spanning-tree shutdown*
>
> *no shutdown*
>
> *!*
>
>
>
> Now, we are not able to ping Compute node management ip (192.168.0.2) from
> Controller node (192.168.0.3) and vice versa.
>
> Because of this “nova hypervisor-list” is empty. I tried configuring VCS
> device with above configuration (access mode) as well as below
> configuration (trunk mode).
>
>
>
> When we are configuring trunk mode setting in VCS, both controller and
> compute nodes are going away from master node (we are getting notification
> in Fuel UI). Not sure what is the expected configuration.
>
>
>
> Kindly let us know what should we do, so that “nova-hypervisor-list” will
> list compute node. I have attached diagnostic snapshot at
> https://www.dropbox.com/s/nf09krcx5zum371/fuel-snapshot-2014-06-26_13-19-07.tgz
>
>
>
> *VCS Configuration – Trunk mode:*
>
> *interface TenGigabitEthernet 133/0/7*
>
> *fabric isl enable*
>
> *fabric trunk enable*
>
> *switchport*
>
> *switchport mode trunk*
>
> *switchport trunk allowed vlan add 101-103*
>
> *switchport trunk tag native-vlan*
>
> *spanning-tree shutdown*
>
> *no shutdown*
>
> *interface TenGigabitEthernet 133/0/13*
>
> *fabric isl enable*
>
> *fabric trunk enable*
>
> *switchport*
>
> *switchport mode trunk*
>
> *switchport trunk allowed vlan add 101-103*
>
> *switchport trunk tag native-vlan*
>
> *spanning-tree shutdown*
>
> *no shutdown*
>
> *interface TenGigabitEthernet 133/0/21*
>
> *fabric isl enable*
>
> *fabric trunk enable*
>
> *switchport*
>
> *switchport mode trunk*
>
> *switchport trunk allowed vlan add 101-103*
>
> *switchport trunk tag native-vlan*
>
> *spanning-tree shutdown*
>
> *no shutdown*
>
>
>
> Thanks and Regards,
>
> Gandhi Rajan
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 

*Kind Regards*

*Miroslav Anashkin**L2 support engineer**,*
*Mirantis Inc.*
*+7(495)640-4944 (office receptionist)*
*+1(650)587-5200 (office receptionist, call from US)*
*35b, Bld. 3, Vorontsovskaya St.*
*Moscow**, Russia, 109147.*

www.mirantis.com

manashkin@xxxxxxxxxxxx

References