fuel-dev team mailing list archive

[Miroslav Anashkin <manashkin@xxxxxxxxxxxx>]

Greetings Gandhi,

No, it is not mandatory to use eth0 for PXE.
During the first Fuel master node boot you may assign any of available ethX
interfaces to work as PXE Boot interface.

About the error:
Your error message boot stopped at “pxe-mof exiting broadcom pxe rom”.
clearly indicates you encountered missing firmware issue.
So, please downgrade bootstrap image on master node as following:
http://docs.mirantis.com/fuel/fuel-5.0/release-notes.html#known-issues-in-mirantis-openstack-5-0

1. Download bootstrap image by the following link:
http://9f2b43d3ab92f886c3f0-e8d43ffad23ec549234584e5c62a6e24.r60.cf1.rackcdn.com/bootstrap-5.0-kernel-2.6.zip


2. Follow the bootstrap image update guide:
Bootstrap kernel issues on certain hardware

The bootstrap image shipped with Mirantis OpenStack is based on a 3.10
kernel with firmware built from the in-kernel tree. This can lead to issues
with some hardware configurations, (including some Dell R410/R610s
servers). See LP1323354 <https://bugs.launchpad.net/fuel/+bug/1323354> for
details. As a workaround, use bootstrap image with 2.6 kernel
<http://9f2b43d3ab92f886c3f0-e8d43ffad23ec549234584e5c62a6e24.r60.cf1.rackcdn.com/bootstrap-5.0-kernel-2.6.zip>.
Copy the downloaded zip archive to the Fuel master node

scp bootstrap-5.0-kernel-2.6.zip root@10.20.0.2:/root/

 Log in to Fuel master node and run the following commands to install new
bootstrap:

cd /root/
yum -y install unzip
unzip bootstrap-5.0-kernel-2.6.zip
cp -b linux /var/www/nailgun/bootstrap/
chmod +x /var/www/nailgun/bootstrap/linux
chmod -w /var/www/nailgun/bootstrap/linux
cp -b initramfs.img /var/www/nailgun/bootstrap/
cobbler sync


To apply changes to already bootstrapped nodes, simply reboot the affected
nodes to boot with the 2.6 kernel.

Note: Existing bootstrap files will be renamed to linux~ and
initramfs.img~, but you may create your own backups as well.

Kind regards,
Miroslav


On Mon, Jun 9, 2014 at 12:18 PM, Gandhirajan Mariappan (CW) <
gmariapp@xxxxxxxxxxx> wrote:

