Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

In an Anchor – Foreign WLC scenario, which WLC sends out the RADIUS accounting?

April 26, 2017Accounting Anchor foreign radius scenario wlc

0

Posted

In an Anchor – Foreign WLC scenario, which WLC sends out the RADIUS accounting?

1 Answer

0

Posted

A. In this scenario, authentication is always done by the anchor WLC. Therefore, RADIUS accounting is sent by the anchor WLC. Q. The guest tunnel between the internal controller and anchor controller fails. I see these logs in the WLC: mm_listen.c:5373 MM-3-INVALID_PKT_RECVD: Received an invalid packet from 10. 40.220.18. Source member:0.0.0.0. source member unknown.. Why? A. You check the status of the tunnel from the WLC GUI on the WLANs page. Click on the drop-down box near a WLAN and choose Mobility Anchors which contains the status of control and data path. The error message is seen due to one of these reasons: • Anchor and internal controllers are on different versions of code. Make sure they run same versions of the code. • Misconfigurations in the mobility anchor configuration. Check that the DMZ is configured itself as the Mobility anchor and the internal WLCs have the DMZ WLC configured as the Mobility anchor. For more information on how to configure the Mobility anchor, refe