Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Configuration Manager (NCM) > NCM Documentation > NCM 7.8 Administrator Guide > Device templates > F5 device template behavior

F5 device template behavior

Created by Caroline Juszczak, last modified by Anthony.Rinaldi_ret on Oct 03, 2016

Views: 1,205 Votes: 0 Revisions: 4

When using device templates for F5 devices, consider the following behavior.

Device setup prerequisites

  • Set the Terminal Access user on the device to Advanced Shell. Do not use Traffic Management Shell (TMSH).
  • Verify the device can reach the NCM server for configuration transfers using SCP.
  • If you plan to upload binary user configuration set (UCS) files, the upload can take a long time. Increase the NCM timeouts to have a complete upload report.
    1. Click Settings > All Settings.
    2. Under Product Specific Settings, choose CLI settings.
    3. Set Telnet/SSH Connection Timeout: 360 seconds
    4. Telnet/SSH Prompt Timeout: 300 seconds

Template details

If you set up NCM to transfer configurations using SSH:

  • The template can download the current running config.
  • You cannot download the startup config.
  • You cannot upload the running or startup config

If you set up NCM to transfer configurations using SCP:

  • The template can download and upload a text single configuration file (SCF) as a running config.
  • The template can download and upload a binary UCS as startup config.
  • You cannot upload the running config to startup, or startup to running config.

    Downloading or uploading configs using TFTP is not supported.

 

Last modified

Tags

Classifications

Public