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

BGP Down Due to the Eth-Trunk Member Is Taken Out from NE40E

Publication Date:  2013-01-18 Views:  38 Downloads:  0
Issue Description


From the picture above, GE3/1/1 is a member of Eth-trunk ). Customer has took out a member trunk, gi3/1/1 from the Eth-trunk (0) where the BGP peer is sitting.

The BGP configuration and excerpt from the syslog are as follows:-

 <Huawei>display current-configuration configuration bgp
#
bgp 65010
peer 220.232.53.208 as-number 65010
peer 220.232.53.208 connect-interface LoopBack0
peer 220.232.53.209 as-number 65010
peer 220.232.53.209 connect-interface LoopBack0
#
ipv4-family unicast
 undo synchronization
 peer 220.232.53.208 enable
 peer 220.232.53.209 enable
#
ipv4-family vpnv4
 policy vpn-target
 peer 220.232.53.208 enable
 peer 220.232.53.209 enable
#
ipv4-family vpn-instance Mgmt
 import-route direct
#
ipv4-family vpn-instance NMS
 import-route direct
#
ipv4-family vpn-instance Pacnet
 import-route direct
#
ipv4-family vpn-instance SNBB_HSI
 import-route direct
#
ipv4-family vpn-instance SNBB_VPN1
 import-route direct
 peer 202.166.123.49 as-number 9506
 peer 202.166.123.49 password cipher %#D`P_1*E[A]5N74$]<AV!!!
 peer 202.166.123.49 route-policy SNBB_primary import
#
ipv4-family vpn-instance mio_voice
 import-route direct
#
return

<Huawei>display current-configuration interface Eth-Trunk 0.10
#
interface Eth-Trunk0.10
vlan-type dot1q 10
description ebgp peer to SNBB_TP_AR11
ip binding vpn-instance SNBB_VPN1
ip address 202.166.123.50 255.255.255.252
traffic-policy be_pol inbound
trust upstream default
statistic enable

<Huawei>display interface Eth-Trunk0
Eth-Trunk0 current state : UP
Line protocol current state : DOWN
Description:to Singnet_TP_AR11
Route Port,Hash arithmetic : According to flow,Maximal BW: 70G, Current BW: 70G, The Maximum Transmit Unit is 1500
Internet protocol processing : disabled
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 0819-a624-1647
Physical is ETH_TRUNK
Current system time: 2013-01-11 14:49:15+08:00
   Last 300 seconds input rate 32046138192 bits/sec, 3810881 packets/sec
   Last 300 seconds output rate 15587243272 bits/sec, 3148749 packets/sec
   Realtime 0 seconds input rate 0 bits/sec, 0 packets/sec
   Realtime 0 seconds output rate 0 bits/sec, 0 packets/sec
   Input: 6872776210492 packets,7128365326246501 bytes
          6872776210492 unicast,0 broadcast,0 multicast
          8 errors,8 drops
   Output:5954047810219 packets,3385032894260512 bytes
          5954047805837 unicast,4382 broadcast,0 multicast
          0 errors,0 drops
   Input bandwidth utilization  :   46%
   Output bandwidth utilization :   22%
-----------------------------------------------------
PortName                      Status      Weight
-----------------------------------------------------
GigabitEthernet3/0/0          UP          1
GigabitEthernet3/0/1          UP          1
GigabitEthernet3/1/0          UP          1
GigabitEthernet3/1/1          UP          1
GigabitEthernet4/0/1          UP          1
GigabitEthernet4/1/0          UP          1
GigabitEthernet4/1/1          UP          1
-----------------------------------------------------
The Number of Ports in Trunk : 7
The Number of UP Ports in Trunk : 7

 
   


 



From the logs, it shows that the customer undo Command="undo eth-trunk", and the cause the BGP peer status change, changed from ESTABLISHED to IDLE. Refer logs below:

