<ruby id="txhzx"><ins id="txhzx"><meter id="txhzx"></meter></ins></ruby>

    <noframes id="txhzx"><form id="txhzx"><nobr id="txhzx"><th id="txhzx"></th></nobr></form>

    <address id="txhzx"><nobr id="txhzx"><meter id="txhzx"></meter></nobr></address>
    <address id="txhzx"></address>

      <form id="txhzx"><listing id="txhzx"><meter id="txhzx"></meter></listing></form>

      <address id="txhzx"></address>
      <em id="txhzx"></em>

          <form id="txhzx"><nobr id="txhzx"><meter id="txhzx"></meter></nobr></form>

          <address id="txhzx"><nobr id="txhzx"><progress id="txhzx"></progress></nobr></address>

          <noframes id="txhzx"><address id="txhzx"></address>

            H3C S5560S_EI-CMW710-R6126P53

            Software name:H3C S5560S_EI-CMW710-R6126P53

            Release date:2019/4/19 14:25:41

            Download

            Software Description:

            H3C S5560S_EI-CMW710-R6126P53 Release Notes

            Contents

            Version information· 1

            Version number 1

            Version history· 1

            Hardware and software compatibility matrix· 1

            Upgrading restrictions and guidelines· 3

            Hardware feature updates· 3

            S5560S_EI-CMW710-R6126P53· 3

            S5560S_EI-CMW710-R6126P39· 3

            S5560S_EI-CMW710-R6126P38· 3

            S5560S_EI-CMW710-R6126P22· 3

            S5560S_EI-CMW710-R6126P20· 3

            S5560S_EI-CMW710-R6126P13· 4

            S5560S_EI-CMW710-R6126P12· 4

            S5560S_EI-CMW710-R6113· 4

            Software feature and command updates· 4

            MIB Updates· 4

            Operation Changes· 5

            Operation changes in R6126P53· 5

            Operation changes in R6126P39· 5

            Operation changes in R6126P38· 5

            Operation changes in R6126P22· 5

            Operation changes in R6126P20· 5

            Operation changes in R6126P13· 5

            Operation changes in R6126P12· 6

            Operation changes in R6113· 6

            Restrictions and cautions· 6

            Open problems and workarounds· 6

            List of resolved problems· 6

            Resolved problems in R6126P53· 6

            Resolved problems in R6126P39· 7

            Resolved problems in R6126P38· 8

            Resolved problems in R6126P22· 10

            Resolved problems in R6126P20· 11

            Resolved problems in R6126P13· 13

            Resolved problems in R6126P12· 14

            Resolved problems in R6113· 20

            Related documentation· 20

            Documentation set 20

            Obtaining Documentation· 20

            Technical support 20

            Appendix A Feature list 21

            Hardware features· 21

            Software features· 25

            Appendix B Upgrading software· 28

            System software file types· 28

            System startup process· 28

            Upgrade methods· 29

            Upgrading from the CLI 30

            Preparing for the upgrade· 30

            Downloading software images to the master switch· 31

            Upgrading the software images· 33

            Upgrading from the Boot menu· 35

            Prerequisites· 35

            Accessing the Boot menu· 36

            Accessing the extended Boot menu· 37

            Upgrading Comware images from the Boot menu· 39

            Upgrading Boot ROM from the Boot menu· 48

            Managing files from the Boot menu· 55

            Handling software upgrade failures· 58

             



            This document describes the features, restrictions and guidelines, open problems, and workarounds for version S5560S_EI-CMW710-R6126P53. Before you use this version in a live network, back up the configuration and test the version to avoid software upgrade affecting your live network.

            Use this documents listed in "Related documentation."

            Version information

            Version number

            H3C Comware Software, Version 7.1.070, Release 6126P53

            Note: You can see the version number with the command display version in any view. Please see Note.

            Version history

            Table 1 Version history

            Version number

            Last version

            Release Date

            Release type

            Remarks

            S5560S_EI-CMW710-R6126P53

            S5560S_EI-CMW710-R6126P39

            2019-04-01

            Release version

            New feature

            S5560S_EI-CMW710-R6126P39

            S5560S_EI-CMW710-R6126P38

            2019-01-25

            Release version

            New feature

            S5560S_EI-CMW710-R6126P38

            S5560S_EI-CMW710-R6126P22

            2018-12-20

            Release version

            New feature

            S5560S_EI-CMW710-R6126P22

            S5560S_EI-CMW710-R6126P20

            2018-10-19

            Release version

            New feature

            S5560S_EI-CMW710-R6126P20

            S5560S_EI-CMW710-R6126P13

            2018-08-31

            Release version

            Fixed bugs

            S5560S_EI-CMW710-R6126P13

            S5560S_EI-CMW710-R6126P12

            2018-05-15

            Release version

            Fixed bugs

            S5560S_EI-CMW710-R6126P12

            S5560S_EI-CMW710-R6113

            2018-04-16

            Release version

            Fixed bugs

            S5560S_EI-CMW710-R6113

            First release

            2017-05-22

            Release version

            First release

             

            Hardware and software compatibility matrix

            Table 2 Hardware and software compatibility matrix

            Item

            Specifications

            Product family

            S5560S-EI Series

            Hardware platform

            S5560S-28S-EI

            S5560S-52S-EI

            S5560S-28P-EI

            S5560S-52P-EI

            S5560S-28S-PWR-EI

            S5560S-52S-PWR-EI

            Minimum memory requirements

            512M

            Minimum Flash requirements

            256M

            Boot ROM version

            Version 126 or higher (Note: Use the display version command in any view to view the version information. Please see Note)

            Host software

            S5560S_EI-CMW710-R6126P53.ipe

            iMC version

            iMC BIMS 7.3 (E0501)

            iMC EAD 7.3 (E0502)

            iMC EIA 7.3 (E0503)

            iMC NTA 7.3E0502

            iMC PLAT 7.3 (E0605P06)

            iMC QoSM 7.3 (E0502)

            iMC RAM 7.3 (E0501)

            iMC SHM 7.3 (E0502)

            iNode version

            iNode PC 7.3 (E0504)

            Web version

            None

            Remarks

            None

             

            Display the system software and Boot ROM versions of S5560S-EI:

            <H3C>dis version                                                           

            H3C Comware Software, Version 7.1.070, Release 6126P53             ---------  

            Copyright (c) 2004-2019 New H3C Technologies Co., Ltd. All rights reserved.      

            H3C S5560S-52S-EI uptime is 0 weeks, 0 days, 0 hours, 7 minutes            

            Last reboot reason : Kernel abnormality reboot                                 

                                                                                           

            Boot image: flash:/s5560s_ei-cmw710-boot-r6126p53.bin                           

            Boot image version: 7.1.070, Release 6126P53                                      

              Compiled Jan 13 2017 16:00:00                                                

            System image: flash:/s5560s_ei-cmw710-system-r6126p53.bin                      

            System image version: 7.1.070, Release 6126P53                                    

              Compiled Sep 13 2017 16:00:00                                                

            Feature image(s) list:                                                         

              flash:/s5560s_ei-cmw710-freeradius-r6126p53.bin, version: 7.1.070             

                Compiled Apr 13 2017 16:00:00                                                                                                                                                                                  

             

                                                                                                                                                

            Slot 1:                                                                        

            Uptime is 0 weeks,0 days,0 hours,7 minutes                                     

            S5560S-52S-EI with 2 Processors                                            

            BOARD TYPE:         S5560S-52S-EI                                          

            DRAM:               512M bytes                                                 

            FLASH:              256M bytes                                                 

            PCB 1 Version:      VER.A                                                      

            Bootrom Version:    126                                             ------ 

            CPLD 1 Version:     001                                                        

            Release Version:    H3C S5560S-52S-EI-6126P53                             

            Patch Version  :    None                                                       

            Reboot Cause  :     ColdReboot                                       

            [SubSlot 0] 48GE+4SFP+      

            Upgrading restrictions and guidelines

            None.

            Hardware feature updates

            S5560S_EI-CMW710-R6126P53

            None.

            S5560S_EI-CMW710-R6126P39

            BIDI 40KM and 80KM Gigabit transceiver modules are supported.

            S5560S_EI-CMW710-R6126P38

            None.

            S5560S_EI-CMW710-R6126P22

            Support :

            S5560S-28S-PWR-EI

            S5560S-52S-PWR-EI

            S5560S_EI-CMW710-R6126P20

            None.

            S5560S_EI-CMW710-R6126P13

            None.

            S5560S_EI-CMW710-R6126P12

            None.

            S5560S_EI-CMW710-R6113

            First release.

            Software feature and command updates

            For more information about the software feature and command update history, see H3C S5560S_EI-CMW710-R6126P53 Release Notes (Software Feature Changes)

            MIB Updates

            Table 3 MIB updates

            Item

            MIB file

            Module

            Description

            S5560S_EI-CMW710-R6126P53

            New

            None

            None

            None

            Modified

            None

            None

            None

            S5560S_EI-CMW710-R6126P39

            New

            None

            None

            None

            Modified

            None

            None

            None

            S5560S_EI-CMW710-R6126P38

            New

            None

            None

            None

            Modified

            None

            None

            None

            S5560S_EI-CMW710-R6126P22

            New

            None

            None

            None

            Modified

            None

            None

            None

            S5560S_EI-CMW710-R6126P20

            New

            None

            None

            None

            Modified

            None

            None

            None

            S5560S_EI-CMW710-R6126P13

            New

            None

            None

            None

            Modified

            None

            None

            None

            S5560S_EI-CMW710-R6126P12

            New

            None

            None

            None

            Modified

            None

            None

            None

            S5560S_EI-CMW710-R6113

            New

            First release

            First release

            First release

            Modified

            First release

            First release

            First release

             

            Operation Changes

            Operation changes in R6126P53

            None.

            Operation changes in R6126P39

            None.

            Operation changes in R6126P38

            None.

            Operation changes in R6126P22

            None.

            Operation changes in R6126P20

            The priority order of referencing ACLs is modified for MQC, packet filter, and portal.

            Before modification: Portal > packet filter > MQC

            After modification: Packet filter > MQC > portal

            Operation changes in R6126P13

            None.

            Operation changes in R6126P12

            None.

            Operation changes in R6113

            First release.

            Restrictions and cautions

            Release 6126P53 must use BootROM 126 or a later version.

            Before upgrading the software, you must fully understand the software feature changes between different software versions in H3C S5560S_EI-CMW710-R6126P53 Release Notes (Software Feature Changes) and evaluate the impacts of the software upgrade on the live network. At the same time, for more information, you can refer to the related documentation sets..

            Open problems and workarounds

            201609030105

            ·            Symptom: Traffic cannot be forwarded between switches.

            ·            Condition: This symptom occurs if the switches receive packets whose source MAC addresses or destination MAC addresses are different from those already learned on the switches.

            ·            Workaround: Delete MAC address entries or broadcast packets to update MAC address entries.

            List of resolved problems

            Resolved problems in R6126P53

            1.       201902020022

            ·            Symptom: When the voice VLAN security mode is enabled and LLDP is enabled for automatic IP phone discovery, the switch drops the LLDPDUs that have voice VLAN tags, and automatic IP phone discovery does not take effect.

            ·            Condition: This symptom might occur if the voice VLAN security mode is enabled and LLDP is enabled for automatic IP phone discovery.

            2.       201903020106

            ·            Symptom: The switch does not issue an ACL to increase the priority of voice packets when receiving them.

            ·            Condition: This symptom occurs if the voice VLAN and LLDP for automatic IP phone discovery are both configured.

            3.       201903180826

            ·            Symptom: The system prompts that the IPv6 ACL referenced by a PBR policy does not exist.

            ·            Condition: This symptom occurs if the IPv6 ACL is created by specifying a name and is referenced by using the name.

            4.       201902140378

            ·            Symptom: The switch series cannot properly communicate with a device using the BCM chip through an established tunnel.

            ·            Condition: This symptom occurs if a tunnel is established between the switch series and a device using the BCM chip.

            5.       201902260316

            ·            Symptom: When the PoE power change triggers a threshold alarm, the On and Off information is displayed incorrectly in the PoE threshold alarm information.

            ·            Condition: This symptom occurs if the PoE threshold alarm function is configured and SNMP notification for PoE threshold alarms is enabled.

            Resolved problems in R6126P39

            1.       201901250098

            ·            Symptom: On an IRF fabric, execution of the voice-vlan enable command fails for lack of resources.

            ·            Condition: This symptom might occur if the value obtained by subtracting the number of OUI addresses from the product of the number of voice VLAN-enabled interfaces and the number of IRF member devices is larger than 56.

            2.       201901250420

            ·            Symptom: A PBR policy does not take effect on an interface if link status change occurs on another interface which is the next hop of a large number of routes.

            ·            Condition: This symptom might occur if link status change occurs on an interface which is the next hop of a large number of routes.

            3.       201901250337

            ·            Symptom: On an IRF fabric, the MAC addresses obtained by using SNMP are inconsistent with those displayed by using the display mac-address command.

            ·            Condition: This symptom might occur if the following conditions exist on an IRF fabric:

            ?  No multichassis aggregation group is configured.

            ?  MAC address synchronization is disabled.

            ?  No inter-slot traffic exists.

            4.       201809110615

            ·            Symptom: An interface leaves its voice VLAN and cannot join the voice VLAN again.

            ·            Condition: This symptom occurs if the following operations are performed:

            a.    On an IRF fabric, LLDP is enabled and voice VLAN is configured on an interface of a subordinate member device, and the interface is connected to a voice device supporting LLDP and CDP.

            b.   Establish or disconnect the LLDP neighbor relationship on the subordinate IRF member device.

            Resolved problems in R6126P38

            1.       201806150108

            ·            Symptom: The rate information of a 100-Mbps port is displayed as 1000 Mbps.

            ·            Condition: This symptom occurs if you execute the link-delay command on the port and set the rate of the peer port to 1000 Mbps.

            2.       201812200151

            ·            Symptom: After a PoE device is powered off and then restarted, the PoE device cannot supply power properly.

            ·            Condition: This symptom occurs if the PoE device is installed with the PSE module LSPPSE24A, LSPPSE48A, LSPPSE16A, or LSPPSE8A.

            3.       201811080865

            ·            Symptom: The switch acting as a DHCP client cannot obtain IP addresses from an H3C DHCP server.

            ·            Condition: This symptom occurs if the DHCP-OFFER message sent by the DHCP server uses a unicast MAC address as the destination MAC address.

            4.       201811260764

            ·            Symptom: An access node is automated and connected to a leaf node through two uplinks and the two links are automatically aggregated. However, the topology shows that there are multiple links between the access node and the leaf node, and there is no aggregate interface in the interface group of each node.

            ·            Condition: This symptom occurs if an access node is automated and connected to a leaf node through two uplinks and the two links are automatically aggregated.

            5.       201810120764

            ·            Symptom: After a two-chassis IRF fabric reboots, MAC authentication users fail authentication on a port of the subordinate member.

            ·            Condition: This symptom might occur if the following conditions exist:

            c.    The IRF member devices each have a port that is working in the userlogin-secure-or-mac port security mode.

            d.   The running configuration is saved and the .mdb configuration file is deleted before the IRF fabric is rebooted.

            e.    MAC authentication users perform authentication on the port in userlogin-secure-or-mac mode of the subordinate member after the IRF fabric reboots.

            6.       201810120762

            ·            Symptom: After the switch upgrades to the current software version and loads a text configuration file, command output shows that port security configuration becomes incorrect.

            ·            Condition: This symptom might occur if the running configuration is saved after port security is configured and then the switch upgrades to the current software version.

            7.       201809190880

            ·            Symptom: An IP phone attached to the switch cannot communicate with the gateway.

            ·            Condition: This symptom might occur if the port which the IP phone is attached to is shut down and then brought up after the IP phone joins a voice VLAN.

            8.       201809180169

            ·            Symptom: The following symptoms exist after the switch is rebooted:

            ?  PoE-capable ports cannot supply power.

            ?  In the output from the display environment command, the temperature of the last sensor is higher than the shutdown temperature threshold or displayed as --.

            ?  The switch outputs the over temperature alarm.

            ?  The SYS LED is red.

            ·            Condition: This symptom might occur if the power supply priority of multiple ports is set to critical and the switch is powered off before rebooted.

            9.       201809150233

            ·            Symptom: The following symptoms exist after the switch is rebooted or has been running for a period of time:

            ?  PoE-capable ports cannot supply power.

            ?  In the output from the display environment command, the temperature of the last sensor is higher than the shutdown temperature threshold or displayed as --.

            ?  The switch outputs the over temperature alarm.

            ?  The SYS LED is red.

            ·            Condition: This symptom might occur if the switch is powered off before rebooted or has been running for a period of time.

            10.     201809140213

            ·            Symptom: After the switch starts up, PoE-capable ports cannot supply power, and the SYS LED becomes red.

            ·            Condition: This symptom might occur if the switch starts up correctly.

            11.     201808310515

            ·            Symptom: When the switch has multiple ECMP routes to a destination, the MAC address entries for the next hops are incorrect.

            ·            Condition: This symptom might occur if the switch has multiple ECMP routes to a destination.

            12.     201810290223

            ·            Symptom: Telnet login fails when the CPU is attacked by packets.

            ·            Condition: This symptom might occur if the CPU is attacked by packets.

            13.     201810220044

            ·            Symptom: The memory is exhausted when Ethernet interfaces are repeatedly shut down and brought up.

            ·            Condition: This symptom might occur if Ethernet interfaces are repeatedly shut down and brought up.

            14.     201809210670

            ·            Symptom: The port security process does not respond.

            ·            Condition: This symptom might occur if LLDP requests user information from the port security module when the disableport-temporarily intrusion protection action is triggered on a port configured with port security.

            15.     201804040436

            ·            Symptom: After an IRF fabric starts up with empty configuration, ARP packets that should be forwarded are sent to the CPU.

            ·            Condition: This symptom might occur if an IRF fabric starts up with empty configuration.

            ·            Workaround: None.

            16.     201810120112

            ·            Symptom: When the switch is frequently accessed through SNMP, resources of the switch are exhausted and SNMP access fails.

            ·            Condition: This symptom might occur if the switch is frequently accessed through SNMP.

            17.     201810130049

            ·            Symptom: The DHCP server stores DHCP client startup files, and the switch acts as a DHCP client. When the switch starts up with empty configuration and then connects to the DHCP server, an error message is output.

            ·            Condition: This symptom might occur if the following conditions exist:

            ?  The DHCP server stores DHCP client startup files.

            ?  The switch acts as a DHCP client, and it starts up with empty configuration.

            Resolved problems in R6126P22

            None.

            Resolved problems in R6126P20

            1.       201808230761

            ·            Symptom: In the display environment command output, the temperature information for the last sensor is incorrect.

            ·            Condition: This symptom occurs if the display environment command is used to display information about all temperature sensors on the device.

            2.       201807310196

            ·            Symptom: The device reboots unexpectedly.

            ·            Condition: This symptom occurs if the following operations are performed:

            ?  The VLAN interface for the super VLAN is bound to a VPN instance.

            ?  The super VLAN is deleted after a new sub VLAN is associated with the super VLAN.

            3.       201807310180

            ·            Symptom: Port isolation does not take effect.

            ·            Condition: This symptom occurs if the following conditions exist:

            ?  Two interfaces in the same VLAN are assigned to the same port isolation group.

            ?  One of the two interface receives MLD packets.

            ?  MLD snooping is enabled for another VLAN.

            4.       201807310170

            ·            Symptom: If you configure the speed auto or undo speed command on a 10-GE fiber port configured with the speed 1000 command, the system prompts that the operation failed.

            ·            Condition: This symptom occurs if you configure the speed auto or undo speed command on a 10-GE fiber port configured with the speed 1000 command.

            5.       201807310159

            ·            Symptom: In a Device 1-Gateway-Device 2 network, when multicast NA packets arrive at Device 2, Device 2 forwards the packets back to the gateway. As a result, the ND entries on the gateway move, and Device 1 cannot ping the gateway intermittently.

            ·            Condition: This symptom occurs if Device 1 sends multicast NA packets in a Device 1-Gateway-Device 2 network.

            6.       201807190265

            ·            Symptom: After the device runs for a period of time, outgoing traffic of an interface on the device cannot be forwarded.

            ·            Condition: This symptom occurs if the following conditions exist:

            ?  A GE interface on the device is configured to autonegotiate the speed and duplex mode.

            ?  A peer interface is manually configured with the speed of 100 Mbps and the full duplex mode.

            ?  The two interfaces are directly connected.

            7.       201808010060

            ·            Symptom: PBR configured on a VLAN interface does not take effect on Layer 3 traffic with the destination MAC address as the virtual MAC address of a VRRP group's virtual IP address, and cannot forward such traffic according to the specified next hop.

            ·            Condition: This symptom occurs if PBR is configured on a VLAN interface configured with a VRRP group.

            8.       201808010055

            ·            Symptom: After a PBR policy is configured on a Layer 3 interface, the interface cannot ping the gateway.

            ·            Condition: This symptom occurs if the Layer 3 interface is configured with an IP address that matches a criterion with an empty forwarding action in the PBR policy.

            9.       201807310211

            ·            Symptom: On the DHCP-enabled switch, MAC authentication is enabled on a port. When a user that has already obtained an IP address passes MAC authentication, the switch assigns the user an authorization VLAN but does not assign the user a new IP address.

            ·            Condition: This symptom occurs if a user that has already obtained an IP address passes MAC authentication.

            10.     201807310199

            ·            Symptom: Some portal-free endpoints cannot ping the external network.

            ·            Condition: This symptom occurs if the portal free-rule command is used to configure an IP-based portal-free rule that specifies IP addresses with non-all-Fs masks as portal-free.

            11.     201807310111、201807310152

            ·            Symptom: The downlink physical interface does not learn MAC address entries. The up/down events of physical interfaces in the uplink aggregate interface are not reported.

            ·            Condition: This symptom occurs if the following conditions exist:

            ?  The MAC address learning limit is configured on the downlink physical interface.

            ?  MAC addresses frequently move between the uplink aggregate interface and the downlink physical interface.

            ?  The aggregate interface is repeatedly shut down and brought up.

            12.     201807310144

            ·            Symptom: Failed to obtain the value of the dot1qTpFdbPort node for VLAN 0.

            ·            Condition: This symptom occurs when you walk on nodes.

            13.     201807310130

            ·            Symptom: When the device acts as a DHCP server and has the EAD assistant feature enabled, PCs attached to the device cannot obtain IP addresses that the DHCP server allocates.

            ·            Condition: This symptom occurs if the following operations are performed:

            ?  Configure 802.1X on the device, and execute the dot1x ead-assistant enable command in system view to enable the EAD assistant feature.

            ?  Configure DHCP Server on the device.

            14.     201807310125

            ·            Symptom: An endpoint cannot ping the gateway.

            ·            Condition: This symptom occurs if the following conditions exist:

            ?  The endpoint is connected to the gateway through the device.

            ?  The interface connecting the device to the endpoint has the ARP gateway protection feature enabled, but the corresponding VLAN interface is not configured.

            15.     201807310117

            ·            Symptom: The device drops Layer 2 multicast data packets with TTL as 1.

            ·            Condition: This symptom occurs if the igmp-snooping drop-unknown command is configured for a VLAN.

            16.     201807310164

            ·            Symptom: The CLI is stuck when commands are executed.

            ·            Condition: This symptom occurs when a DHCP snooping trusted port receives DHCP BOOTP attack packets on an IRF fabric.

            Resolved problems in R6126P13

            1.       201705060208

            ·            Symptom: A 100-Mbps interface is missing.

            ·            Condition: This symptom occurs if a 100-Mbps interface is configured as the reflector port of a mirroring group.

            2.       201804270329

            ·            Symptom: After you use the undo mac-vlan all command to delete all MAC-to-VLAN entries, some MAC-to-VLAN entries remain. The system prompts an operation failure if you execute the undo mac-vlan command to delete the specified MAC-to-VLAN entry.

            ·            Condition: This symptom occurs if MAC-based VLAN is configured on a 52-port device that is not configured with IRF.

            3.       201805020063

            ·            Symptom: Packets cannot be forwarded through an aggregation group. A downlink device cannot ping an uplink device.

            ·            Condition: This symptom occurs if the following conditions exist on an IRF fabric:

            ?  The downlink link is an aggregate link.

            ?  Port isolation is configured on the corresponding aggregate interface.

            Resolved problems in R6126P12

            1.       201712050364

            ·            Symptom: The OSPF neighbor state repeatedly flaps and passing OSPF packets cannot be transparently transmitted.

            ·            Condition: This symptom occurs if the following conditions exist:

            ?  When a large number of data packets need to be sent to the CPU, these packets are assigned to the same queue as OSPF unicast protocol packets with the TTL being not 1.

            ?  The device receives passing OSPF packets.

            2.       201708010087

            ·            Symptom: An MLD report received on an aggregate interface is sent out the aggregate interface by software forwarding.

            ·            Condition: This symptom occurs if the following conditions exist:

            ?  The device receives an MLD report on an aggregate interface..

            ?  MLD snooping is not enabled for the VLAN of the report.

            ?  MLD snooping is enabled for the other VLANs.

            3.       201801160564

            ·            Symptom: An MLD report received on a downlink aggregate interface is sent out of the aggregate interface rather than forwarded to the uplink device.

            ·            Condition: This symptom occurs if the following conditions exist:

            ?  The device has two chips.

            ?  The device receives an MLD report on an aggregate interface with member ports on chip 1.

            ?  MLD snooping is not enabled for the VLAN of the report.

            ?  MLD snooping is enabled for the other VLANs.

            4.       201712210145

            ·            Symptom: When a large number of IPv6 data packets are sent to the CPU, NS multicast packets cannot be properly sent to the CPU.

            ·            Condition: This symptom occurs if a large number of IPv6 packets destined for the IP address of the local device are received.

            5.       201712090381

            ·            Symptom: After an aggregate interface of the device receives an IGMP report from a downlink device, the report is forwarded to a downlink Layer 2 device through the aggregate interface. As a result, the Layer 2 device adds the uplink interface to the outgoing interface list of the multicast forwarding table.

            ·            Condition: This symptom occurs if the following conditions exist:

            ?  The device receives an IGMP report on an aggregate interface.

            ?  IGMP snooping is not enabled for the VLAN of the report.

            ?  IGMP snooping is enabled for the other VLANs.

            6.       201803010122

            ·            Symptom: The following problems occur:

            a.    When an interface receives a packet matching a MAC-to-VLAN entry, the interface does not learn the MAC address of the packet, and drops the packet.

            b.   The dynamic MAC-based VLAN assignment feature does not take effect. An interface cannot automatically join the corresponding VLAN.

            ·            Condition: This symptom occurs if manual voice VLAN assignment mode and dynamic MAC-based VLAN assignment are enabled.

            7.       201803080385

            ·            Symptom: After SSH/Telnet packets are forwarded at Layer 3 by the device, SSH/Telnet operates improperly. 

            ·            Condition: This symptom occurs if SSH/Telnet is enabled on the device and the device forwards the SSH/Telnet packets at Layer 3.

            8.       201801230564

            ·            Symptom: Video conferences freeze because traffic bursts exhaust shared buffer resources and cause traffic loss.

            ·            Condition: This symptom might occur if traffic bursts exhaust shared buffer resources and cause traffic loss.

            9.       201802080372

            ·            Symptom: The device reboots unexpectedly.

            ·            Condition: This symptom occurs if the following conditions exist:

            ?  The device has learned a large number of MAC address entries.

            ?  An interface is added to an aggregation group. The member ports of the aggregation group are repeatedly shut down and brought up.

            10.     201802080165

            ·            Symptom: A maximum of 32 sub-VLANs can be associated with a super VLAN.

            ·            Condition: This symptom occurs if the following operations are performed:

            a.    Create a VLAN interface for a VLAN, and configure an IP address for the VLAN interface.

            b.   Configure the VLAN as a super VLAN.

            c.    Use the subvlan command to associate sub-VLANs with the super VLAN.

            11.     201802100195

            ·            Symptom: QinQ-related configurations on a port are lost.

            ·            Condition: This symptom occurs if master/subordinate switchover occurs to an IRF fabric.

            12.     201801081024

            ·            Symptom: The switch cannot ping the destinations in two static routes.

            ·            Condition: This symptom might occur if the outgoing interface to the next hop in each static route is shut down and then brought up.

            13.     201801270451

            ·            Symptom: The following problems occur:

            ?  Interfaces on the device cannot come up properly after cables are inserted.

            ?  The CLI is stuck when commands are executed.

            ?  The MAC address entry information cannot be obtained in any method.

            ·            Condition: This symptom occurs if the following conditions exist:

            a.    In an STP network, the device has learned a large number of MAC address entries.

            b.   The device frequently receives TC-BPDUs, and synchronously updates the MAC address entries.

            c.    The display mac-address command is executed to display the MAC address entries of the specified VLAN.

            14.     201707220206

            ·            Symptom: The local device cannot be pinged.

            ·            Condition: This symptom occurs if a large number of IPV6_ND_PASS packets are sent to the CPU.

            15.     201712200919

            ·            Symptom: In the following cases, the MAC addresses corresponding to ARP entries are inconsistent.

            ?  Execute the display mac-address and display arp commands in any view to view the MAC addresses corresponding to ARP entries.

            ?  Execute the debug ipv4-drv show arp and debug ipv4-drv show arp commands in probe view to view the MAC addresses corresponding to static ARP entries issued by the device.

            ·            Condition: This symptom occurs if either of the following conditions exist:

            ?  A static route exists. The link directly connected to a valid next hop of the static route flaps.

            ?  The device configured with static routes is rebooted.

            16.     201712090114

            ·            Symptom: If you first configure the IPv6 default route and then configure the ipv6 unreachables enable command, the default route is modified. As a result, the Layer 3 packets with the destination addresses unreachable are sent to the CPU for processing rather than forwarded according to the default route.

            ·            Condition: This symptom occurs if you configure IPv6 static routes first and then configure the ipv6 unreachables enable command.

            17.     201711220080

            ·            Symptom: Flow mirroring does not take effect.

            ·            Condition: This symptom occurs if flow mirroring is configured through a QoS policy and voice VLAN is enabled on the interface where the QoS policy takes effect.

            18.     201711210817

            ·            Symptom: The device cannot learn some MAC addresses.

            ·            Condition: This symptom occurs if the following conditions exist:

            ?  An interface is enabled with voice VLAN and configured with the MAC learning limit.

            ?  The interface goes down and then comes up.

            19.     201711130845

            ·            Symptom: When an interface restores to the up state, intrusion protection is triggered exceptionally.

            ·            Condition: This symptom occurs if the following events occur:

            a.    An interface with port security enabled goes down, and the secure MAC address entry ages out.

            b.   The interface restores to the up state.

            20.     201711020708

            ·            Symptom: The mac-vlan mac-address command fails to configure a MAC-VLAN entry.

            ·            Condition: This symptom occurs if the mac-vlan mac-address command is executed on a device with the specific configurations.

            21.     201709220167

            ·            Symptom: The MAC address table information is incorrectly displayed, and the CPU usage reaches 100%.

            ·            Condition: This symptom occurs if a large number of MAC address entries are added or deleted. 

            22.     201709210407

            ·            Symptom: The HWTACACS server configuration is not deleted as expected, and processes that use the server configuration get abnormal when the switch rolls back configuration.

            ·            Condition: This symptom occurs if the following conditions exist:

            a.    Multiple authentication servers, authorization servers, or accounting servers are configured in an HWTACACS scheme.

            b.   The servers of the same type have the same VPN instance and IP address settings but different port number settings.

            23.     201709050143

            ·            Symptom: The secure MAC address bound to port 1 does not age out according to the secure MAC aging timer after the user moves from port 1 to port 2.

            ·            Condition: This symptom occurs if you enable port security on both ports and set the secure MAC aging timer.

            24.     201708140180

            ·            Symptom: The switch reboots when memory resources are insufficient.

            ·            Condition: This symptom might occur if memory resources are insufficient.

            25.     201709050334

            ·            Symptom: In the Appendix E environment outlined in RFC 2328, OSPF performs incorrect route calculation.

            ·            Condition: This symptom occurs if OSPF redistributes multiple routes with the same IP address but different masks or OSPF removes such redistributed routes.

            26.     201709040837

            ·            Symptom: A user fails to log in through MAC authentication after the switch reboots.

            ·            Condition: This symptom occurs if the following operations are performed:

            a.    Enable port security and set the port security mode of the interface to one of the following options:

            -       macAddressWithRadius.

            -       macAddressOrUserLoginSecure.

            -       macAddressElseUserLoginSecure.

            -       macAddressOrUserLoginSecureExt.

            -       macAddressElseUserLoginSecureExt.

            b.   Save the configuration and delete the binary (.mdb) configuration file.

            c.    Reboot the switch.

            27.     201709040821

            ·            Symptom: An 802.1X user that passes authentication on an interface is assigned an IP address in the guest VLAN, Auth-Fail VLAN, or critical VLAN instead of an IP address in the authorization VLAN.

            ·            Condition: This symptom might occur if the following conditions exist:

            ?  Both 802.1X and DHCP are enabled.

            ?  An 802.1X guest VLAN, Auth-Fail VLAN, or critical VLAN is configured on the interface.

            ?  The server successfully assigns an authorization VLAN.

            28.     201709040809

            ·            Symptom: 802.1X authentication fails on an interface.

            ·            Condition: This symptom might occur if the following operations are performed:

            ?  Enable 802.1X and specify the port-based access control method on an interface.

            ?  Set the username request timeout timer by using the dot1x timer tx-period tx-period-value command.

            29.     201709040788

            ·            Symptom: The CLI does not respond in a console port session for a long time.

            ·            Condition: This symptom occurs if the following sequence of events occurs:

            a.    Enable scheme authentication and command accounting for the console port.

            b.   Enable STP in interface range view.

            30.     201709040766

            ·            Symptom: A user fails both 802.1X authentication and MAC authentication on an interface.

            ·            Condition: This symptom occurs if the following sequence of events occurs:

            a.    Port security is enabled and the port security mode is set to userlogin-secure-or-mac-ext on an interface.

            b.   The user passes MAC authentication after failing 802.1X authentication.

            c.    Execute the shutdown and undo shutdown commands on the interface.

            d.   The user reinitiates authentication.

            31.     201706290743

            ·            Symptom: A fiber port goes down, and it cannot come up or forward traffic.

            ·            Condition: This symptom occurs if 1000-Mbps transceiver modules with a transmission distance of 40 km or longer and an optical fiber are used to connect fiber ports without PHYs, and the optical fiber is unplugged and then plugged.

            32.     201707040599

            ·            Symptom: A user might fail authentication on an interface after the interface is shut down and then brought up.

            ·            Condition: This symptom might occur if both MAC authentication and 802.1X authentication are configured on the interface and authorization ACLs and authorization user profiles are configured on the switch.

            33.     201706090032

            ·            Symptom: A user in the 802.1X guest VLAN, critical VLAN, or Auth-Fail VLAN might fail to update its IP address after it passes 802.1X authentication and is assigned a VLAN.

            ·            Condition: This symptom might occur if the user in the 802.1X guest VLAN, critical VLAN, or Auth-Fail VLAN triggers 802.1X authentication and the user is assigned a VLAN after passing 802.1X authentication.

            34.     201706090030

            ·            Symptom: A user might fail 802.1X authentication on an interface.

            ·            Condition: This symptom might occur if the following conditions exist:

            a.    An 802.1X guest VLAN, critical VLAN, or Auth-fail VLAN is configured on the interface.

            b.   The username request timeout timer is set to a small value by using the dot1x timer tx-period command.

            c.    The 802.1X client interacts with the authentication server for a long time to complete 802.1X authentication.

            35.     201707040813

            ·            Symptom: An IRF physical interface cannot be bound to an IRF port in the Web interface.

            ·            Condition: This symptom might occur if IRF is configured in the Web interface.

            Resolved problems in R6113

            First release.

            Related documentation

            Documentation set

            ·            H3C S5560S-EI & S5130S-HI Switch Series Installation Quick Start

            ·            H3C S5560S-EI & S5130S-HI Switch Series Installation Guide

            ·            H3C PSR150-A & PSR150-D Series Power Modules User Manual

            ·            H3C PSR75-12A Power Module User Manual

            ·            H3C S5560S-EI Switch Series Configuration Guides-R612x

            ·            H3C S5560S-EI Switch Series Command References-R612x

            Obtaining Documentation

            To obtain the related documents from the H3C website at www.gsaguelph.com.hk:

            2.       Click http://www.gsaguelph.com.hk/Technical_Documents.

            3.       Choose the desired product category and model.

            Technical support

            service@h3c.com

            http://www.gsaguelph.com.hk


             

            Appendix A Feature list

            Hardware features

            Table 2 Technical specifications for non-PoE switches of the S5560S-EI series

            Item

            S5560S-28S-EI

            S5560S-52S-EI

            S5560S-28P-EI

            S5560S-52P-EI

            Dimensions (H × W × D)

            43.6 × 440 × 360 mm (1.72 × 17.32 × 14.17 in)

            43.6 × 440 × 360 mm (1.72 × 17.32 × 14.17 in)

            43.6 × 440 × 360 mm (1.72 × 17.32 × 14.17 in)

            43.6 × 440 × 360 mm (1.72 × 17.32 × 14.17 in)

            Weight

            ≤ 8 kg (17.64 lb)

            ≤ 8.5 kg (18.74 lb)

            ≤ 8 kg (17.64 lb)

            ≤ 8.5 kg (18.74 lb)

            Console port

            ·          1 × Micro USB console port

            ·          1 × serial console port

            Only the Micro USB console port is available when you connect both ports.

            USB port

            1

            Management Ethernet port

            1

            10/100/1000BASE-T autosensing Ethernet port

            24 (The rightmost eight ports and their corresponding SFP ports form combo interfaces.)

            48

            24 (The rightmost eight ports and their corresponding SFP ports form combo interfaces.)

            48

            SFP port

            12 (The leftmost eight ports and their corresponding 10/100/1000BASE-T autosensing Ethernet ports form combo interfaces.)

            4

            8 (Each and its corresponding 10/100/1000BASE-T autosensing Ethernet port form a combo interface.)

            N/A

            SFP+ port

            N/A

            N/A

            4

            4

            Power module slot

            2, on the rear panel

            Input voltage

            PSR75-12A:

            ·          Rated voltage:

            ?  100 VAC to 240 VAC @ 50 or 60 Hz

            ?  240 VDC

            ·          Max voltage:

            ?  90 VAC to 290 VAC @ 47 to 63 Hz

            ?  180 VDC to 320 VDC

            PSR150-A1:

            ·          Rated voltage: 100 VAC to 240 VAC @ 50 or 60 Hz

            ·          Max voltage: 90 VAC to 264 VAC @ 47 to 63 Hz

            PSR150-D1:

            ·          Rated voltage: –48 VDC to –60 VDC

            ·          Max voltage: –36 VDC to –72 VDC

            DC power source for the PSR150-D1 power module: –48 VDC power source in the equipment room or an RPS (H3C RPS800-A or RPS1600-A)

            Minimum power consumption

            ·          Single PSR75-12A input: 12 W

            ·          Single PSR150-A1 input: 15 W

            ·          Single PSR150-D1 input: 15 W

            ·          Dual PSR75-12A inputs: 13 W

            ·          Dual PSR150-A1 inputs: 20 W

            ·          Dual PSR150-D1 inputs: 21 W

            ·          Single PSR75-12A input: 21 W

            ·          Single PSR150-A1 input: 24 W

            ·          Single PSR150-D1 input: 25 W

            ·          Dual PSR75-12A inputs: 23 W

            ·          Dual PSR150-A1 inputs: 29 W

            ·          Dual PSR150-D1 inputs: 30 W

            ·          Single PSR75-12A input: 12 W

            ·          Single PSR150-A1 input: 16 W

            ·          Single PSR150-D1 input: 15 W

            ·          Dual PSR75-12A inputs: 14 W

            ·          Dual PSR150-A1 inputs: 22 W

            ·          Dual PSR150-D1 inputs: 21 W

            ·          Single PSR75-12A input: 21 W

            ·          Single PSR150-A1 input: 25 W

            ·          Single PSR150-D1 input: 26 W

            ·          Dual PSR75-12A inputs: 24 W

            ·          Dual PSR150-A1 inputs: 30 W

            ·          Dual PSR150-D1 inputs: 32 W

            Maximum power consumption

            ·          Single PSR75-12A input: 29 W

            ·          Single PSR150-A1 input: 32 W

            ·          Single PSR150-D1 input: 35 W

            ·          Dual PSR75-12A inputs: 32 W

            ·          Dual PSR150-A1 inputs: 39 W

            ·          Dual PSR150-D1 inputs: 44 W

            ·          Single PSR75-12A input: 44 W

            ·          Single PSR150-A1 input: 46 W

            ·          Single PSR150-D1 input: 57 W

            ·          Dual PSR75-12A inputs: 46 W

            ·          Dual PSR150-A1 inputs: 52 W

            ·          Dual PSR150-D1 inputs: 59 W

            ·          Single PSR75-12A input: 33 W

            ·          Single PSR150-A1 input: 35 W

            ·          Single PSR150-D1 input: 40 W

            ·          Dual PSR75-12A inputs: 36 W

            ·          Dual PSR150-A1 inputs: 42 W

            ·          Dual PSR150-D1 inputs: 47 W

            ·          Single PSR75-12A input: 47 W

            ·          Single PSR150-A1 input: 49 W

            ·          Single PSR150-D1 input: 58 W

            ·          Dual PSR75-12A inputs: 49 W

            ·          Dual PSR150-A1 inputs: 56 W

            ·          Dual PSR150-D1 inputs: 60 W

            Chassis leakage current compliance

            UL60950-1/EN60950-1/IEC60950-1/GB4943

            Melting current of power module fuse

            ·          PSR75-12A: 3.15 A, 250 V

            ·          PSR150-A1: 6.3 A, 250 V

            ·          PSR150-D1: 8 A, 250 V

            Operating temperature

            0°C to 45°C (32°F to 113°F)

            Relative humidity

            5% to 95%, noncondensing

            Fire resistance compliance

            UL60950-1/EN60950-1/IEC60950-1/GB4943

            Table 3 Technical specifications for PoE switches of the S5560S-EI series

            Item

            S5560S-28S-PWR-EI

            S5560S-52S-PWR-EI

            Dimensions (H × W × D)

            43.6 × 440 × 460 mm (1.72 × 17.32 × 18.11 in)

            43.6 × 440 × 460 mm (1.72 × 17.32 ×18.11 in)

            Weight

            ≤ 8.5 kg (18.74 lb)

            ≤ 9.5 kg (20.94 lb)

            Console port

            ·          1 × Micro USB console port

            ·          1 × serial console port

            Only the Micro USB console port is available when you connect both ports.

            USB port

            1

            1

            Management Ethernet port

            1

            1

            10/100/1000BASE-T autosensing Ethernet port

            24 (The rightmost four ports and their corresponding SFP ports form combo interfaces.)

            48

            SFP port

            4 (The four ports and their corresponding 10/100/1000BASE-T autosensing Ethernet ports form combo interfaces.)

            N/A

            SFP+ port

            4

            Power module slot

            2, on the rear panel

            Input voltage

            PSR180-56A:

            ·          Rated voltage:

            ?  100 VAC to 240 VAC @ 50 or 60 Hz

            ?  240 VDC

            ·          Max voltage:

            ?  85 VAC to 290 VAC @ 47 to 63 Hz

            ?  180 VDC to 320 VDC

            PSR360-56A/PSR720-56A:

            ·          Rated voltage: 100 VAC to 240 VAC @ 50 or 60 Hz

            ·          Max voltage: 90 VAC to 264 VAC @ 47 to 63 Hz

            PSR1110-56A:

            ·          Rated voltage: 115 VAC to 240 VAC @ 50 or 60 Hz

            ·          Max voltage: 102.5 VAC to 264 VAC @ 47 to 63 Hz

            PSR560-56D:

            ·          Rated voltage: –48 VDC to –60 VDC

            ·          Max voltage: –36 VDC to –72 VDC

            DC power source: –48 VDC power source in the equipment room or an RPS (H3C RPS1600-A)

            PoE power capacity

            Depends on the power module configurations. For more information, see Table 4.

            Power consumption (static)

            27 W

            37 W

            Power consumption (max)

            920 W

            1854 W

            Chassis leakage current compliance

            UL60950-1/EN60950-1/IEC60950-1/GB4943

            Melting current of power module fuse

            ·          PSR180-56A:

            ?  AC: 6.3 A, 500 V

            ?  DC: 6.3 A, 400 V

            ·          PSR360-56A: 6.3 A, 250 V

            ·          PSR560-56D: 30 A, 75 V

            ·          PSR720-56A/PSR1110-56A: 15 A, 250 V

            Operating temperature

            0°C to 45°C (32°F to 113°F)

            Relative humidity

            5% to 95%, noncondensing

            Fire resistance compliance

            UL60950-1/EN60950-1/IEC60950-1/GB4943

            Table 4 PoE power capacity of the S5560S-28S-PWR-EI and S5560S-52S-PWR-EI switches

            Power module configuration

            S5560S-28S-PWR-EI

            S5560S-52S-PWR-EI

            Total PoE power capacity

            Max PoE power capacity per port

            Total PoE power capacity

            Max PoE power capacity per port

            2 × PSR1110-56A

            810 W

            30 W

            1680 W

            30 W

            1 × PSR1110-56A and 1 × PSR720-56A

            810 W

            30 W

            1680 W

            30 W

            1 × PSR1110-56A and 1 × PSR560-56D

            810 W

            30 W

            1560 W

            30 W

            1 × PSR1110-56A and 1 × PSR360-56A

            810 W

            30 W

            1320 W

            30 W

            2 × PSR720-56A

            810 W

            30 W

            1320 W

            30 W

            1 × PSR720-56A and 1 × PSR560-56D

            810 W

            30 W

            1140 W

            30 W

            2 × PSR560-56D

            810 W

            30 W

            900 W

            30 W

            1 × PSR720-56A and 1 × PSR360-56A

            810 W

            30 W

            900 W

            30 W

            1 × PSR1110-56A

            810 W

            30 W

            900 W

            30 W

            1 × PSR560-56D and 1 × PSR360-56A

            810 W

            30 W

            810 W

            30 W

            1 × PSR720-56A

            600 W

            30 W

            600 W

            30 W

            2 × PSR360-56A

            600 W

            30 W

            600 W

            30 W

            1 × PSR560-56D

            480 W

            30 W

            480 W

            30 W

            1 × PSR360-56A

            280 W

            30 W

            280 W

            30 W

            2 × PSR180-56A

            185 W

            30 W

            185 W

            30 W

            1 × PSR180-56A

            90 W

            30 W

            90 W

            30 W

             

            Software features

            Table 5 Software features of the S5560S-EI series

            Feature

            S5560S-28P-EI

            S5560S-52P-EI

            S5560S-28S-EI

            S5560S-28S-PWR-EI

            S5560S-52S-EI

            S5560S-52S-PWR-EI

            Full duplex Wire speed L2 switching capacity

            56Gbps

            104Gbps

            128Gbps

            176Gbps

            Whole system Wire speed L2 switching Packet forwarding rate

            41.664Mpps

            77.381Mpps

            95.232Mpps

            130.952Mpps

            IRF

            ·          Ring topology

            ·          Daisy chain topology

            ·          LACP MAD

            ·          ARP MAD

            Link aggregation

            ·          Aggregation of 1-GE ports

            ·          Aggregation of 10-GE ports

            ·          Static link aggregation

            ·          Dynamic link aggregation

            ·          Inter-device aggregation

            ·          A maximum of 14 aggregation groups on a device

            ·          A maximum of 124 inter-device aggregation groups

            ·          A maximum of 8 ports for each aggregation group

            Flow control

            ·          IEEE 802.3x flow control

            Jumbo Frame

            ·          Supports maximum frame size of 10000

            MAC address table

            ·          16K MAC addresses

            ·          1K static MAC addresses

            ·          Blackhole MAC addresses

            ·          MAC address learning limit on a port

            VLAN

            ·          Port-based VLANs (4094 VLANs)

            ·          QinQ

            ARP

            ·          4K entries

            ·          512 static entries

            ·          Gratuitous ARP

            ·          ARP black hole

            ·          ARP detection (based on DHCP snooping entries/802.1X security entries/static IP-to-MAC bindings)

            ·          ARP source suppression

            ND

            ·          1K entries

            ·          128  static entries

            VLAN virtual interface

            ·          1024

            DHCP

            ·          DHCP client

            ·          DHCP snooping

            ·          DHCP relay

            ·          DHCP server

            ·          DHCPv6 Server

            ·          DHCPv6 relay

            ·          DHCPv6 snooping

            UDP Helper

            ·          UDP Helper

            DNS

            ·          Static DNS

            ·          Dynamic DNS

            ·          IPv4 and IPv6 DNS

            unicast route

            ·          IPv4 and IPv6 static routes

            ·          RIP/RIPng

            ·          OSPF/OSPFv3

            ·          Routing policies

            ·          Policy-based routing

            ·          IPv6 policy-based routing

            Multicast

            ·          IGMP snooping

            ·          PIM Snooping

            ·          MLD snooping

            ·          IPv4 and IPv6 multicast VLAN

            ·          IPv6 PIM Snooping

            Broadcast/multicast/unicast storm control

            ·          Storm control based on port rate percentage

            ·          PPS-based storm control

            ·          Bps-based storm control

            MSTP

            ·          STP/RSTP/MSTP protocol

            ·          STP Root Guard

            ·          BPDU Guard

            ·          128 PVST instances

            QoS/ACL

            ·          Remarking of 802.1p and DSCP priorities

            ·          Packet filtering at L2 (Layer 2) through L4 (Layer 4)

            ·          Eight output queues for each port

            ·          SP/WRR/SP+WRR queue scheduling algorithms

            ·          Port-based rate limiting

            ·          Flow-based redirection

            ·          Time range

            Mirroring

            ·          Stream mirroring

            ·          Port mirroring

            Security

            ·          Hierarchical management and password protection of users

            ·          AAA authentication

            ·          RADIUS authentication

            ·          HWTACACS

            ·          LDAP

            ·          SSH 2.0

            ·          Port isolation

            ·          802.1X

            ·          Portal

            ·          Port security

            ·          MAC-address-based authentication

            ·          IP Source Guard

            ·          HTTPS

            ·          PKI

            ·          IPsec

            ·          EAD

            ·          Public key management

            802.1X

            ·          Up to 2K users

            ·          Port-based and MAC address-based authentication

            ·          Trunk port authentication

            ·          Dynamic 802.1X-based QoS/ACL/VLAN assignment

            Loading and upgrading

            ·          Loading and upgrading through XModem protocol

            ·          Loading and upgrading through FTP

            ·          Loading and upgrading through the trivial file transfer protocol (TFTP)

            Management

            ·          Configuration at the command line interface

            ·          Remote configuration through Telnet

            ·          Configuration through Console port

            ·          Simple network management protocol (SNMP)

            ·          Remote Monitoring(RMON)

            ·          IMC NMS

            ·          System log

            ·          Hierarchical alarms

            ·          NTP

            ·          Power supply alarm function

            ·          Fan and temperature alarms

            Maintenance

            ·          Debugging information output

            ·          Ping and Tracert

            ·          Remote maintenance through Telnet

            ·          NQA

            ·          802.1ag

            ·          802.3ah

            ·          DLDP

            ·          Virtual Cable Test

             


             

            Appendix B Upgrading software

            This chapter describes types of software used on the switch and how to upgrade software while the switch is operating normally or when the switch cannot correctly start up.

            System software file types

            Software required for starting up the switch includes:

            ·            Boot ROM image—A .bin file that comprises a basic section and an extended section. The basic section is the minimum code that bootstraps the system. The extended section enables hardware initialization and provides system management menus. You can use these menus to load software and the startup configuration file or manage files when the switch cannot correctly start up.

            ·            Software images—Includes boot images and system images.

            ?  Boot image—A .bin file that contains the operating system kernel. It provides process management, memory management, file system management, and the emergency shell.

            ?  System image—A .bin file that contains the minimum modules required for device operation and some basic features, including device management, interface management, configuration management, and routing management.

            The software images that have been loaded are called “current software images.” The software images specified to load at next startup are called “startup software images.”

            These images might be released separately or as a whole in one .ipe package file. If an .ipe file is used, the system automatically decompresses the file, loads the .bin boot and system images in the file and sets them as startup software images. Typically, the Boot ROM and software images for this switch series are released in an .ipe file named main.ipe.

             

             

            NOTE:

            Boot ROM images are not released along with the boot images and system images. To get a version of Boot ROM image, contact the H3C technical support.

             

            System startup process

            Upon power-on, the Boot ROM image runs to initialize hardware and then the software images run to start up the entire system, as shown in 0.

            System startup process

             

            Upgrade methods

            You can upgrade system software by using one of the following methods:

             

            Upgrading method

            Software types

            Remarks

            Upgrading from the CLI

            ·          Boot ROM image

            ·          Software images

            ·          You must reboot the switch to complete the upgrade.

            ·          This method can interrupt ongoing network services.

            Upgrading from the Boot menu

            ·          Boot ROM image

            ·          Software images

            Use this method when the switch cannot correctly start up.

            CAUTION CAUTION:

            Upgrading an IRF fabric from the CLI instead of the Boot menu.

            The Boot menu method increases the service downtime, because it requires that you upgrade the member switches one by one.

             

            The output in this document is for illustration only and might vary with software releases. This document uses boot.bin and system.bin to represent boot and system image names. The actual software image name format is chassis-model_Comware-version_image-type_release, for example, S5560S_EI-CMW710-BOOT-R6126P53.bin and S5560S_EI-CMW710-SYSM-R6126P53.bin.

            Upgrading from the CLI

            This section uses a two-member IRF fabric as an example to describe how to upgrade software from the CLI. If you have more than two subordinate switches, repeat the steps for the subordinate switch to upgrade their software. If you are upgrading a standalone switch, ignore the steps for upgrading the subordinate switch. For more information about setting up and configuring an IRF fabric, see the installation guide and IRF configuration guide for the H3C S5560S-EI switch series.

            Preparing for the upgrade

            Before you upgrade software, complete the following tasks:

            Log in to the IRF fabric through Telnet or the console port. (Details not shown.)

            Identify the number of IRF members, each member switch's role, and IRF member ID.

            <Sysname> display irf

            MemberID   Role   Priority  CPU-Mac         Description

             *+1      Master  5         0023-8927-afdc  ---

               2      Standby 1         0023-8927-af43  ---

            --------------------------------------------------

             * indicates the device is the master.

             + indicates the device through which the user logs in.

             

             The Bridge MAC of the IRF is: 0023-8927-afdb

             Auto upgrade                : no

             Mac persistent              : 6 min

             Domain ID                   : 0 

            Verify that each IRF member switch has sufficient storage space for the upgrade images.

             

            IMPORTANT

            IMPORTANT:

            Each IRF member switch must have free storage space that is at least two times the size of the upgrade image file.

             

            # Identify the free flash space of the master switch.

            <Sysname> dir

            Directory of flash:

                 0      -rw-       41424  Aug 23 2013 02:23:44     startup.mdb

                 1      -rw-        3792  Aug 23 2013 02:23:44     startup.cfg

                 2      -rw-    53555200  Aug 23 2013 09:53:48     system.bin

                 3      drw-           -  Aug 23 2013 00:00:07     seclog

                 4      drw-           -  Aug 23 2013 00:00:07     diagfile

                 5      drw-           -  Aug 23 2013 00:00:07     logfile

                 6      -rw-     9959424  Aug 23 2013 09:53:48     boot.bin

                 7      -rw-     9012224  Aug 23 2013 09:53:48     backup.bin

             

            524288 KB total (453416 KB free) 

            # Identify the free flash space of each subordinate switch, for example, switch 2.

            <Sysname> dir slot2#flash:/

            Directory of slot2#flash:/

                 0      -rw-       41424  Jan 01 2011 02:23:44     startup.mdb

                 1      -rw-        3792  Jan 01 2011 02:23:44     startup.cfg

                 2      -rw-    93871104  Aug 23 2013 16:00:08     system.bin

                 3      drw-           -  Jan 01 2011 00:00:07     seclog

                 4      drw-           -  Jan 01 2011 00:00:07     diagfile

                 5      drw-           -  Jan 02 2011 00:00:07     logfile

                 6      -rw-     13611008  Aug 23 2013 15:59:00     boot.bin

                 7      -rw-     9012224  Nov 25 2011 09:53:48     backup.bin

             

            524288 KB total (453416 KB free)

            Compare the free flash space of each member switch with the size of the software file to load. If the space is sufficient, start the upgrade process. If not, go to the next step.

            Delete unused files in the flash memory to free space:

             

            CAUTION

            CAUTION:

            ·       To avoid data loss, do not delete the current configuration file. For information about the current configuration file, use the display startup command.

            ·       The delete /unreserved file-url command deletes a file permanently and the action cannot be undone.

            ·       The delete file-url command moves a file to the recycle bin and the file still occupies storage space. To free the storage space, first execute the undelete command to restore the file, and then execute the delete /unreserved file-url command.

             

            # Delete unused files from the flash memory of the master switch.

            <Sysname> delete /unreserved flash:/backup.bin

            The file cannot be restored. Delete flash:/backup.bin?[Y/N]:y

            Deleting the file permanently will take a long time. Please wait...

            Deleting file flash:/backup.bin...Done.

            # Delete unused files from the flash memory of the subordinate switch.

            <Sysname> delete /unreserved slot2#flash:/backup.bin

            The file cannot be restored. Delete slot2#flash:/backup.bin?[Y/N]:y

            Deleting the file permanently will take a long time. Please wait...

            Deleting file slot2#flash:/backup.bin...Done.

            Downloading software images to the master switch

            Before you start upgrading software images packages, make sure you have downloaded the upgrading software files to the root directory in flash memory. This section describes downloading an .ipe software file as an example.

            The following are ways to download, upload, or copy files to the master switch:

            ·            FTP download from a server

            ·            FTP upload from a client

            ·            TFTP download from a server

            Prerequisites

            If FTP or TFTP is used, the IRF fabric and the PC working as the FTP/TFTP server or FTP client can reach each other.

            Prepare the FTP server or TFTP server program yourself for the PC. The switch series does not come with these software programs.

            FTP download from a server

            You can use the switch as an FTP client to download files from an FTP server.

            To download a file from an FTP server, for example, the server at 10.10.110.1:

            Run an FTP server program on the server, configure an FTP username and password, specify the working directory and copy the file, for example, newest.ipe, to the directory.

            Execute the ftp command in user view on the IRF fabric to access the FTP server.

            <Sysname> ftp 10.10.110.1

            Trying 10.10.110.1...

            Press CTRL+C to abort

            Connected to 10.10.110.1(10.10.110.1).

            220 FTP service ready.

            User (10.10.110.1:(none)):username                      

            331 Password required for username.

            Password:                                                

            230 User logged in.

            Enable the binary transfer mode.

            ftp> binary

              200 Type set to I.

            Execute the get command in FTP client view to download the file from the FTP server.

            ftp> get newest.ipe

              227 Entering Passive Mode (10,10,110,1,17,97).

              125 BINARY mode data connection already open, transfer starting for /newest.ipe

              226 Transfer complete.

              32133120 bytes received in 35 seconds (896. 0 kbyte/s)

            ftp> bye

            221 Server closing.

            FTP upload from a client

            You can use the IRF fabric as an FTP server and upload files from a client to the IRF fabric.

            To FTP upload a file from a client:

            On the IRF fabric:

            Enable FTP server.

            <Sysname> system-view

            [Sysname] ftp server enable

            Configure a local FTP user account:

            # Create the user account.

            [Sysname] local-user abc

            # Set its password and specify the FTP service.

            [Sysname-luser-manage-abc] password simple pwd

            [Sysname-luser-manage-abc] service-type ftp

            # Assign the network-admin user role to the user account for uploading file to the working directory of the server.

            [Sysname-luser-manage-abc] authorization-attribute user-role network-admin

            [Sysname-luser-manage-abc] quit

            [Sysname] quit

            On the PC:

            1.       Log in to the IRF fabric (the FTP server) in FTP mode.

            c:\> ftp 1.1.1.1

            Connected to 1.1.1.1.

            220 FTP service ready.

            User(1.1.1.1:(none)):abc                              

            331 Password required for abc.

            Password:                                             

            230 User logged in.

            Enable the binary file transfer mode.

            ftp> binary

            200 TYPE is now 8-bit binary.

            Upload the file (for example, newest.ipe) to the root directory of the flash memory on the master switch.

            ftp> put newest.ipe

            200 PORT command successful

            150 Connecting to port 10002

            226 File successfully transferred

            ftp: 32133120 bytes sent in 64.58 secs (497.60 Kbytes/sec).

            TFTP download from a server

            To download a file from a TFTP server, for example, the server at 10.10.110.1:

            Run a TFTP server program on the server, specify the working directory, and copy the file, for example, newest.ipe, to the directory.

            On the IRF fabric, execute the tftp command in user view to download the file to the root directory of the flash memory on the master switch.

            <Sysname> tftp 10.10.110.1 get newest.ipe

            Press CTRL+C to abort.

              % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                             Dload  Upload   Total   Spent    Left  Speed

            100 30.6M    0 30.6M    0     0   143k      0 --:--:--  0:03:38 --:--:--  142k

            Upgrading the software images

            To upgrade the software images:

            Specify the upgrade image file (newest.ipe in this example) used at the next startup for the master switch, and assign the M attribute to the boot and system images in the file.

            <Sysname> boot-loader file flash:/newest.ipe slot 1 main

            Verifying image file..........Done.                                            

            Images in IPE:                                                                 

              boot.bin                                            

              system.bin                                          

            This command will set the main startup software images. Continue? [Y/N]:y      

            Add images to target slot.                                                     

            Decompressing file boot.bin to flash:/boot.bin....................Done.        

            Decompressing file system.bin to flash:/system.bin................Done.        

            The images that have passed all examinations will be used as the main startup so

            ftware images at the next reboot on slot 1.

            Specify the upgrade image file as the main startup image file for each subordinate switch. This example uses IRF member 2. (The subordinate switches will automatically copy the file to the root directory of their flash memories.)

            <Sysname> boot-loader file flash:/newest.ipe slot 2 main

            Verifying image file..........Done.                                            

            Images in IPE:                                                                 

              boot.bin                                            

              system.bin                                           

            This command will set the main startup software images. Continue? [Y/N]:y      

            Add images to target slot.                                                     

            Decompressing file boot.bin to flash:/boot.bin....................Done.        

            Decompressing file system.bin to flash:/system.bin................Done.        

            The images that have passed all examinations will be used as the main startup so

            ftware images at the next reboot on slot 2.

            Enable the software auto-update function.

            <Sysname> system-view

            [Sysname] irf auto-update enable

            [Sysname] quit

            This function checks the software versions of member switches for inconsistency with the master switch. If a subordinate switch is using a different software version than the master, the function propagates the current software images of the master to the subordinate as main startup images. The function prevents software version inconsistency from causing the IRF setup failure.

            Save the current configuration in any view to prevent data loss.

            <Sysname> save

            The current configuration will be written to the device. Are you sure? [Y/N]:y

            Please input the file name(*.cfg)[flash:/startup.cfg]

            (To leave the existing filename unchanged, press the enter key):

            flash:/startup.cfg exists, overwrite? [Y/N]:y

            Validating file. Please wait.................

            Saved the current configuration to mainboard device successfully.

            Slot 2:

            Save next configuration file successfully.

            Reboot the IRF fabric to complete the upgrade.

            <Sysname> reboot

            Start to check configuration with next startup configuration file, please wait.

            ........DONE!

            This command will reboot the device. Continue? [Y/N]:y

             Now rebooting, please wait...

            The system automatically loads the .bin boot and system images in the .ipe file and sets them as the startup software images.

            Execute the display version command in any view to verify that the current main software images have been updated (details not shown).

             

             

            NOTE:

            The system automatically checks the compatibility of the Boot ROM image and the boot and system images during the reboot. If you are prompted that the Boot ROM image in the upgrade image file is different than the current Boot ROM image, upgrade both the basic and extended sections of the Boot ROM image for compatibility. If you choose to not upgrade the Boot ROM image, the system will ask for an upgrade at the next reboot performed by powering on the switch or rebooting from the CLI (promptly or as scheduled). If you fail to make any choice in the required time, the system upgrades the entire Boot ROM image.

             

            Upgrading from the Boot menu

            In this approach, you must access the Boot menu of each member switch to upgrade their software one by one. If you are upgrading software images for an IRF fabric, using the CLI is a better choice.

             

            TIP

            TIP:

            Upgrading through the Ethernet port is faster than through the console port.

             

            Prerequisites

            Make sure the prerequisites are met before you start upgrading software from the Boot menu.

            Setting up the upgrade environment

            Use a console cable to connect the console terminal (for example, a PC) to the console port on the switch.

            Connect the Ethernet port on the switch to the file server.

             

             

            NOTE:

            The file server and the configuration terminal can be co-located.

             

            Run a terminal emulator program on the console terminal and set the following terminal settings:

            ?  Bits per second—9,600

            ?  Data bits—8

            ?  Parity—None

            ?  Stop bits—1

            ?  Flow control—None

            ?  Emulation—VT100

            Preparing for the TFTP or FTP transfer

            To use TFTP or FTP:

            ·            Run a TFTP or FTP server program on the file server or the console terminal.

            ·            Copy the upgrade file to the file server.

            ·            Correctly set the working directory on the TFTP or FTP server.

            ·            Make sure the file server and the switch can reach each other.

            Verifying that sufficient storage space is available

            IMPORTANT

            IMPORTANT:

            For the switch to start up correctly, do not delete the main startup software images when you free storage space before upgrading Boot ROM. On the Boot menu, the main startup software images are marked with an asterisk (*).

             

            When you upgrade software, make sure each member switch has sufficient free storage space for the upgrade file, as shown in 0.

            Minimum free storage space requirements

            Upgraded images

            Minimum free storage space requirements

            Comware images

            Two times the size of the Comware upgrade package file.

            Boot ROM

            Same size as the Boot ROM upgrade image file.

             

            If no sufficient space is available, delete unused files as described in “Managing files from the Boot menu.”

            Scheduling the upgrade time

            During the upgrade, the switch cannot provide any services. You must make sure the upgrade has a minimal impact on the network services.

            Accessing the Boot menu

            Starting......

            Press Ctrl+D to access BASIC BOOT MENU

                                                                                  

            ********************************************************************************

            *                                                                              *

            *              H3C S5560S-28S-EI BOOTROM, Version 126                          *

            *                                                                              *

            ********************************************************************************

            Copyright (c) 2004-2019 New H3C Technologies Co., Ltd.                    

                                                                                            

            Creation Date       : Mar 17 2016, 18:15:02                                    

            CPU Clock Speed     : 400MHz                                                  

            Memory Size         : 512MB                                                    

            Flash Size          : 256MB                                                    

            CPLD Version        : 001                                                      

            PCB Version         : Ver.A                                                    

            Mac Address         : 000012346666

             

            Press Ctrl+B to access EXTENDED BOOT MENU...1

            Press one of the shortcut key combinations at prompt.

            Shortcut keys

            Shortcut keys

            Prompt message

            Function

            Remarks

            Ctrl+B

            Press Ctrl+B to enter Extended Boot menu...

            Accesses the extended Boot menu.

            Press the keys within 1 second (in fast startup mode) or 5 seconds (in full startup mode) after the message appears.

            You can upgrade and manage system software and Boot ROM from this menu.

             

             

            Accessing the extended Boot menu

            Press Ctrl+B within 1 second (in fast startup mode) or 5 seconds (in full startup mode) after the "Press Ctrl-B to enter Extended Boot menu..." prompt message appears. If you fail to do this, the system starts decompressing the system software.

            Alternatively, you can enter 4 in the basic Boot menu to access the extended Boot menu.

            The "Password recovery capability is enabled." or "Password recovery capability is disabled." message appears, followed by the extended Boot menu. Availability of some menu options depends on the state of password recovery capability (see 0). For more information about password recovery capability, see Fundamentals Configuration Guide in H3C S5560S-EI Switch Series Configuration Guides-R612x.

            Password recovery capability is enabled.

             

               EXTENDED BOOT MENU

             

            1. Download image to flash

            2. Select image to boot

            3. Display all files in flash

            4. Delete file from flash

            5. Restore to factory default configuration

            6. Enter BootRom upgrade menu

            7. Skip current system configuration

            8. Set switch startup mode

            0. Reboot

            Ctrl+Z: Access EXTENDED ASSISTANT MENU

            Ctrl+F: Format file system

            Ctrl+P: Change authentication for console login

            Ctrl+R: Download image to SDRAM and run

            Ctrl+Y: Change Work Mode

            Ctrl+C: Display Copyright

             

            Enter your choice(0-8):

             

            Extended Boot ROM menu options

            Option

            Tasks

            1. Download image to flash

            Download a software image file to the flash.

            2. Select image to boot

            ·          Specify the main and backup software image file for the next startup.

            ·          Specify the main and backup configuration files for the next startup. This task can be performed only if password recovery capability is enabled.

            3. Display all files in flash

            Display files on the flash.

            4. Delete file from flash

            Delete files to free storage space.

            5. Restore to factory default configuration

            Delete the current next-startup configuration files and restore the factory-default configuration.

            This option is available only if password recovery capability is disabled.

            6. Enter BootRom upgrade menu

            Access the Boot ROM upgrade menu.

            7. Skip current system configuration

            Start the switch without loading any configuration file.

            This is a one-time operation and takes effect only for the first system boot or reboot after you choose this option.

            This option is available only if password recovery capability is enabled.

            8. Set switch startup mode

            Set the startup mode to fast startup mode or full startup mode.

            0. Reboot

            Reboot the switch.

            Ctrl+F: Format file system

            Format the current storage medium.

            Ctrl+P: Change authentication for console login

            Skip the authentication for console login.

            This is a one-time operation and takes effect only for the first system boot or reboot after you choose this option.

            This option is available only if password recovery capability is enabled.

            Ctrl+R: Download image to SDRAM and run

            Download a system software image and start the switch with the image.

            This option is available only if password recovery capability is enabled.

            Ctrl+Z: Access EXTENDED ASSISTANT MENU

            Access the EXTENDED ASSISTANT MENU.

            For options in the menu, see 0.

            Ctrl+Y: Change Work Mode

            Change Work Mode.

            Ctrl+C: Display Copyright

            Display the copyright statement.

             

            EXTENDED ASSISTANT menu options

            Option

            Task

            1. Display Memory

            Display data in the memory.

            2. Search Memory

            Search the memory for a specific data segment.

            0. Return to boot menu

            Return to the extended Boot ROM menu.

             

            Upgrading Comware images from the Boot menu

            You can use the following methods to upgrade Comware images:

            ·            Using TFTP to upgrade software images through the Ethernet port

            ·            Using FTP to upgrade software images through the Ethernet port

            ·            Using XMODEM to upgrade software through the console port

            Using TFTP to upgrade software images through the Ethernet port

            Enter 1 in the Boot menu to access the file transfer protocol submenu.

            1. Set TFTP protocol parameters

            2. Set FTP protocol parameters

            3. Set XMODEM protocol parameters

            0. Return to boot menu

             

            Enter your choice(0-3):

            Enter 1 to set the TFTP parameters.

            Load File Name      :update.ipe

            Server IP Address   :192.168.0.3

            Local IP Address    :192.168.0.2

            Subnet Mask         :255.255.255.0

            Gateway IP Address  :0.0.0.0

            TFTP parameter description

            Item

            Description

            Load File Name

            Name of the file to download (for example, update.ipe).

            Server IP Address

            IP address of the TFTP server (for example, 192.168.0.3).

            Local IP Address

            IP address of the switch (for example, 192.168.0.2).

            Subnet Mask

            Subnet mask of the switch (for example, 255.255.255.0).

            Gateway IP Address

            IP address of the gateway (in this example, no gateway is required because the server and the switch are on the same subnet).

             

             

            NOTE:

            ·       To use the default setting for a field, press Enter without entering any value.

            ·       If the switch and the server are on different subnets, you must specify a gateway address for the switch.

             

            Enter all required parameters, and enter Y to confirm the settings. The following prompt appears:

            Are you sure to download file to flash? Yes or No (Y/N):Y

            Enter Y to start downloading the image file. To return to the Boot menu without downloading the upgrade file, enter N.

            Loading.........................................................................

            ................................................................................

            ................................................................................

            ................................................................Done!

            Enter the M (main), B (backup), or N (none) attribute for the images. In this example, assign the main attribute to the images.

            Please input the file attribute (Main/Backup/None) M

            Image file boot.bin is self-decompressing...

            Free space: 534980608 bytes

            Writing flash...................................................................

            ................................................................................

            ...................................................................Done!

            Image file system.bin is self-decompressing...

            Free space: 525981696 bytes

            Writing flash...................................................................

            ................................................................................

            ................................................................................

            ................................................................................

            ................................................................................

            ................................................................................

            .......................................................................Done!

             

             

            NOTE:

            ·       The switch always attempts to boot with the main images first. If the attempt fails, for example, because the main images are not available, the switch tries to boot with the backup images. An image with the none attribute is only stored in flash memory for backup. To use it at reboot, you must change its attribute to main or backup.

            ·       If an image with the same attribute as the image you are loading is already in the flash memory, the attribute of the old image changes to none after the new image becomes valid.

             

            Enter 0 in the Boot menu to reboot the switch with the new software images.

               EXTENDED BOOT MENU

             

            1. Download image to flash

            2. Select image to boot

            3. Display all files in flash

            4. Delete file from flash

            5. Restore to factory default configuration

            6. Enter BootRom upgrade menu

            7. Skip current system configuration

            8. Set switch startup mode

            0. Reboot

            Ctrl+Z: Access EXTENDED ASSISTANT MENU

            Ctrl+F: Format file system

            Ctrl+P: Change authentication for console login

            Ctrl+R: Download image to SDRAM and run

            Ctrl+Y: Change Work Mode

            Ctrl+C: Display Copyright

             

            Enter your choice(0-8): 0

            Using FTP to upgrade software images through the Ethernet port

            Enter 1 in the Boot menu to access the file transfer protocol submenu.

            1. Set TFTP protocol parameters

            2. Set FTP protocol parameters

            3. Set XMODEM protocol parameters

            0. Return to boot menu

             

            Enter your choice(0-3):

            Enter 2 to set the FTP parameters.

            Load File Name      :update.ipe

            Server IP Address   :192.168.0.3

            Local IP Address    :192.168.0.2

            Subnet Mask         :255.255.255.0

            Gateway IP Address  :0.0.0.0

            FTP User Name       :switch

            FTP User Password   :***

            FTP parameter description

            Item

            Description

            Load File Name

            Name of the file to download (for example, update.ipe).

            Server IP Address

            IP address of the FTP server (for example, 192.168.0.3).

            Local IP Address

            IP address of the switch (for example, 192.168.0.2).

            Subnet Mask

            Subnet mask of the switch (for example, 255.255.255.0).

            Gateway IP Address

            IP address of the gateway (in this example, no gateway is required because the server and the switch are on the same subnet).

            FTP User Name

            Username for accessing the FTP server, which must be the same as configured on the FTP server.

            FTP User Password

            Password for accessing the FTP server, which must be the same as configured on the FTP server.

             

             

            NOTE:

            ·       To use the default setting for a field, press Enter without entering any value.

            ·       If the switch and the server are on different subnets, you must specify a gateway address for the switch.

             

            Enter all required parameters, and enter Y to confirm the settings. The following prompt appears:

            Are you sure to download file to flash? Yes or No (Y/N):Y

            Enter Y to start downloading the image file. To return to the Boot menu without downloading the upgrade file, enter N.

            Loading.........................................................................

            ................................................................................

            ................................................................................

            ................................................................Done!

            Enter the M (main), B (backup), or N (none) attribute for the images. In this example, assign the main attribute to the images.

            Please input the file attribute (Main/Backup/None) M

            Image file boot.bin is self-decompressing...

            Free space: 534980608 bytes

            Writing flash...................................................................

            ................................................................................

            ...................................................................Done!

            Image file system.bin is self-decompressing...

            Free space: 525981696 bytes

            Writing flash...................................................................

            ................................................................................

            ................................................................................

            ................................................................................

            ................................................................................

            ................................................................................

            .......................................................................Done!

             

               EXTENDED BOOT MENU

             

            1. Download image to flash

            2. Select image to boot

            3. Display all files in flash

            4. Delete file from flash

            5. Restore to factory default configuration

            6. Enter BootRom upgrade menu

            7. Skip current system configuration

            8. Set switch startup mode

            0. Reboot

            Ctrl+Z: Access EXTENDED ASSISTANT MENU

            Ctrl+F: Format file system

            Ctrl+P: Change authentication for console login

            Ctrl+R: Download image to SDRAM and run

            Ctrl+Y: Change Work Mode

            Ctrl+C: Display Copyright

             

            Enter your choice(0-8):0

             

             

            NOTE:

            ·       The switch always attempts to boot with the main images first. If the attempt fails, for example, because the main images not available, the switch tries to boot with the backup images. An image with the none attribute is only stored in flash memory for backup. To use it at reboot, you must change its attribute to main or backup.

            ·       If an image with the same attribute as the image you are loading is already in the flash memory, the attribute of the old image changes to none after the new image becomes valid.

             

            Enter 0 in the Boot menu to reboot the switch with the new software images.

            Using XMODEM to upgrade software through the console port

            XMODEM download through the console port is slower than TFTP or FTP download through the Ethernet port. To save time, use the Ethernet port as long as possible.

            Enter 1 in the Boot menu to access the file transfer protocol submenu.

            1. Set TFTP protocol parameters

            2. Set FTP protocol parameters

            3. Set XMODEM protocol parameters

            0. Return to boot menu

             

            Enter your choice(0-3):

            Enter 3 to set the XMODEM download baud rate.

            Please select your download baudrate:

            1.* 9600

            2.  19200

            3.  38400

            4.  57600

            5.  115200

            0.  Return to boot menu

             

            Enter your choice(0-5):5

            Select an appropriate download rate, for example, enter 5 to select 115200 bps.

            Download baudrate is 115200 bps                              

            Please change the terminal's baudrate to 115200 bps and select XMODEM protocol

            Press enter key when ready

            Set the serial port on the terminal to use the same baud rate and protocol as the console port. If you select 9600 bps as the download rate for the console port, skip this task.

            Select Call > Disconnect in the HyperTerminal window to disconnect the terminal from the switch.

            Disconnecting the terminal from the switch

             

            b.   Select File > Properties, and in the Properties dialog box, click Configure.

            Properties dialog box

             

            c.    Select 115200 from the Bits per second list and click OK.

            Modifying the baud rate

             

            d.   Select Call > Call to reestablish the connection.

            Reestablishing the connection

             

            Press Enter. The following prompt appears:

            Are you sure to download file to flash? Yes or No (Y/N):Y

            Enter Y to start downloading the file. (To return to the Boot menu, enter N.)

            Now please start transfer file with XMODEM protocol

            If you want to exit, Press <Ctrl+X>

            Loading ...CCCCCCCCCCCCCCCCCCCCCCCCC 

            Select Transfer > Send File in the HyperTerminal window.

            Transfer menu

             

            In the dialog box that appears, click Browse to select the source file, and select Xmodem from the Protocol list.

            File transmission dialog box

             

            Click Send. The following dialog box appears:

            File transfer progress

             

            Enter the M (main), B (backup), or N (none) attribute for the images. In this example, assign the main attribute to the images.

            Please input the file attribute (Main/Backup/None) m

            The boot.bin image is self-decompressing...

            # At the Load File name prompt, enter a name for the boot image to be saved to flash memory.

            Load File name  : default_file boot-update.bin       (At the prompt,

            Free space: 470519808 bytes

            Writing flash...................................................................

            .............Done!

            The system-update.bin image is self-decompressing...

            # At the Load File name prompt, enter a name for the system image to be saved to flash memory.

            Load File name  : default_file system-update.bin     

            Free space: 461522944 bytes

            Writing flash...................................................................

            .............Done!

            Your baudrate should be set to 9600 bps again!

            Press enter key when ready

             

             

            NOTE:

            ·       The switch always attempts to boot with the main images first. If the attempt fails, for example, because the main images not available, the switch tries to boot with the backup images. An image with the none attribute is only stored in the flash memory for backup. To use it at reboot, you must change its attribute to main or backup.

            ·       If an image with the same attribute as the image you are loading is already in flash memory, the attribute of the old image changes to none after the new image becomes valid.

             

            If the baud rate of the HyperTerminal is not 9600 bps, restore it to 9600 bps as described in step 0. If the baud rate is 9600 bps, skip this step.

             

             

            NOTE:

            The console port rate reverts to 9600 bps at a reboot. If you have changed the baud rate, you must perform this step so you can access the switch through the console port after a reboot.

             

               EXTENDED BOOT MENU

             

            1. Download image to flash

            2. Select image to boot

            3. Display all files in flash

            4. Delete file from flash

            5. Restore to factory default configuration

            6. Enter BootRom upgrade menu

            7. Skip current system configuration

            8. Set switch startup mode

            0. Reboot

            Ctrl+Z: Access EXTENDED ASSISTANT MENU

            Ctrl+F: Format file system

            Ctrl+P: Change authentication for console login

            Ctrl+R: Download image to SDRAM and run

            Ctrl+Y: Change Work Mode

            Ctrl+C: Display Copyright

             

            Enter your choice(0-8): 0

            Enter 0 in the Boot menu to reboot the system with the new software images.

            Upgrading Boot ROM from the Boot menu

            You can use the following methods to upgrade the Boot ROM image:

            ·            Using TFTP to upgrade Boot ROM through the Ethernet port

            ·            Using FTP to upgrade Boot ROM through the Ethernet port

            ·            Using XMODEM to upgrade Boot ROM through the console port

            Using TFTP to upgrade Boot ROM through the Ethernet port

            Enter 6 in the Boot menu to access the Boot ROM update menu.

            1. Update full BootRom

            2. Update extended BootRom

            3. Update basic BootRom

            0. Return to boot menu

             

            Enter your choice(0-3):

            Enter 1 in the Boot ROM update menu to upgrade the full Boot ROM.

            The file transfer protocol submenu appears:

            1. Set TFTP protocol parameters

            2. Set FTP protocol parameters

            3. Set XMODEM protocol parameters

            0. Return to boot menu

             

            Enter your choice(0-3):

            Enter 1 to set the TFTP parameters.

            Load File Name      :update.btm

            Server IP Address   :192.168.0.3

            Local IP Address    :192.168.0.2

            Subnet Mask         :255.255.255.0

            Gateway IP Address  :0.0.0.0

            TFTP parameter description

            Item

            Description

            Load File Name

            Name of the file to download (for example, update.btm).

            Server IP Address

            IP address of the TFTP server (for example, 192.168.0.3).

            Local IP Address

            IP address of the switch (for example, 192.168.0.2).

            Subnet Mask

            Subnet mask of the switch (for example, 255.255.255.0).

            Gateway IP Address

            IP address of the gateway (in this example, no gateway is required because the server and the switch are on the same subnet).

             

             

            NOTE:

            ·       To use the default setting for a field, press Enter without entering any value.

            ·       If the switch and the server are on different subnets, you must specify a gateway address for the switch.

             

            Enter all required parameters and press Enter to start downloading the file.

            Loading.................................................Done! 

            Enter Y at the prompt to upgrade the basic Boot ROM section.

            Will you Update Basic BootRom? (Y/N):Y

            Updating Basic BootRom...........Done.

            Enter Y at the prompt to upgrade the extended Boot ROM section.

            Updating extended BootRom? (Y/N):Y

            Updating extended BootRom.........Done.

            Enter 0 in the Boot ROM update menu to return to the Boot menu.

            1. Update full BootRom

            2. Update extended BootRom

            3. Update basic BootRom

            0. Return to boot menu

             

            Enter your choice(0-3):

            Enter 0 in the Boot menu to reboot the switch with the new Boot ROM image.

            Using FTP to upgrade Boot ROM through the Ethernet port

            Enter 6 in the Boot menu to access the Boot ROM update menu.

            1. Update full BootRom

            2. Update extended BootRom

            3. Update basic BootRom

            0. Return to boot menu

             

            Enter your choice(0-3):

            Enter 1 in the Boot ROM update menu to upgrade the full Boot ROM.

            The file transfer protocol submenu appears:

            1. Set TFTP protocol parameters

            2. Set FTP protocol parameters

            3. Set XMODEM protocol parameters

            0. Return to boot menu

             

            Enter your choice(0-3):

            Enter 2 to set the FTP parameters.

            Load File Name     :update.btm

            Server IP Address  :192.168.0.3

            Local IP Address   :192.168.0.2

            Subnet Mask        :255.255.255.0

            Gateway IP Address :0.0.0.0

            FTP User Name      :switch

            FTP User Password  :123

            FTP parameter description

            Item

            Description

            Load File Name

            Name of the file to download (for example, update.btm).

            Server IP Address

            IP address of the FTP server (for example, 192.168.0.3).

            Local IP Address

            IP address of the switch (for example, 192.168.0.2).

            Subnet Mask

            Subnet mask of the switch (for example, 255.255.255.0).

            Gateway IP Address

            IP address of the gateway (in this example, no gateway is required because the server and the switch are on the same subnet).

            FTP User Name

            Username for accessing the FTP server, which must be the same as configured on the FTP server.

            FTP User Password

            Password for accessing the FTP server, which must be the same as configured on the FTP server.

             

             

            NOTE:

            ·       To use the default setting for a field, press Enter without entering any value.

            ·       If the switch and the server are on different subnets, you must specify a gateway address for the switch.

             

            Enter all required parameters and press Enter to start downloading the file.

            Loading.................................................Done! 

            Enter Y at the prompt to upgrade the basic Boot ROM section.

            Will you Update Basic BootRom? (Y/N):Y

            Updating Basic BootRom...........Done.

            Enter Y at the prompt to upgrade the extended Boot ROM section.

            Updating extended BootRom? (Y/N):Y

            Updating extended BootRom.........Done.

            Enter 0 in the Boot ROM update menu to return to the Boot menu.

            1. Update full BootRom

            2. Update extended BootRom

            3. Update basic BootRom

            0. Return to boot menu

             

            Enter your choice(0-3):

            Enter 0 in the Boot menu to reboot the switch with the new Boot ROM image.

            Using XMODEM to upgrade Boot ROM through the console port

            XMODEM download through the console port is slower than TFTP or FTP download through the Ethernet port. To save time, use the Ethernet port as long as possible.

            Enter 6 in the Boot menu to access the Boot ROM update menu.

            1. Update full BootRom

            2. Update extended BootRom

            3. Update basic BootRom

            0. Return to boot menu

             

            Enter your choice(0-3):

            Enter 1 in the Boot ROM update menu to upgrade the full Boot ROM.

            The file transfer protocol submenu appears:

            1. Set TFTP protocol parameters

            2. Set FTP protocol parameters

            3. Set XMODEM protocol parameters

            0. Return to boot menu

             

            Enter your choice(0-3):

            Enter 3 to set the XMODEM download baud rate.

            Please select your download baudrate:

            1.* 9600

            2.  19200

            3.  38400

            4.  57600

            5.  115200

            0.  Return to boot menu

             

            Enter your choice(0-5):5

            Select an appropriate download rate, for example, enter 5 to select 115200 bps.

            Download baudrate is 115200 bps                              

            Please change the terminal's baudrate to 115200 bps and select XMODEM protocol

            Press enter key when ready

            Set the serial port on the terminal to use the same baud rate and protocol as the console port. If you select 9600 bps as the download rate for the console port, skip this task.

            Select Call > Disconnect in the HyperTerminal window to disconnect the terminal from the switch.

            Disconnecting the terminal from the switch

             

            b.   Select File > Properties, and in the Properties dialog box, click Configure.

            Properties dialog box

             

            c.    Select 115200 from the Bits per second list and click OK.

            Modifying the baud rate

             

            d.   Select Call > Call to reestablish the connection.

            Reestablishing the connection

             

            Press Enter to start downloading the file.

            Now please start transfer file with XMODEM protocol

            If you want to exit, Press <Ctrl+X>

            Loading ...CCCCCCCCCCCCCCCCCCCCCCCCC 

            Select Transfer > Send File in the HyperTerminal window.

            Transfer menu

             

            In the dialog box that appears, click Browse to select the source file, and select Xmodem from the Protocol list.

            File transmission dialog box

             

            Click Send. The following dialog box appears:

            File transfer progress

             

            Enter Y at the prompt to upgrade the basic Boot ROM section.

            Loading ...CCCCCCCCCCCCCC  ...Done! 

            Will you Update Basic BootRom? (Y/N):Y

            Updating Basic BootRom...........Done.

            Enter Y at the prompt to upgrade the extended Boot ROM section.

            Updating extended BootRom? (Y/N):Y

            Updating extended BootRom.........Done.

            If the baud rate of the HyperTerminal is not 9600 bps, restore it to 9600 bps at the prompt, as described in step 0. If the baud rate is 9600 bps, skip this step.

            Please change the terminal's baudrate to 9600 bps, press ENTER when ready.

             

             

            NOTE:

            The console port rate reverts to 9600 bps at a reboot. If you have changed the baud rate, you must perform this step so you can access the switch through the console port after a reboot.

             

            Press Enter to access the Boot ROM update menu.

            Enter 0 in the Boot ROM update menu to return to the Boot menu.

            1. Update full BootRom

            2. Update extended BootRom

            3. Update basic BootRom

            0. Return to boot menu

             

            Enter your choice(0-3):

            Enter 0 in the Boot menu to reboot the switch with the new Boot ROM image.

            Managing files from the Boot menu

            From the Boot menu, you can display files in flash memory to check for obsolete files, incorrect files, or space insufficiency, delete files to release storage space, or change the attributes of software images.

            Displaying all files

            Enter 3 in the Boot menu to display all files in flash memory and identify the free space size.

               EXTENDED BOOT MENU

             

            1. Download image to flash

            2. Select image to boot

            3. Display all files in flash

            4. Delete file from flash

            5. Restore to factory default configuration

            6. Enter BootRom upgrade menu

            7. Skip current system configuration

            8. Set switch startup mode

            0. Reboot

            Ctrl+Z: Access EXTENDED ASSISTANT MENU

            Ctrl+F: Format file system

            Ctrl+P: Change authentication for console login

            Ctrl+R: Download image to SDRAM and run

            Ctrl+Y: Change Work Mode

            Ctrl+C: Display Copyright

             

            Enter your choice(0-8): 3

            The following is a sample output:

            Display all file(s) in flash:

             

            File Number    File Size(bytes)     File Name

            ================================================================================

            1              8177                 flash:/testbackup.cfg

            2(*)           53555200             flash:/system.bin

            3(*)           9959424              flash:/boot.bin

            4              3678                 flash:/startup.cfg_backup

            5              30033                flash:/default.mdb

            6              42424                flash:/startup.mdb

            7              18                   flash:/.pathfile

            8              232311               flash:/logfile/logfile.log

            9              5981                 flash:/startup.cfg_back

            10(*)          6098                 flash:/startup.cfg

            11             20                   flash:/.snmpboots

            Free space: 464298848 bytes

            The current image is boot.bin

            (*)-with main attribute

            (b)-with backup attribute

            (*b)-with both main and backup attribute

            Deleting files

            If storage space is insufficient, delete obsolete files to free up storage space.

            To delete files:

            Enter 4 in the Boot menu:

            Deleting the file in flash:

             

            File Number    File Size(bytes)     File Name

            ================================================================================

            1              8177                 flash:/testbackup.cfg

            2(*)           53555200             flash:/system.bin

            3(*)           9959424              flash:/boot.bin

            4              3678                 flash:/startup.cfg_backup

            5              30033                flash:/default.mdb

            6              42424                flash:/startup.mdb

            7              18                   flash:/.pathfile

            8              232311               flash:/logfile/logfile.log

            9              5981                 flash:/startup.cfg_back

            10(*)          6098                 flash:/startup.cfg

            11             20                   flash:/.snmpboots

            Free space: 464298848 bytes

            The current image is boot.bin

            (*)-with main attribute

            (b)-with backup attribute

            (*b)-with both main and backup attribute

            Enter the number of the file to delete. For example, enter 1 to select the file testbackup.cfg.

            Please input the file number to change: 1

            Enter Y at the confirmation prompt.

            The file you selected is testbackup.cfg,Delete it? (Y/N):Y

            Deleting....................................Done!

            Changing the attribute of software images

            Software image attributes include main (M), backup (B), and none (N). System software and boot software can each have multiple none-attribute images but only one main image and one backup image on the switch. You can assign both the M and B attributes to one image. If the M or B attribute you are assigning has been assigned to another image, the assignment removes the attribute from that image. If the removed attribute is the sole attribute of the image, its attribute changes to N.

            For example, the system image system.bin has the M attribute and the system image system-update.bin has the B attribute. After you assign the M attribute to system-update.bin, the attribute of system-update.bin changes to M+B and the attribute of system.bin changes to N.

            To change the attribute of a system or boot image:

            Enter 2 in the Boot menu.

               EXTENDED BOOT MENU

             

            1. Download image to flash

            2. Select image to boot

            3. Display all files in flash

            4. Delete file from flash

            5. Restore to factory default configuration

            6. Enter BootRom upgrade menu

            7. Skip current system configuration

            8. Set switch startup mode

            0. Reboot

            Ctrl+Z: Access EXTENDED ASSISTANT MENU

            Ctrl+F: Format file system

            Ctrl+P: Change authentication for console login

            Ctrl+R: Download image to SDRAM and run

            Ctrl+Y: Change Work Mode

            Ctrl+C: Display Copyright

             

            Enter your choice(0-8): 2

             

            1 or 2 at the prompt to set the attribute of a software image. (The following output is based on the option 2. To set the attribute of a configuration file, enter 3.)

            1. Set image file

            2. Set bin file

            3. Set configuration file

            0. Return to boot menu

             

            Enter your choice(0-3): 2

             

            File Number    File Size(bytes)     File Name

            ================================================================================

             

            1(*)              53555200              flash:/system.bin

            2(*)              9959424               flash:/boot.bin

            3                 13105152              flash:/boot-update.bin

            4                 91273216              flash:/system-update.bin

            Free space: 417177920 bytes

            (*)-with main attribute

            (b)-with backup attribute

            (*b)-with both main and backup attribute

            Note:Select .bin files. One but only one boot image and system image must be included.

            Enter the number of the file you are working with. For example, enter 3 to select the boot image boot-update.bin. and enter 4 to select the system image system-update.bin.

            Enter file No.(Allows multiple selection):3

            Enter another file No.(0-Finish choice):4

            Enter 0 to finish the selection.

            Enter another file No.(0-Finish choice):0

            You have selected:

            flash:/boot-update.bin

            flash:/system-update.bin

            Enter M or B to change its attribute to main or backup. If you change its attribute to M, the attribute of boot.bin changes to none.

            Please input the file attribute (Main/Backup) M

            This operation may take several minutes. Please wait....

            Next time, boot-update.bin will become default boot file!

            Next time, system-update.bin will become default boot file! 

            Set the file attribute success!

            Handling software upgrade failures

            If a software upgrade fails, the system runs the old software version.

            To handle a software upgrade failure:

            Verify that the software release is compatible with the switch model and the correct file is used.

            Verify that the software release and the Boot ROM release are compatible. For software and Boot ROM compatibility, see the hardware and software compatibility matrix in the correct release notes.

            Check the physical ports for a loose or incorrect connection.

            If you are using the console port for file transfer, check the HyperTerminal settings (including the baud rate and data bits) for any wrong setting.

            Check the file transfer settings:

            ?  If XMODEM is used, you must set the same baud rate for the terminal as for the console port.

            ?  If TFTP is used, you must enter the same server IP addresses, file name, and working directory as set on the TFTP server.

            ?  If FTP is used, you must enter the same FTP server IP address, source file name, working directory, and FTP username and password as set on the FTP server.

            Check the FTP or TFTP server for any incorrect setting.

            Check that the storage device has sufficient space for the upgrade file.

             

            上海快三稳定计划_上海快三稳定计划|官网_首页 http://cn.engadget.com/tag/竞彩足球比分直播彩票【28c63.com】 http://cn.engadget.com/tag/体育彩票2剩1篮球【28c63.com】 http://cn.engadget.com/tag/体育彩票开奖号码查询【28c63.com】 http://cn.engadget.com/tag/全天秒速赛车计划数据【28c63.com】 http://cn.engadget.com/tag/六合2m彩票【28c63.com】 http://cn.engadget.com/tag/哪个彩票软件最好【28c63.com】 http://cn.engadget.com/tag/500彩票安卓版【28c63.com】 http://cn.engadget.com/tag/幸运飞艇死公式【28c63.com】 http://cn.engadget.com/tag/pk10开奖聚彩【28c63.com】 http://cn.engadget.com/tag/体育彩票怎么查询结果【28c63.com】 http://cn.engadget.com/tag/广东快乐十分历史彩乐乐【28c63.com】 http://cn.engadget.com/tag/幸运飞艇官方在哪里【28c63.com】 http://cn.engadget.com/tag/中国彩票31选7【28c63.com】 http://cn.engadget.com/tag/电信话费怎么买彩票【28c63.com】 http://cn.engadget.com/tag/幸运飞艇手机高频开奖直播【28c63.com】 http://cn.engadget.com/tag/彩票玩家交流群【28c63.com】 http://cn.engadget.com/tag/福利彩票2019015【28c63.com】 http://cn.engadget.com/tag/广东快乐十分怎样下注【28c63.com】 http://cn.engadget.com/tag/幸运飞艇官网开奖视频【28c63.com】 http://cn.engadget.com/tag/福利彩票6十1开奖结果【28c63.com】 http://cn.engadget.com/tag/广东快乐十分玩法技巧【28c63.com】 http://cn.engadget.com/tag/幸运飞艇微信二维码【28c63.com】 http://cn.engadget.com/tag/pk10彩控视频【28c63.com】 http://cn.engadget.com/tag/时时彩开奖结果【28c63.com】 http://cn.engadget.com/tag/幸运飞艇龙虎最多看过几期【28c63.com】 http://cn.engadget.com/tag/时时彩五码缩后三直选【28c63.com】 http://cn.engadget.com/tag/吉祥8彩票官网【28c63.com】 http://cn.engadget.com/tag/福彩幸运农场开奖结果【28c63.com】 http://cn.engadget.com/tag/幸运彩票的抽奖网址【28c63.com】 http://cn.engadget.com/tag/11选五彩票带单老师【28c63.com】 http://cn.engadget.com/tag/新网彩科技的彩票网站【28c63.com】 http://cn.engadget.com/tag/幸运飞艇开奖最快的官网【28c63.com】 http://cn.engadget.com/tag/pk10一码方法【28c63.com】 http://cn.engadget.com/tag/3d彩票技巧和规律【28c63.com】 http://cn.engadget.com/tag/秒速时时彩大小规律【28c63.com】 http://cn.engadget.com/tag/微信版pk10网盘【28c63.com】 http://cn.engadget.com/tag/东森平台【28c63.com】 http://cn.engadget.com/tag/重庆幸运农场logo【28c63.com】 http://cn.engadget.com/tag/北京pk10大富翁【28c63.com】 http://cn.engadget.com/tag/中国福彩网能买彩票吗【28c63.com】 http://cn.engadget.com/tag/幸运农场计划人工软件【28c63.com】 http://cn.engadget.com/tag/pk10自动投注网站【28c63.com】 http://cn.engadget.com/tag/彩票报纸大全【28c63.com】 http://cn.engadget.com/tag/幸运飞艇长龙最长几把【28c63.com】 http://cn.engadget.com/tag/北京pk10在线人工计划【28c63.com】 http://cn.engadget.com/tag/九万彩票什么时候出的【28c63.com】 http://cn.engadget.com/tag/幸运农场一天开多少期【28c63.com】 http://cn.engadget.com/tag/微信投注pk10【28c63.com】 http://cn.engadget.com/tag/彩票500vip可靠吗【28c63.com】 http://cn.engadget.com/tag/幸运飞艇预测计划网【28c63.com】 http://cn.engadget.com/tag/盛世pk10直播【28c63.com】 http://cn.engadget.com/tag/爱乐透彩票软件可靠吗【28c63.com】 http://cn.engadget.com/tag/秒速时时彩开奖视频【28c63.com】 http://cn.engadget.com/tag/pk10超神单双【28c63.com】 http://cn.engadget.com/tag/今天体育彩票6加1【28c63.com】 http://cn.engadget.com/tag/重庆幸运农场综合走势【28c63.com】 http://cn.engadget.com/tag/北京pk10报号【28c63.com】 http://cn.engadget.com/tag/山东互联网彩票【28c63.com】 http://cn.engadget.com/tag/幸运飞艇开奖视频网址【28c63.com】 http://cn.engadget.com/tag/pk10怎么看冷号热号【28c63.com】 http://cn.engadget.com/tag/中国福彩网能买彩票吗【28c63.com】 http://cn.engadget.com/tag/幸运飞艇宝典下载【28c63.com】 http://cn.engadget.com/tag/pk10免费软件【28c63.com】 http://cn.engadget.com/tag/重庆福利彩票幸运农场【28c63.com】 http://cn.engadget.com/tag/秒速时时彩是新德里【28c63.com】 http://cn.engadget.com/tag/彩票进球的玩法【28c63.com】 http://cn.engadget.com/tag/重庆福利彩票幸运农场【28c63.com】 http://cn.engadget.com/tag/幸运农场APP【28c63.com】 http://cn.engadget.com/tag/幸运飞艇包9码【28c63.com】 http://cn.engadget.com/tag/pk10模拟盘【28c63.com】 http://cn.engadget.com/tag/彩宝彩票作弊器【28c63.com】 http://cn.engadget.com/tag/重庆幸运农场在线计划【28c63.com】 http://cn.engadget.com/tag/北京pk10猜冠军技巧大全【28c63.com】 http://cn.engadget.com/tag/天游彩票软件【28c63.com】 http://cn.engadget.com/tag/幸运飞艇群微信群【28c63.com】 http://cn.engadget.com/tag/福彩赛车pk10【28c63.com】 http://cn.engadget.com/tag/天天中彩票有彩金吗【28c63.com】 http://cn.engadget.com/tag/重庆幸运农场时间【28c63.com】 http://cn.engadget.com/tag/彩票跑马计划【28c63.com】 http://cn.engadget.com/tag/998彩票是真的吗?【28c63.com】 http://cn.engadget.com/tag/幸运飞艇杀两码公式【28c63.com】 http://cn.engadget.com/tag/体育彩票怎么买法【28c63.com】 http://cn.engadget.com/tag/广东快乐十分稳赚技巧大全【28c63.com】 http://cn.engadget.com/tag/幸运飞艇官网赔率【28c63.com】 http://cn.engadget.com/tag/富人买股票穷人买彩票【28c63.com】 http://cn.engadget.com/tag/卓易彩票 买版多多【28c63.com】 http://cn.engadget.com/tag/九州网站有没有幸运飞艇【28c63.com】 http://cn.engadget.com/tag/类似盛源彩票【28c63.com】 http://cn.engadget.com/tag/广东快乐十分推荐任3【28c63.com】 http://cn.engadget.com/tag/彩票团队qq号【28c63.com】 http://cn.engadget.com/tag/极速飞车彩票技巧【28c63.com】 http://cn.engadget.com/tag/重庆幸运农场快乐十分走试图【28c63.com】 http://cn.engadget.com/tag/江苏体育彩票7位数24期【28c63.com】 http://cn.engadget.com/tag/领航娱乐彩票注册【28c63.com】 http://cn.engadget.com/tag/重庆幸运农场计划软件【28c63.com】 http://cn.engadget.com/tag/后三组选包胆这么玩【28c63.com】 http://cn.engadget.com/tag/ba平台【28c63.com】 http://cn.engadget.com/tag/秒速时时彩选开奖网【28c63.com】 http://cn.engadget.com/tag/67彩票 国际官网平台【28c63.com】 http://cn.engadget.com/tag/乐天彩票不能提款【28c63.com】 http://cn.engadget.com/tag/新一代幸运飞艇手机版计划【28c63.com】 http://cn.engadget.com/tag/北京pk10冠亚军单式【28c63.com】 http://cn.engadget.com/tag/彩票728【28c63.com】 http://cn.engadget.com/tag/京东彩票网站吗【28c63.com】 http://cn.engadget.com/tag/手机彩票在线投注【28c63.com】 http://cn.engadget.com/tag/福彩幸运农场走势图表【28c63.com】 http://cn.engadget.com/tag/3cp彩票平台可信吗【28c63.com】 http://cn.engadget.com/tag/必赢彩票还能从新开吗?【28c63.com】 http://cn.engadget.com/tag/幸运飞艇开奖全国统一?【28c63.com】 http://cn.engadget.com/tag/北京pk10是那里开奖的【28c63.com】 http://cn.engadget.com/tag/网络彩票那个正规【28c63.com】 http://cn.engadget.com/tag/幸运飞艇有什么技巧【28c63.com】 http://cn.engadget.com/tag/pk10改单【28c63.com】 http://cn.engadget.com/tag/北京pk10推荐计划【28c63.com】 http://cn.engadget.com/tag/比较大的彩票网【28c63.com】 http://cn.engadget.com/tag/千金城彩票正规吗【28c63.com】 http://cn.engadget.com/tag/幸运农场平台注册【28c63.com】 http://cn.engadget.com/tag/彩票授权书【28c63.com】 http://cn.engadget.com/tag/怎么在手机上买彩票啊【28c63.com】 http://cn.engadget.com/tag/幸运飞艇最长单双的龙【28c63.com】 http://cn.engadget.com/tag/什么彩票是正规的【28c63.com】 http://cn.engadget.com/tag/彩票快三群【28c63.com】 http://cn.engadget.com/tag/掌上彩票APP【28c63.com】 http://cn.engadget.com/tag/团彩网能买彩票了【28c63.com】 http://cn.engadget.com/tag/幸运飞艇玩外围冠军号【28c63.com】 http://cn.engadget.com/tag/北京pk10计划公式【28c63.com】 http://cn.engadget.com/tag/互联网彩票行业情况【28c63.com】 http://cn.engadget.com/tag/幸运飞艇滚动开奖直播【28c63.com】 http://cn.engadget.com/tag/pk10羸钱技巧【28c63.com】 http://cn.engadget.com/tag/晋江华洲体育彩票网点【28c63.com】 http://cn.engadget.com/tag/幸运飞艇怎么买?【28c63.com】 http://cn.engadget.com/tag/北京赛车pk10直播预测【28c63.com】 http://cn.engadget.com/tag/8828彩票平台安全吗【28c63.com】 http://cn.engadget.com/tag/一分时时彩【28c63.com】 http://cn.engadget.com/tag/中国休育彩票【28c63.com】 http://cn.engadget.com/tag/幸运农场能看直播吗【28c63.com】 http://cn.engadget.com/tag/pk10定胆【28c63.com】 http://cn.engadget.com/tag/500vip彩票上中了20万【28c63.com】 http://cn.engadget.com/tag/幸运飞艇微【28c63.com】 http://cn.engadget.com/tag/彩票老师直播【28c63.com】 http://cn.engadget.com/tag/秒速时时彩稳赚技巧【28c63.com】 http://cn.engadget.com/tag/武汉福利彩票【28c63.com】 http://cn.engadget.com/tag/盈发彩票是真的吗【28c63.com】 http://cn.engadget.com/tag/幸运飞艇杀5码【28c63.com】 http://cn.engadget.com/tag/pk10计划交流【28c63.com】 http://cn.engadget.com/tag/彩票快乐十分开奖查询【28c63.com】 http://cn.engadget.com/tag/幸运飞艇稳赢【28c63.com】 http://cn.engadget.com/tag/永盛彩票靠谱吗【28c63.com】 http://cn.engadget.com/tag/幸运飞艇提示【28c63.com】 http://cn.engadget.com/tag/腾龙pk10缩水【28c63.com】 http://cn.engadget.com/tag/一定牛彩票是正规的吗【28c63.com】 http://cn.engadget.com/tag/幸运飞艇看走势【28c63.com】 http://cn.engadget.com/tag/599彩票【28c63.com】 http://cn.engadget.com/tag/重庆幸运农场即时开奖【28c63.com】 http://cn.engadget.com/tag/乐都彩票是真的吗【28c63.com】 http://cn.engadget.com/tag/75秒极速赛车定位技术【28c63.com】 http://cn.engadget.com/tag/幸运农场选号【28c63.com】 http://cn.engadget.com/tag/幸运飞艇微信群群规【28c63.com】 http://cn.engadget.com/tag/pk10北京赛车缩水软件【28c63.com】 http://cn.engadget.com/tag/北京pk10冠亚和单双【28c63.com】 http://cn.engadget.com/tag/2019彩票什么时间开市【28c63.com】 http://cn.engadget.com/tag/幸运飞艇没规律【28c63.com】 http://cn.engadget.com/tag/北京pk10走势图 投注【28c63.com】 http://cn.engadget.com/tag/上海彩票快3开奖结果【28c63.com】 http://cn.engadget.com/tag/幸运飞艇开机时间【28c63.com】 http://cn.engadget.com/tag/彩友多上买彩票合法吗【28c63.com】 http://cn.engadget.com/tag/广东快乐十分20选8开奖走势图【28c63.com】 http://cn.engadget.com/tag/幸运飞艇交流群【28c63.com】 http://cn.engadget.com/tag/微信上可以买彩票【28c63.com】 http://cn.engadget.com/tag/广东快乐十分20选8复式玩法【28c63.com】 http://cn.engadget.com/tag/金亚洲彩票开户【28c63.com】 http://cn.engadget.com/tag/福利彩票官方网站【28c63.com】 http://cn.engadget.com/tag/幸运农场幸运五是几倍【28c63.com】 http://cn.engadget.com/tag/pk10彩票计划软件【28c63.com】 http://cn.engadget.com/tag/卓易彩票 版官方最【28c63.com】 http://cn.engadget.com/tag/幸运飞艇开奖计划图【28c63.com】 http://cn.engadget.com/tag/55彩票正规吗【28c63.com】 http://cn.engadget.com/tag/秒速赛车开奖号码有规律嘛【28c63.com】 http://cn.engadget.com/tag/广西快3开奖【28c63.com】 http://cn.engadget.com/tag/太子彩票软件【28c63.com】 http://cn.engadget.com/tag/幸运飞艇号码规律统计【28c63.com】 http://cn.engadget.com/tag/冠军pk10【28c63.com】 http://cn.engadget.com/tag/广东快乐十分稳赚计划软件【28c63.com】 http://cn.engadget.com/tag/福彩河北快3开奖结果【28c63.com】 http://cn.engadget.com/tag/大赢家彩票充值【28c63.com】 http://cn.engadget.com/tag/幸运农场开奖号码【28c63.com】 http://cn.engadget.com/tag/体育彩票手机客户端【28c63.com】 http://cn.engadget.com/tag/广东快乐十分开奖信息【28c63.com】 http://cn.engadget.com/tag/现在为啥买不了彩票了【28c63.com】 http://cn.engadget.com/tag/玖壹彩票官方网【28c63.com】 http://cn.engadget.com/tag/秒速时时彩开奖结果【28c63.com】 http://cn.engadget.com/tag/大运彩票网公平吗【28c63.com】 http://cn.engadget.com/tag/广东快乐十分20选8开奖【28c63.com】 http://cn.engadget.com/tag/头奖彩票APP中过大奖吗【28c63.com】 http://cn.engadget.com/tag/海南彩票信用盘【28c63.com】 http://cn.engadget.com/tag/幸运飞艇彩票分析【28c63.com】 http://cn.engadget.com/tag/qq30秒是真彩票吗【28c63.com】 http://cn.engadget.com/tag/福彩广东快乐十分【28c63.com】 http://cn.engadget.com/tag/北京赛车pk10开奖记录统计【28c63.com】 http://cn.engadget.com/tag/全国最大彩票网app【28c63.com】