Configure WAN Connections

Configure a WAN

1. Click Configure in the left menu bar to open the Configure dashboard.
2. Hover over the device in the honeycomb and click Configure to open the site information window.
   
   
    
3. Click Next to open the Configuration > Network screen.
   
   
    
4. Click the WAN icon to open the Network > WAN screen.
   
   
    
5. Click WAN1-Port0 to add one or multiple WAN interfaces.
   
   
    
6. If needed, select the + WAN icon in the interface name drop-down menu to add a WAN. To delete the highest-numbered WAN, select it in the drop-down menu and then click the trash icon.
7. Select the WAN to be configured in the drop-down menu. The WAN connection at appliance port 0 is WAN1, port 1 is WAN2, and so forth.
8. Use the toggle switch to switch a WAN interface on or off.
9. Click a circuit role:
   • Hot Standby—For internet-bound and SD-WAN traffic, a hot-standby circuit has a lower preference than the primary circuit. You can create rules to steer traffic on the interface. Titan sends DIA traffic to a hot-standby interface only if the primary interface is down.
   • Primary—The interface that sends SD-WAN and DIA traffic.
10. Select the transport domain for the WAN connection. You must select the transport domain before you deploy the device:
    • Internet
    • MPLS
11. For a hub–controller topology, toggle to switch the Hub–Controller Staging on or off, and select the staging pool size.
12. In the Tunnel Selection field, choose the tunnel type:
    • For an Internet transport domain:
      • Internet only (Globe icon)—Select for internet access only.
      • SD-WAN only (Hub icon)—Select for SD-WAN access only.
      • SD-WAN and Internet (DIA) Split Tunnel (Combined Globe and Hub icon)—Select for SD-WAN and DIA.
        Note: Spoke sites must have at least one WAN configured as VPN only. This configures the spoke to accept and use the default route propagated by the hub gateway for centralized internet access. It is recommended that you set only one WAN interface as VPN-only for the spoke.
    • For an MPLS transport domain:
      • SD-WAN only (Hub icon)—Select to have the SD-WAN interface send traffic to SD-WAN networks.
      • SD-WAN and Split Tunnel (MPLS)—Select to route data packets between two networks based on network traffic from the LAN. For SD-WAN and Split-Tunnel (MPLS) traffic, you must configure EBGP in the Routing tab and you must select the Redistribution option. By default, the default VRF for the tenant is selected. See Configure Routing.
13. Use the toggle switch to enable or disable remote access VPN. See Configure Remote Access VPN.
14. Enter the VLAN ID for the interface.
15. Enter the maximum transmission unit (MTU), in bytes. The range is 72 through 9000 bytes.
16. In the Network Address field, select DHCP or Static. Note that to change the network address configuration, you must first lock the device. For more information, see Edit WAN or LTE Interfaces in an Active Device, below.
    1. If you select Static enter a private IP address and a gateway, and enter the primary and secondary IP addresses for DNS servers.
    2. For a hub–controller topology, click the NATeD toggle to enable NAT firewall and the enter the public IP address for the firewall WAN interface. Note that you cannot configure DHCP for a hub–controller.
