- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: C 7000 blade SFP incompatible
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
11-17-2017 11:42 AM
11-17-2017 11:42 AM
C 7000 blade SFP incompatible
Hello i have C 7000 blade with 2 flex fabric 10 GB/24 module and 8 server BL 460 gen9 my probleme is connect this with MSA2040 and SWITCH SN3000B i don't show FibreChannel module in VC Manager and when i connect SFP + to flex incompatible message or mismatch notification show
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2018 04:46 AM
04-25-2018 04:46 AM
Re: C 7000 blade SFP incompatible
Hi,
- Determine which VC Ethernet Module in the enclosure is the "Standby" for Virtual Connect Manager (use VCSU �healthcheck).
- Power off the VC-Ethernet modules corresponding to the standby bay side of the enclosures (i.e., all even or all odd bays in the domain).
- Make a change to the configuration that affects all modules by selecting "Define Ethernet Network," then entering the Network Name as "Test-Delete." Do not add Uplinks - Select "Apply."
- Power on the VC-Ethernet modules powered off in step 2.
- Wait for modules to be recovered and checkpoint to be completed to Standby bay. Recovery time will vary depending on the size of the VC domain.
- Power off the VC-Ethernet modules corresponding to the primary bay side of the enclosures (i.e., all of the other VC-Ethernet modules).
- Reverse the change to the configuration (e.g., delete the network created in step 3).
- Power on the VC-Ethernet modules powered off in step 6.
- Wait for the modules to be recovered and checkpoint to be completed to standby bay. Recovery time will vary depending on the size of the VC domain.
I am an HPE Employee
If this information helps you with your issue, please click the thumb to register a Kudo.
Also, if it resolves your issue, please consider marking it as an Solution Accepted.
I work for HPE