GRE + FOU - Null pointer exception resulting in hard crash of network appliance #7
Labels
No Label
Circuit provider
Datacentre
Feature request
Monitoring
Network Fabric Router
Network software
Resolved
Website
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Reference: ev/issues#7
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There is a bug in either the Linux kernel or the iproute2 package included by default on our network appliances (EVXs + NFRs). On some runs of the
ip fou
command, a null pointer exception can be triggered, causing a complete lock up of the appliance, requiring a hard reset to resolve.This only affects appliances that have our beta GRETAP tunnels deployed, however these can be deployed for a single connection on an NFR with several connections that will experience a disruption if the NPE gets triggered.
We are currently testing the latest backported Linux kernel and iproute2 package to see if the issue has been resolved upstream.
The backported kernel and related tools have been confirmed as stable, and have resolved the Null Pointer Exception triggered by GRE + FOU tunnels. This change is now planned to be deployed to all NFRs on a rolling basis.
For our shared backbone platform, we will be scheduling these changes internally and sending out notifications for the work.
Where dedicated backbones are involved, we will be in touch with the customer to schedule the work.
NFR maintenance on hold due to #16
Mai X9 has been updated to backported kernel during separate maintenance window.