32. Layer 3 Switching
ROX™ v2.2 User Guide
367
RuggedBackbone™ RX1500
Synopsis: A string conforming to: "(([0-1]?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])\.){3}([0-1]?[0-9]?[0-9]|
2[0-4][0-9]|25[0-5])/\p{N}+"
Synopsis: string - the keyword { any }
Identifies the source IP address or subnet. To match the rule, the incoming packet's source IP
address must belong to the subnet.
destination
Synopsis: IPv4 address in dotted-decimal notation
Synopsis: A string conforming to: "(([0-1]?[0-9]?[0-9]|2[0-4][0-9]|25[0-5])\.){3}([0-1]?[0-9]?[0-9]|
2[0-4][0-9]|25[0-5])/\p{N}+"
Synopsis: string - the keyword { any }
Defines the destination IP address or subnet. To match the rule, the incoming packet's destination
IP address must belong to the subnet.
gateway
Synopsis: IPv4 address in dotted-decimal notation
Defines the nexthop IP address. The matched unicast packet is sent to the identified gateway.
The address of the next-hop. The matched unicast packet is sent to the out-vlan. This is the list of
VLANs the matched multicast packet will be sent to.
Pkts/sec
Synopsis: unsigned integer
Displays the statistical throughput of all packets matching the rule, in packets per second.
static
Synopsis: boolean
Whether the rule is static or dynamic.Static rules are configured as a result of management activity.
Dynamic rules are automatically learned by the device and can be unlearned subject to Aging Time
routing-action
Synopsis: string - one of the following keywords { exclude, forward }
Action applied to packets matching the rule:
• Forward : perform hardware acceleration.
• Exclude : exclude from hardware acceleration and always pass matching packets to the CPU
for software routing.
status
Synopsis: string - one of the following keywords { excluding, pending, resolving, active }
Whether the rule is currently operational or not:
• Active : rule is fully operational and can be applied, so hardware acceleration is performed.
• Resolving : rule is not operational yet due to some unresolved information, like ARP or gateway's
MAC address in the MAC Address Table. Hardware acceleration is not performed.
• Pending : there are not enough hardware resources to setup the rule and all its dependencies.
Hardware acceleration is not performed.
Insufficient - there are not enough hardware resources to set up the rule and all its dependencies.
Hardware routing is not performed.
