Frequently Asked Questions

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 previous one.
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.

It is possible to run mutiple configuration commands at once, but not support configuration that reboots devices in the middle of action.

We recommend that up to 10 SmartBridges connect to one netLD server.

Please check the section 7.1 Port Usage in NetLD Manual.

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.

Data Retention setting has the following options: Perpetual, 1-7 years, and 6 months.

Yes, you can download the document including the example of the structure of core server and SmartBridges from here.

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.

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.

According to specifications, there is no limit to keeping logs, but it depends on HDD capacity that NetLD is installed. Once log file (netld.log) reached 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.

Yes, netLD sends SNMP Traps to destination IP address in case of following occasions:
・Configuration is changed at device *1
・New device is added in the network.
・Device is deleted.
・Backing up configuration of device is failed.
・Compliance is violated.
*1: At the time of backup, if there is any difference between latest configuration and the last configuration, SNMP Trap will be sent.

The status of the job that has been run is reflected automatically.

Please check the following:
・SNMP of devices should be valid.
・SNMP community that has been set to devices should be same as the one that has been set to netLD credential.
・Ping/SNMP to devices should not be shut out by Firewall or antivirus software.
・Multiple network groups should not exist on “Network Groups” of credential/protocol. netLD has been revised to display the result of discovery and error. [Device added.] This is a state that the device has been successfully discovered and added to device inventory list. [There was no SNMP response.] This is a state that the device responded to Telnet, SSH or Ping, but not SNMP request. Please make sure that SNMP of device is vaild.
For setting method of SNMP of Cisco device, please refer to the following: https://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/7282-12.html [No adapter matches] This is a state that the device responded to SNMP request, but no adapters match to netLD. Please make sure that if netLD supports the device. Devices [Server protocol settings for SNMP for this device are disabled.] This is a state that SNMP protocol in “Inventory” -> “Protocols” is disabled for the network group. Please check protocol settings. [There was no ICMP ping response.] This is a state that the device did not respond to ICMP ping request. (This status is only available for discovering single IP address.) Please make sure that ping/SNMP to devices is not shut out by Firewall or antivirus software. [Unable to establish TCP connection on port 22(SSH) or 23(Telnet).] This is a state that netLD cannot connect to port 22(SSH) and 23(Telnet) of the device. (This status is only available for discovering single IP address.) Please make sure that if those ports are available.

Please make sure that trigger of the job has been set up. Setting method: Click [+] icon in the bottom of “Schedule” tab, set trigger name and contents, and Click “OK” button. Click floppy icon in the schedule window, and add it to “Trigger” column.

For update history of netLD, please refer to the link below: https://www.logicvein.com/update-history/

Switch with a stack configuration is registered as one device. As methods of distinguishing a stack by netLD, there are following ways: 1. Command Runner Check a stack information by running command such as “show switch”. 3750-Stk>show switch Current Switch# Role Mac Address Priority State ——————————————————– 1 Slave 0016.4748.dc80 5 Ready *2 Master 0016.9d59.db00 1 Ready 2. Hardware Report If there are main switch, member switch 1, and member switch 2, report is displayed as following: 10.0.0.1 -C3750 -Switch ————————– Type　 Slot＃　 Slot Type　 　…　　Description Chassis Card　　　1　　 stack Card　　　2　 　 stack ————————–

In the case of managing hundreds devices throughout a year, the capacity will be about 100MB, which is fairly small. *It would vary depending on frequency of use jobs, complexity of network like VLAN and heavy configuration.

Cron is a scheduler of job execution that is similar to Cron/Crontab of Unix. For description method of Cron, please refer to Net LineDancer Manual.

No, it is not possible to connect multiple servers to one SmartBridge. Connection as “Server : SmartBridge = 1 : n” is only available.

No. For features except backup, available feature is different depending on each device adapter. For supported feature of each adapter, please refer to the list of “Supported Devices and Features” below: Matrix

If devices have been registered more than the number of devices the license permits, “Backup” menu will be grayed out. Please reduce the number of devices.

It will be solved by backing up to devices.
netLD caches credentials and protocols that have been used to backup, and pushes commands with tools such as “Command Runner” or configuration change to device by using those cached. Therefore, the above error will happen when configuration change is performed in the status of cache deleted.
Also, the cache is to be renewed when credentials and protocols are changed. If credential or protocol is changed, please backup configuration of devices without fail.

