Huawei tftp error failed to run this command because incorrect packet was received

Windows-терминалы WTware

Программа-клиент службы терминалов Windows Terminal Services, для бездисковых терминалов и загрузки по сети. Основной сайт http://www.wtware.ru

Ошибка TFTP

Ошибка TFTP

Сообщение Tpyna4ek » Ср апр 14, 2010 10:36 am

Re: Ошибка TFTP

Сообщение aka » Ср апр 14, 2010 11:32 am

Мало «решить его удалить». Надо его действительно удалить. Пуск — панель управления — администрирование — службы — упрощенный ftp.

Для проверки можно попробовать tftpd32. Если оно тоже скажет, что порт tftp занят — значит порт действительно занят.

Re: Ошибка TFTP

Сообщение Tpyna4ek » Ср апр 14, 2010 12:11 pm

Re: Ошибка TFTP

Сообщение aka » Ср апр 14, 2010 9:04 pm

Re: Ошибка TFTP

Сообщение 978143 » Вт ноя 16, 2010 6:15 am

Wtware 4.9.14
очень долго грузится терминал и потом появляется такое сообщение i`m tired (хотя вроде разобрался с сообщением)
а вот с торможением непонятки, лог прилагаю.

сам клиент на virtual box тестируется

смущает вот это:
[192.168.1.254] Requests file «4.9.14packageskernel». Tsize is requested, blksize 1240 bytes.
[192.168.1.254] Sending OASK (tsize 1554816, blksize 1240).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).

Re: Ошибка TFTP

Сообщение aka » Вт ноя 16, 2010 6:50 am

Если оно доходит до «i`m tired», значит все, что оно хотело, оно загрузило.

Чуть выше, чем смущающий текст, есть кнопка «вести лог». Нажми ее

Re: Ошибка TFTP

Сообщение 978143 » Вт ноя 16, 2010 7:30 am

Источник

Windows-терминалы WTware

Программа-клиент службы терминалов Windows Terminal Services, для бездисковых терминалов и загрузки по сети. Основной сайт http://www.wtware.ru

Проблема с загрузкой TFTP

Проблема с загрузкой TFTP

Сообщение crazyfa » Ср окт 16, 2019 11:53 am

Re: Проблема с загрузкой TFTP

Сообщение aka » Ср окт 16, 2019 12:35 pm

Re: Проблема с загрузкой TFTP

Сообщение crazyfa » Ср окт 16, 2019 1:13 pm

Re: Проблема с загрузкой TFTP

Сообщение AlexPetrov » Чт дек 19, 2019 12:48 pm

Периодически всплывает проблема с загрузкой по сети WTware на Raspberry Pi 3 B+. Помогает только многократная перезагрузка Raspberry Pi.
В логах проблема выглядит так:
10-54-11-546| [192.168.10.110] «0ca90504fixup.dat»: tsize is requested, blksize default.
10-54-11-546| [192.168.10.110] «0ca90504fixup.dat»: «C:Program Files (x86)WTwareTFTPDROOT5.8.68pi2localbootfixup.dat».
10-54-11-546| [192.168.10.110] «0ca90504fixup.dat»: completed.
10-54-13-546| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-13-546| [192.168.10.110] Resend block 3774.
10-54-15-561| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-15-561| [192.168.10.110] Resend block 3774.
10-54-17-561| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-17-561| [192.168.10.110] Resend block 3774.
10-54-19-561| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-19-561| [192.168.10.110] Resend block 3774.
10-54-21-561| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-21-561| [192.168.10.110] Resend block 3774.
10-54-23-561| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-23-561| [192.168.10.110] Resend block 3774.
10-54-25-577| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-25-577| [192.168.10.110] Resend block 3774.
10-54-27-593| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-27-593| [192.168.10.110] Resend block 3774.
10-54-29-593| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-29-593| [192.168.10.110] Resend block 3774.
10-54-31-609| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-31-609| [192.168.10.110] Client not responding. Connection closed.

или так:
11-31-46-704| [TFTP] «0ca90504kernel7.img»: tsize is requested, blksize default.
11-31-46-704| [TFTP] «0ca90504kernel7.img»: «C:Program Files (x86)WTwareTFTPDROOT5.8.68pi2localbootkernel7.img».
11-31-50-283| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-31-50-283| [TFTP] Resend block 2233.
11-31-52-283| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-31-52-283| [TFTP] Resend block 2233.
11-31-54-283| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-31-54-283| [TFTP] Resend block 2233.
11-31-56-298| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-31-56-298| [TFTP] Resend block 2233.
11-31-58-298| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-31-58-298| [TFTP] Resend block 2233.
11-32-00-314| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-32-00-314| [TFTP] Resend block 2233.
11-32-02-314| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-32-02-314| [TFTP] Resend block 2233.
11-32-04-330| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-32-04-330| [TFTP] Resend block 2233.
11-32-06-330| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-32-06-330| [TFTP] Resend block 2233.
11-32-08-330| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-32-08-330| [TFTP] Client not responding. Connection closed.

На сниффере, снимающему трафик с порта, к которому подключен Raspberry Pi, видно, что от WTware на Raspberry Pi, просто перестают приходить TFTP Acknowledgement.

Источник

Troubleshooting Cases: Transferring Files Using FTP/TFTP

During system maintenance such as software upgrade and configuration file backup, files must be transferred between a PC and the device. FTP/TFTP is used to transfer files.

PC Functioning as an FTP Server

Run the FTP server software on the FTP server and configure the FTP service. For details, see relevant help documentation.

Connect the device and the FTP server. (The IP addresses are used as an example.)

1. Connect the FTP server to GE0/0/0 of the device using a network cable.
2. Configure an IP address 192.168.0.1/24 for GE0/0/0.
3. Configure an IP address 192.168.0.2/24 for the FTP server. (Configure an IP address for the network adapter of the PC. The configuration details are omitted.)

• In this example, the FTP server and the device are directly connected. If they are not directly connected, you must ensure that they have reachable routes to each other.
• After the configuration is complete, run the ping command to test the connectivity between the FTP server and device.

Log in to the FTP server using FTP.

Run the put command to upload files to the FTP server or run the get command to download files from the FTP server to the device.

PC Functioning as a TFTP Server

Run the TFTP server software on the TFTP server (PC) and configure the TFTP service. For details, see relevant help documentation.

Connect the TFTP server and the device and configure IP addresses for them. For details, see PC Functioning as an FTP Server.

Run the tftp put command to upload files to the TFTP server or run the tftp get command to download files from the TFTP server to the device.

Device Functioning as an FTP Server

Connect the PC and the device and configure IP addresses for them.

