Sponsored Content
Operating Systems Solaris Help with Stubborn Sun Ultra Enterprise 450 Post 302673949 by Perderabo on Wednesday 18th of July 2012 03:24:34 PM
Old 07-18-2012
Well, E450 is not really from "these days". Smilie It's not even from the current century.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Enterprise 450 Solaris 9 Problems

I am just getting started loading an Enterprise 450 Dell with Solaris 9 however I cannot get out of a loop that is not letting me get started. My basic question is what are the key strokes to get you out of a boot sequence so that you can at least clear the hard drive or start an install ... (9 Replies)
Discussion started by: Joe7778
9 Replies

2. Solaris

ultra enterprise 3000

I have been trying to install a few different distributions on this server, i have 1 sparc 250 mhz, 512 ram, it has a scsi with the built in ethernet, ive tried debian, bsd, with no luck, i can gentoo live cd to run and work with the ethernet, but i would like a normal distro, anywaysi have solaris... (4 Replies)
Discussion started by: hahjoel
4 Replies

3. Solaris

keyboard & monitor for SUn ultra enterprise 3000

Hi all, i just purchased Sun Ultra Enterprise 3000, but they did not include with keyboard/mouse . i am very new with this box. could you give me which type of keyboard i can use and video connector to my monitor since serial connectors for keyboard and video is different with my PC. ... (5 Replies)
Discussion started by: waterbear
5 Replies

4. Solaris

ULTRA ENTERPRISE 3000is it worth switching on

Please excuse my noobie ignorance, I have just taken posession of a ULTRA ENTERPRISE 3000 for a song. I know it is old , is it worth powering up, or worth more as scrap metal? Would a $1000 pc have more grunt as a web server? Google doesn't seem to be able to answer my question. I also have 2... (1 Reply)
Discussion started by: kadil
1 Replies

5. Solaris

Sun ultra enterprise 450 server does not power on

Hi, I have a sun ultra enterprise 450 server. There is no power supply to the peripheral components. Can anyone suggest what might be the problem with the server? What do i have to check for? I am new to the solaris and server world. Please suggest in detail. :) Thanks, Ashwini (5 Replies)
Discussion started by: tgashwini
5 Replies

6. Solaris

Problem booting Sun ultra enterprise 450 server

Hi, I have a sun ultra enterprise 450 server. This server powers on and a white screen appears with the system and network information. But it doesnot boot up completely. Booting operation wil be halted by a warning: \usr\sbin\fsck not found. Most likely the mount of \usr failed or the... (5 Replies)
Discussion started by: tgashwini
5 Replies

7. Solaris

Usb to serial connection to Sun Enterprice 450

Hi all, I must connect my PC (Windows 2000) to Sun Enterprise 450 (4 X UltraSPARC-II 400Mhz) for Solaris 10 Installation. My PC doesn't have a serial port therefore I must use USB port. How can I connect USB port of my PC to the serial port (DB 25) of Sun 450? Will be there any problems with... (3 Replies)
Discussion started by: Sunb3
3 Replies

8. UNIX for Dummies Questions & Answers

Sun ultra enterprise 450 power issue

I've search the forum and came up with someone having the same issue where the power does not going to the main board. I turn the key and nothing, no lights or anything moving. I have another board put it in the same system and it works just fine. Please help, thank you in advance. (2 Replies)
Discussion started by: vhtran
2 Replies

9. Solaris

Powering ON SUN 450 Enterprise

Problem powering ON the SUN 450 E, we checked voltage and the power supply. Seems to be we have out of 3 LED's in the back 2 are glowing, when we turn the power button on the front from standby to ON. Does anyone know how to troubleshoot this?. I have looked through some troubleshooting... (2 Replies)
Discussion started by: calsum
2 Replies

10. Solaris

Sun Ultra Enterprise 4500 not booting