When password of device has been changed, credentials also need to be changed according to new passwords of device.

If some files couln’t be deleted because of in use during uninstall, those will be deleted when Windows is rebooted.
Therefore, when you reinstall netLD, please follow below steps:
1. Uninstall netLD.
2. Reboot Windows.
3. Install netLD.

Due to mail server settings, sending email with account that is not registered in the server may be unavailable.
Please make sure SMTP server settings for sending email.
1. Click “Settings” in the right of screen.
2. Click “Mail Server” on the left menu, and enter each section.
・Mail server hostname or IP address
・From email address
・From name
・Server requires authentication
・Mail server username
・Mail server password
3. Click “OK”.

Since “ARP Table” and “MAC Table” get SNMP information of device, please make sure if the set communities are the same between SNMP setting of device and credential of netLD. *In netLD, when netLD discovers or collects neighbor information (click binoculars icon), information collected or updated is shown.

“Live ARP Table”, “Interface Brief”, and “IP Routing Table” get SNMP information of device. Therefore, set SNMP of device, and make sure if the set communities are the same between community of device and credential of netLD.

Authenticating by serial number, internet connection is necessary. In the case of internet connection is limited, online authentication may not be unavailable. If the problem cannot be solved, we will issue license file for local authentication, so please contact support@logicvein.com. MAC of server is necessary to issue license file. (In the case of multipler NICs, please send one of NICs that are connecting with cable.)

Please make sure that other Web server such as IIS or Apache is not working on netLD server.

If running job is falied, you can check the detail of error by double-clicking status icon. In the case of the job that detail of result is shown, since the result of command between netLD and device will be shown, it is possible to check contents.

There is a possibility that configuration of device is not backed up. Please make sure that configuration backup is completed correctly before running job.

For IOS Software Distribution feature, only firm update of Cisco device was by default available. Firmware update of NEC WA is now available from menu “NEC WA Software Distribution”. For other devices, it is possible to update firmware by using Command Runner with job feature and creating job for firmware update.

Yes, netLD has a feature to restore startup-config at any generations that have been backed up previously.

No, since netLD just tries to insert registered commands to devices, netLD operations don’t include validating the configuration already inserted into the device.

No, it is not possible to run operations of more than two jobs sequentially after a result analysis. it is necessary to run those jobs one by one manually with current version.

Yes, all jobs are to be implemented due to a schedule. it is possible to run job that was created at fixed intervals.

No, theoretically there is no limit of the number to be added in the job.

Yes, netLD basically supports it by using Command Runner feature. *netLD may not always support interactive commands for some devices.

Yes, in addition, it is possible to use them without remembering different command and grammars. For example, about “Backup” menu, the command is different by each vendor, but it is possible to run backup without remembering those commands in the case of netLD.

It is possible to save configuration information as much as possible.
[Setting procedure]
1. Select “Settings” in the right of screen.
2. Select “Data Retention” from left menu.
3. Set “Duration to keep configuration history” to “Forever”.

netLD collects return values of commands like “show version”, “show module”, and “show tech”, what are called in Cisco device as H/W inventory information.

By selecting “Inventory” -> “Add new device”, or by importing CSV file, it is possible to register nodes manually.

For example, In the case of the environment that managed nodes are about 1,000, and backup configuration automatically once a week, not backing up configuration of 1,000 nodes all at once, but creating 10 jobs that run backup of 100 nodes, and stagger running schedule not to oppress bandwidth. Then it will be ok.

Basically, netLD runs various processes by CLI base.
By the way, netLD collects configurations with TFTP, or issues “show startup-config” and “show-running” commands what are called in Cisco device to nodes, and then saves return values as configuration information by copy and paste.

Required conditions to run discovery are the following:
・netLD should be able to reach managed device and IP address.
・SNMP setting at node side should be valid.
・Nodes should be able to receive Telnet or SSH protocol.

It is possible to register nodes by following either way:
・Run polling into LAN by IP address base, and register devices that have responded (= auto discovery).
・Enter IP address directly.
・Import CSV file.

Please create a format with CSV that is included IP address and adapter ID. You can save inventory export Excel template from “Inventory” in the right of the screen.

Yes, it is possible to add up to 5 custom device fields from ver.11.04.
For added fields, it is possible to set viewing restriction to login user.
[Setting procedure]
1. Select “Settings” -> “Custom Device Fields”, and enter names for each custom fields.
2. Select “Settings” -> “Users” -> “Add Users”, and select custom field that user can view.

