Use these lines to enable SCP server in IOS. To allow IOS to serve these files via TFTP we use the following line: The Option 43 sub-options 1 and 3 are concatenated into one string in the IOS config. The length portion of the TLV is the length of characters used to specify the value.Ġ109.7166.7831.2e63.6f6e.6603.0474.6674.70Ġ9 = length of 9 characters in the config file name (nf)ħ166.7831.2e63.6f6e.66 = hex representation of the word "nf" (Value)Ġ4 = length of 4 characters in transfer method (tftp)ħ4.6674.70 = hex representation of the word "tftp" (Value) In our case sub-option 1 sets the configuration file (Value) to nf and sub-option 3 sets the transfer mode (Value) to tftp. Sub-option 3 (Type) is used to define the transfer method. Sub-option 1 (Type) is used to define the name of the configuration file to be downloaded. We're specifying option 43 TLVs for sub-options 1 and 3. The option 43 line warrants more explanation. ! Specify the sub-options, the length and the value (TLV) ! Set a reservation based on the vQFX MAC address Here is the relevant config (my comments in bold): The vQFX config that was uploaded to the ZTP/TFTP server is shown at the bottom of this page. The first step is to configure the DHCP server and upload the vQFX configuration files that will be downloaded as part of the auto-image-upgrade process. Download and install configuration file.Obtain ZTP information from DHCP server via Option 43.It's just that it was difficult to figure out how configure the sub-options, and that concatenating them into a single line was the way to do it. The IOS configuration and hex conversions was really the trickiest part of this process. The Cisco IOS box will also be the ZTP/TFTP server. And sometimes, using a switch or router is more convenient, albeit more difficult, than finding a Windows server or something else to use. I became far better at using IOS as a DHCP server than I ever imagined. My decision to use a Cisco IOS device as a DHCP server was due to the extraordinary depth the CCIE Route/Switch lab exam covered this topic. We can use this feature on other Juniper platforms, including physical switches and routers, but here we'll focus on vQFX, a virtual QFX image running on EVE-ng in my case. This feature can be used to upgrade the version of code running on the device, but we'll use it simply to install a configuration file. We can do this by utilizing the ZTP feature on a vQFX called "chassis auto-image-upgrade".
Suppose we wanted to provision the configuration on a vQFX automatically, and deterministically assign an IP address to the management interface, to later use another automation tool to finish the device configuration.
0 kommentar(er)
