SRX Services Gateway
SRX Services Gateway

J-Web broken after Upgrade to 19.4R1.10

a week ago

Hey all,

 

i just got my SRX300-JSE delivered yesterday and upgraded from 15.1X49-D180.2 to 19.4R1.10. Now J-Web doesnt show any policies and zones. instead it displays just a circle saying "please wait, syncing from device" which you can wait hours for and it doesnt do anything.

 

If i do changes on the CLI it works flawless, but i cant do any changes on J-WEB since it doesnt show zones, policies and interfaces etc. In addition the box gets super slow and huge cpu load after clicking a while around in the JWEB Interface and it crashes completly so that only restart web-management helps.

 

I dont really mind since im fine with the command line and i also dont really want to setup the config completly again after i go the ipsec tunnels, sky atp etc. all working.

 

Just curious if someone knows how it may be fixed, is jweb using some own kind of database which is synced from cli config and may be broken now? I dont even find anything strange in the log files, no errors or anything. There must be some way to regenerate it. 

2 REPLIES 2
SRX Services Gateway
Solution
Accepted by topic author flyersa
a week ago

Betreff: J-Web broken after Upgrade to 19.4R1.10

[ Edited ]
a week ago

Hello,

 

can you please check if this thread helps you to resolve your issue?

 

https://forums.juniper.net/t5/SRX-Services-Gateway/SRX340-19-4R1-Firmware-upgrade-issue/td-p/472068

--------------------------------------------------

If this solves your problem, please mark this post as "Accepted Solution".
If you think that my answer was helpful, please spend some Kudos.
SRX Services Gateway

Re: J-Web broken after Upgrade to 19.4R1.10

a week ago

I assume from your description this works correctly in 15.1 and has the issue in 19.4 thus this is going to be a software bug.  These are known as PR (problem reports) in Junos.  I don't see your particular one listed in my searches of the public PR database located here.

 

https://prsearch.juniper.net/InfoCenter/index?page=prsearch

 

You can report this bug via a JTAC ticket and they can confirm if it is already known or create a new PR if needed for the software team to fix the issue.

https://my.juniper.net/#dashboard/servicerequests

 

Steve Puluka BSEET - Juniper Ambassador
IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
http://puluka.com/home