Using “advanced search” -> “Changed: Within range”, it is possible to search devices by specifying the date of configuration backed up.
Also, it is possible to check it by making a “Configuration Changes” report from “Reports” in the right of the screen.

Yes, by making network group and making devices grouping, viewing restriction of devices is available in a network group unit.
[Setting procedure]
1. Select “Settings” -> “Networks”, and add network.
2. Select added network from “Network” in the right of the screen.
3. Add device to network.
4. Select “Settings” -> “Users” -> “Add User” -> “Networks”, and select network that user can view.

To send Trap from netLD, it is necessary to compile private MIB at NMS side. You can donwload MIB to compile from the following: https://www.logicvein.com/wp-content/uploads/2020/12/mib.zip

Yes, if new configuration is compared with last cofiguration and there is any difference additionally found, it is possible to send SNMP trap.
[Conditions of sending SNMP trap]
1. When configuration of device is changed (when difference is detected.)
2. When new device is added to inventory.
3. When device is deleted from inventory.
4. When netLD backup job is failed, trap will be contained hostname, IP address, configuration file name of device.

Yes, it is possible to change timeout of console screen by following steps.
1. Select “Settings”.
2. Select “Network Server” and change “User login idle timeout (minutes)”.
3. Push “OK” button.
* As for invalid timeout, set “525,600(maximum)”. It is unnecessary to reboot netLD server.

If credentials of managed devices are same, it is possible to use dynamic credential to apply same credential to managed devices by specifying IP address range.
Also, if static credential already has a list of devices or so, it is useful to associate one device with the other credential one by one.
[Example of dynamic credential setting]
In the case of setting credential to following devices:
・192.168.0.1, 192.168.2, 192.168.0.3(same credential like user and password all for three)
・10.0.0.1(different credential from others)
1. In “Credential” screen, add “Network Group” as any name.
2. Enter “192.168.0.1 – 192.168.0.3” to address specification column on the right, and add it.
3. Enter information like user and password of devices.
4. For 10.0.0.1, follow same steps above 1-3, and add credential.

Yes, it is possible to select target devices by Ctrl or Shift key in Device view, and then select tool from “Change” in the right of Device view and run it.
If you are unable to make changes to multiple devices all at once, the tool will be grayed out.

Yes, it is possible to import devices from CSV file.
Also, it is possoble to add devices that have responded by discovery in specifying IP address range.

Basic feature of netLD is available by following steps.
1. Credential setting -> Enter information like password, user SNMP community of managed devices as credential.
2. Protocol setting -> Select protocol that is used to backup configuration of managed devices.
3. Add managed devices -> Add devices by manually or discovery with specifying IP address range.
4. Backup configuration -> Backup configuration of device. After processing above steps, it is possible to use Tool feature or Report feature or so. Please refer to the chapter 1.5, Initial Configuration in Net LineDancer Manual.

The tag feature is to manage devices classified by groups with tags. In Device view, it is possible to display only devices you want to manage or apply jobs to target devices in a group unit.
[Procedures of adding Tag]
1. Click “Inventory” -> “Device Tags” in the right of device view.
2. Add new tags and click “OK” button.
3. Select devices and click “Device” -> “Associate tags” in the right of device view.
4. Select tags from a list of tag to apply.

Yes, it is possible to get log of command that is run to devices by following procedures.
1. Click “Help” -> “About” -> “Adapter Logging”.
2. Enter target IP address.
ex) IP/CIDR: 172.20.0.0/16 -> Click “Enable recording of adapter operations”.
* Effective time of debug is 5 minutes.
(Save location \Net LineDancer\scratch\logs)
3. Run process to target device.

If SmartBridge is installed to netLD server by accident, existing data will be deleted, so please make sure that data is backed up, and then install it after checking program.
Utilizing the Virutal Appliance concept, this should not be possible.

There are two ways to upgrade netLD.
[In the case of using version before ver.10.10 or online connection is unavailable from server]
Stop the service of existing netLD and install new version over existing netLD.
For more details of procedures, please refer to “Upgrade Manual” that is distributed when you download upgrade version.
[In the case of using version later than ver.11.04 and online connection is available]
Run “Software Update” from netLD console, and upgrade it.
1. Select “Settings” on the right of screen.
2. Select “Software Update”on the left menu.
3. Click “Install Update”.
4. Update will be started. After that, service will be rebooted.
5. After completing update, the screen will automatically change to login screen.