Enable FTP on the device, and create a user name, password, and FTP path.

Log in to the device by running the ftp command on the PC. Run the get command to download files from the device to the PC or run the put command to upload files to the device.

For example, on an FTP server with the Windows operating system, choose Start > Run, enter cmd, and click OK.

If you use the user name Administrator to log in to the PC, the output differs from the above.

You can run the lcd command to view the path where backup configuration files are saved.

The commands vary with the operating system. For details, see relevant help documentation of each operating system.

Источник

Troubleshooting Cases: Transferring Files Using FTP/TFTP

During system maintenance such as software upgrade and configuration file backup, files must be transferred between a PC and the device. FTP/TFTP is used to transfer files.

PC Functioning as an FTP Server

Run the FTP server software on the FTP server and configure the FTP service. For details, see relevant help documentation.

Connect the device and the FTP server. (The IP addresses are used as an example.)

1. Connect the FTP server to GE0/0/0 of the device using a network cable.
2. Configure an IP address 192.168.0.1/24 for GE0/0/0.
3. Configure an IP address 192.168.0.2/24 for the FTP server. (Configure an IP address for the network adapter of the PC. The configuration details are omitted.)

• In this example, the FTP server and the device are directly connected. If they are not directly connected, you must ensure that they have reachable routes to each other.
• After the configuration is complete, run the ping command to test the connectivity between the FTP server and device.

Log in to the FTP server using FTP.

Run the put command to upload files to the FTP server or run the get command to download files from the FTP server to the device.

PC Functioning as a TFTP Server

Run the TFTP server software on the TFTP server (PC) and configure the TFTP service. For details, see relevant help documentation.

Connect the TFTP server and the device and configure IP addresses for them. For details, see PC Functioning as an FTP Server.

Run the tftp put command to upload files to the TFTP server or run the tftp get command to download files from the TFTP server to the device.

Device Functioning as an FTP Server

Connect the PC and the device and configure IP addresses for them.

Enable FTP on the device, and create a user name, password, and FTP path.

Log in to the device by running the ftp command on the PC. Run the get command to download files from the device to the PC or run the put command to upload files to the device.

For example, on an FTP server with the Windows operating system, choose Start > Run, enter cmd, and click OK.

If you use the user name Administrator to log in to the PC, the output differs from the above.

You can run the lcd command to view the path where backup configuration files are saved.

The commands vary with the operating system. For details, see relevant help documentation of each operating system.

Источник

L2TP VPN troubleshooting

About This Document

Layer 2 Tunneling Protocol (L2TP) virtual private network (VPN) is an important VPN technology used in remote office scenarios to provide access for employees to remotely access intranet resources of enterprises. Users can dial up to establish L2TP VPN tunnels with enterprises through dialup clients on PCs so that they can remotely access servers of enterprises. A fault in L2TP VPN connections can affect the working efficiency of employees on business trips and deteriorates remote server access experience. This document describes common L2TP VPN faults that may occur on the live network and provides fault locating roadmaps and troubleshooting methods.

Application Scenarios of L2TP VPN

There are three L2TP VPN application scenarios: client-initiated, L2TP client-initiated, and NAS-initiated. After you determine the L2TP VPN application scenario and know the role of your AR router in the scenario, L2TP VPN fault troubleshooting can become easier.

Client-Initiated Scenario: Mobile Office Users Initiate L2TP Tunnel Connections to Access the Enterprise Intranet

Mobile office users (employees on business trips) of an enterprise access the Internet through Ethernet networks. The L2TP network server (LNS) functions as the egress gateway of the headquarters. The users can install a dialup client on their mobile terminals to directly establish L2TP tunnels with the LNS, with no need for an independent network access server (NAS). In this scenario, mobile office users can remotely access intranet resources of the enterprise, and flexibly, securely, and reliably work despite of geographical restrictions. Client-initiated L2TP VPN connections typically apply to the scenario where mobile office users of an enterprise need to access the headquarters.

In this scenario, an AR router functions as the LNS. Common L2TP VPN faults may occur on the LNS or dialup client.

L2TP Client-Initiated Scenarios: L2TP Clients Initiate L2TP Tunnel Connections for Intranet Interconnection

To allow users of an enterprise branch to access the headquarters, an L2TP client is deployed at the branch to automatically initiate dialup requests to the LNS to establish an L2TP tunnel and session. In this case, branch users do not need to perform dialup to trigger L2TP tunnel establishment. For branch users, they can access the headquarters network easily, without perceiving differences from that when they access their local branch network. In this scenario, an L2TP VPN tunnel is established between the enterprise headquarters and branch, facilitating enterprise management.

In this scenario, AR routers can function as the L2TP client and LNS, where common L2TP VPN faults may occur.

NAS-Initiated Scenario: Dialup Users Initiate L2TP Tunnel Connections Through the NAS to Access the Enterprise Intranet

To allow branch users of an enterprise to access the headquarters, a carrier deploys an L2TP tunnel between the NAS and LNS. Then users at branches can dial up to access the headquarters network through the NAS. Dialup users access the Internet through dialup. The NAS is deployed by a carrier to provide PPP or PPPoE access services for dialup users. Dialup users can access external networks through the NAS. The LNS is the egress gateway of the headquarters, which authenticates access users to ensure access security.

In this scenario, AR routers can function as the NAS and LNS, where common L2TP VPN faults may occur.

Implementation of L2TP VPN

L2TP VPN is implemented similarly in different scenarios. The following uses the Client-initiated scenario as an example to describe the process of establishing an L2TP tunnel. Figure 1-1 shows the entire tunnel negotiation process.

The mobile office user establishes an L2TP tunnel with the LNS.

The mobile office user establishes an L2TP session with the LNS.

The mobile office user will establish a PPP connection with the LNS in step 3, and the L2TP session records and manages the PPP connection status. Therefore, before a PPP connection is established, an L2TP session needs to be negotiated between the user and LNS. The session carries the LCP negotiation information and user authentication information of the mobile office user. After receiving such information, the LNS authenticates the information. After the authentication succeeds, the LNS notifies the NAS that the session is successfully established. The L2TP session is identified by the session ID.

The mobile office user establishes a PPP connection with the LNS.

The mobile office user obtains the LNS-assigned enterprise intranet IP address using the PPP connection.

The mobile office user sends service packets to access the enterprise HQ server.

Troubleshooting When an L2TP User Fails to Go Online

Checking Whether an L2TP Tunnel Is Established

Troubleshooting Process

In the client-initiated, L2TP client-initiated, or NAS-initiated connection scenario, an L2TP VPN has been configured between devices but PCs connected to the devices cannot communicate with each other. In this case, you can run the display l2tp tunnel command on the faulty device to check information about L2TP tunnels established on it. The following shows a sample command output on the LNS:

• If no tunnel information is displayed in the command output, run the display l2tp tunnel-down-reason command (in V200R010 and later versions) to locate the cause of the L2TP tunnel establishment failure. Then, perform troubleshooting according to Table 1 Possible causes of L2TP tunnel establishment failures and handling suggestions. You can also locate the fault according to the sections in this chapter.

The reset tunnel command was executed.

The tunnel is manually reset. No action is required.

There was no session.

No user goes online in the L2TP client-initiated scenario and the tunnel ages out. No action is required.

The received SCCRQ packet failed to pass the check.

Obtain SCCRQ messages to locate the fault.

The received SCCRP packet failed to pass the check.

Obtain SCCRP messages to locate the fault.

The received SCCCN packet failed to pass the check.

Obtain SCCCN messages to locate the fault.

The tunnel has been set up when the SCCRQ packet was received

Check whether the peer device is faulty.

The tunnel has been set up when the SCCRP packet was received.

Check whether the peer device is faulty.

The tunnel has been set up or was idle when the SCCCN packet was received.

Check whether the peer device is faulty.

The tunnel password was not configured in the L2TP group at the local end but peer device was configured.

Disable tunnel authentication on the peer device.

Sending an SCCRQ packet failed.

Check the public network interface status and public network route on the local device.

Sending an SCCRP packet failed.

Check the public network interface status and public network route on the local device.

Sending an SCCCN packet failed.

Check the public network interface status and public network route on the local device.

There was no SCCRP response from the peer and the packet retransmission count reached the limit.

Check whether the peer device receives SCCRP messages.

A StopCCN packet was received.

Obtain packets or check logs to locate the fault.

Sending a Hello packet failed.

Check whether the intermediate network is normal.

The received packets have already been encapsulated with the L2TP header.

Check the peer device.

The received SCCRQ packet failed to pass the remote name check.

Check configurations on the peer device.

The received SCCRP packet failed to pass the tunnel authentication.

Disable tunnel authentication on the local device.

The tunnel authentication was not configured in the L2TP group locally but was configured on peer device.

Disable tunnel authentication on the peer device.

The received SCCRP packet failed to pass local check due to an unknown AVP.

Obtain SCCRP messages to locate the fault. It is recommended that the AVP field carried in the SCCRP messages be modified on the peer device.

There was no SCCCN response from the peer and the packet retransmission count reached the limit.

Check the peer device and intermediate network.

There was no route to send the packet.

Check the route configuration on the public network interfaces of the devices at both ends.

The tunnel authentication was configured in the L2TP group locally but was not configured on peer device.

Disable tunnel authentication on the local device.

Troubleshooting When an AR Router Functions as an L2TP Client

Context

In the L2TP client-initiated connection scenario where an AR router functions as an L2TP client, after an L2TP VPN is configured between the L2TP client and LNS, the L2TP client and LNS cannot communicate with each other.

Troubleshooting Procedure

1. Check whether the automatic dialup function is enabled on the L2TP client for initiating L2TP connection requests. Check whether the serial port of the L2TP client displays the Up/Down information about the corresponding VT interface and whether the terminal monitor command is configured.

• If no Up/Down information about the corresponding VT interface is displayed on the serial port for a long time and no tunnel is established, the automatic dialup function is disabled on the L2TP client for initiating L2TP connection requests. Run the l2tp-auto-client enable command in the VT interface view to enable the automatic dialup function on the L2TP client for initiating L2TP connection requests.
• If the Up/Down information about the corresponding VT interface is displayed on the serial port but no tunnel is established, go to the next step.

Check whether the PPP user name configured on the VT interface of the L2TP client is the same as that configured in the L2TP group.

If the PPP user name is different from that configured in the L2TP group, change the PPP user name on the L2TP client to be the same.

Check whether the destination IP address of the L2TP tunnel is the LNS’s IP address and reachable.

If the specified destination IP address is not the LNS’s public IP address, change it to the LNS’s public IP address. If a firewall is deployed between the L2TP client and LNS, the ping operation may fail. Ensure that the firewall does not block L2TP packets.

Check whether the tunnel authentication mode configured on the L2TP client is the same as that configured on the LNS.

Ensure that the authentication configurations are the same on the L2TP client and LNS.

• Authentication is not configured on the L2TP client and LNS.
• Authentication is configured on the L2TP client and LNS, and the authentication modes are the same.

Check whether the tunnel name on the L2TP client is specified on the LNS.

• If the tunnel name on the L2TP client is specified on the LNS, check whether the tunnel name is correct.
• If tunnel name authentication is not enabled, you can specify the tunnel name on the L2TP client or not.

Troubleshooting When an AR Router Functions as an NAS

Context

In the NAS-initiated connection scenario where an AR router functions as an NAS, after an L2TP VPN is configured, the NAS and LNS cannot communicate with each other.

Troubleshooting Procedure

1. Check whether a PPP user accesses the NAS.

Run the display pppoe-server session all command to view the PPPoE session status and statistics on the NAS.

• If the PPPoE session is in DOWN state, no PPP user accesses the NAS. Check whether a PPP user has performed dialup to access the NAS.
• If the PPPoE session is in UP state, go to the next step.

Check whether the user authentication information is correct.

Check whether the PPP user name configured on the VT interface of the NAS is the same as that configured in the L2TP group.

If the PPP user name is different from that configured in the L2TP group, change the PPP user name on the NAS to be the same.

Check whether the destination IP address of the L2TP tunnel is the LNS’s IP address and reachable.

If the specified IP address is not the LNS’s public IP address, change it to the LNS’s public IP address. If a firewall is deployed between the NAS and LNS, the ping operation may fail. Ensure that the firewall does not block L2TP packets.

Check whether the tunnel authentication mode configured on the NAS is the same as that configured on the LNS.

Ensure that the authentication configurations are the same on the NAS and LNS.

• Authentication is not configured on the NAS and LNS.
• Authentication is configured on the NAS and LNS, and the authentication modes are the same.

Check whether the tunnel name on the NAS is specified on the LNS.

• If the tunnel name configured on the NAS is specified on the LNS, check whether the tunnel name on the NAS is correct.
• If tunnel name authentication is not enabled, you can specify the tunnel name on the NAS or not.

Troubleshooting When an AR Router Functions as an LNS

Context

In scenarios where an AR router functions as an LNS, after an L2TP VPN is configured, the LNS cannot communicate with the peer device.

Troubleshooting Procedure

1. Check whether an L2TP VPN tunnel is being established on the LNS.

