Cisco NX-OS FCoE Configuration Guide for Nexus 7000, MDS 9500 and MDS 9250i
Configuring FCoE VLANs and Virtual Interfaces
Downloads: This chapterpdf (PDF - 1.41MB) The complete bookPDF (PDF - 2.44MB) | The complete bookePub (ePub - 181.0KB) | Feedback

Configuring FCoE VLANs and Virtual Interfaces

Configuring FCoE VLANs and Virtual Interfaces

This chapter includes the following sections:

Information About Virtual Fibre Channel (VFC) Interfaces

Fibre Channel over Ethernet (FCoE) allows Fibre Channel and Ethernet traffic to be carried on the same physical Ethernet connection between the switch and the servers.

The Fibre Channel portion of FCoE is configured as a virtual Fibre Channel interface. Logical Fibre Channel features (such as interface mode) can be configured on virtual Fibre Channel interfaces.

A virtual Fibre Channel (vfc) interface must be bound to an interface before it can be used. The binding is to a physical Ethernet interface when the converged network adapter (CNA) is directly connected to the switch or port channel when the CNA connects to the Fibre Channel Forwarder (FCF) over a virtual port channel (vPC).

VF Port

A virtual fabric (VF) port in an FCoE network acts as a fabric port that connects to a peripheral device (host or disk) operating as an N port. A VF port can be attached to only one N port.

VE Port

A virtual expansion (VE) port acts as an expansion port in an FCoE network. VE ports can connect multiple FCoE switches together in the network. You can bind a VE port to a physical ethernet port or a port channel.

Traffic is load balanced across equal cost E_Ports and VE_Ports based on SID, DID, and OXID. Traffic across members of a port channel that a VE_Port is bound to is load balanced based on SID, DID, and OXID.

Default Settings for FCoE

This table lists the default settings for FCoE parameters.

Table 1  Default FCoE Parameter Settings

Parameters

Default

FCoE feature

Not installed, disabled

FC-Map

0E.FC.00

Fabric priority

128

Advertisement interval

8 seconds

Licensing Requirements for FCoE

Product License
Cisco Nexus 7000 Series Each F Series module that runs FCoE requires an FCoE license. FCoE enabled in a nondefault VDC does not require the Advanced Services License. For a complete explanation of the Cisco NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco NX-OS Licensing Guide.
Cisco MDS 9500 Series FCoE does not require a license. For a complete explanation of the Cisco NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco NX-OS Licensing Guide.

Guidelines and Limitations

Cisco Nexus 7000: Guidelines and Limitations

  • You cannot enable FCoE on default VLAN.
  • The QoS policy must be the same on all Cisco FCoE switches in the network.
  • Beginning with Cisco NX-OS Release 6.1, FCoE is supported on F2 and F2e Series modules.
    • FCoE supports only F2e (SFP+) modules.
    • FCoE does not support F2e (Copper) modules.

FCoE VDC

FCoE in a dedicated storage VDC has the following guidelines:

  • Enable the FCoE feature set in only one VDC.
  • Create VLANs in the FCoE allocated VLAN range.
  • Do not enable any other features other than storage-related features in the dedicated FCoE VDC.
  • Allocate resources for the dedicated FCoE VDC from an F Series module, such as the 32-port 1- and 10-Gigabit Ethernet I/O module (PID N7K-F132XP-15) .
  • Rollback is not supported in a storage VDC.
  • FCoE support on F2 and F2e Series modules, SF248XP-25 requires Supervisor 2 module.
  • F2 and F2e series modules cannot exist in the same VDC with any other module type. This applies to both LAN and storage VDCs.

Shared Interfaces


Note


Any change in protocol state that flaps the parent port of a shared interface because of any port feature also affects the FCOE traffic on the storage vdc.

The following interface config modes are not allowed while sharing an interface from Ethernet vdc to a storage vdc:

  • SPAN destination
  • Private VLAN mode
  • Port-channel interfaces
  • Access mode
  • mac-packet-classify
  • Interfaces that are part of a VLAN that has an associated QoS policy

Shared Ethernet interfaces must be in trunk mode and only shared with one other VDC.