17. Click Advance Configuration (Customized) to configure advanced WAN settings, and then enter information for the following fields.
    
    
     

    Field	Description
    Link Mode	Select the link mode: Auto—This is the default. Full duplex Half duplex Default: Auto
    Link Speed	Select the link speed: Auto—Use for link speeds about 1 Gbps. This is the default. 10 Mbps 100 Mbps 1 Gbps Default: Auto
    Gateway (Group of Fields)	Click On or Off to enable or disable the interface as a gateway. After you enable an interface to be a gateway, the branch becomes a gateway and sends default route to its peer branch or branches. Then select the gateway topology.
    Full Mesh	Select to have all peer devices receive a default route from the device that is set as the gateway. Typically, this topology is not used.
    Hub (in hub-and-spoke topology)	A gateway is used in a hub-and-spoke topology to allow spokes to route traffic through the hub. To deploy and create a spoke site, you must first create a hub on which a gateway is enabled and deployed. Enabling a gateway as a hub allows you to define traffic-steering rules and policies for having the spoke perform local internet breakout for some traffic while sending all other traffic to the hub gateway.
    Uplink Bandwidth	Enter the actual uplink bandwidth purchased from the service provider. The uplink bandwidth is to the traffic from the branch to the outside network.
    Downlink Bandwidth	Enter the actual bandwidth downlink purchased from the service provider. The downlink bandwidth is to the traffic from the outside network to the branch.
    Traffic Shaping (Group of Fields)	Configure schedulers, which assign traffic with different drop-loss priority levels to different outbound queues.
    Guaranteed Rate	Select the guaranteed transmission rate of data packets. You can define the rate as a percentage of the parent interface’s shaping rate or as the line rate. Range: 1 through 100 percent Default: None
    Transmit Rate	Select the transmission rate for data packets. You can define this in percentage of the parent interface’s shaping rate or the line rate. Range: 1 through 100 percent Default: None
    Drop Probability	Select the traffic class and its low/high drop probability percentage. The total guaranteed bandwidth of EF, AF, and BE traffic cannot exceed 100 percent, and the guaranteed rate percentage must be less than the transmit rate percentage. Assured forwarding (AF) Best effort (BE) Expedited forwarding (EF) Network control (NC)
    Ingress Traffic Shaper (Group of Fields)
    Peak Rate	Enter the maximum ingress rate, in kilobits per second (Kbps). Range: 8 through 10000000 Kbps Default: None
    Peak Burst Size	Enter the maximum burst size, in bytes per second. Range: 1000 through 4294967295 bytes per second Default: None
    Link Monitoring (Group of Fields)
    Next-Hop	Click the toggle to enable dynamic link monitoring for next-hop reachability.
    Remote IP	Enter a remote IP address for remote IP reachability through this WAN link to detect link failures. To change the network address configuration, you must first lock the device. For more information, see Edit WAN or LTE Interfaces in an Active Device, below.
    Interval	Enter the frequency, in seconds, at which to send ICMP packets to the IP address. Range: 1 through 60 seconds Default: 3 seconds
    Threshold	Enter the maximum number of ICMP packets to send to the IP address. If the IP address does not respond after this number of packets, the monitor object, and hence the IP address, is marked as down. Range: 1 through 60 Default: 5

18. Click Save to save the settings.

Configure VLAN Subinterfaces on a WAN Interface

Titan devices support VLAN-based subinterfaces. For interfaces that require VLAN support, you create multiple subinterfaces, where each subinterface maps to an individual VLAN ID. The subinterfaces map to the corresponding VLAN IDs.

To configure a VLAN subinterface on a WAN interface, you can configure the VLAN subinterface on a WAN port manually, or you can change the default WAN network template and select this template when you create a new device. You can add multiple VLAN subinterfaces to the WAN port.

Note that if you enable PPPoE on a single VLAN subinterface on a WAN port, PPPoE is automatically enabled on the other VLAN subinterfaces on the same WAN port. For example, if you enable VLAN_100 and VLAN_200 on WAN1_port0, and if you enable PPPoE on VLAN_100, PPPoE is also enabled on VLAN_200. In this scenario, if you also enable a bridge interface on PPPoE VLAN_200, you must modify the username and password on PPPoE VLAN_200 to prevent unauthorized access.

To configure VLAN subinterfaces on a Titan device, you do the following:

• Edit the default configuration template.
• Create a device with a WAN subinterface.
• Add a WAN PPPoE subinterface on an activated or deployed device.

Configure a Remote Access VPN

For customers who purchase a device license that enables the Secure Access VPN feature in the branch devices and HA devices, you can configure a remote access VPN.

After you add a device, you can enable remote access VPN when configuring the WAN network, and then the Remote Access VPN tab is displayed in the device configuration window.

The Remote Access VPN tab has the following options:

• Secure Access Profiles—The secure access client configuration is common for both the organization and gateway. Hence, in device view, it is read only. You configure a secure access client in the Secure Access Default template.
• IPsec Tunnel Address Pool—For a device on which remote access VPN is enabled, select this option to manually enter the WAN IPsec tunnel address pool information.

Before you enable remote access VPN for a device, you must configure a secure access template. For more information, see Configure a Secure Access Service (Remote Access VPN) Template.

Use the toggle switch to enable or disable remote access VPN, and then enter the device fully qualified domain name (FQDN). For remote access VPN, you must configure at least one port on the device with a static IP address, which is used to terminate the remote clients.

To configure a remote access VPN:

