HP 8/20q HP StorageWorks Simple SAN Connection Manager User Guide (5697-0633, - Page 144
Symptoms, Solution, memory for [HOST, SWITCH
View all HP 8/20q manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 144 highlights
During a server, switch, or storage refresh, I receive an error message similar to the following: The shared memory for [HOST, SWITCH, or VDS] objects is full. Please consult the user's guide to increase the size of the shared memory and reboot the system for the changes to take effect. Symptoms: When you have a very large SAN, the object database allocated in memory is not large enough to support the contents of the entire database. A user usually receives this message when adding a new device to an already massive SAN or by having an extremely large number of LUNs. Solution: For the message that states HOST objects are full, open the following file using a text editor on your management station only: C:\Program Files\QLogic Corporation\RemotePartition\host_config.xml For the message that states SWITCH objects are full, open the following file using a text editor on your management station only: C:\Program Files\QLogic Corporation\RemotePartition\switch_config.xml For the message that states STORAGE or VDS objects are full, open the following file using a text editor on your management station only: C:\Program Files\QLogic Corporation\RemotePartition\vds_config.xml Search for the XML node called memory (in bold), which looks like the following: 3600000 16777216 1 This value represents the memory size to be used for the database. Replace the value with a larger numeric value than what is currently set. HP recommends that you find the current value in the list below and then use the next largest value as your new value. The following values are recommended: • 16777216 • 33554432 • 67108864 • 134217728 Using the XML above as an example, the next largest value would be 33554432 and the new contents of the file would look like the following: 3600000 33554432 1 Save the changes to the XML file and then reboot the management station. SSCM will now start normally with a larger database size in memory. 144 Troubleshooting