Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2362113.1
Update Date:2018-02-16
Keywords:

Solution Type  Problem Resolution Sure

Solution  2362113.1 :   VSM6 - IDR1626.1 Installation (can induce panic in VSM7)  


Related Items
  • StorageTek Virtual Storage Manager System 6 (VSM6)
  •  
  • StorageTek Virtual Storage Manager System 7 (VSM7)
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VSM6
  •  




Created from <SR 3-16644496691>

Applies to:

StorageTek Virtual Storage Manager System 6 (VSM6) - Version All Versions and later
StorageTek Virtual Storage Manager System 7 (VSM7) - Version 7.0.0 to 7.1.2 [Release 7.0]
Information in this document applies to any platform.

Symptoms

 VSM6 or VSM7 panic during the installation of IDR1626.1 on another VSM6 connected to the same FICON infrastructure.

Changes

 IDR1626.1 is being installed on a VSM6.

Cause

 There is a point in the VSM6 installation of IDR1626.1 where the machine does not know it is a VSM6. 
 During that time frame the VSM6 can generate unexpected RNID ELS events.  (RNID ELS = Request Node ID   Extended Link Services)
 If the FICON infrastructure is common to another VSM6 or VSM7 these RNID ELS events can cause the receiving machine to take a panic.

Solution

 Workaround:

 Completely isolate the VSM6 being upgraded with IDR1626.1 from the FICON infrastructure. 
 This can be done by blocking the switch ports going to the VSM6 being upgraded or by unplugging the FICON cables going to that machine.

 

 Fix:

 This problem is addressed in version 7.1.2.05.000 and higher levels of VSM6 and VSM7 code.

References

<BUG:27387024> - NODE KERNEL PANIC AND REBOOT - SUNOS-8000-KL

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback