ASF and Buffer ASF Examples
This section provides you different use case examples for non-buffered and buffered ASF configurations.
For non-buffered ASF examples refer to the following :
For buffered ASF examples refer to the following:
Example 1: ASF, Forward TCP Traffic
In Example 1, ASF is used with GigaSMART Load Balancing and Adaptive Packet Filtering to load balance TCP traffic among multiple tool ports. TCP SYN indicates the start of a connection. Once the TCP SYN packet is detected, subsequent packets belonging to the same TCP connection will be forwarded to a configured tool port. Packets belonging to the same connection will be sent to the same tool port, regardless of the number of connections.
Note: This example uses APF to filter TCP packets to capture the SYN packet. Alternatively, use buffer ASF to capture a whole session by buffering packets.
|
Task
|
Description
|
UI Steps
|
|
1
|
Create a flow session.
|
|
1.
|
From the device view, select GigaSMART > ASF. |
|
3.
|
Type asf4 in the Alias field. |
|
4.
|
Select ipv4-tuple from the Session field list. |
|
|
2
|
Create a port group and specify the tool ports for load balancing.
|
|
1.
|
Select Ports > Port Groups > All Port Groups. |
|
3.
|
Type portgrp1 in the Alias field. |
|
5.
|
Select SMART Load Balancing. |
|
6.
|
Click in the Ports field and select the tool ports. For example, 1/1/x6,1/1/x7,1/2/x3, and 1/2/x4. |
|
|
3
|
Configure a GigaSMART group and associate it with GigaSMART engine ports.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type gsgrp1 in the Alias field. |
|
4.
|
Select two engine ports from the Port List field. For example, 1/3/e1 and 1/3/e2 |
|
|
4
|
Configure the combined GigaSMART operation.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operation and create two GigaSMART Operations. |
|
3.
|
Type gsop1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
5.
|
Select the operations. |
|
o
|
ASF with asf4 for the ASF profile |
|
o
|
Load Balancing with Stateful Type ASF, and Round Robin |
|
|
5
|
Create a virtual port and associate it with the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > Virtual ports. |
|
3.
|
Enter vp1 in the Alias field. |
|
4.
|
Select gsg1 from the GigaSMART Groups list. |
|
|
6
|
Create a first level map.
|
|
1.
|
Select Maps > Maps > Maps. |
|
a.
|
Type map11 in the Alias field. |
|
b.
|
Select First Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the network port 1/1/x1 for the Source. |
|
e.
|
Select the virtual port vp1 for the Destination. |
|
c.
|
Select IPv4 Version and set version to 4 |
|
|
7
|
Create a second level map. The gsrule captures the first packet of a session.
|
|
a.
|
Type map22 in the Alias field. |
|
b.
|
Select Second Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the virtual port vp1 for the Source. |
|
e.
|
Select the port group portgrp1 for the Destination. |
|
f.
|
Select gsop1 form the GSOP list. |
|
Example 2: ASF, Forward VNC Traffic
In Example 2, traffic from a Virtual Network Computing (VNC) application is forwarded from network port 1/1/x1 to tool port 1/1/x6. Packets will be matched with a VNC signature. Once a packet is matched, subsequent packets with the same IPv4 5tuple will be forwarded to the same destination as the matching packet. By default, both the forward and the reverse traffic of the same session will be captured and forwarded.
|
Step
|
Description
|
Command
|
|
1
|
Create a flow session.
|
|
1.
|
From the device view, select GigaSMART > ASF. |
|
3.
|
Type asf1 in the Alias field. |
|
4.
|
Select ipv4-tuple from the Session field list. |
|
|
2
|
Configure a GigaSMART group and associate it with GigaSMART engine ports.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type gsgrp1 in the Alias field. |
|
4.
|
Select two engine ports from the Port List field. For example, 1/3/e1 and 1/3/e2 |
|
|
3
|
Configure the combined GigaSMART operation.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operations and create two GigaSMART Operations. |
|
3.
|
Type gsop1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
5.
|
Select the operations. |
|
o
|
ASF with asf1 for the ASF profile |
|
|
4
|
Create a virtual port and associate it with the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > Virtual ports. |
|
3.
|
Enter vp1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
|
5
|
Create a first level map.
|
|
1.
|
Select Maps > Maps > Maps. |
|
a.
|
Type map11 in the Alias field. |
|
b.
|
Select First Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the network port 1/1/x1 for the Source. |
|
e.
|
Select the virtual port vp1 for the Destination. |
|
c.
|
Select IPv4 Version and set Version to 4 |
|
|
6
|
Create a second level egress map. The gsrule contains the VNC signature.
|
|
a.
|
Type map22 in the Alias field. |
|
b.
|
Select Second Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the virtual port vp1 for the Source. |
|
e.
|
Select the port group portgrp1 for the Destination. |
|
f.
|
Select gsop1 form the GSOP list. |
|
d.
|
Select regex for Type and enter ^rfb 00[1-9]\.00[0-9]\x0a$ |
|
e.
|
Set Offset from 16 to 1000 |
|
Example 3: ASF, Forward Traffic Matching a Pattern
In Example 3, the traffic that matches a particular pattern (ymsg|ypns|yhoo) is forwarded from network port 1/1/x1 to tool port 1/1/x6 after adding a VLAN tag. Packets will be matched with the special signature. Once a packet is matched, subsequent packets with the same source IP, source port, and VLAN ID will be forwarded to the same destination as the matching packet (after the VLAN header is inserted). By default, both the forward and the reverse traffic of the same session will be captured and forwarded.
|
Task
|
Description
|
UI Steps
|
|
1
|
Create a flow session and other parameters.
|
|
1.
|
From the device view, select GigaSMART > ASF. |
|
3.
|
Type asf2 in the Alias field. |
|
5.
|
Set Number of packets to 50. |
|
6.
|
Set the session field. |
|
o
|
Select vlan-id position 1 |
|
|
2
|
Configure a GigaSMART group and associate it with GigaSMART engine ports.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type gsgrp1 in the Alias field. |
|
4.
|
Select two engine ports from the Port List field. For example, 1/3/e1 and 1/3/e2 |
|
|
3
|
Configure the GigaSMART operation.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operation and create two GigaSMART Operations. |
|
3.
|
Type gsop1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GS Groups list. |
|
5.
|
Select the operations. |
|
o
|
Adaptive Packet Filtering |
|
o
|
Add Header and set VLAN to 1000 |
|
o
|
ASF with asf2 for the ASF profile |
|
|
4
|
Create a virtual port and associate it with the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > Virtual ports. |
|
3.
|
Enter vp1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
|
5
|
Create a first level map.
|
|
1.
|
Select Maps > Maps > Maps. |
|
a.
|
Type map11 in the Alias field. |
|
b.
|
Select First Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the network port 1/1/x1 for the Source. |
|
e.
|
Select the virtual port vp1 for the Destination. |
|
c.
|
Select IPv4 Version and set Version to 4 |
|
|
6
|
Create a second level map. The gsrule contains the special signature.
|
|
a.
|
Type map22 in the Alias field. |
|
b.
|
Select Second Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the virtual port vp1 for the Source. |
|
e.
|
Select the too port 1/1/x6 for the Destination. |
|
f.
|
Select gsop1 form the GSOP list. |
|
d.
|
Select regex for Type and enter (ymsg|ypns|yhoo) |
|
e.
|
Set Offsett from 16 to 1000 |
|
Example 4: ASF, Forward GTP Traffic
In Example 4, GTP traffic from network port 1/1/x1 is load balanced based on inner IP and tunnel ID to four tool ports: 1/1/x6, 1/1/x7, 1/2/x3, and 1/2/x4. APF filters GTP-u packets. Once a packet is matched, subsequent packets in the same direction with the same gtpu-teid and inner IP will be forwarded to the same destination as the matching packet. In Example 4, both the outer and inner IP are IPv4.
|
Task
|
Description
|
UI Step
|
|
1
|
Create a flow session and other parameters.
|
|
1.
|
From the device view, select GigaSMART > ASF. |
|
3.
|
Type asf3 in the Alias field. |
|
5.
|
Set the session field. |
|
|
2
|
Create a port group and specify the tool ports for load balancing.
|
|
1.
|
From the left navigation pane, go to System > Ports > Ports > Port Groups > All Port Groups. |
|
3.
|
Type portgrp1 in the Alias field. |
|
5.
|
Select SMART Load Balancing. |
|
6.
|
Click in the Ports field and select the tool ports. For example, 1/1/x6,1/1/x7,1/2/x3, and 1/2/x4. |
|
|
3
|
Configure a GigaSMART group and associate it with GigaSMART engine ports.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type gsgrp1 in the Alias field. |
|
4.
|
Select two engine ports from the Port List field. For example, 1/3/e1 and 1/3/e2 |
|
|
4
|
Configure the combined GigaSMART operation.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOPS) > GigaSMART Operation and create two GigaSMART Operations. |
|
3.
|
Type gsop1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
5.
|
Select the operations. |
|
o
|
Adaptive Packet Filtering |
|
o
|
ASF with asf3 for the ASF profile |
|
o
|
Load Balancing with Stateful, Type ASF, and Least Conn |
|
|
5
|
Create a virtual port and associate it with the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > Virtual ports. |
|
3.
|
Enter vp1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
|
6
|
Create a first level map.
|
|
1.
|
Select Maps > Maps > Maps. |
|
a.
|
Type map11 in the Alias field. |
|
b.
|
Select First Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the network port 1/1/x1 for the Source. |
|
e.
|
Select the virtual port vp1 for the Destination. |
|
c.
|
Select IPv4 Protocol and set Value to UDP. |
|
d.
|
Select Port Destination and set the port value to 2152 |
|
|
7
|
Create a second level map.
|
|
a.
|
Type map22 in the Alias field. |
|
b.
|
Select Second Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the virtual port vp1 for the Source. |
|
e.
|
Select the port group portgrp1 for the Destination. |
|
f.
|
Select gsop1 form the GSOP list. |
|
d.
|
Select IPv4 Protocol and enter the IPv4 address. Set Position to 1. |
|
e.
|
Select Ipv4 Destination and set the port value to 2152. Set Position to 1. |
|
Example 1: Buffer ASF, Drop Netflix Traffic
In Example 1, the goal is to drop all Netflix traffic. The flow session is defined by the 5tuple field and the first occurrence of VLAN ID. The Netflix traffic is expected to be identified in the first 6 packets of a session. (Configure the maximum number of packets buffered before the match to 5.) A maximum of 3 million sessions is specified.
|
Task
|
Description
|
UI Steps
|
|
1
|
Configure a GigaSMART group and associate it with GigaSMART engine ports and Define the maximum number of sessions, in millions.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type gsgrp1 in the Alias field. |
|
4.
|
Select two engine ports from the Port List field. For example, 1/3/e1 and 1/3/e2 |
|
5.
|
Under Params Resource Buffer select ASF and set the Buffer size to 3. |
|
|
2
|
If needed, reload the GigaSMART line card or module to allocate the resources for buffer ASF.
|
If you reset the buffer size of an ASF profile in Task 1, go to the Chassis page and select Table View. Under Cards, select the card to reload. From the Actions menu, select Shut Down and then Start Up.
You can also issue the following CLI commands to reboot the card (the card is in slot 3 in this example):
(config) # card slot 3 down
(config) # no card slot 3 down
|
|
3
|
Create a flow session, specify the buffer count before the match, and enable buffering.
Note: The default protocol is TCP, so it does not need to be specified.
|
|
1.
|
From the device view, select GigaSMART > ASF. |
|
2.
|
Click New or select an existing ASF profile then click Edit. |
|
3.
|
Type asf2 in the Alias field if this is a new ASF profile. |
|
5.
|
Set Buffer Count before Match to 5. |
|
6.
|
Set the session field. |
|
o
|
Select ipv4-5tuple outer |
|
o
|
Select vlan-id position 1 |
|
|
4
|
Configure the combined GigaSMART operation.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operation and create two GigaSMART Operations. |
|
3.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
4.
|
Type gsop1 in the Alias field. |
|
5.
|
Select the operations. |
|
o
|
ASF with asf2 for the ASF profile |
|
|
5
|
Create a virtual port and associate it with the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > Virtual Ports. |
|
3.
|
Enter vp1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
|
6
|
Create a first level map.
|
|
1.
|
Select Maps > Maps > Maps. |
|
a.
|
Type map11 in the Alias field. |
|
b.
|
Select First Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the network port 1/1/x1 for the Source. |
|
e.
|
Select the virtual port vp1 for the Destination. |
|
c.
|
Select IPv4 Protocol and set Value to UDP. |
|
d.
|
Select Port Destination and set the port value to 2152 |
|
|
7
|
Create a second level map. The gsrule specifies the traffic to drop, using keywords. Buffered packets and all subsequent packets will be dropped.
|
|
a.
|
Type map22 in the Alias field. |
|
b.
|
Select Second Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the virtual port vp1 for the Source. |
|
e.
|
Select the tool port 1/1/x6 for the Destination. |
|
f.
|
Select gsop1 form the GSOP list. |
|
d.
|
Select regex and enter netflix|nflxvideo|nflximg|Netflix|nflxext. |
|
e.
|
Set the offset from 0 to 1460 |
|
f.
|
Set Protocol to tcp and set Position to 1. |
|
Example 2: Buffer ASF, Drop YouTube Traffic
In Example 2, the goal is to drop all YouTube traffic. The YouTube traffic is expected to be identified in the first 7 packets of a session. (Configure the maximum number of packets buffered before the match to 6.) A maximum of 4 million sessions is specified.
|
Step
|
Description
|
Command
|
|
1
|
Configure a GigaSMART group and associate it with GigaSMART engine ports and define the maximum number of sessions, in millions
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type gsgrp1 in the Alias field. |
|
4.
|
Select two engine ports from the Port List field. For example, 1/3/e1 and 1/3/e2 |
|
5.
|
Under Params Resource Buffer, select ASF and set the Buffer Size to 4. |
|
|
2
|
If needed, reload the GigaSMART line card or module to allocate the resources for buffer ASF.
|
If you reset the buffer size of an ASF profile in Task 1, go to the Chassis page and select Table View. Under Cards, select the card to reload. From the Actions menu select Shut Down and then Start Up.
You can also issue the following CLI commands to reboot the card (the card is in slot 3 in this example):
(config) # card slot 3 down
(config) # no card slot 3 down
|
|
3
|
Create a flow session, specify the buffer count before the match, and enable buffering.
Note: The default protocol is TCP, so it does not need to be specified.
|
|
1.
|
From the device view, select GigaSMART > ASF. |
|
2.
|
Click New or select an existing ASF profile then click Edit. |
|
3.
|
Type asf2 in the Alias field if this is a new ASF profile. |
|
5.
|
Set Buffer Count before Match to 6. |
|
6.
|
Set the session field to ipv4-5tuple outer |
|
|
4
|
Configure the combined GigaSMART operation.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operations and create two GigaSMART Operations. |
|
3.
|
Type gsop1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
5.
|
Select the operations. |
|
o
|
Adaptive Packet Filtering |
|
o
|
ASF with asf2 for the ASF profile |
|
|
5
|
Create a virtual port and associate it with the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > Virtual Ports. |
|
3.
|
Enter vp1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
|
6
|
Create a first level map.
|
|
1.
|
Select Maps > Maps > Maps. |
|
a.
|
Type map11 in the Alias field. |
|
b.
|
Select First Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the network port 1/1/x1 for the Source. |
|
e.
|
Select the virtual port vp1 for the Destination. |
|
c.
|
Select IPv4 Version and set Version to v4. |
|
|
7
|
Create a second level map. The gsrule specifies the traffic to drop, using keywords. Buffered packets and all subsequent packets will be dropped.
|
|
a.
|
Type map22 in the Alias field. |
|
b.
|
Select Second Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the virtual port vp1 for the Source. |
|
e.
|
Select the tool port 1/1/x6 for the Destination. |
|
f.
|
Select gsop1 form the GSOP list. |
|
d.
|
Select regex and enter youtube|ytimg|yt3.ggpht|tubeMogul|tmogul. |
|
e.
|
Set the offset from 0 to 1460 |
|
f.
|
Set Protocol to tcp and set Position to 1. |
|
Example 3: Buffer ASF, Drop Windows Update Traffic
In Example 3, the goal is to drop all Windows update traffic. The Windows update traffic is expected to be identified on the HTTP request packet of a session. A maximum of 2 million sessions is specified.
|
Task
|
Description
|
UI Steps
|
|
1
|
Configure a GigaSMART group and associate it with GigaSMART engine ports and define the maximum number of sessions, in millions.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type gsgrp1 in the Alias field. |
|
4.
|
Select two engine ports from the Port List field. For example, 1/3/e1 and 1/3/e2 |
|
5.
|
Under Params Resource Buffer, select ASF and set the Buffer Size to 2. |
|
|
2
|
If needed, reload the GigaSMART line card or module to allocate the resources for buffer ASF.
|
If you reset the buffer size of an ASF profile in Task 1, go to the Chassis page and select Table View. Under Cards, select the card to reload. From the Actions menu select Shut Down and then Start Up.
You can also issue the following CLI commands to reboot the card (the card is in slot 3 in this example):
(config) # card slot 3 down
(config) # no card slot 3 down
|
|
3
|
Create a flow session, specify the buffer count before the match, and enable buffering.
Note: The default protocol is TCP, so it does not need to be specified.
|
|
1.
|
From the device view, select GigaSMART > ASF. |
|
2.
|
Click New or select an existing ASF profile then click Edit. |
|
3.
|
Type asf2 in the Alias field if this is a new ASF profile. |
|
5.
|
Set Buffer Count before Match to 3. |
|
6.
|
Set the session field to ipv4-5tuple outer |
|
|
4
|
Configure the combined GigaSMART operation.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operations and create two GigaSMART Operations. |
|
3.
|
Type gsop1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
5.
|
Select the operations. |
|
o
|
Adaptive Packet Filtering |
|
o
|
ASF with asf2 for the ASF profile |
|
|
5
|
Create a virtual port and associate it with the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > Virtual Ports. |
|
3.
|
Enter vp1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
|
6
|
Create a first level map.
|
|
1.
|
Select Maps > Maps > Maps. |
|
a.
|
Type map11 in the Alias field. |
|
b.
|
Select First Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the network port 1/1/x1 for the Source. |
|
e.
|
Select the virtual port vp1 for the Destination. |
|
c.
|
Select IPv4 Version and set Version to v4. |
|
|
7
|
Create a second level map. The gsrule specifies the traffic to drop. Buffered packets and all subsequent packets will be dropped.
|
|
a.
|
Type map22 in the Alias field. |
|
b.
|
Select Second Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the virtual port vp1 for the Source. |
|
e.
|
Select the tool port 1/1/x6 for the Destination. |
|
f.
|
Select gsop1 form the GSOP list. |
|
d.
|
Select regex and enter msdownload/update/software. |
|
e.
|
Set the offset from 0 to 1460 |
|
f.
|
Set Protocol to tcp and set Position to 1. |
|
Example 4: Buffer ASF, Forward VNC Traffic
In Example 4, the goal is to forward VNC traffic from network port 1/1/x1 to tool port 1/1/x6. All packets belonging to the TCP connection need to be sent to the tool port. The first data packet after the TCP handshake is expected to contain the VNC pattern match. A maximum of 2 million sessions is specified.
|
Task
|
Description
|
UI Steps
|
|
1
|
Configure a GigaSMART group and associate it with GigaSMART engine ports and define the maximum number of sessions, in millions.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type gsgrp1 in the Alias field. |
|
4.
|
Select two engine ports from the Port List field. For example, 1/3/e1 and 1/3/e2 |
|
5.
|
Under Params Resource Buffer, select ASF and set the Buffer Size to 2. |
|
|
2
|
If needed, reload the GigaSMART line card or module to allocate the resources for buffer ASF.
|
If you reset the buffer size of an ASF profile in Task 1, go to the Chassis page and select Table View. Under Cards, select the card to reload. From the Actions menu select Shut Down and then Start Up.
You can also issue the following CLI commands to reboot the card (the card is in slot 3 in this example):
(config) # card slot 3 down
(config) # no card slot 3 down
|
|
3
|
Create a flow session, specify the buffer count before the match, and enable buffering.
Note: The default protocol is TCP, so it does not need to be specified.
|
|
1.
|
From the device view, select GigaSMART > Application Session Filtering. |
|
2.
|
Click New or select an existing ASF profile then click Edit. |
|
3.
|
Type asf1 in the Alias field if this is a new ASF profile. |
|
5.
|
Set Buffer Count before Match to 3. |
|
6.
|
Set the session field to ipv4-5tuple outer |
|
|
4
|
Configure the combined GigaSMART operation.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operation and create two GigaSMART Operations. |
|
3.
|
Type gsop1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
5.
|
Select the operations. |
|
o
|
Adaptive Packet Filtering |
|
o
|
ASF with asf1 for the ASF profile |
|
|
5
|
Create a virtual port and associate it with the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > Virtual Ports. |
|
3.
|
Enter vp1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
|
6
|
Create a first level map.
|
|
1.
|
Select Maps > Maps > Maps. |
|
a.
|
Type map11 in the Alias field. |
|
b.
|
Select First Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the network port 1/1/x1 for the Source. |
|
e.
|
Select the virtual port vp1 for the Destination. |
|
c.
|
Select IPv4 Version and set Version to v4. |
|
|
7
|
Create a second level map. The gsrule specifies the traffic to pass. Buffered packets and all subsequent packets will be passed.
|
|
a.
|
Type map22 in the Alias field. |
|
b.
|
Select Second Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the virtual port vp1 for the Source. |
|
e.
|
Select the tool port 1/1/x6 for the Destination. |
|
f.
|
Select gsop1 form the GigaSMART Operations (GSOP) list. |
|
d.
|
Select regex and enter ^rfb 00[1-9]\.00[0-9]\x0a$. |
|
e.
|
Set Protocol to tcp and set Position to 1. |
|
Example 5: Buffer ASF, Forward HTTPS Traffic on Non-Standard Port
In Example 5, the goal is to forward HTTPS traffic that uses a non-standard Layer 4 port. All packets belonging to the TCP connection need to be sent to the tool port. A maximum of 5 million sessions is specified.
|
Task
|
Description
|
UI Steps
|
|
1
|
Configure a GigaSMART group and associate it with GigaSMART engine ports and define the maximum number of sessions, in millions.
|
|
1.
|
GigaSMART > GigaSMART Groups > GigaSMART Groups. |
|
3.
|
Type gsgrp1 in the Alias field. |
|
4.
|
Select two engine ports from the Port List field. For example, 1/3/e1 and 1/3/e2 |
|
5.
|
Under Params Resource Buffer, select ASF and set the Buffer Size to 2. |
|
|
2
|
If needed, reload the GigaSMART line card or module to allocate the resources for buffer ASF.
|
If you reset the buffer size of an ASF profile in Task 1, go to the Chassis page and select Table View. Select the card in the table. From the Actions menu select Shut Down and then Start Up.
You can also issue the following commands to reboot the card (the card is in slot 3 in this example):
(config) # card slot 3 down
(config) # no card slot 3 down
|
|
3
|
Create a flow session, specify the buffer count before the match, and enable buffering.
Note: The default protocol is TCP, so it does not need to be specified.
|
|
1.
|
From the device view, select GigaSMART > ASF. |
|
2.
|
Click New or select an existing ASF profile then click Edit. |
|
3.
|
Type asf2 in the Alias field if this is a new ASF profile. |
|
5.
|
Set Buffer Count before Match to 3. |
|
6.
|
Set the session field to ipv4-5tuple outer |
|
|
4
|
Configure the combined GigaSMART operation.
|
|
1.
|
From the device view, select GigaSMART > GigaSMART Operations (GSOP) > GigaSMART Operations and create two GigaSMART Operations. |
|
3.
|
Type gsop1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
5.
|
Select the operations. |
|
o
|
ASF with asf2 for the ASF profile |
|
|
5
|
Create a virtual port and associate it with the GigaSMART group.
|
|
1.
|
From the device view, select GigaSMART > Virtual Ports. |
|
3.
|
Enter vp1 in the Alias field. |
|
4.
|
Select gsgrp1 from the GigaSMART Groups list. |
|
|
6
|
Create a first level map.
|
|
1.
|
Select Maps > Maps > Maps. |
|
a.
|
Type map11 in the Alias field. |
|
b.
|
Select First Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the network port 1/1/x1 for the Source. |
|
e.
|
Select the virtual port vp1 for the Destination. |
|
c.
|
Select IPv4 Version and set Version to v4. |
|
|
7
|
Create a second level map. The gsrule specifies the traffic to pass. The RegEx expression identifies the traffic as SSL. Buffered packets and all subsequent packets will be passed.
|
|
a.
|
Type map22 in the Alias field. |
|
b.
|
Select Second Level for Type. |
|
c.
|
Select By Rule for Subtype. |
|
d.
|
Select the virtual port vp1 for the Source. |
|
e.
|
Select the tool port 1/1/x6 for the Destination. |
|
f.
|
Select gsop1 form the GSOP list. |
|
d.
|
Select regex and enter x16\x03.{3}\x01. |
|
e.
|
Set Protocol to tcp and set Position to 1. |
|
|
|