cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1310
Views
0
Helpful
2
Replies

Can the same pair of Fabric Interconnect be shared for both UCS Blades and HyperFlex?

SIMMN
Spotlight
Spotlight

I have a customer asking to quote for some hx220m4 boxes but they do not want to buy another pair of the FIs. They want to just use their existing FIs which are currently used for the UCS chassis. I never done the shared FI for UCS and HyperFlex...Is it supported by Cisco? If so, would there be any risk?

 

Also, I read somewhere on cisco.com that UCS chassis is supported to be added to FIs of an existing hyperflex cluster. Is it still true?

 

1 Accepted Solution

Accepted Solutions

Kirk J
Cisco Employee
Cisco Employee

Greetings.

That is a loaded question ;)

Please see https://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/HyperFlex_HX_DataPlatformSoftware/TechNotes/b_Adding_HX_to_Existing_UCS-FI_Domain.html

 

The answer is "maybe", depending on requirements for existing blades, the requirements for HX, how large a HX environment you think you will grow to, etc

As the above referenced article mentions, you will want to have the customer open a TAC case to review the existing config, go through the HX checklist, and potential caveats.

This is a scenario where, if done incorrectly, will end up with an under-performing HX or overall UCSM environment that is out of compliance/unsupported.

 

Thanks,

Kirk...

View solution in original post

2 Replies 2

Kirk J
Cisco Employee
Cisco Employee

Greetings.

That is a loaded question ;)

Please see https://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/HyperFlex_HX_DataPlatformSoftware/TechNotes/b_Adding_HX_to_Existing_UCS-FI_Domain.html

 

The answer is "maybe", depending on requirements for existing blades, the requirements for HX, how large a HX environment you think you will grow to, etc

As the above referenced article mentions, you will want to have the customer open a TAC case to review the existing config, go through the HX checklist, and potential caveats.

This is a scenario where, if done incorrectly, will end up with an under-performing HX or overall UCSM environment that is out of compliance/unsupported.

 

Thanks,

Kirk...

Thanks! Good information.

Review Cisco Networking for a $25 gift card