10 More Discussions You Might Find Interesting
1. Solaris
dear members,
i am a newbie to solaris 11.3, and deeply impressed. On my test pc (Lenovo M90), however, using the internet hangs the system from time to time;
initializing the connecting (WLAN) during installation (via the live cd)
took two attempts as well.
Maybe someone has a solution... (7 Replies)
Discussion started by: RichardLichten
7 Replies
2. Solaris
Hello, i have a solaris 11 sparc64 and Im trying to do a backup to tape. This is the display:
# ufsdump 0uf /dev/rmt/0cbn /dev/rdsk/c2t0d0s2
DUMP: Date of this level 0 dump: February 27, 2013 01:58:23 PM CET
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/rdsk/c2t0d0s2 to... (2 Replies)
Discussion started by: Ferch13
2 Replies
3. Solaris
Power server up runs through diagnostics.
Goes to the boot section and then the bit where the cursor is spinning and thats it. Hangs completely.
Any ideas? (10 Replies)
Discussion started by: psychocandy
10 Replies
4. Solaris
Got a strange problem.
I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10.
When I try to ssh from one Solaris 10 server to another server ssh hangs.
I have an identical server and when I try this everything works fine.
The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies
5. Ubuntu
Hi All
I have a dedicated backup server running ubuntu 10.04, which has recently been rebuilt (same OS, just different h/w)
This is used to receive ufsdump output from a number of Solaris servers, using the following syntax:
ufsdump 1uf :/path/to/backup/file /fs/to/be/backed/up
This has... (1 Reply)
Discussion started by: in2deep
1 Replies
6. Solaris
Solaris 10 (Sun V210) System hangs every couple of months. Have to go into ALOM to reset. I did a consolehistory report and seen this in it.
Failed to exec inetd_start method of instance svc:/network/bootps/udp:default: I/O error
WARNING: /pci@1c,600000/scsi@2 (glm0):
Resetting... (3 Replies)
Discussion started by: Joeentech
3 Replies
7. Solaris
Hi,
We've got a Sun Fire V245 that's failing to boot from either boot disk (mirrored using SVM). It simply hangs after loading a few modules:
Sun Fire V245, No Keyboard
Copyright 2006 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.22.22, 1024 MB memory installed, Serial... (5 Replies)
Discussion started by: badoshi
5 Replies
8. Solaris
Greetings Forumers!
I tried installing Solaris Cluster 3.3 today. I should say I tried configuring the Cluster today. The software is already installed on two systems. I am trying to configure a shared filesystem between two 6320 Blades. I selected the "Custom" install because the "Typical"... (2 Replies)
Discussion started by: bluescreen
2 Replies
9. Solaris
Hi all,
I have a SUN server Sun-Fire-V890 running solaris 9, with a remote system console .
Both the IP adresses of the server and the console are in a private network (address 10.67.xxx).
For some reasons I need to give the access to the server from outside address 194.xxx, but I prefer that... (2 Replies)
Discussion started by: aribault
2 Replies
10. UNIX for Advanced & Expert Users
/dev/md/dsk/d0 20174761 1778528 18194486 9% /
/dev/md/dsk/d30 17648810 1592139 15880183 10% /usr
/proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
fd 0 0 0 ... (0 Replies)
Discussion started by: sriny
0 Replies
stmsboot(1M) stmsboot(1M)
NAME
stmsboot - administration program for the Solaris I/O multipathing feature
SYNOPSIS
/usr/sbin/stmsboot [-d | -e | -u | -L | -l controller_number]
The Solaris I/O multipathing feature is a multipathing solution for storage devices that is part of the Solaris operating environment. This
feature was formerly known as Sun StorEdge Traffic Manager (STMS) or MPxIO.
The stmsboot program is an administrative command to manage enumeration of fibre channel devices under Solaris I/O multipathing. Solaris
I/O multipathing-enabled devices are enumerated under scsi_vhci(7D), providing multipathing capabilities. Solaris I/O multipathing-disabled
devices are enumerated under the physical controller.
In the /dev and /devices trees, Solaris I/O multipathing-enabled devices receive new names that indicate that they are under Solaris I/O
multipathing control. This means a device will have a different name from its original name (following installation) when it is under
Solaris I/O multipathing control. The stmsboot command automatically updates /etc/vfstab and dump configuration to reflect the device names
changes when enabling or disabling Solaris I/O multipathing. A reboot is required for changes to take effect.
The following options are supported:
-e
Enables Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports. Following this enabling, you are prompted to reboot.
During the reboot, vfstab and the dump configuration will be updated to reflect the device name changes.
-d
Disables Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports. Following this disabling, you are prompted to reboot.
During the reboot, vfstab and the dump configuration will be updated to reflect the device name changes.
-u
Updates vfstab and the dump configuration after you have manually modified the configuration to have Solaris I/O multipathing enabled
or disabled on specific fp(7D) controller ports. This option prompts you to reboot. During the reboot, vfstab and the dump configura-
tion will be updated to reflect the device name changes.
-L
Display the device name changes from non-Solaris I/O multipathing device names to Solaris I/O multipathing device names.
-l controller_number
Display the device name changes from non-Solaris I/O multipathing device names to Solaris I/O multipathing device names for the speci-
fied controller.
Along with its primary function of enabling or disabling Solaris I/O multipathing, the stmsboot command is used to update vfstab and the
dump configuration to reflect device name changes. For a system to function properly, you must configure the applications that consume the
devices by old names to use the new names.
The -L and -l options display the mapping between the old and new device names. These options work after the changes made to the Solaris
I/O multipathing configuration have taken effect. For example, you can use these options following the reboot after invoking stmsboot -e.
The old device names must exist in order to display the mappings.
Example 1: Enabling Solaris I/O Multipathing Following OS Upgrade
To enable Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports run:
# stmsboot -e
Example 2: Disabling Solaris I/O Multipathing
To disable Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports, run:
# stmsboot -d
Example 3: Enabling Solaris I/O Multipathing on Selected Ports
You want to enable Solaris I/O multipathing on some fibre channel controller ports and disable the feature on the rest. You edit the
fp.conf file (see fp(7D)) to enable or disable Solaris I/O multipathing on specific controller ports. You then run the following command to
have vfstab and the dump configuration updated to reflect the new device names:
# stmsboot -u
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu, SUNWcslr |
+-----------------------------+-----------------------------+
|Interface Stability |Obsolete |
+-----------------------------+-----------------------------+
SEE ALSO
dumpadm(1M), ufsdump(1M), dumpdates(4), vfstab(4), fcp(7D), fctl(7D), fp(7D), qlc(7D), scsi_vhci(7D)
Consult the Sun StorEdge Disk Tray [or Subsystem] Administrator's Guide for the T3, 3910, 3960, 6120, and 6320 storage subsystems.
Sun StorEdge Traffic Manager Installation and Configuration Guide
Solaris I/O multipathing is not supported on all devices. After enabling Solaris I/O multipathing, only those devices that Solaris I/O mul-
tipathing supports are placed under Solaris I/O multipathing control. Non-supported devices remain as before.
For Solaris releases prior to the current release, the -e and -d options remove the mpxio-disable property entries from fp.conf file (see
fp(7D)) and add a global mpxio-disable entry to fp.conf.
The current release of the Solaris operating system does not support the mpxio-disable property. Solaris I/O multipathing is always
enabled. If you want to disable multipathing, you must use the mechanisms provided by the HBA drivers. See fp(7D).
Enabling Solaris I/O Multipathing on a Sun StorEdge Disk Array
The following applies to Sun StoreEdge T3, 3910, 3960, 6120, and 6320 storage subsystems.
To place your Sun StorEdge disk subsystem under Solaris I/O multipathing control, in addition to enabling Solaris I/O multipathing, the
mp_support of the subsystem must be set to mpxio mode. The preferred sequence is to change the subsystem's mp_support to mpxio mode, then
run stmsboot -e. If Solaris I/O multipathing is already enabled but the subsystem's mp_support is not in mpxio mode, then change the
mp_support to mpxio mode and run stmsboot -u.
Refer to the Sun StorEdge Administrator's Guide for your subsystem for more details.
ufsdump Users
The ufsdump command keeps records of the filesystem dumps in /etc/dumpdates (see dumpdates(4)). Among other items, the records contain
device names. An effect of the "active" stmsboot options (-e, -d, and -u) is to change the device name of a storage device. The stmsboot
command does not modify the dumpdates file. Because of this, the dumpdates records will refer to the old device names, that is, the device
names that were in effect before you ran stmsboot. The effect of this device name-dumpdates disagreement is that, following use of stms-
boot, ufsdump will be processed as if no previous dump had ever been made, thus dumping the entire filesystem (effectively, a level 0
dump).
Procedure to Use stmsboot in Sun Cluster Environment
If possible, use stmsboot -e before you start installing Sun Cluster software. After you run stmsboot, you install Sun Cluster software as
you normally would.
If you install Sun Cluster software before running stmsboot, you must use the following procedure.
On each machine in the cluster on which you want to enable the Solaris multipathing feature, enter:
# stmsboot -e
...and allow the system to reboot.
When the system comes up, enter the following two commands:
1. # /usr/cluster/bin/scdidadm -C
2. # /usr/cluster/bin/scdidadm -r
The preceding commands update did mappings with new device names while preserving did instance numbers for disks that are connected to
multiple cluster nodes. did instance numbers of the local disks might not be preserved. For this reason, the did disk names for local
disks might change.
3. Update /etc/vfstab to reflect any new did disk names for your local disks.
4. Reboot the system.
To disable the Solaris multipathing feature, use stmsboot -d (instead of stmsboot -e), then follow the procedure above.
To view mappings between the old and new device names, run stmsboot -L. To view did device name mappings, run /usr/cluster/bin/scdidadm -L.
3 Mar 2005 stmsboot(1M)