1. In the Add Device Details popup window, click Remote Access VPN toggle to enable the option. See Add Devices Using Titan Portal.
2. Configure the secure access default template. See Configure a Secure Access Service (Remote Access VPN) Template.
3. In the Network > WAN window, enter information for the following fields.
   
   
    

   Field	Description
   Remote Access VPN Interface	Click the toggle switch to enable or disable remote access VPN.
   FQDN	Enter the FQDN of the device.
   Network Address
   Address	Enter a static IP address to use to terminate the remote clients.
   Gateway	Enter the IP address of the gateway.
   Name Servers (DNS)
   Primary	Enter the IP address of the primary DNS name server.
   Secondary	Enter the IP address of the secondary DNS name server.

4. Deploy the device, or publish if the device is already activated.
5. Activate the device, and wait until the device is completely up and the monitor shows a device with an IP address.
6. To configure the IPsec tunnel address pool WAN interfaces, select IPsec the Tunnel Address Pool tab, and enter information for the following fields.
   
   
    

   Field	Description
   Start Address	Enter the lowest IP address in the pool assigned to the VSA client.
   End Address	Automatically assigned based on the lowest address.
   Netmask	Automatically assigned based on the lowest address.

7. Upload all necessary key certificates and CA certificate for the device. You can upload a CA certificate only on an activated device. See Configure and Activate SASE Gateway Devices.
8. For a new device, configure the captive portal for all WAN ports with the following port numbers. See Configure Miscellaneous Parameters.
   • HTTP—80
   • HTTPS—443

Edit WAN or LTE Interfaces in an Active Device

After you configure WAN interfaces and deploy or activate the device, you can make the following changes to a WAN or LTE interface:

• Add or remove a WAN, LAN, or LTE interface.
• Switch gateway ON or OFF.
• Update the transport from internet to MPLS or vice versa.
• Enable or disable PPPoE.

To make changes to a WAN or LTE interface, you must first lock the device using the enable lock mode option in the honeycomb view in the Titan Portal home screen. The lock icon displays only if the device is deployed. A blue lock icon indicates that the device is unlocked, and a red red lock icon indicates that the device is locked. After you publish the changes to Titan Portal, you must unlock the device.

To edit WAN interfaces:

1. Click Configure in the left menu bar to open the Configure dashboard.
2. Click the icon in the honeycomb to lock the device.
3. Enter a reason for enabling lock mode in the Enable lock mode popup window and click Yes.
   
   
    
4. Hover over the device in the honeycomb and click Configure to open the site information window.
   
   
5. Click Next to open the Configuration > Network screen.
6. Click the WAN box to open the Network > WAN screen.
   
   
    
7. Click WAN1-Port0 to display a list of available ports and their corresponding WAN numbers.
8. Select a WAN port.
   • Click the icon to delete the selected WAN.
   • Click the + WAN icon to add a WAN interface. The + WAN icon displays only if WAN ports are available to be configured.
     
     
      
9. Click Publish and then click Continue.
   
   
    
10. Click the icon in the honeycomb to unlock the device and then click Yes.
    
    

Configure IPsec VPN Settings

To create an IPsec tunnel to other appliances or applications, you use the IPsec VPN option on the Network > WAN screen. Titan Portal then adds the name of the tunnel to the drop-down menus for WAN static IP routes, steering rules, and firewall rules for route-based IPsec profiles. For policy-based and rule-based VPNs, no zone or menu options are available in static, steering, and security rules. Tunnels use preshared key (PSK) authentication and are built using IKEv1, IKEv2, or both IKEv1 or IKEv2. If you configure the tunnel using IKEv1, ensure that the shared key value for the local authentication and peer authentication are the same.

When you configure IPsec route-based profiles, by default, Titan Portal creates a security rule that allows IPsec traffic and the rule is displayed in the security rule list. For an IPsec profile, the security rule is created with the same name as IPsec route-based profile name. You cannot edit or delete a system-generated default rule for port forwarding or for an IPsec profile. However, you can disable or reorder a default rule to change its priority.

You can click + Add to configure multiple tunnels.

To configure an IPsec tunnel:

1. From the Network > WAN screen, click the IPsec VPN option to display the IPsec VPN fields.
   
   
    
