Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 18 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 2213 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

XG 125 - SFOS 18.0.2 MR-2 Random Rebooting

Carlos Cesario

Hi,

I have one device XG125 with SFOS 18.0.2 MR-2 that re rebooting randomly.

I already checked infrastructure, power cords, no-break, cables but the device still rebooting.

Is there any log file for debug these events? I would check it before open a case.

Regards

Carlos



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

    Hi folks,

    Only to report, even apply V18-MR4 the problem persits.

    :(

  • FormerMember
    0 FormerMember in reply to Carlos Cesario

    Hi ,

    Thank you for the update.

    Could you please run the following command from the console: "system firewall-acceleration show"? If firewall-acceleration is enabled, try to disable it with the following command: "system firewall-acceleration disable"

    I would also suggest you set up a console logging, capture the next reboot event and provide the console logs on your support case to help identify the issue. 

    Console Logging

    ===============

               Note: Though the article explicitly mentioned XG, it is the same details for UTM

               Note: Be sure that the computer in question does not go into Standby or Hibernate while logging

    • Using PuTTY, go to 'Session' - 'Logging'
    • Here, select "All session output', and set the file name to a folder and name for later retrieval.
    • Configure the Serial connection to use the proper COM port on your PC and a Speed of 38400.
    • Start the session, and log in to ensure it is all proper.
    • Once logged in, you can leave it there or log out and leave the session at the password prompt. Either way, leave the session active and allow it to capture the output from the next reboot.
    • Once that reboot occurs, you can end the Serial connection and upload the PuTTY log file on your support case. 

    Thanks,

  • 0 in reply to FormerMember

    Hi

    Thank you by your feedback.

    The firewall-acceleration it is disabled since I moved to V18

    console> system firewall-acceleration show
    Firewall Acceleration is Disabled.
    console>

    About the Console Logging it is a bit difficult to do this, because the device is hosted in a Datacenter and maybe thre are no way to provide this.

    There is any other mode t get/save this!?

    Regards

    Carlos

  • FormerMember
    0 FormerMember in reply to Carlos Cesario

    Hi ,

    Unfortunately, there is no other way to save the console logging. If you can arrange the console logging, that will help us to identify the issue. 

    Thanks,

  • 0 in reply to FormerMember

    Hi 

    Thanks by your feedback. 

    I understand you, but I think that is impossible todo due location where the device is hosted.

    Any tmux/screen alternative cannot be used for this!?

    Regards

    Carlos

  • 0 in reply to Carlos Cesario

    The reboot issues needs to be verified, what is going on in case of the kernel panic happen. Such output will be logged to serial, as SSH etc. will be killed. 

  • 0 in reply to LuCar Toni

    Hi Folks, only to report.

    After a several battlewith support, nothing anormal it was identified, and a new RMA process it was provided.

    Acorrding the support, there are some devices with DIMM memory error, and this affect 0,1% a-0,2% devices.

    Well, I will wait the new device arrive and change it. I hope that will be this

    Carlos

Reply Children
No Data