---
title: "Notes on TFTP Service for ACM Operation"
canonical: "https://docs.infoblox.com/space/NetMRI753/42077248/Notes%20on%20TFTP%20Service%20for%20ACM%20Operation"
format: markdown
---
A NIOS appliance can also operate as a TFTP server. The enterprise network may also have an existing public TFTP server. For more information on us> Macro (anchor)

ing a NIOS appliance as a TFTP server, see the *Infoblox* *NIOS* *Administrator* *Guide*, Chapter 8, *File* *Distribution* *Services*.

For initial bring-up of the bare-metal device, NetMRI's TFTP server directory contains a small Cisco or Juniper configuration file. The two files are called:

- `network_confg` (Cisco)
- `router.conf` (Juniper)

Other files may also be present. You can also create your own.

Each file contains the organization's assigned device IP address and assigned credentials for the Enable and Telnet/SSH passwords and secret settings. A sample network_confg file includes the basic credentials for the Enable password and for telnet and SSH access, and enables SNMP:

`username autoconfig privilege 15 password 0 autoconfig `

`snmp-server community autoconfig RO`

`line vty 0 4`

`exec-timeout 60 0 `

`logging synchronous `

`login local`

`transport input telnet ssh `

`end`

A sample Juniper file is in the topic <span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)</span>*<span style="color: #0000ff">[Sample](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)</span>*<span style="color: #0000ff">[Juniper](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)</span>*<span style="color: #0000ff">[router.conf](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)</span>*<span style="color: #0000ff">[File](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/42141742)</span>*.

If the administrator wants to deviate from the `autoconfig string` (i.e. for hostname, community string and/or CLI credentials), the following holds true:

- The defined hostname must remain `autoconfig`;
- You can change the community string, and you should update the global community string guesser list with the desired community string;
- You can change CLI credentials, and you should update the global CLI credentials guesser list with the desired CLI credentials (i.e. username, password and enable password);
- The stub configuration files must be updated to reflect desired changes, and if using NetMRI's TFTP server, redeployed using the admin shell **tftpsync** command.

You can edit the configuration files to contain your own credentials and settings. Access configuration files by using the NetMRI administrative shell and entering an **ls** **tftp** command. When finished, run the NetMRI **tftpsync** command to move these files into the public TFTP server file system.

> ⚠️ **Note**
> ⚠️ 
> ⚠️ NetMRI also runs a TFTP service by default and may be used for serving configuration files.