FUJITSU PCI Fibre Channel Update2. Update Information. for Solaris (TM) Operating Environment -

Transcription

1 FUJITSU PCI Fibre Channel Update2 Update Information for Solaris (TM) Operating Environment -

2 Contents Chapter 1 New Feature...1 Chapter 2 Modification...3 i

3 ii

4 Chapter 1 New Feature The following table 1.1 defines new features added to the software of the previous version levels. [Table 1.1] Number Version Level New Feature Name Solaris 7 support 2 GP7000F model 1000, 2000 support Description Drivers that works on the 64-bit kernel of Solaris 7 are added. Driver supports the High-Reliability driver I/F of FUJITSU GP7000F model 1000, Solaris 8 support Driver supports Solaris Fabric Support Driver supports Fabric. Only class 3 is supported. 5 Function for clustered system of hot device replacement support 6 Dynamic Reconfiugration support Driver supports the function to execute the exchange of the fibre channel device to all nodes of the clustered system. Supported of Dynamic Reconfiguration for GP7000F M1000/2000 and PRIMEPOWER 800/1000/2000(*1). (*1)Please confirm the shipment time of Solaris8(for PRIMEPOWER 800/1000/2000) to sales in charge of our company. 7 Fibre Channel Tape support Driver supports Fibre channel Tape equipment ( ) Update1 Update2 1Gbps/2Gbps Fibre Channel card(pw008fc2u or PW008FC2X) support Command for hot target device addition supported HBAAPI. Support HBAAPI Support. Solaris 9 9/04 OE support 1Gbps/2Gbps Fibre Channel card(pw008fc3u or PW008FC3X) support Driver supports 2Gbps Fibre channel card(pw008fc2u or PW008FC2X). You can add target device dynamically without DR. Renewal of installer for Solaris 9 9/04 OE. support.. Driver supports new 2Gbps Fibre channel card(pw008fc3u or PW008FC3X). 1

5 2

6 Chapter 2 Modification Bugs found in the software of the previous version levels are fixed. See the following table for the details of the bugs and P-number. [Table ] Number Version Level P-number 1.1 ( ) PE12729 Bug Timeout message from the disk driver might be displayed under the following 1. Using GP7B8FC1U as a HBA(Host Bus Adapter), and 2. Connecting more than 2 target devices to the adapter, and 3. Issueing more than 255 I/O commands to each target. 1.1 ( ) PE12743 Panic might occur under the following 1. When using RAID device via Fibre Channel(GP7B8FC1U). 1.1 ( ) PE ( ) PE ( ) PE12948 Panic which displays the message "mutex_exit:not owner" might occur under the following 1. Connecting RAID(or disk) devices other than GP-DxxF2x or GR700 series. Fibre Channel adapters other than GP7B8FC1U might not be able to coexist with GP7B8FC1U. 1. When you installed FUJITSU PCI Fibre Channel 1.0 Chgfcctl command displays the message; "chgfcctl: specified disk is used by other process.", and aborts under the following 1. When you use the Multipath disk control software. A panic whose message is "recursive mutex_enter" occures under the following 1. Using GP7B8FC1U Fibre Channel adapter and it receives one of the following extended link service command PE RES(Read Exchange Status Block) - RSS(Read Sequence Status Block) - RTV(Read Timeout Value) - RLS(Read Link Status Block) - ECHO(Echo) - TEST(Test) 7 ( ) P A panic occures under the following 1. When I/O completion and abort request collides ( ) PE13138 A panic with "assertion failed:!(path->path_wait_flag & WAIT_FCPH_CALBACK)" occurs under the following 1. You are using RAID heavily, and 2. When you disconnect the optical fibre from a GP7B8FC1U or a RAID. ( ) PE13421 A garbage is contained in DF_CTL field under the following 1. When GP7B8FC1U receives LOGO command and responds to this command. ( ) PE13428 A panic at "fcph_rem_que+0x10" occurs uner the following 1. When you use GP7B8FC1U. Especially, when you disconnect the optical fibre. ( ) PE13482 A I/O won't complete and a message "scsi command abort(abts) timeout" is logged to /var/adm/messages. 1. When you use GP7B8FC1U, and 2. When you disconnect the optical fiber while I/O is running. You might see a message "no memory for disk label" under the following ( ) PE When you use GP7B8FC1U, and 2. When you connect a RAID that has many logical units. ( ) PE14218 You can't get a panic dump under the following 1. When you are going to dump to a device that is connected via GP7B8FC1U. 14 PE14223 A panic with "bad mutex" will occur under the following 3

