Open ChaosYoda opened 6 months ago
Thank you for your information let's investigate.
I thought I would add the response I got from FS.com
"For the information you provided yesterday, after our internal discussion, the command to modify the SN has been disabled, and even if attempted, the modification will not be successful." This was after following the documentation, the /system/misc/eqsn get, will show the eqsn as the new one ( this is the one that modifies your login information), but if you do /traffic/pon/show onu, then the serial number remains unchanged. This command is apparently not implemented. So I am not exactly sure what the "/system/misc/eqsn set" is supposed to do, but it does not change the onu's S/N , the only impact I have seen is that your login for telnet suddenly changes. The documentation says it changes the series number, but that isn't clear on what that means.
After speaking to FS.com it seems you cannot modify the S/N used in the OLT AUTH, resulting in me having to RMA the device.
Have you tried to see what is sent in the MIBs? I remind you that OLT xgs-pon are much more picky, are you sure it is the wrong s/n and not something else in the ONT that doesn't like OLT?
Well I had FS.com on a teamviewer call to try and figure this out and the result was them saying the device does not support altering the gpon_sn. I wasn't sure how to check the MIBs to be honest.
But in all fairness they didn't exactly understand what I was trying to do.
1) #ONU> traffic/pon/show onu 2) #ONT> system/mib/show 256
As it turns out the fs.com's xgspon cannot update it's gpon_sn, the command described in the guide will only actually change the login to the device, to actually alter the gpon_sn that is used the in Auth process, the command has not been implemented and doesn't work.
I have returned my device based on this. Doing a factory reset or eeprom reset will also ensure the device can no longer be accessed.