A network engineer configures BGP between R1 and R2. Both routers use BGP peer group CORP and are set up to use MD5 authentication. This message is logged to the console of router R1:
`May 5 39:85:55.469: %TCP-6-BADAUTH` Invalid MD5 digest from 10.10.10.1 (29832) to 10.120.10.1 (179) tebleid -0
Which two configurations allow a peering session to form between R1 and R2? (Choose two.)
To establish a BGP peering session with MD5 authentication, both routers must be configured with the same password for the peer group, and each router must specify the peer's IP address and associate it with the peer group. In this case, Router R1 is 10.120.10.1 and Router R2 is 10.10.10.1. Therefore, R1 should be configured with R2's IP address and the password, and R2 should be configured with R1's IP address and the password. This setup will ensure that the MD5 password match and the peering session can be established successfully.
Answer is correct, AB. The question states the console output is from R1, which means that R1 is 10.120.10.1, and R2 is 10.10.10.1. If you missed that you may have assumed the reverse and picked DE.
because R1 is 10.120.10.1, according to the error message which states TCP port 179, which is DESTINATION port for BGP, hence A, B are the only possible answers in this case. The destination port 179 is referring to the incoming router 10.120.1.x
I think ED choice is more appropriate; all because the syslog message was obtained from R1 that indicated R1 is 10.10.0.1
vice versa: R2 is 10.10.10.1 . but AB is correct
if the two routers have different passwords configured, a message such as this is displayed: %TCP-6-BADAUTH: Invalid MD5 digest from [peer's IP address]:11004 to [local router's IP address]:179 https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/112188-configure-md5-bgp-00.html
solid^ TY
Given answer is correct. Verified in GNS3 lab.
Answer is AB. Verified in my lab. R1 indicates it is receiving an Invalid MD5 digest from R2's IP/ R2 is sending that to port 179 of R1's IP.
(29832) random port number represent source. (179) BGP default port number represent destination.
A,B is correct. The log is on R1.
I confused, the TCP destination port is 179 and source port is dynamic. so the ip address for R1 is 10.10.10.1
A & B are correct 10.120.10.1 (179) is the local router IP (R1) 10.10.10.1 (29832) is the peer router IP (R2) On R1, configure R2 (IP 10.10.10.1) as a neighbor with the password. On R2, configure R1 (IP 10.120.10.1) as a neighbor with the password. This is from cisco: if the two routers have different passwords configured, a message such as this is displayed: %TCP-6-BADAUTH: Invalid MD5 digest from [peer's IP address]:11004 to [local router's IP address]:179 https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/112188-configure-md5-bgp-00.html#:~:text=if%20the%20two,IP%20address%5D%3A179
I think ED choice is more appropriate; all because the syslog message was obtained from R1 that indicated R1 is 10.10.0.1
R1 is configured with the IP 10.10.10.1 while R2 is configured with 10.120.10.1. This is noticeable because BGP speaks over port 179. So the destination port is attached to the destination IP as noted in the error log. This way we can determine the destination IP is accurate (B).
cisco_R2#show running-config | section bgp router bgp 2 bgp router-id 2.2.2.2 bgp log-neighbor-changes neighbor GR_AS3 peer-group neighbor GR_AS3 remote-as 3 neighbor GR_AS3 password cisco neighbor 192.168.255.3 peer-group GR_AS3 ! address-family ipv4 redistribute connected neighbor 192.168.255.3 activate neighbor 192.168.255.3 soft-reconfiguration inbound exit-address-family cisco_R2#
cisco_R3#show running-config | section bgp router bgp 3 bgp router-id 3.3.3.3 bgp log-neighbor-changes neighbor GR_AS2 peer-group neighbor GR_AS2 remote-as 2 neighbor GR_AS2 password 7 1511021F0725 neighbor 192.168.255.22 peer-group GR_AS2 neighbor 192.168.255.55 remote-as 5 ! address-family ipv4 redistribute connected neighbor GR_AS2 soft-reconfiguration inbound neighbor 192.168.255.22 activate neighbor 192.168.255.55 activate neighbor 192.168.255.55 soft-reconfiguration inbound neighbor 192.168.255.55 route-map to_R5 in exit-address-family cisco_R3#
cisco_R3#show ip bgp summary | b Nei Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 192.168.255.22 4 2 9 14 44 0 0 00:04:14 3 192.168.255.55 4 5 42 59 44 0 0 00:32:39 3 cisco_R3#
Answer is correct. The port number used (179) also gives it away. But Cisco asking so many questions that are not in the OCG is breaking my spirit.
AB is correct. tested in EVENG
R1 is 10.10.0.1
i think alarm TCP-6-BADAUTH` Invalid MD5 digest. the local router in inspector and found that Invalid. Local router should be destination (port 179). So, local router R1 is 10.120