- play_arrow Overview
- play_arrow Storage Overview
-
- play_arrow Transit Switch, FCoE, and FIP Snooping
- play_arrow Using FCoE on a Transit Switch
- Understanding FCoE Transit Switch Functionality
- Understanding FCoE
- Understanding FCoE LAGs
- Configuring an FCoE LAG
- Example: Configuring an FCoE LAG on a Redundant Server Node Group
- Understanding OxID Hash Control for FCoE Traffic Load Balancing on QFabric Systems
- Understanding OxID Hash Control for FCoE Traffic Load Balancing on Standalone Switches
- Enabling and Disabling CoS OxID Hash Control for FCoE Traffic on Standalone Switches
- Enabling and Disabling CoS OxID Hash Control for FCoE Traffic on QFabric Systems
- Configuring VLANs for FCoE Traffic on an FCoE Transit Switch
- Understanding FIP Snooping, FBF, and MVR Filter Scalability
- Understanding VN_Port to VF_Port FIP Snooping on an FCoE Transit Switch
- Configuring VN2VF_Port FIP Snooping and FCoE Trusted Interfaces on an FCoE Transit Switch
- Understanding VN_Port to VN_Port FIP Snooping on an FCoE Transit Switch
- Enabling VN2VN_Port FIP Snooping and Configuring the Beacon Period on an FCoE Transit Switch
- Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Directly Connected to the Same FCoE Transit Switch)
- Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Directly Connected to Different FCoE Transit Switches)
- Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Indirectly Connected Through an Aggregation Layer FCoE Transit Switch)
- Disabling Enhanced FIP Snooping Scaling
- Understanding MC-LAGs on an FCoE Transit Switch
- Example: Configuring CoS Using ELS for FCoE Transit Switch Traffic Across an MC-LAG
- Understanding FCoE and FIP Session High Availability
- Troubleshooting Dropped FIP Traffic
- Troubleshooting Dropped FCoE Traffic
-
- play_arrow Fibre Channel and FCoE-FC Gateways
- play_arrow Using Fibre Channel and FCoE-FC Gateways
- Understanding Fibre Channel
- Understanding an FCoE-FC Gateway
- Understanding Fibre Channel Fabrics on the QFabric System
- Configuring an FCoE-FC Gateway Fibre Channel Fabric
- Understanding FCoE-FC Gateway Functions
- Disabling the Fabric WWN Verification Check
- Understanding FCoE and FIP Session High Availability
- Understanding FIP Functions
- Understanding FIP Implementation on an FCoE-FC Gateway
- Understanding FIP Parameters on an FCoE-FC Gateway
- Configuring FIP on an FCoE-FC Gateway
- Setting the Maximum Number of FIP Login Sessions per ENode
- Setting the Maximum Number of FIP Login Sessions per FC Interface
- Setting the Maximum Number of FIP Login Sessions per FC Fabric
- Setting the Maximum Number of FIP Login Sessions per Node Device
- Monitoring Fibre Channel Interface Load Balancing
- Troubleshooting Dropped FIP Traffic
- Understanding Fibre Channel Virtual Links
- Understanding Interfaces on an FCoE-FC Gateway
- Example: Setting Up Fibre Channel and FCoE VLAN Interfaces in an FCoE-FC Gateway Fabric
- Configuring a Physical Fibre Channel Interface
- Converting an Ethernet Interface To a Fibre Channel Interface
- Configuring an FCoE VLAN Interface on an FCoE-FC Gateway
- Assigning Interfaces to a Fibre Channel Fabric
- Deleting a Fibre Channel Interface
- Troubleshooting Fibre Channel Interface Deletion
- Disabling VN2VF_Port FIP Snooping on an FCoE-FC Gateway Switch Interface
- Disabling Storm Control on FCoE Interfaces on an FCoE-FC Gateway
- Understanding Load Balancing in an FCoE-FC Gateway Proxy Fabric
- Defining the Proxy Load-Balancing Algorithm
- Simulating On-Demand Fibre Channel Link Load Rebalancing (Dry Run Test)
- Example: Configuring Automated Fibre Channel Interface Load Rebalancing
-
- play_arrow Configuration Statements and Operational Commands
Defining an Application for DCBX Application Protocol TLV Exchange
Define each application for which you want DCBX to exchange application protocol information. You can define Layer 2 and Layer 4 applications. After you define applications, you map them to IEEE 802.1p code points, and then apply the application map to the interfaces on which you want DCBX to exchange application protocol information with connected peers. (See Related Documentation for how to configure application maps and apply them to interfaces, and for an example of the entire procedure that also includes classifier configuration.)
In Junos OS Release 12.1, the FCoE application was configured by default, so you did not need to configure it in an application map. In Junos OS Release 12.2, if you want DCBX to advertise the FCoE application on an interface and you apply an application map to that interface, you must explicitly configure FCoE in the application map. You also must enable priority-based flow control (PFC) on the FCoE code point on all interfaces that you want to advertise FCoE. If you apply an application map to an interface, the interface sends DCBX TLVs only for the applications configured in the application map.
Define Layer 2 applications by mapping an application name to an EtherType. Define Layer 4 applications by mapping an application name to a protocol (TCP or UDP) and a destination port.
To define a Layer 2 application, specify the name of the application and its EtherType:
content_copy zoom_out_map[edit applications] user@switch# set application application-name ether-type ether-type
For example, to configure an application named
PTP(for Precision Time Protocol) that uses the EtherType0x88F7:content_copy zoom_out_mapuser@switch# set applications application ptp ether-type 0x88F7
To define a Layer 4 application, specify the name of the application, its protocol (TCP or UDP), and its destination port:
content_copy zoom_out_map[edit] user@switch# set applications application application-name protocol (tcp | udp) destination-port port-value
For example, to configure an application named
iscsi(for Internet Small Computer System Interface) that uses the protocolTCPand the destination port3260:content_copy zoom_out_mapuser@switch# set applications application iscsi protocol tcp destination-port 3260
