From Newsgroup: comp.unix.solaris

On 2025-02-11 17:07, YTC#1 wrote:

On 11/02/2025 20:59, OrangeFish wrote:

On 2025-01-28 03:52, YTC#1 wrote (in part):

On 27/01/2025 21:40, OrangeFish wrote (in part):

[...]

PVID VID MTU-a-a MODE
-a-a-a-a primary-vsw0 00:14:4f:fb:8a:b8 e1000g0 switch@0 1-a-a-a-a-a-a-a-a-a-a-a-a-a-a 1

With s11, hat should have been net0 not e1000g0

I suggest blowing away your primary and ldom (the ldom OS will remain
intact) and rebuilding.

In summary, my mistake was installing ldom 1.2 in Solaris 11.3.-a I
should have installed VM Sparc 3.6.-a (I do not have VM Sparc 3.6.)

Welcome to the world of Oracle.
Have you no Oracle support account at work?

I'm retired -- this is purely my hobby.

To reconfigure anything means rebooting and I am worried that one bad
memory stick may prevent rebooting:

============================ FRU Status ============================
Location-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a Name-a-a-a-a-a Status
------------------------------------------------------
NNL08250CP:CH/MB/CMP0/CH2/R1/D1-a-a-a DIMM-a-a-a-a-a disabled

As it is disabled, providing others are available, then it will reboot.

(Personally, I'd take it out, reseat it and then attempt to clear the status).

or buy a new DIMM :_)

I will try the first and, if it fails, the second.

OF.

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 12/02/2025 00:28, OrangeFish wrote:

On 2025-02-11 17:07, YTC#1 wrote:

On 11/02/2025 20:59, OrangeFish wrote:

On 2025-01-28 03:52, YTC#1 wrote (in part):

On 27/01/2025 21:40, OrangeFish wrote (in part):

[...]

PVID VID MTU-a-a MODE
-a-a-a-a primary-vsw0 00:14:4f:fb:8a:b8 e1000g0 switch@0 1-a-a-a-a-a-a-a-a-a-a-a-a-a-a 1

With s11, hat should have been net0 not e1000g0

I suggest blowing away your primary and ldom (the ldom OS will
remain intact) and rebuilding.

In summary, my mistake was installing ldom 1.2 in Solaris 11.3.-a I
should have installed VM Sparc 3.6.-a (I do not have VM Sparc 3.6.)

Welcome to the world of Oracle.
Have you no Oracle support account at work?

I'm retired -- this is purely my hobby.

And the software is delivered via the repo.
I presume you are just using the GA repo?

The ldomsmanager software should be available from that.

Just run pkg install ldomsmanager
--
Bruce Porter
"The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
There *is* an alternative! http://www.openoffice.org/
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

I am running ldom 1.2 on a T2000 under Solaris 11.3 and following the instructions here:
https://docs.oracle.com/cd/E19227-01/820-7253/index.html

The primary domain was setup using the instructions here (using the
same names): https://docs.oracle.com/cd/E19227-01/820-7253/createdefaultservices/index.html

I created a logical domain and installed Solaris 10 within.

The admin guide states (https://docs.oracle.com/cd/E19227-01/820-7253/enablenetworkbtwncsdomainandotherdomains/index.html):
By default, networking between the control domain and other domains in
the system is disabled. To enable this, the virtual switch device
should be configured as a network device.

Here starts my problem. The virtual switch vsw0 does not show up in
the primary domain.

How do I proceed?

OF.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 26/01/2025 01:02, OrangeFish wrote:

I am running ldom 1.2 on a T2000 under Solaris 11.3 and following the

Erm, should that not be Oracle VM Server for SPARC (as LDoms were
renamed) 3.5? As that is what comes with S11.3

instructions here:
https://docs.oracle.com/cd/E19227-01/820-7253/index.html

The primary domain was setup using the instructions here (using the
same names): https://docs.oracle.com/cd/E19227-01/820-7253/createdefaultservices/ index.html

I created a logical domain and installed Solaris 10 within.

The admin guide states
(https://docs.oracle.com/cd/E19227-01/820-7253/ enablenetworkbtwncsdomainandotherdomains/index.html):
By default, networking between the control domain and other domains in
the system is disabled. To enable this, the virtual switch device
should be configured as a network device.

Here starts my problem.-a The virtual switch vsw0 does not show up in
the primary domain.

How do I proceed?

Sounds like you have not configured it correctly.

What does the following show

* ldm ls primary

* ldm ls <your ldom)

* ldm ls -l

* ipadm

(Or just send me an explorer output, saves time :-) )
--
Bruce Porter
"The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
There *is* an alternative! http://www.openoffice.org/
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 2025-01-26 15:33, YTC#1 wrote:

