Sponsored Content
Operating Systems Solaris 3510FC connected to Solaris10 -- v240 Post 302590844 by ppchu99 on Tuesday 17th of January 2012 06:36:57 PM
Old 01-17-2012
Bug 3510FC

I did this cabling according to the best practise of SE 3510FC document..

one dual controller tray + one expansion tray...

I noticed the lights on the 6 drives for each tray is off for some strange reason when operating...

here is the connection I see:

FC2 (1st controller) ---> bottom right FC port, expansion tray
FC3 (2nd controller) ---> bottomr left FC port , expansion tray
FC3 (1st controller) ---> v240 host
FC2 (2nd controller) ---> 420R host

I am almost 99% of this cable connection is OK, since at one point I was able to see the disks on both hosts, using vxvm, now if I do a path listing to some disks, it is telling me invalid, about half of the total hosts. cfgadm tells me half of them are not connected..

I am curious what might be the problems...
 

10 More Discussions You Might Find Interesting

1. 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

2. UNIX for Dummies Questions & Answers

Jumpstart Sunfire V240

Hi, 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... (0 Replies)
Discussion started by: jump
0 Replies

3. 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

4. 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

5. Solaris

Alom Sun V240

hallo anybody know how to set alom mail alerty server with yahoomail ? thank u?where i can find mail server address for yahoomail?thank (1 Reply)
Discussion started by: yanto85
1 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. Solaris

v240 -- wrong date