Depending on the number of managed nodes, the required resources will be changed.
Please refer to the following:
System
[Precaution of installation]
Please make sure that other software will not use the same ports, which netLD will be deployed before installation.

No, netLD doesn’t support variable of multiple lines.
However, it is possible to correspond by making configurations algebraic value every one line.
[Procedures]
1. Make template of following style.
————————— conf t
Substitute(1)ACL1-1
Substitute(2)ACL1-2
Substitute(3)ACL1-3
Substitute(4)ACL2-1
Substitute(5)ACL2-2
exit
write mem
exit
————————— 2. Export template (xls).
please refer to the following:
3. Enter algebraic value to template.
Enter algebraic value to xls template.
4. Import
Import template.
please refer to the following:
*It is necessary to make template to each vendor.

It is not necessary to consider a leap year affecting netLD.
However, in the case of using Cron feature and Monthly in schedule feature, when you specified 29th as the end of February of leap year, and if the year is not leap year, it will be recognized as March 1st and schedule may not work correctly.

New feature called “Custom Device Fields” is added from Ver.11.04.
In Custom Device Fields, it is possible to add maximum 5 columns that can be named specifically.
Also, it is possible to give viewing restriction to each column.

Since the advent of the Virtual Appliance, netLD is now its own appliance and can only run on VMWare, HyperV, AWS, Azure or other cloud applications.

Yes. Also, it is possible to give permissions and viewing restrictions to each user.

No, netLD doesn’t have limits to the capacity except for physical HDD limit.

Once server is completely unavailable for some reason, replace it with new server and contact support@logicvein.com, then we will reissue license. The request should come with a reason for reissue.

There are two types of license form.
[Online authentication license]
When netLD is installed, enter the license key and authenticate it online.
[File authentication license]
We issue license file that is tied up with MAC address information of netLD server.
Apply license file to netLD server and authenticate it off-line

It requires both professional language skill and network knowledge. If you want to manage the devices that are not in our adapter list, please contact support@logicvein.com for details.

If the server that netLD is installed has enough resources, it is possible to manage about 40,000 nodes as a standalone server.
Also, by using/adding SmartBridges it is possible to manage maximum 200,000 nodes with one core server, and each SmartBridge handling 30,000 nodes each.
Also, please refer to system requirements of netLD.

Yes, because of updating OS of devices, and if the commands that have been changed, the feature of netLD will be unavailable. In the case of the contract of support is valid, we will support at no charge in principle.

Yes, via the system backup.

Yes, netLD can work on VMware, HyperV, AWS, Azure and other cloud applications. For more details, please contact support@logicvein.com

Yes, it is available. For details of setting or so, please contact support@logicvein.com

No, it is not possible. We do offer Webex support. For more details, please contact support@logicvein.com

The support covers the following:
・Q&A by email or phone regardless of presale or aftersales.
・Fixing bugs
・Free provision of new version installer
・Fixing adapters of OS that are supported
*Some adapters need to be updated in line with the netLD version up.

No. As NetLD is a virtual applicance, it is self contained and does not allow for other third party applications.

Yes, it is possible by buying an additional license. For more details, please contact sales@logicvein.com.

For bandwidth and processing time of OS image retrieval, please refer to the following:
netLD server: Windows 7
Core2 Duo CPU T7250 @ 2.00GHz 1.99GHz
2GB RAM
Router:
C2801
12.4(15)T12
Line Speed:
100Mbps
■IOS image retrieval
・Processing time -> 124 seconds (file size: 22,629KB)
・Bandwidth usage -> 2Mbps (average)
*Processing time may vary due to OS image size, response speed, server spec, and line speed.

With Virtual Appliance, a second server can be setup for a redundant system, but would be separate from the original server.
Best option is to schedule a snapshot of the VA on a regular basis, which allows for a fast re-install.

Primarily the more nodes you will manage, the more powerful the server should be.
Please check the link below:
System
If you let us know how many nodes will be managed, we will answer promptly.

We are releasing a list of devices that netLD supports. Please check the link below:
Matrix
For devices that are not supproted, it may be necessary to develop adaptor, Generally speaking, it is possible to support devices that have CLI.
For more details, please contact support@logicvein.com.

