B23Q8YA-G-02-F PRIMEPOWER Hardware Platform Guide: Operation for Solaris™ 10 Operating System -- Start Here--
4 PRIMEPOWER 200/400/600 z Set the MODE switch on the operation panel of the system to "SECURE" mode. z Set OBP command (PROM command
5 7. 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
6 7. Enter the Open Boot Environment. Some of the manuals attached to the card may instruct "Reboot your machine", which means to ente
7 5. Restart the Solstice Enterprise Agent (SEA) daemon. # /etc/init.d/init.snmpdx start<Return> 1.2.5 Other notes and bug information F
8
9 Chapter 2 Backup and Restore of System Disk (PRIMEPOWER1/200/250/400/450/600/650/850) This chapter explains the procedures to backup/restore t
10 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
11 ok boot -s <Return> 2. Backup the file system with the ufsdump(1M) command. Example: Backup to the "/dev/rmt/0." # ufsdump 0u
12 /dev/rdsk/c0t0d0s0. 2.3 Backup and Restore of Disk Unit When backing up a disk unit, use the dd(1M) command. The following describes how to
13 Chapter 3 Backup and Restore of System Disk (PRIMEPOWER800/900/1000/1500/2000/2500) This chapter explains the procedures to backup/restore th
14 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
15 Chapter 4 Secondary LAN port on PRIMEPOWER250/450 This chapter describes how to use the secondary LAN (10/100/1000Mbps) port on PRIMEPOWER250
16 Example /etc/hostname6.fjgi*: Define the unique hostname (This sample named giga-v6): addif giga-v6/120 up Note: If you defined the hostname
17 Table 4.1 Parameters List Parameter Value Description fjgi When using PRIMEPOWER250/450 secondary LAN port, please set name="fjgi"
18 Parameter Value Description Auto (Default) Auto select Master or Slave by the partner. (This can be set when AutoNegotiation_A= On.) Master
19 - 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 i
20 Parameter Status Meaning flow_control Read only 0 : None (Not doing flow_control) 1 : LocSend (Can transmit pause frame only) 2 : Rem (Can
21 Parameter Status Meaning lp_10hdx_cap Read only Setting of link-partner 10Mbps/HalfDuplex, when link up with AutoNegotiation. 0 : Invalid 1
22 - If you execute ndd command repeatedly, fjgi interface performance may drop. - The values of link_speed, link_mode, autonego, flow_contro
23 ok cd /pci@83,2000/FJSV,pwga@1 <Return> ok .prp <Return> role slave *1 duplex ha
1 Preface Solaris™ Operating System is described as Solaris in this manual. Purpose This manual provides notes necessary after installing the Sola
24 ok 4. 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&g
Figure 4.1 Example of VLAN environment By using VLAN, traffic management of two or more networks by
26 protocol. z Since PRIMECLUSTER GLS 4.1A20 or previous version do not correspond to a VLAN interface, please do not use VLAN interface with th
27 Message Cause Workaround -role master: Communicate as Master. slave: Communicate as Slave. Illegal value for [ParameterName]. Error found i
28 Message Cause Workaround fjgi_board_init_mem: Failed to dma_alloc !! DMA resources cannot be allocated. statistick block can't alloced!!
29 z 1:n operation standby mode z Mutual standby mode z TCP/IP communication z Using to the cluster interconnect (PRIMECLUSTER). (But,
30
31 Chapter 5 Precautions This chapter explains necessary precautions. 5.1 Limitations and known bugs for Solaris This chapter explains limitat
32 Limitations and known bugs No Recommended actions Remarks For growfs(1M), the following patch is required to be installed. 120254-02 or later
33 Limitations and known bugs No Recommended actions Remarks Solaris Live Upgrade is not supported with RAID-1(mirror) Custom Jumpstart insta
2 All other products or company names mentioned in this document are claimed as trademark and trade names by their respective companies. March, 2
34 Limitations and known bugs No Recommended actions Remarks Follow these instructions to remove a package. (For example SUNWabc) 1) Re-instal
35 Limitations and known bugs No Recommended actions Remarks "Internet (IP) Address” in “Workstation information” of CDE environment is show
36 Limitations and known bugs No Recommended actions Remarks There are some differences in behavior of MIB between SNMP agents of SMA and SEA. z
37 Limitations and known bugs No Recommended actions Remarks A /noautoshutdown file might be created at first boot after Solaris 10 installation.
38 Limitations and known bugs No Recommended actions Remarks On PRIMEPOWER 200 (360MHz or higher) / 400(360MHz or higher)/600/650(except SPARC64
39 Limitations and known bugs No Recommended actions Remarks The -R option for pkgadd(1M), pkgrm(1M), patchadd (1M), and patchrm(1M) utilities ha
40 Limitations and known bugs No Recommended actions Remarks I Installation and removal of a package or patch may fail in a system with non-globa
41 Specification and incompatibility No Recommended actions Remarks 4 nslookup(1M) results on Solaris 10 differ from those of Solaris 9 or older
42 Specification and incompatibility No Recommended actions Remarks The following messages may be displayed during patch installation using patch
43 Specification and incompatibility No Recommended actions Remarks In Solaris10, rsh(1) will output messages according to the value of the LANG
i Contents Chapter 1 Notes after the Installation ...
44
ii 4.3.2.6 Configuring VLAN interface...
1 Chapter 1 Notes after the Installation This chapter describes the post-installation notes. 1.1 PRIMEPOWER - Specific Notes 1.1.1 Modificatio
2 - /dev/term/fa000, fa001, ... - /dev/cua/fa000, fa001, ... - /dev/se_hdlc0, se_hdlc1, ... Because the number of this device name is allocate
3 Also, the following messages are stored many times in XSCF log, too. The error messages can be ignored safely. SCF> show-error-logs <Ret
Comentarios a estos manuales