after shutting down the server and the ILOM/ALOM, its date seems to go back to 1977..rather than current date.. problem with battery on ILOM/ALOM ??:( (1 Reply)
Discussion started by: ppchu99
1 Replies

8. Solaris

Sun V240 Raid Question

Hi All, I'm new to this site. I have a few question since I'm in the process how to to repair my raid on Sun V240 Server. 1. How can we create RAID in Sun Sparc v240? 2. What utility can help people create RAID in Sun Sparc v240? 3. Do we need any special software to create the... (12 Replies)
Discussion started by: angkor
12 Replies

9. Solaris

breaking into a v240's alom

had a v240 pre-configured and running the OS and alom, for about 3 months good, no issues. All of sudden, I can't see the IP address of the OS and the alom.. There is nothing wrong with thet network... I suspect the ALOM crashed and/or something bad happened to it.. Is there anyway... (3 Replies)
Discussion started by: ppchu99
3 Replies

10. Solaris

V240 no OBP or console available

Hey guys, I recently replaced the heatsinks on two different V240's. Repasted and replaced them myself. After attempting to bring them back up, there was no display coming from the KVM. I figured it was a matter of environment in OBP and attempted to get to the OK prompt from the... (20 Replies)
Discussion started by: DanielSluder
20 Replies
EJECT(1)							   User Commands							  EJECT(1)

NAME
eject - eject removable media SYNOPSIS
eject [options] device|mountpoint DESCRIPTION
Eject allows removable media (typically a CD-ROM, floppy disk, tape, JAZ, ZIP or USB disk) to be ejected under software control. The com- mand can also control some multi-disc CD-ROM changers, the auto-eject feature supported by some devices, and close the disc tray of some CD-ROM drives. The device corresponding to device or mountpoint is ejected. If no name is specified, the default name /dev/cdrom is used. The device may be addressed by device name (e.g. 'sda'), device path (e.g. '/dev/sda'), UUID=<uuid> or LABEL=<label> tags. There are four different methods of ejecting, depending on whether the device is a CD-ROM, SCSI device, removable floppy, or tape. By default eject tries all four methods in order until it succeeds. If device partition is specified, the whole-disk device is used. If the device or a device partition is currently mounted, it is unmounted before ejecting. OPTIONS
-a, --auto on|off This option controls the auto-eject mode, supported by some devices. When enabled, the drive automatically ejects when the device is closed. -c, --changerslot slot With this option a CD slot can be selected from an ATAPI/IDE CD-ROM changer. Linux 2.0 or higher is required to use this feature. The CD-ROM drive can not be in use (mounted data CD or playing a music CD) for a change request to work. Please also note that the first slot of the changer is referred to as 0, not 1. -d, --default List the default device name. -f, --floppy This option specifies that the drive should be ejected using a removable floppy disk eject command. -F, --force Force eject, don't check device type. -h, --help Print a help text and exit. -i, --manualeject on|off This option controls locking of the hardware eject button. When enabled, the drive will not be ejected when the button is pressed. This is useful when you are carrying a laptop in a bag or case and don't want it to eject if the button is inadvertently pressed. -p, --proc This option allow you to use /proc/mounts instead /etc/mtab. It also passes the -n option to umount(1). -q, --tape This option specifies that the drive should be ejected using a tape drive offline command. -m, --no-unmount The option tells eject to not try to unmount at all. -M, --no-partitions-unmount The option tells eject to not try to unmount another partitions on partitioned devices. If another partition is mounted the program will not attempt to eject the media. It will attempt to unmount only mountpoint or mounted device given on eject command line. -n, --noop With this option the selected device is displayed but no action is performed. -t, --trayclose With this option the drive is given a CD-ROM tray close command. Not all devices support this command. -T, --traytoggle With this option the drive is given a CD-ROM tray close command if it's opened, and a CD-ROM tray eject command if it's closed. Not all devices support this command, because it uses the above CD-ROM tray close command. -r, --cdrom This option specifies that the drive should be ejected using a CDROM eject command. -s, --scsi This option specifies that the drive should be ejected using SCSI commands. -v, --verbose Run in verbose mode; more information is displayed about what the command is doing. -V, --version Display program version and exit. -x, --cdspeed <speed> With this option the drive is given a CD-ROM select speed command. The speed argument is a number indicating the desired speed (e.g. 8 for 8X speed), or 0 for maximum data rate. Not all devices support this command and you can only specify speeds that the drive is capable of. Every time the media is changed this option is cleared. This option can be used alone, or with the -t and -c options. -X, --listspeed With this option the CD-ROM drive will be probed to detect the available speeds. The output is a list of speeds which can be used as an argument of the -x option. This only works with Linux 2.6.13 or higher, on previous versions solely the maximum speed will be reported. Also note that some drive may not correctly report the speed and therefore this option does not work with them. EXIT STATUS
Returns 0 if operation was successful, 1 if operation failed or command syntax was not valid. NOTES
Eject only works with devices that support one or more of the four methods of ejecting. This includes most CD-ROM drives (IDE, SCSI, and proprietary), some SCSI tape drives, JAZ drives, ZIP drives (parallel port, SCSI, and IDE versions), and LS120 removable floppies. Users have also reported success with floppy drives on Sun SPARC and Apple Macintosh systems. If eject does not work, it is most likely a limi- tation of the kernel driver for the device and not the eject program itself. The -r, -s, -f, and -q options allow controlling which methods are used to eject. More than one method can be specified. If none of these options are specified, it tries all four (this works fine in most cases). Eject may not always be able to determine if the device is mounted (e.g. if it has several names). If the device name is a symbolic link, eject will follow the link and use the device that it points to. If eject determines that the device can have multiple partitions, it will attempt to unmount all mounted partitions of the device before ejecting (see --no-partitions-unmount). If an unmount fails, the program will not attempt to eject the media. You can eject an audio CD. Some CD-ROM drives will refuse to open the tray if the drive is empty. Some devices do not support the tray close command. If the auto-eject feature is enabled, then the drive will always be ejected after running this command. Not all Linux kernel CD-ROM driv- ers support the auto-eject mode. There is no way to find out the state of the auto-eject mode. You need appropriate privileges to access the device files. Running as root is required to eject some devices (e.g. SCSI devices). AUTHORS
Jeff Tranter <tranter@pobox.com> - original author. Karel Zak <kzak@redhat.com> and Michal Luscon <mluscon@redhat.com> - util-linux version. SEE ALSO
lsblk(8), findmnt(8), mount(8), umount(8) AVAILABILITY
The eject command is part of the util-linux package and is available from Linux Kernel Archive <ftp://ftp.kernel.org/pub/linux/utils/util- linux/>. Linux April 2012 EJECT(1)
All times are GMT -4. The time now is 11:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy