The answer is C because SW2 is running PAgP (Cisco Proprietary). "channel-group 1 mode desirable" enables PAgP. "channel-group 1 mode active on" enables LACP. This also concludes that both switches are Cisco switches.
For me the answer is C, this is a cisco exam, however at least one of those switches should be cisco, and according with the picture, both outcomes are the same, so both are cisco.
Answer is C , the I - Stand-ALone means that SW2 is the only one using PagP and SW3 it's not.
Stand-ALone means that switch 2 is the only one standing in PagP mode .
D is correct
the exhibit is not complete, here is the complete one.
Switch2 #show etherchannel summary
Flags: D - down P - in port-channel
I - stand-alone s - suspended
Number of channel-groups in use: 1
Number of aggregators: 1
Group Port-channel Protocol Ports
------+-------------+-----------+----------------------------------------------
1 Po1(SD) PAgP Gi0/0(I) Gi0/1(I)
Switch3 #show etherchannel summary
Flags: D - down P - in port-channel
I - stand-alone s - suspended
Number of channel-groups in use: 1
Number of aggregators: 1
Group Port-channel Protocol Ports
------+-------------+-----------+----------------------------------------------
1 Po1(SD) LACP Gi0/0(I) Gi0/1(I)
as you see, there´s a protocol mismatch on both sides.
PAgP is a Cisco proprietary protocol, whereas LACP is an open standard, making LACP the preferred choice (we don´t know if SW3 is a cisco swich or not).
since SW3 is configured for LACP, configuring LACP is best way to resolve this issue.
The simple fact that the etherchannel bundle is showing PagP and the interfaces are showing standalone, even when connect suggest that the SW might be a different protocol. You are better off changing the channel protocol to active. I support D as the final answer.
A problem with this question is that it does not specify what switch the proposed configuration should be on for answers C and D. Also answers C and D says both INTERFACES, not both switches.
C would be correct if we're changing both interfaces on SW3 so that we match PagP on SW2.
But answer D could be correct if we change both interfaces on SW2, since with the complete configuration shown for SW3 on other sites for this question, it is configured for LACP.
I can't see the entire output, so I don't know the deal with SW3. But if we have PAgP configured on the SW2, then on the SW3, we must configure auto or desirable to bring etherchannel up.
SW2 It's already configured with Port Aggregation Protocol as shown on the output of Show Etherchannel Summary.
The question also does not specify which switch to make the configuration we are to assume it's on SW3, if we configure Active on both interfaces the Etherchannel will not bundle due to incompatible protocols
Active/Passive are both configuration for LACP.
Active/Passive = Bundle
Active/Active = Bundle
Passive/Passive = No bundle
Auto/Desirable are both configurations for PAGP
Auto/Desirable = Bundle
Desirable/Desirable = Bundle
Auto/Auto = No bundle
Hope this helps.
C is correct
one side (sw2) shows PAgP, so for the etherchannel works properly both sw must run the same protocol, so teh option is "desirable"
Regards!
This question is ridiculous.
Both solutions can work, it depends if I have multivendor on my enviroment or not.
Of course as the other says because both are Cisco switches Cisco prefer to use their own protocols....
SW2 is using PAgP and both members interface Gi0/0 and Gi0/1 are in state(I),
it means they are not receiving any activity.
configure channel-group 1 mode desirable on SW3.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
rggod
Highly Voted 3 years, 10 months agonoov
3 years, 10 months agoreh
3 years, 4 months agogtddrf
3 years, 7 months agoDeepak_k
3 years, 10 months agoMiguex125
Highly Voted 3 years, 9 months agomatass_md
Most Recent 5 days, 12 hours agodavdtech
5 months, 2 weeks ago[Removed]
9 months ago[Removed]
9 months ago9d3b6c3
8 months, 1 week agosupershysherlock
11 months, 1 week agoHaidary
1 year, 3 months agoHaidary
1 year, 3 months agoLanreDipeolu
1 year, 6 months agodanman32
1 year, 7 months agouhljeb
1 year, 10 months agoClauster
1 year, 11 months agoDataset
2 years agostan3435
2 years, 1 month agoXBfoundX
2 years, 1 month agoRose66
2 years, 1 month agoKOJJY
2 years, 2 months agoAsymptote
2 years, 3 months ago