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

How to Deal with It When Competitor's GSR Cannot Ping the Address of a User Gateway of BAS Under the NE80E

Publication Date:  2012-07-27 Views:  33 Downloads:  0
Issue Description
Networking:
(User gateway address: 58.212.215.1) 5200F��(G3/0/3.4000) NE80E (uplink)―GSR����external network
The user gateway address of the 5200F can be successfully pinged directly from the NE80E or through the address that connects the GSR and the NE80E but cannot on the GSR. 
 
Alarm Information
Null
Handling Process
interface GigabitEthernet3/0/3.4000
description to NJ-HouDaShuGen-5200F-01 218.2.119.18
control-vid 4000 dot1q-termination-----The problem was solved after vid was changed from 1 to 4000.
dot1q termination vid 4000
ip address 218.2.119.17 255.255.255.252
traffic-policy icmp outbound
arp broadcast enable
trust upstream default
trust 8021p
This problem was cause by the QinQ interface running a routing protocol, because, in this case, control-vid and vid must be the same. If an interface needs to support a routing protocol, rt-protocol must be added at the end of the command to be configured. In this manner, you will be reminded if the two parameters are different. If rt-protocol is not added, the two parameters will not be checked for consistency.
[NJ-LZX-R-NE80E-01-GigabitEthernet3/0/3.4000]control-vid 4000 dot1q-termination
?
rt-protocol Support router protocol
<cr>
If the two parameters are configured to be different, VLINID in the hardware forwarding table is incorrect, causing abnormal forwarding. 
 
Root Cause
Configure the ACL on the NE80E.
<NJ-LZX-R-NE80E-01>dis acl 3999
Advanced ACL 3999, 5 rules
test
Acl’s step is 5
rule 5 permit icmp source 222.190.36.161 0 destination 58.212.215.1 0 (2 times matched)
rule 10 permit icmp source 58.212.215.1 0 destination 222.190.36.161 0 (0 times matched)
rule 15 permit icmp source 222.190.36.161 0 destination 218.2.119.18 0 (0 times matched)
rule 20 permit icmp destination 218.2.119.18 0 (31 times matched)
rule 25 permit icmp destination 58.212.215.1 0 (20 times matched)
traffic classifier icmp operator or
if-match acl 3999
traffic behavior icmp
traffic policy icmp
statistics enable
classifier icmp behavior icmp
The policy is applied to the incoming direction of the four uplink interfaces on the NE80E and the sub-interface connecting the NE80E and the 5200F.
Ping the address of the uplink interface (218.2.119.18) and the user gateway address (58.212.215.1) of the 5200F from the public network. The results viewed showed that data came into the NE80E from the uplink interface and went out from the downlink interface in pinging 218.2.119.18 and that the ACL could be matched on the uplink interface of the NE80E and could not on the downlink interface in pinging 58.212.215.1. It indicated that the data with the destination address of the user gateway reached the NE80E but was not forwarded. The test result showed that the NE80E was faulty. 
 
Suggestions
If an interface needs to support a routing protocol, rt-protocol must be added at the end of the command to be configured. In fact, the addition of rt-protocol is to check whether the two parameters are the same. Therefore, you only need to configure the two parameters to be the same. 

END