Thread Info
  • State Suggested Answer
  • +6 person also asked this people also asked this
  • Locked Locked
  • Replies 47 replies
  • Answers 4 answers
  • Subscribers 46 subscribers
  • Views 25622 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

v18 MR-1 killing all traffic

Gary Parr

I loaded MR-1, everything was fine for a while then suddenly all traffic dropped. I could still get into XG itself and nothing looked wrong, so I thought it was an upstream device. I rebooted those but still nothing. Rebooted XG and suddenly everything started working again. No more than 15 minutes later, all traffic died again. This time I spent some time looking at the XG logs but nothing stood out. No services were reported down and all interfaces and gateways reported as up. I have since reverted back to GA build 354 and all again is right with the world. When I have some time I can push MR-1 back on and dig some more, but wanted to share in case anyone else has had a similar experience.



This thread was automatically locked due to age.
Parents
  • 0

    I know this is the MR-1 thread and I've never installed it but I just had an episode where my WAN traffic stopped passing traffic. I'm running 18.0.0 GA-Build379.HF052220.1 with about 20 days uptime. I could successfully ping the device but couldn't SSH or access the WebUI. I tried to console but the screen was blank. I ended up pulling the power to restore access. From the system graphs the CPU was under considerable load by the System stat or kernel space. I couldn't find anything in the logviewer around the time the issue happened.

Reply
  • 0

    I know this is the MR-1 thread and I've never installed it but I just had an episode where my WAN traffic stopped passing traffic. I'm running 18.0.0 GA-Build379.HF052220.1 with about 20 days uptime. I could successfully ping the device but couldn't SSH or access the WebUI. I tried to console but the screen was blank. I ended up pulling the power to restore access. From the system graphs the CPU was under considerable load by the System stat or kernel space. I couldn't find anything in the logviewer around the time the issue happened.

Children