Siemens RUGGEDCOM ROX II, User Manual

Page: 369 / 798

RUGGEDCOM ROX II
CLI User Guide
Chapter 9
Layer 3
Viewing Routing Rules 323
Parameter Description
in-vlan Synopsis: A 32-bit signed integer
Identifies the ingress VLAN. To match the rule, the packet's ingress VLAN must match the
number.
out-vlans Synopsis: A 32-bit signed integer
Identifies the egress VLAN. The matched multicast packet is sent to the identified VLAN.
proto Synopsis: An 8-bit unsigned integer
The IP Encapsulated Protocol number. Unless zero is specified, the incoming packet's IP
protocol must match this number.
source Synopsis: { any } or a string
Identifies the source IP address or subnet. To match the rule, the incoming packet's source IP
address must belong to the subnet.
src-port Synopsis: A 32-bit signed integer between 0 and 65535
The port associated with the source flow. A value of 0 means Not Applicable.
destination Synopsis: { any } or a string
Defines the destination IP address or subnet. To match the rule, the incoming packet's
destination IP address must belong to the subnet.
dest-port Synopsis: A 32-bit signed integer between 0 and 65535
The port associated with the destination flow. A value of 0 means Not Applicable.
gateway Synopsis: A string
Defines the nexthop IP address. The matched unicast packet is sent to the identified
gateway.
packets-per-second Synopsis: A 32-bit unsigned integer
Displays the statistical throughput of all packets matching the rule, in packets per second.
static Synopsis: { true, false }
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: { forward, exclude }
The action applied to packets matching the rule:
• Forward: Perform a hardware acceleration.
• Exclude: Exclude from hardware acceleration and always pass matching packets to the
CPU for software routing.
status Synopsis: { active, resolving, pending, excluding }
Whether the rule is currently operational or not:
• Active: The rule is fully operational and can be applied, so hardware acceleration is
performed.
• Resolving: The rule is not operational yet due to some unresolved information, like the
Address Resolution Protocol (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.