7 ( ) 1. When you use GP7B8FC1U, and 2. Extended Link service transmission failure and its timeout collides..1 ( ) P ( ) PE ( ) PE14733 ( ) PG00668 ( ) PG00671 ( ) ( ) PG00817 ( ) PG00872 ( ) PG00942 ( ) PG00943 A message "unix: warning: interrupt level x not serviced." is sometimes displayed under the following 1. When you use GP7B8FC1U, and 2. I/O load is very heavy. A panic with "assertion failed: fcph_exp->fc_ex_mng.reserve[0]" might occur under the following 1. When you use GP7B8FC1U, and 2. Memory lack occurs when scsi_init_pkt() is called. A message "unix: warning: interrupt level 4 not serviced." may be displayed for the following conditions: 1. with the use of GP7B8FC1U, and 2. the SCSI Reset command is issued in command processing by SCSI target driver. A message "received short frame", "link down" may be displayed for the following conditions: 1. connected Arbitrated loop topology, and 2. I/O load is very heavy. A message "scsi command timeout" may be displayed for the following conditions: 1. When two or more GP7B8FC1U access to one RAID controller, and 2. I/O load is very heavy, and 3. response speed of the RAID controller declines for a heavy load. PG00672 Added the function to emulate the behavior when disabled Auto request sence. Panic might occur under the following 1. many logical unit is defined, and 2. when hard error and link error occur. It cannot detected the target device for the following 1. connected with fabric, and 2. when you set domain ID of fabric(fibre channel switch) to 128 or more. Panic might occur under the following 1. Two target devices or more are connected with GP7B8FC1U I/O commands or more are sent from GP7B8FC1U at the same time. 3. when it causes Linkdown by the cable pulling out etc. I/O commands might kept stopping under the following 1. Two target devices or more are connected with GP7B8FC1U I/O commands or more are sent from GP7B8FC1U at the same time. 3. when it causes Linkdown by the cable pulling out etc. ( ) P GP7B8FC1U can't find some LUs of the RAID system under the following 1. If boot device is a non-scsi one(ssa, IDE etc.) 26 PG ( ) PG02332 ( ) PG02522 ( ) PG02523 I/O commands might kept stoppoing under the following 1. A number of logical unit are defined. 2. When scsi_reset(9f) is executed all of them. The port property definition for instance 0, 9, 19, in /kernel/drv/fjpfca.conf dosen't work. Such adapter works as auto negotiation mode. 1. Adapter's instance 0, 9, 10, 19, 's port property is defined. The targets that target id is 15(0xf),31(0x1f),47(0x2f)... are not detected by GP7B8FC1U. 1. If "Disable device probing Option"(SN200's configuration option) is set "0". The host might be hung under the following 1. GP7B8FC1U detects Extended Link Service exchange timeout,then driver frees Fibre Channel resouces ( i.e. exchange id, sequence id ) after R_A_TOV past. 2. If GP7B8FC1U sends an exchange to name server of SN200 at the same time. ( ) PG03274 I/O commands might kept stoppoing under the following 1. The disk Array has so many LUs. 4

8 When disk array responses a NOT READY sense(2/4/1). ( ) PG03276 Time for path fail over is too long under the following 1. A persistent link down condition is occur. ( ) PG03491 ( ) P ( ) P ( ) P ( ) A fiber channel link is not up under the following 1. GP7B8FC1U connects with SN SN200's power switch off and on with fibre channel cable puluged in. A panic whose message is "mutex_enter: bad_mutex" occur under the following 1. When LU liberation processing. A panic whose message is "mutex_enter: bad_mutex" occur under the following 1. When LU liberation processing was done. A panic with Illegal area access will occur under the following 1. By point-to-point(nport) connection, not to go by way of a fiber channel switch, and 2. When connected directly with a disk array device / FC tape device. PG04429 When bootstraps, some LUs might not be recognized by GP7B8FC1U. ( ) PG04454 When you disconnect system board, panic might be happen with the messages "mutex enter: bad mutex" ) ( ) PG04857 ( ) PG05497 When linkdown occur frequently in Arbitrated loop topology, GP7B8FC1U might not detect targets. PG04859 Supports the lus driver of Legato's Networker If driver can't recognize target for a few minutes and scsi_reset(9f) command execute it's device, but open(3c) system call to it's target must be succeeded before target has been lost, system might be hung.. ( ) PG05863 When reconfigure boot straps( i.e. boot -r ). panic might be happen with the messages "assertion failed: failover_timer_inactive(port)". ( ) PG05864 When GP7B8FC1U connected with SN200 and linkdown occur frequently, panic might be happen. ( ) ( ) ( ) ( ) ( ) PG05865 If scsi_abort(9f) call from upper layer driver, panic might be happen. PG06484 Even if the target disappears without RSCN, improve elapsed time of path fail over. PG06485 E_D_TOV is changed to 2000ms in private loop environment. PG07155 When ABTS is received to I/O under execution, I/O may not return. PG07223 Freezing Timeout value changed to 20sec. ( ) PG07373 When the information on the target which does not exist in NameServer remains, I/O to the target may not return. ( ) PG07506 If I/O command executes at the same time scsi_reset(9f) return to thr ULP driver(e.g sd), I/O to the target may not return. 50 PG07556 When LOGO received from target, stop transmit ABTS concerned with active exchange. 5

9 ( ) ( ) PG10199 When GP7B8FC1U receives FCP_XFER_RDY frame with burst_len field error,driver may detect this error quickly. ( ) PG11072 Driver supports RSCN(Remote node Status Change Notification) address format 3. ( ) PG11073 When boot straps, Added the function to disable to display A message "Link Failure Cable Probrem?". ( ) PG11074 ( ) PG11080 ( ) PG11802 Panic might occur under the following 1. connected with fabric, and 2. linkdown occur when GP7B8FC1U send fibre channel frames to fabric's Name server. I/O commands might end immidiately in error under the following 1. scsi_reset(9f) is executed, and 2. linkdown occur. Driver can't be recognized target which was hot device replacement before in under the following 1. You use PRIMEPOWER M1000, M2000, and 2. You bind the target-id and WWN(as fcp-bind-target in fjpfca.conf), and 3. You execute hot device replacement of fibre channel device(chgfcctl or clchgfc), and 4. System is not rebooting, and 5. You disconnect system board with GP7B8FC1, and connect that. ( ) PG11803 If you execute hot device replacement of fibre channel device in I/O under execution, panic might be happen. ( ) PG11811 Installing driver is failed with messages "System configuration files modified but fjpfca driver not loaded or attached.", because of DMA attribute setting failure. ( ) PG11910 ( ) PG13393 ( ) PG14623 A message "panic[cpuxx]/thread=xxxxxxxx: assertion failed: failover_timer_inactive(port), file: fcp_port.c, line: XXX" is displayed and panic occur under the following condition. 1. Within 30 second from the target was disappeared because of failure. 2. If you execute hot deveice replacement of fibre channel device. A panic occur under the following 1. When an adapter reset command (fc_adm-r fjpfcax) is executed during access to disk array device and tape device, and 2. When a PCI system error occurs. I/O may remain suspended and I/O processing hung-up may occur under the following 1. The disk array device that target ID is more than 16 exists, and 2. When I/O access is received during poll processing of reset etc. ( ) PG15531 Display a message of scsi command (abts) timeout, and there is the case that I/O does not return to. ( ) PG15533 A panic with Illegal area access will occur under the following 1. In detach processing movement of a driver. ( ) PG15534 ( ) PG15536 ( ) PG15537 I/O in execution can be continued under the following 1. Connected to a fiber channel switch, and 2. When divided zone during I/O execution. Added the function which is not accessed by judging an I/O device to be unusual and changing into a blockade state When a demand of inaccurate data transmission length is received among I/O A panic whose message is "assersion fail:!(fcph_seqp->status & FCPH_SEQ_STATUS_ABTS_SR)" occur under the following 1. Between I/O, received ABTS. 6

10 ( ) ( ) ( ) PG15578 PG15576 It supports I/O published with time-out un-specifying. PG15577 Do not reply to PDISC extended link service normally. A panic which illegal DMA address is assigned under the following 1. When it is used in Solaris 8 where SunOS 5.8 kernel update patch or subsequent ones is not applied. ( ) PG15707 Boot time can delay under the following 1. When set port property in "nport" and was connected to FC-HUB. ( ) PG16308 ( ) ( ) PG17136 ( ) PG17279 A panic occur under the following 1. Transmission channel abnormality occurs, and 2. When data were canceled. PG16309 Some device recognition can fail in boot. In 2G fiber channel card (PW008FC2) system panic or a system may incorrect-operate under the following 1. connect the disk array device / tape device which can communicate with 2Gbps, and 2. When the receiving buffer address specified by upper software is odd number byte boundary. Recognition processing of a target device under the following 1. When a state change notice for a target device occurred from FC-SWITCH continually. ( ) PG17280 In boot, succeed in recognition of a target device, but there can be a thing failing in recognition processing of LU ( ) PG17389 ( ) PG18200 Hard interrupt continues being notified of and can reach system hang under the following 1. When adapter reset processing was done. A panic by the or illegal area access how I/O does not return to can occur under the following 1. Connected to a fiber channel switch, and 2. When let a cable. ( ) PG18201 Don't Link Up in host boot under the following 1. When connected to a fiber channel switch. ( ) PG18812 Improve to write throughput of the case that used PW008FC2 with PRIMEPOWER1000/2000. ( ) PG19399 ( ) PG19708 ( ) PG20045 ( ) PG20440 New I/O does not return under the following 1. It is executed SCSI reset or SCSI abort, and 2. When new I/O was published during the processing. A panic occur under the following 1. Use fiber channel card (GP7B8FC1), and 2. When the state by a transmission channel obstacle normally, and do not link up continues it after boot for ten minutes. A panic with Illegal area access will occur under the following 1. In PW008FC2 use, and 2. In publication of mode sense command. Recognition processing can fail under the following 1. When, in system boot, LU recognition processing was executed just after initialization processing of a driver. ( ) PG22343 Disconnect processing of PHP/DR under the following 1. When disconnect fiber channel card (PW008FC2,GP7B8FC1) by PHP/DR. 7

11 85 86 ( ) PG22344 ( ) PG22431 A panic whose message is "mutex_enter: bad_mutex" occur under the following 1. When disconnect fiber channel card (PW008FC2,GP7B8FC1) by PHP/DR. A panic whose message is "Bus Timeout Event detected.." occur under the following 1. When disconnect fiber channel card (PW008FC2) by PHP/DR. In 2G fiber channel card (PW008FC2) system panic or a system may incorrect-operate under the following ( ) PG23323 ( ) PG23170 It supports HBAAPI. 1. connect the disk array device / tape device which can communicate with 2Gbps, and 2. When the receiving buffer address specified by upper software is odd number byte boundary. 3. When more data transmission to I/O is completed almost simultaneous. ( ) PG25029 a system panic and a hang phenomenon occur under the following 1. When scsi_abort(9f) was published in large quantities. ( ) PG25030 ( ) PG25031 Repeat link up and down with message is "Freezing Timeout.." display under the following 1. When transmission channel abnormality occurred. A system panic whose message is "assertion failed: (ex->cntl & FC_EX_CTL_IGNORE_TX) == 0" occur under the following 1. When transmission channel abnormality occurred. ( ) PG25163 I/O in execution can do hangup under the following 1. In the hard error occurrence. ( ) PG27875 Inprove to the return time of individual I/O when the clear demand of the I/O cue by scsi_abort (9F) carries out a timeout ( ) PG27876 Although there are no abnormalities in operation, the message of "WARNING interrupt level 6 not serviced" may be displayed under the following 1. At the time of command issue of pole, such as scsi_reset (9F). ( ) PG28745 Improve to the Clexecd is point which hangs-up and becomes heavy load in PCL and Safe cluster function standstill. ( ) ( ) PG30442 ( PG30441 It supports untagged-qing. PG32322 A system panic whose message is "assertion failed: dest->addr_info & FC_PORT_PORT_NAME, file: fcp_arp.c, line: XXX" occur under the following 1. In transmission channel abnormality. panic occurs on a system that LMF installed ( ) PG32706 Dynamic Reconfiguration/PCI Hot Plug might be failed during high performance I/O execution. ( ) ( ) ( ) PG32322 When disconnecting card(pw008fc2,gp7b8fc1) at DR/PHP, panic might be occur. PG32076 FcpGetTargetMapping HBAAPI function returns wrong information for FC Tape device. PG35915 Driver supports new 2Gbps Fibre channel card(pw008fc3u or PW008FC3X). 8

12 103 ( ) PG36017 A panic may occur when a system receive a fibre channel frame under shortage of system memory. 9

13 10