Start a Conversation

Solved!

Go to Solution

1346

July 27th, 2021 10:00

eth1 active on secondary controller on PS6210

We stumbled upon an issue that has us scratching our heads.  We were getting ready to move the 10Gb cables on the standby controller to a new set of switches, but eth1 was showing activity on that controller.  I'll attempt to post a couple images, but essentially it looks like this:

Controller 0 = secondary   f/w: v9.1.4   boot time: 7/22/2021
Controller 1 = primary   f/w: v9.1.4   boot time: 6/1/2021

eth0   10Gbps   status = up   controller = primary
eth1   10Gbps   status = up   controller = secondary

 

Since we didn't think it was possible to have both controllers with activity at the same time, can someone help explain what we're seeing?  We ended up pulling the eth1 cable from the primary controller (since it didn't show any activity), and sure enough, it didn't miss a beat/ping.

group-manager-network-tab.PNG

ps6210-controller-ports.jpg

3 Apprentice

 • 

1.5K Posts

July 27th, 2021 14:00

Hello, 

 That is completely normal.  At some point the carrier was lost for that port on the active controller.  This EQL model has the ability through an internal bus access the physical port on the passive. It's a "port failover" feature.  The passive controller isn't actually handling any traffic.  It's not possible to do so as the passive controller does not have access to the drives or volumes.  

 You can proceed without concern. 

If you are still under contract you should consider upgrading the firmware to 10.0.3. 

 Regards, 

Don 

15 Posts

July 28th, 2021 04:00

Thanks Don.  Does this mean a port failover can be triggered by something like a switch reboot or unplugging a cable?  And is there a way (maybe through CLI) to force it to fail back to the port on the primary CM?  

3 Apprentice

 • 

1.5K Posts

July 28th, 2021 07:00

Hello, 

 That's exactly what it means. At some point the carrier / link was lost.  The vertical failover immediately switched to the physical port, not ethernet controller, on the passive. So no change in MAC address. 

 There's no command to force it to go back to the primary.  When you pull the cable it will go back to the primary controller port on its own. 

 Regards, 

Don 

15 Posts

July 28th, 2021 08:00

Perfect!  Thanks for the explanation.

No Events found!

Top