If L2TP has been configured on the LNS but no debugging information is displayed in the command output, check whether the peer device or intermediate network is faulty.

Check whether the tunnel authentication mode configured on the LNS is the same as that configured on the peer device.

Ensure that the authentication configurations are the same on the LNS and peer device.

• Authentication is not configured on the LNS and peer device.
• Authentication is configured on both the LNS and peer device, and the authentication modes are the same.

Check whether the tunnel name on the peer device is specified on the LNS.

• If the tunnel name on the peer device is specified on the LNS, check whether the tunnel name is correct.
• If tunnel name authentication is not enabled on the peer device, you can specify the tunnel name on the peer device or not.

Check whether a VPN instance is configured on the interface connecting the LNS to the peer device.

If a VPN instance is configured, you need to add the VPN instance configuration to the L2TP configuration.

Checking Whether an L2TP Session Is Established

Troubleshooting Process

In the client-initiated, L2TP client-initiated, or NAS-initiated connection scenario, an L2TP VPN has been configured between devices but PCs connected to the devices cannot communicate with each other In this case, you can run the display l2tp session command on the faulty device to check information about L2TP sessions established on it. The following shows a sample command output on the LNS:

• If no session information is displayed in the command output, run the display l2tp session-down-reason command (in V200R009 and later versions) to locate the cause of the L2TP session establishment failure. Then, perform troubleshooting according to Table 1-2 You can also locate the fault according to the sections in this chapter.

the reset session command was executed.

No action is required. Wait for the session to be renegotiated.

the number of sessions reached the limit.

To support more concurrent sessions, replace the device with another one with higher specifications.

sending packets failed.

Check whether there is a route to the peer device.

the received ICRQ packet failed to pass the check.

Check whether the format of the ICRQ message and AVP field in the ICRQ message meet the protocol requirements.

the received ICRP packet failed to pass the check.

Check whether the format of the ICRP message and AVP field in the ICRP message meet the protocol requirements.

the received ICCN packet failed to pass the check.

Check whether the format of the ICCN message and AVP field in the ICCN message meet the protocol requirements.

the session has been established when the ICRQ packet was received.

Check whether the tunnel ID or session ID in the ICRQ message sent by the peer device is incorrect.

the session has been established when the ICRP packet was received.

Check whether the tunnel ID or session ID in the ICRP message sent by the peer device is incorrect.

the session has been established when the ICCN packet was received.

Check whether the tunnel ID or session ID in the ICCN message sent by the peer device is incorrect.

the session was idle when the ICRP packet was received.

Check whether the tunnel ID or session ID in the ICRP message sent by the peer device is incorrect.

the session was idle when the ICCN packet was received.

Check whether the tunnel ID or session ID in the ICCN message sent by the peer device is incorrect.

processing the ICRP packet failed.

Check whether the format of the ICRP message and AVP field in the ICRP message meet the protocol requirements.

an error occurred during data preparation.

The virtual access interface corresponding to the session fails to be created on the local device. Contact technical support personnel.

a CDN packet was received.

Check why the peer device requests to disconnect the tunnel.

there was no response for the ICRQ or ICRP packet.

The peer device does not respond to the ICRQ or ICRQ message. Check whether the configuration on the peer device and the return route are correct.

the PPP link was terminated.

If a PPP Terminate Request is received from the peer device, check why the peer device requests to terminate the session.

the Multichassis-MP bundle does not exist.

The negotiation fails or the peer device terminates the session. If services are affected, contact technical support personnel.

the session was Multichassis-MP temp call to find the bundle.

The MP service is processed normally, and no action is required.

Physical interface is down.

The physical interface alternates between Up and Down. Check whether the physical connection is normal.

PPP Authentication of peer device failed.

Check whether the user name and password configured on the local device are correct.

PPP Authentication failed from AAA Server.

Check whether the user name and password for L2TP dialup are correct and whether the authentication configurations on the AAA server are correct.

The IP Address of interface hasn’t been configured.

If no IP address of the VT interface is configured when the device functions as an LNS, configure an IP address for the VT interface.

The IP Address conflicts.

When the IP address allocated to the device functioning as the LAC conflicts with the IP address of another interface, check the address pool configuration on the LNS or change the IP address of another interface on the local device.

Troubleshooting When an AR Router Functions as an L2TP Client

Context

In the L2TP client-initiated connection scenario where an AR router functions as an L2TP client, after an L2TP VPN is configured between the L2TP client and LNS, the L2TP client and LNS cannot communicate with each other.

Troubleshooting Procedure

1. Check whether user authentication is successful.

Check whether an authentication failure log is recorded.

• If the user name or password is incorrect, configure it correctly.
• If the user name and password are correct, check whether authentication is enabled on the L2TP client.

Check whether the authentication modes are the same on the L2TP client and LNS.

Ensure that the authentication configurations are the same on the L2TP client and LNS.

• Authentication is not configured on the L2TP client and LNS.
• Authentication is configured on the L2TP client and LNS, and the authentication modes are the same.

Troubleshooting When an AR Router Functions as an NAS

Context

In the NAS-initiated connection scenario where an AR router functions as an NAS, after an L2TP VPN is configured, the NAS and LNS cannot communicate with each other.

Troubleshooting Procedure

1. Check whether user authentication is successful.

Check whether an authentication failure log is recorded.

• If the user name or password is incorrect, configure it correctly.
• If the user name and password are correct, check whether authentication is enabled on the NAS.

Check whether the tunnel authentication modes are the same on the NAS and LNS.

Ensure that the authentication configurations are the same on the NAS and LNS.

• Authentication is not configured on the NAS and LNS.
• Authentication is configured on the NAS and LNS, and the authentication modes are the same.

Troubleshooting When an AR Router Functions as an LNS

Context

In scenarios where an AR router functions as an LNS, after an L2TP VPN is configured, the LNS cannot communicate with the peer device.

Troubleshooting Procedure

1. Check whether user authentication is successful.

Check whether an authentication failure log is recorded.

If a log is recorded indicating that CHAP authentication fails, the PPP link is disconnected. Check whether the user name, password, and authentication mode configured in the AAA view on the LNS are the same as those on the peer device.

Ensure that the authentication configurations are the same on the LNS and peer device.

• Authentication is not configured on the LNS and peer device.
• Authentication is configured on the LNS and peer device, and the user name, password, and authentication mode are the same.

Check whether the correct address pool is specified on the VT interface of the LNS for assigning an IP address for the peer device.

• If the address pool is incorrect, run the remote address command to specify the correct address pool.
• If the address pool is correct, go to the next step.

Checking the L2TP Dialup Configuration on the PC

