[ Contents
] [ Index ]
Selecting a Server to Manage a Controller
When you assign a server to manage a controller, information regarding the managing server is produced. SANscape stores this information on a controller and uses it to keep track of the managing server. In the event a server is shut down, for maintenance for example, and you try to assign another server to manage the controller, SANscape reads the stored server information from the controller and warns you that the controller is being managed already. You can view the managing server name by choosing the firmware application menu called view and edit Host luns > Edit Host-ID/WWN Name List. Refer to the SANnet II Family RAID Firmware User's Guide for your array for information about accessing the firmware application. If you want to change a server assignment, for example, because you are moving an array to a new location, before you move the array, you need to unassign the managing server following the steps in To Unassign the Managing Server. If you have already moved the array, when the array starts up, you might see a warning message that the controller is already being managed by another server. Because the "force" option doesn't unassign the agent of the original server, only override the current server assignment after you have unassigned the original managing server. If you do not manually unassign the original server, it continues to monitor and manage the unit along with the new server. After you have unassigned a server, you can also manually delete the server following the steps in To Manually Delete a Server Using the Terminal Window. Refer to the SANnet II Family RAID Firmware User's Guide for your array for information about accessing the firmware application. To Unassign the Managing Server
To Manually Delete a Server Using the Terminal Window Refer to the SANnet II Family RAID Firmware User's Guide for your array for information about accessing the firmware application.
|