Scribd
Upload
67 views4 pages

External Bypass - Verification Procedure - Customer Space - Allot Confluence Server

This document provides a verification procedure for an external bypass unit used with an Allot DPI solution. The procedure includes 13 steps to ensure the bypass unit is correctly configured and connected, such as connecting interfaces, enabling the bypass unit in the NE configuration, and performing loop tests to verify bypass functionality. The goal is to troubleshoot that the bypass unit allows network traffic to pass through in case of NE failure or for maintenance.

Uploaded by

tslm
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
67 views4 pages

External Bypass - Verification Procedure - Customer Space - Allot Confluence Server

This document provides a verification procedure for an external bypass unit used with an Allot DPI solution. The procedure includes 13 steps to ensure the bypass unit is correctly configured and connected, such as connecting interfaces, enabling the bypass unit in the NE configuration, and performing loop tests to verify bypass functionality. The goal is to troubleshoot that the bypass unit allows network traffic to pass through in case of NE failure or for maintenance.

Uploaded by

tslm
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

17/06/13 External Bypass - Verification Procedure - Customer Space - Allot Confluence Server

External Bypass - Share Tools

Verification Procedure
Added by Ratinesh Kumar, last edited by Dan Shalem on Jun 09, 2013

External Bypass Unit


The Bypass Unit is an essential component of the Allot DPI solution as it prevents network traffic disruption in the
case of NetEnforcer failure and allows bypass (fail to wire) for planned maintenance windows.

About This Procedure


This procedure aims to verify that the bypass unit is correctly configured and connected for troubleshooting
purposes. This procedure does not cover connecting Bypass and NE to the network for the first time).

Verification Procedure
1. Ensure the NE serial interface (Bypass) is connected to the serial interface (Primary) on the Bypass unit
using the Allot provided DB9 cable.
2. The LED for Mode on the NE will be green when the NE is connected to the Bypass Unit and is active. The
LED will be off (no light) when either the Bypass Unit is not connected to the NE or the NE is in bypass
mode.

3. Connect the Internal interface on the Bypass to the Internal Interface (labeled ‘To NetEnforcer’)

4. Connect the External interface on the Bypass to the Internal Interface (labeled ‘To NetEnforcer’)

5. Connect the Internal interface on the Bypass (NOT labeled ‘To NetEnforcer’. On the left) to the Internal network
router/switch

6. Connect the External interface on the Bypass (NOT labeled ‘To NetEnforcer’. On the left) to the External/Upstream
network router/switch

https://kb.allot.com/display/CUS/External+Bypass+-+Verification+Procedure 1/4
17/06/13 External Bypass - Verification Procedure - Customer Space - Allot Confluence Server

7. On the NX GUI right click on the NE and select ‘Configuration’. In the NE configuration select the ‘Networking’ tab.
Ensure the ‘Enable Bypass Unit’ is checked.

8. Log into the NE via SSH and verify the NE is active with command: ‘go config view network’. System status
should be ‘active’

This is the result of NE being active

https://kb.allot.com/display/CUS/External+Bypass+-+Verification+Procedure 2/4
17/06/13 External Bypass - Verification Procedure - Customer Space - Allot Confluence Server

This is the result of NE being bypass

9. To make NE bypass enter: ‘go config network –dev_mode system:bypass’

10. To make NE active enter: ‘go config network –dev_mode system:active’

11. To do a loop test to ‘Eliminate the Bypass Unit’ disconnect the Bypass unit from the NE. Connect the Internal
Interface (labeled ‘To NetEnforcer’) on the Bypass Unit to the External Interface (labeled ‘To NetEnforcer’). Ensure the
Serial cable is still connected. Traffic should pass through.

12. To do a loop test to ‘Eliminate the NE’ disconnect the Bypass unit from the NE. Connect the Internal Interface on
the NE to Internal network router/switch and the External Interface to the External/Upstream network router/switch.
Ensure the Bypass is disabled (Uncheck the ‘Enable Bypass in 7 above or enter commend ‘go config network –

https://kb.allot.com/display/CUS/External+Bypass+-+Verification+Procedure 3/4
17/06/13 External Bypass - Verification Procedure - Customer Space - Allot Confluence Server

bypass_unit disable’ on NE). Traffic should pass through

13. Also verify that the correct type of cables are being used as well as the Duplex and Speed settings are correct.
Change the Duplex and Speed settings of the NE interfaces to Auto to avoid mismatches.

14. Also verify that the NIC 'Action on failure' is set to the desired action.

Like Be the first to like this

https://kb.allot.com/display/CUS/External+Bypass+-+Verification+Procedure 4/4

You might also like