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

Initiating a disruptive load-balancing process, Displaying and maintaining NPV, NPV configuration

Page 95 highlights

Step 1. Enter system view. 2. Enter VSAN view. 3. Configure a downlink-to-uplink interface mapping. Command Remarks system-view N/A vsan vsan-id N/A npv traffic-map server-interface interface-type interface-number external-interface interface-type interface-number By default, no mapping is configured. Initiating a disruptive load-balancing process CAUTION: This feature redistributes downlink traffic across all uplink interfaces for better load balancing, but it causes traffic interruption. If interfaces in a VSAN are not distributed evenly, you can use this feature to force all nodes in the VSAN to relog in to the core switch. To initiate a disruptive load-balancing process: Step 1. Enter system view. 2. Enter VSAN view. 3. Initiate a disruptive load-balancing process. Command system-view vsan vsan-id npv load-balance disruptive Displaying and maintaining NPV Execute display commands in any view. Task Display the nodes on downlink interfaces and their mapped uplink interfaces. Display the traffic mapping information. Display status information. Command display npv login [ vsan vsan-id ] [ interface interface-type interface-number ] [ count ] display npv traffic-map [ vsan vsan-id ] [ interface interface-type interface-number ] display npv status [ vsan vsan-id ] NPV configuration example Network requirements As shown in Figure 25, configure Switch A (edge switch) as an NPV switch to expand the network. 89

  • 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

89
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter VSAN view.
vsan
vsan-id
N/A
3.
Configure a
downlink-to-uplink
interface mapping.
npv traffic-map server-interface
interface-type interface-number
external-interface
interface-type
interface-number
By default, no mapping is configured.
Initiating a disruptive load-balancing process
CAUTION:
This feature redistributes downlink traffic across all uplink interfaces for better load balancing, but it
causes traffic interruption.
If interfaces in a VSAN are not distributed evenly, you can use this feature to force all nodes in the VSAN
to relog in to the core switch.
To initiate a disruptive load-balancing process:
Step
Command
1.
Enter system view.
system-view
2.
Enter VSAN view.
vsan
vsan-id
3.
Initiate a disruptive load-balancing process.
npv load-balance disruptive
Displaying and maintaining NPV
Execute
display
commands in any view.
Task
Command
Display the nodes on downlink interfaces and their
mapped uplink interfaces.
display npv login
[
vsan
vsan-id
] [
interface
interface-type
interface-number
] [
count
]
Display the traffic mapping information.
display npv traffic-map
[
vsan
vsan-id
] [
interface
interface-type
interface-number
]
Display status information.
display npv status
[
vsan
vsan-id
]
NPV configuration example
Network requirements
As shown in
Figure 25
, configure Switch A (edge switch) as an NPV switch to expand the network.