HPE FlexNetwork 10500 SERIES Troubleshooting Manual
  1. Manuals
  2. Brands
  3. HPE Manuals
  4. Network Router
  5. FlexNetwork 10500 SERIES
  6. Troubleshooting manual

HPE FlexNetwork 10500 SERIES Troubleshooting Manual

Hide thumbs Also See for FlexNetwork 10500 SERIES:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual, Installation Manual
HPE FlexNetwork 10500 Switch Series

Troubleshooting Guide

Part number: 5200-1913
Software version: 10500-CMW710-R7524
Document version: 6W100-20161230
The information in this document is subject to change without notice.
© Copyright 2016 Hewlett Packard Enterprise Development LP

Advertisement

Table of Contents
loading

Related Manuals for HPE FlexNetwork 10500 SERIES

Summary of Contents for HPE FlexNetwork 10500 SERIES

  • Page 1: Troubleshooting Guide

    HPE FlexNetwork 10500 Switch Series Troubleshooting Guide Part number: 5200-1913 Software version: 10500-CMW710-R7524 Document version: 6W100-20161230 The information in this document is subject to change without notice. © Copyright 2016 Hewlett Packard Enterprise Development LP...

  • Page 2: Table Of Contents

    Contents Introduction ····················································································· 1 General guidelines ····················································································································· 1 Collecting log and operating information ························································································· 1 Collecting common log messages ··························································································· 2 Collecting diagnostic log messages ························································································· 4 Collecting operating statistics ································································································· 5 Contacting technical support ········································································································ 6 Dealing with password loss ································································ 7 Dealing with console login password loss ························································································...
  • Page 3 Solution ··························································································································· 44 Transceiver module failure ········································································································· 45 Symptom ························································································································· 45 Solution ··························································································································· 45 Reporting non-HPE transceiver modules ······················································································· 47 Symptom ························································································································· 47 Troubleshooting flowchart ··································································································· 48 Solution ··························································································································· 48 Failure to support digital diagnosis on a transceiver module ······························································ 48 Symptom ·························································································································...
  • Page 4 Related commands ·················································································································· 55 Troubleshooting IRF ······································································· 55 IRF fabric setup failure ·············································································································· 56 Symptom ························································································································· 56 Troubleshooting flowchart ··································································································· 57 Solution ··························································································································· 58 IRF split ································································································································· 60 Symptom ························································································································· 60 Troubleshooting flowchart ··································································································· 60 Solution ··························································································································· 60 BFD MAD failure ······················································································································ 61 Symptom ·························································································································...

  • Page 5: Introduction

    Introduction This document provides information about troubleshooting common software and hardware problems with 10500 switches. This document applies to Release 10500-CMW710-R7524. General guidelines IMPORTANT: To prevent a problem from causing loss of configuration, save the configuration each time you finish configuring a feature.

  • Page 6: Collecting Common Log Messages

    * Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP * Without the owner's prior written consent, * no decompiling or reverse-engineering shall be allowed. ****************************************************************************** <HPE> logfile save The contents in the log file buffer have been saved to the file flash:/logfile/logfile.log <HPE> switchback...
  • Page 7 * Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP * Without the owner's prior written consent, * no decompiling or reverse-engineering shall be allowed. ****************************************************************************** <HPE> logfile save The contents in the log file buffer have been saved to the file flash:/logfile/logfile.log <HPE> switchback...

  • Page 8: Collecting Diagnostic Log Messages

    * Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP * Without the owner's prior written consent, * no decompiling or reverse-engineering shall be allowed. ****************************************************************************** <HPE> diagnostic-logfile save The contents in the diagnostic log file buffer have been saved to the file flash:/diagfile/diagfile.log <HPE> switchback...

  • Page 9: Collecting Operating Statistics

    Directory of flash:/diagfile 0 -rw- 161321 Jul 11 2013 16:16:00 diagfile.log 1021104 KB total (421416 KB free) # Display the diagnostic log file on each standby MPU for the default MDC: In standalone mode, display the diagnostic log file on the standby MPU. ...

  • Page 10: Contacting Technical Support

    16:52:51 UTC Tue 19/07/2016 ================================================= ===============display version=============== HPE Comware Software, Version 7.1.070, Release 7523P01 Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP HP 10504 uptime is 0 weeks, 0 days, 1 hour, 19 minutes Last reboot reason : USER reboot Boot image: flash:/10500-cmw710-boot-r7523P01.bin...

  • Page 11: Dealing With Password Loss

    Technical support registration numbers (if applicable). This information will help the support engineer assist you as quickly as possible. The following is the contact of Hewlett Packard Enterprise Support for networking products: http://www.hpe.com/support/hpesc Dealing with password loss Dealing with console login password loss Use either of the following methods: •...

  • Page 12: Using Bootware Menus To Change The Console Login Password

    user-role level-15 user-role network-admin user-role network-operator return The output shows that VTY 0 has the user role level-15. You have the right to change the console login password. Configure password authentication for console login and set the password. You can also configure a different login authentication mode.
  • Page 13 command-alias enable command-alias mapping undo no command-alias mapping quit exit command-alias mapping return end password-recovery enable • View the bootstrap information displayed when you access the extended BootWare menu. If the message "Password recovery capability is enabled." is displayed, password recovery capability is enabled.
  • Page 14 |<1> Boot System |<2> Enter Serial SubMenu |<3> Enter Ethernet SubMenu |<4> File Control |<5> Restore to Factory Default Configuration |<6> Skip Current System Configuration |<7> BootWare Operation Menu |<8> Skip Authentication for Console Login |<9> Storage Device Operation |<0> Reboot ============================================================================ Ctrl+Z: Access EXTENDED ASSISTANT MENU Ctrl+F: Format File System...
  • Page 15 [Sysname-line-aux1/1] return Save the running configuration to use the configuration at the next reboot. <Sysname> save The current configuration will be written to the device. Are you sure? [Y/N] :y Please input the file name(*.cfg)[flash:/default.cfg] (To leave the existing filename unchanged, press the enter key):default.cfg Validating file.
  • Page 16 Note: The current operating device is flash Enter < Storage Device Operation > to select device. ==========================<EXTENDED-BOOTWARE MENU>========================== |<1> Boot System |<2> Enter Serial SubMenu |<3> Enter Ethernet SubMenu |<4> File Control |<5> Restore to Factory Default Configuration |<6> Skip Current System Configuration |<7>...

  • Page 17: Dealing With Telnet Password Loss

    Booting Normal Extend BootWare The Extend BootWare is self-decompressing......... Done. After the device starts up, configure a new console login password. You can also configure a different login authentication mode. <Sysname> system-view [Sysname] line aux 1/1 [Sysname-line-aux1/1] authentication-mode password [Sysname-line-aux1/1] set authentication password simple 12345678 [Sysname-line-aux1/1] return Save the running configuration to use the configuration at the next reboot.

  • Page 18: Solution

    Solution CAUTION: Do not execute the save command before you complete the tasks in this section. The save operation overwrites the restored startup configuration file with the running configuration. To resolve the problem: Transfer a backup copy of the startup configuration file to the root directory of the default storage medium on each MPU: IMPORTANT: The device loads startup configuration files from the default storage medium.

  • Page 19: Related Commands

    "Troubleshooting system management" and "Troubleshooting ports." • For more information about the LEDs, see HPE FlexNetwork 10500 Switch Series Installation Guide. Configuration terminal display failure No display on the configuration terminal Symptom The configuration terminal does not have display when the switch is powered on.

  • Page 20: Garbled Display On The Configuration Terminal

    Garbled display on the configuration terminal Symptom The configuration terminal has a garbled display when the switch is powered on. Solution To resolve the problem: Verify that the following settings are configured for the terminal: Baud rate—9600.  Data bits—8. ...

  • Page 21: Solution

    Solution To resolve the problem: Verify that the system software image on the MPU is correct. a. Log in to the MPU through the console port and restart the switch. If the system reports that a CRC error occurs or that no system software image is available during the BootWare loading process, reload the system software image.

  • Page 22: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 2 Troubleshooting newly installed standby MPU boot failure Newly installed standby MPU boot failure New MPU Remove and reinstall Resolved? installed securely? the MPU Power sufficient? Add power modules Resolved? Same model as Replace the Resolved? the active MPU? standby MPU Same software version Upgrade the...

  • Page 23: Service Module Reboot Failure

    Verify that the MPU is the same model as the active MPU. If they are not the same model, replace the MPU with one that is the same model as the active MPU. Verify that the MPU runs the same software version as the active MPU. If the two MPUs run different software versions, upgrade the software version of the standby MPU to make sure the two MPUs run the same software version.

  • Page 24: Service Module Boot Failure

     Verify that the service module has loaded files. <Sysname> display logbuffer %May 3 13:27:17:086 2013 HPE DEVM/4/BOARD_LOADING: Board is loading file on Chassis 1 Slot 7. %May 3 13:27:17:647 2013 HPE DEVM/5/LOAD_FINISHED: Board has finished loading file on Chassis 1 Slot 7.

  • Page 25: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 4 Troubleshooting service module boot failure Newly installed service module boot failure Remove and reinstall Resolved? Installed securely? the module Power sufficient? Add power modules Resolved? Reload the system System software image Resolved? software image on the MPU correct? Upgrade the system System software image Resolved?

  • Page 26: Unexpected Card Reboot

    Execute the display logbuffer command to verify that the service module has loaded files. [Sysname]display logbuffer %May 3 13:27:17:086 2013 HPE DEVM/4/BOARD_LOADING: Board is loading file on Chassis 1 Slot 7. %May 3 13:27:17:647 2013 HPE DEVM/5/LOAD_FINISHED: Board has finished loading file on Chassis 1 Slot 7.

  • Page 27: Operating Power Module Failure

    Execute the command to identify the reason that caused the most recent reboot. HPE Comware Software, Version 7.1.070, Release 7523P01 Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP HP 10504 uptime is 0 weeks, 0 days, 2 hours, 11 minutes Last reboot reason : USER reboot ……...

  • Page 28: Newly Installed Power Module Failure

    Power 0 State: Normal Power 1 State: Absent Power 2 State: Absent Power 3 State: Absent Execute the display alarm command to view alarm information about the power module.  <Sysname> display alarm Slot Level Info INFO Power 1 is absent. INFO Power 2 is absent.

  • Page 29: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 6 Troubleshooting newly installed power module failure Newly installed power module failure The power module Remove and reinstall Resolved? in Absent state? the power module Power cord Connect the power Resolved? cord securely connected securely? Contact the support Solution To resolve the problem: Identify the operating state of the power module.

  • Page 30: Fan Tray Failure

    b. Remove and install the power module into an empty power module slot. Then execute the display power command to verify that the power module has changed to Normal state in the new slot. If the power module remains in Fault state, go to step 4. If the problem persists, contact Hewlett Packard Enterprise Support.

  • Page 31: Related Commands

    Verify that the fan tray is operating correctly. a. Identify whether the fan tray is faulty. − Execute the display environment command to view temperature information. If the temperature continues to rise, put your hand at the air outlet to feel if air is being expelled out of the air outlet.

  • Page 32: High Cpu Usage

    High CPU usage Symptom The sustained CPU usage is over 80% on a card. Troubleshooting flowchart Figure 8 Troubleshooting high CPU usage High CPU usage Route flapping problem? Verify that the device is not being attacked Problem resolved? Verify that no link loops exist Problem resolved? Locate the card that has a...

  • Page 33: Solution

    Solution Possible reasons for high CPU usage problems include: • Route flapping is taking place. • The device is being attacked. • A link loop exists. A link loop might cause broadcast storm and network flapping problems. If such a problem occurs, large amounts of protocol packets are sent to the CPU. Many interfaces on the device receive heavy traffic.
  • Page 34 − Verify that STP is enabled and correctly configured. − Verify that STP is operating correctly on neighboring devices. c. If the problem persists, an STP protocol calculation error might have occurred or interfaces are not blocked at the driver level as expected. Shut down the uplink interface of the loop or disconnect the cable and then connect the cable again to trigger STP recalculation to recover services.
  • Page 35 [<ffffffffc05587a8>] DRV_Sal_EVENT_Read+0x1f8/0x290 [system] [<ffffffffc07351e4>] drv_sysm_gdb_console+0xc4/0x2d0 [system] [<ffffffffc1a04114>] thread_boot+0x84/0xa0 [system] [<ffffffff8015c420>] kthread+0x130/0x140 [<ffffffff801183d0>] kernel_thread_helper+0x10/0x20 Iteration 3 of 5 ------------------------------ Kernel stack: [<ffffffff80355290>] schedule+0x570/0xde0 [<ffffffff80355da8>] schedule_timeout+0x98/0xe0 [<ffffffff802047e4>] ep_poll+0x4b4/0x5e0 [<ffffffffc05587a8>] DRV_Sal_EVENT_Read+0x1f8/0x290 [system] [<ffffffffc07351e4>] drv_sysm_gdb_console+0xc4/0x2d0 [system] [<ffffffffc1a04114>] thread_boot+0x84/0xa0 [system] [<ffffffff8015c420>] kthread+0x130/0x140 [<ffffffff801183d0>] kernel_thread_helper+0x10/0x20 Iteration 4 of 5 ------------------------------ Kernel stack: [<ffffffff80355290>] schedule+0x570/0xde0...

  • Page 36: High Memory Usage

    High memory usage Symptom The memory usage on a card is over 60% for more than 30 minutes. Troubleshooting flowchart Figure 9 Troubleshooting high memory usage High memory usage Display memory usage information Display memory call information Contact the support Solution IMPORTANT: As a best practice, do not reboot the device before you contact Hewlett Packard Enterprise Support.
  • Page 37 4096 kmalloc-4096 131016 kmalloc-131016 1718 2048 kmalloc-8 16777160 0 4096 kmalloc-16777160 2048 sgpool-64 inotify_event_cache 16328 kmalloc_dma-16328 LFIB_IlmEntryCache 1080 LFIB_IlmEntryCache 1464 MFW_FsCache L2VFIB_Ac_cache CCF_JOBDESC NS4_Aggre_TosSrcPre IPFS_CacheHash_cachep ---- More ---- Each value line shows the memory information for a slab. The Number field shows the number of objects (memory blocks) allocated to the module.

  • Page 38: Temperature Alarms

    ---- More ---- The first field of the output shows the number of objects. The remaining fields show the call information. Save the information displayed in the previous steps. Contact Hewlett Packard Enterprise Support. Temperature alarms Symptom Temperature alarms occur. Troubleshooting flowchart Figure 10 Troubleshooting temperature alarms Temperature alarms...

  • Page 39: Solution

    Solution To resolve the problem: Check the ambient temperature. If the ambient temperature is higher than 45°C (113°F), lower the ambient temperature by adding air conditioners or taking other heat dissipation measures. Check the device temperature. If the device temperature is higher than 68°C (154.4°F), use the display fan command to check the fan tray operating status.

  • Page 40: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 11 Troubleshooting link up failure on a port A port fails to come up Speed/duplex match Configure matching Resolved? on local and peer port? speed/duplex Network cable correct? Replace network cable Resolved? Local port operating correctly? Replace local port Resolved? Peer port operating correctly? Replace peer port...

  • Page 41: 1000-Mbps Sfp Fiber Port Fails To Come Up

    1000-Mbps SFP fiber port fails to come up Symptom A 1000-Mbps SFP fiber port cannot come up. Troubleshooting flowchart Figure 12 Troubleshooting link up failure on a port A port fails to come up Speed/duplex match Configuring matching Resolved? on local and peer port? speed/duplex Speed/duplex match on Configuring matching...
  • Page 42 c. Execute the display interface brief command to examine whether the speed and duplex mode of the port match the speed and duplex mode of the peer port. d. If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port.
  • Page 43 If the transceiver module is not operating correctly, replace it with a new HPE transceiver module that matches the fiber port.

  • Page 44: 10-Gigabit Sfp+/Xfp Fiber Port Fails To Come Up

    If the problem persists, contact Hewlett Packard Enterprise Support. 10-Gigabit SFP+/XFP fiber port fails to come up Symptom A 10-Gigabit SFP+/XFP fiber port cannot come up. Troubleshooting flowchart Figure 13 Troubleshooting link up failure on a port A 10-GE SFP+/XFP fiber port fails to come up Speed/duplex match Configure matching...

  • Page 45: Solution

    If the transceiver module is not operating correctly, replace it with a new HPE transceiver module that matches the fiber port.

  • Page 46: Troubleshooting Flowchart

    If the transceiver module is not operating correctly, replace it with a new HPE transceiver module that matches the fiber port.

  • Page 47: 100-Ge Cfp Fiber Port Fails To Come Up

    IMPORTANT: If a QSFP+ to SFP+ cable is used, use an optical attenuator to make sure the Tx power of the QSFP+ module stays below the Rx power of the SFP+ module. Verify that the fiber matches the transceiver module. If they do not match, replace the fiber with a new one that matches the transceiver module.

  • Page 48: A Port Goes Down

    If the transceiver module is not operating correctly, replace it with a new HPE transceiver module that matches the fiber port.

  • Page 49: Transceiver Module Failure

    − If the Tx power reaches the limit, verify that the local transceiver module and fiber are operating correctly. − If the Rx power reaches the limit, verify that the remote transceiver module and fiber are operating correctly. If the port is a copper port, set the speed and duplex mode for the local and peer ports. Verify that the link, peer device, and intermediate device are operating correctly.
  • Page 50 Field Description Transceiver info checksum error Transceiver information checksum error. Transceiver type and port configuration Transceiver type does not match port configuration. mismatch Transceiver type not supported by port The port does not support the transceiver type. hardware RX loss of signal Incoming (Rx) signal is lost.

  • Page 51: Reporting Non-Hpe Transceiver Modules

    <Sysname> display logbuffer %Oct 17 21:37:24:812 2011 nl-denbo-ro01 OPTMOD/4/PHONY_MODULE: -Chassis=2-Slot=3; GigabitEthernet2/3/0/5: This transceiver is NOT sold by HPE. HPE therefore shall NOT guarantee the normal function of the device or assume the maintenance responsibility thereof!

  • Page 52: Troubleshooting Flowchart

    If the Vendor Name field is HPE, the transceiver module might be an HPE transceiver module without an electrical label or a non-HPE transceiver module. b. If the Vendor Name field is not HPE, you can determine that this is not an HPE transceiver module. Replace it with an HPE transceiver module.

  • Page 53: Troubleshooting Flowchart

    Consult Hewlett Packard Enterprise Support about whether the transceiver module supports digital diagnosis. If the transceiver module vendor is identified as HPE and the transceiver module supports digital diagnosis but the problem persists, contact Hewlett Packard Enterprise Support. Error frames (for example, CRC errors) on a port...
  • Page 54 <Sysname> display interface gigabitethernet3/0/1 GigabitEthernet3/0/1 Current state: DOWN Line protocol state: DOWN Description: GigabitEthernet3/0/1 Interface Bandwidth: 1000000 kbps Maximum transmission unit: 1500 Internet address: 2.1.1.2/24 (primary) IP packet frame type: Ethernet II, hardware address: 0000-fc00-9276 IPv6 packet frame type: Ethernet II, hardware address: 0000-fc00-9276 Loopback is not set Media type is twisted pair, port hardware type is 1000_BASE_T Port priority: 0...

  • Page 55: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 18 Troubleshooting error frames (for example, CRC errors) on a port Error frames on the port Determine the type of error frames accumulating Optical power Replace it with a transceiver of transceiver module with correct optical Resolved? module correct? power Speed and...
  • Page 56 # Replace the local port with a new one to verify that the local port is operating correctly. − If error frames stop accumulating, replace the local port and send the error information to the technical support. − If error frames continue to accumulate, check the peer device and the intermediate link. If the value of the input overruns field is increasing, verify that the interface module is ...

  • Page 57: Failure To Receive Or Send Packets

    b. Determine whether the speed and duplex mode of the port match the speed and duplex mode of the peer port. c. If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port. Verify that the port and the link medium are operating correctly: a.

  • Page 58: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 19 Troubleshooting the failure to receive packets A port fails to receive or send packets View packet statistics of the port Port configurations affect Modify port Resolved? packet receiving or sending? configurations Use correct port and Port and link medium correct? Resolved link medium Contact the support...

  • Page 59: Related Commands

    from the display interface command is accumulating, you can determine that the port can receive packets. d. If the port is configured with STP, use the display stp brief command to verify that the port is not in the discarding state. e.

  • Page 60: Irf Fabric Setup Failure

    IRF fabric setup failure Symptom A chassis cannot be added to an IRF fabric.

  • Page 61: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 20 Troubleshooting IRF fabric setup failure IRF setup failure Number of chassis in the You cannot add the chassis to fabric fewer than the upper limit? the IRF fabric Replace with a chassis that is Same chassis model? the same model as existing IRF Resolved? member chassis...

  • Page 62: Solution

    IRF mode of the IRF fabric. Verify that the member chassis upper limit is not reached for the IRF mode. For more information about the upper limit, see HPE FlexNetwork 10500 Switch Series Virtual Technologies Configuration Guide for the software version.
  • Page 63 The switch might support transceiver modules or DAC cables that provide higher speed than SFP+, QSFP+, or CFP, depending on the software version and interface module model. For more information, see the latest HPE FlexNetwork 10500 Switch Series Virtual Technologies Configuration Guide.

  • Page 64: Irf Split

    The next system working mode is advance. b. If the system operating mode of the chassis is different than the IRF fabric, execute the system-working-mode command to change the system operating mode for the chassis. The changed mode will take effect after a reboot. 11.

  • Page 65: Bfd Mad Failure

    c. If transceiver modules and fibers are used, execute the display transceiver diagnosis command. Make sure the transmit and receive power has not exceeded the power specifications of the fiber module. d. Remove hardware problems that might cause recurring IRF split events: e.

  • Page 66: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 22 Troubleshooting BFD MAD failure BFD MAD failure BFD MAD link Correct the connections Resolved? connections correct? All BFD MAD Resolved? Bring up the ports ports up? BFD MAD VLAN interface Correct the settings Resolved? configured correctly? BFD MAD VLAN and ports Correct the settings Resolved?
  • Page 67 If you do not use an intermediate device, verify that each pair of member chassis has a  dedicated BFD MAD link. If you use an intermediate device, verify that each member chassis has a dedicated BFD  MAD link with the intermediate device. Verify that all physical ports used for BFD MAD are up: a.

  • Page 68: Lacp Mad Failure

    Member ports in the link Identify port-down event Resolved? aggregation always up? cause and remove the issue Contact the support Solution To resolve the problem: Verify that the intermediate device is an HPE device that supports extended LACPDUs for MAD.

  • Page 69: Pex Joining Eirf System Failure

    If the intermediate device does not support extended LACPDUs for MAD, replace the intermediate device, or use BFD MAD for split detection. Verify that each member chassis has a link in the link aggregation with the intermediate device. Verify that the link aggregation is operating in dynamic mode. To enable dynamic aggregation mode, use the link-aggregation mode dynamic command.

  • Page 70: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 24 Troubleshooting PEX joining eIRF system failure A device failed to join an eIRF system as a PEX The device cannot join the Is the device PEX capable? eIRF system as a PEX Enable eIRF capability Is eIRF capability enabled Resolved? on the parent fabric on the parent fabric?
  • Page 71 Verify that the Boot ROM of the device is PEX capable from the device's release notes. If the Boot ROM does not support PEX, upgrade the Boot ROM to a PEX-capable version. For more information, see software upgrade in HPE FlexNetwork 10500 Switch Series Fundamentals Configuration Guide.
  • Page 72 9. Set switch startup mode 0. Reboot Ctrl+F: Format File System Ctrl+P: Skip Super Password Ctrl+Y: Change Work Mode Ctrl+R: Download application to SDRAM and Run Ctrl+Z: Access EXTEND-ASSISTANT MENU Enter your choice(0-9): c. Enter Y to confirm the operating mode change. PE mode is disabled.
  • Page 73 Line protocol state: UP IP packet frame type: Ethernet II, hardware address: 5cdd-70b2-8758 Description: Pex101/0/0/29 Interface Bandwidth: 10000000 kbps Loopback is not set Media type is optical fiber, port hardware type is 10G_BASE_SR_SFP 10Gbps-speed mode, full-duplex mode Link speed type is autonegotiation, link duplex type is autonegotiation Maximum frame length: 9216 MDI type: Automdix Last clearing of counters: Never...
  • Page 74 The 10500 switch might support transceiver modules or DAC cables that provide higher speed than SFP+ or QSFP+, depending on the software version and interface module model. For more information, see the latest HPE FlexNetwork 10500 Switch Series Virtual Technologies Configuration Guide.

  • Page 75: Pex Split

    − On PEXs, the breakout interfaces of a 40-GE port cannot be connected to the parent fabric. For more information about the binding and connection restrictions, see HPE FlexNetwork 10500 Switch Series Virtual Technologies Configuration Guide. If the problem persists, contact Hewlett Packard Enterprise Support.

  • Page 76: Related Commands

    c. If transceiver modules and fibers are used, execute the display transceiver diagnosis command. Make sure the transmit and receive power has not exceeded the power specifications of the fiber module. d. Remove hardware problems that might cause recurring PEX split events: e.

  • Page 77: Acl Application Failure For Unsupported Acl Rules

    ACL application failure for unsupported ACL rules Symptom The system fails to apply a packet filter or an ACL-based QoS policy to the hardware. It displays an error message that an unsupported rule exists in the ACL. The following is a sample error message: Error: Slot=2 Fail to apply or refresh packet filter policy 3180 rule 5 on interface Vlan-interface20.

  • Page 78: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 27 Troubleshooting ACL application failure Failure to apply an ACL Hardware resources Delete unnecessary ACLs Resolved? are sufficient? Contact the support Solution Insufficient hardware resources might be insufficient Counter, Meter, or ACL resources. To resolve the problem: Check the ACL, Counter, and Meter resource usage for insufficiency.

  • Page 79: Acl Application Failure Without An Error Message

    EFP Counter IFP—Resource usage for inbound traffic.  EFP—Resource usage for outbound traffic.  Delete unnecessary ACLs to release resources if the failure is caused by ACL resource insufficiency. Delete unnecessary ACLs that use Meter or Counter resources if the failure is caused by Meter or Counter resource insufficiency.

  • Page 80: Related Commands

    a. Use the following commands to display ACLs that are used by QoS policies and packet filters: − display packet-filter − display qos policy user-defined − display traffic classifier user-defined b. Execute the display acl command to check for overlapping rules in the ACLs. For example, the following sample output shows that rule 0 in ACL 3100 and rule 0 in ACL 3009 can both match traffic sourced from 2.2.2.1.

  • Page 81: Service Module Assignment Failure

    Service module assignment failure Symptom The location command fails to assign a service module to an MDC. Troubleshooting flowchart Figure 29 Troubleshooting service module assignment failure Service module assignment failure Resources sufficient? Re-assign resources Resolved? The module belongs to Reclaim the module Resolved? another MDC? Contact the support...
  • Page 82 Name Quota(MB) Used(MB) Available(MB) ---------------------------------------------------------------- Admin 1318.7 34.0 1284.7 chassis 3 Slot 0: Used 583.5MB, Free 7289.1MB, Total 7872.6MB: Name Quota(MB) Used(MB) Available(MB) ---------------------------------------------------------------- Admin 7872.6 583.5 7289.1 mdcA 7872.6 7289.1 CPU: chassis 3 Slot 3: Name Weight Usage(%) ------------------------------------------------- Admin chassis 3 Slot 6: Name...

  • Page 83: Interface Assignment Failure

    mdc mdcA id 2 location chassis 3 slot 3 mdc start Return Reclaim the service module. In this example, the service module belongs to the default MDC. [Sysname-mdc-1-Admin]undo location chassis 3 slot 3 The configuration associated with the specified slot of MDC will be lost. Continue? [Y/N]:y Verify that the service module does not belong to the default MDC.

  • Page 84: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 30 Troubleshooting interface assignment failure Interface assignment failure Display interfaces of MDCs Reclaim the service module and its Interfaces assigned to interfaces from the Resolved? another MDC? MDC and re-assign them Assign all interfaces All interfaces on the on the service module Resolved? service module assigned to the...
  • Page 85 GigabitEthernet3/3/0/6 GigabitEthernet3/3/0/7 GigabitEthernet3/3/0/8 GigabitEthernet3/3/0/9 GigabitEthernet3/3/0/10 GigabitEthernet3/3/0/11 GigabitEthernet3/3/0/12 GigabitEthernet3/3/0/13 GigabitEthernet3/3/0/14 GigabitEthernet3/3/0/15 GigabitEthernet3/3/0/16 GigabitEthernet3/3/0/17 GigabitEthernet3/3/0/18 GigabitEthernet3/3/0/19 GigabitEthernet3/3/0/20 GigabitEthernet3/3/0/21 GigabitEthernet3/3/0/22 GigabitEthernet3/3/0/23 GigabitEthernet3/3/0/24 Ten-GigabitEthernet3/3/0/25 Ten-GigabitEthernet3/3/0/26 MDC mdcB's interface(s): M-GigabitEthernet1/0/0/0 [Sysname]mdc mdcA [Sysname-mdc-2-mdcA]display this mdc mdcA id 2 location chassis 3 slot 3 mdc start allocate interface GigabitEthernet3/3/0/1 to GigabitEthernet3/3/0/24 Ten-GigabitEthernet3/3/0/25 Ten-GigabitEthernet3/3/0/26 return...

  • Page 86: Related Commands

    location chassis 3 slot 3 mdc start allocate interface GigabitEthernet3/3/0/1 to GigabitEthernet3/3/0/24 Ten-GigabitEthernet3/3/0/25 to Ten-GigabitEthernet3/3/0/26 return [Sysname-mdc-3-mdcB]quit [Sysname]display mdc interface MDC Admin's interface(s): M-GigabitEthernet1/0/0/0 FortyGigE3/4/0/1 FortyGigE3/4/0/2 FortyGigE3/4/0/3 FortyGigE3/4/0/4 FortyGigE3/5/0/1 FortyGigE3/5/0/2 FortyGigE3/5/0/3 FortyGigE3/5/0/4 MDC mdcA's interface(s): M-GigabitEthernet1/0/0/0 MDC mdcB's interface(s): M-GigabitEthernet1/0/0/0 GigabitEthernet3/3/0/1 GigabitEthernet3/3/0/2 GigabitEthernet3/3/0/3...

Table of Contents