Manage Maps

A map alias specifies the name of the map. The alias must be unique and can contain up to 128 alphanumeric characters. Aliases are case-sensitive.

Most special characters are supported in map aliases. However, map aliases that are only one period (.) or two periods (..) should not be created. These aliases cannot be accessed for editing.

The following are the steps for creating a map:

1.

Check the status of the nodes and ports that you plan to use with the map.

For information about how to check the status of the nodes and ports, refer to Status of Line Cards/Nodes and Ports.

2.

From the device view, go to Maps > Maps to open the Maps page.

3.

Click New.

4.

Enter the Map Information:

a.

Enter an alias for the map.

Use an alias that helps identify the task and destination. For example netflix_traffic_to_wireshark.

b.

(Optional) Enter a description about the map. When adding description, consider the following:

•

Use up to 128 characters, including spaces.

•

Enclose the description in quotation marks, if the description is longer than one word.

•

To include double quotation marks (") inside the quotation marks, precede it with a backslash (\).

See also Description to Map Rules.

c.

Select the Type.

The map type can be Regular, First Level, Second Level, or Inline.

For detailed information about the types of maps, refer to Map Types

d.

Select the map Subtype.

The map subtype can be By Rule, Pass All, or Collector.

For detailed information about Pass All, refer to About Map-passall Maps. For detailed information about Collector, refer to About Shared Collectors.

e.

Enable the Pass Traffic checkbox if no rules are matching.

f.

Enable the Control Traffic checkbox to pass the GTP control traffic (GTP-c) to all GigaSMART engines in a GTP engine group. A GTP engine group has multiple GigaSMART engine port members.

Note:  The Control Traffic checkbox is applicable only for GTP and is displayed only if the map type is configured as First level, and the map sub type is configured as By Rule.

5.

Specify the Map Source and Destination.

a.

From the Source and Destination drop-down list, select the required source and destination ports for the map. To create a port list, click Port Editor.

Note:  You can add a maximum of 324 ports in the Source drop-down list, if the ports are not attached to a GigaStream.

Note:  For details about port types that are supported for the different types of maps, refer to Port Lists.

b.

If you have selected a circuit port in the Destination drop-down list, select the required circuit tunnel from the Encapsulation Tunnel drop-down list to encapsulate the traffic.

Note:  For details about circuit tunnels, refer to About Circuit-ID Tunnels.

c.

If the map is used to redirect the decapsulated traffic to the required tool ports, ensure that you select the IP interface in the Source drop-down list. You must have attached the IP interface to the VXLAN or L2GRE tunnel. For details about VXLAN or L2GRE tunnels, refer to About Virtual Extensible LAN (VXLAN) Tunnels and About Layer 2 Generic Routing Encapsulation (L2GRE) Tunnels. From the Destination drop-down list, select the required tool ports.

d.

If the map will use a GigaSMART operation, select the operation from the GigaSMART Operations (GSOP) drop-down list.

e.

If you select tool GigaStream for the destination, you can view the utilization value for the GigaStream.

6.

Add rules to the map.

To add rules to the map, do any of the following:

o

Use the Quick Editor. For details, refer to the How to Use the Quick Editor for Pass and Drop Rules.

o

Import a map template by clicking Import.

o

Create a rule by clicking Add a Rule.

For detailed information about map rules, refer to Map Rules.

7.

Set the Map Order by selecting the priority from the Priority list.

For details about map priority, refer to Map Priority.

8.

Set the Map Permissions.

For details about map permissions, refer to Port Access and Map Sharing.

You can create a copy of an existing map by doing the following:

1.

Select Maps > Maps to open the Maps page.

2.

Select the check box of the map that you to clone.

3.

Click Clone.

4.

Make changes to the map as necessary, such as specifying an alias.

5.

Click Save.

To edit an existing map:

1.

Click the List view button.

2.

Select the map on the Maps page by either selecting the check box and then clicking Edit, or click on the row in the table and clicking Edit in the Map Quick View.

3.

Make the changes to the map.

When editing a map, you can only modify the following:

o

Map alias

o

Description

o

Change the source and destination.

o

Select a different GS Operation.

o

Modify rules.

o

Add rules.

o

Delete rules.

o

Permissions as allowed.

4.

Click Save.

Keep in mind the following rules and notes before you delete a map:

• If you have configured an active visibility policy action for a map, ensure that you delete the active visibility policy before you delete the map. If you delete the map before deleting the active visibility policy, it would result in errors in the policy action.
• If you delete a map, which has a network port that is shared with another map, the map statistics will be reset for the other map.

To delete a map or maps, do the following:

1.

Select Maps > Maps to open the Maps page.

2.

Select the check box for the map or maps to delete, and then Click Delete.

3.

When the message appears, asking if you want to delete the selected maps, click OK.

Note:  In the GRIP configuration, when you delete a map on the primary node, irrespective of the inline-network traffic-path, the traffic is switched to the secondary node. The port utilization must be 0% on the primary node and active on the secondary node.

Map Groups are a collection of maps that are used with GTP Flow Sampling Overlap and GTP Whitelisting Overlap GigaSMART solutions.

Use the Map Groups page to create a group of maps for GTP forward listing and GTP flow sampling. All the maps in a map group receive traffic according to map rules, rather than map priority. Thus, multiple copies of a GTP packet can be sent to more than one tool. This functionality is referred to as overlapping maps.

The virtual port for specified as the source for GTP forward listing and GTP flow sampling must have GTP Overlap enabled.

When creating Map Groups keep the following in mind:

■

A map group can be associated with only one GigaSMART group (gsgroup).

■

All maps within a map group must be connected to the same vport.

■

A map group can consist of only one GTP forward listing map or only one GTP flow sampling map but it cannot contains two maps of the same type.

■

Once you have created a map group, you cannot edit it to change the type or subtype of the map. However, you can add or edit the map rules for a map, which is configured in a map group. Similarly, you cannot edit the map group alias but you can edit the aliases of the maps that are configured in the map group.

■

If multiple map groups are configured, the maps within each map group must point to the same port groups as the other map groups.

To create a Map Group, do the following:

1.

Select Maps > Map Groups to open the Maps page.

2.

Click New.

3.

Enter an alias for the map group.

Use an alias that helps identify the map group.

4.

(Optional) Enter a description about the map group. Refer to Description to Map Rules for the considerations regarding description.

5.

Click in the Maps field and select the maps to add to the map group.

6.

Click Save.

Use description to label the purpose of a rule or the type of traffic covered by a rule. To add a map rule description to a map select Maps > Maps > Edit.

Consider the following when adding map rule description:

■

Use up to 128 characters, including spaces.

■

Enclose the description in quotation marks, if the description is longer than one word.

■

To include double quotation marks (") inside the quotation marks, precede the quote mark with a backslash (\).

When creating a map, you can use the Quick Rule Editor to quickly select custom port numbers for a map rule or add a range of IP address.