The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter provides step-by-step procedures for many of the workflows and operations that you can perform with Cisco IOx Local Manager.
App lifecycle workflows include the operations that you use to add, activate, deactivate, start, stop, upgrade, and delete an app.
There is no limit, other than system resource restrictions, on the number of apps that can simultaneously have the status of DEPLOYED, For PAAS apps, there also is no limit on how many can simultaneously have the status of ACTIVATED, or STARTED. For VM apps, only one can have the status of ACTIVATED or STARTED at a time.
The following sections describe these workflows:
Adding an app uploads the app tarball (a file in tar format) to the host system. After you add the app, it appears on the Cisco IOx Local Manager Applications page and has status DEPLOYED. System CPU and RAM resources are not yet reserved for the app. An app with this status can be activated, upgraded, or deleted.
To add an app, perform the following steps.
Make sure that the app tarball is stored in a local or network location that the system from which you logged in to Cisco IOx Local Manager can access.
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Click the Add/Deploy button on the Applications page.
The Deploy application dialog box displays.
Step 3 In the Deploy application dialog box, take these actions:
a. In the Application ID field enter, a unique identifier to be assigned to the app.
The identifier can contain up to 64 letters, numbers, and underscores (_), in any combination.
b. Click the Choose File button and follow the on-screen prompts to locate and select the app tarball.
The file uploads to the host system. This process can take some time. When the upload completes, the Successfully Deployed dialog box displays.
To ensure that the upload completes successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the upload is in process.
Step 4 In the Successfully Deployed dialog box, click OK .
Activating an app reserves host system CPU and memory (RAM) resources that the app requires to run, designates the network from which the app obtains its IP address, and assigns host system serial ports for use by the app, if requested. After you activate an app, its status on the Cisco IOx Applications page appears as ACTIVATED.
You can activate an app that has a status of DEPLOYED.
As part of the activation process, you designate a resource profile for the app. A resource profile designates the amount of CPU and memory resources that the app needs to run. You can choose from several preset resource profiles or enter custom values for a profile. See the “App-ID > Resources Page” section for more information.
When an app is activated, the host system reserves the resources that the app needs to run, but the resources are not used until the app starts. You cannot activate an app if the host system does not have sufficient resources available for the app to run.
In addition, for a PAAS app, the appropriate cartridges must be installed before the app can be activated.
To activate an app, follow these steps:
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Make sure that DEPLOYED appears in the Status field for the app that you want to activate.
Step 3 Click activate in the Actions field for the app that you want to activate.
The App-ID page for the app appears.
Step 4 Makes sure that the Resources tab is selected on the App-ID page.
Step 5 In the Resource Profile area, take either of these actions to choose a resource profile, which designates the host system CPU and memory resources that the app requires when it runs:
The system enters information in the CPU and Memory fields based on the option that you choose. In this case, these fields become read only.
Make sure that you do not enter a CPU or memory value that exceeds the available CPU or memory resources that are displayed at the bottom of the Resource Profile area. If you enter a value that exceeds resource availability, the app cannot be activated.
If needed, refer to the app documentation or developer for information regarding resources that an app requires when it runs.
Step 6 In the Network Configuration area, choose an option from each drop-down to designate the logical network from which the app obtains its IP address for the corresponding the port.
The ports in this area appear as eth X , where X is a number. The number of ports depend on the number of network interfaces that the app defines in its metadata. For example, if the app metadata defines one network interface, eth0 appears in the this area. If the app metadata defines two network interfaces, eth0 and eith1 appear in this area.
The options that appear in the drop-down list include either of the following terms in their descriptions:
Step 7 (Optional) If the app metadata requests TCP or UDP ports to be open on a network interface and if the interface is connected to a NAT network, take these actions to configure how TCP and UDP ports on the host system are mapped to internal ports of the app:
a. Click the Port Mapping link that corresponds to the network interface for which you want to configure port mapping. (This link appear only if the app metadata requests TCP or UDP ports to be open on a network interface and if the interface is connected to a NAT network.)
b. Take either of these actions in the Port Mapping dialog box that appears:
– To cause the system to map ports automatically, click the Auto radio button. The system takes this action by default.
– To enter port mapping information manually, click the Custom radio button. The Port Mapping table provides a description of each internal port and the corresponding internal ports that the app requests, as defined in the metadata for the app. In each the External Port(s) field, enter the ports on the host system to which you want to map the corresponding internal ports.
Step 8 (Optional) To manually configure eth X TCP and UDP port mappings for a NAT network, take the following actions.
If you skip this step, the system configures these port mappings automatically based on a range of ports that is defined in the Cisco IOx configuration.
a. In the Network Configuration area, click the Port Mapping link that corresponds to the logical NAT network for which you want to configure port mappings.
The Port Mapping dialog box appears. This dialog box lists the TCP and UDP internal ports that are defined by the metadata for the app. It also lists the external ports to which each internal port is mapped. An external port value of auto indicates that the system assigns external ports for NAT automatically.
b. In the Port Mapping dialog box that displays, click the custom radio button.
If you click the Auto radio button, the system assigns external ports for NAT automatically, and the other options in this dialog box are not available for editing.
c. In each External Port(s) field, enter the port or port range to which the corresponding internal port should be mapped. To enter a port range, separate the first and last port in the range with a hyphen (-).
Step 9 In the Serial Access Configuration area, click the radio button or buttons that correspond to the host system serial port or ports that you want to assign for use by the app.
This area appears only if the app metadata requests that a serial port on the host system be assigned for use by the app.
Step 10 Click the Activate button at the bottom of the Resources tab.
If sufficient CPU and memory resources are available on the host system, the activation process executes. This process can takes some time.
To ensure that the activation completes successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the activation is in process.
Deactivating an app releases the host system CPU and memory (RAM) resources that were reserved for the app and makes these resources available of other uses. After you deactivate an app, its status on the Cisco IOx Applications page appears as DEPLOYED.
You can deactivate an app that has a status of ACTIVATED or STOPPED.
To deactivate an app, perform the following steps. This procedure has the same effect as clicking the Deactivate button on the App-ID > Resources page.
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Make sure that ACTIVATED or STOPPED appears in the Status field for the app that you want to deactivate.
Step 3 Click deactivate in the Actions field for the app that you want to deactivate.
The deactivation process executes. This process can take some time. A progress bar indicates the status of the deactivation process.
To ensure that process executes successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the app is deactivating.
Starting an app initiates starts the app container for the app on the host system. CPU and memory (RAM) resources that were reserved for the app become in use. After you start an app, its status on the Cisco IOx Applications page appears as RUNNING.
You can start an app that has a status of ACTIVATED or STOPPED.
To start an app, follow these steps:
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Make sure that ACTIVATED or STOPPED appears in the Status field for the app that you want to start.
Step 3 Click start in the Actions field for the app that you want to start.
The starting process executes. This process can take some time.
To ensure that the app starts successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the app is starting.
Stopping an app immediately shuts down its app container on the host system. CPU and memory (RAM) resources that were used by the app remain reserved for it but are not in use. After you stop an app, its status on the Cisco IOx Applications page appears as STOPPED.
You can stop an app that has a status of RUNNING.
To stop an app, follow these steps:
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Make sure that RUNNING appears in the Status field for the app that you want to stop.
Step 3 On the Applications page, click stop in the Actions field for the app that you want to stop.
The stopping process executes. This process can takes some time.
To ensure that the app stops successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the app is stopping.
Upgrading an app replaces it with another version. The replacement app must be in a tarball (a file in tar format).
You typically use this operation to replace an app with a newer version or with a version that addresses issues in the existing version. After you upgrade an app, its status on the Cisco IOx Applications page appears as DEPLOYED
You can upgrade an app that has a status of DEPLOYED.
To upgrade an app, perform the following steps.
Make sure that upgrade tarball is stored in a local or network location that the system from which you logged in to Cisco IOx Local Manager can access.
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Make sure that DEPLOYED appears in the Status field for the app that you want to upgrade.
Step 3 On the Applications page, click upgrade in the Actions field for the app that you want to upgrade.
The Upgrade application dialog box appears.
Step 4 In the Upgrade application dialog box, take these actions:
a. Make sure that the Application Id field shows the identifier of the app that you want to upgrade.
b. Click the Browse button and follow the on-screen prompts to locate and select the upgrade tarball.
c. (Optional) Check the Preserve Application Data check box if you want the upgrade process to preserve existing app data.
This data includes information written to the app directory, app log files, and app configuration files. If you do not check this check box, the upgrade process deletes this data.
The upgrade process executes. This process can take some time.
To ensure that the upgrade completes successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the upgrade is in process.
Deleting an app removes it from the host system and releases CPU and memory (RAM) resources that were reserved for the app. After you delete an app, it no longer appears on the Cisco IOx Applications page.
You can delete an app that has a status of DEPLOYED.
To delete an app, follow these steps:
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Make sure that DEPLOYED appears in the Status field for the app that you want to delete.
Step 3 Click delete in the Actions field for the app that you want to delete.
In the dialog box that prompts you to confirm the deletion, click Yes .
To ensure that the app deletes successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the app deletes.
App management workflows include the operations that you use for various app management activities, including updating an app configuration file, accessing an app via a console, and downloading an app log file.
These workflows also include operations that you use to upload files to the /data directory or subdirectory in an app container, download files to your local system, and delete files or subdirectories from the /data directory in an app container. The files can be configuration files or other files that an app needs when it runs.
The following sections describe the app management workflows:
When an app starts, it can read its specific configuration information from a configuration file. This file is named package_config.ini. It is a text file that is stored in the /data directory in the app container for the app.
The package_config.ini file is included in the app .tar package. Its contents and format are flexible and are defined by the app developer. It must be a text file, and its name and location cannot be changed.
This section explains how to update the contents of an package_config.ini file from Cisco IOx Local Manager. You also can update this file by accessing the /data directory in the app container through a console and editing package_config.ini.
To update an app configuration file from Cisco IOx Local Manager, follow these steps:
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Click manage in the Actions field for the app for which you want to update a configuration file.
The App-ID page for the app appears.
Step 3 On the App-ID page, choose the App-Config tab.
Step 4 In the App-ID > App-Config page, take these actions:
a. In the text field, enter configuration information for the app.
If an app is running, you can access its container (for a PAAS app) or VM (for a KVM app) via a console. After you access the container or VM, you can use Linux console commands to obtain information about the app.
To access an app via a console, perform the following steps.
Use Cisco IOS configuration options to forward an SSH port on the router that you want to use for console access to port 22 on the Cisco IOx host system. For instructions, see your Cisco IOS documentation.
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Make sure that RUNNING appears in the Status field for the app that you want to access.
Step 3 Click manage in the Actions field for the app that you want to access.
The App-ID page for the app appears.
Step 4 On the App-ID page, choose the App-Info tab.
Step 5 On the App-ID > App-Info page, take these actions to obtain the private key that you need for console access:
a. In the Console Access area, click the app_id .pem link that appears in the sample command, where app_id is the identifier of the app.
b. In the dialog box that displays, highlight and copy all text that displays.
Make sure to include the “-----BEGIN RSA PRIVATE KEY-----” and “-----END RSA PRIVATE KEY-----” text.
c. Click the OK button to close the dialog box.
Step 6 On the system from which you logged in to Cisco IOx Local Manager, take these actions:
a. Use a text editor to create a text file called app_id .pem, where app_id is the identifier of the app whose container or VM you want to access.
b. Paste the private key that you copied into this file, and save it locally.
c. Make sure that this file has the Linux permission 700.
Step 7 Take these actions to connect to the host system from a console:
a. From the console system, start an SSH client, and enter the command that appears in the Console Access area on the App-ID > App-Info page.
– Replace <SSH_PORT > with the port number for console access to the host system.
– Replace app_id .pem with the path to the file that you created in Step 6, if the file is not in the current directory.
b. Use the commands in your SSH client to complete the connection process.
An app writes information about its operation and related activities to app log files that it creates in the /data/logs directory in the app container for the app. You can download an app log file from the host system to the location of your choice.
To download an app log file, follow these steps:
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Click manage in the Actions field for the app for which you want to download a log file.
The App-ID page for the app appears.
Step 3 On the App-ID page, choose the Logs tab.
Step 4 On the App-ID > Log page, click Download in the Download field for the app log file that you want.
Step 5 Follow the on-screen prompts to save the file in the location of your choice.
Uploading a file puts a file into the designated location under the /data directory of the container for an app. The app must be in the ACTIVATED, RUNNING, or STOPPED state. This operation is not available for use when an app is in the DEPLOYED state.
To upload a file to an app /data directory, follow these steps:
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Make sure that ACTIVATED , RUNNING , or STOPPED appears in the Status field for the app for which you want to upload a file.
Step 3 Click manage in the Actions field for the app for which you want to upload a file.
The App-ID page for the app appears.
Step 4 On the App-ID page, choose the App-DataDir tab.
Step 5 In the App-ID > App-DataDir page, click the Upload button.
The Upload Configuration dialog box displays.
Step 6 In the Upload Configuration dialog box, take these actions:
a. If you want to upload the file to a subdirectory of the /data directory, enter that subdirectory path in the Path field. Do not precede the path with any text, including a slash ( / ) or /data .
If you enter a path that does not exist, the system creates that path under the /data directory.
If you want to upload the file to the top level of the /data directory, do not enter a path in this field.
b. Click the Browse button and follow the on-screen prompts to navigate to and select the file to upload.
The upload process executes. This process can take some time. A progress bar indicates the status of the upload process.
To ensure that the file uploads successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the file is uploading.
Downloading a file from an app /data directory file saves a copy of the file to your local PC. The app for which you are downloading a file must be in the ACTIVATED, RUNNING, or STOPPED state. This operation is not available for use when an app is in the DEPLOYED state.
To download a file from an app /data directory, follow these steps:
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Make sure that ACTIVATED , RUNNING , or STOPPED appears in the Status field for the app for which you want to download a file.
Step 3 Click manage in the Actions field for the app for which you want to download a file.
The App-ID page for the app appears.
Step 4 On the App-ID page, choose the App-DataDir tab.
Step 5 In the App-ID > App-DataDir page, take these actions:
a. In the Name field, navigate to and click the name of the file that you want to download.
b. Follow the on-screen prompts to save the file.
Deleting a file or directory from an app /data directory permanently removes the item from the directory. The app for which you want to delete a file or directory must be in the ACTIVATED, RUNNING, or STOPPED state. This operation is not available for use when an app is in the DEPLOYED state.
To delete a file or directory from an app /data directory, follow these steps:
Step 1 Choose Applications from the Cisco IOx Local Manager menu bar.
The Applications page displays.
Step 2 Make sure that ACTIVATED , RUNNING , or STOPPED appears in the Status field for the app for which you want to delete a /data directory file or directory.
Step 3 Click manage in the Actions field for the app for which you want to delete a /data directory file or directory.
The App-ID page for the app appears.
Step 4 On the App-ID page, choose the App-DataDir tab.
Step 5 In the App-ID > App-DataDir page, click delete in the Actions field for the file or directory that you want to delete.
Step 6 In the dialog box that prompts you to confirm the deletion, click Yes .
The delete process executes. This process can take some time.
To ensure that the file deletes successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the file is deleting.
A Cisco IOx app can be a PAAS type, a KVM type, LXC app, or a Docker type. Unlike a KVM, Docker, or LXC, a PAAS app, which typically is created with a higher level language such as Java or Python, is in a package that contains only files for the app logic. The package does not include Linux operating system files or the root file system that the app requires.
To activate, a PAAS app requires cartridges, which are Cisco-provided files that you install on the host system.
If an app requires cartridges but the cartridges are not yet installed, you can still add the app in Cisco IOx Local Manager. However, you must install the required cartridges before you can activate the app. To determine whether an app requires cartridges, you can look at the Cartridge Required field on the App-ID > App-Info page. See the “App-ID > App-info Page” section for more information.
Cartridge management workflows include the operations that you use to install, delete, and view information about cartridges. The following sections describe these workflows:
Installing a cartridge uploads it to the host system and makes it available to the apps that require it.
To install cartridge, perform the following steps.
Make sure that the cartridge file is stored in a local or network location that the system from which you logged in to Cisco IOx Local Manager can access.
Step 1 Choose Cartridges from the Cisco IOx Local Manager menu bar.
Step 2 Click the Install button on the Cartridges page.
The Deploy Cartridge dialog box displays.
Step 3 In the Deploy Cartridge dialog box, take these actions:
a. Click the Browse button and follow the on-screen prompts to locate and select the cartridge file.
The cartridge file installs on the host system. This process can take some time. When the upload completes, the Successfully Deployed dialog box displays.
To ensure that the cartridge deploys successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the deployment is in process.
Step 4 In the Successfully Deployed dialog box, click OK .
Deleting a cartridge removes it from the host system. Apps that require this cartridge cannot be activated until the cartridge is installed again
To delete cartridge, perform the following steps.
Deactivate all apps that use the cartridge, as described in the “Deactivating an App” section.
Step 1 Choose Cartridges from the Cisco IOx Local Manager menu bar.
Step 2 On the Cartridges page, click Delete in the Actions field for the cartridge that you want to delete.
Step 3 In the dialog box that prompts you to confirm the deletion, click Yes .
The delete process executes. This process can take some time.
To ensure that the cartridge deletes successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the cartridge is deleting.
You can view detailed information about any cartridge that is installed on the host system. To do so, follow these steps:
Step 1 Choose Cartridges from the Cisco IOx Local Manager menu bar.
Step 2 On the Cartridges page, click Info in the Actions field for the cartridge for which you want to view detailed information.
The Cartridge Information window displays.
Cisco Data in Motion runs on a Cisco IOx host system and provides a middleware service to Cisco IOx apps. Cisco Data in Motion also can be used as a standalone service. The Cisco Data in Motion middleware service must be started before an app can use it. This service requires you to upload a license before starting it.
The following sections describe the workflows that relate to middleware management:
Uploading a Cisco Data in Motion license puts the license on the host system so that the Cisco Data in Motion service can run.
To upload a Cisco Data in Motion license, perform the following steps.
Make sure that the Cisco Data in Motion license file is stored in a local or network location that the system from which you logged in to Cisco IOx Local Manager can access.
Step 1 Choose Middleware Service from the Cisco IOx Local Manager menu bar.
The Middleware Service page displays.
Step 2 If the Status field for the service for which you want to upload the license shows Stopped , click start in the Actions field for the service.
Step 3 Click license in the Actions field for the service for which you want to upload the license.
The Upload License File dialog box displays.
Step 4 In the Upload License File dialog box, take these actions:
a. In the Login name field, enter the user name that you use to log in to Cisco IOS.
This name must be configured in Cisco IOS as a “user” with privilege 15.
b. In the Login password field, enter the user name that you use to log in to Cisco IOS.
c. Click the Browse button and follow the on-screen prompts to locate and select the file that you want.
The upload process begins. This process can take some time.
To ensure that the upload completes successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the upload is in process.
Starting the Cisco Data in Motion service makes the service available to apps that require it.
You must upload the license before the service becomes fully functional. See the “Uploading a Cisco Data in Motion License” section.
To start the Cisco Data in Motion service, follow these steps:
Step 1 Choose Middleware Service from the Cisco IOx Local Manager menu bar.
The Middleware Service page displays.
Step 2 On the Middleware Service page, click start in the Actions field for the service that you want to start.
The starting process executes. This process can take some time. A progress bar indicates the status of the starting process.
To ensure that the middleware starts successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the service is starting.
Stopping the Cisco Data in Motion service makes the service unavailable on the host system.
To stop the Cisco Data in Motion service, follow these steps:
Step 1 Choose Middleware Service from the Cisco IOx Local Manager menu bar.
The Middleware Service page displays.
Step 2 On the Middleware Service page, click stop in the Actions field for the service that you want to stop.
The stopping process executes. This process can take some time. A progress bar indicates the status of the stopping process.
To ensure that the middleware stops successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the service is stopping.
Internal network management workflows include the operations that you use to add, view information about, edit information for, or delete a Cisco IOx internal network. These networks allow apps on host systems to communicate with other systems.
The workflows for adding and deleting an internal network can be performed only for host systems that allow internal networks to be added.
The following sections describe the internal network management workflows:
Adding an internal network lets you add a Cisco IOx internal network for an app that requires the network for external connectivity. This operation is available only on host systems that allow internal networks to be added.
If needed, refer to the app documentation or developer for information network configuration that an app requires when it runs.
To add an internal network, perform the following steps.
Step 1 Choose System Setting from the Cisco IOx Local Manager menu bar.
The System Setting page displays.
Step 2 Click the Add Network button in the System Logs area on the System Setting page.
The Add Network dialog box displays.
If you do not see the Add button, click Additional Networks to expand this area.
Step 3 In the Add Network dialog box, take these actions:
a. In the Network Description field, enter a brief description of the internal network.
b. From the Physical Interface drop-down list, choose the physical interface that the internal network should use for connectivity.
The options that are available depend on your host system platform. See your host system documentation for information about these options.
c. In the Vlan ID field, enter the identifier of the VLAN on which this internal network operates, if applicable.
d. Check the Nat Enabled check box if you want to enable NAT networking mode on this network, otherwise skip to Step 3 h .
If you check Nat Enabled , the Nat Subnet fields and Bridge IP radio buttons appear. The Nat Subnet fields include a system-provided address range for the NAT subnet.
e. If you want to change the system-provided address range for the NAT subnet, in the Nat Subnet fields, enter the range that you want.
The system does not allow you to define an address range that includes addresses that are in use by another internal NAT network that is configured on the host system.
f. Click one of these Bridge IP radio buttons:
– Static —Click to configure a static IP address for the Cisco IOx bridge. The IP Address / Mask , Gateway IP , DNS , and Domain fields appear.
– DHCP —Click to cause the Cisco IOx bridge to obtain its IP address from an available DCHP server. Skip to Step 3 h .
g. If you clicked the Static radio button for Bridge IP, take these actions:
– In the IP Address / Mask field, enter the IP address and subnet mask for the Cisco IOx bridge
– In the Gateway IP field, enter the IP address of the gateway server for the Cisco IOx bridge
– In the DNS field, enter the IP address of the DNS server for the Cisco IOx bridge
– In the Domain field, enter the domain for the static bridge IP address.
h. Check the Bridge Enabled check box if you want to enable bridge networking mode on this network.
You can view information about any internal network that is configured in Cisco IOx Local Manager.
To view information about an internal network, follow these steps:
Step 1 Choose System Setting from the Cisco IOx Local Manager menu bar.
The System Setting page displays.
Step 2 In the Additional Networks area on the System Setting page, click view in the Actions field for the network about which you want to view information.
The Additional Information window displays, which provide detailed information about the internal network.
You can edit the description of any internal network that is configured in Cisco IOx Local Manager. You also can edit the address range for the NAT subnet, if NAT is enabled for the internal network.
To edit information for an internal network, follow these steps:
Step 1 Choose System Setting from the Cisco IOx Local Manager menu bar.
The System Setting page displays.
Step 2 In the Additional Networks area on the System Setting page, click edit in the Actions field for the network for which you want to edit information.
The Edit Network dialog box displays.
Step 3 In the Edit Network dialog box, take these actions as needed:
a. In the Network Description field, update the description of the internal network.
b. In the NAT Subnet field, update the address range for the NAT subnet.
The system does not allow you to define an address range that includes addresses that are in use by another internal network that is configured on the host system.
Step 4 In the Edit Network dialog box, click the OK button.
Information for the network is updated.
Deleting an internal network removes its configuration from the host system.
The internal network named svcbr_0 is provided by default. This network cannot be deleted because it provides minimum outside connectivity for Cisco IOx hosting.
In addition, an internal network cannot be deleted if an app that uses is it is in the ACTIVATED, RUNNING, or STOPPED state.
To delete an internal network, perform the following steps.
Step 1 Choose System Setting from the Cisco IOx Local Manager menu bar.
The System Setting page displays.
Step 2 In the Additional Networks area on the System Setting page, click delete in the Actions field for the network that you want to delete.
Step 3 In the dialog box that prompts you to confirm the deletion, click Yes .
The delete process executes. This process can take some time.
To ensure that the network deletes successfully, do not refresh your browser or attempt another Cisco IOx Local Manager operation while the network is deleting.
The app signature validation feature causes Cisco IOx Local Manager to validate each app that you add by comparing a certificate on the host system with a certificate in the app. This feature ensures that an app that you add meets the following criteria:
When you enable the app signature validation feature, you can only add apps that are signed. If you try to add an app that is not signed, the message “Application Deployment Failed” displays.
You can enable the app signature validation feature only on host systems that supports app signing. The Application Signature Validation configuration options do not appear on host systems that do not support app signing.
Configuring the app signature validation feature involves enabling the feature and uploading to the host system the trust anchor (certificate) that matches the certificate in the apps that you will add.
To configure app signature validation, follow these steps:
Step 1 Choose System Setting from the Cisco IOx Local Manager menu bar.
The System Setting page displays.
Step 2 In the Configuration area under the Application Signature Validation area, take these actions:
a. Check the Enabled check box next to “Application Signature Verification.”
b. Click the Save Configuration button.
Step 3 In the Trust Anchor area under the Application Signature Validation area, take these actions to upload the certificate to the host system:
a. Click the Import Trust Anchor button. The Import Trust Anchor dialog box appears.
b. In the Import Trust Anchor dialog box, click Choose File, and then navigate to and select the certificate file (a .tar or .tar.gz file) that you want to use.
c. In the Import Trust Anchor dialog box, click Choose File .
The certificate uploads to the host system and the Trust Anchor area displays the checksum value and metadata of the certificate. If this certificate is not the one that you want, you can upload another one, which replaces the one that is displayed.
The host system can capture information about a variety of operations and store this information in host system log files. You can configure the type and level of information that the system logs, and you can download and provide host log files to Cisco for troubleshooting, if needed.
The following sections describe the workflows that relate to host system log files:
Configuring host system log files lets you set the categories for which the host system logs information and the level at which it logs information.
To configure host system log files, perform the following steps. This procedure sets the same log level for each category that you choose. If you want to set different log levels for different categories, repeat this procedure as needed.
Step 1 Choose System Info from the Cisco IOx Local Manager menu bar.
The System Info page displays.
Step 2 Click the Logging Management button in the Logs area on the System Info page.
The Logging Management dialog box displays. This dialog box lists each category for which the system collects logging information, and shows the log level that is configured for each category. It also lets you configure options that relate to host system logs.
If you do not see the Logging Management button, click Logs to expand this area.
Step 3 In the Logging Management dialog box, take these actions:
a. Check the check box for each category for which you want the system to collect logging information. Categories include:
– API Services — REST API communication between the Cisco IOx host system and Cisco IOx Local Manager (or Cisco Fog Director)
– APP Management —App lifecycle management
– System Information —System health info for the host system
– Other —Other system components
You can click the check box in the title row of the table to quickly check boxes for all categories.
b. Take either of these actions:
– From the Log Level drop-down list, choose the level of logging messages that the system collects. Options, in order of least messages to most messages collected, are critical , error , warning , info , and debug .
– Click the Load Defaults button to set the log level for each category to the default value of info .
The host system starts collecting logging information.
You can download a host system log file from the host system to the location of your choice. You can then review the file or provide it to Cisco for assistance with troubleshooting, if needed.
To download a host system log file, follow these steps:
Step 1 Choose System Info from the Cisco IOx Local Manager menu bar.
The System Info page displays.
Step 2 In the Logs area on the System Info page, click download in the View field for the host system log file that you want to download.
If you do not see the download option, click Logs to expand this area.
Step 3 Follow the on-screen prompts to save the file in the location of your choice.
A snapshot file is a tar file that contains hardware and app file information that relates to the IOx framework. It includes information from log files and specific system health and debugging information that can be useful for troubleshooting complex issues. If you experience issues with Cisco IOx Local Manager, you can generate and then download a snapshot file, which you can provide to Cisco for assistance.
The following sections describe the workflows that relate to snapshot files:
Generating a snapshot files collects information in a tar file that is stored on the host system. You can generate a snapshot file whenever needed.
To generate a snapshot file, follow these steps:
Step 1 Choose System Info from the Cisco IOx Local Manager menu bar.
The System Info page displays.
Step 2 Click the Generate snapshot file button in the TechSupport Information area on the System Info page.
If you do not see Generate snapshot file button, click Logs to expand this area.
The snapshot file is generated and its name appears in the Tech Support snapshot file name field. The filename is tech_support_ timestamp , where timestamp is the host system date and time that the file was generated.
Downloading a snapshot file downloads it from the host system to the location of your choice.
To download a snapshot file, follow these steps:
Step 1 Choose System Info from the Cisco IOx Local Manager menu bar.
The System Info page displays.
Step 2 In the TechSupport Information area on the System Info page, click download in the Download field for the snapshot file that you want to download.
If you do not see the download option, click Logs to expand this area.
Step 3 Follow the on-screen prompts to save the file in the location of your choice.
Deleting a snapshot file removes it from the host system.You can delete any snapshot file when it is no longer needed.
To delete a snapshot file, follow these steps:
Step 1 Choose System Info from the Cisco IOx Local Manager menu bar.
The System Info page displays.
Step 2 In the TechSupport Information area on the System Info page, click the
Delete
icon
in the Delete field for the snapshot file that you want to delete.
If you do not see the Delete icon, click Logs to expand this area.
The host system can create a core dump file if a process crashes. A core dump file contains information that can be useful for troubleshooting.
The following sections describe the workflows that relate to core dump files:
Downloading a core dump file downloads it from the host system to the location of your choice.
To download a core dump file, follow these steps:
Step 1 Choose System Info from the Cisco IOx Local Manager menu bar.
The System Info page displays.
Step 2 In the TechSupport Information area on the System Info page, click download in the Download field for the core file that you want to download.
If you do not see the download option, click Logs to expand this area.
Step 3 Follow the on-screen prompts to save the file in the location of your choice.
Deleting a core dump file removes it from the host system.You can delete any core dump file when it is no longer needed.
To delete a core dump file, follow these steps:
Step 1 Choose System Info from the Cisco IOx Local Manager menu bar.
The System Info page displays.
Step 2 In the TechSupport Information area on the System Info page, click the
Delete
icon
in the Delete field for the core dump file that you want to delete.
If you do not see the Delete icon, click Logs to expand this area.