On 26/01/2025 01:02, OrangeFish wrote:

I am running ldom 1.2 on a T2000 under Solaris 11.3 and following the

Erm, should that not be Oracle VM Server for SPARC (as LDoms were
renamed) 3.5? As that is what comes with S11.3

Oh, I did not see that when I installed 11.3. "apropos oracle" finds
nothing about that. (Ldom was installed in /usr/sbin.)

instructions here:
https://docs.oracle.com/cd/E19227-01/820-7253/index.html

The primary domain was setup using the instructions here (using the
same names):
https://docs.oracle.com/cd/E19227-01/820-7253/createdefaultservices/
index.html

I created a logical domain and installed Solaris 10 within.

The admin guide states
(https://docs.oracle.com/cd/E19227-01/820-7253/
enablenetworkbtwncsdomainandotherdomains/index.html):
By default, networking between the control domain and other domains in
the system is disabled. To enable this, the virtual switch device
should be configured as a network device.

Here starts my problem. The virtual switch vsw0 does not show up in
the primary domain.

How do I proceed?

Sounds like you have not configured it correctly.

Indeed.

What does the following show

* ldm ls primary

primary# ldm ls primary
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv- SP 12 24G 68% 51d 22h 40m

* ldm ls <your ldom)

primary# ldm ls sol10
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
sol10 active -n---- 5000 4 8064M 0.3% 51d 22h 18m

* ldm ls -l

NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv- SP 12 24G 67% 51d 22h 42m

SOFTSTATE
Solaris running

MAC
00:14:4f:cb:4a:44

HOSTID
0x84cb4a44

VCPU
VID PID UTIL STRAND
0 0 56% 100%
1 1 80% 100%
2 2 68% 100%
3 3 76% 100%
4 4 76% 100%
5 5 80% 100%
6 6 50% 100%
7 7 75% 100%
8 12 55% 100%
9 13 60% 100%
10 14 72% 100%
11 15 65% 100%

MAU
ID CPUSET
0 (0, 1, 2, 3)
1 (4, 5, 6, 7)

MEMORY
RA PA SIZE
0x8000000 0x8000000 24G

VARIABLES
boot-device=/pci@780/pci@0/pci@9/scsi@0/disk@0,0:a disk0 disk1
diag-switch?=true
nvramrc=." ChassisSerialNumber NNL08250CP " cr
use-nvramrc?=true

IO
DEVICE PSEUDONYM OPTIONS
pci@780 bus_a
pci@7c0 bus_b

VCC
NAME PORT-RANGE
primary-vcc0 5000-5100

VSW
NAME MAC NET-DEV DEVICE DEFAULT-VLAN-ID
PVID VID MTU MODE
primary-vsw0 00:14:4f:fb:8a:b8 e1000g0 switch@0 1 1
1500

VDS
NAME VOLUME OPTIONS MPGROUP DEVICE
primary-vds0 sol10_disc0
/dev/zvol/dsk/alien/other/sol10/disc0
sol10_iso /other/archive/sol10-u11.iso

VCONS
NAME SERVICE PORT
SP

