after editing save things like
# commit confirmed
and if every works as use planned to? confirm the configration with
# commit
otherwise the new configuration will be automatically rollback if not confirmed.
dd if=/dev/zero of=/dev/rad3 count=20 dd if=install-media-5.4R3.2-domestic of=/dev/rad3 bs=64k
#!/bin/bash # junos bash policer # http://tnt.aufbix.org/ echo if [ $# -lt 2 ]; then echo 1>&2 "$0: not enough arguments" echo echo "example:" echo -e "1gb =\t./junos_policer\t1gb\t1000000000" echo -e "100mb =\t./junos_policer\t100mb\t100000000" echo -e "1mb =\t./junos_policer\t1mb\t1000000" exit 0 fi echo cir=$(($2/1000*500/8)) if (( $cir < 15000 )); then cir=15000 fi echo "set firewall policer $1 logical-interface-policer" echo "set firewall policer $1 if-exceeding bandwidth-limit $2" echo "set firewall policer $1 if-exceeding burst-size-limit $cir" echo "set firewall policer $1 then discard"
original: The Data Plumber
To check this out do the following:
1. start shell 2. sysctl machdep.bootdevs
This second command will tell you the order in which devices are booted from. If ‘disk’ is absent from that list, you need to add it back in and reboot the routing-engine. Do the following:
su root (you’ll need the root password for this) sysctl -w machdep.bootdevs=usb,compact-flash,disk,lan Exit from the shell and reboot the RE.
The above is for an MX960 with an RE-2000 installed, and the device names change a bit depending on what you are using. Best to check it against another working system if you can.
Here’s a cut-and-paste from my MX960:
root@MX960-RE1% sysctl machdep.bootdevs machdep.bootdevs: usb,compact-flash,lan root@MX960-RE1% sysctl -w machdep.bootdevs=usb,compact-flash,disk,lan machdep.bootdevs: usb,compact-flash,lan -> usb,compact-flash,disk,lan root@MX960-RE1% exit exit % sysctl machdep.bootdevs machdep.bootdevs: usb,compact-flash,disk,lan % exit