No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OSPF Neighbor cannot Set up Because of Unreasonable Configuration of EACL for NetEngine80

Publication Date:  2012-07-27 Views:  48 Downloads:  0
Issue Description
      Version: VRP3.10-0426SP03 
Topology: NE80 (g1/0/1)--(VLAN3002 G1/0/0)S8016 
The interface of NE80 is down because of link, and when it is restored to be up, the OSPF neighbor with S8016 cannot set up. 
Alarm Information
Null
Handling Process
1. Check the configuration, and it is found that the RULE-MAP for EACL ACL2 configured for interconnecting interfaces contains the address of interconnecting interfaces.  
2. Modify RULE-MAP rules, and iron out the address of interconnecting interface. The problem is solved. 
Root Cause

1. Check the configurations of the equipment, as follows:  
    rule-map crc1 ip 222.47.0.0 0.0.255.255 222.32.0.0 0.31.255.255
    flow-action crc redirect ip 222.47.1.185 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. 
      
      

Suggestions
Null

END