------------------------------------------------------------------------------ NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
sol10 active -n---- 5000 4 8064M 0.4% 51d 22h 19m

SOFTSTATE
Solaris running

MAC
00:14:4f:fa:28:e5

HOSTID
0x84fa28e5

VCPU
VID PID UTIL STRAND
0 16 0.4% 100%
1 17 0.3% 100%
2 18 0.2% 100%
3 19 0.2% 100%

MAU
ID CPUSET
3 (16, 17, 18, 19)

MEMORY
RA PA SIZE
0x8000000 0x608000000 8064M

VARIABLES
auto-boot?=false
boot-device=disc0:a cdrom
keyboard-layout=US-English

NETWORK
NAME SERVICE DEVICE MAC MODE PVID
VID MTU
vnet0 primary-vsw0@primary network@0 00:14:4f:f9:66:6a 1
1500

DISK
NAME VOLUME TOUT DEVICE SERVER MPGROUP
disc0 sol10_disc0@primary-vds0 disk@0 primary

cdrom sol10_iso@primary-vds0 disk@1 primary


VCONS
NAME SERVICE PORT
sol10 primary-vcc0@primary 5000

* ipadm

primary# ipadm
NAME CLASS/TYPE STATE UNDER ADDR
lo0 loopback ok -- --
lo0/v4 static ok -- 127.0.0.1/8
lo0/v6 static ok -- ::1/128
net0 ip ok -- --
net0/v4 static ok -- 10.0.1.26/24
net0/v6 addrconf ok --
fe80::214:4fff:fecb:4a44/10

(Or just send me an explorer output, saves time :-) )

Sorry -- what is "explorer output"?

Sincerely,
N.

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

In article <vn8ugd$18jbe$1@dont-email.me>,
OrangeFish <OrangeFish@invalid.invalid> wrote:

Sorry -- what is "explorer output"?

The first flaming hoop Larry Ellison's customers must jump thru
in order to report a reproducable Solaris bug or obtain a Sun
part replacement.

<URL:http://pkg.oracle.com/solaris/release/manifest/0/support%2Fexplorer@20.4.20.11.10%2C5.11%3A20201209T023117Z>

John
groenveld@acm.org
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 28/01/2025 00:50, John D Groenveld wrote:

In article <vn8ugd$18jbe$1@dont-email.me>,
OrangeFish <OrangeFish@invalid.invalid> wrote:

Sorry -- what is "explorer output"?

The first flaming hoop Larry Ellison's customers must jump thru
in order to report a reproducable Solaris bug or obtain a Sun
part replacement.

Heh, yeah, granted. But for diagnosing issues when not attached to the
system an invaluable tool.

It can also be used to rebuild a system (config) if no documentation.

<URL:http://pkg.oracle.com/solaris/release/manifest/0/support%2Fexplorer@20.4.20.11.10%2C5.11%3A20201209T023117Z>

John
groenveld@acm.org

--
Bruce Porter
"The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
There *is* an alternative! http://www.openoffice.org/
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 27/01/2025 21:40, OrangeFish wrote:

On 2025-01-26 15:33, YTC#1 wrote:

On 26/01/2025 01:02, OrangeFish wrote:

I am running ldom 1.2 on a T2000 under Solaris 11.3 and following the

Erm, should that not be Oracle VM Server for SPARC (as LDoms were
renamed) 3.5? As that is what comes with S11.3

Oh, I did not see that when I installed 11.3.-a "apropos oracle" finds nothing about that.-a (Ldom was installed in /usr/sbin.)

instructions here:
https://docs.oracle.com/cd/E19227-01/820-7253/index.html

The primary domain was setup using the instructions here (using the
same names):
https://docs.oracle.com/cd/E19227-01/820-7253/createdefaultservices/
index.html

I created a logical domain and installed Solaris 10 within.

The admin guide states
(https://docs.oracle.com/cd/E19227-01/820-7253/
enablenetworkbtwncsdomainandotherdomains/index.html):
By default, networking between the control domain and other domains in
the system is disabled. To enable this, the virtual switch device
should be configured as a network device.

