HP GbE2c HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Application Gu - Page 56

Port path cost, Spanning Tree Group configuration guidelines, Default Spanning Tree configuration - port mapping

Get HP GbE2c - Blc Layer 2/3 Fiber SFP Option PDF manuals and user guides
UPC - 808736802215
View all HP GbE2c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 56 highlights

Port path cost The port path cost assigns lower values to high-bandwidth ports, such as Gigabit Ethernet, to encourage their use. The objective is to use the fastest links so that the route with the lowest cost is chosen. A value of 0 indicates that port cost is computed dynamically based on link speed. This works when forcing link speed, so it does not just apply to "auto negotiated link speed". By default, all switch ports have the path cost set to 4, independent of the link speed. To use dynamic path cost, based on link speed, set the path cost to 0 (zero). For example, if the path cost is set to zero: • A 100 Mbps link receives a path cost of 19 • A 10 Mbps link receives a path cost of 100 Configure the port path cost using the following command: /cfg/l2/stp y/port x/cost Spanning Tree Group configuration guidelines This section provides important information on configuring Spanning Tree Groups (STGs). Default Spanning Tree configuration In the default configuration, a single STG with the ID of 1 includes all ports on the switch. It is called the default STG. All other STGs (except the default STG) are empty, and VLANs must be added by the user. You cannot assign ports directly to an STG. Add the ports to a VLAN, and add the VLAN to the STG. STGs 1-127 are enabled by default and assigned an ID number from 1 to 127. STG 128 is disabled by default, and contains the management VLAN 4095. An STG cannot be deleted, only disabled. If you disable the STG while it still contains VLAN members, Spanning Tree will be off on all ports belonging to that VLAN. Adding a VLAN to a Spanning Tree Group If no VLANs exist beyond the default VLAN 1, see the "Creating a VLAN" section in this chapter for information on adding ports to VLANs. Add the VLAN to the STG using the command /cfg/l2/stp /add . Creating a VLAN When you create a VLAN, then that VLAN automatically belongs to STG 1, the default STG. If you want the VLAN in another STG, you must move the VLAN by assigning it to another STG. To move a newly created VLAN to an existing STG: 1. Create the VLAN. 2. Add the VLAN to an existing STG. When creating a VLAN also consider the following: • A VLAN cannot belong to more than one STG. • VLANs that span multiple switches must be mapped within the same Spanning Tree Group (have the same STG ID) across all the switches. Rules for VLAN tagged ports Rules for VLAN tagged ports are listed below: • If a port is tagged, it can belong to multiple STGs. • When a tagged port belongs to more than one STG, the egress BPDUs are tagged to distinguish the BPDUs of one STG from those of another STG. • An untagged port cannot span multiple STGs. Spanning Tree Protocol 56

  • 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
Spanning Tree Protocol 56
Port path cost
The port path cost assigns lower values to high-bandwidth ports, such as Gigabit Ethernet, to encourage their use. The
objective is to use the fastest links so that the route with the lowest cost is chosen. A value of 0 indicates that port cost
is computed dynamically based on link speed. This works when forcing link speed, so it does not just apply to “auto
negotiated link speed”.
By default, all switch ports have the path cost set to 4, independent of the link speed. To use dynamic path cost,
based on link speed, set the path cost to 0 (zero). For example, if the path cost is set to zero:
•
A 100 Mbps link receives a path cost of 19
•
A 10 Mbps link receives a path cost of 100
Configure the port path cost using the following command:
/cfg/l2/stp y/port x/cost
Spanning Tree Group configuration guidelines
This section provides important information on configuring Spanning Tree Groups (STGs).
Default Spanning Tree configuration
In the default configuration, a single STG with the ID of 1 includes all ports on the switch. It is called the default STG.
All other STGs (except the default STG) are empty, and VLANs must be added by the user.
You cannot assign ports directly to an STG. Add the ports to a VLAN, and add the VLAN to the STG. STGs 1-127 are
enabled by default and assigned an ID number from 1 to 127. STG 128 is disabled by default, and contains the
management VLAN 4095.
An STG cannot be deleted, only disabled. If you disable the STG while it still contains VLAN members, Spanning Tree
will be off on all ports belonging to that VLAN.
Adding a VLAN to a Spanning Tree Group
If no VLANs exist beyond the default VLAN 1, see the “Creating a VLAN” section in this chapter for information on
adding ports to VLANs.
Add the VLAN to the STG using the command
/cfg/l2/stp <
stg number
>/add <
vlan number
>
.
Creating a VLAN
When you create a VLAN, then that VLAN automatically belongs to STG 1, the default STG. If you want the VLAN in
another STG, you must move the VLAN by assigning it to another STG.
To move a newly created VLAN to an existing STG:
1.
Create the VLAN.
2.
Add the VLAN to an existing STG.
When creating a VLAN also consider the following:
•
A VLAN cannot belong to more than one STG.
•
VLANs that span multiple switches must be mapped within the same Spanning Tree Group (have the same STG
ID) across all the switches.
Rules for VLAN tagged ports
Rules for VLAN tagged ports are listed below:
•
If a port is tagged, it can belong to multiple STGs.
•
When a tagged port belongs to more than one STG, the egress BPDUs are tagged to distinguish the BPDUs of
one STG from those of another STG.
•
An untagged port cannot span multiple STGs.