An architect is planning an HPE Moonshot System deployment. The architect plans to individually connect each iLO CM module to the management network. The customer informs the architect that this plan requires too many 1GbE ports per rack for the data center infrastructure.
What is one way that the architect can alter the plan to meet the customers needs, while still allowing iLO access to the HPE Moonshot Systems?
To meet the customer's needs while minimizing the number of 1GbE ports per rack, the architect can keep one iLO CM Management port connected to the network and use the iLO CM link ports on each iLO CM module to daisy chain the chassis together. This approach reduces the number of required network ports by connecting only one port on each chassis to avoid loops, while still maintaining iLO access to the HPE Moonshot Systems.
A = Incorrect, always try and separate production traffic from management traffic B = Correct, see P90 in HPE Master ASE v4 “You can choose to connect each Apollo chassis directly to the switch that you selected for the iLO connections. Connect only one port on each chassis to avoid loops. As an alternatice design, you could connect several Apollo a6000 Chassis in a daisy chain and then connect the final chassis to the switch.”, “ it uses fewer ports on the network switch” C = Incorrect D = You will require an extra switch, not reduce the number of ports required
The question says about " An architect is planning an HPE Moonshot System deployment. " not a6000. I believe the given answer D is correct.