> Hi Miroslav,
>
>
>
> Also, We are using eth1 as Admin (PXE) network instead of eth0. *Is it
> mandatory to use eth0 as Admin (PXE) network?*
>
>
>
> *Note:* In our setup, eth0 of the servers are connected to management
> network and eth1 is used to connect with VDX devices (Admin Network - PXE)
>
>
>
> Thanks and Regards,
>
> Gandhi Rajan
>
>
>
> *From:* Gandhirajan Mariappan (CW)
> *Sent:* Monday, June 09, 2014 12:47 PM
> *To:* 'Miroslav Anashkin'
>
> *Cc:* fuel-dev@xxxxxxxxxxxxxxxxxxx; DL-GRP-ENG-SQA-Open Stack; Prakash
> Kaligotla; eshumakher@xxxxxxxxxxxx; adanin@xxxxxxxxxxxx;
> izinovik@xxxxxxxxxxxx
> *Subject:* RE: Verify Network Failed
>
>
>
> Hi Miroslav,
>
>
>
> I have shared the diagnostic snapshot at
> https://www.dropbox.com/s/py32h7s9vpamxy5/fuel-snapshot-2014-06-09_06-45-29.tgz
>
> While booting the slave1, boot stopped at “pxe-mof exiting broadcom pxe
> rom”. We are troubleshooting the same by checking the PXE configuration.
>
>
>
> Thanks and Regards,
>
> Gandhi Rajan
>
>
>
> *From:* Miroslav Anashkin [mailto:manashkin@xxxxxxxxxxxx
> <manashkin@xxxxxxxxxxxx>]
> *Sent:* Friday, June 06, 2014 9:21 PM
> *To:* Gandhirajan Mariappan (CW)
> *Cc:* fuel-dev@xxxxxxxxxxxxxxxxxxx; DL-GRP-ENG-SQA-Open Stack; Prakash
> Kaligotla; eshumakher@xxxxxxxxxxxx; adanin@xxxxxxxxxxxx;
> izinovik@xxxxxxxxxxxx
> *Subject:* Re: Verify Network Failed
>
>
>
> Greetings Gandhi,
>
> If I remember correct, your Admin (PXE) network is set up as separate
> network, based on external network switch, connected to eth0 interface on
> every node.
> All the communication between the master node and OpenStack nodes goes via
> Admin network.
>
> So, up and running eth0 interface is absolutely required on all nodes in
> your environment to get Admin network function properly.
>
> Please check, why eth0 is disabled on the OpenStack nodes and enable it.
>
>
> In addition, you may also generate diagnostic snapshot and share it on
> some site like DropBox, so we could download it and investigate the error.
> Diagnostic snapshot is set of the current logs and settings of your
> Mirantis OpenStack installation
> You can achieve this by following these steps:
>
> 1 - Go to master node web interface
>
> 2 - Click Support at the top
> 3 - Click "Generate diagnostic snapshot"
> 4 - Download generated snapshot (may take more 10 minutes depending on the
> size of logs)
>
> 5.- Upload the snapshot file somewhere like dropbox.com and send us a
> link to the uploaded snapshot.
>
> Kind regards,
>
> Miroslav
>
>
>
>
>
> On Fri, Jun 6, 2014 at 10:43 AM, Gandhirajan Mariappan (CW) <
> gmariapp@xxxxxxxxxxx> wrote:
>
> Hi,
>
>
>
> “Verify Network” is getting failed. Kindly let us know how to proceed on
> this.
>
> We have created 3 VLANs (VLAN101, VLAN102, VLAN103) in the Brocade VDX
> device and assigned the ports connected to Server as tagged VLAN.
>
>
>
> We are using default IP addresses in Networks tab > VLAN Manager. Do we
> need to set any other configuration in the Brocade VDX device apart from
> VLAN settings (please refer below snippet)?
>
>
>
> *Brocade VDX Configuration:*
>
> sw0# show vlan brief
>
> Total Number of VLANs configured : 11
>
> VLAN       Name            State                      Ports
>
>
> (F)-FCoE                                             (u)-Untagged,
> (t)-Tagged
>
> (R)-RSPAN                                            (c)-Converged
>
> ======== =============== ==========================
> ================================================
>
> 101      VLAN0101        ACTIVE                     Te 139/0/13(c)   Te
> 133/0/24(c)
>
>                                                     *Te 133/0/21(t)*   Te
> 133/0/18(c)
>
>                                                     Te 133/0/17(c)   Te
> 133/0/16(c)
>
>                                                     Te 133/0/14(c)   *Te
> 133/0/13(t)*
>
>                                                     Te 133/0/8(c)   *Te
> 133/0/7(t)*
>
> 102      VLAN0102        ACTIVE                     Te 139/0/13(c)   Te
> 133/0/24(c)
>
>                                                     *Te 133/0/21(t)*   Te
> 133/0/18(c)
>
>                                                     Te 133/0/17(c)   Te
> 133/0/16(c)
>
>                                                     Te 133/0/14(c)   *Te
> 133/0/13(t)*
>
>                                                     Te 133/0/8(c)   *Te
> 133/0/7(t)*
>
> 103      VLAN0103        ACTIVE                     Te 139/0/13(c)   Te
> 133/0/24(c)
>
>                                                     *Te 133/0/21(t)*   Te
> 133/0/18(c)
>
>                                                     Te 133/0/17(c)   Te
> 133/0/16(c)
>
>                                                     Te 133/0/14(c)   *Te
> 133/0/13(t)*
>
>                                                     Te 133/0/8(c)   *Te
> 133/0/7(t)*
>
>
>
>
>
> *Current Setup:*
>
> Our setup consists of 3 nodes (1-master, 1-Controller, 1-Compute) and all
> three are connected to Brocade VDX device
>
> [image: cid:image007.png@01CF75CF.84E98410]
>
>
>
> *Verify Network:*
>
> Flow got completed in 1st node and 2nd node below, whereas Flow is
> in-progress for some time (around 30 minutes) for 3rd node (we do not
> have 3rd slave node in our setup)
>
>
>
> After some time (around 30 minutes), connections are getting failed.
>
>
>
>
>
>
>
>
>
> Thanks and Regards,
>
> Gandhi Rajan
>
>
>
>
> --
>
>
>
> *Kind RegardsMiroslav 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
>



-- 

*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