Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > NCM Device Template for F5 Big-IP (1.3.6.1.4.1.3375) device

NCM Device Template for F5 Big-IP (1.3.6.1.4.1.3375) device

Updated: October 30, 2018

Overview

This article provides an NCM Device Command Template to be used with F5 Big-IP (1.3.6.1.4.1.3375) devices.

Environment

  • NCM any version
  • Device: F5 Big-IP (1.3.6.1.4.1.3375)

Resolution

Solutions below provide device templates. For additional information on naming files, see Device Template file naming convention.

Solution 1 - Use tmsh shell

  1. Prerequisite: The user account that NCM uses to connect to the device must have tmsh set for terminal access:
    • Configure from the F5 GUI: Main > System > Users.
  2. Depending on your version of NCM, use the relevant steps to add the following template. For information on using device templates, see Creating and Modifying Device Templates in the NCM Administrator Guide.

  3. Use the following lines for the content of the template:
    <Configuration-Management Device="F5" SystemOID=" 1.3.6.1.4.1.3375">
            <Commands>
                    <Command Name="RESET" Value="modify cli preference pager disabled"/>
                    <Command Name="VirtualPrompt" Value="#"/>
                    <Command Name="PreCommand" Value="y"/>
                    <Command Name="Reboot" Value=""/>
                    <Command Name="EnterConfigMode" Value=""/>
                    <Command Name="ExitConfigMode" Value=""/>
                    <Command Name="DownloadConfig" Value="tmsh -q show running-config"/>
                    <Command Name="UploadConfig" Value=""/>
                    <Command Name="DownloadConfigIndirect" Value=""/>
                    <Command Name="UploadConfigIndirect" Value=""/>
                    <Command Name="EraseConfig" Value=""/>
                    <Command Name="SaveConfig" Value=""/>
                    <Command Name="Version" Value="tmsh -q show sys version"/>
            </Commands>
    </Configuration-Management>
    

The credentials set up in NCM to log into this device will need to be sufficient to issue the commands.
Root level is recommended if it is not required.

Solution 2 - Use Advanced Shell

  1. Prerequisite: The user account that NCM uses to connect to the device must have "Advanced shell" set for terminal access:
    • Configure from F5 GUI: Main > System > Users.
  2. Depending on your version of NCM, use the relevant steps to add the following template. For information on using device templates, see Creating and Modifying Device Templates in the NCM Administrator Guide.

  3. Use the following lines for the content of the template:
    <Configuration-Management Device="F5" SystemOID=" 1.3.6.1.4.1.3375">
            <Commands>
                    <Command Name="RESET" Value=""/>
                    <Command Name="Reboot" Value=""/>
                    <Command Name="EnterConfigMode" Value=""/>
                    <Command Name="ExitConfigMode" Value=""/>
                    <Command Name="Startup" Value=""/>
                    <Command Name="Running" Value=""/>
                    <Command Name="DownloadConfig" Value="tmsh -q show running-config"/>
                    <Command Name="SaveConfig" Value="tmsh save"/>
                    <Command Name="Version" Value="tmsh show sys version"/>
            </Commands>
    </Configuration-Management>
    

The credentials set up in NCM to log into this device will need to be sufficient to issue the commands.
Root level is recommended if it is not required.

NCM cannot store the desired UCS file in the database, but one may be able to use the Execute scripts feature in NCM to back it up.

 

 

 

Last modified

Tags

Classifications

Public