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

The NE40 Cannot Implement Layer 3 Interconnection with the NE80E Because the MAC Address Is Not Written into the Board

Publication Date:  2012-07-27 Views:  34 Downloads:  0
Issue Description
The networking diagram is as follows:
NE40 (gi3/0/0) ------------------(gi1/0/0) NE80E
The gi1/0/0 interface on the NE80E is assigned with this IP address: 222.56.112.141. The LPUF inserted in slot 3 on the NE40 is a WAN board, whose gi3/0/0 interface is assigned with this IP address: 222.56.112.142. The problem is that the IP address of the GE interface on the NE80E cannot be pinged.
[KM_ZXJF_NE40-8]ping 222.56.112.141
PING 222.56.112.141: 56 data bytes, press CTRL_C to break
Request time out
Request time out
Request time out
Request time out
Request time out

--- 222.56.112.141 ping statistics ---
5 packet(s) transmitted
0 packet(s) received
100.00% packet loss
Note: The LPUF inserted in slot 3 on the NE40 is registered as a WAN board.
<KM_ZXJF_NE40-8>disp dev pic
Pic-status information of all lpu_nat_gre boards:
LPU 3: Online
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
PIC # Online    Type        Port_count         Init_result       Logic down
0              Present           ETH-1000M wan      2            SUCCESS           SUCCESS
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Portnum: 0 1
Status : Ok Ok
PIC # Online    Type       Port_count         Init_result        Logic down
1               Present          ETH-1000M wan      2            SUCCESS          SUCCESS
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Portnum: 0        1
Status : Ok       Ok 
 
Alarm Information
Null
Handling Process
1. Viewing the configuration, the engineer found that the configuration was nothing wrong and the port was Up on the physical layer and protocol layer.
<KM_ZXJF_NE40-8>disp int gi3/0/0
GigabitEthernet3/0/0 current state: up
Line protocol current state: up
Hardware is WAN-FastEthernet,
Address is ffff-ffff-ffff
Description: TO->NE80E_GE_1/0/0
Internet address is 222.56.112.142/30 Is-Primary
The Maximum Transmit Unit is 1500 bytes, the BandWidth is 1000000 Kbits
Send-frame-type is Ethernet_II, loopback not set
Negotiation disabled, full-duplex, 1000Mbps
Flow control disabled, urpf disabled
This port works as a Router
Statistics last cleared: never
Traffic statistics:
Last 5 minutes input rate 0 bits/sec, 0 packets/sec
Last 5 minutes output rate 8 bits/sec, 0 packets/sec
10 packets input, 640 bytes
794 packets output, 57510 bytes
Input: 0 shorts, 0 jumbos, 0 giants, 0 pauses
           0 unicasts, 0 multicasts, 10 broadcasts
           0 MulticastOctets, 0 MulticastPkts 
           0 InvalidVlanOctets, 0 InvalidVlanPkts
           0 input fragments, 0 jabbers
           0 CRC, 0 errors, 0 overruns
Output: 0 shorts, 0 jumbos, 0 giants
              20 unicasts, 0 multicasts, 774 broadcasts 
              0 MulticastOctets, 0 MulticastPkts
              0 InvalidVlanOctets, 0 InvalidVlanPkts 
              0 runts, 0 jabbers, 0 CRC
              0 deferrals, 0 underruns, 0 aborts
              0 collisions, 0 lates, 0 singles
              0 multiples, 0 excessives
2. Through check, the engineer found that the two ends were consistent in the negotiation mode and duplex mode. The problem was that the gi3/0/0 interface could not learn the MAC address sent from the peer.
<KM_ZXJF_NE40-8>disp arp int gi3/0/0
Arp Table:
Total number of arp:0         static:0          dynamic:0
IP Address          MAC Address              VlanID Type VPN-Instance           Interface
3. Viewing the status information of the gi3/0/0 interface, the engineer found that the MAC address was ffff-ffff-ffff. Inquiring the R&D personnel, the engineer learned that the MAC address was not written into the board. After the MAC address was written into the board, the problem was solved. 
 
Root Cause
1. Incorrect configuration such as inconsistent masks causes it impossible to ping the IP addresses at both ends.
2. The optical fiber problem causes the abnormal transmission and launch optical power at the port, whose physical status is Down. Another possibility is that the negotiation parameters are inconsistent at the two ends, which causes the interconnection failure.
3. The MAC address fails to be learned, which leads to the ping failure. 
 
Suggestions
In new services, if the Ethernet interfaces such as the GE interface are all Up, but their IP addresses cannot be pinged, it is recommended that you check whether the MAC addresses can be learned by the interfaces at both sides. 

END