Here starts my problem.-a The virtual switch vsw0 does not show up in
the primary domain.

How do I proceed?

Sounds like you have not configured it correctly.

Indeed.

What does the following show

* ldm ls primary

primary# ldm ls primary
NAME-a-a-a-a-a-a-a-a-a-a-a-a STATE-a-a-a-a-a FLAGS-a-a CONS-a-a-a VCPU-a MEMORY-a-a UTIL-a UPTIME
primary-a-a-a-a-a-a-a-a-a active-a-a-a-a -n-cv--a SP-a-a-a-a-a 12-a-a-a 24G-a-a-a-a-a-a 68%-a 51d 22h
40m

* ldm ls <your ldom)

primary# ldm ls sol10
NAME-a-a-a-a-a-a-a-a-a-a-a-a STATE-a-a-a-a-a FLAGS-a-a CONS-a-a-a VCPU-a MEMORY-a-a UTIL-a UPTIME
sol10-a-a-a-a-a-a-a-a-a-a-a active-a-a-a-a -n-----a 5000-a-a-a 4-a-a-a-a 8064M-a-a-a 0.3%-a 51d 22h
18m

* ldm ls -l

NAME-a-a-a-a-a-a-a-a-a-a-a-a STATE-a-a-a-a-a FLAGS-a-a CONS-a-a-a VCPU-a MEMORY-a-a UTIL-a UPTIME
primary-a-a-a-a-a-a-a-a-a active-a-a-a-a -n-cv--a SP-a-a-a-a-a 12-a-a-a 24G-a-a-a-a-a-a 67%-a 51d 22h
42m

SOFTSTATE
Solaris running

MAC
-a-a-a 00:14:4f:cb:4a:44

HOSTID
-a-a-a 0x84cb4a44

VCPU
-a-a-a VID-a-a-a PID-a-a-a UTIL STRAND
-a-a-a 0-a-a-a-a-a 0-a-a-a-a-a-a 56%-a-a 100%
-a-a-a 1-a-a-a-a-a 1-a-a-a-a-a-a 80%-a-a 100%
-a-a-a 2-a-a-a-a-a 2-a-a-a-a-a-a 68%-a-a 100%
-a-a-a 3-a-a-a-a-a 3-a-a-a-a-a-a 76%-a-a 100%
-a-a-a 4-a-a-a-a-a 4-a-a-a-a-a-a 76%-a-a 100%
-a-a-a 5-a-a-a-a-a 5-a-a-a-a-a-a 80%-a-a 100%
-a-a-a 6-a-a-a-a-a 6-a-a-a-a-a-a 50%-a-a 100%
-a-a-a 7-a-a-a-a-a 7-a-a-a-a-a-a 75%-a-a 100%
-a-a-a 8-a-a-a-a-a 12-a-a-a-a-a 55%-a-a 100%
-a-a-a 9-a-a-a-a-a 13-a-a-a-a-a 60%-a-a 100%
-a-a-a 10-a-a-a-a 14-a-a-a-a-a 72%-a-a 100%
-a-a-a 11-a-a-a-a 15-a-a-a-a-a 65%-a-a 100%

MAU
-a-a-a ID-a-a-a-a CPUSET
-a-a-a 0-a-a-a-a-a (0, 1, 2, 3)
-a-a-a 1-a-a-a-a-a (4, 5, 6, 7)

MEMORY
-a-a-a RA-a-a-a-a-a-a-a-a-a-a-a-a-a-a PA-a-a-a-a-a-a-a-a-a-a-a-a-a-a SIZE
-a-a-a 0x8000000-a-a-a-a-a-a-a 0x8000000-a-a-a-a-a-a-a 24G

VARIABLES
-a-a-a boot-device=/pci@780/pci@0/pci@9/scsi@0/disk@0,0:a disk0 disk1
-a-a-a diag-switch?=true
-a-a-a nvramrc=." ChassisSerialNumber NNL08250CP " cr
-a-a-a use-nvramrc?=true

IO
-a-a-a DEVICE-a-a-a-a-a-a-a-a-a-a PSEUDONYM-a-a-a-a-a-a-a OPTIONS
-a-a-a pci@780-a-a-a-a-a-a-a-a-a bus_a
-a-a-a pci@7c0-a-a-a-a-a-a-a-a-a bus_b

VCC
-a-a-a NAME-a-a-a-a-a-a-a-a-a-a-a-a PORT-RANGE
-a-a-a primary-vcc0-a-a-a-a 5000-5100

VSW
-a-a-a NAME-a-a-a-a-a-a-a-a MAC-a-a-a-a-a-a-a-a-a-a-a-a-a-a NET-DEV DEVICE-a-a DEFAULT-VLAN-ID
PVID VID MTU-a-a MODE
-a-a-a primary-vsw0 00:14:4f:fb:8a:b8 e1000g0 switch@0 1-a-a-a-a-a-a-a-a-a-a-a-a-a-a 1

With s11, hat should have been net0 not e1000g0

I suggest blowing away your primary and ldom (the ldom OS will remain
intact) and rebuilding.

I always create CDom and LDoms via script, so I can redo.

---8< EG for CDOm (with cluster ldoms)
#!/bin/ksh
#
ldm add-vdiskserver primary-vds0 primary
ldm add-vconscon port-range=5000-5100 primary-vcc0 primary
ldm add-vswitch net-dev=net0 primary-vsw0 primary
ldm add-vswitch net-dev=net1 primary-vsw1 primary
ldm add-vswitch net-dev=net2 mode=sc primary-vsw2 primary
ldm add-vswitch net-dev=net3 mode=sc primary-vsw3 primary


ldm set-vcpu 4 primary
ldm start-reconf primary
ldm set-memory 4g primary

ldm add-config -r conf-a
#shutdown -y -g0 -i6
---8<

---8< Ldom1
#!/bin/ksh -x

guest=ld-1
mem=4G
cpu=4
vcon=5011

ldm add-domain ${guest}
ldm set-vcpu ${cpu} ${guest}
ldm set-mem ${mem} ${guest}
ldm set-vcons port=${vcon} ${guest}
ldm bind ${guest}
ldm ls

# 1 VLAN
ldm add-vnet vnet0 primary-vsw0 ${guest}
ldm add-vnet vnet1 primary-vsw1 ${guest}

#zfs create -o mountpoint=/ldoms rpool/ldoms
#zfs create rpool/ldoms/${guest}
#mkfile -n 20g /ldoms/${guest}/disk0.img
ldm add-vdiskserverdevice /ldoms/${guest}/disk0.img rootvol-${guest}@primary-vds0
ldm add-vdisk vdisk10 rootvol-${guest}@primary-vds0 ${guest}
ldm bind ${guest}
ldm list
---8<

-a-a-a-a 1500

VDS
-a-a-a NAME-a-a-a-a-a-a-a-a VOLUME-a-a-a-a-a OPTIONS MPGROUP DEVICE
-a-a-a primary-vds0 sol10_disc0 /dev/zvol/dsk/alien/other/sol10/disc0
-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a sol10_iso-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a /other/archive/sol10-u11.iso

VCONS
-a-a-a NAME-a-a-a-a-a-a-a-a-a-a-a-a SERVICE-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a PORT
-a-a-a SP

------------------------------------------------------------------------------
NAME-a-a-a-a-a-a-a-a-a-a-a-a STATE-a-a-a-a-a FLAGS-a-a CONS-a-a-a VCPU-a MEMORY-a-a UTIL-a UPTIME
sol10-a-a-a-a-a-a-a-a-a-a-a active-a-a-a-a -n-----a 5000-a-a-a 4-a-a-a-a 8064M-a-a-a 0.4%-a 51d 22h
19m