2. In the IPsec VPN option drop-down menu, enter information for the following fields.
    

   Field	Description
   Name	Enter the IPsec tunnel name. Titan Portal adds the tunnel name to the IPsec drop-down menu in the Static IP Route screen.
   Redistribute	Click to make the IPsec tunnel eligible for redistribution into the VPN network when thee tunnel is used as the next hop for a static route.
   VRF	Select a source VRF (routing instance).
   Peer Type	Enter format for the peer value: hostname, fully qualified domain name (FQDN), or IP address.
   Peer Type Value	Enter peer value using the format selected in Peer Type.
   Local Authentication
   Authentication Type	Displays the authentication type (PSK).
   Identity Type	Enter format for the identity type value: email, FQDN, or IP address.
   Identity Type Value	Enter value in the format selected in Identity Type.
   Shared Key	Enter preshared key.
   Peer Authentication
   Authentication Type	Displays the authentication type (PSK).
   Identity Type	Enter format for the identity type value: email, FQDN, or IP address.
   Identity Type Value	Enter value in the format selected in Identity Type.
   Shared Key	Enter the preshared key.
   IKE Version	Select the IKE version: IKEv1 IKEv2 IKEv1 or IKEv2
   Hash Algorithm	Select the hash algorithms to use: MD5—MD5 Message Digest Algorithm SHA-1—Secure Hash Algorithm 1 with 160-bit digest SHA-256—Secure Hash Algorithm 2 with 256-bit digest SHA-384—Secure Hash Algorithm 2 with 384-bit digest SHA-512—Secure Hash Algorithm 2 with 512-bit digest
   Encryption	Select the encryption algorithms to use: 3DES—Triple DES encryption algorithm AES 128—AES CBC Encryption Algorithm with 128-bit key AES 256—AES CBC Encryption Algorithm with 256-bit key
   DH Group	Select the Diffie-Hellman group to use: Diffie-Hellman Group 1—768-bit modulus Diffie-Hellman Group 2—1024-bit modulus Diffie-Hellman Group 5—1536-bit modulus Diffie-Hellman Group 14—2048-bit modulus Diffie-Hellman Group 15—3072-bit modulus Diffie-Hellman Group 16—4096-bit modulus Diffie-Hellman Group 19—256-bit elliptic curve Diffie-Hellman Group 20—384-bit elliptic curve Diffie-Hellman Group 21—521-bit elliptic curve Diffie-Hellman Group 25—192-bit elliptic curve Diffie-Hellman Group 26—224-bit elliptic curve
   IKE Rekey Time	Enter the time interval for how often to regenerate the IKE key. Range: 3600 through 28800 seconds Default: 3600 seconds
   IPsec Transforms	Specify the IPsec transform and Diffie-Hellman group.
   Hash Algorithm	Select the hash algorithms to use: MD5—MD5 Message Digest Algorithm SHA-1—Secure Hash Algorithm 1 with 160-bit digest SHA-256—Secure Hash Algorithm 2 with 256-bit digest SHA-384—Secure Hash Algorithm 2 with 384-bit digest SHA-512—Secure Hash Algorithm 2 with 512-bit digest XCBC—Extended Cypher Block Chaining
   Encryption	Select the encryption algorithm to use: 3DES—Triple DES encryption algorithm AES128—AES CBC encryption algorithm with 128-bit key AES128-CTR—AES counter mode encryption algorithm with 128-bit key AES128-GCM—AES GCM encryption algorithm with 128-bit key AES256—AES CBC encryption algorithm with 256-bit key AES256-GCM—AES GCM encryption algorithm with 128-bit key NULL
   Perfect Forward Secrecy Group	Select the Diffie-Hellman groups to use for PFS: Diffie-Hellman Group 1—768-bit modulus Diffie-Hellman Group 2—1024-bit modulus. Diffie-Hellman Group 5—1536-bit modulus Diffie-Hellman Group 14—2048-bit modulus Diffie-Hellman Group 15—3072-bit modulus Diffie-Hellman Group 16—4096-bit modulus Diffie-Hellman Group 19—256-bit elliptic curve Diffie-Hellman Group 20—384-bit elliptic curve Diffie-Hellman Group 21—521-bit elliptic curve Diffie-Hellman Group 25—192-bit elliptic curve Diffie-Hellman Group 26—224-bit elliptic curve No PFS
   IPsec Rekey Time	Enter the time interval for how often to regenerate the IPsec key. Range: 3600 through 28800 seconds Default: 3600 seconds
   Tunnel Network (Route-Based Only)	Use a route-based tunnel configuration.
   Tunnel IP Local Address	Enter the IP address of the local tunnel interface in CIDR format. If you do not specify a value, the IP address is automatically generated.
   Tunnel IP Remote Address	Enter the IP address of the remote tunnel interface. If you do not specify a value, the IP address is automatically generated.
   Policy-Based VPN	Click the Policy-Based VPN toggle to turn on VPN policies configuration options. If you select this option, click the Add Rule icon to add a policy. You can configure a tunnel either using route-based or policy-based options.     In the Policy-Based VPN popup window, enter information for the following fields.   Name—Enter a name for the policy. Protocol—Select a protocol: Any ICMP TCP UDP Source IP—Enter the IPv4 source address or prefix. Port—Enter the source port number. Destination IP—Enter the IPv4 destination address or prefix. Port—Enter the destination port number. Click Add.

   
   To change the IPsec tunnel type from a route-based tunnel to a policy-based tunnel, or vice versa, you must delete the existing IPsec tunnel and then publish the configuration. Then, add the IPsec tunnel with required tunnel type, and publish the configuration again.
