HP 6125XLG R2306-HP 6125XLG Blade Switch FCoE Configuration Guide - Page 93

Downlink-to-uplink interface mappings, Disruptive load balancing, NPV configuration task list

Page 93 highlights

Downlink-to-uplink interface mappings NPV switches automatically map downlink interfaces to uplink interfaces. Before a downlink interface is brought up, the NPV switch maps it to the uplink interface with the minimum load among all operational uplink interfaces. The load here indicates the number of downlink interfaces mapped to the uplink interface. When automatic mapping cannot meet requirements (for example, when a downlink interface must be connected to a fabric through a specified uplink interface), you can manually map the downlink interface to a specified uplink interface or a set of uplink interfaces. After you configure the mapping, the downlink interface can be mapped to only the configured uplink interfaces. In other words, if none of the configured uplink interfaces is operational, the downlink interface cannot be operational. A configured mapping selects the uplink interface with the minimum load from configured uplink interfaces and then maps the downlink interface to it. After a mapping is established, all traffic from the downlink interface is forwarded through the uplink interface. Disruptive load balancing When a new uplink interface becomes operational, the NPV switch does not perform a remapping for load balancing. In the event of remapping, the NPV switch reinitializes the downlink interface so that the nodes connected to the downlink interface register with the core switch again. This causes traffic interruption to the nodes. You can trigger a remapping by using commands for better load balancing. In this case, the NPV switch reinitializes all downlink interfaces. NPV configuration task list Tasks at a glance Remarks (Required.) Configuring the switch to operate in NPV mode See "Configuration procedure" in "Configuring an FCoE mode." (Required.) Configuring uplink interfaces and downlink interfaces N/A (Optional.) Configuring downlink-to-uplink interface mappings N/A (Optional.) Initiating a disruptive load-balancing process N/A Configuring uplink interfaces and downlink interfaces After configuring the switch to operate in NPV mode, configure the uplink interfaces and downlink interfaces. 87

  • 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

87
Downlink-to-uplink interface mappings
NPV switches automatically map downlink interfaces to uplink interfaces. Before a downlink interface is
brought up, the NPV switch maps it to the uplink interface with the minimum load among all operational
uplink interfaces. The load here indicates the number of downlink interfaces mapped to the uplink
interface.
When automatic mapping cannot meet requirements (for example, when a downlink interface must be
connected to a fabric through a specified uplink interface), you can manually map the downlink interface
to a specified uplink interface or a set of uplink interfaces. After you configure the mapping, the downlink
interface can be mapped to only the configured uplink interfaces. In other words, if none of the
configured uplink interfaces is operational, the downlink interface cannot be operational.
A configured mapping selects the uplink interface with the minimum load from configured uplink
interfaces and then maps the downlink interface to it.
After a mapping is established, all traffic from the downlink interface is forwarded through the uplink
interface.
Disruptive load balancing
When a new uplink interface becomes operational, the NPV switch does not perform a remapping for
load balancing. In the event of remapping, the NPV switch reinitializes the downlink interface so that the
nodes connected to the downlink interface register with the core switch again. This causes traffic
interruption to the nodes.
You can trigger a remapping by using commands for better load balancing. In this case, the NPV switch
reinitializes all downlink interfaces.
NPV configuration task list
Tasks at a glance
Remarks
(Required.) Configuring the switch to operate in NPV mode
See "
Configuration procedure
" in "
Configuring
an FCoE mode
."
(Required.)
Configuring uplink interfaces and downlink
interfaces
N/A
(Optional.)
Configuring downlink-to-uplink interface
mappings
N/A
(Optional.)
Initiating a disruptive load-balancing process
N/A
Configuring uplink interfaces and downlink
interfaces
After configuring the switch to operate in NPV mode, configure the uplink interfaces and downlink
interfaces.