SOFTSTATE
Solaris running

MAC
-a-a-a 00:14:4f:fa:28:e5

HOSTID
-a-a-a 0x84fa28e5

VCPU
-a-a-a VID-a-a-a PID-a-a-a UTIL STRAND
-a-a-a 0-a-a-a-a-a 16-a-a-a-a 0.4%-a-a 100%
-a-a-a 1-a-a-a-a-a 17-a-a-a-a 0.3%-a-a 100%
-a-a-a 2-a-a-a-a-a 18-a-a-a-a 0.2%-a-a 100%
-a-a-a 3-a-a-a-a-a 19-a-a-a-a 0.2%-a-a 100%

MAU
-a-a-a ID-a-a-a-a CPUSET
-a-a-a 3-a-a-a-a-a (16, 17, 18, 19)

MEMORY
-a-a-a RA-a-a-a-a-a-a-a-a-a-a-a-a-a-a PA-a-a-a-a-a-a-a-a-a-a-a-a-a-a SIZE
-a-a-a 0x8000000-a-a-a-a-a-a-a 0x608000000-a-a-a-a-a 8064M

VARIABLES
-a-a-a auto-boot?=false
-a-a-a boot-device=disc0:a cdrom
-a-a-a keyboard-layout=US-English

NETWORK
-a-a-a NAME-a SERVICE-a-a-a-a-a-a-a-a-a-a-a-a-a DEVICE-a-a-a-a MAC-a-a-a-a-a-a-a-a-a-a-a-a-a-a MODE-a-a PVID
VID MTU
-a-a-a vnet0 primary-vsw0@primary network@0-a 00:14:4f:f9:66:6a 1 -a-a-a 1500

DISK
-a-a-a NAME-a VOLUME-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a TOUT DEVICE-a SERVER-a MPGROUP
-a-a-a disc0 sol10_disc0@primary-vds0-a-a-a-a-a disk@0-a primary
-a-a-a cdrom sol10_iso@primary-vds0-a-a-a-a-a-a-a disk@1-a primary

VCONS
-a-a-a NAME-a-a SERVICE-a-a-a-a-a-a-a-a-a-a-a-a-a PORT
-a-a-a sol10-a primary-vcc0@primary 5000

* ipadm

primary# ipadm
NAME-a-a-a-a-a-a-a-a-a-a-a-a-a CLASS/TYPE STATE-a-a-a-a-a-a-a UNDER-a-a-a-a-a ADDR
lo0-a-a-a-a-a-a-a-a-a-a-a-a-a-a loopback-a-a ok-a-a-a-a-a-a-a-a-a-a ---a-a-a-a-a-a-a-a --
-a-a lo0/v4-a-a-a-a-a-a-a-a static-a-a-a-a ok-a-a-a-a-a-a-a-a-a-a ---a-a-a-a-a-a-a-a 127.0.0.1/8
-a-a lo0/v6-a-a-a-a-a-a-a-a static-a-a-a-a ok-a-a-a-a-a-a-a-a-a-a ---a-a-a-a-a-a-a-a ::1/128
net0-a-a-a-a-a-a-a-a-a-a-a-a-a ip-a-a-a-a-a-a-a-a ok-a-a-a-a-a-a-a-a-a-a ---a-a-a-a-a-a-a-a --
-a-a net0/v4-a-a-a-a-a-a-a static-a-a-a-a ok-a-a-a-a-a-a-a-a-a-a ---a-a-a-a-a-a-a-a 10.0.1.26/24
-a-a net0/v6-a-a-a-a-a-a-a addrconf-a-a ok-a-a-a-a-a-a-a-a-a-a -- fe80::214:4fff:fecb:4a44/10

(Or just send me an explorer output, saves time :-) )

Sorry -- what is "explorer output"?

AS John has pointed out, it is a data capture (bundle of) scripts.
Useful to analyse issues.

