Managed gateways

Enrolling your Cisco IOS gateways to Control Hub helps you to simplify device management and allows you to new Webex Calling services. As gateways maintain a connection with Control Hub, you can manage and monitor them from anywhere, along with the rest of your Webex Calling devices.


This process doesn't apply to Cisco IOS Voice Gateways, such as the VG400, which are fully managed as devices in Control Hub.

A small connector application, known as the GuestShell, is responsible for establishing and maintaining a connection from the gateway to Control Hub. The Guest Shell and connector applications are configured and set up using a script, which is run on the gateway from the Webex cloud during the enrollment process.

To simplify the installation process, the script adds a number of necessary gateway configurations.

Gateway connectors

Gateway connectors are small applications that run in the gateway GuestShell to maintain a connection to Control Hub, coordinate events, and collect status information. For more information on GuestShell, see GuestShell.

The gateway connectors are installed on the Cisco IOS XE GuestShell container.

There are two types of connectors:

  • Management connector

  • Telemetry connector

An interactive menu-driven TCL script helps to set up the GuestShell, as well as installation and maintenance of the management connector.

The management connector takes care of gateway enrollment and lifecycle management of the telemetry connector.

After successful completion of enrollment, the management connector downloads and installs the latest telemetry connector.

The following graphic shows how the different components connect in a Webex Calling solution:

As part of TCL script execution, the following information gets collected from the user:

  • External interface

  • DNS server addresses

  • Proxy details

  • Connector IP address

  • Gateway Credentials (username and password)

The TCL script performs the following configurations:

  • Virtual Port Group—Required for guestshell configuration.

  • Guestshell

  • NETCONF Yang

  • SNMP Trap configuration—Required for notifications from Cisco IOS XE.

  • IP Route—To route connector-related traffic through virtual port group.

The TCL script performs the following configurations:

!
interface VirtualPortGroup 0
 ip unnumbered GigabitEthernet1
 no mop enabled
 no mop sysid
!

!
app-hosting appid guestshell
 app-vnic gateway0 virtualportgroup 0 guest-interface 0
  guest-ipaddress 10.65.125.227 netmask 255.255.255.128
 app-default-gateway 10.65.125.142 guest-interface 0
 app-resource profile custom
  cpu 800
  memory 256
  persist-disk 500
 name-server0 72.163.128.140
 name-server1 8.8.8.8
!

!
netconf-yang
netconf-yang cisco-ia snmp-trap-control trap-list 1.3.6.1.4.1.9.9.41.2.0.1
netconf-yang cisco-ia snmp-community-string Gateway-Webex-Cloud
!

!
logging snmp-trap emergencies
logging snmp-trap alerts
logging snmp-trap critical
logging snmp-trap errors
logging snmp-trap warnings
logging snmp-trap notifications
!

!
snmp-server community Gateway-Webex-Cloud RO
snmp-server enable traps syslog
snmp-server manager
!

!
ip route 10.65.125.227 255.255.255.255 VirtualPortGroup0
!

For the sample configuration:

  • GigabitEthernet1 is assigned as the external interface. The IP address of GigabitEthernet1 is 10.65.125.142.

  • The connector IP address must be in the same network as the one chosen for external connectivity. It can be a private network address, but it must have HTTP access to the internet.

  • The TCL script tracks and saves the configuration changes to the Cisco IOS XE startup configuration.

  • As part of the uninstallation process, the TCL script removes the configuration changes.

Limitations and restrictions

Gateway connectors have the following limitations:

  • Cisco 1100 Integrated Services Router platforms

  • High Availability (HA) mode

  • Controller or SD-WAN mode (Site Survivability only supports gateways running in Cisco IOS XE Autonomous mode)

  • Cisco IOS Voice Gateways, such as VG400, which is fully managed as devices in Control Hub.

Prerequisites

