User Tools

Site Tools


fcoemon

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
fcoemon [2013/01/24 10:27]
rbbratta
fcoemon [2013/01/24 10:49]
rbbratta
Line 73: Line 73:
 First of all, the network interface must be "​up"​ for the FCoE instance to be created. Secondly, if the FCoE configuration indicates that DCB is required, then the following criteria must be satisfied before the FCoE interface is created: First of all, the network interface must be "​up"​ for the FCoE instance to be created. Secondly, if the FCoE configuration indicates that DCB is required, then the following criteria must be satisfied before the FCoE interface is created:
  
- ​  * DCB is enabled on the Ethernet interface.+  ​* DCB is enabled on the Ethernet interface.
  
- ​  * The PFC DCB feature is enabled and operational.+  ​* The PFC DCB feature is enabled and operational.
  
- ​  * The App:FCoE DCB feature is enabled and operational.+  ​* The App:FCoE DCB feature is enabled and operational.
  
- ​  * The priority indicated by the App:FCoE feature is also enabled for PFC.+  ​* The priority indicated by the App:FCoE feature is also enabled for PFC.
  
 Once the FCoE instance is created by **fcoemon**,​ it will only be destroyed under the following conditions: Once the FCoE instance is created by **fcoemon**,​ it will only be destroyed under the following conditions:
  
- ​  * The driver for the Ethernet interface is unloaded.+  ​* The driver for the Ethernet interface is unloaded.
  
- ​  * A user administratively destroys the FCoE instance using **fcoeadm**.+  ​* A user administratively destroys the FCoE instance using **fcoeadm**.
  
- ​  * The **fcoemon** daemon is terminated.+  ​* The **fcoemon** daemon is terminated.
  
 If DCB is required for the FCoE instance, and the DCB settings change after the interface is created, the following criteria are used to disable the FCoE instance: If DCB is required for the FCoE instance, and the DCB settings change after the interface is created, the following criteria are used to disable the FCoE instance:
  
- ​  * DCB is disabled on the Ethernet interface.+  ​* DCB is disabled on the Ethernet interface.
  
- ​  * The App:FCoE DCB feature is not enabled.+  ​* The App:FCoE DCB feature is not enabled.
  
- ​  * The App:FCoE and PFC features are operational AND the priority indicated by App:FCoE is not enabled for PFC.+  ​* The App:FCoE and PFC features are operational AND the priority indicated by App:FCoE is not enabled for PFC.
  
 Otherwise, the FCoE instance will always remain enabled. Otherwise, the FCoE instance will always remain enabled.
Line 103: Line 103:
 Once the //​fcoe-utils//​ and **lldpad** packages have been installed and the corresponding services are running, there are a few simple configuration steps required to get an FCoE instance up and running. The following assumes that DCB will be required for the interface. Once the //​fcoe-utils//​ and **lldpad** packages have been installed and the corresponding services are running, there are a few simple configuration steps required to get an FCoE instance up and running. The following assumes that DCB will be required for the interface.
  
- ​  * Ensure that the configuration on the peer device (e.g. FCoE capable switch) has the necessary configurations (VLANs, DCB, DCBX).+  ​* Ensure that the configuration on the peer device (e.g. FCoE capable switch) has the necessary configurations (VLANs, DCB, DCBX).
  
- ​  * Configure any needed VLAN interfaces on the local system.+  ​* Configure any needed VLAN interfaces on the local system.
  
- ​  * Create and configure ///​etc/​fcoe/​cfg-<​ifname>//​ files for the network interfaces over which FCoE instances need to be created. See the //FILES// sections for details. Note that //ifname// may be for a VLAN interface.+  ​* Create and configure ///​etc/​fcoe/​cfg-<​ifname>//​ files for the network interfaces over which FCoE instances need to be created. See the //FILES// sections for details. Note that //ifname// may be for a VLAN interface.
  
- ​  * Restart the **fcoe** service (i.e. **fcoemon**).+  ​* Restart the **fcoe** service (i.e. **fcoemon**).
  
- ​  * The default DCB configuration of an Ethernet interface managed by **lldpad** requires the following configuration using **dcbtool**.+  ​* The default DCB configuration of an Ethernet interface managed by **lldpad** requires the following configuration using **dcbtool**.
  
   dcbtool sc ethX dcb on          <-- enable DCB on the interface   dcbtool sc ethX dcb on          <-- enable DCB on the interface
Line 160: Line 160:
 **fcoemon** is part of the //​fcoe-utils//​ package, maintained through the //​Open-FCoE//​ project. Resources for both developers and users can be found at the //​Open-FCoE//​ website http://​open-fcoe.org/​ **fcoemon** is part of the //​fcoe-utils//​ package, maintained through the //​Open-FCoE//​ project. Resources for both developers and users can be found at the //​Open-FCoE//​ website http://​open-fcoe.org/​
  
-This document was created by man2html, using the manual pages.\\ ​ Time: 18:27:08 GMT, January 24, 2013+This document was created by man2html, using the manual pages.\\ ​ Time: 18:47:31 GMT, January 24, 2013
  
fcoemon.txt · Last modified: 2013/01/24 10:49 by rbbratta