ldom host cannot see ldom primary
in [Solaris]
|
Prev: PLS COMMENT: *ONE* zfs safest, foolproof(est)? Re: ZFS: A *nested*zfs down within a higher-up zfs: SNAPSHOT the top one, bot one done too?
Next: Assembler "/usr/ccs/bin/as" error while running Oracle 11G upgrade script
From: Vide on 5 Jan 2010 05:57 Hi I've a Solaris 10 installation with ldom The primary domain is running SunOS solaris10 5.10 Generic_141444-09 sun4v sparc SUNW,SPARC-Enterprise- T5220 Solaris and the ldom guest SunOS bdofi 5.10 Generic_141444-09 sun4v sparc SUNW,SPARC-Enterprise-T5220 Now, both have access to the LAN but they cannot see each other through the network, so no ping, no scp, nothing. I am pretty new to ldom and solaris so I really don't know where to start... I gues something related to the ldom virtual switch... Thanks in advance -- Vide
From: Zfs.. on 5 Jan 2010 08:31 On Jan 5, 10:57 am, Vide <vid...(a)gmail.com> wrote: > Hi > > I've a Solaris 10 installation with ldom > The primary domain is running > > SunOS solaris10 5.10 Generic_141444-09 sun4v sparc SUNW,SPARC-Enterprise- > T5220 Solaris > > and the ldom guest > > SunOS bdofi 5.10 Generic_141444-09 sun4v sparc SUNW,SPARC-Enterprise-T5220 > > Now, both have access to the LAN but they cannot see each other through the > network, so no ping, no scp, nothing. > I am pretty new to ldom and solaris so I really don't know where to start.... > I gues something related to the ldom virtual switch... > > Thanks in advance > > -- > Vide Do you have the virtual switch plumbed up in the Control Domain ? Post the output of ldm list-bindings primary
From: Vide on 5 Jan 2010 09:20 Zfs.. wrote: > Do you have the virtual switch plumbed up in the Control Domain ? > > Post the output of ldm list-bindings primary # ldm list-bindings primary NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME primary active -n-cv- SP 24 28G 1.8% 20d 20h 8m MAC 00:21:28:0f:5d:f4 HOSTID 0x850f5df4 CONTROL failure-policy=ignore DEPENDENCY master= VCPU VID PID UTIL STRAND 8 8 9.5% 100% 9 9 0.8% 100% 10 10 1.0% 100% 11 11 0.6% 100% 12 12 2.7% 100% 13 13 0.4% 100% 14 14 0.3% 100% 15 15 17% 100% 16 16 2.3% 100% 17 17 2.0% 100% 18 18 2.2% 100% 19 19 1.5% 100% 20 20 1.2% 100% 21 21 2.1% 100% 22 22 1.6% 100% 23 23 2.6% 100% 24 24 0.8% 100% 25 25 1.5% 100% 26 26 1.1% 100% 27 27 5.4% 100% 28 28 2.2% 100% 29 29 2.6% 100% 30 30 0.6% 100% 31 31 1.6% 100% MAU ID CPUSET 0 (8, 9, 10, 11, 12, 13, 14, 15) 1 (16, 17, 18, 19, 20, 21, 22, 23) 2 (24, 25, 26, 27, 28, 29, 30, 31) MEMORY RA PA SIZE 0x8000000 0x8000000 28G VARIABLES auto-boot?=false keyboard-layout=Spanish IO DEVICE PSEUDONYM OPTIONS pci@0 pci niu(a)80 niu VCC NAME PORT-RANGE primary-vcc0 5000-5100 CLIENT PORT bdofi(a)primary-vcc0 5000 VSW NAME MAC NET-DEV DEVICE DEFAULT-VLAN-ID PVID VID MTU MODE primary-vsw0 00:14:4f:fa:6c:01 e1000g0 switch@0 1 1 1500 PEER MAC PVID VID MTU vnet1(a)bdofi 00:14:4f:f8:f7:76 1 1500 VDS NAME VOLUME OPTIONS MPGROUP DEVICE primary-vds0 c1t0d0s0 /dev/dsk/c1t0d0s0 cdrom /dev/rdsk/c0t0d0s2 zdisk0 /dev/zvol/dsk/ofipool/ofidisk0 CLIENT VOLUME cdrom(a)bdofi cdrom zdisk0(a)bdofi zdisk0 VCONS NAME SERVICE PORT SP -- Vide
From: Zfs.. on 5 Jan 2010 10:35 On Jan 5, 2:20 pm, Vide <vid...(a)gmail.com> wrote: > Zfs.. wrote: > > Do you have the virtual switch plumbed up in the Control Domain ? > > > Post the output of ldm list-bindings primary > > # ldm list-bindings primary > NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME > primary active -n-cv- SP 24 28G 1.8% 20d 20h 8m > > MAC > 00:21:28:0f:5d:f4 > > HOSTID > 0x850f5df4 > > CONTROL > failure-policy=ignore > > DEPENDENCY > master= > > VCPU > VID PID UTIL STRAND > 8 8 9.5% 100% > 9 9 0.8% 100% > 10 10 1.0% 100% > 11 11 0.6% 100% > 12 12 2.7% 100% > 13 13 0.4% 100% > 14 14 0.3% 100% > 15 15 17% 100% > 16 16 2.3% 100% > 17 17 2.0% 100% > 18 18 2.2% 100% > 19 19 1.5% 100% > 20 20 1.2% 100% > 21 21 2.1% 100% > 22 22 1.6% 100% > 23 23 2.6% 100% > 24 24 0.8% 100% > 25 25 1.5% 100% > 26 26 1.1% 100% > 27 27 5.4% 100% > 28 28 2.2% 100% > 29 29 2.6% 100% > 30 30 0.6% 100% > 31 31 1.6% 100% > > MAU > ID CPUSET > 0 (8, 9, 10, 11, 12, 13, 14, 15) > 1 (16, 17, 18, 19, 20, 21, 22, 23) > 2 (24, 25, 26, 27, 28, 29, 30, 31) > > MEMORY > RA PA SIZE > 0x8000000 0x8000000 28G > > VARIABLES > auto-boot?=false > keyboard-layout=Spanish > > IO > DEVICE PSEUDONYM OPTIONS > pci@0 pci > niu(a)80 niu > > VCC > NAME PORT-RANGE > primary-vcc0 5000-5100 > CLIENT PORT > bdofi(a)primary-vcc0 5000 > > VSW > NAME MAC NET-DEV DEVICE DEFAULT-VLAN-ID > PVID VID MTU MODE > primary-vsw0 00:14:4f:fa:6c:01 e1000g0 switch@0 1 > 1 1500 > PEER MAC PVID VID > MTU > vnet1(a)bdofi 00:14:4f:f8:f7:76 1 > 1500 > > VDS > NAME VOLUME OPTIONS MPGROUP DEVICE > primary-vds0 c1t0d0s0 > /dev/dsk/c1t0d0s0 > cdrom > /dev/rdsk/c0t0d0s2 > zdisk0 > /dev/zvol/dsk/ofipool/ofidisk0 > CLIENT VOLUME > cdrom(a)bdofi cdrom > zdisk0(a)bdofi zdisk0 > > VCONS > NAME SERVICE PORT > SP > > -- > Vide If both the control and guest domain are on different subnets then plumbing the vsw0 interface might solve your problem ifconfig vsw0 plumb ifconfig vsw0 "address on guests subnet" plumb up and then try your ping / ssh etc
From: Vide on 5 Jan 2010 11:09
Zfs.. wrote: > If both the control and guest domain are on different subnets then > plumbing the vsw0 interface might solve your problem They are on the same /20, although the primary was misconfigured and had a /8 netmask. Now I've changed it on the primary but still n o luck... maybe ldm doesn't understand this on the fly? -- Vide |