| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||
Solution Type Problem Resolution Sure Solution 1011209.1 : Sun StorEdge[TM] 6960/6910: Unable to Add New Host/HBA to Vicom Router
PreviouslyPublishedAs 215401 Symptoms Unable to add new host/hba to Vicom router; showvemap or savevemap which are called from the menu interface (runsecfg) would fail abnormally with a core dumped due to slicview; running slicview command directly would exit with "segmentation fault" and core dumped. Resolution Root cause was due to exceeding the limit of 32 entries in host list (HBA entries) of Vicom router's (aka Virtualization Engine (ve)) database. Vicom router remembers everything ever connected to it in the desire to provide device persistence. However, there was no facility provided to remove unwanted entries, so the table will keep growing unless the entire database is wiped out and reset to factory default. One workaround therefore, is to backup all data, reset the Vicom database, then rebuild the entire configuration and restore. Note that lun slicing (vlun) is done at Vicom, and with no proven way to guarantee that re-creation of slice would result in the same boundaries for the vlun, as such, data will need to be restored after reset and rebuild. The alternative is to engage Vicom Systems, Inc's service to remove the unwanted entries without destroying the rest of the database. The process involves using unsupported procedures and is proprietary to Vicom. Product Sun StorageTek 6960 Sun StorageTek 6910 Internal Comments
Service Request ID: 10910634 As documented in bugid 4647274, it was thought that the limit of 32 would not be exceeded in a real production environment; it was understood that there is a need to allow removal of old and unwanted entries but the bug was filed as an RFE instead, which never made into release prior to the product being EOL. In the end, Vicom Systems Inc. was paid to provide the service to clear the entries using proprietary commands, and that was how this incident was resolved. 6960, 6910, indy, vicom, ve, virtualization engine, slicview, showvemap, savevemap Previously Published As 87717 Change History Date: 2006-11-20 User Name: 71396 Action: Approved Comment: Performed final review of article. Updating product name and trademarking. Publishing. Version: 3 Date: 2006-11-20 User Name: 71396 Action: Accept Comment: Version: 0 Date: 2006-11-20 User Name: 87977 Action: Approved Comment: Please send to final review Version: 0 Date: 2006-11-12 User Name: 87977 Action: Accept Comment: Version: 0 Date: 2006-11-12 User Name: 35753 Action: Approved Comment: Documenting what problem to expect when a Vicom's host list is fill up, and what are the possible resolutions. A customer hit this problem after years of using 6960. In this case it was preventing adding of host, but the same could occur if an hba failed and was replaced, therefore, new WWN, which means a new entry. The bug is known but was filed as RFE, arguably not, but given the status of Vicom, there is no point pursuing it since there will never be bug fixes. Version: 0 Date: 2006-11-10 User Name: 35753 Action: Migrated Comment: apollo 1-20530212 2006-11-09 Version: 0 Product_uuid 86b6cc47-00d7-43f1-8efd-81690a8d5b6f|Sun StorageTek 6960 681b08b4-d683-4f9e-b8ba-cbbb87b01d05|Sun StorageTek 6910 Attachments This solution has no attachment |
||||||||||||
|
||||||||||||