Related Manuals for Fujitsu Solaris 10
Summary of Contents for Fujitsu Solaris 10
- Page 1 B23Q8YA-G-02-F PRIMEPOWER Hardware Platform Guide: Operation for Solaris™ 10 Operating System -- Start Here--...
- Page 3 Customer, shall not use the Product without securing the sufficient safety required for the High Safety Required Use. In addition, Fujitsu (or other affiliate's name) shall not be liable against the Customer and/or any third party for any claims or damages arising in connection with the High Safety Required Use of the Product.
- Page 4 Notes This manual may not be copied by any means without the express written permission of FUJITSU LIMITED. FUJITSU LIMITED reserves the right to make changes to this manual without prior notice. All Rights Reserved, Copyright © FUJITSU LIMITED 2005-2009...
-
Page 5: Table Of Contents
Contents Chapter 1 Notes after the Installation ........................1 PRIMEPOWER - Specific Notes.............................1 1.1.1 Modifications of Solaris OS (Patches, PTF, Program Local Fix)................1 1.1.2 Changing the date and time............................1 1.1.3 Serial port.................................1 1.1.3.1 PRIMEPOWER800/1000/2000..........................1 1.1.3.2 PRIMEPOWER900/1500/2500..........................1 1.1.4 Gigabit Ethernet port on PRIMEPOWER250/450 ....................2 1.1.5 Fibre Channel Cards (PW008FC3, PW008FC2 or GP7B8FC1) ................2 1.1.6... - Page 6 4.3.2.6 Configuring VLAN interface ..........................24 4.3.2.6.1 IEEE 802.1Q TagVLAN ..........................24 4.3.2.6.2 How to create the VLAN interface ......................25 Messages..................................26 Using GigabitEthernet on a Cluster System........................28 4.5.1 Support for Cluster System ............................28 4.5.2 Cluster Environment Setup Procedure ........................29 4.5.3 Notes in Cluster Environment ..........................29 Chapter 5 Precautions............................31 Limitations and known bugs for Solaris.........................31...
-
Page 7: Chapter 1 Notes After The Installation
1.1.1 Modifications of Solaris OS (Patches, PTF, Program Local Fix) Only the modifications (patches, PTF, Program Local Fix, etc.) for PRIMEPOWER provided by FUJITSU LIMITED can be applied to existing PRIMEPOWER systems running Solaris OS software. Do not use patches provided by Sun Microsystems, Inc. on the World Wide Web or those provided by other vendors. -
Page 8: Gigabit Ethernet Port On Primepower250/450
Install the driver again after an update of Solaris 10. For more detailed information, refer to "FUJITSU PCI Fibre Channel 3.0 Installation Guide" that is provided with the driver CD-ROM or the page described above. 1.1.6 Time for booting Solaris When booting Solaris 10 10/08 or later from Solaris CD/DVD or from the network via network instances such as hme/qfe, it may take more time (approx. -
Page 9: Solaris Os - Notes And Bug Information
Also, the following messages are stored many times in XSCF log, too. The error messages can be ignored safely. SCF> show-error-logs <Return> ***** No.01/32 Date = 2008/09/16 09:47:00 SysDamage = ALARM(STOP) FaultDetect = OBP FaultCode = 260000FF DetailInfo = [BOOTB]Boot Block error ReplaceParts= --- Syslog msg = Detected hardware error 30C97830 260000FF 08071523 3615FFFF... - Page 10 PRIMEPOWER 200/400/600 Set the MODE switch on the operation panel of the system to "SECURE" mode. Set OBP command (PROM command) to disable a Break signal. For more detailed information, refer to "PRIMEPOWER USER'S MANUAL." PRIMEPOWER 250/450/650/850/800/900/1000/1500/2000/2500 Set the MODE switch on the operation panel of the system to "LOCK" mode. Set OBP command (PROM command) to disable a Break signal.
-
Page 11: Notes On Pci Cards
Press the Eject button on the diskette drive unit, then eject the diskette. WARNING messages of se driver When a serial port receives a lot of data, such as when a large amount of text is pasted on a console screen connected to a serial port, the console message "seN: Buffer overrun"... -
Page 12: Setting Up Primepower Mib Information
Sun SNMP Agent, After modification: sysdescr Fujitsu SNMP Agent, model_name Write the model name displayed in the step 3, in the place of “model_name”. You can customize the above sysdescr string the way you like. But some network management software... -
Page 13: Other Notes And Bug Information
Restart the Solstice Enterprise Agent (SEA) daemon. # /etc/init.d/init.snmpdx start<Return> 1.2.5 Other notes and bug information For other notes and bug information during the system operation, refer to the following document: "Solaris 10 Release Notes " Unsupported Features The following features described in Solaris OS manuals are not supported. Table 1.1 Unsupported features Description Alternative method... -
Page 15: Chapter 2 Backup And Restore Of System Disk (Primepower1/200/250/400/450/600/650/850)
Chapter 2 Backup and Restore of System Disk (PRIMEPOWER1/200/250/400/450/600/65 0/850) This chapter explains the procedures to backup/restore the disk (hereafter called, the system disk) containing the Solaris OS software. Types of Backup Procedures Backup of the system disk requires that the disk and slices to be backed up not be in use. The system disk contains file systems (such as the root (/) file system) that cannot be unmounted. -
Page 16: Backup And Restore Of File System Unit
If you are restoring, use the dd(1M) command after booting from the Solaris OS CD/DVD to restore the slice unit. If you back up slice 0, it will only be possible to restore to a disk having the same physical properties (disk space, number of cylinders) as the original. -
Page 17: Restore Of File System Unit
ok boot -s <Return> Backup the file system with the ufsdump(1M) command. Example: Backup to the "/dev/rmt/0." # ufsdump 0ucf /dev/rmt/0 / <Return> 2.2.2 Restore of File System Unit When restoring the file system unit, the Solaris OS is booted from the Solaris 10 CD1 or Solaris 10 DVD. After booting Solaris OS, mount the disk to be restored temporarily, and then restore the file system unit. -
Page 18: Backup And Restore Of Disk Unit
/dev/rdsk/c0t0d0s0. Backup and Restore of Disk Unit When backing up a disk unit, use the dd(1M) command. The following describes how to back up a disk unit to a tape device using the dd(1M) command. The backup records physical properties such as disk space and a number of cylinders, so it is only possible to restore to a disk having the same physical properties. -
Page 19: Chapter 3 Backup And Restore Of System Disk (Primepower800/900/1000/1500/2000/2500)
Chapter 3 Backup and Restore of System Disk (PRIMEPOWER800/900/1000/1500/2000/2 500) This chapter explains the procedures to backup/restore the disk (hereafter called, the system disk) containing the Solaris OS software. Types of Backup Procedures Backup of the system disk requires that the disk and slices being backed up not be in use. The system disk contains file systems (such as the root (/) file system) that cannot be dismounted. - Page 20 restore the slice unit. If you back up slice 0, it will only be possible to restore to a disk having the same physical properties (such as disk space and a number of cylinders) as the original. Disk partition information such as the size of each slice will not be backed up. You must record the information separately.
-
Page 21: Chapter 4 Secondary Lan Port On Primepower250/450
PRIMEPOWER250/450 This chapter describes how to use the secondary LAN (10/100/1000Mbps) port on PRIMEPOWER250/450. Outline The secondary LAN port on PRIMEPOWER250/450 is controlled by FUJITSU PCI Gigabit Ethernet Driver (Interface name is “fjgi”) included in Solaris 10. Notes When using 1000 Mbps communication, be sure to set Autonegation to 'on'. -
Page 22: Defining Hostname
Example /etc/hostname6.fjgi*: Define the unique hostname (This sample named giga-v6): addif giga-v6/120 up Note: If you defined the hostname in hostname.fjgi* file, see the section "4.3.1.2 Defining Hostname" for detailed information. To use the GigabitEthernet as an VLAN interface: See "4.3.2.6 Configuring VLAN interface", and after defining VLAN name, proceed with above 1 or 2 procedure. - Page 23 Table 4.1 Parameters List Parameter Value Description name fjgi When using PRIMEPOWER250/450 secondary LAN port, please set name="fjgi". FJSV,pgtb When using PCI card PW008GE5, please set name="FJSV,pgtb". FJSV,pgsb When using PCI card PW008GE4, please set name="FJSV,pgsb". parent Please refer to “4.3.2.1.2 How to Set The location of the device node in a Parameter”.
-
Page 24: How To Set Parameter
Parameter Value Description Role_A Auto (Default) Auto select Master or Slave by the partner. (This can be set when AutoNegotiation_A= On.) Master Communicate by Master. Slave Communicate by Slave. 4.3.2.1.2 How to Set Parameter The method of setting up of each parameter of the secondary LAN port (FJSV,pwga) shown in Table 4.1 is explained. -
Page 25: To Use Ndd(1M) Utility
If you set a JumboFrame, it will be unable to transmit and receive the data of IEEE802.3 form. If you use two or more cards, or VLAN interfaces, enabling JumboFrame function becomes effective to all cards and all interfaces. When you perform file transfer by FTP, please set MTU size to less than 8232byte. Please use Jumbo Frames function only in 1000 Mbps communication. - Page 26 Parameter Status Meaning flow_control Read only 0 : None (Not doing flow_control) 1 : LocSend (Can transmit pause frame only) 2 : Rem (Can receive pause frame only) 3 : Sym (Can receive and transmit pause frame) cardtype Read only 0 : SX(PW008GE4) 1 : T(PRIMEPOWER250/450 secondary LAN port,...
- Page 27 Parameter Status Meaning lp_10hdx_cap Read only Setting of link-partner 10Mbps/HalfDuplex, when link up with AutoNegotiation. 0 : Invalid 1 : Valid lp_100fdx_cap Read only Setting of link-partner 100Mbps/FullDuplex, when link up with AutoNegotiation. 0 : Invalid 1 : Valid lp_100hdx_cap Read only Setting of link-partner 100Mbps/HalfDuplex, when link up...
-
Page 28: Changing The Setting Of Fcode
If you execute ndd command repeatedly, fjgi interface performance may drop. The values of link_speed, link_mode, autonego, flow_control are effective, only when link_status = 1. If link_status = 0, these values are invalid. The values of lp_10fdx_cap, lp_10hdx_cap, lp_100fdx_cap, lp_100hdx_cap, lp_1000fdx_cap, lp_1000hdx_cap, lp_pauseTX, lp_pauseRX,... -
Page 29: Network Install
ok cd /pci@83,2000/FJSV,pwga@1 <Return> ok .prp <Return> role slave duplex half transfer-speed 0000000a cabinet-name Cabinet#0 board-name Motherboard#1 assigned-addresses 83002810 00000000 00100000 00000000 00010000 82002830 00000000 00110000 00000000 00010000 *1: Appears only when slave-mode is set. *2: Appears only when half-duplex is set. *3: Appears only when transfer-speed is set. -
Page 30: Configuring Vlan Interface
Search the device path to the secondary LAN port with a show-nets command from ok prompt of a client system. ok show-nets <Return> Example ok show-nets a) /pci@83,2000/FJSV,pwga@1 b) /pci@1f,4000/FJSV,pgsb@4 q) NO SELECTION Enter Selection, q to quit: From ok prompt of a client system, please start a client system using the secondary LAN port. ok boot /pci@83,2000/FJSV,pwga@1 <Return>... -
Page 31: How To Create The Vlan Interface
- No TagVLAN - With TagVLAN PRIMEPOWER PRIMEPOWER fjgi0 fjgi1 fjgi1000 fjgi2000 X.X.1.1 X.X.2.1 X.X.1.1 X.X.2.1 Secondary LAN NIC secondary LAN LAN Switch LAN Switch To X.X.1.X To X.X.2.X To X.X.1.X To X.X.2.X network network network network (netmask: 255.255.255.0 ) Figure 4.1 Example of VLAN environment By using VLAN, traffic management of two or more networks by the single physical interface can be done. -
Page 32: Messages
protocol. Since PRIMECLUSTER GLS 4.1A20 or previous version do not correspond to a VLAN interface, please do not use VLAN interface with those. PRIMECLUSTER GLS 4.1A30 or later (only Fast switching mode or NIC switching mode) can use VLAN interface. VLAN function can be used only in Solaris 8, Solaris 9 or Solaris 10. - Page 33 Message Cause Workaround -role master: Communicate as Master. slave: Communicate as Slave. Illegal value for Error found in the parameter of Check whether the definition file is [ParameterName]. definition file (fjgi.conf). correct. fail to FragCount Abnormalities were found in message fragmentation.
-
Page 34: Using Gigabitethernet On A Cluster System
Message Cause Workaround fjgi_board_init_mem: DMA resources cannot be allocated. Failed to dma_alloc !! statistick block can't alloced!! hwmib block can't alloced Statistic information resources handle! couldn't be allocated. hwmib block can't bind handle! fjgi_board_init_mem: DMA resources cannot be allocated. Failed to dma alloc2!! Illegal value for The value of LinkSpeed_A of a Please set a right value of... -
Page 35: Cluster Environment Setup Procedure
1:n operation standby mode Mutual standby mode TCP/IP communication Using to the cluster interconnect (PRIMECLUSTER). (But, using in a JumboFrame or as VLAN interface can not be performed) The support ranges of takeover form are the following ranges. PRIMECLUSTER Taking over form Support Support Not Supported... -
Page 37: Chapter 5 Precautions
Chapter 5 Precautions This chapter explains necessary precautions. Limitations and known bugs for Solaris This chapter explains limitations and known bugs for Solaris. Table 5.1 Limitations and known bugs for Solaris Limitations and known bugs Remarks Recommended actions The following patches are required to be installed in the following order after installation Solaris 10 of Solaris 10. - Page 38 Limitations and known bugs Remarks Recommended actions For growfs(1M), the following patch is required to be installed. Solaris 10 120254-02 or later SunOS 5.10: ufs Patch 3/05 and Install the above patches. 1/06 only When using any of the following PGX cards and monitors, the display monitor does not Solaris 10 enter standby mode if you haven’t logged on from CDE (Common Desktop 3/05 only...
- Page 39 Limitations and known bugs Remarks Recommended actions Solaris Live Upgrade is not supported with RAID-1(mirror) Custom Jumpstart installation for mirror volumes using a profile that has filesys keyword of both original and target disk, will fail and the following error message will be shown at first boot after the installation.
- Page 40 Limitations and known bugs Remarks Recommended actions Follow these instructions to remove a package. (For example SUNWabc) Re-install the package to system. # pkgadd SUNWabc Find out path name of SMF service manifest in the package. # grep SUNWabc /var/sadm/install/contents | \ grep /var/svc/manifest | awk '{ print $1 }' | grep xml /var/svc/manifest/system/abc.xml Run the following command.
- Page 41 Limitations and known bugs Remarks Recommended actions "Internet (IP) Address” in “Workstation information” of CDE environment is shown Solaris 10 with a IPv6 unicast address as “::FFFF:***.***.***.***”. 3/05 only This problem is solved by the following patch. 119284-01 or later CDE 1.6: sdtwsinfo patch During system shutdown, some messages similar to the following might be displayed on the console.
- Page 42 Limitations and known bugs Remarks Recommended actions There are some differences in behavior of MIB between SNMP agents of SMA and SEA. sysObjectID (MIB to show system device type) SEA shows the value as “enterprises.42.2.1.1”, however, SMA shows the value as “netSnmpAgentOIDs.3”.
- Page 43 Limitations and known bugs Remarks Recommended actions A /noautoshutdown file might be created at first boot after Solaris 10 installation. If /noautoshutdown file exists power management and power saving could be disabled. Check for and remove /noautoshutdown file if you need to enable power management and power saving features.
- Page 44 SOURCE: cpumem-diagnosis, REV: 1.3 EVENT-ID: aaf47b25-cfd2-4984-f598-e81bcbba274f DESC: The number of single bit errors associated with this memory module continues to exceed acceptable levels. Refer to http://www.fujitsu.com/global/services/computing/server/unix/prmpwr_msg/SUN4US -8000-7D for more information. AUTO-RESPONSE: An attempt will be made to remove this memory page from service.
- Page 45 Limitations and known bugs Remarks Recommended actions The -R option for pkgadd(1M), pkgrm(1M), patchadd (1M), and patchrm(1M) utilities Solaris 10 have limitations when zones are included in the remote target image. 3/05 only When a package and/or patch needs to be removed from non-global zone, install the following patch before patch/package removal.
-
Page 46: Specification And Incompatibility For Solaris
Limitations and known bugs Remarks Recommended actions I Installation and removal of a package or patch may fail in a system with non-global zones, under the following conditions. non-global zone is configured using zonecfg(1M), but not installed by zoneadm(1M). non-global zone is just booted by zoneadm(1M) after installation, without any non-global zone settings such as host name and root password. - Page 47 Specification and incompatibility Remarks Recommended actions nslookup(1M) results on Solaris 10 differ from those of Solaris 9 or older versions. e.g.) Solaris 9 # nslookup > aaa213.sample.test.com. Server: aaat11.sample.test.com Address: xxx.xxx.xxx.nnn Name: aaa13.sample.test.com Address: xxx.xxx.xxx.mmm Aliases: aaa213.sample.test.com, aaa113.sample.test.com Solaris 10 # nslookup >...
- Page 48 Specification and incompatibility Remarks Recommended actions The following messages may be displayed during patch installation using patchadd(1M). Package {PKGNAME} from directory {PKGNAME} in patch {PATCHID} is not installed on the system. Architecture for package {PKGNAME} from directory {PKGNAME} in patch {PATCHID} differs from the package installed on the system.
- Page 49 Specification and incompatibility Remarks Recommended actions In Solaris10, rsh(1) will output messages according to the value of the LANG variable that is defined in /etc/default/init. However, in the previous Solaris versions, the system will use the LANG=C locale for a command, that is run at the server side by rsh(1), without mentioning any specific value for the LANG variable.