IIRC, as long as you can see the repo, then
pkg install explorer

And it should be in /usr/sbin

After running an output file is in /var/explorer/output

Sincerely,
N.

--
Bruce Porter
"The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
There *is* an alternative! http://www.openoffice.org/
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 1/25/25 19:02, OrangeFish wrote:

I am running ldom 1.2 on a T2000 under Solaris 11.3

Is the T2000 LDOM hardware / management program that different than the
T1000?

I thought that the T1000 and T2000 were mostly identical save for the
number of CPUs.

I ask because I'm interested in running LDOMs on my T1000 but can't run
them under Solaris 10 because I don't have the LDOM software and my
tests with 11.<something I don't remember> didn't support the T1000.
--
Grant. . . .
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 29/01/2025 00:12, Grant Taylor wrote:

On 1/25/25 19:02, OrangeFish wrote:

I am running ldom 1.2 on a T2000 under Solaris 11.3

Is the T2000 LDOM hardware / management program that different than the T1000?

I thought that the T1000 and T2000 were mostly identical save for the
number of CPUs.

I ask because I'm interested in running LDOMs on my T1000 but can't run
them under Solaris 10 because I don't have the LDOM software and my
tests with 11.<something I don't remember> didn't support the T1000.

The T1000 will run S11.x up to S11.3

You can get S11 CBE here, https://www.oracle.com/solaris/solaris11/downloads/solaris-downloads.html


For S11.4 you need a T4 or newer.
--
Bruce Porter
"The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
There *is* an alternative! http://www.openoffice.org/
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 1/29/25 03:30, YTC#1 wrote:

The T1000 will run S11.x up to S11.3

I know that the system will run Solaris 11, I've had it on there. But
that's not what I was asking about.

I had Solaris 11.0 (and maybe something newer) but it wouldn't manage LDOMs.

From the reading that I did, the LDOM mechanism in the T1000 (and I
thought T2000) was older and not compatible with the LDOM software that
is part of Solaris 11.
--
Grant. . . .
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 30/01/2025 14:45, Grant Taylor wrote:

On 1/29/25 03:30, YTC#1 wrote:

The T1000 will run S11.x up to S11.3

I know that the system will run Solaris 11, I've had it on there.-a But that's not what I was asking about.

I had Solaris 11.0 (and maybe something newer) but it wouldn't manage
LDOMs.

From the reading that I did, the LDOM mechanism in the T1000 (and I
thought T2000) was older and not compatible with the LDOM software that
is part of Solaris 11.

<checks>
Yep, you are correct. Sorry

LDom V2 should work, but 1.2 "preferred"
--
Bruce Porter
"The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
There *is* an alternative! http://www.openoffice.org/
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 1/30/25 10:19, YTC#1 wrote:

<checks>
Yep, you are correct. Sorry

No need to apologize. I could have been misremembering what I
understood at the time or even misunderstood at the time.

LDom V2 should work, but 1.2 "preferred"

So, my question still stands; is the T2000 LDOM hardware / management
program that different than the T1000?

Or do you happen to have the magical software that's not part of Solaris
11 to make it work on your T2000?
--
Grant. . . .
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 31/01/2025 02:31, Grant Taylor wrote:

On 1/30/25 10:19, YTC#1 wrote:

<checks>
Yep, you are correct. Sorry
</c>

No need to apologize.-a I could have been misremembering what I
understood at the time or even misunderstood at the time.

LDom V2 should work, but 1.2 "preferred"

So, my question still stands; is the T2000 LDOM hardware / management program that different than the T1000?

Or do you happen to have the magical software that's not part of Solaris
11 to make it work on your T2000?

Ah, I don;t have a T2000, I have a T5120 and and a T4 (both now unused
and surplus).

It was the OP with the T2000.

The T1000/2000 are known as a T1 chip. The T5xxx range are T2 (then we
have more simply named T3/4/5/6/7/8 :-)