netLD mainly supports managed router, L2, L3 switch, firewall, and wireless AP.
Please check the link below:
Matrix
Also, we are able to develop adapters on-demand when device is not supported.
*Note: There may be a device that cannot be supported.
For more details, please contact support@logicvein.com.

You can check system requirement of netLD from the link below: System

Yes, netLD supports IPv6 in all versions.

For bandwidth and processing time of configuration back up, please refer to the following:
netLD server:
Windows 7
Core2 Duo CPU T7250 @ 2.00GHz 1.99GHz
2GB RAM
Router:
C2801
12.4(15)T12
Line Speed:
100Mbps
■Bandwidth and processing time of configuration back up
・Processing time -> 5 seconds
・Bandwidth usage -> 350Kbps (maximum)
*Processing time may vary due to configuration size, response speed, server spec, and line speed.

MIB files are stored in netLD server directly “/osgi-config/network”.

Yes, netLD supports OS software distribution feature to Cisco IOS and NEC WA.
OS software distribution is supported in Cisco IOS and NEC WA only.
it is possible to distribute OS software by using “Command Runner”.

Yes, netLD implements tool menu of commands that is commonly used.
In the case of using tool menu, it is possible to change configurations of multi-vendor devices all at once.

Yes, you can change processing nodes. contact support@logicvein.com for more information.

netLD supports this feature. Active Directory authentication is supported. Login authentication can be correlated by just specifying the authentication server.

No, netLD does’nt encrypt data of managed nodes.
In the case of data encryotion is necessary, please use EFS feature of Windows OS.

Yes, it is possible to run 10 registered jobs at the same time. Also, In the case of more than 10 jobs, netLD runs 10 jobs in registered order, and if one of them has been completed, the 11th one will be added and processed.

No, netLD does not understand either grammar of commands or the correctness.

Yes, you can check a list of nodes that has been running the jobs, and the commands sent and the acknowledgements between server and devices.

Line speed that is faster than 128K is required. However, in the case of managing with 128K, task of backing up configuration may be delayed.

Configurations that have been backed up previously are saved as history and can be referred or compared with other configuration later. You can set the duration to keep configuration history by “Settings” -> “Data Retention” on the right of screen.

For discovery, ICMP and SNMP are used.
For backup and change, SNMP, SSH, TELNET, and TFTP or so are used.
Depending on devices, netLD choose necessary protocols below:
・SSH
・TELNET
・HTTPS
・HTTP
・SCP
・FTP
・TFTP
・SNMP
*SSH or TELNET is required.

netLD uses Posgres in redundant configuration.

Yes, when you access netLD remotely by browser, https is used between server and clients.

Yes, you can export inventory as CSV by “Inventory” -> “Export inventory as Excel file” on the right of “Devices” screen.

Yes, you can check it by “Jobs” Tab -> “Job History”.
You can check the following contents by “Job History”:
・Name of job (both automatic and manual)
・Start time
・End time
・User
・Result of running Tool and Report job (double-click job)
・Result of running via Terminal Proxy

There are no difference about except for its validity.
However, evaluation version has following limits:
available nodes: 100 nodes
expiration date of license: 30 days
[In the case of online authentication]
30 days since the date installed
[In the case of off-line authentication]
30 days since the date of license file that was created

Yes, you can check the license expiration date by referring to “Help” -> “About” on the right of screen. Also, netLD warns you by popup banner (1min) within 90 days from expiration.

Yes, netLD can combine mix and matched permissions and set them to user account.

netLD is a virtual appliance, and can be setup on the following
* VMWare
* Windows HyperV
* AWS
*Azure
other cloud applications also
For more detail, please contact support@logicvein.com.

If a user wishes to convert an evaluation into a full version, they need a new/updated license.enc file provided by LogicVein.
The license.enc file is copied into the osgi-config/security directory and the service restarted.
That’s it, it should be activated with a new license at that point.

