Configure Inline Bypass Examples
The following sections provide examples of inline bypass solutions. The solutions are presented in an order from simple to complex. Refer to the following:
• | Example 1: Unprotected Inline Bypass |
• | Example 2—Unprotected Flexible Inline, Two Collector Maps |
• | Example 3: Unprotected Inline Bypass with an Inline Tool Group |
• | Example 4: Protected Inline Bypass Using Bypass Combo Modules |
• | Example 5: Inline Tool Group (N+1) Redundancy |
• | Example 6: Inline Tool Series |
• | Example 7: Inline Tool Series with Local Failover Action |
• | Example 8: Inline Network Group (Many-to-One) |
• | Example 9: Inline Network Group (Many-to-Many) |
• | Example 10: Inline Flow Mapping® Based Solution A |
• | Example 11: Inline Flow Mapping® Based Solution B |
• | Example 12: Inline Flow Mapping® Based Solution C |
• | Example 13: Inline Flow Mapping® Based Solution D |
• | Example 14: OOB Maps Originating from Inline Network |
• | Example 15: OOB Maps Originating from Inline Network Group |
• | Example 16: Asymmetrical Hashing in Inline Tool Group |
• | Example 17: Maps to Individual Inline Tool Group Members |
• | Example 18: Gigamon Resiliency for Inline Protection |
Example 1: Unprotected Inline Bypass
Example 1 is a simple, unprotected inline bypass solution. In the example, aliases are used for inline network ports (iN1 and iN2), inline tool ports (iT1 and iT2), inline network (inNet), inline tool (inTool), and inline map (inMap).
On GigaVUE-HC3, an unprotected inline bypass solution can be configured on the bypass combo module with the inline networks and inline tools on ports 1/1/x1..x16 or on ports c1..c4, or on any other module on the GigaVUE-HC3 node.
On GigaVUE-HC2, an unprotected inline bypass solution can be configured with the inline networks and inline tools on ports 1/1/x1..x16 or on ports x17..x24, or on any other module on the GigaVUE-HC2 node. Refer to Figure 1 Logical Bypass, which shows a GigaVUE-HC2.
Figure 11 | Logical Bypass |
On GigaVUE‑HC1, an unprotected inline bypass solution can be configured on the base module, with the inline networks and inline tools on ports 1/1/x1..x12 and
1/1/g1..g4, or on the bypass combo module on ports x1..x4.
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 3/1/x1 alias iN1 (config) # port 3/1/x2 alias iN2 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN1 and net-b iN2 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 3/1/x3 alias iT1 (config) # port 3/1/x4 alias iT2 |
|||
|
Configure inline tool and enable it. |
(config) # inline-tool alias inTool pair tool-a iT1 and tool-b iT2 |
|||
|
Configure map passall, from inline network to inline tool. |
(config) # map-passall alias inMap |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Display the configuration for this example. |
(config) # show port |
Example 2: Unprotected Inline Bypass with Default Heartbeat
Example 2 adds the default heartbeat profile to the unprotected inline bypass solution on GigaVUE-HC2 in Example 1.
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 3/1/x1 alias iN1 (config) # port 3/1/x2 alias iN2 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN1 and net-b iN2 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 3/1/x3 alias iT1 (config) # port 3/1/x4 alias iT2 |
|||
|
Configure default heartbeat profile. |
(config) # hb-profile alias hb1 |
|||
|
Configure inline tool and enable it. |
(config) # inline-tool alias inTool pair tool-a iT1 and tool-b iT2 |
|||
|
Specify heartbeat profile and enable heartbeat. |
(config) # inline-tool alias inTool hb-profile hb1 |
|||
|
Configure map passall, from inline network to inline tool. |
(config) # map-passall alias inMap |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Display the configuration for this example. |
(config) # show hb-profile |
Example 3: Unprotected Inline Bypass with an Inline Tool Group
Example 3 adds a second inline tool to the unprotected inline bypass solution on GigaVUE-HC2 in Example 1 and creates an inline tool group consisting of two tools. It also configures a custom heartbeat profile.
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 3/1/x1 alias iN1 (config) # port 3/1/x2 alias iN2 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN1 and net-b iN2 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 3/1/x3 alias iT1 (config) # port 3/1/x4 alias iT2 (config) # port 3/1/x5 alias iT3 (config) # port 3/1/x6 alias iT4 |
|||
|
Configure a custom heartbeat profile. |
(config) # hb-profile alias hb_custom |
|||
|
Configure inline tools and enable them. |
(config) # inline-tool alias inTool1 pair tool-a iT1 and tool-b iT2 (config) # inline-tool alias inTool1 enable |
|||
|
Specify heartbeat profile and enable heartbeat on each inline tool. |
(config) # inline-tool alias inTool1 hb-profile hb_custom |
|||
|
Configure inline tool group and enable it. |
(config) # inline-tool-group alias inToolGroup tool-list inTool1,inTool2 |
|||
|
Configure map passall, from inline network to inline tool group. |
(config) # map-passall alias inMap |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Display the configuration for this example. |
(config) # show inline-tool-group |
Example 4: Protected Inline Bypass Using Bypass Combo Modules
Example 4 is a protected inline bypass solution using bypass combo modules on GigaVUE-HC2. It also configures heartbeat and negative heartbeat profiles.
Protected inline networks are based on the pairs of ports associated with the physical protection switches located on the bypass combo modules. Unlike the unprotected examples, you do not need to configure inline network ports because they are created automatically. On GigaVUE-HC2, the port pairs are numbered for example: 2/2/x17 and 2/2/x18, 2/2/x19 and 2/2/x20, 2/2/x21 and 2/2/x22, 2/2/x23 and 2/2/x24.
You do not need to configure inline networks because they are also created automatically on bypass combo modules. The aliases of the default inline networks are: default_inline_net_2_2_1, default_inline_net_2_2_2, default_inline_net_2_2_3, default_inline_net_2_2_4.
On GigaVUE-HC3, protected inline bypass can be configured on the bypass combo module on ports c1..c4.
On GigaVUE‑HC1, protected inline bypass can be configured on the bypass combo module. It can also be configured on the TAP-HC1-G10040 module placed in either bay 2 or bay 3, so the ports will be 1/2/g1..g8 or 1/3/g1..g8. For an example, refer to Example to Configure Inline Bypass on H Series Nodes.
Note: The default value of the physical-bypass attribute of protected inline networks is set to enable, which means that the fibers attached to ports net-a and net-b of the inline network are optically coupled and the traffic is exchanged between end nodes without coming to the switching fabric of the GigaVUE node. As shown in Example 4, after configuring the inline tool and the map passall, the physical-bypass attribute is set to disable in order to activate the inline-bypass solution.
Step |
Description |
Command |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 2/2/x11 alias iT1 (config) # port 2/2/x12 alias iT2 |
|||
|
Configure heartbeat profile alias. |
(config) # hb-profile alias hb2 |
|||
|
Configure negative heartbeat profile alias and PCAP file. |
(config) # nhb-profile alias nhb1 |
|||
|
Configure inline tool. Also specify the heartbeat profile, the negative heartbeat profile, enable heartbeat and negative heartbeat, and also enable inline tool. |
(config) # inline-tool alias inTool1 |
|||
|
Configure map passall, from inline network to inline tool. |
(config) # map-passall alias inMap1 |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias default_inline_net_2_2_1 traffic-path to-inline-tool |
|||
|
Disable physical bypass on the default inline network alias. |
(config) # inline-network alias default_inline_net_2_2_1 physical-bypass disable |
|||
|
Display the configuration for this example. |
(config) # show port |
Example 5: Inline Tool Group (N+1) Redundancy
Example 5 is an inline bypass solution on GigaVUE-HC2 for an inline tool group with N+1 redundancy. In this example, N=2. The inline network is unprotected. Example 5 expands upon Example 3 by adding a spare to the inline tool group.
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 3/1/x1 alias iN1 (config) # port 3/1/x2 alias iN2 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN1 and net-b iN2 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 3/1/x3 alias iT1 (config) # port 3/1/x4 alias iT2 (config) # port 3/1/x5 alias iT3 (config) # port 3/1/x6 alias iT4 (config) # port 3/1/x7 alias iT5 (config) # port 3/1/x8 alias iT6 |
|||
|
Configure inline tools and enable them. |
(config) # inline-tool alias inTool1 pair tool-a iT1 and tool-b iT2 (config) # inline-tool alias inTool1 enable |
|||
|
Configure inline tool group and parameters. Enable it and then configure failover action. |
(config) # inline-tool-group alias inToolGroup |
|||
|
Configure map passall, from inline network to inline tool group. |
(config) # map-passall alias inMap |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Display the configuration for this example. |
(config) # show inline-tool-group |
Example 6: Inline Tool Series
Example 6 is an inline bypass solution on GigaVUE-HC2 for an inline tool series. The inline network is unprotected. The order of the tools and inline tool groups in the tool list defines the order of the series. The map directs the traffic to the series, that is, to the first inline tool or inline tool group in the tool list. Example 6 includes two inline tools in the series and an inline tool group.
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 3/1/x1 alias iN11 (config) # port 3/1/x2 alias iN12 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN11 and net-b iN12 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 3/1/x3 alias iT1 (config) # port 3/1/x4 alias iT2 (config) # port 3/1/x5 alias iT3 (config) # port 3/1/x6 alias iT4 (config) # port 3/1/x7 alias iT5 (config) # port 3/1/x8 alias iT6 (config) # port 3/1/x9 alias iT7 (config) # port 3/1/x10 alias iT8 |
|||
|
Configure inline tools and enable them. |
(config) # inline-tool alias inTool1 pair tool-a iT1 and tool-b iT2 (config) # inline-tool alias inTool1 enable |
|||
|
Configure inline tool group and parameters. Enable it and then configure failover action. |
(config) # inline-tool-group alias inToolGroup |
|||
|
Configure inline tool series and enable it. Then configure failover action. |
(config) # inline-serial alias inSer |
|||
|
Configure map passall, from inline network to inline tool series. |
(config) # map-passall alias inMap |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Display the configuration for this example. |
(config) # show inline-serial |
Example 7: Inline Tool Series with Local Failover Action
Example 7 is an inline bypass solution on GigaVUE-HC2 for an inline tool series. The failover action is specified for one of the inline tools (network-bypass), rather than for the series as a whole. Also the recovery mode is specified as manual.
When the individual inline tool fails, traffic is dropped at the inline network ports. When the tool recovers and is ready to be put back into service, use the recover command.
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 3/1/x1 alias iN11 (config) # port 3/1/x2 alias iN12 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN11 and net-b iN12 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 3/1/x3 alias iT1 (config) # port 3/1/x4 alias iT2 (config) # port 3/1/x5 alias iT3 (config) # port 3/1/x6 alias iT4 (config) # port 3/1/x7 alias iT5 (config) # port 3/1/x8 alias iT6 |
|||
|
Configure inline tools and enable them. |
(config) # inline-tool alias inTool1 pair tool-a iT1 and tool-b iT2 (config) # inline-tool alias inTool1 enable |
|||
|
Configure failover action and recovery mode for the second tool in the list. |
(config) # inline-tool alias inTool2 failover-action network-bypass |
|||
|
Configure inline tool series, and enable it, then configure failover action, per-tool. |
(config) # inline-serial alias inSer |
|||
|
Configure map passall, from inline network to inline tool series. |
(config) # map-passall alias inMap |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Display the configuration for this example. |
(config) # show inline-tool |
|||
|
Display the forwarding state when the tool fails. |
(config) # show inline-network |
|||
|
After the inline tool recovers and is in the ready state, put the inline tool back into service. |
(config) # inline-tool alias inTool2 recover |
Example 8: Inline Network Group (Many-to-One)
Example 8 is an inline bypass solution on GigaVUE-HC2 for an inline network group. This is a many-to-one example with two inline networks and one inline tool. The inline networks are mix of protected and unprotected.
On GigaVUE-HC3, unprotected inline bypass can be configured on any module on the node. Protected inline bypass can be configured on the bypass combo module on ports c1..c4.
On GigaVUE‑HC1, unprotected inline bypass can be configured on the base module, with the inline networks and inline tools on ports 1/1/x1..x12 and 1/1/g1..g4, or on the bypass combo module on ports x1..x4. Protected inline bypass can be configured on the bypass combo module, or on the TAP-HC1-G10040 module placed in either bay 2 or bay 3, so the ports will be 1/2/g1..g8 or 1/3/g1..g8. On the TAP module, you will need to configure inline network ports and the inline network because they are not created automatically (as they are on bypass combo modules).
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 7/2/x1 alias iN1 (config) # port 7/2/x20 alias iN2 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN1 and net-b iN2 |
|||
|
Configure an inline network group consisting of a single unprotected inline network and two protected inline networks. |
(config) # inline-network-group alias inNetGroup |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 7/2/x3 alias iT1 (config) # port 7/2/x4 alias iT2 |
|||
|
Configure inline tool and enable it. Also, specify that the inline tool is going to be shared by different sources. When shared is enabled (true), the inline tool can receive traffic from multiple sources (the inline networks in the inline network group). |
(config) # inline-tool alias inTool pair tool-a iT1 and tool-b iT2 |
|||
|
Configure map passall, from inline network group to inline tool. |
(config) # map-passall alias inMap |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Disable physical bypass on the default inline network aliases. |
(config) # inline-network alias default_inline_net_7_2_1 physical-bypass disable |
|||
|
Display the configuration for this example. |
(config) # show inline-network-group |
Example 9: Inline Network Group (Many-to-Many)
Example 9 is an inline bypass solution on GigaVUE-HC2 for an inline network group. Example 9 expands upon Example 8 by adding a second inline tool. The inline networks are a mix of unprotected and protected.
In addition, user-defined VLAN tags are added in Example 9 to guide traffic from the multiple inline networks in the inline network group.
On GigaVUE-HC3, unprotected inline bypass can be configured on any module on the node. Protected inline bypass can be configured on the bypass combo module on ports c1..c4.
On GigaVUE‑HC1, unprotected inline bypass can be configured on the base module, with the inline networks and inline tools on ports 1/1/x1..x12 and 1/1/g1..g4, or on the bypass combo module on ports x1..x4. Protected inline bypass can be configured on the bypass combo module, or on the TAP-HC1-G10040 module placed in either bay 2 or bay 3, so the ports will be 1/2/g1..g8 or 1/3/g1..g8. On the TAP module, you will need to configure inline network ports and the inline network because they are not created automatically (as they are on bypass combo modules).
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 7/2/x1 alias iN1 (config) # port 7/2/x20 alias iN2 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN1 and net-b iN2 |
|||
|
Configure an inline network group consisting of a single unprotected inline network and two protected inline networks. |
(config) # inline-network-group alias inNetGroup |
|||
|
(Optional) Configure user-defined VLAN tags. Note: The net-a and net-b ports can have the same VLAN tag, but tags must otherwise be unique within the inline network group. |
(config) # port 7/2/x1 ingress-vlan-tag 1201 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 7/2/x3 alias iT1 (config) # port 7/2/x4 alias iT2 7/2/x9 alias iT3 7/2/x10 alias iT4 |
|||
|
Configure inline tools and enable them. Also, specify that inline tools are going to be shared by different sources. When shared is enabled (true), the inline tools can receive traffic from multiple sources (the inline networks in the inline network group). |
(config) # inline-tool alias inTool1 pair tool-a iT1 and tool-b iT2 (config) # inline-tool alias inTool1 enable inTool1 shared true |
|||
|
Configure inline tool group and enable it. |
(config) # inline-tool-group alias inToolGroup tool-list inTool1,inTool2 |
|||
|
Configure map passall, from inline network to inline tool group. |
(config) # map-passall alias inMap |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Disable physical bypass on the default inline network aliases. |
(config) # inline-network alias default_inline_net_7_2_1 physical-bypass disable |
|||
|
Display the configuration for this example. |
(config) # show inline-network-group |
Example 10: Inline Flow Mapping® Based Solution A
Example 10 is an inline flow mapping based solution on GigaVUE-HC2. Example 10 has a single, unprotected inline network, a single inline tool, a rule-based map (VLAN 100) from the inline network to the inline tool, and a shared collector from the inline network to bypass. Traffic on VLAN 100 will be inspected by the inline tool while the remaining traffic will not be inspected (will be bypassed).
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 7/2/x1 alias iN1 (config) # port 7/2/x20 alias iN2 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN1 and net-b iN2 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 7/2/x2 alias iT1 (config) # port 7/2/x15 alias iT2 |
|||
|
Configure inline tool and enable it. |
(config) # inline-tool alias inTool pair tool-a iT1 and tool-b iT2 |
|||
|
Enable default heartbeat. |
(config) # inline-tool alias inTool heart-beat |
|||
|
Configure rule-based map, from inline network to inline tool. |
(config) # map alias inMap1 |
|||
|
Add a shared collector for any unmatched data and send it to bypass. |
(config) # map-scollector alias scoll |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Display the configuration for this example. |
(config) # show inline-network |
Example 11: Inline Flow Mapping® Based Solution B
Example 11 is an inline flow mapping based solution on GigaVUE-HC2. Example 11 has a single, unprotected inline network, a single inline tool, a rule-based map (VLAN 100) from the inline network to bypass, and a shared collector from the inline network to the inline tool. Traffic on VLAN 100 will not be inspected by the inline tool, while the remaining traffic will be inspected by the inline tool (through the bypass).
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 7/2/x1 alias iN1 (config) # port 7/2/x20 alias iN2 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN1 and net-b iN2 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 7/2/x2 alias iT1 (config) # port 7/2/x15 alias iT2 |
|||
|
Configure inline tool and enable it. |
(config) # inline-tool alias inTool pair tool-a iT1 and tool-b iT2 |
|||
|
Enable default heartbeat. |
(config) # inline-tool alias inTool heart-beat |
|||
|
Configure rule-based map, from inline network to bypass. |
(config) # map alias inMap2 |
|||
|
Add a shared collector, from inline network to inline tool. |
(config) # map-scollector alias scoll2 |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Display the configuration for this example. |
(config) # show map |
Example 12: Inline Flow Mapping® Based Solution C
Example 12 is an inline flow mapping based solution on GigaVUE-HC2. Example 12 has a single, unprotected inline network, two individual inline tools, a rule-based map (portdst 22) from the inline network to bypass, a rule-based map (portdst 80) from the inline network to the first inline tool, and a shared collector from the inline network to the second inline tool. Traffic that does not match the map rules will be sent to the shared collector, ensuring that all traffic is exchanged between side A and side B of the network.
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 7/2/x1 alias iN1 (config) # port 7/2/x20 alias iN2 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN1 and net-b iN2 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 7/2/x2 alias iT1 (config) # port 7/2/x15 alias iT2 (config) # port 7/2/x3 alias iT3 (config) # port 7/2/x4 alias iT4 |
|||
|
Configure inline tools and enable them. |
(config) # inline-tool alias inTool1 pair tool-a iT1 and tool-b iT2 (config) # inline-tool alias inTool1 enable |
|||
|
Enable default heartbeats. |
(config) # inline-tool alias inTool1 heart-beat |
|||
|
Configure rule-based map, from inline network to bypass. |
(config) # map alias inMap3 |
|||
|
Configure rule-based map, from inline network to first inline tool. |
(config) # map alias inMap4 |
|||
|
Add a shared collector, from inline network to second inline tool. |
(config) # map-scollector alias scoll3 |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Display the configuration for this example. |
(config) # show inline-tool |
Example 13: Inline Flow Mapping® Based Solution D
Example 13 is an inline flow mapping based solution on GigaVUE-HC2. Example 13 has a variety of constructs: an inline network group made up of two protected inline networks, an inline tool group, an inline tool series, an individual inline tool, a rule-based map (VLAN 100) from the inline network group to the inline tool group, a rule-based map (portdst 80) from the inline network group to the inline tool series, a rule-based map (ipsrc 10.123.12.57) from the inline network group to the individual inline tool, and a shared collector from the inline network group to bypass.
Since Example 13 uses protected inline networks on GigaVUE-HC2, they do not need to be configured as described in Example 4: Protected Inline Bypass Using Bypass Combo Modules, so the configuration begins with the inline network group.
On GigaVUE-HC3, unprotected inline bypass can be configured on any module on the node. Protected inline bypass can be configured on the bypass combo module on ports c1..c4.
On GigaVUE‑HC1, unprotected inline bypass can be configured on the base module, with the inline networks and inline tools on ports 1/1/x1..x12 and 1/1/g1..g4, or on the bypass combo module on ports x1..x4. Protected inline bypass can be configured on the bypass combo module, or on the TAP-HC1-G10040 module placed in either bay 2 or bay 3, so the ports will be 1/2/g1..g8 or 1/3/g1..g8. On the TAP module, you will need to configure inline network ports and the inline network because they are not created automatically (as they are on bypass combo modules).
Step |
Description |
Command |
||||||||||||
|
Configure an inline network group consisting of two protected inline networks. |
(config) # inline-network-group alias inNetGroup |
||||||||||||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 7/2/x2 alias iT1 (config) # port 7/2/x15 alias iT2 (config) # port 7/2/x3 alias iT3 (config) # port 7/2/x4 alias iT4 (config) # port 7/2/x7 alias iT5 (config) # port 7/2/x8 alias iT6 (config) # port 7/2/x13 alias iT7 (config) # port 7/2/x14 alias iT8 (config) # port 7/2/x15 alias iT9 (config) # port 7/2/x16 alias iT10 |
||||||||||||
|
Configure inline tools as follows:
Also, enable inline tools. Specify that inline tools are going to be shared by different sources. When shared is enabled (true), the inline tools can receive traffic from multiple sources (the inline networks in the inline network group). |
(config) # inline-tool alias inTool1 pair tool-a iT1 and tool-b iT2 (config) # inline-tool alias inTool1 enable inTool1 shared true |
||||||||||||
|
Enable default heartbeats. |
(config) # inline-tool alias inTool1 heart-beat |
||||||||||||
|
Configure an inline tool group and enable it. |
(config) # inline-tool-group alias inToolGroup |
||||||||||||
|
Configure an inline tool series and enable it. |
(config) # inline-serial alias inSer |
||||||||||||
|
Configure rule-based map, from the inline network group to the inline tool group. |
(config) # map alias inMap1 |
||||||||||||
|
Configure rule-based map, from the inline network group to the inline tool series. |
(config) # map alias inMap2 |
||||||||||||
|
Configure rule-based map, from the inline network group to the individual inline tool. |
(config) # map alias inMap3 |
||||||||||||
|
Add a shared collector from the inline network group to bypass. |
(config) # map-scollector alias scoll |
||||||||||||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
||||||||||||
|
Disable physical bypass on the default inline network aliases. |
(config) # inline-network alias default_inline_net_7_2_1 physical-bypass disable |
||||||||||||
|
Display the configuration for this example. |
(config) # show inline-network |
Example 14: OOB Maps Originating from Inline Network
Example 14 combines out-of-band (OOB) maps with a map passall originating from an inline network on GigaVUE-HC2. In Example 14, the map passall sends all traffic to the inline tool. The OOB rule-based map sends traffic to an OOB tool.
When the source port of an OOB map is associated with an inline network, multiple source ports are supported in the port list (the from argument of the map command).
A protected inline network (which uses bypass combo modules) is included in Example 14. You do not need to configure inline network ports because they are created automatically. The port pairs in Example 14 are 1/1/x21 and 1/1/x22. You do not need to configure an inline network because it is also created automatically. The alias of the default inline network in Example 14 is default_inline_net_1_1_3.
On GigaVUE-HC3, protected inline bypass can be configured on the bypass combo module on ports c1..c4.
On GigaVUE‑HC1, protected inline bypass can be configured on the bypass combo module, or on the TAP-HC1-G10040 module placed in either bay 2 or bay 3, so the ports will be 1/2/g1..g8 or 1/3/g1..g8. On the TAP module, you will need to configure inline network ports and the inline network because they are not created automatically (as they are on bypass combo modules).
Step |
Description |
Command |
|||
|
Configure a regular tool port of port type (tool) and administratively enable it. This is the OOB tool. |
(config) # port 1/1/x12 type tool |
|||
|
Configure two inline tool ports of port type (inline-tool) and administratively enable them. |
(config) # port 1/2/x23 type inline-tool (config) # port 1/2/x24 type inline-tool |
|||
|
Configure inline tool and enable it. |
(config) # inline-tool alias inTool1 pair tool-a 1/2/x23 and tool-b 1/2/x24 |
|||
|
Configure a map passall, from the inline network to the inline tool. This sends all the traffic to the inline tool. |
(config) # map-passall alias inline_map1 |
|||
|
Configure the OOB rule-based map, with both inline network ports in the from argument, and the OOB tool in the to argument. |
(config) # map alias OoB_map |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias default_inline_net_1_1_3 traffic-path to-inline-tool |
|||
|
Disable physical bypass on the default inline network alias. |
(config) # inline-network alias default_inline_net_1_1_3 physical-bypass disable |
|||
|
Display the configuration and statistics for this example. |
(config) # show inline-network |
Example 15: OOB Maps Originating from Inline Network Group
Example 15 expands on Example 14 by combining out-of-band (OOB) maps with a map passall originating from an inline network group on GigaVUE-HC2.
When the source port of an OOB map is associated with an inline network group, only one port is supported in the port list. In this case, multiple OOB maps are needed because each OOB map only accepts one inline network port as the input (the from argument of the map command).
A protected inline network (which uses bypass combo modules) is included in Example 15. You do not need to configure inline network ports or the inline networks because they are created automatically. The port pairs in Example 15 are
1/1/x17 and 1/1/x18, as well as 1/1/x19 and 1/1/x20. The aliases of the default inline networks in Example 15 are default_inline_net_1_1_1 and default_inline_net_1_1_2.
In Example 15, two OOB maps send traffic from each inline network port (associated with default_inline_net_1_1_1) to the OOB tool. Two more maps would be needed to send traffic from each inline network port (associated with default_inline_net_1_1_2) to the OOB tool, but this is not included in Example 15.
On GigaVUE-HC3, protected inline bypass can be configured on the bypass combo module on ports c1..c4.
On GigaVUE‑HC1, protected inline bypass can be configured on the bypass combo module, or on the TAP-HC1-G10040 module placed in either bay 2 or bay 3, so the ports will be 1/2/g1..g8 or 1/3/g1..g8. On the TAP module, you will need to configure inline network ports and the inline network because they are not created automatically (as they are on bypass combo modules).
Step |
Description |
Command |
|||
|
Configure an inline network group consisting of two protected inline networks. |
(config) # inline-network-group alias inNetGroup |
|||
|
Configure a regular tool port of port type (tool) and administratively enable it. This is the OOB tool. |
(config) # port 1/1/x12 type tool |
|||
|
Configure two inline tool ports of port type (inline-tool) and administratively enable them. |
(config) # port 1/2/x23 type inline-tool (config) # port 1/2/x24 type inline-tool |
|||
|
Configure inline tool and enable it. Also, specify that the inline tool is going to be shared by different sources. When shared is enabled (true), the inline tool can receive traffic from multiple sources (the inline networks in the inline network group). |
(config) # inline-tool alias inTool1 pair tool-a 1/2/x23 and tool-b 1/2/x24 |
|||
|
Configure a map passall, from the inline network group to the inline tool. This sends all the traffic to the inline tool. |
(config) # map-passall alias inline_map1 |
|||
|
Configure the first rule-based map. This is an OOB map from one inline network port (associated with default_inline_net_1_1_1) to the OOB tool. |
(config) # map alias OoB_map1 |
|||
|
Configure a second rule-based map. This is an OOB map from the other inline network port (associated with default_inline_net_1_1_1) to the OOB tool. |
(config) # map alias OoB_map2 |
|||
|
Configure a third rule-based map. This is an OOB map from a single inline tool port to the OOB tool. |
(config) # map alias OoB_map3 |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias default_inline_net_1_1_1 traffic-path to-inline-tool |
|||
|
Disable physical bypass on the default inline network aliases. |
(config) # inline-network alias default_inline_net_1_1_1 physical-bypass disable |
|||
|
Display the configuration and statistics for this example. |
(config) # show inline-network |
Example 16: Asymmetrical Hashing in Inline Tool Group
Example 16 is an inline bypass solution on GigaVUE-HC2 for an inline tool group with four tools. The inline tool group uses asymmetrical hashing (unlike Example 5: Inline Tool Group (N+1) Redundancy which uses symmetrical hashing). The hashing is based on the source IP address for side A and the destination IP address for side B.
A rule-based map (vlan 200) is configured from the inline network to the inline tool group. Traffic that matches the map rule and has the same source IP on side A and destination IP on side B will be sent to the same inline tool in the inline tool group.
A shared collector is configured from the inline network to bypass. Traffic that does not match the map rule will be sent to the shared collector and bypassed.
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 1/2/x1 alias iN1 (config) # port 1/2/x2 alias iN2 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN1 and net-b iN2 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 1/2/x15 alias iT1 (config) # port 1/2/x16 alias iT2 (config) # port 1/2/x19 alias iT3 (config) # port 1/2/x20 alias iT4 (config) # port 1/2/x21 alias iT5 (config) # port 1/2/x22 alias iT6 (config) # port 1/2/x23 alias iT7 (config) # port 1/2/x24 alias iT8 |
|||
|
Configure inline tools and enable them. |
(config) # inline-tool alias inTool1 pair tool-a iT1 and tool-b iT2 (config) # inline-tool alias inTool1 enable |
|||
|
Configure inline tool group and parameters. Enable it and then configure failover action. |
(config) # inline-tool-group alias inToolGroup |
|||
|
Configure rule-based map, from inline network to inline tool group. |
(config) # map alias inNet-to-ITG |
|||
|
Add a shared collector for any unmatched data and send it to bypass. |
(config) # map-scollector alias inNet-to-bypass |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Display the configuration for this example. |
(config) # show inline-tool-group |
Example 17: Maps to Individual Inline Tool Group Members
Example 17 is an inline bypass solution on GigaVUE-HC2 for an inline tool group with four tools. It is similar to Example 16: Asymmetrical Hashing in Inline Tool Group, but has four rule-based inline maps, one to each individual member of the inline tool group. In Example 17, asymmetrical hashing is used, but the hashing could also be symmetrical. The hashing only applies to the traffic sent to the shared collector.
Example 17 is different from Example 5: Inline Tool Group (N+1) Redundancy. In Example 5, all the traffic was sent to the inline tool group as a whole, using a map passall. Hashing distributed the traffic across the group.
With the multiple rule-based maps in Example 17, specific traffic is sent to specific tools in the inline tool group according to the rules. Each of the four inline maps directs traffic from one source IP address to a specific inline tool in the group.
A shared collector is configured from the inline network to the inline tool group. Traffic that does not match any of the map rules is sent to the shared collector and will be distributed according to the hashing value specified for the group.
Step |
Description |
Command |
|||
|
Configure inline network aliases, port type (inline-network), and administratively enable inline network ports. |
(config) # port 1/2/x1 alias iN1 (config) # port 1/2/x2 alias iN2 |
|||
|
Configure inline network. |
(config) # inline-network alias inNet pair net-a iN1 and net-b iN2 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable inline tool ports. |
(config) # port 1/2/x15 alias iT1 (config) # port 1/2/x16 alias iT2 (config) # port 1/2/x19 alias iT3 (config) # port 1/2/x20 alias iT4 (config) # port 1/2/x21 alias iT5 (config) # port 1/2/x22 alias iT6 (config) # port 1/2/x23 alias iT7 (config) # port 1/2/x24 alias iT8 |
|||
|
Configure inline tools and enable them. |
(config) # inline-tool alias inTool1 pair tool-a iT1 and tool-b iT2 (config) # inline-tool alias inTool1 enable |
|||
|
Configure inline tool group and parameters. Enable it and then configure failover action. |
(config) # inline-tool-group alias inToolGroup |
|||
|
Configure rule-based map, from inline network to first tool in inline tool group, from the same source, inNet. |
(config) # map alias inNet-to-inTool1 |
|||
|
Configure rule-based map, from inline network to second tool in inline tool group, from the same source, inNet. |
(config) # map alias inNet-to-inTool2 |
|||
|
Configure rule-based map, from inline network to third tool in inline tool group, from the same source, inNet. |
(config) # map alias inNet-to-inTool3 |
|||
|
Configure rule-based map, from inline network to fourth tool in inline tool group, from the same source, inNet. |
(config) # map alias inNet-to-inTool4 |
|||
|
Add a shared collector for any unmatched data and send it to the inline tool group. Again, the source is the same, inNet. |
(config) # map-scollector alias inNet-to-ITG |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias inNet traffic-path to-inline-tool |
|||
|
Display the configuration for this example. |
(config) # show inline-tool-group |
Example 18: Gigamon Resiliency for Inline Protection
You can configure Gigamon Resiliency for inline protection on H Series nodes (GigaVUE‑HC1, GigaVUE-HC2, and GigaVUE-HC3). Example 18 is an inline bypass solution for GRIP using TAP-HC1-G10040 modules on GigaVUE‑HC1 with copper ports. The same instructions apply to GigaVUE-HC2 and GigaVUE-HC3.
Note: On the GigaVUE-HC2, the configuration steps will be the same as in this example, but the network ports and the TAP module will be different.
First, configure the GigaVUE‑HC1 with the primary role, then configure the GigaVUE‑HC1 with the secondary role. The configuration is the same (is synchronized) on both nodes, except for step 3, in which the protection role (primary or secondary) is specified.
Note that in this example, link fail propagation (LFP) is disabled to reduce inline network recovery time after failover. When a primary to secondary failover occurs and LFP is enabled for copper inline bypass links, network service recovery may take several seconds because of Ethernet link renegotiation. Optical links failover faster and typically recover service much faster. For inline networks where only one path is available, this is a consideration. When GRIP is deployed with high availability networks where a second path is present, it is a best practice to leave LFP enabled.
Configuring Primary Role GigaVUE‑HC1
Step |
Description |
Command |
|||
|
Configure ports on the TAP-HC1-G10040 module as passive (in passive mode, relays are closed). Also configure ports, port type (inline-network). |
(config) # port 1/3/g1..g8 params taptx passive |
|||
|
Configure stack port (for signaling port/link) and enable it. |
(config) # port 1/1/x1 type stack |
|||
|
Create the redundancy profile by giving it a name and configuring parameters for the redundancy profile such as the signaling port and protection role (primary). |
(config) # redundancy-profile alias RP_001 |
|||
|
Configure inline network. |
(config) # inline-network alias IN_001 pair net-a 1/3/g1 and net-b 1/3/g2 |
|||
|
Associate the redundancy profile to the inline network. Also disable link fail propagation on the inline network. |
(config) # inline-network alias IN_001 redundancy-profile RP_001 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable them. |
(config) # port 1/1/x11 type inline-tool (config) # port 1/1/x12 type inline-tool |
|||
|
Configure inline tool and failover action. Then enable inline tool. |
(config) # inline-tool alias IT_001 pair tool-a 1/1/x11 and tool-b 1/1/x12 |
|||
|
Configure map passall, from inline network to inline tool. |
(config) # map-passall alias INtoIT |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias IN_001 traffic-path to-inline-tool |
Configure Secondary Role GigaVUE‑HC1
Step |
Description |
Command |
|||
|
Configure ports on the TAP-HC1-G10040 module as passive (in passive mode, relays are closed). Also configure ports, port type (inline-network). |
(config) # port 1/3/g1..g8 params taptx passive |
|||
|
Configure stack port (for signaling port/link) and enable it. |
(config) # port 1/1/x1 type stack |
|||
|
Configure parameters for the redundancy profile such as the signaling port and protection role (secondary). |
(config) # redundancy-profile alias RP_001 |
|||
|
Configure inline network. |
(config) # inline-network alias IN_001 pair net-a 1/3/g1 and net-b 1/3/g2 |
|||
|
Associate the redundancy profile to the inline network. Also disable link fail propagation on the inline network. |
(config) # inline-network alias IN_001 redundancy-profile RP_001 |
|||
|
Configure inline tool ports, port type (inline-tool), and administratively enable them. |
(config) # port 1/1/x11 type inline-tool (config) # port 1/1/x12 type inline-tool |
|||
|
Configure inline tool and failover action. Then enable inline tool. |
(config) # inline-tool alias IT_001 pair tool-a 1/1/x11 and tool-b 1/1/x12 |
|||
|
Configure map passall, from inline network to inline tool. |
(config) # map-passall alias INtoIT |
|||
|
Configure the path of the traffic to inline tool. |
(config) # inline-network alias IN_001 traffic-path to-inline-tool |