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

Configuring the auto fabric reconfiguration function, Manually initiating the fabric reconfiguration

Page 35 highlights

• Disruptive reconfiguration-Floods the Reconfigure Fabric (RCF) frames throughout the fabric, and notifies all switches to perform a disruptive reconfiguration. During the reconfiguration procedure, each switch clears all data for renegotiation, and data transmission in the fabric is disrupted. • Non-disruptive reconfiguration-Floods the Build Fabric (BF) frames throughout the fabric, and notifies all switches to perform a non-disruptive reconfiguration. During the reconfiguration procedure, each switch tries to save the last running data for its domain ID to remain unchanged. Thus, data transmission in the fabric is not disrupted. Depending on the triggering conditions, the fabric reconfiguration includes auto reconfiguration and manual reconfiguration. • When two fabrics are merged: { The switches automatically perform a disruptive reconfiguration if the domain ID lists overlap. { The system automatically performs a non-disruptive reconfiguration if the principal switch information of the two fabrics is different and the domain ID lists are not empty or overlapping. { You can manually initiate a disruptive reconfiguration to trigger the fabric reconfiguration if ports are isolated and priority values of switches are modified. • When the principal switch in a fabric is down, the system automatically performs a non-disruptive reconfiguration. Configuring the auto fabric reconfiguration function Step 1. Enter system view. 2. Enter VSAN view. 3. Enable the auto fabric reconfiguration function. Command system-view vsan vsan-id domain auto-reconfigure enable Remarks N/A N/A By default, the auto fabric reconfiguration function is disabled. Manually initiating the fabric reconfiguration Step 1. Enter system view. 2. Enter VSAN view. 3. Initiate the fabric reconfiguration. Command system-view vsan vsan-id domain restart [ disruptive ] Configuring a VFC interface to reject incoming RCF requests In a stable fabric, to avoid unnecessary disruptive reconfigurations, you can configure a VFC interface to reject the RCF requests received from a specific VSAN by replying with a reject message. With this feature, the interface on which an RCF request is received is isolated. To configure a VFC interface to reject the received RCF requests: 29

  • 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

29
Disruptive reconfiguration
—Floods the Reconfigure Fabric (RCF) frames throughout the fabric, and
notifies all switches to perform a disruptive reconfiguration. During the reconfiguration procedure,
each switch clears all data for renegotiation, and data transmission in the fabric is disrupted.
Non-disruptive reconfiguration
—Floods the Build Fabric (BF) frames throughout the fabric, and
notifies all switches to perform a non-disruptive reconfiguration. During the reconfiguration
procedure, each switch tries to save the last running data for its domain ID to remain unchanged.
Thus, data transmission in the fabric is not disrupted.
Depending on the triggering conditions, the fabric reconfiguration includes auto reconfiguration and
manual reconfiguration.
When two fabrics are merged:
{
The switches automatically perform a disruptive reconfiguration if the domain ID lists overlap.
{
The system automatically performs a non-disruptive reconfiguration if the principal switch
information of the two fabrics is different and the domain ID lists are not empty or overlapping.
{
You can manually initiate a disruptive reconfiguration to trigger the fabric reconfiguration if
ports are isolated and priority values of switches are modified.
When the principal switch in a fabric is down, the system automatically performs a non-disruptive
reconfiguration.
Configuring the auto fabric reconfiguration function
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter VSAN view.
vsan
vsan-id
N/A
3.
Enable the auto fabric
reconfiguration function.
domain auto-reconfigure enable
By default, the auto fabric
reconfiguration function is disabled.
Manually initiating the fabric reconfiguration
Step
Command
1.
Enter system view.
system-view
2.
Enter VSAN view.
vsan
vsan-id
3.
Initiate the fabric reconfiguration.
domain restart
[
disruptive
]
Configuring a VFC interface to reject incoming RCF
requests
In a stable fabric, to avoid unnecessary disruptive reconfigurations, you can configure a VFC interface to
reject the RCF requests received from a specific VSAN by replying with a reject message. With this
feature, the interface on which an RCF request is received is isolated.
To configure a VFC interface to reject the received RCF requests: