HP 6125G HP 6125G & 6125G/XG Blade Switches Layer 2 - LAN Switching Co - Page 16

Configuration restrictions and guidelines, Configuration procedure, Configuring jumbo frame support

Page 16 highlights

Configuration restrictions and guidelines • On an interface that is physically down, you can only perform internal loopback testing. On an interface administratively shut down, you can perform neither internal nor external loopback testing. • You cannot configure the speed, duplex, mdi, or shutdown command on the Ethernet interface during loopback testing. • During loopback testing, the Ethernet interface operates in full duplex mode. When you disable loopback testing, the interface returns to its duplex setting. Configuration procedure To enable loopback testing on an Ethernet interface: Step 1. Enter system view. 2. Enter Ethernet interface view. Command system-view interface interface-type interface-number 3. Enable loopback testing. loopback { external | internal } 4. Disable loopback testing. undo loopback Remarks N/A N/A Optional. Disabled by default. After loopback testing is complete, to avoid influence on normal data packet forwarding, use this command to disable loopback testing on the interface. Configuring jumbo frame support An Ethernet interface might receive some frames larger than the standard Ethernet frame size (called "jumbo frames") during high-throughput data exchanges such as file transfers. Usually, an Ethernet interface discards jumbo frames. With jumbo frame support enabled, the interface can process frames larger than the standard Ethernet frame size yet within the specified range. To configure jumbo frame support in interface view: Step 1. Enter system view. 2. Enter Ethernet interface view. Command system-view interface interface-type interface-number 3. Configure jumbo frame support. jumboframe enable [ value ] Remarks N/A N/A By default, the switch allows jumbo frames within 9216 bytes to pass through Ethernet interfaces. If you set the value argument multiple times, the latest configuration takes effect. 7

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231

7
Configuration restrictions and guidelines
On an interface that is physically down, you can only perform internal loopback testing. On an
interface administratively shut down, you can perform neither internal nor external loopback
testing.
You cannot configure the
speed
,
duplex
,
mdi
, or
shutdown
command on the Ethernet interface
during loopback testing.
During loopback testing, the Ethernet interface operates in full duplex mode. When you disable
loopback testing, the interface returns to its duplex setting.
Configuration procedure
To enable loopback testing on an Ethernet interface:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter Ethernet interface view.
interface
interface-type
interface-number
N/A
3.
Enable loopback testing.
loopback
{
external
|
internal
}
Optional.
Disabled by default.
4.
Disable loopback testing.
undo loopback
After loopback testing is complete,
to avoid influence on normal data
packet forwarding, use this
command to disable loopback
testing on the interface.
Configuring jumbo frame support
An Ethernet interface might receive some frames larger than the standard Ethernet frame size (called
"jumbo frames") during high-throughput data exchanges such as file transfers. Usually, an Ethernet
interface discards jumbo frames. With jumbo frame support enabled, the interface can process frames
larger than the standard Ethernet frame size yet within the specified range.
To configure jumbo frame support in interface view:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter Ethernet
interface view.
interface
interface-type
interface-number
N/A
3.
Configure jumbo
frame support.
jumboframe enable
[
value
]
By default, the switch allows jumbo frames within
9216 bytes to pass through Ethernet interfaces.
If you set the
value
argument multiple times, the
latest configuration takes effect.