Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
An ME60 V100R005C02B01B served as an LAC and needed to set up L2TP tunnels with multiple LNSs.
When tunnel loading-share was not configured for L2TP groups, the RADIUS server delivered four LNS IP addresses and ME60 set up four L2TP tunnels.
Problem 2:When tunnel loading-share was configured for L2TP groups, the RADIUS server delivered four LNS IP addresses but ME60 set up only one L2TP tunnel.
The RADIUS server delivered four tags each of which contained four LNS IP addresses. According to trace information, the LNS IP addresses were in different sequence for each user. For a user, ME60 always selected the first LNS IP address to set up a tunnel. If the tunnel existed, no tunnel needed to be created.
Because the four LNS IP addresses had been delivered as the first one, ME60 set up four tunnels.
The RADIUS server delivered four tags each of which contained only one LNS IP address. Therefore, ME60 used the existing tunnel of the L2TP-group to which the tag belonged (no tunnel would be created unless no existing tunnel was available).Therefore, when tunnel loading-share was configured for L2TP groups, the RADIUS server delivered four LNS IP addresses but ME60 set up only one L2TP tunnel.
Modified the RADIUS configuration so that only one tag which carried multiple LNS IP addresses was configured in the attribute Tunnel-Server-Endpoint(67).