- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect-FC removal of Static Login
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2010 02:35 PM
10-12-2010 02:35 PM
Virtual Connect-FC removal of Static Login
Reo had a question on the Virtual Connect Fibre Channel module:
***************************
Hi All, we have seen removal of Static Login Support in VC-fw v3.00 or later.
>Removal of Static Login Support in Utah and Omaha/Ocho Modules.
reference,
================
Virtual Connect Fabric
By default, all of the VC-FC uplinks are grouped into a single fabric, distributing connectivity from all 16
server blades in the enclosure. If a port in the group becomes unavailable, hosts logged in through that
port are reconnected to the fabric through the remaining ports in the group, resulting in auto-failover.
However, users can redistribute the connections manually.
To form a Virtual Connect fabric correctly, participating uplinks must be connected to the same SAN
fabric. The WWN of the principle fabric switch indicates connectivity to the same SAN fabric in Virtual
Connect.
The module uses dynamic login distribution to provide an uplink port path failover that allows server
connections to failover within the Virtual Connect fabric. Server connections are redistributed across all
available (currently logged into the external SAN) uplink ports.
================
Why was this static function removed?
***********************
Dave responded:
***************************
Reo,
I believe there are two main reasons. One is that Dynamic has auto login. The other is that Static uplinks were tied into specific downlink bays. Depending on the number of uplink and the servers installed, bandwidth could be an issue. If the site was using full height, BL870s or the new BL890 some uplinks may not be used.
See attached info: