HP 6120G/XG HP ProCurve Series 6120 Blade Switches Advanced Traffic Management - Page 72

Configuration, Syntax

Page 72 highlights

Note Note Static Virtual LANs (VLANs) Special VLAN Types 4. Test the management VLAN from all of the management stations authorized to use the Management VLAN, including any SNMP-based network management stations. Ensure that you include testing any Management VLAN links between switches. If you configure a Management VLAN on a switch by using a Telnet connection through a port that is not in the Management VLAN, then you will lose management contact with the switch if you log off your Telnet connection or execute write memory and reboot the switch. Configuration In order to enable management-vlan, oobm must be disabled first, since the two are mutually exclusive. Syntax: [no] management-vlan < vlan-id | vlan-name > Configures an existing VLAN as the management VLAN. The no form disables the management VLAN and returns the switch to its default management operation. Default: Disabled. In this case, the VLAN returns to standard VLAN operation. For example, suppose you have already configured a VLAN named My_VLAN with a VID of 100. Now you want to configure the switch to do the following: ■ Use My_VLAN as a Management VLAN (tagged, in this case) to connect port A1 on switch "A" to a management station. (The management station includes a network interface card with 802.1Q tagged VLAN capability.) ■ Use port A2 to extend the Management VLAN to port B1 (which is already configured as a tagged member of My_VLAN) on an adjacent Procurve switch that supports the Management VLAN feature. Switch "A" Switch "B" A1 A2 B1 Figure 2-31. Illustration of Configuration Example ProCurve (config)# management-vlan 100 ProCurve (config)# vlan 100 tagged a1 ProCurve (config)# vlan 100 tagged a2 2-49

  • 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

2-49
Static Virtual LANs (VLANs)
Special VLAN Types
4.
Test the management VLAN from all of the management stations autho-
rized to use the Management VLAN, including any SNMP-based network
management stations. Ensure that you include testing any Management
VLAN links between switches.
Note
If you configure a Management VLAN on a switch by using a Telnet connection
through a port that is not in the Management VLAN, then you will lose
management contact with the switch if you log off your Telnet connection or
execute
write memory
and
reboot
the switch.
Configuration
Note
In order to enable management-vlan, oobm must be disabled first, since the
two are mutually exclusive.
For example, suppose you have already configured a
VLAN
named
My_VLAN
with a VID of 100. Now you want to configure the switch to do the following:
Use
My_VLAN
as a Management VLAN (tagged, in this case) to connect
port A1 on switch “A” to a management station. (The management station
includes a network interface card with 802.1Q tagged VLAN capability.)
Use port A2 to extend the Management VLAN to port B1 (which is already
configured as a tagged member of
My_VLAN
) on an adjacent Procurve
switch that supports the Management VLAN feature.
Figure 2-31.
Illustration of Configuration Example
ProCurve (config)# management-vlan 100
ProCurve (config)# vlan 100 tagged a1
ProCurve (config)# vlan 100 tagged a2
Syntax:
[no] management-vlan <
vlan-id | vlan-name
>
Configures an existing VLAN as the management VLAN. The
no
form disables the management VLAN and returns the switch to its
default management operation. Default: Disabled. In this case, the
VLAN returns to standard VLAN operation.
Switch
B
Switch
A
A1
B1
A2