10-21-2017
dear sir
thanks for the kind reply. well the main problem was the medical device and now we solved and it works properly.however, there is an imaging system installed in the sun blade and once the medical device detect something , it install in the data base and the imaging shown in the imaging system in the sun blade.
well i want the sun blade run. so if there is a way to make the solaries run without a hard drive or dvd disc
i am looking to heir from you as soon as possible
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I would like to upgrade the memory in my Sun Blade 150 workstation. In reading through Sun's Blade 150 DIMM Installation Guide, it indicates that the memory must be "certified by Sun for the Sun Blade 150 system."
Does anyone know if any SDRAM, PC133 • CL=2 • Unbuffered • ECC • 133MHz • 3.3V ... (2 Replies)
Discussion started by: here2learn
2 Replies
2. UNIX for Dummies Questions & Answers
Hi, I am new to UNIX. I have a Sun Blade 150 worksation. I used a Dell monitor and Dell keyboard as input and output devices. However, workstation always told me that keyboard couldn't be found. I used Dell keyboard with USB and Dell keyboard with series connector. It all didn't work. Please help... (10 Replies)
Discussion started by: duke0001
10 Replies
3. Solaris
I'm not familiar with this particular machine and it's baffling me. For those that are familar with the workstation, allow me to paint a picture. If you were looking down on the machine (open) you would see the main board and then a riser board. On the left side of the riser board are jacks... (1 Reply)
Discussion started by: silversaleen68
1 Replies
4. Solaris
FYI noob to here and sun blades...
I have a sun blade 100 and I can't get the cdrom to work. if i try using vold that doesn't seem to work either...maybe i'm not using it correctly.
Upon boot you can open/close the cdrom and it runs but after i'm logged in it won't open and i can't access it... (2 Replies)
Discussion started by: shaun138
2 Replies
5. Solaris
We had to replace a hard drive in one of our Sun Blade 150s, but now it hangs during the Jumpstart. It will show 1 or 2 Timeout for ARP/RARP messages and then start the spinning numbers. It always stops at 2ae00 and just hangs there.
We have 1 combined jumpstart server and it is also our NIS+... (5 Replies)
Discussion started by: stottsja
5 Replies
6. Solaris
Hi,
I have a Solaris 8.0 BLADE 150 machine. I have an onboard graphics alongwith an addon XVR500 graphics card. Now, when I use the motherboard graphics, I am not able to login to the XWINDOWS terminal, instead it stays on the console.
But, if I insert the monitor cable to the XVR500 port,... (2 Replies)
Discussion started by: angshuman_ag
2 Replies
7. Solaris
I have recently re-installed Solaris 10 on a Sun Blade 150 followed by a patch set (10_Recommended) dated 2011.12.05.
I have just noticed /bin/sun now returns false, rather than true. See below.
$ uname -a
SunOS myblade1 5.10 Generic_147440-07 sun4u sparc SUNW,Sun-Blade-100
$ /bin/sparc &&... (1 Reply)
Discussion started by: apmcd47
1 Replies
8. Solaris
Hello,
Ive just aquired a blade 150 off ebay.Im new to suns and are having a problem getting it to boot off the cdrom.Openboot continuously tries to do a network boot and I cant enter any commands.Im using an average pc keyboard and it definetly works.Thanks for any help.:wall: (3 Replies)
Discussion started by: chucky
3 Replies
9. Solaris
Hello,
I cant get my blade box to boot off the harddrive after installing solaris 10.I can get to a root prompt after issuing "boot cdrom -s".I tried booting off disk0 and disk1,but I get "the file just loaded does not seem to be executable".Thanks for any help.:wall: (4 Replies)
Discussion started by: chucky
4 Replies
10. Solaris
Hi everybody,
I'm having big troubles in installing Solaris 8 on a Sun Blade 150.
Here are some system specs:
Sun Blade 150 (UltraSPARC-IIe 550MHz)
RAM: 256MB
OBP 4.10.6 2003/06/06 12:30
POST 2.0.1 2001/08/23 17:13
When I try to boot from Solaris 8 CD with boot cdrom or... (10 Replies)
Discussion started by: Vortigern
10 Replies
LEARN ABOUT DEBIAN
fence_drac
fence_drac(8) System Manager's Manual fence_drac(8)
NAME
fence_drac - fencing agent for Dell Remote Access Card
SYNOPSIS
fence_drac [OPTION]...
DESCRIPTION
fence_drac is an I/O Fencing agent which can be used with the Dell Remote Access Card (DRAC). This card provides remote access to control-
ling power to a server. It logs into the DRAC through the telnet interface of the card. By default, the telnet interface is not enabled.
To enable the interface, you will need to use the racadm command in the racser-devel rpm available from Dell. To enable telnet on the
DRAC:
[root]# racadm config -g cfgSerial -o cfgSerialTelnetEnable 1
[root]# racadm racreset
fence_drac accepts options on the command line as well as from stdin. Fenced sends parameters through stdin when it execs the agent.
fence_drac can be run by itself with command line options. This is useful for testing and for turning outlets on or off from scripts.
Vendor URL: http://www.dell.com
OPTIONS
-a IPaddress
IP address or hostname of the switch.
-c cmd_prompt
Force fence_drac to use cmd_prompt as the command prompt
-d dracversion
Force fence_drac to treat the device as though it was for the specified drac version
-D dumpfile
Debug file of the telnet interaction
-h Print out a help message describing available options, then exit.
-l login
Login name.
-m modulename
The module name of the blade when using DRAC/MC firmware.
-o action
The action required. reboot (default), off, on or status.
-p password
Password for login.
-S path
Full path to an executable to generate the password for login.
-f seconds
Wait X seconds before fencing is started
-V Print out a version message, then exit.
STDIN PARAMETERS
action = < param >
The action required. reboot (default), off, on or status.
agent = < param >
This option is used by fence_node(8) and is ignored by fence_apc.
cmd_prompt = < param >
Force fence_drac to use cmd_prompt as the command prompt
drac_version = < param >
Force fence_drac to treat the device as though it was for the specified drac version.
debug = < dumpfile >
Debug file of the telnet interaction
ipaddr = < hostname | ip >
IP address or hostname of the switch.
login = < param >
Login name.
modulename = < param >
The module name of the blade when using DRAC/MC firmware.
passwd = < param >
Password for login.
passwd_script = < param >
Full path to an executable to generate the password for login.
delay = < param >
Wait X seconds before fencing is started
SEE ALSO
fence(8), fence_node(8)
fence_drac(8)