Determine Solaris server model inside a zone?

up vote
0
down vote

favorite

I'm a DBA doing some inventory and as part of it, I gather some system info. I'm wondering if it's possible to determine what hardware a zone is running on if you only have access to the zone?

I think the answer is "no" because you can't run prtdiag. prtconf also is not available (to any usable extent).

Most of what I need (number of cpus, amount of RAM, OS release, etc.) I can get, so this is a bit of icing on the cake to say "it's on an M5000" or whatever. Works fine from a true physical but I think the info is unavailable in a zone. Anything I missed? Thanks!

asked Nov 15 at 15:40

raindog308

1111

I think if you do find a way to do what you need it should be reported to Oracle as a security vulnerability.
– Jesse_b
Nov 15 at 15:42

add a comment |

up vote
0
down vote

favorite

I'm a DBA doing some inventory and as part of it, I gather some system info. I'm wondering if it's possible to determine what hardware a zone is running on if you only have access to the zone?

I think the answer is "no" because you can't run prtdiag. prtconf also is not available (to any usable extent).

asked Nov 15 at 15:40

raindog308

1111

I think if you do find a way to do what you need it should be reported to Oracle as a security vulnerability.
– Jesse_b
Nov 15 at 15:42

add a comment |

up vote
0
down vote

favorite

I'm a DBA doing some inventory and as part of it, I gather some system info. I'm wondering if it's possible to determine what hardware a zone is running on if you only have access to the zone?

I think the answer is "no" because you can't run prtdiag. prtconf also is not available (to any usable extent).

asked Nov 15 at 15:40

raindog308

1111

I'm a DBA doing some inventory and as part of it, I gather some system info. I'm wondering if it's possible to determine what hardware a zone is running on if you only have access to the zone?

I think the answer is "no" because you can't run prtdiag. prtconf also is not available (to any usable extent).

solaris solaris-zones

asked Nov 15 at 15:40

raindog308

1111

asked Nov 15 at 15:40

raindog308

1111

asked Nov 15 at 15:40

raindog308

1111

asked Nov 15 at 15:40

raindog308

1111

asked Nov 15 at 15:40

raindog308

1111

I think if you do find a way to do what you need it should be reported to Oracle as a security vulnerability.
– Jesse_b
Nov 15 at 15:42

add a comment |

I think if you do find a way to do what you need it should be reported to Oracle as a security vulnerability.
– Jesse_b
Nov 15 at 15:42

I think if you do find a way to do what you need it should be reported to Oracle as a security vulnerability.
– Jesse_b
Nov 15 at 15:42

add a comment |

1 Answer
1

active

oldest

votes

up vote
0
down vote

The maximum that you could from Solaris zone - to learn server family name via processor type.
For example, this is something from SPARC T7-* family:

user@zone:~$ psrinfo -vp

   The physical processor has 6 virtual processors (16-21)

     SPARC-M7 (chipid 0, clock 4133 MHz)

and you could only guess if it is primary or guest LDOM.

Also you could find some information about connected to LDOM disks via iostat:

user@zone:~$ iostat -En

   ssd2             Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 

   Vendor: HITACHI  Product: OPEN-V      -SUN Revision: 8301 Serial No: 50413A37000E 

   Size: 214.75GB <214749020160 bytes>

   Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 

   Illegal Request: 1343 Predictive Failure Analysis: 0 Non-Aligned Writes: 0 

   ssd3             Soft Errors: 0 Hard Errors: 6 Transport Errors: 6 

   Vendor: HITACHI  Product: OPEN-V      -SUN Revision: 8301 Serial No: 50413A37000D 

   Size: 483.18GB <483183820800 bytes>

   Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 

   Illegal Request: 1343 Predictive Failure Analysis: 0 Non-Aligned Writes: 0

But there is no guarantee that this is full list of connected devices to physical server, because there may be several LDOMs on it.

PS/

If you have root access to LDOM, you may use virtinfo command to learn some parent machine information (you could not use it in zone):

root@ldom:~# virtinfo -a

Domain role: LDoms guest I/O

Domain name: domain1

Domain UUID: 8dff4050-8f62-4db5-b5b1-b14023fc058a

Control domain: physical-server-name.local

Chassis serial#: AK00000000

answered Nov 22 at 16:38

Sasha Golikov

2317

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481966%2fdetermine-solaris-server-model-inside-a-zone%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
0
down vote

The maximum that you could from Solaris zone - to learn server family name via processor type.
For example, this is something from SPARC T7-* family:

user@zone:~$ psrinfo -vp

   The physical processor has 6 virtual processors (16-21)

     SPARC-M7 (chipid 0, clock 4133 MHz)

and you could only guess if it is primary or guest LDOM.

Also you could find some information about connected to LDOM disks via iostat:

user@zone:~$ iostat -En

   ssd2             Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 

   Vendor: HITACHI  Product: OPEN-V      -SUN Revision: 8301 Serial No: 50413A37000E 

   Size: 214.75GB <214749020160 bytes>

   Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 

   Illegal Request: 1343 Predictive Failure Analysis: 0 Non-Aligned Writes: 0 

   ssd3             Soft Errors: 0 Hard Errors: 6 Transport Errors: 6 

   Vendor: HITACHI  Product: OPEN-V      -SUN Revision: 8301 Serial No: 50413A37000D 

   Size: 483.18GB <483183820800 bytes>

   Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 

   Illegal Request: 1343 Predictive Failure Analysis: 0 Non-Aligned Writes: 0

But there is no guarantee that this is full list of connected devices to physical server, because there may be several LDOMs on it.

PS/

If you have root access to LDOM, you may use virtinfo command to learn some parent machine information (you could not use it in zone):