In the client-initialized scenario, when a PC uses the built-in dialup software to establish an L2TP VPN connection with the LNS, the dialup may fails. Table 1-3 provides common L2TP VPN connection faults on PCs and troubleshooting suggestions to help you quickly rectify faults and recover network services. If the fault persists, go to Troubleshooting Procedure for detailed troubleshooting procedure. The following uses a Windows 10 PC as an example.

A Windows 10 PC fails to establish an L2TP VPN connection through dialup.

The system returns the error «L2TP connection attempt failed because the security layer encountered a processing error during the initial negotiations with the remote computer.»

By default, the Windows 10 operating system does not support IPsec NAT Traversal (NAT-T) security associations to servers that are located behind a NAT device. Therefore, if the VPN server is behind a NAT device, a Windows 10 PC or Windows 10-based dialup client cannot set up an L2TP connection to the VPN server.

Modify the registry on the PC to rectify this fault.

Click Start and then Run. Enter regedit in the Open box and press Enter to open the Registry Editor. Locate and click HKEY_LOCAL_MACHINESystemCurrentControlSetServicesPolicyAgent . Create a DWORD value named AssumeUDPEncapsulationContextOnSendRule , and set the value to 2. Locate and click HKEY_LOCAL_MACHINESystemCurrentControlSetServicesRasmanParameters , create a DWORD value named ProhibitIpSec and set the value to 0. Then, restart the PC.

A Windows 7 PC fails to establish an L2TP VPN connection through dialup.

The system returns the error 789 «L2TP connection attempt failed because the security layer encountered a processing error during the initial negotiations with the remote computer.»

By default, the Windows 7 operating system does not support IPsec NAT-T security associations to servers that are located behind a NAT device. Therefore, if the VPN server is behind a NAT device, a Windows 7 PC or Windows 7-based dialup client cannot set up an L2TP connection to the VPN server.

Modify the registry on the PC to rectify this fault.

Click Start and then Run. Enter regedit in the Open box and press Enter to open the Registry Editor. Locate and click HKEY_LOCAL_MACHINESystemCurrentControlSetServicesPolicyAgent . Create a DWORD value named AssumeUDPEncapsulationContextOnSendRule , and set the value to 2. Locate and click HKEY_LOCAL_MACHINESystemCurrentControlSetServicesRasmanParameters , create a DWORD value named ProhibitIpSec and set the value to 0. Then, restart the PC.

A Windows PC establishes a L2TP VPN connection through dialup after dozens of attempts.

The system returns the error 691 «The remote connection was denied because the user name and password combination you provided is not recognized, or the selected authentication protocol is not permitted on the remote access server.»

This error occurs because the LNS supports only 16-byte challenge messages. When the length of challenge messages received by the LNS is not 16 bytes, CHAP authentication fails and error 691 is returned.

Run the mandatory-lcp command to enable mandatory LCP re-negotiation so that the LNS and clients negotiate 16-byte challenge messages.

Troubleshooting Procedure

1. Check whether the tunnel name configured on the LNS is the same as that configured on the dialup client.

• Check the tunnel name configured on the dialup client. Access VPN, select the L2TP VPN configuration file, and click Advanced options .
• Check whether the LNS has the same tunnel name.

If the tunnel names are different, run the allow l2tp command in the L2TP group view on the LNS to specify the same tunnel name. Alternatively, on the L2TP page of the PC, click Edit . On the Edit VPN connection page that is displayed, enter the server name or address, and click Save. A connection is then re-established.

Check whether tunnel authentication is enabled on both the dialup client and LNS.

• Check whether tunnel authentication is enabled on the LNS. If so, the tunnel authentication mode and ciphertext password are displayed in the display this command output.
• Check whether tunnel authentication is enabled on the dialup client. Right-click Start and choose Network Connections . Click Change adapter settings , right-click your VPN connection, and choose Properties from the shortcut menu. On the Security tab page, check the data encryption setting.

If tunnel authentication is enabled on the LNS but disabled on the dialup client, enable tunnel authentication on the dialup client. The tunnel authentication password on the dialup client must be the same as that configured on the LNS.

Troubleshooting When an L2TP User Goes Online Successfully but Services Are Unavailable

Context

In the client-initiated, L2TP client-initiated, or NAS-initiated scenario, after an L2TP VPN is configured between devices, services are interrupted, and access users on the devices cannot access intranet resources.

Troubleshooting Procedure

Perform a ping or tracert operation to check whether the local and peer devices can communicate with each other.

• If they can communicate with each other, check whether they have obtained the correct IP addresses and gateway information from the carrier and whether the peer device can communicate with the carrier’s gateway. For details, see Troubleshooting: IP Unicast Routing.
• If they cannot communicate with each other, go to the next step.

Troubleshooting When an L2TP User Goes Online and Offline Repeatedly Causing Frequent Service Interruption

Context

In the client-initiated, L2TP client-initiated, or NAS-initiated connection scenario, an L2TP VPN has been configured between devices but PCs connected to the devices cannot communicate with each other. In this case, check whether the following logs are recorded: IFNET/4/LINK_STATE:The line protocol [line-protocol] on the interface [interface-name] has entered the [state] state and PPP/4/CHAPAUTHFAIL:On the interface [interface-name], PPP link was closed because CHAP authentication failed. These logs show that the L2TP tunnel frequently alternate between Up and Down, causing frequent service interruptions.

Troubleshooting Procedure

1. Check whether the CPU usage of the devices is high. If the CPU usage exceeds 70%, PPP heartbeat packets time out.

If the CPU usage is too high, rectify the fault by referring to CPU Usage Is High.

Run the following command multiple times to check the statistics on the packets sent to the CPU and determine whether number of dropped L2TP packets increases.

If L2TP packets are lost, run the following commands to configure a larger rate limit for L2TP and PPP packets to be sent to the CPU.

Collecting Information About Common L2TP Faults

Run the display diagnostic-information file-name command in the user view to collect diagnostic information and save the information to a file.

After the diagnostic information file is generated, you can export the file from the device using TFTP, FTP, or SFTP. For details, see Local File Management.

You can run the dir command in the user view to check whether the file is generated.

You can also run the display diagnostic-information command and save terminal logs in a diagnostic file on a disk. For details, see Diagnostic File Obtaining Guide.

If this command output is too long, press Ctrl+C to abort this command.

The display diagnostic-information command displays system diagnostic information, which helps you locate faults but may affect system performance. For example, the CPU usage may become high. Therefore, do not use this command when the system is running properly.

Do not run the display diagnostic-information command simultaneously on multiple terminals connected to a device. This is because doing so may cause the CPU usage of the device to become high and the device performance to deteriorate.

Run the save logfile command in the user view to save the log and alarm information in the buffer to a file.

