Q001. What is the difference between Tera Term and netLD?
A001. Main difference between netLD and Tera Term.
1. netLD manage configurations of all devices on DB all at once.
Therefore, it is possible to avoid inconsistency of device management due to forgetting to
report configuration of having been changed.
In Tera Term, only administrator knows the contents of device change by himself.
On the other hand, it is possible for netLD to share history of changes among multiple users.
2. In netLD, it is possible to make report of configuration generation management,
comparison, and change history.
Therefore, it is possible to make trouble-shooting by configuration comparison with
3. In netLD, it is possible to make multiple changes to managed devices all at once.
In Tera Term, it is necessary to create macro/script to make changes to multiple
devices at once.
Compare to Tera Term macro, configuration time is saved 89% to make accesslist
configuration change to 28 Cisco devices.
This is the data provided by NTT Data SMS.
Q002. In Command Runner, is it possible to run command causing rebooting devices in the middle of action?
A002. It is possible to run mutiple configuration commands at once,
but not to support configuration that reboots devices in the middle of action.
Q004. Which ports does netLD use?
Aoo4. Check the section 7.1 Port Usage in NetLD Manual.
Q005. What are the requirements for Plug and Play (Zero-Touch)?
Q005. A5.There are following conditions to apply Plug and Play (formerly Zero-Touch): ・IOS: After ver.15.2(2) (for Zero-Touch, ver.12.3) released, CNS AutoInstall is implemented. *1 ・startup-config: There should be no "startup-config" that is valid to devices. *2 ・DHCP Server *3: In the case of using netLD DHCP server feature, it should be possible to distribute IP addresses via DHCP to target devices. *1 Implemented features of IOS can be checked from the link below: http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp *2 When placing an order, choose the option in which default configuration is not installed on nvram. If you delete configuration manually, use commands such as "write erase", "erase startup-config", or "erase nvram" and the size of configuration on nvram must be zero. *3 If you don't want to use netLD DHCP feature, you can use an external DHCP Server (DHCP Option 150). If there is no router supporting Zero-Touch in the same broadcast domain in which netLD installed, configure a staging router as a DHCP relay that transfers DHCP requests to netLD.
Q006. How many generation configurations can netLD save?
A006.Data Retention setting has the following options: Perpetual, 1-7 years, and 6 months.
Q007. Is there documentation for core server and SmartBridges about traffic and process?
A7. Yes, you can download the document including the example of the structure of core server and SmartBridges from here.
Q009. Is it possible to import managed devices all at once.
A009. It is possible to import managed devices all at once with CSV files. Import procedures: 1. Select "Save inventory import Excel template" from Inventory tab on the right, and save it. 2. Open the file saved, input or select IP address, Network, and Adaptor, save it. 3. Select "Import/update inventory from Excel file" from Inventory tab, import Excel file that is saved in step 2.
Q010. Why is a different IP address registered from the IP address that was specified by discovery?
A010. When netLD discovers the device that has multiple IP addresses, netLD chooses administrative IP address and registers it to avoid registering duplicate IP addresses of same device. Therefore, the IP address that is not specified by discovery can be registered. If such IP address that is registered, register it by going to "Add new device". When netLD discovers devices, administrative IP address is selected by following processes: 1. Run "show interface" command when netLD discovers. 2. Run "ping" in order of interfaces that is shown. 3. Pick the IP address that responds first as adminisrative IP address. Ping execution is operated by following processes: 1. Ping to softwareLoopback interface at first. 2. If there is no response from softwareLoopback, ping to physical interface that is not loopback. 3. Do not ping to interface that is down.
Q011. How long does netLD keeps logs?
A011. According to specifications, there is no limit to how long logs are kept, but it depends on HDD capacity that netLD is installed. Once log file (netld.log) reaches 2048KB that is fixed as maximum size, backup file is produced as following: netld.log <- current netld.log.1 <- latest netld.log.2 <- second from latest netld.log.3 <- oldest Also, it is possible to change the maximum size of log and the frequency of backup. [Configuration procedures of file size] 1. Open "Net LineDancerosgi-configlog4jlog4j.properties" by text editor. 2. Edit following lines: log4j.appender.SERVER.MaxFileSize=2048KB -> maximum size log4j.appender.SERVER.MaxBackupIndex=3 -> frequency of backup 3. Reboot netLD service. ->Use command prompt stop service command: net stop netld start service command: net start netld ->Use control panel Select "Net LineDancer" from service to reboot.