3. Click +Add IPsec Profile. This saves the tunnel to the IPsec VPN screen but not the Titan cloud.
   
   
   
   Use the trash icon to delete a tunnel or the pencil icon to edit a tunnel. Click the Eye icon to display tunnel details.
4. Click Save to save the changes to the Titan cloud. Once saved, Titan Portal adds the IPsec tunnel name to the drop-down menus for WAN static IP routes, steering rules, and firewall rules. See Manage Firewall Policies, Configure Traffic Steering, and Configure Internet Traffic Steering.

Configure PPPoE Settings

Point-to-Point Protocol over Ethernet (PPPoE) is used with DSL services in which individual users connect to a DSL modem over Ethernet. The PPPoE username and password configured on the WAN interface must match settings on the WAN server to be active; otherwise, PPPoE is inactive. You cannot remove or add a new PPPoE instance once a device has been deployed but you can edit the PPPoE username and password at any time.

When PPPoE is active, you can monitor status within the WAN interface from the Monitoring > Network screen. You can also perform a speed test and view steering options from the Speed Test and Steering screens.

Versa Titan supports xDSL interface on CSG355 and CSG365 appliances. You must upgrade these appliances to Versa Operating System^TM VOS^TM (VOS) Release 21.2.1 or later to get the xDSL option displayed in your Versa Titan Portal. GZTP and WiFi are not available for xDSL activation with static IP and PPPoE. Use Versable activation with mobile app to activate the device when xDSL with static IP and PPPoE is configured. You can configure and enable PPPoE only on WAN1 and WAN2 ports before you deploy the device. You use Titan Portal to configure and deploy xDSL device. Titan Mobile can be used only for xDSL device activation and monitoring the status.

To configure PPPoE:

1. Click Configure in the left menu bar to open the Configure dashboard.
2. Hover over the device in the honeycomb and click Configure to open the site information window.
3. Click Next to open the Configuration > Network screen.
4. Click the WAN icon and select the WAN interface.
5. Click the PPPoE tab and switch the PPPoE Status toggle to on.
   
   
    
6. Select an interface type:
   • Ethernet
   • xDSL
7. Select a multiplexing type:
   • LLC
   • VC-MUX
8. Select an instance type in the drop-down menu:
   • Internet Only—Traffic is directed to DIA only.
   • SD-WAN Only—Traffic is directed to the SD-WAN VPN only.
   • SD-WAN and Internet (DIA) Split Tunnel—VPN traffic is directed to the SD-WAN VPN. Internet traffic is directed to DIA.
9. Enter the username and password in the fields provided.
10. Enter the Service Name provided by DSL provider.
11. Enter the name of the access concentrator. The access concentrator name on both the client and the server must be the same to establish the PPPoE session.
12. Enter the virtual path identifier.
    Range: 0 through 256
13. Enter the Virtual channel identifier.
    Range: 32 through 65535; 0 through 31 are reserved
14. Enter the VLAN ID configured for the xDSL line.
15. Click Save to save the settings.

Configure LTE and APN Settings

You can configure Long-Term Evolution (LTE) wireless broadband services on appliances that support LTE. LTE wireless functionality is useful when a branch does not have a wired connection to the internet.