Jan 11 13:41:35 <20.5> OC-PE4 Jan 11 2013 05:41:37 OC-PE4 %%01SHELL/5/CMDRECORD(l)[85862]:Record command information. (Task=VT5 , Ip=220.232.53.78, User=hoisan, Command="system-view")
Jan 11 13:41:39 <20.5> OC-PE4 Jan 11 2013 05:41:41 OC-PE4 %%01SHELL/5/CMDRECORD(l)[85863]:Record command information. (Task=VT5 , Ip=220.232.53.78, User=hoisan, Command="interface GigabitEthernet 3/1/1")
Jan 11 13:41:43 <20.6> OC-PE4 Jan 11 2013 05:41:44 OC-PE4 %%01SHELL/6/DISPLAY_CMDRECORD(l)[85864]:Record display command information. (Task=VT5 , Ip=220.232.53.78, User=hoisan, Command="display this")
Jan 11 13:41:50 <20.5> OC-PE4 Jan 11 2013 05:41:52 OC-PE4 %%01SHELL/5/CMDRECORD(l)[85865]:Record command information. (Task=VT5 , Ip=220.232.53.78, User=hoisan, Command="undo eth-trunk")
Jan 11 13:41:50 <20.2> OC-PE4 Jan 11 2013 05:41:52 OC-PE4 SRM_BASE/2/PORTPHYSICALUP: OID 1.3.6.1.4.1.2011.5.25.129.2.5.2 Physical state of the port changes to up. (EntityPhysicalIndex=16974338, BaseTrapSeverity=3, BaseTrapProbableCause=74752, BaseTrapEventType=5, EntPhysicalName="GigabitEthernet3/1/1")
Jan 11 13:41:50 <20.4> OC-PE4 Jan 11 2013 05:41:52 OC-PE4 IFNET/4/IF_LINKUP:OID 1.3.6.1.6.3.1.1.5.4 Interface 139 turned into UP state.(AdminStatus=1,OperStatus=1,InterfaceName=GigabitEthernet3/1/1)
Jan 11 13:41:50 <20.5> OC-PE4 Jan 11 2013 05:41:52 OC-PE4 %%01TRUNK/5/MEMBER_DOWN(l)[85866]:The status of the trunk member went Down. (TrunkName=Eth-Trunk0, PortName=GigabitEthernet3/1/1)
Jan 11 13:41:50 <20.6> OC-PE4 Jan 11 2013 05:41:52 OC-PE4 %%01IFNET/6/IF_INFO_CHANGE(l)[85867]:The interface Eth-Trunk0 changed the Baud from 70000000000 bit to 60000000000 bit.
Jan 11 13:41:50 <20.5> OC-PE4 Jan 11 2013 05:41:52 OC-PE4 %%01TRUNK/5/MEMBER_DOWN(l)[85868]:Slot=3;The status of the trunk member went Down. (TrunkName=Eth-Trunk0, PortName=GigabitEthernet3/1/1)
Jan 11 13:41:52 <20.5> OC-PE4 Jan 11 2013 05:41:54 OC-PE4 %%01VTY/5/ACL_DENY(l)[85869]:The TCP request was denied according to ACL rules. (IpAddress=90.31.81.212)
Jan 11 13:41:52 <20.5> OC-PE4 Jan 11 2013 05:41:54 OC-PE4 %%01SHELL/5/CMDRECORD(l)[85870]:Record command information. (Task=VT5 , Ip=220.232.53.78, User=hoisan, Command="quit")
Jan 11 13:41:53 <20.5> OC-PE4 Jan 11 2013 05:41:55 OC-PE4 %%01SHELL/5/CMDRECORD(l)[85871]:Record command information. (Task=VT5 , Ip=220.232.53.78, User=hoisan, Command="quit")
Jan 11 13:41:59 <20.6> OC-PE4 Jan 11 2013 05:42:01 OC-PE4 %%01SHELL/6/DISPLAY_CMDRECORD(l)[85872]:Record display command information. (Task=VT5 , Ip=220.232.53.78, User=hoisan, Command="display interface GigabitEthernet 3/1/0")
Jan 11 13:42:00 <20.4> OC-PE4 Jan 11 2013 05:42:02 OC-PE4 DS/4/DATASYNC_CFGCHANGE:OID 1.3.6.1.4.1.2011.5.25.191.3.1 configurations have been changed. The current change number is 41, the change loop count is 0, and the maximum number of records is 4095.
Jan 11 13:42:06 <20.6> OC-PE4 Jan 11 2013 05:42:08 OC-PE4 %%01SHELL/6/DISPLAY_CMDRECORD(l)[85873]:Record display command information. (Task=VT5 , Ip=220.232.53.78, User=hoisan, Command="display interface GigabitEthernet 3/1/1")

BGP status change from establish to idle.

Jan 11 13:43:02 <20.6> OC-PE4 Jan 11 2013 05:43:04 OC-PE4 %%01BGP/6/SEND_NOTIFY(l)[85874]:The router sent a NOTIFICATION message to peer 202.166.123.49. (ErrorCode=4, SubErrorCode=0, BgpAddressFamily=SNBB_VPN1, ErrorData=NULL)
Jan 11 13:43:02 <20.3> OC-PE4 Jan 11 2013 05:43:04 OC-PE4 %%01BGP/3/STATE_CHG_UPDOWN(l)[85875]:The status of the peer 202.166.123.49 changed from ESTABLISHED to IDLE. (InstanceName=SNBB_VPN1, StateChangeReason=Hold Timer Expired)
Jan 11 13:43:02 <20.2> OC-PE4 Jan 11 2013 05:43:04 OC-PE4 BGP/2/BACKWARD:OID 1.3.6.1.2.1.15.7.2 The BGP FSM moves from a higher numbered state to a lower numbered state. (BgpPeerRemoteAddr=202.166.123.49, InstanceId=5, Afi=1, Safi=1, PeerType=1, PeerRemoteAddr=202.166.123.49, InterfaceIndex=0, BgpPeerLastError=40, BgpPeerState=1, BgpPeerUnavaiReason=4, InterfaceName=null)


 

Handling Process
Normally, BGP protocol packets , like established and update, is based on TCP connection. Exchanging bgp keepalive packets is done by active member port of Eth-trunk.

Although GE3/1/1 quit eth-trunk0, GE3/1/1 still keep the physical up status. GE2/2/2 of peer router still play an active role. Router-other still send BGP protocol packets from GE2/2/2 to OC-PE4 GE3/1/1 ,the port GE3/1/1 does not have own ip address, drop protocol packets, then BGP peer went down.

BGP protocol packets were based on TCP connection,  it cannot realize the membership change of Eth-Trunk. Eth-Trunk port deals with traffic is based on active member ports. According to Hash Algorithm ,routers determine which member port deal with specific traffic.

 

Root Cause
BGP protocol packets were based on TCP connection,  it cannot realize the membership change of Eth-Trunk. Eth-Trunk port deals with traffic is based on active member ports. According to Hash Algorithm ,routers determine which member port deal with specific traffic.
Solution
Please provide below info:

<Huawei>display bgp peer (IP) log-info
<Huawei>display bgp vpnv4 vpn-instance (Name) peer (IP) log-info
<Huawei>display tcp statistics
<Huawei>display bfd session all
<Huawei>display current-configuration

display diagnostic info
log.log
dblg.log
<OC-PE4>display bfd session all 


Suggestions
Please check on the BGP status before taken out the eth-trunk member by using command below:

<Huawei>display bgp peer

END