Jumpstart issue with multiple NIC's

From: Gavin.Whittaker@jpmchase.com
Date: Tue May 02 2006 - 08:07:52 EDT


All

I have the problem and wondered if anyone else has run into this

Its a proof of concept design we are attempting to use in our organisation,
clients are UAT boxes and in the event of problems with a live box the UAT
box needs to be configured as a live prod host, rather than fiddling with
dual boots and worrying about keeping them in sync, its been decided that
we will treat Fujitsu PP850's like a linux blade and any problems we have
we just re-build it as a new host or as itself if it develops a problem.

jump server is PP850 with two quad cards, it has one connection to public
network, in port 3 of one the quad cards is a cross over cable which i will
call uat, in port 4 is another cross over cable which i will call prod.

the two cross over cables are connected to another PP850 (same spec as jump
server) and is connected into same ports as the jump server

on the client devalias has been set up as shown (in bold)

{c} ok devalias
tape /pci@87,2000/scsi@1,1/tape@5,0
cdrom /pci@87,2000/scsi@1,1/disk@4,0:f
disk11 /pci@8f,2000/scsi@1/disk@1,0
disk10 /pci@8f,2000/scsi@1/disk@0,0
disk1 /pci@87,2000/scsi@1/disk@1,0
disk0 /pci@87,2000/scsi@1/disk@0,0
disk /pci@87,2000/scsi@1/disk@0,0
scsi /pci@87,2000/scsi@1
obp-net /pci@87,4000/network@1,1
net /pci@87,4000/network@1,1
ttyb /pci@87,4000/ebus@1/FJSV,se@14,400000:b
ttya /pci@87,4000/ebus@1/FJSV,se@14,400000:a
serialno 6B03316342
backup /pci87,4000/network@1,1
prod /pci@84,2000/pci@1/FJSV,p4ta@3,1
uat /pci@84,2000/pci@1/FJSV,p4ta@3
scf /pci@87,4000/ebus@1/FJSV,scfc@14,200000

{c} ok cd /pci@84,2000/pci@1/FJSV,p4ta@3,1
{c} ok .properties
component-name C0M00-PCI#00
fru PCI slot(PCI#00 at Cabinet#0,SCFA#0)
status okay
assigned-addresses 83811910 00000000 00160000 00000000 00010000
                         82811930 00000000 00170000 00000000 00010000
local-mac-address 00 00 77 9e eb 6b
fjgiga-rev 000000c0
product-name FJSV,p4ta
device_type network
address-bits 00000030
max-frame-size 00004000
reg 00811900 00000000 00000000 00000000 00000000
                         03811910 00000000 00000000 00000000 00010000
model Broadcom,BCM5704C
compatible fjgi
name FJSV,p4ta
media-type 1000BASE-4T
fcode-rom-offset 00000000
66mhz-capable
fast-back-to-back
devsel-speed 00000001
class-code 00020000

{c} ok cd /pci@84,2000/pci@1/FJSV,p4ta@3
{c} ok .properties
component-name C0M00-PCI#00
fru PCI slot(PCI#00 at Cabinet#0,SCFA#0)
status okay
assigned-addresses 83811810 00000000 00140000 00000000 00010000
                         82811830 00000000 00150000 00000000 00010000
local-mac-address 00 00 77 9e eb 6a
fjgiga-rev 000000c0
product-name FJSV,p4ta
device_type network
address-bits 00000030
max-frame-size 00004000
reg 00811800 00000000 00000000 00000000 00000000
                         03811810 00000000 00000000 00000000 00010000
model Broadcom,BCM5704C
compatible fjgi
name FJSV,p4ta
media-type 1000BASE-4T
fcode-rom-offset 00000000
66mhz-capable
fast-back-to-back
devsel-speed 00000001
class-code 00020000

on client:

root@ubrsts-cn2p# eeprom | grep mac-address
local-mac-address?=true
root@ubrsts-cn2p#

on jumpstart server the following files are in place

root@ubrsts-cn1p# cat /etc/hosts
#
# Internet host table
#
127.0.0.1 localhost
169.95.205.127 ubrsts-cn1p-backup
169.95.228.145 ubrsts-cn1p-ipmp1
169.95.228.146 ubrsts-cn1p-ipmp2
169.95.228.147 ubrsts-cn1p loghost
# The entry below is for the fake IO network until the real IO network is
up
192.168.1.1 ubrsts-cn1p-prod
192.169.1.1 ubrsts-cn1p-uat
#
# Temp entry added by Gav to test jumsptart
#
192.168.1.2 ubrsts-cn2p-prod
192.169.1.2 ubrsts-cn2u-uat

root@ubrsts-cn1p# cat /etc/ethers
0:0:77:9e:eb:6b ubrsts-cn2p-prod
0:0:77:9e:eb:6a ubrsts-cn2u-uat

root@ubrsts-cn1p# cat /etc/bootparams
ubrsts-cn2p-prod
root=ubrsts-cn1p-prod:/export/jumpstart/sb10/sparc_10-0106/Solaris_10/Tools/Boot
 install=ubrsts-cn1p-prod:/export/jumpstart/sb10/sparc_10-0106 boottype=:in
sysid_config=ubrsts-cn1p-prod:/export/jumpstart/sb10/installdb
install_config=ubrsts-cn1p-prod:/export/jumpstart/sb10 rootopts=:rsize=8192
ubrsts-cn2u-uat
root=ubrsts-cn1p-uat:/export/jumpstart/sb10/sparc_10-0106/Solaris_10/Tools/Boot
 install=ubrsts-cn1p-uat:/export/jumpstart/sb10/sparc_10-0106 boottype=:in
sysid_config=ubrsts-cn1p-uat:/export/jumpstart/sb10/installdb
install_config=ubrsts-cn1p-uat:/export/jumpstart/sb10 rootopts=:rsize=8192
root@ubrsts-cn1p#

the scenario is that the client needs to configured from a uat box to a
prod box, this is done by re-jumping the client as a prod box via the prod
network interface

{c} ok boot prod - install (to re-jump it as a uat box use
boot uat - install)

doing a snoop on both interfaces on the jumpstart server reveals primarily
that all traffic was on the prod network but eventually the client and jump
server do talk on the uat network and that thsi causes confusion and the
client is always built as a uat box - not sure if this is because it sees
it first on the card ie mac address ie last figure is a compare to b

if i comment out the uat entry in /etc/ethers, prod box builds fine

will summarise

thanks
Gav

Gavin Whittaker | IB Central Technology - IT Risk Management | JPMorgan
Chase, 60 Victoria Embankment, London, EC4Y OJP | ( W: +44 207 325 0635 | +
gavin.whittaker@jpmchase.com
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:39:43 EDT