Juniper SRX5600, Руководство по оборудованию

Страница: 368 / 483

{secondary:node0}
root@node0> show configuration system scripts
set system scripts commit file interface-monitoring-check.slax
set system scripts op file srx-monitor.xsl
root@node0> show configuration event-options
{secondary:node0}
root@node0> show configuration event-options
set event-options generate-event 60s time-interval 60
set event-options policy NAT-POOL-UTIL events 60s
set event-options policy NAT-POOL-UTIL then event-script
srx-nat-bucket-overload.slax arguments utilization-threshold 90
set event-options policy NAT-POOL-UTIL then event-script
srx-nat-bucket-overload.slax arguments pool GLOBAL
set event-options event-script traceoptions file escript.log size 1m files 2
set event-options event-script traceoptions flag output
set event-options event-script file srx-monitor-addbook-policy-count.slax
f. If any scripts are referenced in the configuration, then back up these scripts:
root@node0# scp /var/db/scripts/commit/commit-script.slax root@node1-fxp0-ip:
/commit-script.slax
4. Install the replacement Routing Engine:
a. Power off node 0:
root@node0> request system power-off
b. Wait until a message appears on the console confirming that the services have stopped, and then
physically turn off the power.
c. Label and disconnect all the cables connected to node 0.
d. Replace the Routing Engine.
e. To prevent a split-brain scenario (where the control link is connected while both the nodes are in
the primary state), reconnect only the console cable and the cable to the fxp0 interface. Leave the
rest of the cables disconnected.
f. Ensure that the status of the control link and fabric link on node 1 is down:
root@node1> show chassis cluster interfaces
371