Hi, I hope anyone could help me on this. Here we have an Ultra Enterprise 4500 server. Since a few days ago, when starting the system, it showed a message about a faulty CPU fan. So, we manage to clean it up by removing it and then installing it back (as in the user manual). After that, when... (2 Replies)
Discussion started by: lonchus
2 Replies
patchsvr(1M)						  System Administration Commands					      patchsvr(1M)

NAME
patchsvr - set up a Sun Update Connection Proxy SYNOPSIS
/usr/sbin/patchsvr setup [-c cache-location] [-d] [-h] [-l] [-p update-source-url] [-s pw-file-location] [-u user-name] [-x web-proxy- host:port] /usr/sbin/patchsvr start /usr/sbin/patchsvr stop /usr/sbin/patchsvr enable /usr/sbin/patchsvr disable DESCRIPTION
The patchsvr command enables you to set up a Sun Update Connection Proxy on your intranet. The setup subcommand configures the Sun Update Connection Proxy. The start and stop subcommands start and stop the Sun Update Connection Proxy. Finally, the enable and disable subcom- mands permit you to start up and prevent startup of the Sun Update Connection Proxy at boot time. The Sun Update Connection Proxy was previously called local patch server. Note - The Sun Update Connection Proxy supports client systems that use the Sun Update Connection, System Edition software and the Sun Patch Manager 2.0 software. A Sun Update Connection client system is not compatible with the older local patch server feature asso- ciated with the Sun Patch Manager 2.0 software. Configuring Your Sun Update Connection Proxy By default, Update Manager expects that your local systems are connected, via the Internet, to the Sun update server to be analyzed and to receive updates. By using a Sun Update Connection Proxy instead, you can minimize the Internet traffic and serve your local systems from a update server on your intranet. The system you choose to act as the Sun Update Connection Proxy must be running at least the Developer Solaris Software Group of the Solaris 10 Operating System. You must also install the Sun Update Manager 1.0 software and the Sun Update Connection Proxy software. The use of a Sun Update Connection Proxy addresses security concerns and reduces the amount Internet traffic between the Sun update server and your client systems. For instance, instead of having to download updates and metadata from the Sun update server to each of your systems, the data is downloaded to the Sun Update Connection Proxy the first time that a client system requests an update. After the update data is stored on your Sun Update Connection Proxy, the transfer of update data to your system for analysis is done over your intranet instead of over the Internet. You can configure a chain of update servers on your intranet. The last link in the chain of local servers can point to the Sun update server or to a local collection of updates. By using this chain of servers, an update download request from your system to its primary update server can be forwarded to other servers in the chain in an attempt to fulfill the request. So, if your system's primary server can- not locate an update, the server makes the same request of the next server in the chain to see if the update is stored there. If the update is found, it is downloaded to the system. If the update is not found, the request continues along the chain until the update is found or the terminal point in the chain is reached. Each server in the chain stores the updates found on another server in the chain based on the download request. So, an update that is not initially found on your local server will be downloaded to your local server and stored before being downloaded to the client system. Your Sun Update Connection Proxy must specify the source of updates to use. By default, the server obtains updates from the Sun update server, but it can also obtain updates from another update server in the chain or from a collection of updates on your system. You must specify the URL that points to the collection of updates. By default, the Sun update server is the source of updates. The URL is: https://getupdates.sun.com/solaris/ Note that this URL must appear as a single line. This URL must point to another server in the chain or to a collection of updates on the local system. This URL cannot be null. Starting and Stopping Your Sun Update Connection Proxy The patchsvr start command starts the Sun Update Connection Proxy. You can also enable the boot-time startup of the Sun Update Connection Proxy by running patchsvr enable. The patchsvr stop command stops the Sun Update Connection Proxy. You can also disable the boot-time startup of the Sun Update Connection Proxy by running patchsvr disable. Before you use your Sun Update Connection Proxy for the first time, you must run the patchsvr start command. Use these commands when you want to change the configuration of your Sun Update Connection Proxy. Before you use the patchsvr setup command to change the configuration parameter values, you must stop your Sun Update Connection Proxy. Then, you can update the configuration val- ues. Finally, you must restart the Sun Update Connection Proxy. OPTIONS
The following options are supported for the patchsvr setup command: -c cache-location Specifies the location of the server's cache, also known as the update repository. This is the directory in which downloaded updates are stored on the Sun Update Connection Proxy. You must specify a full path to the cache loca- tion. By default, the cache location is file:/var/sadm/spool/patchsvr. Ensure that this update repository has 2 Gbytes of free disk space available to store downloaded updates. -d Resets the Sun Update Connection Proxy configuration settings to the default values. -h Displays information about the command-line options. -l Lists the configuration settings for the update server. -p update-source-url Specifies the URL that points to the collection of updates. By default, the URL points to the Sun update server: https://getupdates.sun.com/solaris/ Note that this URL must appear as a single line. -s pw-file-location Specifies the path of the proxy password file in which you have stored your proxy password. You must put the password in a file rather than specifying it on the command line because command-line information is visible via the ps command. -u user-name Specifies the user name required for web proxy authentication. -x web-proxy-host:port Specifies the local web proxy. If the Sun Update Connection Proxy is behind a firewall, use this option to specify the web proxy that accesses the Internet. Get the name of the web proxy, web-proxy-host, and its port, port, from your system administrator or network administrator. The default port value is 8080. Do not use this option if you are accessing update data from a collection of updates on the Sun Update Connection Proxy. EXAMPLES
Example 1: Changing the Cache Location # patchsvr setup -c /var/update/cache Example 2: Specifying the Sun Update Server as the Source of Updates # patchsvr setup -p https://getupdates.sun.com/solaris/ The Sun update server is the default source of updates. Example 3: Specifying a Sun Update Connection Proxy as the Source of Updates # patchsvr setup -p http://updatesvr1:3816/solaris/ Specifies the system called updatesvr1, a Sun Update Connection Proxy, as the source of updates. Example 4: Specifying a CD as the Source of Updates # patchsvr setup -p file:/cdrom/cdrom0 Specifies the CD mounted from the first CD-ROM drive of the local system as the update source. Example 5: Specifying a Web Proxy # patchsvr setup -x webproxy:8080 Specifies the host name, webproxy, and port, 8080, of the web proxy that your Sun Update Connection Proxy uses to connect to the Internet. Example 6: Specifying a User Name and Password for Web Proxy Authentication # (umask 77 ; vi /tmp/password) # patchsvr setup -u terry -s /tmp/password # rm /tmp/password While in a subshell, you create a temporary file that is not readable by others and put the password in that file. Next, you specify the user name, terry, and location of the password file, /tmp/password, used to authenticate the web proxy that your Sun Update Connection Proxy uses to connect to the Internet. Then, you delete the temporary file now that the web proxy authentication is specified. Example 7: Resetting the Configuration Settings to the Default Values # patchsvr setup -d Example 8: Listing the Configuration Settings for Your Sun Update Connection Proxy # patchsvr setup -l Patch source URL: https://getupdates.sun.com/solaris/ Cache location: /var/sadm/spool/patchsvr Web proxy host name: mars Web proxy port number: 8080 Shows the configuration settings, which include information about the source of updates, the location of the cache directory, and, if needed, a web proxy and port. Example 9: Starting the Sun Update Connection Proxy # patchsvr start Example 10: Stopping the Sun Update Connection Proxy # patchsvr stop Stops your Sun Update Connection Proxy. While the update server is stopped, you can change the configuration settings for your Sun Update Connection Proxy, then restart it. Example 11: Enabling the Boot-Time Startup of the Sun Update Connection Proxy # patchsvr enable Example 12: Disabling the Boot-Time Startup of the Sun Update Connection Proxy # patchsvr disable ATTRIBUTES
See the attributes(5) man page for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWpsvru | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
smpatch(1M), attributes(5) Sun Update Manager 1.0 Administration Guide SunOS 5.10 12 May 2005 patchsvr(1M)
All times are GMT -4. The time now is 05:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy