update msg without MpReachNlri or MpUnReachNlri is now normal

Signed-off-by: ISHIDA Wataru <[email protected]>
---
 ryu/services/protocols/bgp/peer.py |    2 --
 1 file changed, 2 deletions(-)

diff --git a/ryu/services/protocols/bgp/peer.py 
b/ryu/services/protocols/bgp/peer.py
index 24edf2d..0ee39be 100644
--- a/ryu/services/protocols/bgp/peer.py
+++ b/ryu/services/protocols/bgp/peer.py
@@ -986,8 +986,6 @@ class Peer(Source, Sink, NeighborConfListener, Activity):
 
         # non-MPBGP Update msg.
         if not (mp_reach_attr or mp_unreach_attr):
-            LOG.info('Received UPDATE msg. with no MpReachNlri or '
-                     'MpUnReachNlri attribute.')
             if not self.is_mpbgp_cap_valid(RF_IPv4_UC):
                 LOG.error('Got UPDATE message with un-available'
                           ' afi/safi %s' % RF_IPv4_UC)
-- 
1.7.9.5


------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Ryu-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ryu-devel

Reply via email to