root@ldom:~# virtinfo -a

Domain role: LDoms guest I/O

Domain name: domain1

Domain UUID: 8dff4050-8f62-4db5-b5b1-b14023fc058a

Control domain: physical-server-name.local

Chassis serial#: AK00000000

answered Nov 22 at 16:38

Sasha Golikov

2317

add a comment |

up vote
0
down vote

The maximum that you could from Solaris zone - to learn server family name via processor type.
For example, this is something from SPARC T7-* family:

user@zone:~$ psrinfo -vp

   The physical processor has 6 virtual processors (16-21)

     SPARC-M7 (chipid 0, clock 4133 MHz)

and you could only guess if it is primary or guest LDOM.

Also you could find some information about connected to LDOM disks via iostat:

user@zone:~$ iostat -En

   ssd2             Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 

   Vendor: HITACHI  Product: OPEN-V      -SUN Revision: 8301 Serial No: 50413A37000E 

   Size: 214.75GB <214749020160 bytes>

   Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 

   Illegal Request: 1343 Predictive Failure Analysis: 0 Non-Aligned Writes: 0 

   ssd3             Soft Errors: 0 Hard Errors: 6 Transport Errors: 6 

   Vendor: HITACHI  Product: OPEN-V      -SUN Revision: 8301 Serial No: 50413A37000D 

   Size: 483.18GB <483183820800 bytes>

   Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 

   Illegal Request: 1343 Predictive Failure Analysis: 0 Non-Aligned Writes: 0

But there is no guarantee that this is full list of connected devices to physical server, because there may be several LDOMs on it.

PS/

If you have root access to LDOM, you may use virtinfo command to learn some parent machine information (you could not use it in zone):

root@ldom:~# virtinfo -a

Domain role: LDoms guest I/O

Domain name: domain1

Domain UUID: 8dff4050-8f62-4db5-b5b1-b14023fc058a

Control domain: physical-server-name.local

Chassis serial#: AK00000000

answered Nov 22 at 16:38

Sasha Golikov

2317

add a comment |

up vote
0
down vote

The maximum that you could from Solaris zone - to learn server family name via processor type.
For example, this is something from SPARC T7-* family:

user@zone:~$ psrinfo -vp

   The physical processor has 6 virtual processors (16-21)

     SPARC-M7 (chipid 0, clock 4133 MHz)

and you could only guess if it is primary or guest LDOM.

Also you could find some information about connected to LDOM disks via iostat:

user@zone:~$ iostat -En

   ssd2             Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 

   Vendor: HITACHI  Product: OPEN-V      -SUN Revision: 8301 Serial No: 50413A37000E 

   Size: 214.75GB <214749020160 bytes>

   Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 

   Illegal Request: 1343 Predictive Failure Analysis: 0 Non-Aligned Writes: 0 

   ssd3             Soft Errors: 0 Hard Errors: 6 Transport Errors: 6 

   Vendor: HITACHI  Product: OPEN-V      -SUN Revision: 8301 Serial No: 50413A37000D 

   Size: 483.18GB <483183820800 bytes>

   Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 

   Illegal Request: 1343 Predictive Failure Analysis: 0 Non-Aligned Writes: 0

But there is no guarantee that this is full list of connected devices to physical server, because there may be several LDOMs on it.

PS/

If you have root access to LDOM, you may use virtinfo command to learn some parent machine information (you could not use it in zone):

root@ldom:~# virtinfo -a

Domain role: LDoms guest I/O

Domain name: domain1

Domain UUID: 8dff4050-8f62-4db5-b5b1-b14023fc058a

Control domain: physical-server-name.local

Chassis serial#: AK00000000

answered Nov 22 at 16:38

Sasha Golikov

2317

The maximum that you could from Solaris zone - to learn server family name via processor type.
For example, this is something from SPARC T7-* family:

user@zone:~$ psrinfo -vp

   The physical processor has 6 virtual processors (16-21)

     SPARC-M7 (chipid 0, clock 4133 MHz)

and you could only guess if it is primary or guest LDOM.

Also you could find some information about connected to LDOM disks via iostat:

user@zone:~$ iostat -En

   ssd2             Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 

   Vendor: HITACHI  Product: OPEN-V      -SUN Revision: 8301 Serial No: 50413A37000E 

   Size: 214.75GB <214749020160 bytes>

   Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 

   Illegal Request: 1343 Predictive Failure Analysis: 0 Non-Aligned Writes: 0 

   ssd3             Soft Errors: 0 Hard Errors: 6 Transport Errors: 6 

   Vendor: HITACHI  Product: OPEN-V      -SUN Revision: 8301 Serial No: 50413A37000D 

   Size: 483.18GB <483183820800 bytes>

   Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 

   Illegal Request: 1343 Predictive Failure Analysis: 0 Non-Aligned Writes: 0

But there is no guarantee that this is full list of connected devices to physical server, because there may be several LDOMs on it.

PS/

If you have root access to LDOM, you may use virtinfo command to learn some parent machine information (you could not use it in zone):

root@ldom:~# virtinfo -a

Domain role: LDoms guest I/O

Domain name: domain1

Domain UUID: 8dff4050-8f62-4db5-b5b1-b14023fc058a

Control domain: physical-server-name.local

Chassis serial#: AK00000000

answered Nov 22 at 16:38

Sasha Golikov

2317

answered Nov 22 at 16:38

Sasha Golikov

2317

answered Nov 22 at 16:38

Sasha Golikov

2317

answered Nov 22 at 16:38

Sasha Golikov

2317

add a comment |

draft saved

draft discarded

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Sstrhsrtj