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.
Содержание RUGGEDCOM ROX II
Страница 2: ...RUGGEDCOM ROX II CLI User Guide ii ...
Страница 4: ...RUGGEDCOM ROX II CLI User Guide iv ...
Страница 39: ...RUGGEDCOM ROX II CLI User Guide Table of Contents xxxix 19 5 VLANs 752 ...
Страница 40: ...Table of Contents RUGGEDCOM ROX II CLI User Guide xl ...
Страница 46: ...Preface RUGGEDCOM ROX II CLI User Guide xlvi Customer Support ...
Страница 96: ...Chapter 2 Using RUGGEDCOM ROX II RUGGEDCOM ROX II CLI User Guide 50 Accessing Maintenance Mode ...
Страница 170: ...Chapter 5 System Administration RUGGEDCOM ROX II CLI User Guide 124 Deleting a Scheduled Job ...
Страница 256: ...Chapter 6 Security RUGGEDCOM ROX II CLI User Guide 210 Enabling Disabling a Firewall ...
Страница 402: ...Chapter 11 Wireless RUGGEDCOM ROX II CLI User Guide 356 Managing Cellular Modem Profiles ...
Страница 646: ...Chapter 13 Unicast and Multicast Routing RUGGEDCOM ROX II CLI User Guide 600 Deleting a Multicast Group Prefix ...
Страница 732: ...Chapter 15 Network Discovery and Management RUGGEDCOM ROX II CLI User Guide 686 Viewing NETCONF Statistics ...
Страница 790: ...Chapter 17 Time Services RUGGEDCOM ROX II CLI User Guide 744 Deleting a Broadcast Multicast Address ...