Jumpstart Sunfire V240

Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Jumpstart Sunfire V240
# 1  
Old 11-21-2007
Jumpstart Sunfire V240

I trying to jumpstart SunFire V240 Solaris 10, 2006_01. All the jumpstart files on jumpstart install and boot server are ok (tested on another machine Sun Ultra 10). But this system comes out with: "The file just loaded does not appear to be executable." after "boot net - install" and setting arp connection with the boot install server. (boot-device is set to net)
If booting the same Solaris version from a DVD it runs smoothly. Grrrrrr ...
Any ideas?
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Failed to identify flash rom on Sunfire V240 running Solaris 10

Hi Guys, I have performed OBP & ALOM upgrade on V240 system. One of my system, running Solaris 10, having issue to identify flash rom during ALOM 1.6.10 version upgrade (OBP upgraded to latest one). May I know what the reason of this error and how can I fix it so I can upgrade ALOM using... (0 Replies)
Discussion started by: myrpthidesis
0 Replies

2. Solaris

Question on selling/unloading Sunfire V240

Over 6 years ago I picked up a Sunfire V240 from my employer who was unloading all of their Sun hardware. Two processors, 4GB RAM and half dozen SCSI disk drives. It doesn't have an OS or a CD Rom/DVD drive. I have a collection of SCSI drives that should work with the server. So if I can get... (2 Replies)
Discussion started by: gandolf989
2 Replies

3. Solaris

SunFire V240 CPU Heat Sink Replacement

