juniper srx: useful commands

Will update this post as I find useful commands.

Reset dynamic VPN due to connectivity issues: restart ipsec-key-management

Show logged on users: show system users
Logout connected user: request system logout user username terminal session

Show open sessions: show security flow session
View running Junos applications: show configuration groups junos-defaults applications
Show current sessions: show security flow session

Show system snapshot: show system snapshot media internal
Show system software backup: show system software backup

Delete autorecovery config: request system autorecovery state clear
Save autorecovery config: request system autorecovery state save

Delete rescue config: request system configuration rescue delete
Save rescue config: request system configuration rescue save

Upgrade bootloader: go to shell by typing “start shell” in cli
bootupgrade –u /boot/uboot –l /boot/loader

View BIOS version: show chassis routing-engine bios
View BIOS version and available upgrade: show system firmware
View current and upgrade BIOS with backup: request system firmware upgrade re bios backup
Check status of BIOS upgrade: show system firmware

View contents of a directory: file list directory
Show system directory usage: show system directory-usage /cf
Check disk space: show system storage detail
View contents of a directory: file list directory
Delete a file: file delete /var/tmp/xyz

Cleanup storage space: request system storage cleanup
Delete upgrade package backup: request system software delete-backup

Show device name, model and software version: show version

Upgrade software through ssh: put a copy of Junos software on a ftp location your device can access upon connecting (do not put where you have to browse to after connection). This needs to be done right after you are logged on to the device, and not in cli.

Login to ftp: ftp ip
Change directory to /var/tmp: lcd /var/tmp
Type bin and hit enter
Command to download the file to device: get junos-srxsme-12.1X46-D40.2-domestic.tgz
Type bye to exit ftp mode when file is downloaded successfully and go to cli.
Invoke the following command to install: request system software add no-copy /var/tmp/junos-srxsme-12.1X46-D40.2-domestic.tgz
Install may take a hot minute so be patient. Once this is complete reboot your device: request system reboot

Juniper Junos: change timeout settings for ssh/telnet/web console

To change application timeout:
cli/configure
ssh: set applications application junos-ssh inactivity-timeout 1440
telnet: set applications application junos-telnet inactivity-timeout 1440
web: set system services web-management session idle-timeout 1440

Note: auto complete does not work after application, so you will have to type it all in.

To view timeout settings, exit to cli
start shell user root
vty fwdd
show usp app-def tcp

And you’re done.

Juniper: Create a policy based VPN tunnel between two sites for NetScreen devices

Juniper devices are my personal favorites. While they are as robust and complicated as Cisco they are being sold at a fraction of what Cisco sells their similar products. We are currently using Netscreen and SA boxes exclusively to provide secure VPN connection between our 20+ offices across the US.

While Netscreen built-in help is quite comprehensive and easy to follow, it does not eliminate the need for a rookie to quickly setup a tunnel between two locations. I am going to cut the extra steps out of these instructions, and assuming you already have it setup and have Internet connection I jump right to the quick and dirty tunnel setup.

Almost all Netscreen devices, even the oldest and cheapest models are VPN capable. Most older models like NS5 have one trust (WAN side) and one untrust (LAN side). From this point forward I will refer to LAN and WAN connection as trust and untrust. Devices like NS5GT have a 4 port router built-in through which you can directly connect multiple computers to trust ports. However, it is also possible to isolate those ports and set them as untrust/trust (default mode), home/work (two home and two work ports to separate work and home networks), dual untrust (redundant WAN), and combined (redundant untrust, two home and one work zones). We will be covering the default port mode which is trust/untrust port mode. I just give you a tip if you decide to setup a home/work zone: once you are done with your tunnels you will have to create policies to allow access from home to work or the other way around!

This tutorial explains a quick and dirty setup to create a VPN tunnel between two NS5GT devices. If I don’t explain an options it means it’s not absolutely necessary for a VPN tunnel, so leave it alone and play around with them once you’ve learned how it’s done. Basics are all the same and can be found in pretty much the same spot on different devices. Here are given values:

Site A:
WAN IP: http://8.8.8.1/27″ href=”http://8.8.8.1/27″>8.8.8.1/27
LAN IP: http://10.10.0.0/22″ href=”http://10.10.0.0/22″>10.10.0.0/22

Site B:
WAN IP: http://8.8.9.1/26″ href=”http://8.8.9.1/26″>8.8.9.1/26
LAN IP: http://192.168.36.0/24″ href=”http://192.168.36.0/24″>192.168.36.0/24

Steps are identical on both devices, except when you will have to enter WAN and LAN info. So basically you will have to follow the steps below on both devices. I am going to start with the device installed in Site A:

Expand Policies – Policy Elements – Addresses and click on List.
With Untrust zone selected, click New.
Give your site a name and Enter LAN information for Site B in IP box (Site A for device installed in Site B): http://192.168.36.0/24″ href=”http://192.168.36.0/24″>192.168.36.0/24. If you don’t know what /24 means simply enter your subnet mask in its entirety (255.255.255.0). Leave zone as Untrust and click OK.
Now in Addresses screen, select Trust from pull down menu and hit New. Then enter LAN info for the site in which your device is installed (Site A, Site B for device installed in Site B). Same procedure as step 3 above.
Expand VPNs – AutoKey Advanced and click on Gateway.
Click New.
Give your Gateway a name, enter Site B WAN address (Site A for device installed in Site B): http://8.8.9.1/26″ href=”http://8.8.9.1/26″>8.8.9.1/26. Leave everything else alone, then click Advanced.
Enter a preshared key. That’s basically a password to secure communications between the VPN devices. This password should be the same for both Sites A and B.
Select your local interface on which your VPN tunnel will operate, which is your WAN port. If you’re not sure which port is your WAN, expand Network – Interfaces and click List. Interface assigned to your public IP is the one you need.
The simplest tunnel will be Predefined, Standard. For more complicated algorithm you can select User Defined, Custom. Since it’s a quick and dirty tutorial we are going to use Predefined.
Click Return to go back, then click OK.
Under the same menu (VPNs) click on AutoKey IKE.
Click New.
Give your VPN a name, like “Site A to Site B”.
You should now see “Site B” in Predefined Remote Gateway box – select it.
Leave everything else in that screen alone and click Advanced.
If you want VPN monitoring check the box VPN Monitor towards the bottom of the screen. Hit return and then OK.

At this point our VPN tunnel is complete. However, to allow access from one site to the other, we will have to create a policy.

Expand Policy and click on Policies.
At top, for “From” field select Untrust and for “To” select Trust from the pull down menus, then hit New.
Give your policy a name (optional).
In Source Address, select Site B from pull down menu (Site A for device installed in Site B).
In Destination, select Site A (Site B for device installed in Site B).
In action, select Tunnel.
In Tunnel, select the VPN name you chose in step 14 above.
If you want to allow bi-directional access, check the box next to Modify matching bidirectional VPN. Leave that box unchecked if you’d like to have a one way policy to allow access from Site A to B, but not the other way around.
If you want to enable logging, check the appropriate box.
Click OK.

w00t… you’re done. Once you complete the steps in both sites you should be able to ping Site B computers from Site A and vice versa!