≡ Menu

The following JunOS configuration has been tested on PlusNet Fibre broadband running with external BT Openreach Modem. This setup should work with other VDSL/FTTC providers since they use the same underlaying BT infrastructure.

  • The configuration has been tested on SRX210H running JunOS 11.4R9.4 & 12.1X44-D35.5
  • BT Openreach modem connect to interfaces fe-0/0/7 on the SRX

Set the underlaying interface encapsulation to be PPP-Over-Ethernet.

set interfaces fe-0/0/7 unit 0 encapsulation ppp-over-ether

Set PPP Options with Authentication method CHAP.

If your ISP happen to use PAP Authentication method, then you need to reflect that.

set interfaces pp0 unit 0 ppp-options chap default-chap-secret YOUR-PASSWORD
set interfaces pp0 unit 0 ppp-options chap local-name YOUR-USERNAME
set interfaces pp0 unit 0 ppp-options chap no-rfc2486
set interfaces pp0 unit 0 ppp-options chap passive

[click to continue…]

How to Upgrade Juniper SRX

In this case, I will be upgrading an SRX210H. This step is rather straight forward and If you require further clarification, please refer to the appropriate guide from Juniper Network’s Website.

First of all, Copy the JunOS Software into a USB FAT32 Formatted drive.

Make sure you have checked the integrity of the file by runnning md5sum, and compare it with the one listed on Juniper Network’s Website.

nish@WS /media/nish/JunOS $ md5sum junos-srxsme-11.4R9.4-domestic.tgz 
ac7a405477544d4a81b382f9816931d2  junos-srxsme-11.4R9.4-domestic.tgz
nish@WS /media/nish/JunOS $ 

Go into the Shell prompt by issuing the command nish@iNET> start shell if you are not already in there

Check the devices to see before plugging in the USB Drive containing JunOS.

% ls /dev/da*
/dev/da0        /dev/da0s1c     /dev/da0s2c     /dev/da0s3e     /dev/da0s4a
/dev/da0s1      /dev/da0s2      /dev/da0s3      /dev/da0s3f     /dev/da0s4c
/dev/da0s1a     /dev/da0s2a     /dev/da0s3c     /dev/da0s4
% 

[click to continue…]

Juniper SRX Autorecovery Alarm Light

There are various reasons the Alarm light might come on. First to check, why you are seeing the alarm.

System Alarm Info
nish@iNET# run show system alarms 
1 alarms currently active
Alarm time               Class  Description
2013-11-02 01:09:17 GMT  Minor  Autorecovery information needs to be saved

In the above case, it is because Autorecovery information is not saved.

This is accomplished by doing the following command

Saving Autorecovery Info
nish@iNET> request system autorecovery state save 
Saving config recovery information
Saving license recovery information
Saving BSD label recovery information
nish@iNET> 

Router Solicitation Address

This is the address which the clients should transmit for router solicitation.

You can see an example of JunOS DCHP Option 32 address configuration below.

set system services dhcp pool 192.168.1.0/24 option 32 ip-address 192.168.1.33

One of the favourite features about Junos when it comes to configuration management is the ability to manage configuration on a methodical manner. This is where the “COMMIT” configuration comes in and takes care of any unnecessary configuration mistakes which could have been made while performing a certain task.

To quote from Juniper’s website

When you commit the current candidate configuration, you can require an explicit confirmation for the commit to become permanent. This is useful if you want to verify that a configuration change works correctly and does not prevent access to the router. If the change prevents access or causes other errors, the router automatically returns to the previous configuration and restores access after the rollback confirmation timeout passes. This feature is called automatic rollback.

This feature will automatically rollback a “Candidate Configuration” unless the commit confirmed command is entered.

junos commit
[click to continue…]

Copyright © Nish Vamadevan 2002-2017. All Rights Reserved. Terms and Policies.