H3C S7500X Series User manual

H3C S7500X Switch Series
Interface Configuration Guide
New H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 7585P05 and later versions
Document version: 6W100-20200529

Copyright © 2020, New H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior written
consent of New H3C Technologies Co., Ltd.
Trademarks
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this
document are the property of their respective owners.
Notice
The information in this document is subject to change without notice. All contents in this document, including
statements, information, and recommendations, are believed to be accurate, but they are presented without
warranty of any kind, express or implied. H3C shall not be liable for technical or editorial errors or omissions
contained herein.

Preface
This configuration guide covers the configuration of various interfaces.
This preface includes the following topics about the documentation:
•
Audience.
•
Conventions.
•
Documentation feedback.
Audience
This documentation is intended for:
•
Network planners.
•
Field technical support and servicing engineers.
•
Network administrators working with the S7500E switch series.
Conventions
The following information describes the conventions used in the documentation.
Command conventions
Convention
Description
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars,
from which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select a minimum of one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign
can be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention
Description
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the New User window opens; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create >
Folder.

Symbols
Convention
Description
WARNING! An alert that calls attention to important information that if not understood or followed
can result in personal injury.
CAUTION:
An alert that calls attention to important information that if not understood or followed
can result in data loss, data corruption, or damage to hardware or software.
IMPORTANT:
An alert that calls attention to essential information.
NOTE:
An alert that contains additional or supplementary information.
TIP:
An alert that provides helpful information.
Network topology icons
Convention
Description
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that
supports Layer 2 forwarding and other Layer 2 features.
Represents an access controller, a unified wired-WLAN module, or the access
controller engine on a unified wired-WLAN switch.
Represents an access point.
Represents a wireless terminator unit.
Represents a wireless terminator.
Represents a mesh access point.
Represents omnidirectional signals.
Represents directional signals.
Represents a security product, such as a firewall, UTM, multiservice security
gateway, or load balancing device.
Represents a security module, such as a firewall, load balancing, NetStream, SSL
VPN, IPS, or ACG module.
Examples provided in this document
Examples in this document might use devices that differ from your device in hardware model,
configuration, or software version. It is normal that the port numbers, sample output, screenshots,
and other information in the examples differ from what you have on your device.
T
T
T
T

Documentation feedback
You can e-mail your comments about product documentation to [e-mail].
We appreciate your comments.

i
Contents
Bulk configuring interfaces·············································································1
Configuration restrictions and guidelines···········································································································1
Configuration procedure·····································································································································1
Displaying and maintaining bulk interface configuration····················································································2

1
Bulk configuring interfaces
You can enter interface range view to bulk configure multiple interfaces with the same feature
instead of configuring them one by one. For example, you can execute the shutdown command in
interface range view to shut down a range of interfaces.
Configuration restrictions and guidelines
When you bulk configure interfaces in interface range view, follow these restrictions and guidelines:
•
In interface range view, only the commands supported by the first interface are available. The
first interface is specified with the interface range command.
•
Before you configure an interface as the first interface in an interface range, make sure you can
enter the view of the interface by using the interface interface-type { interface-number |
interface-number.subnumber } command.
•
Do not assign both an aggregate interface and any of its member interfaces to an interface
range. Some commands, after being executed on both an aggregate interface and its member
interfaces, can break up the aggregation.
•
No limit is set on the maximum number of interfaces in an interface range. The more interfaces
in an interface range, the longer the command execution time.
•
The maximum number of interface range names is limited only by the system resources. To
guarantee bulk interface configuration performance, configure fewer than 1000 interface range
names.
•
After a command is executed in interface range view, one of the following situations might
occur:
The system displays an error message and stays in interface range view. It means that the
execution failed on member interfaces in the interface range.
−If the execution failed on the first member interface in the interface range, the command
is not executed on any member interfaces.
−If the execution failed on non-first member interfaces, the command takes effect on the
other member interfaces.
The system returns to system view. It means that:
−The command is supported in both system view and interface view.
−The execution failed on a member interface in interface range view and succeeded in
system view.
−The command is not executed on the subsequent member interfaces.
You can use the display this command to verify the configuration in interface view of each
member interface. In addition, if the configuration in system view is not needed, use the
undo form of the command to remove the configuration.
Configuration procedure
Step Command Remarks
1. Enter system view. system-view N/A

