  I still don't fully understand what you are doing. If you are referring to the connection as when you have a network cable attached from each of the two CMC GB1 ports to your switch then that is not how the CMCs work. The redundancy is active/passive so you should not be able to SSH or connect in any way to the passive controller. If having the passive controller connected to your switch causes the EWS of the active controller to not function then that is likely an issue with  your switch blocking traffic to stop a broadcast storm since the passive controller should not be on the network. If you are referring to having GB1 and GB2 on the active CMC connected to your switch at the same time causing network traffic to not work properly then yes, they are working as intended. They are not supposed to be connected that way. GB1 should be connected to your network to allow access to the CMC. GB2 is for daisy chaining CMCs together. GB2 should only be connected to GB1 of another CMC in another chassis(not the redundant CMC in the same chassis). Thanks
Hi  we have this issue that when both CMC management is both patched at the same time the UI cannot be accessed. I can ping the IP and I can SSH to it except for the UI Additionally, I have intermittent access to the iDRAC UI of all the blade servers under it even though ping is consistent. When only connected to 1 management interface, everything works well. I'm pretty sure this is a management network redundancy issue.. but not sure how to fix it.
CMC Web UI not working when network is redundant mode