This document describes how to handle common problems caused by incorrect configurations, including incorrect parameter settings, missing key configurations, and misconfigurations, and provides detailed handling suggestions and procedures.
STAs have difficulties in going online or roaming, cannot go online or roam, or connect to a remote AP.
Error-prone configuration: Network planning is not performed before AP deployment, or APs are not deployed according to the network plan.
Suggestion: Test the onsite signal strength or use the CloudCampus APP to scan the onsite signal heatmap. Re-plan the network to adjust the AP deployment or deploy more APs to ensure signal coverage.
Check whether CAC is configured in the RRM profile and whether the CAC threshold is set properly. Check whether a large number of STAs failed to go online due to rejection by CAC.
Threshold (RSSI) = Threshold (SNR) + Noise. The value of Noise is –95 dBm.
Based on the preceding command output, the RSSI threshold is –45 dBm, calculated by 50 + (–95 dBm). This threshold is too high for STAs to access the network.
If the live network is well planned and the coverage is good (greater than –65 dBm), it is recommended that this threshold be set to about 15.
Suggestion: If the problem is caused by the user CAC function, disable the user CAC function or adjust thresholds as required.
Check whether the maximum number of access STAs is configured.
Error-prone configuration: The maximum number of access STAs is set too small, so STAs fail to access the network.
Suggestion: Restore the maximum number of access STAs to the default value or increase the maximum number of access STAs as required.
Check whether load balancing is enabled.
Suggestion: Restore the default deny threshold for STA access. If the fault persists, disable load balancing.
Check whether the function of disconnecting STAs is configured and whether the threshold is set properly.
Error-prone configuration: The threshold for disconnecting STAs is set too high, causing STAs to go offline frequently.
Suggestion: In scenarios with good coverage, the threshold of 15 or 20 is recommended.
Check whether the function of denying access from legacy STAs.
Suggestion: It is recommended that this function be disabled unless necessary.
Check whether the service VLAN is configured the same as the management VLAN or VLAN 1 is configured as the service VLAN.
If no service VLAN is displayed, the current service VLAN is the default VLAN 1.
Suggestion: Properly plan the service VLAN. Do not configure it to be VLAN 1 or the same as the management VLAN
STAs Go Offline Unexpectedly
Fault Symptom
STAs frequently go offline or go online and offline.
Procedure
- Check whether a STA frequently roams.
Check measure: Run the display station roam-track sta-mac sta-mac command to check the roaming track of the STA. If the STA frequently roams, use a Wi-Fi signal scanning tool to check whether the signal strength in the target area is lower than –65 dBm.
Suggestion: Re-plan the network to adjust the AP deployment or increase APs to ensure signal coverage.
Check whether smart roaming thresholds are set properly.
- High thresholds related to smart roaming are configured, causing STAs to frequently go online and offline.
- The AC is configured to disconnect STAs based on the STA rate.
- In scenarios with good coverage, the threshold of 15 or 20 is recommended.
- Delete the trigger mode configuration of smart roaming as check-rate. In most cases, this configuration can cause STAs to frequently go online and offline.
STAs Encounter Slow Network Access
Fault Symptom
The transmission speed or the speed displayed on a STA is low.
Procedure
- Check whether only the 2.4 GHz network is enabled.
Error-prone configuration: No VAP service is referenced in the AP group view or AP specific view, or the radio disable command is configured.
Suggestion: Enable the 5 GHz radio unless necessary to release burden on 2.4 GHz radios.
Check whether the rate limit is configured in the traffic profile, causing slow network access for STAs.
Error-prone configuration: Rate limiting is configured, and the rate limit is set low.
Suggestion: Set a proper rate limit based on the number of access STAs and service planning.
Check whether the rate limit is configured in the SSID profile.
Traffic policing controls traffic by monitoring the rate of traffic, and discards excess traffic to limit traffic within a specified range and to protect network resources.
When data is sent from a high-speed link to a low-speed link, the low-speed link bandwidth is insufficient. As a result, a large number of packets are discarded. In this case, the data traffic rate needs to be limited. The interface of the high-speed link then discards the packets whose rate exceeds the traffic policing rate so that the outgoing traffic rate is limited to a specified range. You can also configure traffic policing for incoming traffic on the interface of the low-speed link. When the CBS is smaller than the number of bytes in a packet, packets of this type are discarded.
Error-prone configuration: Traffic policing is configured in the SSID profile.
Suggestion: Disable traffic policing in the SSID profile, unless necessary.
Check whether the TKIP encryption mode is used, causing a low link setup rate.
The 802.11n APs can be encrypted in WEP or TKIP mode. The association rate displayed on the STAs may be only 54 Mbit/s because the 802.11n standard does not define the WEP or TKIP encryption mode. If the 802.11n APs use the WEP or TKIP encryption mode, the STAs are associated only at 802.11g rates.
Error-prone configuration: The TKIP encryption mode is used.
Suggestion: Set the AES or TKIP-AES encryption mode.
Check whether the WMM function is disabled.
802.11ax, 802.11ac, and 802.11n STAs must support WMM. If the WMM function is disabled on a radio, 802.11ax, 802.11ac, and 802.11n cannot work and STAs can access the network only in 802.11a/b/g mode.
Suggestion: Enable the WMM function.
Источник
Troubleshooting S Series Switch Port and Interface Problems
Introduction
This document describes how to check the switch interface or port status and how to locate an interface physically down fault and restore the interface to the up state.
Major causes of the interface physically down event include hardware and software failures.
Hardware failures: include hardware failures of the local and peer devices, such as failures of cards, interfaces, optical modules, fibers, and network cables.
Software failures: include inconsistent configurations of the local and peer devices, such as the interface negotiation mode, rate, and duplex configuration.
The following figure shows the possible causes of the interface physically Down event.
How Do I Check the Interface or Port Status?
Checking Service Interface Indicators to Determine the Interface Status
Observe service interface indicators to quickly identify the service interface status. The following uses the S6730-H48X6C as an example. In Figure 1-1, the indicator numbered 4 is a 10GE optical interface indicator, and the indicator numbered 5 is a 40GE/100GE optical interface indicator.
The interface is not connected or has been shut down. The interface cannot send or receive packets normally.
A link has been established on the interface.
The interface is sending or receiving data.
The interface is sending or receiving data.
Running the display interface brief or display interface interface-type interface-number Command to Check the Interface Physical Status
You can run the display interface brief command in any view to check the physical status of all interfaces (based on the PHY field in the command output).
Alternatively, run the display interface interface-type interface-number command in any view to check the physical status of a specified interface (based on the current state field in the command output).
In the preceding command output, the physical status of GE0/0/12 is Administratively DOWN, indicating that the shutdown command has been run on the interface. To enable the interface to go up, run the undo shutdown command in the interface view.
- For a Layer 2 physical interface (an Ethernet interface works at Layer 2 mode by default): If its physical status indicated by the current state field displays up, its protocol status indicated by the Line protocol current state field displays up. For example, if a Layer 2 physical interface is connected correctly and its attribute configuration is correct, its physical status and protocol status are both up.
- For a Layer 3 physical interface (The undo portswitch command has been run on the interface to change the working mode of the interface from Layer 2 mode to Layer 3 mode): Its protocol status indicated by the Line protocol current state field displays up only when its physical status indicated by the current state field displays up and its protocol negotiation succeeds. For example, if a Layer 3 physical interface is connected correctly, its attribute configuration is correct, and it is not configured with an IP address, its physical status and protocol status are up and down respectively.
The following table lists more commands for checking interface configurations or statistics.
display interface counters
Display statistics about packets sent or received on physical interfaces.
display interface ethernet brief
Display brief information about Ethernet interfaces, including the physical status, auto-negotiation mode, duplex mode, rate, and average bandwidth usages in the inbound and outbound directions in the recent period.
display counters error
Display error packet statistics on interfaces.
display error-down recovery
Display information about the interfaces in error-down state, including the interface name, cause of the error-down event, delay after which an interface changes to up, and remaining time for the up event.
Checking Interface Logs to Identify the Interface Status
Causes of an Interface Physically Down Event and Troubleshooting Methods
How Do I Locate and Rectify an Interface Physically Down Fault Caused by Improper Operations?
Cause Description
When an interface changes from up to physically down, check whether improper operations are performed recently. For example, check whether cables are incorrectly removed and installed, accidental touch on the device causes loose cable connections, or misoperations are performed using commands on the device.
Troubleshooting Method
In any view of the interconnected two devices, run the display interface interface-type interface-number command to check the current running status and statistics of the specified interface.
Recovery Measure
- In the command output, if the current state field displays Administratively down, the interface has been manually shut down. You need to run the undo shutdown command on the interface.
- If the current state field displays Down, check whether interfaces on both ends of the link have the same rate, duplex mode, and auto-negotiation mode. Use recovery methods based on the value of the Negotiation field.
Negotiation Field Value
Indicates that the interface works in auto-negotiation mode. The interface rate and duplex mode are negotiated by both ends.
If the negotiated interface rate and duplex mode are different on both ends, run the restart command on the interface to restart the interface for re-negotiation. If the negotiation fails, run the undo negotiation auto command on the interface to configure the interface to work in non-auto negotiation mode. For details about how to configure the interface rate and duplex mode, see the recovery method used when the Negotiation field displays DISABLE.
Indicates that the interface works in non-auto negotiation mode. Run the speed < 10| 100 | 1000 | 2500 | 5000 | 10000 > and duplex < full | half > commands in the interface view to adjust the rate and duplex mode of the interface to ensure that the two parameters on both ends are the same.
Before taking recovery measures, you are advised to rectify service faults to prevent the interface from entering the ERROR DOWN state again.
You can recover an interface from the ERROR DOWN state using either of the following measures:
Run the shutdown and undo shutdown commands or run the restart command in the interface view to restart the interface.
Run the error-down auto-recovery cause down-cause interval interval-value command in the system view to enable an interface to automatically restore to Up state from the Error-Down state.
Value of the down-cause Field
When the device negotiates to the AS mode, its interface status becomes down and then becomes up after services in the service profiles have been delivered.
After the auto-defend action command is used to configure actions against attack sources, the interface that receives attack packets is shut down to prevent the device from attacks.
On an STP-enabled network, run the stp bpdu-protection command after BPDU protection is configured on edge interfaces of a switch, the switch sets the physical status of the edge interface that receives BPDUs to down to block services on this interface if the switch is attacked by forged BPDUs.
When the efm trigger error-down command associates a remote fault event with the current interface of a switch, the switch sets the protocol status of the interface to down to interrupt all services on the interface if EFM detects the critical-event, dying-gasp, link-fault, or timeout fault event.
When link monitoring is configured for an interface on a link, the link is considered unavailable if the number of errored frames, errored codes, or errored frame seconds detected by the interface reaches or exceeds the threshold within a specified period. You can run the efm threshold-event trigger error-down command to associate an EFM threshold crossing event with the current interface. The system then sets the administrative status of the interface to down. In this manner, all services on the interface are interrupted.
When an Ethernet interface configured with a backup link receives error packets, faults such as service packet loss occur. Run the error-statistics threshold-event trigger error-down command. To ensure nonstop service transmission, when the number of received error packets reaches the alarm threshold, the interface is shut down and services are switched to the backup link.
An interface receives Runts error packets if the optical fiber, network cable, or optical module is removed and reinstalled, the shutdown or undo shutdown command is executed, or Runts packets are forwarded on the network. To avoid worse impact on the device or services, the device counts the number of Runts error packets received by an interface within 1 minute, and shuts down the interface if the number reaches the alarm threshold 5.
Cable faults or active/standby switchovers will cause an interface to frequently alternate between up and down. You can run the port link-flap protection enable command to enable link flapping protection on the interface. When the switch receives an interface up/down message, it checks the number of interface flappings and interval. If the number of interface flappings within the specified period reaches the configured limit, the switch shuts down the interface.
Run the storm-control action command. After the storm control action is configured as error-down on an interface, the interface is shut down when the average rate of received broadcast, multicast, and unknown unicast packets is larger than the specified limit within the interval for detecting storms.
When interface security is configured on a switch, the MAC addresses learned by the switch become secure dynamic MAC addresses. If the port-security protect-action command sets the security protection action to shutdown on an interface, the interface is shut down when the number of secure MAC addresses learned by the interface exceeds the upper limit or static MAC address flapping is detected after static MAC address detection is enabled.
When MAC address flapping occurs on a user network because of loops, you can configure a loop prevention action for the switch to perform when MAC address flapping occurs. After the MAC address flapping action is configured on an interface, if the switch detects MAC address flapping on the interface, it sets the physical status of the interface to down.
When the optical power of an Ethernet optical interface configured with a backup link is reduced, faults such as packet loss occur. To ensure normal service operation, run the transceiver power low trigger error-down command. Then the interface is triggered to transit to the error-down state and services are switched immediately if the optical power is lower than the lower alarm threshold.
After the switch runs for a long time, the chip memory identifier has a data integrity error.
How Do I Locate and Rectify an Interface Physically Down Fault Caused by Hardware Faults?
Cause Description
When a card, an interface, or the peer device becomes faulty, the corresponding interface becomes physically down. Therefore, check whether hardware failures exist.
Troubleshooting Method
Run the display interface brief command in any view to check brief information about the status and configuration of all interfaces.
- If multiple interfaces change from up to down, cards of the local device or peer device may become faulty and the peer device status may change. For example, an active/standby switchover is performed on the peer device, the peer device is in sleeping state or restarted.
- If a single interface changes from up to down, check whether any metal reeds in the two connected interfaces have sunk or shifted. If not, run the loopback internal command in the interface view to check whether hardware failures occur in the interface. If the interface status indicated by the current state field changes to up after the loopback internal command is executed, the internal connection of the interface is normal and no hardware failure occurs. If the interface status is still down, the internal connection of the interface is abnormal and a hardware failure occurs.
Recovery Measure
- Multiple interfaces become physically Down.
- If multiple interfaces become physically down and these interfaces belong to the same card and are connected to multiple normal peer devices, the card may be faulty. Run the reset slot slot-id command to reset the card. If the fault persists, replace this card.
- If multiple interfaces become physically down and these interfaces connect the local device to the same peer device, the peer device may be faulty. You need to log in to the peer device to check whether the corresponding card is faulty. If so, reset or replace it. If an active/standby switchover is performed on the peer device, or the peer device is in sleeping state or restarted, it is a normal situation that these interfaces become physically down. These interfaces will automatically return to the up state after the peer device becomes stable. In this scenario, the interfaces will frequently alternate between up and down, causing a large number of the following up/down logs:
If the peer device is frequently restarted, for example, an AP connected to a switch is frequently restarted, the interface that connects the switch to the AP becomes physically down. You need to check the reason for the frequent AP restart and determine whether a network loop occurs, whether a large number of ARP broadcast packets exist, and whether a network attack occurs. If these problems exist, solve them to ensure that the interface becomes up.
- A single interface becomes physically Down
If only a single interface becomes physically down, check whether any metal reeds in the two connected interfaces have sunk or shifted. If one interface becomes faulty, use another idle interface to replace this interface.
How Do I Locate and Rectify an Interface Physically Down Fault Caused by Connection Medium Faults?
Cause Description
Physical interfaces of switches include electrical and optical interfaces. Involved transmission media include RJ45 cables, optical modules, and fibers. When transmission media are aging or damaged or optical modules receive and send signals abnormally, interfaces become physically down.
Troubleshooting Method
Connection media failures of electrical interfaces
- Check whether cables are connected correctly.
Ensure that interfaces on both ends are connected using the same network cable. If the two interfaces are connected through the optical distribution frame, ensure that the network cables are connected correctly. Ensure that the interfaces are connected correctly, and that the cable is firmly installed and intact.
- Check whether the cable specification and length comply with related standards.
According to Ethernet cable standards, the network cable length cannot exceed 100 meters. A GE electrical interface working at 1000 Mbits cannot go Up when it uses a network cable of a category lower than Category 5. A network cable of a category higher than Category 5 is recommended for the connection between electrical interfaces.
- Check whether the status of line pairs in cables is normal.
If any of the four line pairs in a cable is damaged, connected electrical interfaces cannot go up. Use a cable tester or run the virtual-cable-test command in the interface view to check whether line pairs in cables are correctly connected.
If the Pair state field displays Ok, line pairs are normal. If the Pair state field displays Unknown, you are advised to use a cable analyzer to perform a test. If the Pair state field displays another state ( Open or Short for example), replace the cable with another cable.
Connection media failures of optical interfaces
- Check whether the optical module of the interface is a Huawei-certified optical module.
For the Huawei-certified optical modules, Huawei has added Huawei logo and identifier and changed the vendor information in the product elabel and optical module information into HUAWEI.
When a non-certified optical module is installed into a switch, the switch reports an alarm. The alarm format is as follows:
- Check whether the optical module is normal.
- If a non-Huawei certified optical module is installed, replace it with a Huawei-certified optical module. Non-Huawei certified optical modules cannot ensure transmission reliability and may affect service stability. Huawei is not responsible for any problem caused by the use of non-Huawei certified optical modules and will not fix such problems.
- Run the display transceiver interface command to check the parameters of optical modules and whether these parameters are within the normal range according to the following table.
- If the current of an optical module is too high or too low, replace the optical module.
- If the transmit power of an optical module is too low or too high, replace the optical module.
- If the receive power of an optical module is too low or too high, use an optical power meter to test the optical power attenuation of each part of the link and repair abnormal parts. If the fault persists, replace the optical module or fiber to ensure that the transmission distance and fiber type of the optical module meet networking requirements.
- Run the display device command in any view to check the device model and component information. If the device is a modular switch, you can focus on the corresponding card names.
- Use the hardware query tool to check whether the used optical module type matches the interface and whether the optical module matches the fiber model.
- Run the display transceiver interface command in any view of the two devices to check whether optical module parameters on the two devices are consistent.
- Check whether fibers are connected correctly. An optical module provides a TX end and an RX end. When connecting two interfaces, you need to connect the TX and RX ends of one optical module to the RX and TX ends of the other optical module using two fibers.
- Ensure that the currently used optical module matches the optical interface and fiber according to the hardware query tool. If they do not match, replace the corresponding component.
- If the parameters of the optical modules on both ends of the link are inconsistent, replace the corresponding components.
- Ensure that optical fibers are correctly connected.
- If the current interface is a combo interface, ensure that its working mode meets the following requirements:
- When the auto mode is specified, the system checks whether the combo optical interface has an optical module installed, and selects the interface working mode as follows. To specify the auto mode, run the combo-port auto command in the interface view. By default, a combo interface works in auto mode.
- Before the switch restarts, the combo interface works as an electrical interface.
- After the switch restarts, the combo interface works as an optical interface.
- Check the temperature and humidity in the equipment room.
Run the display transceiver interface command to check whether optical modules of interfaces on both ends are normal, including the receive power, transmit power, and current. Ensure that these values are in the normal range.
Optical Module Attribute
Bias current (mA)
The value is between Bias LowThreshold(mA) and Bias High Threshold(mA).
Current Rx Power (dBM)
The value is between Default Rx Power LowThreshold(dBM) and Default Rx Power LowThreshold(dBM).
Current Tx Power (dBM)
The value is between Default Tx Power LowThreshold(dBM) and Default Tx Power LowThreshold(dBM).
Recovery Measure
Connection media failures of electrical interfaces
If the cable of an electrical interface is faulty, you are advised to replace this cable.
Connection media failures of optical interfaces
How Do I Locate and Rectify an Interface Physically Down Fault Caused by the Improper Use of Connection Medium?
Cause Description
When connecting two devices, check whether optical modules match optical interfaces, whether optical modules match fiber models, and whether optical modules and fibers are connected correctly. When an interface becomes physically down, rectify the fault accordingly.
Troubleshooting Method
Check whether the interface is a combo interface. If so, check whether the combo interface is used correctly. That is, check whether the current working mode of the interface is consistent with the current connection.
Combo interface GE1/0/1 corresponds to two interfaces on the device panel: combo optical interface and combo electrical interface. The two interfaces cannot work at the same time. To configure the attributes of the combo optical or electrical interface, enter the same interface view of GE1/0/1.
Recovery Measure
Combo Interface Status
Working Mode of a Combo Interface
The combo electrical interface is not connected, and the combo optical interface has an optical module installed.
The combo interface works as an optical interface.
The combo electrical interface is connected using a network cable, the combo interface is up, and the combo optical interface has an optical module installed.
The combo electrical interface is connected using a network cable, the combo interface is down, and the combo optical interface has an optical module installed.
The combo interface works as an optical interface.
In summary, when the auto mode is specified and the combo optical interface has an optical module installed, the combo interface works as an optical interface after the device restarts. Determine whether to install an optical module into the combo optical interface based on the connection medium (optical fiber or network cable).
When the working mode of the combo interface is the force mode, you can forcibly specify the working mode based on the type of the interface connecting the local and remote devices.
Type of the Interface Connecting the Local Device to the Remote Device
The local combo electrical interface is connected to the remote electrical interface.
Run the combo-port copper command in the interface view to set the working mode of the combo interface to copper.
The local combo optical interface is connected to the remote optical interface.
Run the combo-port fiber command in the interface view to set the working mode of the combo interface to fiber.
In summary, after confirming that the transmission media (optical fibers or cables) are correct, check whether the working mode of the combo interface is correct. You can run the combo-port < copper | fiber > command to ensure that the working mode of the interface matches the connection media.
How Do I Locate and Rectify an Interface Physically Down Fault Caused by Environmental Factors?
Cause Description
Switches can be used in various scenarios at any network layer. When a switch and its connection media become faulty because of environmental factors, interfaces of the switch may become physically Down.
Troubleshooting Method
For S series switches, the operating temperature is in the range 0ºC to 45ºC, the relative humidity is in the range 5% RH to 95% RH (non-condensing).
- Check cable layout.
Power cables and service cables must be deployed separately. Low-current lines must be separated from high-current lines to prevent interference. Check whether network cables are damaged and aged out because of high temperature or rack wear.
Источник
-
-
December 26 2012, 12:02
Обновляем прошивку коммутатора HUAWEI S5300
Читаем Upgrade Guide который должен идти в комплекте с прошивкой. (ниже рассмотрен пример с прошивкой R001C00SPC300)
Вкратце он содержит в себе — перечень требований к системе (совместимость версий, проверка используемой версии и т.д.), поведение системы во время обновления (перезагрузка, время загрузки прошивки по сети, по serial cable и т.п.)
1.1 Version Requirements Before Upgrade
Table 1-1 Version requirements before upgrade
|
Version |
Upgrade Instruction |
|
S5300: V100R001, and V100R002 |
It must be upgraded to V100R003, and then to V200R001C00SPC300. |
|
S5300: V100R003, V100R005C00, V100R005C00SPC100, V100R005C01, V100R005C01SPC100, V100R006C00SPC300 V100R006C00SPC500 V100R006C00SPC600 V100R006C00SPC800 V200R001C00SPC100 V200R001C00SPC200 S3300/S6300: V100R006C00SPC300 V100R006C00SPC500 V100R006C00SPC600 V100R006C00SPC800 V200R001C00SPC100 V200R001C00SPC200 |
It can be directly upgraded to V200R001C00SPC300. |
Дальше идет часть подготовки системы к апгрейду — список проверок (в столбец Result включил команды проверки)
Table 1-1 Upgrade preparation checklist
|
No. |
Item |
Check Point |
Result |
|---|---|---|---|
|
1 |
Check the system software version |
The system software version is between V100R005 and V200R001C00SPC300. |
display version |
|
2 |
Check the running status of the device |
The switch functions normally. |
display device |
|
3 |
Set up an environment for the upgrade |
An environment is set up for the upgrade as required. |
|
|
4 |
Obtain required software for the upgrade |
Software required for the upgrade is obtained. |
|
|
5 |
Back up the key data in the flash memory |
All the key data in the flash memory is backed up. |
|
|
6 |
Check the available space in the flash memory |
The space in the flash memory is sufficient for storing the system software package and other files such as patch files and configuration files. |
dir |
В зависимости от способа апгрейда необходимы разные версии прошивки — для обновления по сети — S5300EI-V200R001C00SPC300.cc
для обновления через BootRom — S5300-EI: S5300EI-bootrom.bin
Далее рассматривается пошаговое обновление для каждого из способов.
Нас интересует обновление через командную строку, S5300 в качестве фтп сервера:
Конфигурируем фтп сервер
<Quidway> system-view
[Quidway] ftp server enable
[Quidway] aaa
[Quidway-aaa] local-user ftpuser password cipher ftppwd
[Quidway-aaa] local-user ftpuser service-type ftp
[Quidway-aaa] local-user ftpuser ftp-directory flash:
[Quidway-aaa] return
Задаем IP адрес
An idle service interface is recommended. This example assumes that GigabitEthernet0/0/1 is used and the IP address is 1.1.1.1/24.
<Quidway> system-view
[Quidway]interface gigabitethernet0/0/1
[Quidway-GigabitEthernet0/0/1]port link-type access
[Quidway-GigabitEthernet0/0/1]quit
[Quidway] vlan 10
[Quidway-vlan10] port gigabitethernet0/0/1
[Quidway-vlan10] quit
[Quidway] interface vlanif 10
[Quidway-Vlanif10] ip address 1.1.1.1 24
[Quidway-Vlanif10] quit
[Quidway]
Заходим на фтп сервер
Assume that the Windows XP operating system is used.
Store the file to be uploaded in the specified directory (for example, D:>directory). Choose Start > Run. Enter cmd and press Enter. Enter FTP 1.1.1.1. Enter the user name at the user prompt and the password at the password prompt, and then press Enter. The following information is displayed:
D:>ftp 1.1.1.1
Connected to 1.1.1.1.
220 FTP service ready.
User (1.1.1.1:(none)): ftpuser
331 Password required for 1.
Password:
230 User logged in.
ftp>
Сохраняем текущую конфигурацию и прошивку на компьютер
ftp> binary
200 Type set to I.
ftp> get s5300-v100r006c00.cc
200 Port command okay.
150 Opening BINARY mode data connection for s5300-v100r006c00.cc.
226 Transfer complete.
ftp: 12472284 bytes received in 80.33Seconds 1350.65Kbytes/sec.
The preceding output indicates the configuration file has been transferred and you can find it in D:>.
ftp> get vrpcfg.zip
200 Port command okay.
150 Opening BINARY mode data connection for vrpcfg.zip
226 Transfer complete.
ftp: 589 bytes received in 0.01Seconds 60Kbytes/sec.
The preceding output indicates the configuration file has been transferred and you can find it in D:>.
ftp> get s5300sph001.pat
200 Port command okay.
150 Opening BINARY mode data connection for s5300sph001.pat.
226 Transfer complete.
ftp: 333436 bytes received in 0.33Seconds 1350.65Kbytes/sec.
The preceding output indicates the configuration file has been transferred and you can find it in D:>.
Загружаем прошивку на коммутатор
Run the put source-filename [ destination-filename ] command on the FTP client (PC) to upload the system software from the PC.
ftp> put D:S5300EI-V200R001C00SPC300.cc
200 Port command okay.
150 Opening BINARY mode data connection for S5300EI-V200R001C00SPC300.CC.
226 Transfer complete.
ftp: 14136780 bytes received in 87.33Seconds 1350.65Kbytes/sec.
ftp>
Загружаем новую конфигурацию на коммутатор (если конфигурация не должна быть изменена — пропускаем данный шаг).
ftp> put vrpcfgnew.zip
Определяем прошивку которая будет загружена при перезагрузке коммутатора.
<Quidway> startup system-software S5300EI-V200R001C00SPC300.cc
Warning: Basic BOOTROM will be upgraded. Continue?(Y/N)[N]: y
BOOTROM begin to be upgraded ! please wait for a moment
Info: BOOTROM UPGRADE OK
Succeeded in setting the software for booting system.
Обновляем BootROM (опционально InV100R003, V100R005, V100R006 and V200R001 the BootROM обновляется автоматически) Для обновлений других версий необходимо вручную обновить BootROM
<Quidway> system-view
[Quidway] upgrade basic-bootrom S5300EI-V200R001C00SPC300.cc
Warning: Basic BOOTROM will be upgraded. Continue?(Y/N)[N]: y
Upgrading BOOTROM,please wait for a moment
[Slot 0]:
Info: BOOTROM UPGRADE OK.
Перезагружаем коммутатор
<Quidway> reboot
Info: The system is now comparing the configuration, please wait.
Warning: All the configuration will be saved to the configuration file for the next startup:flash:/vrpcfg.zip, Continue?[Y/N]:y
Now saving the current configuration to the slot 0.
Info: Save the configuration successfully.
System will reboot! Continue?[Y/N]: y
Info: system is rebooting, please wait…
- Remove From My Forums
-
Question
-
User696604810 posted
problem
An unhandled exception occurred while processing the request.
InvalidOperationException: Unable to resolve service for type ‘TabDataAccess.Repositories.RepositoryTab`1[TabDataAccess.Dto.Employee]’ while attempting to activate ‘WebTabCore.Controllers.EmployeeController’.
Microsoft.Extensions.DependencyInjection.ActivatorUtilities.GetService(IServiceProvider sp, Type type, Type requiredBy, bool isDefaultParameterRequired)
-
InvalidOperationException: Unable to resolve service for type ‘TabDataAccess.Repositories.RepositoryTab`1[TabDataAccess.Dto.Employee]’ while attempting to activate ‘WebTabCore.Controllers.EmployeeController’.
- what i do as following
-
An unhandled exception occurred while processing the request. InvalidOperationException: Unable to resolve service for type 'TabDataAccess.Repositories.RepositoryTab`1[TabDataAccess.Dto.Employee]' while attempting to activate 'WebTabCore.Controllers.EmployeeController'. Microsoft.Extensions.DependencyInjection.ActivatorUtilities.GetService(IServiceProvider sp, Type type, Type requiredBy, bool isDefaultParameterRequired) InvalidOperationException: Unable to resolve service for type 'TabDataAccess.Repositories.RepositoryTab`1[TabDataAccess.Dto.Employee]' while attempting to activate 'WebTabCore.Controllers.EmployeeController'. what i do as following
what i do as below
-
public class Employee { public int EmployeeId { get; set; } public int BranchCode { get; set; } public string EmployeeName { get; set; } public int EmployeeAge { get; set; } } Repository public class RepositoryTab<T> : IrepositoryTab<T> where T : class { protected TabDbContext db { get; set; } private DbSet<T> dbSet; public RepositoryTab(TabDbContext Tabdb) { db = Tabdb; dbSet = db.Set<T>(); } public IEnumerable<T> GetAll() { return dbSet.ToList(); } } public interface IrepositoryTab<T> where T : class { IEnumerable<T> GetAll(); } configureservices services.AddDbContext<TabDbContext>(options => options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection"))); appsetting.json "ConnectionStrings": { "DefaultConnection": "Server=.\SQL2014;Database=ErpWeb;uid=sa;pwd=abc123;ConnectRetryCount=0;"why this exceptioh happen
-
Answers
-
User-1764593085 posted
Yes, as I have answered in your another post:
How to implement repository pattern in asp.net core 2.1
you need to use IrepositoryTab<Employee> in your controller
private readonly IRepository<Employee> _repository; public EmployeesController(IRepository<Employee> repository) { _repository = repository; }If you have resolved the problem, please mark the helpful answer or yourself to close the thread.
Thank you.
Xing
-
Marked as answer by
Thursday, October 7, 2021 12:00 AM
-
Marked as answer by