To have a better experience, please upgrade your IE browser.upgrade
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?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
1. Check the configurations of the equipment, as follows:
rule-map crc1 ip 184.108.40.206 0.0.255.255 220.127.116.11 0.31.255.255
flow-action crc redirect ip 18.104.22.168 GigabitEthernet1/0/2
eacl acl2 crc1 crc
The EACL is applied to the interconnecting interface of S8016, and the RULE-MAP contains the address of the interface. The DD packets from the process to set up OSPF neighbor are unicast and redirected. However, the S8016 at peer cannot receive the packets, so OSPF neighbor cannot set up.
2. EACL has been in existence before the interface is down, but why does it not influence the state of neighbor? This is because DD packets will not be exchanged once the neighbor relationship has been set up. The HELLO packets to maintain neighbor relationship are multicast, and the EACL is configured after the neighbor has been set up.