3.5.6 Number of TCP/UDP port-number detection patterns
The table below describes the capacity limits for the TCP or UDP port number detection patterns used in filter or QoS flow detection conditions. These patterns refer to hardware resources that are used with the port settings in a flow detection condition.
|
Model |
Maximum number per switch |
|---|---|
|
All models |
32 #1NGn #2 |
Legend: n: Number of member switches
- Note #1
-
Enabling VXLAN PMTU function consumes one hardware resource.
- Note #2
-
In a stack configuration, the capacity limits increase according to the number of member switches.
The TCP/UDP port number detection patterns are used with the flow detection condition settings described in the table below. Patterns are not used only at creation of an access list (access-list) or QoS flow list (qos-flow-list). For the TCP/UDP port number detection patterns to be used, apply the created access list and QoS flow list to the interface by using the following configuration commands:
-
ip access-group
-
ipv6 traffic-filter
-
ip qos-flow-group
-
ipv6 qos-flow-group
|
Flow detection condition parameter |
Available specifications |
Receiving-side flow detection mode |
Sending-side flow detection mode |
|---|---|---|---|
|
All modes |
All modes |
||
|
Source port number |
Single specification (eq) |
- |
- |
|
Range specification (range) |
OK |
Not applicable |
|
|
Destination port number |
Single specification (eq) |
- |
- |
|
Range specification (range) |
OK |
Not applicable |
- Legend
-
OK: The TCP/UDP port number detection patterns are used.
- : Do not use TCP/UDP port-number detection pattern
The TCP/UDP port number detection patterns are shared in some cases for the Switch:
-
Filter entries and QoS entries are shared only if there are multiple filter or QoS entries.
-
Patterns are shared between TCP and UDP.
-
Patterns are not shared between source and destination port numbers.
-
Patterns are shared between IPv4- and IPv6-based flow detection conditions.
The following table describes some examples of using the TCP/UDP port number detection patterns.
|
Pattern Usage Example* |
Number of parameters |
Display from the show system operation command (Value for Used of Resources (Used/Max)) |
|---|---|---|
|
Filter entry:
Filter entry:
|
A different range of source port numbers is specified in the two entries.
Therefore, the following two patterns are used: |
2 |
|
Filter entry:
Filter entry:
QoS entry:
|
This is an example of the first type of shared pattern. There are three entries, all of which specify the same range in the destination port number range (10 to 20), so the pattern is shared.
Therefore, the following one pattern is used: |
1 |
|
QoS entry:
QoS entry:
|
This is an example of the second type of shared pattern. There are two entries, both of which share a pattern because they specify the same value in the source port number range (10 to 20).
Therefore, the following one pattern is used: |
1 |
|
QoS entry:
|
This is an example of the third type of pattern, which is not shared. Although the same range is specified, a pattern is not shared between the source port range and the destination port range.
Therefore, the following two patterns are used: |
2 |
|
QoS entry:
QoS entry:
|
This is an example of the fourth type of shared pattern. There are two entries, both of which specify the same range in the source port number range (10 to 20), so the pattern is shared.
Therefore, the following one pattern is used: |
1 |
Note: The values in parentheses are the range of specifiable values when you specify the eq parameter or the range parameter.