After the diagnostic information file is generated, export the file from the device using TFTP, FTP, or SFTP. For details, see Local File Management.

You can also run the display logbuffer and display trapbuffer commands to view the log and alarm information on the device, and save terminal logs in a diagnostic file on a disk. For details, see Diagnostic File Obtaining Guide.

Technical support personnel will provide instructions for you to submit all the collected information and files, so that they can locate faults.

Источник

Windows-терминалы WTware

Программа-клиент службы терминалов Windows Terminal Services, для бездисковых терминалов и загрузки по сети. Основной сайт http://www.wtware.ru

Ошибка TFTP

Ошибка TFTP

Сообщение Tpyna4ek » Ср апр 14, 2010 10:36 am

Re: Ошибка TFTP

Сообщение aka » Ср апр 14, 2010 11:32 am

Мало «решить его удалить». Надо его действительно удалить. Пуск — панель управления — администрирование — службы — упрощенный ftp.

Для проверки можно попробовать tftpd32. Если оно тоже скажет, что порт tftp занят — значит порт действительно занят.

Re: Ошибка TFTP

Сообщение Tpyna4ek » Ср апр 14, 2010 12:11 pm

Re: Ошибка TFTP

Сообщение aka » Ср апр 14, 2010 9:04 pm

Re: Ошибка TFTP

Сообщение 978143 » Вт ноя 16, 2010 6:15 am

Wtware 4.9.14
очень долго грузится терминал и потом появляется такое сообщение i`m tired (хотя вроде разобрался с сообщением)
а вот с торможением непонятки, лог прилагаю.

сам клиент на virtual box тестируется

смущает вот это:
[192.168.1.254] Requests file «4.9.14packageskernel». Tsize is requested, blksize 1240 bytes.
[192.168.1.254] Sending OASK (tsize 1554816, blksize 1240).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).
[192.168.1.254] Incorrect ACK received (expected 220, received 219).

Re: Ошибка TFTP

Сообщение aka » Вт ноя 16, 2010 6:50 am

Если оно доходит до «i`m tired», значит все, что оно хотело, оно загрузило.

Чуть выше, чем смущающий текст, есть кнопка «вести лог». Нажми ее

Re: Ошибка TFTP

Сообщение 978143 » Вт ноя 16, 2010 7:30 am

Источник

Windows-терминалы WTware

Программа-клиент службы терминалов Windows Terminal Services, для бездисковых терминалов и загрузки по сети. Основной сайт http://www.wtware.ru

Проблема с загрузкой TFTP

Проблема с загрузкой TFTP

Сообщение crazyfa » Ср окт 16, 2019 11:53 am

Re: Проблема с загрузкой TFTP

Сообщение aka » Ср окт 16, 2019 12:35 pm

Re: Проблема с загрузкой TFTP

Сообщение crazyfa » Ср окт 16, 2019 1:13 pm

Re: Проблема с загрузкой TFTP

Сообщение AlexPetrov » Чт дек 19, 2019 12:48 pm

Периодически всплывает проблема с загрузкой по сети WTware на Raspberry Pi 3 B+. Помогает только многократная перезагрузка Raspberry Pi.
В логах проблема выглядит так:
10-54-11-546| [192.168.10.110] «0ca90504fixup.dat»: tsize is requested, blksize default.
10-54-11-546| [192.168.10.110] «0ca90504fixup.dat»: «C:Program Files (x86)WTwareTFTPDROOT5.8.68pi2localbootfixup.dat».
10-54-11-546| [192.168.10.110] «0ca90504fixup.dat»: completed.
10-54-13-546| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-13-546| [192.168.10.110] Resend block 3774.
10-54-15-561| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-15-561| [192.168.10.110] Resend block 3774.
10-54-17-561| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-17-561| [192.168.10.110] Resend block 3774.
10-54-19-561| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-19-561| [192.168.10.110] Resend block 3774.
10-54-21-561| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-21-561| [192.168.10.110] Resend block 3774.
10-54-23-561| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-23-561| [192.168.10.110] Resend block 3774.
10-54-25-577| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-25-577| [192.168.10.110] Resend block 3774.
10-54-27-593| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-27-593| [192.168.10.110] Resend block 3774.
10-54-29-593| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-29-593| [192.168.10.110] Resend block 3774.
10-54-31-609| [192.168.10.110] Timeout occured while transfer «0ca90504start.elf».
10-54-31-609| [192.168.10.110] Client not responding. Connection closed.

или так:
11-31-46-704| [TFTP] «0ca90504kernel7.img»: tsize is requested, blksize default.
11-31-46-704| [TFTP] «0ca90504kernel7.img»: «C:Program Files (x86)WTwareTFTPDROOT5.8.68pi2localbootkernel7.img».
11-31-50-283| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-31-50-283| [TFTP] Resend block 2233.
11-31-52-283| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-31-52-283| [TFTP] Resend block 2233.
11-31-54-283| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-31-54-283| [TFTP] Resend block 2233.
11-31-56-298| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-31-56-298| [TFTP] Resend block 2233.
11-31-58-298| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-31-58-298| [TFTP] Resend block 2233.
11-32-00-314| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-32-00-314| [TFTP] Resend block 2233.
11-32-02-314| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-32-02-314| [TFTP] Resend block 2233.
11-32-04-330| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-32-04-330| [TFTP] Resend block 2233.
11-32-06-330| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-32-06-330| [TFTP] Resend block 2233.
11-32-08-330| [TFTP] Timeout occured while transfer «0ca90504kernel7.img».
11-32-08-330| [TFTP] Client not responding. Connection closed.

На сниффере, снимающему трафик с порта, к которому подключен Raspberry Pi, видно, что от WTware на Raspberry Pi, просто перестают приходить TFTP Acknowledgement.

Источник

Troubleshooting Cases: Transferring Files Using FTP/TFTP

During system maintenance such as software upgrade and configuration file backup, files must be transferred between a PC and the device. FTP/TFTP is used to transfer files.

PC Functioning as an FTP Server

Run the FTP server software on the FTP server and configure the FTP service. For details, see relevant help documentation.

Connect the device and the FTP server. (The IP addresses are used as an example.)

1. Connect the FTP server to GE0/0/0 of the device using a network cable.
2. Configure an IP address 192.168.0.1/24 for GE0/0/0.
3. Configure an IP address 192.168.0.2/24 for the FTP server. (Configure an IP address for the network adapter of the PC. The configuration details are omitted.)

• In this example, the FTP server and the device are directly connected. If they are not directly connected, you must ensure that they have reachable routes to each other.
• After the configuration is complete, run the ping command to test the connectivity between the FTP server and device.