2
Step Command Remarks
2. Enter interface range
view.
•interface range
{ interface-type
interface-number [ to
interface-type
interface-number ] } &<1-24>
•interface range name name
[ interface { interface-type
interface-number [ to
interface-type
interface-number ] }
&<1-24> ]
By using the interface range name
command, you assign a name to an
interface range and can specify this
name rather than the interface range
to enter the interface range view.
3. (Optional.) Display
commands available for
the first interface in the
interface range.
Enter a question mark (?) at the
interface range prompt. N/A
4. Use available
commands to configure
the interfaces. Available commands depend on
the interface. N/A
5. (Optional.) Verify the
configuration. display this N/A
Displaying and maintaining bulk interface
configuration
Execute the display command in any view.
Task Command
Display information about the interface ranges
created by using the interface range name
command. display interface range [name name ]

i
Contents
Configuring Ethernet interfaces ·····································································1
Configuring a management Ethernet interface ··································································································1
Ethernet interface naming conventions··············································································································2
Configuring common Ethernet interface settings·······························································································2
Configuring a combo interface (single combo interface)············································································2
Splitting a 40-GE interface and combining 10-GE breakout interfaces······················································3
Changing the interface type of 100-GE interfaces in batches····································································4
Configuring basic settings of an Ethernet interface or subinterface···························································5
Configuring an Ethernet subinterface·········································································································6
Configuring the link mode of an Ethernet interface····················································································7
Configuring jumbo frame support···············································································································7
Configuring physical state change suppression on an Ethernet interface ·················································8
Configuring dampening on an Ethernet interface·······················································································9
Enabling link flapping protection on an interface······················································································10
Configuring FEC·······································································································································11
Enabling loopback testing on an Ethernet interface·················································································12
Configuring generic flow control on an Ethernet interface ·······································································12
Enabling EEE on an Ethernet interface····································································································13
Setting the statistics polling interval·········································································································14
Forcibly bringing up a fiber port················································································································14
Configuring a Layer 2 Ethernet interface ·········································································································16
Configuring storm suppression ················································································································16
Configuring storm control on an Ethernet interface··················································································17
Setting speed options for autonegotiation on an Ethernet interface ························································18
Setting the MDIX mode of an Ethernet interface······················································································19
Testing the cable connection of an Ethernet interface·············································································20
Enabling bridging on an Ethernet interface······························································································20
Configuring a Layer 3 Ethernet interface or subinterface·················································································21
Setting the MTU for an Ethernet interface or subinterface·······································································21
Displaying and maintaining an Ethernet interface or subinterface···································································21

1
Configuring Ethernet interfaces
The Switch Series supports Ethernet interfaces, management Ethernet interfaces, and Console
interfaces.
Your device supports the following types of Ethernet interfaces:
•
Layer 2 Ethernet interfaces—Physical Ethernet interfaces operating at the data link layer
(Layer 2) to switch packets.
•
Layer 3 Ethernet interfaces—Physical Ethernet interfaces operating at the network layer
(Layer 3) to route packets. You can assign an IP address to a Layer 3 Ethernet interface.
•
Layer-configurable Ethernet interfaces—Physical Ethernet interfaces that can be configured
to operate in bridge mode as Layer 2 Ethernet interfaces or in route mode as Layer 3 Ethernet
interfaces.
•
Layer 3 Ethernet subinterfaces—Logical interfaces operating at the network layer. You can
assign an IP address to a Layer 3 Ethernet subinterface. On a Layer 3 Ethernet interface, you
can create multiple Layer 3 subinterfaces.
This chapter describes how to configure management Ethernet interfaces and Ethernet interfaces.
Configuring a management Ethernet interface
About management Ethernet interface
A management Ethernet interface uses an RJ-45/LC connector. You can connect the interface to a
PC for software loading and system debugging, or connect it to a remote NMS for remote system
management.
Restrictions and guidelines
The management Ethernet interface can be a copper port or fiber port.
•
By default, the duplex mode is auto for a copper port and full for a fiber port. The duplex
command cannot modify the duplex mode to any value other than the default for the copper port
or fiber port.
•
By default, the speed is auto for a copper port and 1000 Mbps for a fiber port. The speed
command cannot modify the speed to any value other than the default for the copper port or
fiber port.
In standalone mode, when the switch has multiple management Ethernet interfaces, only the
management Ethernet interface on the active MPU processes management traffic.
In IRF mode, when an IRF system has multiple management Ethernet interfaces, only the
management Ethernet interface on the global active MPU processes management traffic.
Configuration procedure
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enter management
Ethernet interface view. interface
M-GigabitEthernet
interface-number N/A
3. (Optional.) Set the
interface description.description text The default setting is
M-GigabitEthernet0/0/0 Interface.
4. (Optional.) Shut down
the interface. shutdown By default, the management Ethernet
interface is up.