Storage VDC

Configuring a VDC for the OOB management interface mgmt0 is accomplished with the vrf context management command. However, a storage VDC does not support VRF, so configuring mgmt0 requires a different approach.

The following table shows how to configure mgmt 0 for a VDC and for a storage VDC:

Configuring mgmt 0 for VDC Configuring mgmt 0 for storage VDC
vrf context management
ip route 0.0.0.0/0 default_gateway
interface mgmt 0
ip address mgmt0_ip_address mgmt0_subnet_mask
no shut
ip route 0.0.0.0/0 default_gateway
Note   

The ip route command specifies the default route that points to the default gateway.

where

  • mgmt0_ip_address is the mgmt0 IPv4 address.
  • mgmt0_subnet_mask is the mgmt0 IPv4 netmask.
  • default_gateway is the IPv4 address of the default-gateway.

For more information about VDC, see the Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide.

Cisco MDS 9000 Series: Guidelines and Limitations

  • You cannot enable FCoE on the default VLAN.
  • You can only enable FCoE on an FCoE module. This does not apply to MDS 9250i.
  • The QoS policy must be the same on all Cisco FCoE switches in the network.
  • Cisco MDS 9500 and 9250i does not support LAN traffic and only accepts and processes FCoE frames.
  • You must install a Supervisor-2A module to configure FCoE. This does not apply to MDS 9250i.
  • You can install an FCoE module in a fabric that uses FC-Redirect services but do not install the FCoE module in the same switch where FC-Redirect services application modules are enabled.
  • SME does not support any FCoE connected devices including devices connected through the MDS FCoE linecard (DX-X9708-K9)
  • In Cisco MDS NX-OS Release 5.2(x), you cannot install a FCoE module in a switch that is running DMM, SME, or IOA.
  • Cisco MDS 9250i supports a maximum number of up to 32 VSANs.
  • MDS 9250i does not support FCoE Switched Port Analyzer (SPAN).
  • MDS 9250i does not support FCoE port diagnostics, such as generic online diagnostics (GOLD) and Online Health Management System (OHMS).

Configuring Virtual Interfaces

Mapping a VSAN to a VLAN

A unique, dedicated VLAN must be configured at every converged access switch to carry traffic for each virtual fabric (VSAN) in the SAN (for example, VLAN 1002 for VSAN 10, VLAN 1003 for VSAN 2, and so on). If you enable MST, you must use a separate Multiple Spanning Tree (MST) instance for FCoE VLANs.


Note


You must exit VLAN mode to execute the configured commands on the Cisco Nexus 7000 Series Switches.


Before You Begin
  • Ensure you have installed the correct license for FCoE.
  • Ensure you have enabled FCoE.
  • For Cisco Nexus 7000 Series Switches, ensure that you are in the storage VDC.
SUMMARY STEPS

    1.    configure terminal

    2.    vsan database

    3.    vsan vsan-id

    4.    vlan vlan-id

    5.    fcoe [vsan vsan-id]

    6.    exit

    7.    (Optional) show vlan fcoe

    8.    (Optional) copy running-config startup-config


