Moves, Adds, and Changes Made Simple

Xsigo accelerates server I/O management, dramatically reducing the time required for routine server management tasks like these:

• Deploying a new server
• Migrating applications among servers
• Deploying new I/O to a server

Server Management Challenges

Server management tasks often become complex group efforts. The web of interdependencies between applications, server I/O, networking, and storage means that any change must be coordinated by at least three managers (server, storage, and networking). In larger data centers, additional managers (security, data backup, and change control) may be involved as well. To simply move an application from one server to another requires significant coordination.

Virtual I/O Streamlines Management

Xsigo accelerates server management in two ways:

• Virtual I/O: The Xsigo’s virtual NICs and virtual HBAs appear to applications and operating systems exactly as their physical counterparts.
• Persistent identities: Server I/O (vNICs and vHBAs) can be moved among servers without changing identitites (MAC addressed and WWNs), so changes to server I/O remain transparent to the network and storage.

Xsigo eliminates the fixed NICs and HBAs that tie applications to specific servers. Instead, the system uses virtual resources that can be deployed on the fly and transparently moved from server to server. I/O identities (down to the level of WWNs and MAC addresses) can be determined in advance and can remain persistent through a migration. The virtual resources and persistent identities accelerate common server management tasks.

Here are specific examples of how common data center tasks are simplified by using the Xsigo solution.

Example: Deploy a New Server

Without Xsigo	With Xsigo
Connectivity must be pre-planned and physically added to the server. All associated cabling must be planned and installed Each server has separate I/O attributes that must be reflected in the storage and network settings. Typical deployment time: weeks.	Connectivity is virtual and can be deployed to the server as needed. Simple cable planning. Cabling is identical for every server. Pre-assign storage. Network resources can be assigned for multiple servers at one time. The server manager can deploy servers as required without involving the entire team. Typical deployment time: hours

 Example: Move an Application

Without Xsigo	With Xsigo
When an application is installed on a new server, the I/O attributes will change. Networking and storage settings must reflect that change, which requires the resource managers to be involved. Typical time required: weeks.	I/O can be moved from one server to another in single drag-and-drop operation. Attributes remain persistent. When the application is brought up on the new server, it will see the same resources. No need to re-map networking and storage.

Example: Add Connectivity

Without Xsigo	With Xsigo
De-rack server. Install card. Return server to rack. Run the required cabling. Bring server up and map the resources to the new connectivity.	Deploy virtual connectivity. Map the resources to the new connectivity.

Example: Server Sparing

Without Xsigo	With Xsigo
Server standby  is accomplished two ways: Clustering: One standby for every server. Highly available, but costly. Or… Sparing: Swap servers when needed. Cost effective, but requires labor, downtime, re-cabling, and re-mapping of storage and network resources. Managers must trade off competing objectives.	Migrate virtual connectivity to standby server. Re-deploy application.