Prepare your device for a gateway enrollment:

  • Access to the Control Hub as an organization administrator

  • IP addresses, usernames, and passwords for the devices that you want to configure.

  • Cisco IOS XE Version:

    • Local Gateways—Cisco IOS XE Amsterdam 17.3.4a or later

    • Survivability Gateways—Cisco IOS XE Cupertino 17.9.3a or later

  • System Prerequisites

    • Minimum free memory—256 MB

    • Minimum disk space—2000 MB (including 1100 MB for GuestShell container and 500 MB for connector applications). If an SSD (harddisk:) is installed, this will be used for the connector installation. In all other cases, System bootflash: will be used.

If the bootflash of your router is 4GB and there's less than 2GB of available capacity (the minimum capacity), delete all IOS binary (.bin) images except the one that is currently running. After you delete the files, free up extra space.


The following are optional steps to free up bootflash disk space. Perform the following steps and change the boot files to install mode only if:

  • The router is using the bundled boot mode (booting from .bin).

  • The .pkgs isn't already extracted (install mode).

Use the following steps to expand the binary image and boot from components:

  1. Create a new directory using mkdir bootflash:/image.

  2. Expand the IOS binary image using request platform software package expand file bootflash:/<image>.bin to bootflash:/image.

  3. In configuration mode, remove the current boot options using no boot system.

  4. Configure new boot statement: boot system bootflash:/image/packages.conf.

  5. Exit from configuration mode, save the configuration, and reboot.

  6. Once the router has restarted, use show version to verify that the router booted from bootflash:/image/packages.conf. If so:

    1. Verify that the bootflash:/sysboot directory is empty.

    2. Delete the remaining IOS binary image.

    3. Delete any core images using delete /f /r bootflash:/core/*.

    4. Delete trace log files using delete /f /r bootflash:/tracelogs/*.

    5. If there’s still insufficient disk space, review the remaining files in bootflash: and delete any other nonessential files such as logs and CDRs.

  • A supported Cisco router, which is connected to a network with a path to the internet. The basic configuration must have the following:

    • DNS server configured to resolve public domain names.

    • To configure the DNS server, use the following commands:

      • ip name-server <IP address>

      • HTTP Proxy server if you want to reach the internet through a proxy.

    • HTTP Proxy server if you want to reach to the internet through a proxy.

    • Gateway credentials: Credentials (username and password) with privilege level 15 access that the connector can use to access the gateway through its NETCONF interface.

      To authenticate and authorize NETCONF access, ensure that the default aaa lists are configured as illustrated in the example. You can use any method option in the default list. You can't use a named aaa list to control NETCONF access. If the default lists aren’t configured correctly, you may see an "invalid method list" error message in the system log. 

      aaa new-model
aaa authentication login default radius local
aaa authorization exec default radius local if-authenticated
username test privilege 15 secret <password>

    Network Prerequisites

    • The connector IP address must be in the same network as the one chosen for external connectivity. It can be a private network address, but it must have HTTP access to the internet.


      If you use Virtual CUBE on Amazon Web Services (AWS) as your Local Gateway, refer to Associate a secondary IP address for Virtual CUBE on AWS for steps on how to associate a secondary IP address for connector use.

    • You must be connected to the Control Hub and on-premises devices to complete the enrollment process.

    • URLs for Webex services:

      • *.ucmgmt.cisco.com

      • *.webex.com

      • *.wbx2.com

    • Transport protocols: Transport Layer Security (TLS) version 1.2

    • Import the IOS public certificate authority bundle. The certificates added to the gateway trust pool are used to verify access to Webex servers. Use the following configuration command to import the bundle. 

      crypto pki trustpool import url http://www.cisco.com/security/pki/trs/ios.p7b

Associate a secondary IP address for Virtual CUBE on AWS

If you use Virtual CUBE on AWS as your Local Gateway, perform the following steps on the AWS interface to associate a secondary IP address for connector use.


We recommend that you perform this activity during a maintenance window.

Before you begin

  • To use Virtual CUBE on the Amazon Web Services (AWS) as your Local Gateway, you must associate a secondary private IP address with the gateway interface. You can use this IP address as the connector IP address.

  • Associate an Elastic public IP address with the secondary IP address so that the secondary IP address is publicly available for gateway enrollment.

  • The associated security group policy must allow HTTPS inbound traffic for successful enrollment. You can remove this once enrollment is complete.

1

Go to Services > EC2 > Instances, and select the Cisco gateway instance.

2

In the Network interfaces window, click eth0.

A dialog box displays detailed information about the eth0 interface.

3

Click Interface ID Value.

4

Click Actions, and choose Manage IP address from the drop-down list.

5

Expand eth0 and select assign new IP address and confirm assignment.

Note of this secondary IP address.
6

Click Actions and select Associate Address from the drop-down list.

7

Choose an available public IP address from the Elastic IP address list.

Validate that the selected IP address matches with the secondary IP address that you noted.
8

(Optional) To reassign a public IP address that is currently in use and it’s mapped to another elastic network interface (ENI), click Allow Reassociation.

9

Click Associate Address to associate the public IP address (Amazon elastic IP) with the private IP address of the network interface.

You can now use this private IP address as the Connector IP address while doing connector installation. Use the corresponding public IP address (Amazon elastic IP address) for enrollment in Control Hub.

Add a new gateway instance in Control Hub

Complete the following steps in Control Hub to add a new gateway instance.

If you've already added the gateway to Control Hub and have installed the management connector, you can skip this procedure. Go to Step 5 of Enroll the gateway to Control Hub to complete the enrollment process.

1

Sign in to Control Hub, https://admin.webex.com/.

2

Under SERVICES, click Calling and then click the Managed Gateways tab.

3

Click the Add Gateway button.

4

Copy the tclsh command shown in the Add a Managed Gateway window. You must run the command on the gateway CLI as a part of the management connector installation procedure.

What to do next

You can resume the enrollment process in Control Hub after the connector is installed on the gateway.

Install the gateway connector

Before proceeding with the installation of the management connector, make sure that you meet all the Prerequisites.

  1. Sign in to the gateway using a console or SSH connection, then paste the following string to the router exec command prompt:
Command or Action Purpose

Sign in to the gateway using a console or SSH connection, then paste the following string to the router exec command prompt:

tclsh https://binaries.webex.com/ManagedGatewayScriptProdStable/gateway_onboarding.tcl

 

  • This command downloads and runs a connector installation script. You can copy this string from the dialog that you see immediately after you choose to add a new gateway in Control Hub.

  • If it is not available already, the script downloads the connector package and stores it in the bootflash:/gateway_connector directory.

  • The script also carries out precondition checks for Cisco IOS XE version, available disk space in bootflash, and so on. The precondition check status must be "Passed" to proceed with the installation.

  • With some terminal applications, backspace may not work correctly and copy or paste functionality may be limited while running the script.

If the connector is not set up already, the script takes you to the installation menu; if the connector is set up, it takes you to the home menu.

1

Choose the interface that's in the same network as the address reserved for the connector.


 ===============================================================
             Webex Gateway Connector Installation
 ===============================================================


 Choose the external-interface from the below list of available interfaces:
 ===============================================================
   Number          Interface          IP-Address        Status
 ===============================================================
     1          GigabitEthernet1      10.65.125.142       up    
 ===============================================================

 Enter a number to choose the external interface: 1

 

  • The script creates a Virtual Port Group interface that shares the same IP as the chosen interface. It is used for the routing of GuestShell container traffic.

  • The script displays only the interfaces which are in "up" state and have IP addresses assigned.
2

Configure the DNS server to be used by the connector. By default, use the servers configured in IOS.

These DNS settings were detected in the gateway configuration:
 72.163.128.140 
Do you want to use these settings for the connector? [Y/n]:

 

Y is the default input here. If you press Enter, Y is taken as the input.


 
Detected settings may be overridden if necessary:
These DNS settings were detected in the gateway configuration:
72.163.128.140
Do you want to use these settings for the connector? [Y/n]: n
3

If you need to use a proxy to access the internet, enter the proxy details when prompted.

If the gateway has already been configured with a proxy, the following details are used by default. Type n to override these settings, if required. 


These proxy settings were detected in the gateway configuration:
 Proxy Server : proxy-wsa.esl.cisco.com
 Proxy Port   : 80
Do you want to use these settings for the connector? [Y/n]:

  • If you enter n, the system asks if you require a proxy. Enter the proxy hostname/IP address, if you require one. 

    These proxy settings were detected in the gateway configuration:
Proxy Server : proxy-wsa.esl.cisco.com
Proxy Port : 80
Do you want to use these settings for the connector? [Y/n]:n
Proxy required? [y/N]: y
Enter proxy hostname/IP address:

  • Reenter the password if the proxy requires one.
4

Configure SNMP trap settings.

To push notifications to the Cisco Webex cloud, the script updates the SNMP trap configuration level in the router if it is set below the notification level. The system prompts you to confirm whether to change the SNMP trap configuration to the notification level. To retain the current SNMP trap configuration level, select n. 


SNMP Traps for syslog messages are
configured at <alerts> level and they would be changed to <notifications>
level in order to push notifications to the Webex Cloud.
Please confirm if it is ok to proceed?:  [Y/n]:
5

Enter the connector IP address. 


 Enter Connector IP address: 10.65.125.227
6

Enter the username and password that the connector uses to access the router NETCONF interface. 


Enter Gateway username: lab
Enter Gateway password: ***
Confirm Gateway password: ***

 

Type in the password manually. Copy and paste might not work.

Enter the gateway credentials that you identified in the Prerequisites section. The connector uses the credentials to access the router IOS NETCONF interface.

You get the "Cloud connector is installed successfully" message after the successful installation.

===============================================================
                 Webex Managed Gateway Connector
===============================================================

  *** Cloud connector is installed successfully. ***
-------------------------------------------------------
         *** Interface Status ***
-------------------------------------------------------
   Interface               IP-Address          Status
-------------------------------------------------------
   GigabitEthernet1        10.65.125.142       up    
   VirtualPortGroup0       10.65.125.142       up    
   Connector               10.65.125.188       up
   
-------------------------------------------------------

          *** App Status ***
-------------------------------------------------------
 Service                 Status
-------------------------------------------------------
 Guestshell              RUNNING
 Management Connector    RUNNING
-------------------------------------------------------

===============================================================
 Select option h for home menu or q to quit:

 

You can quit the script by choosing the 'q' option after successful installation. If there is installation failure, you can choose 'h' option to change any settings, collect logs, and so on. Refer to the Post-installation activities section for more details. If you want to retry installation, you can choose uninstallation and then relaunch the script to try installation again.


 

You can launch (or relaunch) the TCL script directly using bootflash:gateway_connector/gateway_onboarding.tcl or https://binaries.webex.com/ManagedGatewayScriptProdStable/gateway_onboarding.tcl at any given point.

7

Enter the username and password that the connector uses to access the router NETCONF interface. 


Enter Gateway username: lab
Enter Gateway password: ***
Confirm Gateway password: ***

 

Type in the password manually. Copy and paste might not work.

Enter the gateway credentials that you identified in the Prerequisites section. The connector uses the credentials to access the router IOS NETCONF interface.

You get the "Cloud connector is installed successfully" message after the successful installation.

===============================================================
                 Webex Managed Gateway Connector
===============================================================

  *** Cloud connector is installed successfully. ***
-------------------------------------------------------
         *** Interface Status ***
-------------------------------------------------------
   Interface               IP-Address          Status
-------------------------------------------------------
   GigabitEthernet1        10.65.125.142       up    
   VirtualPortGroup0       10.65.125.142       up    
   Connector               10.65.125.188       up
   
-------------------------------------------------------

          *** App Status ***
-------------------------------------------------------
 Service                 Status
-------------------------------------------------------
 Guestshell              RUNNING
 Management Connector    RUNNING
-------------------------------------------------------

===============================================================
 Select option h for home menu or q to quit:

 

You can quit the script by choosing the 'q' option after successful installation. If there is installation failure, you can choose 'h' option to change any settings, collect logs, and so on. Refer to the Post-installation activities section for more details. If you want to retry installation, you can choose uninstallation and then relaunch the script to try installation again.


 

You can launch (or relaunch) the TCL script directly using bootflash:gateway_connector/gateway_onboarding.tcl or https://binaries.webex.com/ManagedGatewayScriptProdStable/gateway_onboarding.tcl at any given point.

Enroll the gateway to Control Hub

Before you begin

The management connector must be installed on the gateway already.

1

Check that the Add a Managed Gateway window displays in Control Hub.

If the window doesn't display, under SERVICES, click Calling, select the Managed Gateways tab, and click Add Gateway.

2

In the Add a Managed Gateway window, check I have installed the management connector on the gateway and click Next.


 
Make sure that the connector is successfully installed before you perform this step.

3

At the Add a Managed Gateway screen, enter the connector IP address that you entered during the connector installation procedure, and a preferred display name for the gateway

4

Click Next.


 

  • Ensure that your browser is configured to allow popups for this page before you click Next.

  • Access the connector management page and complete the enrollment process within an hour.

    If it's not possible to complete the enrollment within an hour, restart the enrollment process from step 1 of this procedure. The gateway details that you entered earlier will not be saved.

    To continue this process from a different or restarted browser (within an hour), select the Enroll Gateway option for your gateway on the Control Hub Managed Gateways page.

  • The connector web server uses a self-signed certificate. In the browser, you must allow or accept the certificate.
A browser tab that connects to the connector management page on the router opens so that you can complete the enrollment.
5

To login, enter the Gateway Admin Username and Password that you used during the connector installation procedure, listed in step 6.

6

Click Enroll Now to open a new window for authenticating the connector to the Webex cloud.


 
Make sure your browser allows popups.

7

Sign in using a Webex administrator account.

8

Check Allow Access to the Gateway Management Connector .

Gateway connector states

Connector states of both management and telemetry connectors display on the connector details page.

  • Log in to your customer organization at https://admin.webex.com.

  • Go to Services > Calling.

  • Click Manage Gateways.

Table 1. Management Connector States

Management connector states

Connectivity status

Description

Running

Connected

Indicates that the connector is in the running state and the device is connected to the Cisco Webex cloud.

Running

Not Connected

Indicates that the connector is in the running state, but the device is not connected to the Cisco Webex cloud.

Running

Heartbeat Failed

Indicates that the connector is in the running state, but heartbeat failed for the enrolled device.

Running

Enrollment Failed

Indicates that the connector is in the running state, but enrollment of the device to the Cisco Webex cloud failed.

Table 2. Telemetry Connector States

Telemetry Connector States

Connectivity Status

Description

Not Installed

Not Available

Indicates that the telemetry connector is not installed.

Downloading

Not Available

Indicates that the telemetry connector download is in progress.

Installing

Not Available

Indicates that the telemetry connector installation is in progress.

Not configured

Not Available

Indicates that the telemetry connector installation is successful, but services have not started or are configured yet.

Running

Not Available

Indicates that the telemetry connector is running but information about its connectivity to the Cisco Webex cloud is not available.

Running

Connected

Indicates that the telemetry connector is in the running state and it is connected to the Cisco Webex cloud.

Running

Not Connected

Indicates that the telemetry connector is in the running state but it is not connected to the Cisco Webex cloud.

Running

Heartbeat Failed

Indicates that the telemetry connector is in the running state and the telemetry heartbeat to the Cisco Webex cloud failed.

Disabled

Not Available

Indicates that the telemetry connector is in the maintenance mode (disabled state) and information about its connectivity to the cloud is not available.

Stopped

Disconnected

Indicates that the telemetry connector is in the stopped state (may be partial or both telemetry service and web-socket broker service are stopped) and it is not connected to the Cisco Webex cloud.

This section describes alarms generated in the telemetry connector module. The Telemetry Connector alarms get sent to the Cisco Webex cloud and displayed in Control Hub.

The following table describes the connector-related messages:

Title

Description

Severity

Solution

Telemetry module started.

This message is sent when the Telemetry module becomes functional.

Alert

NA

Telemetry module upgraded.

This message is sent when the Telemetry module has been upgraded from "old_version" to "new_version".

Alert

NA

NETCONF connection failure.

This alarm is raised when the Telemetry module fails to establish NETCONF connection to the gateway.

Critical

Verify that NETCONF is enabled on the gateway and that it is reachable from the connector. Try to disable and enable the connector container. If the problem persists, go to https://help.webex.com/contact, click Support, and raise a case.

NETCONF authentication failure.

This alarm is raised when the Telemetry module fails to establish NETCONF connection to the gateway.

Critical

Verify that username and password are configured correctly on the gateway. Try to disable and enable the connector container. If the problem persists, go to https://help.webex.com/contact, click Support, and raise a case.

NETCONF SNMP events subscription failure.

This alarm is raised when the Telemetry module fails to create a NETCONF subscription for SNMP events.

Critical

Verify that NETCONF is enabled on the gateway and that it is reachable in the connector. Try to disable and enable the connector container. If the problem persists, go to https://help.webex.com/contact, click Support, and raise a case. For more information on how to enable and disable, see Post-installation activities.

Telemetry metrics collection failure.

This alarm is raised when the Telemetry module fails to collect metrics from the gateway through a NETCONF GET query.

Critical

Verify that NETCONF is enabled on the gateway and that it is reachable from the connector. Try to disable and enable the connector container. If the problem persists, go to https://help.webex.com/contact, click Support, and raise a case. For more information on how to enable and disable, see Post-installation activities.

Telemetry gateway connection failure.

This alarm is raised when the connector fails to establish a web socket connection with the telemetry gateway.

Critical

Verify that the telemetry gateway URL (*.ucmgmt.cisco.com) is in the allowed list of the enterprise firewall and reachable from the gateway. If the problem persists, go to https://help.webex.com/contact, click Support, and raise a case.

Failure of telemetry gateway connection through proxy.

This alarm is raised when the connector fails to establish a connection to the configured proxy.

Critical

Verify that proxy details (IP address and port credentials) are configured correctly on the connector and that the proxy is reachable. If the problem persists, go to https://help.webex.com/contact, click Support, and raise a case.

Post-installation activities

Local Administration of the Management Connector

You can use Webex Calling with your gateway after installing the connector successfully. If required, you can update a number of connector settings using the options available in the script menu:


You can relaunch the script at any time using the following command: tclsh bootflash:/gateway_connector/gateway_onboarding.tcl. 

===============================================================
Webex Managed Gateway Connector
===============================================================
Options
s : Display Status Page
v : View and Modify Cloud Connector Settings
e : Enable Guestshell
d : Disable Guestshell
l : Collect Logs
r : Clear Logs
u : Uninstall Connector
q : Quit
===============================================================
Select an option from the menu:

Enable Guestshell

Enable the cloud connector using the e: Enable Guestshell menu option. This changes the status of the connector from INACTIVE to ACTIVE.

Disable Guestshell

Disable the cloud connector using the d: Disable Guestshell menu option. This changes the status of the connector from ACTIVE to INACTIVE.

Uninstall Connector

Uninstall the cloud connector using the u: Uninstall Connector menu option. This deletes all the data in the Guestshell container and removes all configurations that are related to the cloud connector.

Collect Logs

Collect the logs using the l: Collect Logs menu option. The system displays the location where these logs are stored after collecting the logs.


If you have an active support case with Cisco TAC, you can attach the logs directly to your service request using the command copy bootflash:/guest-share/<log-filename> scp://<case-number>:<cxd-token>@cxd.cisco.com .

The following is a sample command:

vcubeprod#copy bootflash:/guest-share/gateway_webex_cloud_logs_2022114090628.tar.gz scp://123456789:a1b2c3d4e5@cxd.cisco.com

Clear Logs

Clear all log files in the device using the r: Clear Logs menu option. This deletes all existing logs except the latest logs of the Tcl script and connectors.

View and Modify Cloud Connector Settings

Make the following changes to the existing settings of a cloud connector using the v: View and Modify Cloud Connector Settings menu option. 


===============================================================
                Webex Managed Gateway Connector
===============================================================
		Script Version         : 2.0.2
		Hostname/IP Addr       : 10.65.125.188
		DNS Server(s)          : 10.64.86.70
		Gateway Username       : lab
		External Interface     : GigabitEthernet1
		Proxy Hostname/IP Addr : proxy-wsa.esl.cisco.com:80
===============================================================
             Options
               c :  Update Gateway Credentials
               e :  Update External Interface
               p :  Update Proxy Details
               n :  Update DNS Server
               k :  Update Connector Package Verification Key
               l :  Modify log level for Cloud Connector
               h :  Go to home menu
               q :  Quit

===============================================================
                        Select an option from the menu: c

Update Gateway Credentials

Update the gateway username and password using the c: Update Gateway Credentials menu option.

Update External Interface

Change the interface to which the connector is bound and the connector IP address using the v: View and Modify Cloud Connector Settings menu option.

Update Proxy Details

You can perform the following tasks using the p: Update Proxy Details menu option:

  • i: Update Proxy IP and Port

  • c: Update Proxy Credentials

  • r: Remove Proxy Credentials

  • a: Remove All Proxy Details

  • h: Go to home menu

Update Connector Package Verification Key

If you have a technical issue and are asked by the support engineer to replace your package verification key, upload the new gateway-webex-connectors.gpg file to bootflash:/gateway_connector/ and use the k: Update Connector Package Verification Key menu option to verify.

Modify Log Level for the Management Connector

Change the logging level for the connector using the l: Modify log level for Cloud Connector menu option and then selec one of the following options: 


===============================================
		  Number      Log Level 
===============================================
		    1           DEBUG 
		    2           INFO 
		    3           WARNING 
		    4           ERROR 
		    5           CRITICAL 
===============================================

Manage your gateway instance in Control Hub

To manage your gateway instance:

  1. Under SERVICES, click Calling, and then click the Managed Gateways tab.

  2. For the applicable gateway instance, click the adjacent dots (…) in the Actions column and select the applicable action.

Pause Connector instructs the management connector to stop the telemetry connector. You can use this option to stop the telemetry connector temporarily while troubleshooting any issues with a gateway. When you pause the connector, services such as configuration validation doesn’t work. Use the Resume Connector action to restart the telemetry connector.

  1. Click Pause Connector from the Actions menu to pause your management connector.
  2. To resume the connector that you paused, click Resume Connector in the Actions menu.
  Command or Action Purpose
1

Click Pause Connector from the Actions menu to pause your management connector.

2

To resume the connector that you paused, click Resume Connector in the Actions menu.

Control Hub records and displays the event history for your managed gateways. View the details of an individual gateway or the consolidated details of all your managed gateways.

  1. Click Event History in the Calling page for the event details of all your managed gateways.
  2. For event details specific to a gateway, click Event History in the Actions menu for that gateway.
  Command or Action Purpose
1

Click Event History in the Calling page for the event details of all your managed gateways.

2

For event details specific to a gateway, click Event History in the Actions menu for that gateway.

  1. From Actions menu, click Delete Gateway to delete any of your gateway instances.
  2. Click Confirm.
  Command or Action Purpose
1

From Actions menu, click Delete Gateway to delete any of your gateway instances.

2

Click Confirm.


 

You can’t delete a gateway instance with assigned services. You must unassign the services first.

Where to go next