I got a replacement Heatsink and Fan unit, but the OEM unit has the SUN Thermal Interface Material (TIM) already on the heatsink matting surface. Because mine is used it does not have the TIM. Also there are 2 different TIM material SUN used based on the Processor (1-1.28GHz uses a glue backed... (1 Reply)
Discussion started by: danneskjold0809
1 Replies

4. UNIX for Dummies Questions & Answers

Installing Solaris 10 on sunfire v240

please help, I am a Linux newbie and I have a sunfire v240 that I got used with the hard drives removed and I am hoping to install Solaris 10 on it to learn. I bought 2 scsi hard drives which are the exact replacement for the machine. I've installed the hard drives and have downloaded Solaris 10... (9 Replies)
Discussion started by: nodgeman
9 Replies

5. Solaris

SUNFIRE V240 procedure to shutdown with safety in order to replace power cables

Question: Which commands to use to shutdown with safety the server; (2 Replies)
Discussion started by: doudou2012
2 Replies

6. Solaris

XIR failed at SF V240

Dear All, I have problem with SF V240 with solaris 10. This server always booting with error message like this What's problem with my server? Best Regards Wisnu:) (10 Replies)
Discussion started by: mbah_jiman
10 Replies

7. Hardware

Need Help connecting to sunfire v240

I recently acquired a sunfire v240 and I'm trying to get into it so I can install linux on it. Right now I'm still trying to get a monitor connected so I can do this. I've tried connecting to it with a crossover cable to my laptop (vista and linux equipped). I was able to get a connection... (2 Replies)
Discussion started by: QuadRunner750
2 Replies

8. Solaris

sun v240 performance

Hi, we are having one sun v240 server, now this server is performing very slow, checked using top, iostat and vmstat commands, output is looking normal, but the performance is very slow and generating more traffic in network, how can we resolve this. Regards RJS (5 Replies)
Discussion started by: rajasekg
5 Replies

9. UNIX for Dummies Questions & Answers

V240 EPROM reset

Hello all, Does anyone know how to reset the ALOM password for Sun fire V240 or the OBP password? I was given a V240 without any password or hard drive. Thanks (3 Replies)
Discussion started by: larryase
3 Replies

10. UNIX for Dummies Questions & Answers

Installing Solaris 9 on Sunfire V240

Hey guys, I had a Sunfire V240 with Solaris 10 preinstalled but replaced the original 2 -73g harddrives with 2 146g drives now I'm trying to install Solaris 9 which I want to use not 10. Now I keep getting this error: Rebooting with command: boot Boot device: disk0:a File and args: The... (2 Replies)
Discussion started by: kingdbag
2 Replies
Login or Register to Ask a Question
NSDB-JUMPSTART(8)					      System Manager's Manual						 NSDB-JUMPSTART(8)

nsdb-jumpstart - Administer a basic FedFS NSDB using OpenLDAP SYNOPSIS
nsdb-jumpstart [-h,--help] [--version] nsdb-jumpstart [--statedir= statedir] install [--security= mode] nsdb-jumpstart [--statedir= statedir] status nsdb-jumpstart [--statedir= statedir] backup nsdb-jumpstart [--statedir= statedir] restore [backup-name] INTRODUCTION
RFC 5716 introduces the Federated File System (FedFS, for short). FedFS is an extensible standardized mechanism by which system adminis- trators construct a coherent namespace across multiple file servers using file system referrals. For further details, see fedfs(7). A FedFS domain's namespace is joined together via junctions. When a file-access client encounters a junction on a file server, the file server provides a list of locations where that client can access the target file set to which the juntion refers. In a FedFS domain, these location lists are stored on one or more LDAP servers, known as namespace databases, or NSDBs, for short. FedFS-enabled file servers access the information stored on NSDBs via standard LDAP queries. Tools that administer a FedFS domain use ldapmodify queries to manage information stored on an NSDB. File-access clients have no need to access NSDBs directly. Further information about junctions and NSDBs is available in fedfs(7). DESCRIPTION
The FedFS NSDB Proposed Standard allows flexible use of any LDAP server and its Directory Information Tree to store and manage NSDB infor- mation. The nsdb-jumpstart(8) command provides a simplified but fully capable stand-alone NSDB based specifically on OpenLDAP. Using this command, you can install a fresh NSDB, or back up or restore your NSDB data. It can even construct a self-signed x.509 certificate to enable secure NSDB queries. Operation The install subcommand sets up an empty NSDB, ready to be used in a FedFS domain. The new NSDB replaces any OpenLDAP configuration that may already exist on the system. OpenLDAP must already be installed on the system. Once the new NSDB is running, FedFS fileset location information is stored as records in a Directory Information Tree under the NCE. This information is managed with commands like nsdb-create-fsn(8). A handful of parameters are needed to set up the new NSDB. These are gathered via a brief interview. The domain name and administrator credentials are provided during this interview. Passwords are not checked for strength, however blank passwords are not permitted. The baseline security requirements for the NSDB are specified at install time using the --security= option. See the SECURITY section for an in-depth discussion. Once set up with the install subcommand, OpenLDAP listens for LDAP queries on the standard LDAP port (389). The underlying LDAP server can be configured like any other OpenLDAP server using the new-style cn=config configuration interface. To display the current status of the NSDB service on the local host, use the status subcommand. Information about the local NSDB service is displayed, including whether the LDAP service is started, whether it actually is an NSDB, and whether TLS security is required to use it. The nsdb-jumpstart(8) command also provides backup and restore facilities. The backup subcommand saves location information stored on the local NSDB to a dated LDIF file. LDIF files created by the backup command are stored in the /var/lib/fedfs/nsdb-backup directory by default. The restore subcommand completely replaces the contents of the NSDB with a backup contained in of one of the previously saved LDIF files. The restore subcommand takes one positional argument, which is the name of the backup to restore. A list of backups is displayed by using the restore subcommand with no argument. The nsdb-jumpstart(8) command must run as root. A audit log of each nsdb-jumpstart(8) operation is stored in /var/lib/fedfs/nsdb-jump- start.log. Subcommands Valid nsdb-jumpstart(8) subcommands are: install Replace the OpenLDAP configuration on the local system with a ready-built NSDB. The user is asked to confirm before action is taken. Specifying the --security= option sets the transport security that the NSDB requires clients to use when communicating with it. status Display the status of the NSDB on the local system. This subcommand takes no arguments. backup Generate an LDIF containing the NSDB information stored on the local LDAP server. The LDIF is stored in a dated file under /var/lib/fedfs/nsdb-backup. This subcommand takes no arguments. restore Replace the NSDB information on the local LDAP server with the contents of an LDIF. This subcommand takes a backup name as an argu- ment. If no backup name is given, a list of backups that can be restored is displayed. The user is asked to confirm before action is taken. Command line options The following options are specified before the subcommand on the command line. --help Displays usage and copyright information, then exit. --version Displays fedfs-utils version information, then exit. --stateidr=pathname Specifies the pathname of the local directory under which NSDB data is maintained. By default, this directory is /var/lib/fedfs. Subcommand options --security=mode Selects the security mode of the NSDB. This option may be specified only on the install subcommand. Valid mode values are none and tls. If none is specified, or the --security= option is not specified, clients can connect to this NSDB in the clear. If tls is specified, the install subcommand creates a self-signed x.509 certificate, and configures the NSDB so that clients are required to use TLS when connecting to the NSDB. EXIT CODES
The nsdb-jumpstart(8) command returns one of two values upon exit. 0 The subcommand succeeded. 1 The subcommand failed. EXAMPLES
Suppose you are the FedFS administrator of the example.net FedFS domain. After you have chosen a reliable server in the example.net domain to act as your NSDB, log in on that server as root, ensure that OpenLDAP is installed, and that any configuration can be discarded. To create a new NSDB with a self-signed certificate for the example.net domain, use: # ./nsdb-jumpstart install --security=tls This command is about to replace the OpenLDAP configuration on this system. Do you want to continue? [y/N] y Enter the name of the Fedfs domain this NSDB will server FedFS domain [ example.net ]: Enter the LDAP administrator DN for this NSDB Admin DN [ cn=admin,cn=config ]: Enter the LDAP administrator password for this DN New password: Re-enter new password: Enter the NSDB administrator password for this DN New password: Re-enter new password: Last chance: about to replace the OpenLDAP configuration on this system. Continue? [y/N] y Setting up a self-signed x.509 certificate. Please answer the following questions: Country (C)? US State or province (ST)? Massachusetts City (L)? Boston Organization (O)? Red Sox Organizational unit (OU)? Fans NSDB configuration was successful. Slapd is enabled and running The LDAP administrator DN is: cn=admin,cn=config The NSDB administrator DN is: cn=NSDB Manager,dc=example,dc=net The NCE is: ou=fedfs,dc=example,dc=net Distribute the NSDB's certificate in /etc/openldap/nsdb-cert.pem # SECURITY
The NSDB created by the nsdb-jumpstart(8) command allows anonymous read access to the NCE and all entries under it. The LDAP server's rootDSE is also readable by anyone. An NSDB client must bind with administrator privileges to update NSDB records for a FedFS domain. ACLs may be adjusted after the NSDB is set up with nsdb-jumpstart(8). Before binding, however, NSDB clients must connect to the NSDB to use it. The --security= setting determines what type of transport layer security is required to connect to the NSDB. When the --security=none option is specified during NSDB setup, or if no --security= setting is specified, NSDB clients can connect to the NSDB using an unencrypted connection to the standard LDAP port (389). By specifying the --security=tls option on the nsdb-jumpstart(8) command, a self-signed x.509 certificate is created that NSDB clients must use to authenticate the NSDB and its contents. The underlying LDAP server requires the use of TLS and the use of AES or better encryption when a client access the NSDB. The NSDB never authenticates its clients. To use this NSDB, the new certificate material must be distributed to NSDB clients (fileservers and administrative systems) and installed using the nsdbparams(8) command, or it can be transferred directly to NSDB clients that are running the rpc.fedfsd(8) daemon. The use of a transport encryption mechanism such as TLS is strongly recommended to protect NSDB requests on untrusted networks. SASL is currently not supported for the NSDB protocol. FILES
/var/lib/fedfs/nsdb-jumpstart.log Log file created during subcommand processing /etc/openldap/nsdb-cert.pem File containing the server's x.509 certificate, in PEM format /etc/openldap/nsdb-key.pem File containing the server's private key, in PEM format /var/lib/fedfs/nsdb-db Directory containing back-end database for the LDAP server's domain controller root suffix SEE ALSO
fedfs(7), nfsref(8), nsdb-create-fsn(8), nsdbparams(8), rpc.fedfsd(8) RFC 5716 for FedFS requirements and overview COLOPHON
This page is part of the fedfs-utils package. A description of the project and information about reporting bugs can be found at http://wiki.linux-nfs.org/wiki/index.php/FedFsUtilsProject. AUTHOR
Chuck Lever <chuck.lever@oracle.com> 3 February 2014 NSDB-JUMPSTART(8)