Configuring Event Policy

[Contents] [Prev] [Next] [Index] [Report an Error]

Event policies can listen for specific events, create log files, invoke JUNOS commands, and invoke event scripts. This chapter discusses the command-line interface (CLI) statements for configuring event policies.

To configure event policy, include the following statements at the [edit] hierarchy level:




event-options {



destinations {



destination-name {

transfer-delay seconds;



archive-sites {

url password password;
}


}


}





generate-event event-name {

time-interval seconds;

time-of-day hh:mm:ss;
}





policy policy-name {



attributes-match {

event1.attribute-name equals event2.attribute-name; 

event.attribute-name matches regular-expression;

event1.attribute-name starts-with event2.attribute-name;
}



events [ events ];



then {



event-script script-name {



arguments {

parameter-name parameter-value;
}





destination destination-name {

retry-count number retry-interval seconds;

transfer-delay seconds;
}



output-filename filename;

output-format (text | xml);

user-name name
}





execute-commands {



commands {
"command";
}





destination destination-name{

retry-countnumber retry-interval seconds;

transfer-delay seconds;
}



output-filename filename;

output-format (text | xml);

user-name username;
}



ignore;

raise-trap;

upload filename committed destination destination-name;



upload filename filename destination destination-name {

retry-countnumber retry-interval seconds;

transfer-delay seconds;

user-name username;
}


}





within seconds {
 
events [ events ];

not events [ events ];

trigger (after number | on number | until number)
}


}





traceoptions {
file filename <files number> <size size> world-readable
| no-world-readable>;
flag flag;
}


}

This chapter discusses the following topics:

[Contents] [Prev] [Next] [Index] [Report an Error]