[CAUSE] The tBgp4RouteInvalid notification is generated when the received route is invalid for a specific reason and the route can not be used or advertised further. [EFFECT] The BGP peer ignores the route and flags the path attribute and the route so that the peer/tribe that was attempting to advertise the associated route can skip this route. The BGP peering is not torn down in this case. [RECOVERY] There is no recovery required for this notification.