I have a brand new SRX320. I pulled it out, assembled it, plugged it in, and attempted to follow the "How to Set Up Your SRX320 Services Gateway".
I got a 192.168.1.2 address on port 5--which is *NOT* what the documentation claims.
Okay, so I moved my connection to port 1 and attempted to get to J-Web on 192.168.1.1--but there was no web server on that.
Okay, so I pull out my serial cable, connect to the management port, and look at the configuration--which bears no resemblance to what the documentation claims the setup should be.
Did I screw something up when I plugged the hardware in? Was I supposed to hold down a button somewhere?
I managed to get the web management stuff enabled from the serial console after poking at things for about 5 hours, but something seems really broken. If I screwed up, please tell me where I failed. Or, somebody at Juniper really needs to go back over their documentation.
Well, unfortunately, sometimes the documentation needs some further review and corrections. So lets get this straight.After plugging up the SRX and connecting to "any of thenetwork ports numbered 0/1 through 0/5 to the Ethernet port on themanagement device, using an RJ-45 cable", and setting your labtop to DHCP, you got an IP 192.168.1.2?Step 2 says ....:" if you are connected to port 0/1(or any port thru 0/5 - my addition based on step 1), then the IP address of themanagement device should be from the 192.168.1.x network.So your IP of 192.168.1.2 is correct and the doc is right up to this point. Did you ping 192.168.1.1 (just for verification sake)?The next step is: Access the J-Web interface using the URL http://192.168.x.1, where x is the port number to which you are connected on the services gateway.So in your case it would be http://192.168.5.1.Now this is quite strange, because normally it would be to go to J-Web: "http://192.168.1.1"So what happened when you tried 5.1? This is quite interesting?
This is problem on some of the first shipped devices where the factory shipped config in no way matched the provided documentation. looked like a config for performance/systest which slipped into ordinary production.
Best suggestion from here is to upgrade the device via usb to at least 15.1X49-D110 and run a "request system zeroize" afterwards. After the reboot, the quick start guide should match.
USB upgrade via cli: https://kb.juniper.net/InfoCenter/index?page=content&id=KB16652&actp=METADATA#cli_stick