Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 26 subscribers
  • Views 15547 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

portMGMT Unplugged after 16.05.03 MR-3

@wajdiaa

Hi,

After applying firmware upgrade 16.05.03 MR-3, the peer administration port (portMGMT in XG-430) used in HA active-passive mode is detected as "unplugged".

I know, check wiring, etc. But it was active a few seconds before installing and the devices are at a data center with hardly any human access so all points to a bug in the release or the process itself (unless otherwise it is proven innocent) ;-).

I've tried to switch off the interface (put to "none") and back but being in HA, I would have to undo the feature first which I'm not sure if it'll help in the first place. Any hints?

Thanks!



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to @wajdiaa

    Hi WajdiAyach, 

    I would need two things from your device ,

    1. Snap Shot of the port with the connected ethernet cable connected to a system and Check if the LED is blinking or not. 

    2. I would need Output of Syslog.log and dmesg 

    Command in Shell Access 

    cat /log/syslog.log

    dmesg

Children
  • 0 in reply to Aditya Patel

    Hi Aditya,

    Support already did a connection this afternoon and rescued the files requested. Jaydeep (2 floors below you :-)) is working on the case if you'd like to follow-up. Tomorrow we'll continue since we're requesting access to the data center. I'm sending you the extraction in any case.

    Thanks again!

  • 0 in reply to @wajdiaa

    Hi again,

    Just to let you all know that the interface is up again after a reboot!

    Thank you all for your help!

  • 0 in reply to @wajdiaa

    Hi WajdiAyach, 

    According to the logs provided, we could not determine the issue. As your Device was in HA a reboot would be an issue . But Since you were ready for a Reboot, that was a recommended action to resolve your issue.  If you face the issue again , I would recommend enabling FSCHECK on your console.

    The command to Enable|Disable|Status FSck Console> system fsck-on-nextboot on|off|show