Log in to the FTP server using FTP.

Run the put command to upload files to the FTP server or run the get command to download files from the FTP server to the device.

PC Functioning as a TFTP Server

Run the TFTP server software on the TFTP server (PC) and configure the TFTP service. For details, see relevant help documentation.

Connect the TFTP server and the device and configure IP addresses for them. For details, see PC Functioning as an FTP Server.

Run the tftp put command to upload files to the TFTP server or run the tftp get command to download files from the TFTP server to the device.

Device Functioning as an FTP Server

Connect the PC and the device and configure IP addresses for them.

Enable FTP on the device, and create a user name, password, and FTP path.

Log in to the device by running the ftp command on the PC. Run the get command to download files from the device to the PC or run the put command to upload files to the device.

For example, on an FTP server with the Windows operating system, choose Start > Run, enter cmd, and click OK.

If you use the user name Administrator to log in to the PC, the output differs from the above.

You can run the lcd command to view the path where backup configuration files are saved.

The commands vary with the operating system. For details, see relevant help documentation of each operating system.

Источник

Transferring Files Using FTP/TFTP

During system maintenance such as software upgrade and configuration file backup, files must be transferred between a PC and the device. FTP/TFTP is used to transfer files.

The FTP protocol and TFTP protocol will bring risk to network security. The SFTP V2 or SCP mode is recommended.

PC Functioning as an FTP Server

Run the FTP server software on the FTP server and configure the FTP service. For details, see relevant help documentation.

Connect the device and the FTP server. (The IP addresses are used as an example.)

1. Connect the FTP server to MEth0/0/0 of the device using a network cable.
2. Configure an IP address 192.168.0.1/24 for MEth0/0/0.
3. Configure an IP address 192.168.0.2/24 for the FTP server.

• In this example, the FTP server and the device are directly connected. If they are not directly connected, you must ensure that they have reachable routes to each other.
• After the configuration is complete, run the ping command to test the connectivity between the FTP server and device.

Log in to the FTP server using FTP.

Run the put command to upload files to the FTP server or run the get command to download files from the FTP server to the device.

PC Functioning as a TFTP Server

Run the TFTP server software on the TFTP server (PC) and configure the TFTP service. For details, see relevant help documentation.

Connect the TFTP server and the device and configure IP addresses for them. For details, see PC Functioning as an FTP Server.

Run the tftp put command to upload files to the TFTP server or run the tftp get command to download files from the TFTP server to the device.

Device Functioning as an FTP Server

Connect the PC and the device and configure IP addresses for them. For details, see PC Functioning as an FTP Server.

Enable FTP on the device, and create a user name, password, and FTP path.

You must set the user level to level 3 or above to establish an FTP connection.

Log in to the device by running the ftp command on the FTP server. Run the get command to download files to the FTP server or run the put command to upload files from the FTP server to the device.

For example, on an FTP server with the Windows operating system, choose Start > Run, enter cmd, and click OK.

If you use the user name Administrator to log in to the PC, the output differs from the above.

You can run the lcd command to view the path where backup configuration files are saved.

The commands vary with the operating system. For details, see relevant help documentation of each operating system.

Источник

Troubleshooting Cases: Transferring Files Using FTP/TFTP

During system maintenance such as software upgrade and configuration file backup, files must be transferred between a PC and the device. FTP/TFTP is used to transfer files.

PC Functioning as an FTP Server

Run the FTP server software on the FTP server and configure the FTP service. For details, see relevant help documentation.

Connect the device and the FTP server. (The IP addresses are used as an example.)

1. Connect the FTP server to GE0/0/0 of the device using a network cable.
2. Configure an IP address 192.168.0.1/24 for GE0/0/0.
3. Configure an IP address 192.168.0.2/24 for the FTP server. (Configure an IP address for the network adapter of the PC. The configuration details are omitted.)

• In this example, the FTP server and the device are directly connected. If they are not directly connected, you must ensure that they have reachable routes to each other.
• After the configuration is complete, run the ping command to test the connectivity between the FTP server and device.

Log in to the FTP server using FTP.

Run the put command to upload files to the FTP server or run the get command to download files from the FTP server to the device.

PC Functioning as a TFTP Server

Run the TFTP server software on the TFTP server (PC) and configure the TFTP service. For details, see relevant help documentation.

Connect the TFTP server and the device and configure IP addresses for them. For details, see PC Functioning as an FTP Server.

Run the tftp put command to upload files to the TFTP server or run the tftp get command to download files from the TFTP server to the device.

Device Functioning as an FTP Server

Connect the PC and the device and configure IP addresses for them.

Enable FTP on the device, and create a user name, password, and FTP path.

Log in to the device by running the ftp command on the PC. Run the get command to download files from the device to the PC or run the put command to upload files to the device.

For example, on an FTP server with the Windows operating system, choose Start > Run, enter cmd, and click OK.

If you use the user name Administrator to log in to the PC, the output differs from the above.

You can run the lcd command to view the path where backup configuration files are saved.

The commands vary with the operating system. For details, see relevant help documentation of each operating system.

Источник

18.05.2016, 11:23. Показов 83023. Ответов 2

<Quidway>display current-configuration

<Quidway>?
User view commands:
  backup         Backup electronic elabel
  cd             Change current directory
  clear          Clear information
  clock          Specify the system clock
  cluster        Run cluster command
  cluster-ftp    FTP command of cluster
  compare        Compare function
  copy           Copy from one file to another
  debugging      Enable system debugging functions
  delete         Delete a file
  ---- More ----

<Quidway>dir
Directory of flash:/

  Idx  Attr     Size(Byte)  Date        Time       FileName
    0  -rw-         14,340  May 17 2016 09:48:24   sw-a-2-1-5348-ip20.cfg
    1  drw-              -  Oct 01 2008 00:08:07   user
    2  -rw-          1,794  Oct 01 2008 00:01:15   private-data.txt
    3  drw-              -  Oct 01 2008 00:08:51   dhcp
    4  drw-              -  Oct 01 2008 00:04:09   syslogfile
    5  drw-              -  Oct 01 2008 00:04:17   resetinfo
    6  -rw-         14,327  May 17 2016 09:34:21   vrpcfg.cfg
    7  -rw-         12,240  May 13 2016 14:14:41   $_patchstate_reboot
    8  -rw-          3,684  May 13 2016 11:14:36   $_patch_history
    9  -rw-     11,113,860  May 13 2016 12:29:36   s5300ei-v100r005c01spc100.cc
   10  -rw-        405,483  May 13 2016 13:31:04   rbsaveddata.txt
   11  -rw-      1,112,497  May 13 2016 14:04:35   s23_33_53-v100r005sph021.pat
   12  -rw-      1,089,375  May 13 2016 14:05:33   s5300ei-v100r005c01spc100.web.zip

30,008 KB total (16,300 KB free)

<Quidway>copy vrpcfg.cfg vrpcfg-my-switch.cfg
Copy flash:/vrpcfg.cfg to flash:/vrpcfg-my-switch.cfg?[Y/N]:y
100%  complete|
Info: Copied file flash:/vrpcfg.cfg to flash:/vrpcfg-my-switch.cfg...Done.
<Quidway>startup saved-configuration vrpcfg-my-switch.cfg
Info: Succeeded in setting the configuration for booting system.
<Quidway>save
The current configuration will be written to the device.
Are you sure to continue?[Y/N]y
Now saving the current configuration to the slot 0 .
Info: Save the configuration successfully.
<Quidway>dir
Directory of flash:/

  Idx  Attr     Size(Byte)  Date        Time       FileName
    0  -rw-         14,340  May 17 2016 09:48:24   sw-a-2-1-5348-ip20.cfg
    1  drw-              -  Oct 01 2008 00:08:07   user
    2  -rw-          1,794  Oct 01 2008 00:01:15   private-data.txt
    3  drw-              -  Oct 01 2008 00:08:51   dhcp
    4  drw-              -  Oct 01 2008 00:04:09   syslogfile
    5  drw-              -  Oct 01 2008 00:04:17   resetinfo
    6  -rw-         14,327  May 17 2016 09:34:21   vrpcfg.cfg
    7  -rw-         14,340  May 18 2016 10:00:30   vrpcfg-my-switch.cfg
    8  -rw-         12,240  May 13 2016 14:14:41   $_patchstate_reboot
    9  -rw-          3,684  May 13 2016 11:14:36   $_patch_history
   10  -rw-     11,113,860  May 13 2016 12:29:36   s5300ei-v100r005c01spc100.cc
   11  -rw-        405,483  May 13 2016 13:31:04   rbsaveddata.txt
   12  -rw-      1,112,497  May 13 2016 14:04:35   s23_33_53-v100r005sph021.pat
   13  -rw-      1,089,375  May 13 2016 14:05:33   s5300ei-v100r005c01spc100.web.zip

30,008 KB total (16,284 KB free)

<Quidway>tftp 192.168.254.100 put vrpcfg-my-switch.cfg
Info: Transfer file in binary mode.
Uploading the file to the remote TFTP server. Please wait.../
TFTP: Uploading the file successfully.
   14340 bytes send in 1 second.

<Quidway>tftp 192.168.254.100 get vrpcfg-my-switch.cfg
Info: Transfer file in binary mode.
Downloading the file from the remote TFTP server. Please wait...
The file vrpcfg-my-switch.cfg exists. Overwrite it?[Y/N]:y
Warning: The file vrpcfg-my-switch.cfg is a system resource file that is in use, overwrite it?[Y/N]:y
|
TFTP: Downloading the file successfully.
   14340 bytes received in 3 seconds.

<Quidway>reboot
Info: The system is now comparing the configuration, please wait.
System will reboot! Continue?[Y/N]:Y

<Quidway>system-view
Enter system view, return user view with Ctrl+Z.
[Quidway]

<Quidway>sy
Enter system view, return user view with Ctrl+Z.
[Quidway]?
System view commands:
  aaa                     AAA view
  acl                     Specify ACL configuration information
  anti-attack             Specify anti-attack configurations
  application-apperceive  Set application-apperceive information
  arp                     Specify ARP configuration information
  arp-miss                Specify ARP MISS configuration information
  arp-suppress            Specify arp suppress configuration information,
                          default is disabled
  autoconfig              AutoConfig configuration information
  bfd                     Specify BFD(Bidirectional Forwarding Detection)
                          configuration information
  ---- More ----

[Quidway]int gig 0/0/1
[Quidway-GigabitEthernet0/0/1]dis th
#
interface GigabitEthernet0/0/1
 voice-vlan 120 enable
 voice-vlan legacy enable
 stp edged-port enable
 ntdp enable
 bpdu enable
 mac-authen
 mac-authen guest-vlan 126
#
return
[Quidway-GigabitEthernet0/0/1]dis int gig 0/0/1
GigabitEthernet0/0/1 current state : UP
Line protocol current state : UP
Description:HUAWEI, Quidway Series, GigabitEthernet0/0/1 Interface
Switch Port,PVID :    1,The Maximum Frame Length is 1600
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is ac85-3ddf-22f0
Port Mode: COMMON COPPER
Speed : 1000,  Loopback: NONE
Duplex: FULL,  Negotiation: ENABLE
Mdi   : AUTO
Last 300 seconds input rate 952 bits/sec, 0 packets/sec
Last 300 seconds output rate 9984 bits/sec, 13 packets/sec
Input peak rate 975112 bits/sec,Record time: 2016-05-17 16:26:04
Output peak rate 751496 bits/sec,Record time: 2016-05-18 09:09:04
Input:  124813 packets, 24769273 bytes
Unicast        :              119918,Multicast          :                4709
Broadcast      :                 186,Jumbo              :                   0
CRC            :                   0,Giants             :                   0
Jabbers        :                   0,Throttles          :                   0
Runts          :                   0,DropEvents         :                   0
Alignments     :                   0,Symbols            :                   0
Ignoreds       :                   0,Frames             :                   0
Discard        :                   0,Total Error        :                   0
Output:  612510 packets, 167203246 bytes
  ---- More ----
[Quidway-GigabitEthernet0/0/1]display mac-authen int gig 0/0/1

 GigabitEthernet0/0/1 state: UP.  MAC address authentication is enabled
  Maximum users: 256
  Current users: 1
  Authentication Success: 4, Failure: 0
  Guest VLAN 126 is not effective

 Online user(s) info:
 UserId   MAC/VLAN            AccessTime              UserName
 ------------------------------------------------------------------------------
 303      001c-c074-ae1a/46   2016/05/18 09:20:19     001cc074ae1a@cams
 ------------------------------------------------------------------------------
 Total 1,1 printed
[Quidway-GigabitEthernet0/0/1]?
gigabitethernet-l2 interface view commands:
  als                    set automatic laser shutdown
  am                     port isolate
  arp                    Specify ARP configuration information
  arp-limit              Limit the number of learnt ARP
  arp-miss               Specify ARP MISS configuration information
  auto                   Auto negotiates port mode
  bpdu                   BPDU message
  broadcast-suppression  Set broadcast flow suppression
  carrier                Set carrier function
  cfm                    Connectivity fault management, which is defined in the
                         802.1ag
  ---- More ----

1