DETAILED STEPS
     Command or ActionPurpose
    Step 1 configure terminal


    Example:
    switch# configure terminal
    switch(config)#
     

    Enters configuration mode.

     
    Step 2 vsan database


    Example:
    switch(config)# vsan database
    switch(config-vsan-db)#
     

    Enters VSAN database configuration mode.

     
    Step 3 vsan vsan-id


    Example:
    switch(config-vsan-db)# vsan 200
    
     

    Defines the VSAN. The VSAN number range is from 1 to 4094.

     
    Step 4 vlan vlan-id


    Example:
    switch(config-vsan-db)# vlan 200
    switch(config-vlan)#
     

    Enters VLAN configuration mode. The VLAN number range is from 1 to 4096.

     
    Step 5 fcoe [vsan vsan-id]


    Example:
    switch(config-vlan)# fcoe vsan 200
     

    Enables FCoE for the specified VLAN and configures the mapping from this VLAN to the specified VSAN. If you do not specify a VSAN number, a mapping is created from this VLAN to the VSAN with the same number.

     
    Step 6 exit


    Example:
    switch(config-vlan)# exit
    switch(config)#
     

    Exits VLAN configuration mode. You must exit this mode to execute the configured commands on the Cisco Nexus 7000 Series Switches.

     
    Step 7 show vlan fcoe


    Example:
    switch(config-vlan)# show vlan fcoe
     
    (Optional)

    Displays information about the FCoE configuration for a VLAN.

     
    Step 8 copy running-config startup-config


    Example:
    switch(config-vlan)# copy running-config startup-config
     
    (Optional)

    Copies the running configuration to the startup configuration.

     

    This example shows how to map VLAN 200 to VSAN 200 on a Cisco MDS 9500 Series Switch:

    switch(config)# vlan 200
    switch(config-vlan)# fcoe vsan 200
    
    

    This example shows how to map VLAN 300 to VSAN 300 on a Cisco Nexus 7000 Series Switches:

    switch(config)# switchto vdc fcoe_vdc
    switch-fcoe_vdc# configure terminal
    switch-fcoe_vdc(config)# vlan 300
    switch-fcoe_vd(config-vlan)# fcoe vsan 300
    
    

    Creating a Virtual Fibre Channel Interface

    You can create a virtual Fibre Channel interface. You must bind the virtual Fibre Channel interface to a physical interface before it can be used.

    Before You Begin
    • Ensure you have installed the correct license for FCoE.
    • Ensure you have enabled FCoE.
    SUMMARY STEPS

      1.    configure terminal

      2.    interface vfc vfc-id

      3.    switchport mode mode

      4.    bind {interface {ethernet slot/port}}

      5.    (Optional) show interface vfc

      6.    (Optional) copy running-config startup-config


    DETAILED STEPS
       Command or ActionPurpose
      Step 1 configure terminal


      Example:
      switch# configure terminal
      switch(config)#
       

      Enters configuration mode.

       
      Step 2 interface vfc vfc-id


      Example:
      switch(config)# interface vfc 4
      switch(config-if)#
       

      Creates a virtual Fibre Channel interface (if it does not already exist) and enters interface configuration mode. The vfc-id range is from 1 to 8192.

       
      Step 3 switchport mode mode


      Example:
      switch(configif)# switchport mode e
      
       

      Configures the switchport mode for a virtual Fibre Channel interface. The mode is E or F. The default is F mode.

       
      Step 4 bind {interface {ethernet slot/port}}


      Example:
      switch(config-if)# bind interface ethernet 1/4
       

      Binds the virtual Fibre Channel interface to the specified interface. Use ? to see the supported interfaces and port channels. Use the no form of this command to unbind the virtual Fibre Channel interface from the specified interface.

       
      Step 5 show interface vfc


      Example:
      switch(config-if)# show interface vfc
       
      (Optional)

      Displays information about the virtual Fibre Channel interfaces.

       

      Step 6 copy running-config startup-config


      Example:
      switch(config)# copy running-config startup-config
       
      (Optional)

      Copies the running configuration to the startup configuration.

       

      This example shows how to bind a virtual Fibre Channel interface to an Ethernet interface:

      switch# configure terminal
      switch(config)# interface vfc 4
      switch(config-if)# bind interface ethernet 1/4
      
      

      This example shows how to delete a virtual Fibre Channel interface:

      switch# configure terminal
      switch(config)# no interface vfc 4
      
      

      Creating a Virtual Fibre Channel Port Channel Interface

      You can create a virtual Fibre Channel port channel interface that automatically binds to the port channel with the same interface number.

      Before You Begin
      • For the Cisco Nexus 7000 Series, ensure that you create the port channel interface before you create the virtual Fibre Channel port channel interface.
      • For the Cisco MDS 9500 switches and MDS 9250i switch, ensure that you create the Ethernet port channel interface before you create the virtual Fibre Channel port channel interface.
      SUMMARY STEPS

        1.    configure terminal

        2.    interface vfc-port-channel int-number

        3.    switchport mode mode

        4.    (Optional) show interface vfc-port-channel int-number

        5.    (Optional) copy running-config startup-config


      DETAILED STEPS
         Command or ActionPurpose
        Step 1 configure terminal


        Example:
        switch# configure terminal
        switch(config)#
         

        Enters configuration mode.

         
        Step 2 interface vfc-port-channel int-number


        Example:
        switch(config)# interface vfc-port-channel 2
        switch(config-if)#
         

        Creates a virtual Fibre Channel interface (if it does not already exist) that is bound to the port channel with the same interface number and enters interface configuration mode. The int-number range is from 1 to 4096 (for Cisco Nexus 7000) or from 257 to 4095 (for Cisco MDS 9500). The default switchport mode for this interface is E.

        Note    Starting from the MDS 9710 switch and newer chassis, we support only the Ethernet port channel or the channel group ID numbers ranging from 513 to 4096. However, we support 257 to 4096 ID numbers on the MDS Ethernet port channel.
         
        Step 3 switchport mode mode


        Example:
        switch(config-if)# switchport mode e
        
         

        Configures the switchport mode for a virtual Fibre Channel interface. The mode is E or F. The default is F mode.

         
        Step 4 show interface vfc-port-channel int-number


        Example:
        switch(config-if)# show interface vfc-port-channel 2
         
        (Optional)

        Displays information about the virtual Fibre Channel interfaces bound to port channel interfaces.

         

        Step 5 copy running-config startup-config


        Example:
        switch(config)# copy running-config startup-config
         
        (Optional)

        Copies the running configuration to the startup configuration.

         

        Associating a Virtual Fibre Channel Interface to a VSAN

        You must configure unique, dedicated VLAN at every converged access switch to carry traffic for each Virtual Fabric (VSAN) in the SAN (for example, VLAN 1002 for VSAN 1, VLAN 1003 for VSAN 2, and so on). If you enable MST, you must use a separate MST instance for FCoE VLANs.

        Before You Begin

        For Cisco Nexus 7000 Series Switches, ensure that you are in the storage VDC.

        SUMMARY STEPS

          1.    configure terminal

          2.    vsan database

          3.    (Optional) vsan vsan-id

          4.    Enter one of the following commands:

          • vsan vsan-id interface vfc vfc-id
          • vsan vsan-id interface vfc-port-channel vfc-id

          5.    (Optional) show vsan

          6.    (Optional) copy running-config startup-config


        DETAILED STEPS
           Command or ActionPurpose
          Step 1 configure terminal


          Example:
          switch# configure terminal
          switch(config)#
           

          Enters configuration mode.

           
          Step 2vsan database


          Example:
          switch(config)# vsan database
          switch(config-vsan-db)#
           

          Enters VSAN configuration mode.

           
          Step 3vsan vsan-id


          Example:
          switch(config-vsan-db)# vsan 2 
           
          (Optional)

          Creates the VSAN. The vsan-id range is from 1 to 4094 and must map to a VLAN on the physical Ethernet interface that is bound to the virtual Fibre Channel interface.

           
          Step 4 Enter one of the following commands:
          • vsan vsan-id interface vfc vfc-id
          • vsan vsan-id interface vfc-port-channel vfc-id


          Example:
          switch(config-vsan-db)# vsan 2 interface vfc 4
           

          Configures the association between the VSAN and virtual Fibre Channel interface or virtual Fibre Channel port channel. The vsan-id range is from 1 to 4094 and must map to a VLAN on the physical Ethernet interface or port channel that is bound to the virtual Fibre Channel interface or virtual Fibre Channel port channel. The vfc-id range is from 1 to 8192. Us the no form of this command to dissassociate the connection between the VSAN and virtual Fibre Channel interface or virtual Fibre Channel port channel.

           
          Step 5 show vsan


          Example:
          switch(config-vsan-db)# show vsan
           
          (Optional)

          Displays information about the VSAN.

           
          Step 6 copy running-config startup-config


          Example:
          switch(config-vsan-db)# copy running-config startup-config
           
          (Optional)

          Copies the running configuration to the startup configuration.

           

          This example shows how to associate a virtual Fibre Channel interface to a VSAN:

          switch# configure terminal
          switch(config)# vsan database
          switch(config-vsan-db)# vsan 2 interface vfc 4
           

          Enabling VE Loopback Configuration

          The VFID check verifies that the VSAN configuration is correct on both ends of a VE link. You can turn off the VFID check for VE ports to allow VE loopback configuration between to VE ports on the same switch.


          Note


          For Cisco MDS 9500 and MDS 9250i switches, start at Step 2 .


          Before You Begin

          For Cisco Nexus 7000 Series, you must be in the storage VDC to configure this feature.

          SUMMARY STEPS

            1.    (Cisco Nexus 7000) switchto vdc vdc-id type storage

            2.    configure terminal

            3.    fcoe veloopback


          DETAILED STEPS
             Command or ActionPurpose
            Step 1 (Cisco Nexus 7000) switchto vdc vdc-id type storage

            Example:
            # switchto vdc fcoe type storage
            fcoe#
             

            Switches to the storage VDC. The step is required for Cisco Nexus 7000 Series only.

             
            Step 2 configure terminal


            Example:
            fcoe# configure terminal
            fcoe(config)#
             

            Enters configuration mode.

             
            Step 3 fcoe veloopback


            Example:
            fcoe(config)# fcoe veloopback
             

            Enables the VFID check for all VE ports.

             

            This example shows how to enable VE loopback for a Cisco Nexus 7000 Series switch:

            switch# switchto vdc fcoe type storage
            fcoe# configure terminal
            fcoe(config)# fcoe veloopback
            

            This example shows how to enable VE loopback for a Cisco MDS 9500 or an MDS 9250i switch:

            switch# configure terminal
            switch(config)# fcoe veloopback
            
            

            Verifying the Virtual Interface

            To display configuration information about virtual interfaces, perform one of the following tasks:

            Command

            Purpose

            show interface vfc vfc-id

            Displays the detailed configuration of the specified Fibre Channel interface.

            show interface brief

            Displays the status of all interfaces.

            show vlan fcoe

            Displays the mapping of FCoE VLANs to VSANs.

            This example shows how to display a virtual Fibre Channel interface bound to an Ethernet interface:

            switch# show interface vfc 3
            vfc3 is up
                Bound interface is Ethernet1/37
                Hardware is Virtual Fibre Channel
                Port WWN is 20:02:00:0d:ec:6d:95:3f
                Admin port mode is F, trunk mode is on
                snmp link state traps are enabled
                Port mode is F, FCID is 0x490100
                Port vsan is 931
                1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
                1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
                  0 frames input, 0 bytes
                    0 discards, 0 errors
                  0 frames output, 0 bytes
                    0 discards, 0 errors
                Interface last changed at Thu May 21 04:44:42 2009
             

            This example shows how to display the status of all the interfaces on the switch (some output has been removed for brevity):

            switch# show interface brief
            -------------------------------------------------------------------------------
            Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                              Mode   Trunk                          Mode  Speed  Channel
                                     Mode                                 (Gbps)
            -------------------------------------------------------------------------------
            fc3/1      1      auto   on      trunking         swl    TE      2    --
            fc3/2      1      auto   on      sfpAbsent        --     --           --
            ...
            fc3/8      1      auto   on      sfpAbsent        --     --           --
            -------------------------------------------------------------------------------
            Interface                Status     IP Address        Speed    MTU   Port
                                                                                 Channel
            -------------------------------------------------------------------------------
            Ethernet1/1              hwFailure  --                --       1500  --
            Ethernet1/2              hwFailure  --                --       1500  --
            Ethernet1/3              up         --                10000    1500  --
            ...
            Ethernet1/39             sfpIsAbsen --                --       1500  --
            Ethernet1/40             sfpIsAbsen --                --       1500  --
            -------------------------------------------------------------------------------
            Interface                Status     IP Address        Speed    MTU
            -------------------------------------------------------------------------------
            mgmt0                    up         172.16.24.41      100      1500
            -------------------------------------------------------------------------------
             
            -------------------------------------------------------------------------------
            Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                              Mode   Trunk                          Mode  Speed  Channel
                                     Mode                                 (Gbps)
            -------------------------------------------------------------------------------
            vfc 1        1      F      --      down             --     --           --
            ...
             

            This example shows how to display the mapping between the VLANs and VSANs on the switch:

            switch# show vlan fcoe
            VLAN      VSAN      Status
            --------  --------  --------
            15        15        Operational
            20        20        Operational
            25        25        Operational
            30        30        Non-operational
             

            Example:Mapping VSANs to VLANs

            The following example shows how to configure the FCoE VLAN and a virtual Fibre Channel interface:

            SUMMARY STEPS

              1.    Enable the associated VLAN and map the VLAN to a VSAN. For Cisco Nexus 7000, ensure you are in the storage VDC.

              2.    Configure the VLAN on a physical Ethernet interface.

              3.    Create a virtual Fibre Channel interface and bind it to a physical Ethernet interface. For Cisco Nexus 7000, ensure you are in the storage VDC.

              4.    Associate the virtual Fibre Channel interface to the VSAN. For Cisco Nexus 7000, ensure you are in the storage VDC.

              5.    (Optional) Display membership information for the VSAN.

              6.    (Optional) Display the interface information for the virtual Fibre Channel interface.


            DETAILED STEPS
              Step 1   Enable the associated VLAN and map the VLAN to a VSAN. For Cisco Nexus 7000, ensure you are in the storage VDC.
              switch(config)# vlan 200
              switch(config-vlan)# fcoe vsan 200
              switch(config-vlan)# exit
              
              
              Step 2   Configure the VLAN on a physical Ethernet interface.
              switch# configure terminal
              switch(config)# interface ethernet 1/4
              switch(config-if)# spanning-tree port type edge trunk
              switch(config-if)# switchport mode trunk
              switch(config-if)# switchport trunk allowed vlan 1,200
              switch(config-if)# exit
              
              
              Step 3   Create a virtual Fibre Channel interface and bind it to a physical Ethernet interface. For Cisco Nexus 7000, ensure you are in the storage VDC.
              switch(config)# interface vfc 4
              switch(config-if)# bind interface ethernet 1/4
              
              
              Note   

              By default, all virtual Fibre Channel interfaces reside on VSAN 1. If the VLAN to VSAN mapping is to a VSAN other than VSAN 1, then proceed to Step 4.

              Step 4   Associate the virtual Fibre Channel interface to the VSAN. For Cisco Nexus 7000, ensure you are in the storage VDC.
              switch(config)# vsan database
              switch(config-vsan)# vsan 200 interface vfc 4
              switch(config-vsan)# exit
              
              
              Step 5   (Optional) Display membership information for the VSAN.
              switch# show vsan 200 membership
              vsan 200 interfaces
                         vfc 4
              
               
              Step 6   (Optional)Display the interface information for the virtual Fibre Channel interface.
              switch# show interface vfc 4
              
              vfc4 is up
              Bound interface is Ethernet1/4
              Hardware is Virtual Fibre Channel
              Port WWN is 20:02:00:0d:ec:6d:95:3f 
              Port WWN is 20:02:00:0d:ec:6d:95:3f 
              snmp link state traps are enabled
              Port WWN is 20:02:00:0d:ec:6d:95:3f 
              APort WWN is 20:02:00:0d:ec:6d:95:3f
              snmp link state traps are enabled
              Port mode is F, FCID is 0x490100
              Port vsan is 200
              1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec 
              1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
              0 frames input, 0 bytes 0 discards, 0 errors 
              0 frames output, 0 bytes 0 discards, 0 errors
              Interface last changed at Thu Mar 11 04:44:42 2010
              

              Additional References for FCoE

              Related Documents

              Related Topic Document Title

              Command reference

              Cisco NX-OS FCoE Command Reference for Cisco Nexus 7000 and Cisco MDS 9500

              Cisco NX-OS licensing

              Cisco NX-OS Licensing Guide

              Standards and RFCs

              Standard/RFC Title
              T11 FC BB-5 Fibre Channel Backbone 5

              MIBs

              MIB MIBs Link
               

              To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

              http:/​/​www.cisco.com/​go/​mibs

              Technical Assistance

              Description Link

              The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

              To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

              Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

              http:/​/​www.cisco.com/​support