That makes sense.. Yes, the second NIC is there but it's not brought up by default. Don't know if that's an OS thing or my environment but I can try to bring up the interface first and try again.
Do note though that after quantum failed once (can't remember exactly when; I've been through much experimenting :p), the 2nd interface is brought up, but is also IP-less. I'll let you know my results. On Thursday, October 3, 2013, christopher_dearb...@dell.com wrote: > Hey Daniel,**** > > ** ** > > So your network json looks like it’s in good shape. What’s happening is > that the conduit map for dual mode, intf1 maps to the 2nd NIC (?1g2), > but, there is no 2nd NIC available.**** > > ** ** > > Can you double check to make sure you have a 2nd NIC in the system?**** > > ** ** > > It’s possible that you do have a 2nd NIC in the system, but that the OS > is not seeing it due to driver issues, etc. Try running dmesg and search > through the output for “eth” to see if you can find any related messages.* > *** > > ** ** > > ** ** > > Hope this helps!**** > > ** ** > > Chris**** > > Dell, Inc**** > > ** ** > > ** ** > > *From:* Daniel San Pedro [mailto:dsanpe...@mcna.net <javascript:_e({}, > 'cvml', 'dsanpe...@mcna.net');>] > *Sent:* Thursday, October 03, 2013 3:27 PM > *To:* Dearborn, Chris > *Cc:* Jakesch, Simon; crowbar; Jacob, Jacob > *Subject:* Re: [Crowbar] mesa-1.6 - cinder barclamp fails when applying > proposal**** > > ** ** > > Here ya go.. Please note that this file was modified before crowbar > install by following the below email: > > Hey Daniel, > > You definitely need to customize your bc-template-network.json file before > installing crowbar. I finally managed to get some time with our network > expert this morning to hash out the changes. > > It sounds like what you want to do is to put all network traffic on eth0 > and leave eth1 open for GUI access. To do this install the OS on the admin > node, then before running install, make a backup copy of your > bc-template-network.json in a different directory, then proceed with > customizing the original. > > The following summarizes the changes I believe you will need to make: > 1. Search the entire file for “192.168.124” and change every > instance to the subnet that you want. > a. Note that if you need a different netmask, you will also need to > update all instances of that. > 2. Change the mode at the top of the file from “single” to “dual” > a. This makes it use the “dual/.*/.*” section of the conduit map > i. Take > a look at the dual section of the conduit map > ii. The > intf0 conduit maps to ?1g1 > 1. “1g” means 1 gigabit and the last “1” means “use the first > interface” which is usually eth0 > 2. The “?” means use the specified speed if available, but if not > available, then use a faster speed if available (10g), and if a faster > speed is not available then use a slower speed (preferring 100m over 10m). > This will force it to use eth0 for the intf0 conduit regardless of the > interface speed. > iii. The > intf1 conduit maps to ?1g2, which will force it to use the second interface > (eth1) regardless of the interface speed. > 3. In the networks section, change the conduit for every network to > be “intf0” except for the public network which should be “intf1”, and the > bmc_vlan network, which should be “intf2” > a. This will move all network traffic to eth0 except for the GUI > traffic, which will be on the public network (eth1). > 4. In the public network section, change “use_vlan” to false so it > will use eth1 for the public network instead of eth1.300. > > After all these changes, run install to install the Crowbar software on > the admin node. > -- Daniel San Pedro Systems Administrator MCNA Dental Plans dsanpe...@mcna.net Mobile: (954) 673-5801 ------------------------ CONFIDENTIALITY NOTICE: This electronic mail may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents by persons other than the intended recipient(s) is strictly prohibited. If you have received this communication in error, please notify the sender immediately by reply e-mail so that we may correct our internal records. Please then delete the original message. Thank you.
_______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
