
Using Technician Interface Software
8-14
2.
Define a slot mask for delayed boot services on the router.
Before creating the delayed boot service on the router, define a slot mask for
the RUIBOOT entity. The slot mask identifies the slots on which the system
will load and run RUIBOOT. At the Technician Interface prompt, enter
BN [3]: set wfServices.wfRuiBootLoad.0 0x7FFE0000;commit
This command allows RUIBOOT, once created, to run on all slots. The
hexadecimal value
0x7FFE0000 works for any model of Bay Networks
router, regardless of the number of slots in that router.
3. Create a delayed boot service on the router.
Create the RUIBOOT service in the router configuration, as follows:
BN [3]: set wfRuiBoot.wfRuiBootBaseDelete.0 1;commit
This also enables delayed boot services on the router. (The system sets the
attribute wfRuiBootBaseDisable, OID = 1.3.6.1.4.1.18.3.3.2.14.1.1, in the
RUIBOOT base record to its default value of 1 or enabled.)
Scheduling Delayed Boot Events
You can schedule a delayed boot event on a router as follows:
1. Log in to the router’s Technician Interface.
Log in to the Technician Interface of the router you want to configure with a
delayed boot event. If you need instructions on how to perform a login via local
console or remote Telnet session, refer to Chapter 1, then resume the procedure
for scheduling a delayed boot event.
2. Schedule a delayed boot event.
To schedule a delayed boot event, you must first create (add) an entry in the
RUIBOOT table of delayed boot events, as follows:
BN [3]: set wfRuiBootTable.wfRuiBootDelete.
<wfRuiBootDateAndTime>
1
BN [3]: commit
Comentarios a estos manuales