Here is an example of creating a custom Smart Change to enable Netflow on router interfaces.
1. Go to the Job Management tab
2. Select “New Job” -> Smart Change
3. Enter a Job name and click Ok.
4. In the job editor, paste in some Netflow boilerplate commands.
5. Now let’s parameterize some of the contents to create a tool. Highlight a fragment to create a replacement, then click on the + button…
6. Create a “Choice” of interfaces for the user to select from…
7. Use the same value for both the “interface” command and the “flow-export source” by highlighting the target, and then dragging and dropping from the list of replacements.
8. Save the job and close the editor.
9. On the Devices tab, select a device(s), and from the Smart Change menu choose your new tool.
10. Fill in your desired data and execute.
It’s that simple.
There are of course many other features of Smart Change, such as exporting an Excel spreadsheet where many devices and values can be populated and then imported to execute a mass change, etc.

Regarding bulk configuration changes and IOS distribution, there is no limit to the number of devices in a single batch.

We always recommend being on the latest versions of both the browser and flash. But these are our minimum client requirements:
Adobe Flash Player:
Flash version 13 and up.
Browsers:
Internet Explorer: version 8 and up.
Chrome: version 38 and up.
Firefox: version 31 and up.
Java is not required.
We don’t have specific support requirements for the client operating systems, but in general we don’t support operating systems that are themselves no longer supported (eg: since Microsoft no longer supports Windows XP, we also don’t support XP).

netLD supports Change Adviser for the following devices:
Apresia
Alaxala
Foundry FastIron
Cisco IOS
Fujitsu Ipcom
NEC IX
Cisco SecurityAppliance (ASA)
Fujitsu SRS
H3C Switch
NEC WA
AlliedTelesis XSeries

Here is a basic overview of the backup procedure…
Initiate CLI connection to device
Run commands
Possibly send configurations over FTP or TFTP back to netLD
Close connection to device
Save hardware and software information to database
Compare configurations and save to database if there is a changev
And here are a little more details for each of the steps…
netLD initiates a backup using the configured protocols and credentials. If the connection with the protocols or credentials fails, it will retry with the next configured combination of credentials and protocols until it can successfully log in to the device. netLD will remember the last successful combination of credentials and protocols for the next time a backup operation is performed against the device.
netLD executes a set of commands against the device in order to collect various hardware and software information from the device. It will also run commands to collect the configuration itself.
Depending on device support this might all be over the CLI (SSH or Telnet) but in some cases netLD will issue a TFTP or FTP command to send the configuration back to the netLD server.
The connection to the device is closed.
The parsed hardware and software information from the device is updated in the netLD database.
netLD will perform a configuration comparison of the collected configurations against the previous backup’s configurations. If there is a change the configuration files are saved into the netLD database. (The configurations are saved using a “reverse delta” model, so only the changes themselves are saved rather than the entire configuration.) If you are running a smart bridge there is an additional step after the communication with the device where the SmartBridge will check it’s saved CRC hash of the configuration to see if there is a change or not. If the CRC hash of the configurations are unchanged then it will tell the main server that there are no changed. This allows the system to save on bandwidth communicating between the smart bridge and main server in the common case of there being no changes.

SSL is used between SmartBridge and netLD.

This error message only appears with Tera Term version 4.87. Downgrading Tera Term to a lower version, this message will never appear.

The draft configuration feature can be used to push the config you directly edited on the devices.

Use the memo template feature. This memo is also available for the configuration or draft configuration, which are also added on this version. For each type of memo (devices, configuration, draft configuration), one template can be created.

Yes, you can attach memos to the devices in the inventory, you can also attach it for the config and draft config.

Change Advisor was added to Net LineDancer v13.08, which can generate commands automatically and push them on the devices.

A121. It is the result of the diff output in the unified format: @@ -“the number of the lines of old file”+”the number of the lines of new file” @@ “@@ -101,6 +101,7 @@” means “the difference between the line 101 through 107 of old file and the line 101 through 108 of new file.”

■Case 1: Failed to import static credentials from an Excel sheet. Please check the following. 1. Is there any space or an irregular character in the “IP Address” column? 2. Is there any double-byte character in IP addresses? 3. Is there two identical IP addresses in the sheet? In the above cases, only those lines containing such errors are not imported. (Other lines are imported.)
■Case 2: Failed to import inventory from an Excel sheet with an error. Please confirm the IP addresses in the imported file. If there are any two identical IP addresses, you cannot import the inventory.
■Case 3: There are some lines that are not imported from an Excel sheet. Please check the following. 1. Is there any space or an irregular character in the “IP Address” column? 2. Is there any double-byte characters in IP addresses? In the above cases, only those lines containing such errors are not imported. (Other lines are imported.)

Yes, Net LineDancer for Linux supports NIC teaming.