![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Problem Resolution Sure Solution 1008914.1 : Sun Fire[TM] 12K/15K/E20K/E25K: Console stuck in IOSRAM mode
PreviouslyPublishedAs 212263 Applies to:Sun Fire 12K Server - Version Not Applicable to Not Applicable [Release N/A]Sun Fire 15K Server - Version Not Applicable to Not Applicable [Release N/A] Sun Fire E20K Server - Version Not Applicable to Not Applicable [Release N/A] Sun Fire E25K Server - Version Not Applicable to Not Applicable [Release N/A] All Platforms SymptomsSun Fire[TM] 15K: Console stuck in IOSRAM mode Changes
CauseConsole cannot be toggled from IOSRAM to network: this may happen if no MAN network is configured at domain side. ~= Toggle the communication path between the network and IOSRAM interfaces. The console was stuck in IOSRAM mode. On typing ~ IOSRAM mode is shown following ~= which should have toggled it. SolutionProcess for enabling dman interface An /etc/ hostname.dman0 file is required for each domain. If the file is not configured, Solaris[TM] does not plumb the domain side I1 interface, thus it cannot switch to network. Create the hostname.dman0 file, and then plumb and bring up the interface. Example: # vi /etc/hostname.dman0 192.168.100.2 netmask + broadcast + private up Create a file for each domain. You can get the IP address from the /etc/opt/SUNWSMS/config/MAN.cf file. Attachments This solution has no attachment |
||||||||||||
|