Unsupported Actions for Firewall Filters in Logical Systems
Table 1 describes
the firewall filter actions that are supported at the [edit firewall] hierarchy
level, but not supported at the [edit logical-systems logical-system-name firewall] hierarchy level.
Firewall Filter Action |
Example |
Description |
|---|---|---|
| Terminating Actions Not Supported in a Logical System | ||
|
[edit]
logical-systems {
ls1 {
firewall {
family inet {
filter foo {
term one {
from {
source-address 10.1.0.0/16;
}
then {
logical-system fred;
}
}
}
}
}
}
}
|
Because the |
| Nonterminating Actions Not Supported in a Logical System | ||
|
[edit]
logical-systems {
ls1 {
firewall {
family inet {
filter foo {
term one {
from {
source-address 10.1.0.0/16;
}
then {
ipsec-sa barney;
}
}
}
}
}
}
}
|
Because the |
|
[edit]
logical-systems {
ls1 {
firewall {
family inet {
filter foo {
term one {
from {
source-address 10.1.0.0/16;
}
then {
next-hop-group fred;
}
}
}
}
}
}
}
|
Because the |
|
[edit]
logical-systems {
ls1 {
firewall {
family inet {
filter foo {
term one {
from {
source-address 10.1.0.0/16;
}
then {
port-mirror;
}
}
}
}
}
}
}
|
Because the |
|
[edit]
logical-systems {
ls1 {
firewall {
family inet {
filter foo {
term one {
from {
source-address 10.1.0.0/16;
}
then {
sample;
}
}
}
}
}
}
}
|
In this example, the |
|
[edit]
logical-systems {
ls1 {
firewall {
family inet {
filter icmp-syslog {
term icmp-match {
from {
address {
192.168.207.222/32;
}
protocol icmp;
}
then {
count packets;
syslog;
accept;
}
}
term default {
then accept;
}
}
}
}
}
}
|
In this example, there must be at least one system log ( Because this firewall configuration relies on a configuration outside the logical system,
the |