How to identify SCSI JBOD arrays commonly used as boot device for disk-less Starcat (12K/15K/E20K/E25K) and Serengeti (3800/48x0/6800/4900/6900) platforms
(Doc ID 1333828.1)
Last updated on MAY 01, 2023
Applies to:
Sun Fire 3800 Server - Version Not Applicable and laterSun Fire E6900 Server - Version Not Applicable and later
Sun Fire 4810 Server - Version Not Applicable and later
Sun Fire 4800 Server - Version Not Applicable and later
Sun Fire 15K Server - Version Not Applicable and later
Information in this document applies to any platform.
Goal
The following High-End platforms do not have internal disks that can be used as boot device, so usually this function is accomplished by an attached SCSI JBOD (Just a Bunch Of Disks) array:
- Sun Fire[TM] 12K/15K/E20K/E25K Servers (Starcat)
- Sun Fire 3800, 4800, 4810, 6800, E4900, and E6900 Systems (Serengeti)
This Document will help to identify which SCSI JBOD array is attached to a disk-less system (usually configured as boot device) among the most commonly used ones:
- Sun StorEdge D1000 (and D2)
- Sun StorEdge 3120
- Sun StorEdge D240 Media Tray
- Sun StorEdge S1
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| Sun StorEdge D1000 (also applicable to Sun StorEdge D2 array) |
| Sun StorEdge 3120 |
| Sun StorEdge D240 Media Tray |
| Sun StorEdge S1 |
| References |