Dell Broadcom NetXtreme Family of Adapters Broadcom NetXtreme II Network Adapt - Page 53

Supported FC/FCoE Devices, Unloading FCoE Driver, Configuring the FCoE Driver

Page 53 highlights

Solaris Driver Software: Broadcom NetXtreme II Network Adapter User Guide Support does not exist for NPIV in the Solaris 10 Update 9. Some of the fcinfo(1M) options, which are available in Solaris 11, are not be available in Solaris 10, Update 9. For more information, read the man page fcinfo(1M). brcmfcoeadm(1M) feature is supported in both Solaris 10 Update 9 and Solaris 11. However, when "delete-fcoe-port" is complete, you need to issue the following two commands to unload the bnxef driver before you can re-issue "createfcoe-port". There is a reaper thread in Solaris 11 that aggressively looks for unused driver modules and unloads the driver. That thread does not exist in Solaris 10 Update 9. Therefore, you have to explicitly look for the driver module ID of the bnxef driver by issuing the following command. # modinfo | grep bnxef 249 fffffffff8d63000 486b8 54 1 bnxef (6.4.13) Then issue the modunload command to unload the module before "create-fcoe-port" is issued to create a new FCoE port. # modunload -i 249 Any time "create-fcoe-port" needs to be issued, the driver must be unloaded, if it is already loaded. If not, the "create-fcoeport" will fail indicating the driver is busy. This is true when you have two or more instances of bnxef loaded, in which case, you should first delete all FCoE ports and then unload the driver. Unloading will occur only when all the instances are deleted. Supported FC/FCoE Devices The bnxef Broadcom 10 Gb FCoE driver works with all the major FCoE fabric devices. It is also compatible with all known FC disk devices and tape devices working through the FCoE fabric. Unloading FCoE Driver Delete all FCoE ports created across the various bnxe instances. 1. Delete all the NPIV ports created before deleting FCoE ports. 2. brcmfcoeadm delete-fcoe-port bnxe 3. modinfo | grep bnxef The first column for the above command will give the module ID for the bnxef driver. 4. modunload -i The procedure should unload the driver. However, if there are many instances of the FCoE ports created, all the FCoE ports must be deleted before the unload can be attempted. Configuring the FCoE Driver The bnxef driver can be configured via the bnxef.conf file installed under /kernel/drv. When this config file is modified, the system must be either rebooted or use the update_drv(1M) command to update the driver configuration. The details of the configurations parameters are detailed in the bnxef(7D) man page. The default parameters should work for all conditions. Please read all Restrictions and Disclaimers. Back to Contents Page file:///T|/htdocs/NETWORK/BroadCom/71921/NetXtremeII/en/solaris.htm[9/26/2012 3:28:52 PM]

  • 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
  • 223
  • 224

Solaris Driver Software: Broadcom NetXtreme II Network Adapter User Guide
file:///T|/htdocs/NETWORK/BroadCom/71921/NetXtremeII/en/solaris.htm[9/26/2012 3:28:52 PM]
Support does not exist for NPIV in the Solaris 10 Update 9.
Some of the fcinfo(1M) options, which are available in Solaris 11, are not be available in Solaris 10, Update 9. For more
information, read the man page fcinfo(1M).
brcmfcoeadm(1M) feature is supported in both Solaris 10 Update 9 and Solaris 11. However, when "delete-fcoe-port" is
complete, you need to issue the following two commands to unload the bnxef driver before you can re-issue "create-
fcoe-port". There is a reaper thread in Solaris 11 that aggressively looks for unused driver modules and unloads the
driver. That thread does not exist in Solaris 10 Update 9. Therefore, you have to explicitly look for the driver module ID
of the bnxef driver by issuing the following command.
# modinfo | grep bnxef
249 fffffffff8d63000
486b8
54
1
bnxef (6.4.13)
Then issue the modunload command to unload the module before "create-fcoe-port" is issued to create a new FCoE
port.
# modunload -i 249
Any time "create-fcoe-port" needs to be issued, the driver must be unloaded, if it is already loaded. If not, the "create-fcoe-
port" will fail indicating the driver is busy. This is true when you have two or more instances of bnxef loaded, in which case,
you should first delete all FCoE ports and then unload the driver. Unloading will occur only when all the instances are deleted.
Supported FC/FCoE Devices
The bnxef Broadcom 10 Gb FCoE driver works with all the major FCoE fabric devices. It is also compatible with all known FC
disk devices and tape devices working through the FCoE fabric.
Unloading FCoE Driver
Delete all FCoE ports created across the various bnxe instances.
1. Delete all the NPIV ports created before deleting FCoE ports.
2. brcmfcoeadm delete-fcoe-port bnxe<instance_number>
3. modinfo | grep bnxef
The first column for the above command will give the module ID for the bnxef driver.
4. modunload -i <module id>
The procedure should unload the driver. However, if there are many instances of the FCoE ports created, all the FCoE ports
must be deleted before the unload can be attempted.
Configuring the FCoE Driver
The bnxef driver can be configured via the bnxef.conf file installed under /kernel/drv. When this config file is modified, the
system must be either rebooted or use the update_drv(1M) command to update the driver configuration.
The details of the configurations parameters are detailed in the bnxef(7D) man page. The default parameters should work for
all conditions.
Please read all
Restrictions and Disclaimers
.
Back to Contents Page