Network Management
NCM Template - F5 Big-IP (1.3.6.1.4.1.3375) variations with and without ciphers
The article provides the device template for F5 Big-IP platform to be used with NCM.
First published date
Last published date
Overview
Product section
Resolution
The solutions below provide device templates. Please follow the article below while naming files:
Naming conventions for Device Template files
Solution 1 - using tmsh shell
Prerequisite: The user account that NCM uses to connect to the device must have "tmsh" set for terminal access: Configure from F5 GUI: Main > System > Users.
-
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.
- Use the following lines as the actual content of the template:
01 <Configuration-Management Device="F5" SystemOID=" 1.3.6.1.4.1.3375"> 02 <Commands> 03 <Command Name="RESET" Value="modify cli preference pager disabled"/> 04 <Command Name="VirtualPrompt" Value="#"/> 05 <Command Name="PreCommand" Value="y"/> 06 <Command Name="Reboot" Value=""/> 07 <Command Name="EnterConfigMode" Value=""/> 08 <Command Name="ExitConfigMode" Value=""/> 09 <Command Name="DownloadConfig" Value="tmsh -q show running-config"/> 10 <Command Name="UploadConfig" Value=""/> 11 <Command Name="DownloadConfigIndirect" Value=""/> 12 <Command Name="UploadConfigIndirect" Value=""/> 13 <Command Name="EraseConfig" Value=""/> 14 <Command Name="SaveConfig" Value=""/> 15 <Command Name="Version" Value="tmsh -q show sys version"/> 16 </Commands> 17 </Configuration-Management>
***Note***
The credentials set up in NCM to log in to this device must be sufficient to issue the commands.
The root level is recommended if not required.
Solution 2 - using Advanced Shell
Prerequisite: The user account that NCM uses to connect to the device must have an "Advanced Shell" set for terminal access: Configure from F5 GUI: Main > System > Users.
-
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.
- Use the following lines as the actual content of the template:
01 <Configuration-Management Device="F5" SystemOID=" 1.3.6.1.4.1.3375"> 02 <Commands> 03 <Command Name="RESET" Value=""/> 04 <Command Name="Reboot" Value=""/> 05 <Command Name="EnterConfigMode" Value=""/> 06 <Command Name="ExitConfigMode" Value=""/> 07 <Command Name="Startup" Value=""/> 08 <Command Name="Running" Value=""/> 09 <Command Name="DownloadConfig" Value="tmsh -q show running-config"/> 10 <Command Name="SaveConfig" Value="tmsh save"/> 11 <Command Name="Version" Value="tmsh show sys version"/> 12 </Commands> 13 </Configuration-Management
***Note***
The credentials set up in NCM to log in to this device will need to be sufficient to issue the commands.
The root level is recommended if not required.
Solution 3:
Version 12 and later
Backing up the UCS as the Startup Config and the Config File as the Running config without ciphers:
<Commands>
<Command Name="RESET" Value="bash"/>
<Command Name="Reboot" Value=""/>
<Command Name="EnterConfigMode" Value=""/>
<Command Name="ExitConfigMode" Value=""/>
<Command Name="Startup" Value="tmsh save /sys ucs /var/local/scf/NCM.ucs${CRLF}${TransferProtocol} /var/local/scf/NCM.ucs ${SCPServerUserName}@${SCPStorageAddress}:${StorageFilename}${CRLF}${SCPServerPassword}" IsBinary="true"/>
<Command Name="Running" Value="tmsh save /sys config file /var/local/scf/Running.config no-passphrase${CRLF}${TransferProtocol} /var/local/scf/Running.config ${SCPServerUserName}@${SCPStorageAddress}:${StorageFilename}${CRLF}yes${SendConditionRegEx:areAre you sure}${CRLF}${SCPServerPassword}"/>
<Command Name="DownloadConfig" Value="tmsh -q show running-config"/>
<Command Name="UploadConfig" Value=""/>
<Command Name="DownloadConfigIndirect" Value=""/>
<Command Name="UploadConfigIndirect" Value=""/>
<Command Name="DownloadConfigIndirectSCP" Value="${ConfigType}"/>
<Command Name="UploadConfigIndirectSCP" Value="${TransferProtocol} ${SCPServerUserName}@${SCPStorageAddress}:${StorageFilename} /var/local/scf/NCM.ucs${CRLF}${SCPServerPassword}${CRLF}tmsh load /sys ucs /var/local/scf/NCM.ucs"/>
<Command Name="EraseConfig" Value=""/>
<Command Name="SaveConfig" Value=""/>
<Command Name="Version" Value="tmsh show /sys version"/>
<Command Name="Disconnect" Value=""/>
</Commands>
Solution 4:
Version 12 and later
Backing up the UCS as the Startup Config and the Config File as the Running config requiring a cipher:
<Commands>
<Command Name="RESET" Value="bash" RegEx="#" />
<Command Name="Reboot" Value="" />
<Command Name="EnterConfigMode" Value="" />
<Command Name="ExitConfigMode" Value="" />
<Command Name="Startup" Value="tmsh save /sys ucs /var/local/NCM.ucs${CRLF}${TransferProtocol} -c aes192-ctr /var/local/NCM.ucs ${SCPServerUserName}@${SCPStorageAddress}:${StorageFilename}${CRLF}yes${SendConditionRegEx:Are you sure}${CRLF}${SCPServerPassword}" IsBinary="true" />
<Command Name="Running" Value="tmsh save /sys config file /var/local/scf/Config_${Date}.config no-passphrase${CRLF} ${TransferProtocol} -c aes192-ctr /var/local/scf/Config_${Date}.config ${SCPServerUserName}@${SCPStorageAddress}:${StorageFilename}${CRLF}yes${SendConditionRegEx:Are you sure}${CRLF}${SCPServerPassword}" />
<Command Name="DownloadConfig" Value="tmsh -q show running-config" />
<Command Name="UploadConfig" Value="" />
<Command Name="DownloadConfigIndirect" Value="" />
<Command Name="UploadConfigIndirect" Value="" />
<Command Name="DownloadConfigIndirectSCP" Value="${ConfigType}" />
<Command Name="UploadConfigIndirectSCP" Value="${TransferProtocol} ${SCPServerUserName}@${SCPStorageAddress}:${StorageFilename} /var/local/scf/NCM.ucs${CRLF}${SCPServerPassword}${CRLF}tmsh load /sys ucs /var/local/scf/NCM.ucs" />
<Command Name="EraseConfig" Value="" />
<Command Name="SaveConfig" Value="" />
<Command Name="Version" Value="tmsh show /sys version" />
<Command Name="Disconnect" Value="" />
</Commands>