An access point name (APN) establishes a connection to the gateway between the carrier's network and the internet. Your service provider may require specific setting for the connection, and you can enter these APN details manually.

To view LTE settings and update APN settings:

1. Click Configure in the left menu bar to open the Configure dashboard.
2. Hover over the device in the honeycomb and click Configure to open the site information window.
3. Click Next to open the Configuration > Network screen.
4. Click the LTE box to open the Network: LTE Screen.
   
   
    

   Fields	Description
   LTE	Select an existing LTE interface in the drop-down menu, or select +LTE to add an additional interface (up to four total).
   On/Off	Use the  toggle switch to switch an LTE interface on or off.
   Circuit Role	Select a circuit role: Primary—The interface that sends SD-WAN and DIA traffic. Hot Standby—For internet-bound traffic, a hot-standby circuit has a lower preference than the primary circuit. For SD-WAN traffic, a hot-standby circuit has the same default preference as the primary circuit. You can create rules to steer traffic on the interface. Titan sends DIA traffic to a hot-standby interface only if the primary interface is down. In hot-standby mode, LTE dynamic monitoring through WAN and LTE links for next-hop reachability or remote IP reachability to detect link failure is enabled. Monitoring of WAN and LTE links is enabled for both next-hop monitoring and remote IP monitoring with the IP address 8.8.8.8, with ICMP probes. Cold Standby—In cold-standby mode, LTE or WAN circuit and link monitoring is disabled. When you enable cold standby for LTE or any other interface, Titan monitors the primary or secondary path using IP SLA, and the LTE link state goes to Up only when the primary or secondary WAN interface is down.
   Gateway	Switch the  toggle to turn the LTE gateway configuration on or off. You must turn this feature on before the configuration is deployed.
   Transport	Select the transport domain for the LTE connection. You must select the transport domain before you deploy the device: Internet MPLS
   MTU (Required)	Enter the maximum transmission unit (MTU). Range: 72 through 9000 bytes
   Uplink Bandwidth	Enter the actual bandwidth purchased from the service provider. Uplink bandwidth refers to the traffic from the branch to the outside network.
   Downlink Bandwidth	Enter the actual bandwidth purchased from the service provider. Downlink bandwidth refers to the traffic from the outside network to the branch.
   Tunnel Selection	Choose the type of tunnel using the Tunnel Selection drop-down menu: Globe icon—Internet only. This is applicable only for transport domain. Hub icon—SD-WAN only Combined Globe and Hub icon—SD-WAN and Internet (DIA) Split Tunnel
   Network Address	The network address and gateway are set to Auto and cannot be changed.
   Name Servers (DNS)	The primary and secondary name servers are set to Auto and cannot be changed.
   Link Monitoring (Group of Fields)	Enable link monitoring to ensure that cold-standby LTE works with WAN as a primary interface and LTE as a secondary interface. If you enable next-hop monitoring on LTE, next-hop ICMP probes are initiated to install routes. However, many service providers block next-hop ICMP probes. In such cases, you can disable next-hop monitoring on LTE and add only a reachable IP address for monitoring (for example, 8.8.8.8). Note that automatic switchover to a secondary LTE or WAN does not work if all ICMP probes are blocked.
   Next Hop	Click the toggle to enable dynamic link monitoring for next-hop reachability.
   Remote IP	Enter a remote IP address for remote IP reachability through this LTE link to detect link failures.
   Interval	Enter the time interval between monitor packets, in seconds. Range: 1 through 60 seconds Default: 3 seconds
   Threshold	Enter the maximum number of monitor packet retransmissions before the node is marked as down. Range: 1 through 60 Default: 5
   APN	Click Manual to configure the APN manually. APN is set to Auto by default.   Access Point Name (APN)—Enter the access point name (APN) that you received from your service provider. PIN—For a USB modem that is locked with a PIN, enter a PIN number. Username—Enter the username provided by the service provider to use to access the wireless WAN. This username is used when a CDMA modem prompts for a username. Password—Enter the password provided by the service provider to access the wireless WAN. This password is used when a CDMA modem prompts for a password. Click Show/Hide to view the new password.

5. Click Save to save the settings.
6. Verify the settings from the Monitoring screen any time you change between Manual or Auto.

Supported Software Information

Releases 10.3.4 and later support all content described in this article.

Additional Information

Configure and Activate a Site
Configure Miscellaneous Parameters
Configure Routing
Configure Security