Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 4359 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

pattern updates not working

TarekHalloun

Hello

i have an xg 125 and since may 10 it is not updating pattern , i get Failed to check for pattern updates

internet is present , the xg works as a gateway

i even tried adding an allow all just for the appliance but in vain 

i rebooted , updated firmware , ping is ok ,  but still same issue

opened a ticket with support since more than a week but they barely done anything ( very bad paid support )

what to check ?!



This thread was automatically locked due to age.
Parents
  • 0 in reply to LuCar Toni

    Hi Tony - there is no update.log or sig_update.log ..only u2d.log .. but it is showing a different ip 192.168.130.2(different XG) instead of 192.168.120.2

     

    XG125_XN02_SFOS 17.5.5 MR-5# tail -f /log/u2d.log                               
    DEBUG     May 27 09:25:28 [3857]: --sfmversion = --oem                          
    DEBUG     May 27 09:25:28 [3857]: Added new server : Host - 192.168.130.2, Port 
    - 8443                                                                          
    DEBUG     May 27 09:25:28 [3857]: Final query string is :                       
    ?&serialkey=C16064BXT94CX09&deviceid=850397e28d24132d4bc51b894399164c0205&fwvers
    ion=17.5.5.433&productcode=CN&appmodel=XG125&appvendor=XN02&useragent=SF&oem=&pk
    g_sysupdate_version=6&sfmversion=--oem                                          
    DEBUG     May 27 09:25:43 [3857]: Response code : 0                             
    DEBUG     May 27 09:25:43 [3857]: Response body :                               
                                                                                    
    DEBUG     May 27 09:25:43 [3857]: Response length : 0                           
    ERROR     May 27 09:25:43 [3857]: Response not parsed successfully.             
    ERROR     May 27 09:25:43 [3857]: FATAL : Error in parsing response, exiting.   




  • 0 in reply to TarekHalloun

    well your advice made me search for this ip and lo and behold the appliance had its central management enabled pointing to 192.168.130.2 ...how i dont know ..why didnt support also see it i still dont know ..

    after disabling SFM pattern updates works 

    thank you

Reply Children
No Data