It has been a while, but use I think the T1000/2000 (being the 1st CMT) differed enough for them to block the running of LDom 2.x from running
on the older kit. Also a way to force people to move on :-)
--
Bruce Porter
"The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
There *is* an alternative! http://www.openoffice.org/
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 1/31/25 03:37, YTC#1 wrote:

I think the T1000/2000 (being the 1st CMT) differed enough for them to
block the running of LDom 2.x from running on the older kit. Also a way
to force people to move on EfOe

Yep.

That's the situation that I'm in.
--
Grant. . . .
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 31/01/2025 14:58, Grant Taylor wrote:

On 1/31/25 03:37, YTC#1 wrote:

I think the T1000/2000 (being the 1st CMT) differed enough for them to
block the running of LDom 2.x from running on the older kit. Also a
way to force people to move on EfOe

Yep.

That's the situation that I'm in.

Want a T4? :-)

(note, I am UK based :-( )
--
Bruce Porter
"The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
There *is* an alternative! http://www.openoffice.org/
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 1/31/25 10:27, YTC#1 wrote:

Want a T4? :-)

Maybe.

(note, I am UK based :-( )

If it was in mid USA, I'd say sure.
--
Grant. . . .
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 2025-01-28 03:52, YTC#1 wrote (in part):

On 27/01/2025 21:40, OrangeFish wrote (in part):

[...]

PVID VID MTU-a-a MODE
-a-a-a-a primary-vsw0 00:14:4f:fb:8a:b8 e1000g0 switch@0 1-a-a-a-a-a-a-a-a-a-a-a-a-a-a 1

With s11, hat should have been net0 not e1000g0

I suggest blowing away your primary and ldom (the ldom OS will remain intact) and rebuilding.

In summary, my mistake was installing ldom 1.2 in Solaris 11.3. I
should have installed VM Sparc 3.6. (I do not have VM Sparc 3.6.)

To reconfigure anything means rebooting and I am worried that one bad
memory stick may prevent rebooting:

============================ FRU Status ============================
Location Name Status ------------------------------------------------------ NNL08250CP:CH/MB/CMP0/CH2/R1/D1 DIMM disabled

I always create CDom and LDoms via script, so I can redo.
[...]

Thank you for the scripts -- they will be useful.

OF.

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.unix.solaris

On 11/02/2025 20:59, OrangeFish wrote:

On 2025-01-28 03:52, YTC#1 wrote (in part):

On 27/01/2025 21:40, OrangeFish wrote (in part):

[...]

PVID VID MTU-a-a MODE
-a-a-a-a primary-vsw0 00:14:4f:fb:8a:b8 e1000g0 switch@0 1-a-a-a-a-a-a-a-a-a-a-a-a-a-a 1

With s11, hat should have been net0 not e1000g0

I suggest blowing away your primary and ldom (the ldom OS will remain
intact) and rebuilding.

In summary, my mistake was installing ldom 1.2 in Solaris 11.3.-a I
should have installed VM Sparc 3.6.-a (I do not have VM Sparc 3.6.)

Welcome to the world of Oracle.
Have you no Oracle support account at work?

To reconfigure anything means rebooting and I am worried that one bad
memory stick may prevent rebooting:

============================ FRU Status ============================ Location-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a-a Name-a-a-a-a-a Status
------------------------------------------------------ NNL08250CP:CH/MB/CMP0/CH2/R1/D1-a-a-a DIMM-a-a-a-a-a disabled

As it is disabled, providing others are available, then it will reboot.

(Personally, I'd take it out, reseat it and then attempt to clear the
status).

or buy a new DIMM :_)

I always create CDom and LDoms via script, so I can redo.
[...]

Thank you for the scripts -- they will be useful.

OF.

--
Bruce Porter
"The internet is a huge and diverse community but mainly friendly" http://ytc1.blogspot.co.uk/
There *is* an alternative! http://www.openoffice.org/
--- Synchronet 3.21d-Linux NewsLink 1.2