Nexus 5548 UP and FCoE an brocade

Hi,
I need help.
Architecture :
I have got two Nexus 5548UP .
The nexus are linked to 2 brocade 200e.
Esxi are conrected to Nexus 2248PP, Fcoe and Data >>> interface 101/1/9
Problem:
I try configured Fcoe to Esxi 5.0 but the interface vfc 1 still down.
My configuration :
fex 101
  pinning max-links 1
  description "FEX101-N2232PP-S12"
  fcoe
fex 102
  pinning max-links 1
  description "FEX102-N2232PP-Sxx"
  fcoe
slot 1
  port 31-32 type fc
vlan 2900
  fcoe vsan 2900
vsan database
  vsan 2900
feature npv
interface fc1/31
  no shutdown
interface fc1/32
interface Ethernet101/1/9
descri  TO-ESXI
  switchport mode trunk
vfc1 is down (Error disabled)
    Bound interface is Ethernet101/1/9
    Hardware is Ethernet
    Port WWN is 20:00:54:7f:ee:b6:4b:bf
    Admin port mode is F, trunk mode is on
    snmp link state traps are enabled
    Port vsan is 2900
    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
    last clearing of "show interface" counters never
Help me,
Cdlt,

Hi,
I had same configuration on both N5K.
I have removed the configuration Fcoe on second N5k.
Interface vfc1 seems to be  Ok.
But i have another problem, On esxi the Emulex One command plug-in  says  ethernet's interfaces is up.
But Vcenter sees them down !!
Emulex One command :
In the distibuted Vswitch :
But LLDP seems Ok :

Similar Messages

  • FCoE with Cisco Nexus 5548 switches and VMware ESXi 4.1

    Can someone share with me what needs to be setup on the Cisco Nexus side to work with VMware in the following scenario?
    Two servers with two cards dual port FCoE cards with two ports connected to two Nexus 5548 switches that are clusterd together.  We want to team the ports together on the VMware side using IP Hash so what should be done on the cisco side for this to work? 
    Thanks...

    Andres,
    The Cisco Road Map for the 5010 and 5020 doesn't include extending the current total (12) FEX capabities.  The 5548 and 5596 will support more (16) per 55xxk, and with the 7K will support upto 32 FEX's.
    Documentation has been spotty on this subject, because the term 5k indicates that all 5000 series switches will support extended FEX's which is not the case only the 55xx will support more than 12 FEX.  Maybe in the future the terminology for the 5k series should be term 5000 series and 5500 series Nexus, there are several differences and advancements between the two series.

  • Link FC between Nexus 5548 UP and Brocade 300

    Hello,
    I have got two Nexus 5548UP and fabric Brocade.
    I would like to connect my Nexus at my fabric Brocade.
    See the pdf file.
    Best regards,

    Its possible to have more links between npv and brocade but if you want to port channel them, please check first with brocade support if they allow F port channel trunking in their code. Not sure if FOS 6.2.2 supports it. From our side (cisco switch running npv) we should be able to do a port channel upto any NPIV switch provided the upstream switch supports it.
    https://supportforums.cisco.com/thread/2091664
    Thanks,
    Vinayak

  • FCoE using Brocade cards CNA1020 and Cisco Nexus 5548 switches

    All,
    I have the following configuration and problem that I am not sure how to fix:
    I  have three Dell R910 servers with 1TB of memory and each has two  brocade 1020 CNA cards dual port.  I am using distributed switches for  the VM network and a second distributed switch for VMotion.  I have two  of the 10G ports configured in each distributed switch using IP Hash.   The management network is configured using a standard switch with two 1G  ports.
    The  Nexus configuration is we have two nexus 5548 switch connected together  with a trunk.  We have two VPC's configured to each ESX hosts  consisting of two 10gig ports in each VPC with one port going to each  switch.  The VPC is configured for static LAG.
    What  I am seeing is that after a few hours the virtual machines will not be  accessible via network anymore.  So if you ping the VM it will not work  and if you get on the console of the VM then ping the gateway then  nothing as well but if you try to ping another virtual machine on the  same host on the same VLAN then it will work so traffic is going through  the ESX backplane.  If I reboot the ESX host then things will work  again for another few hours or so then the problem repeats.
    The version of vSphere I am using is ESXi4.1
    Please assist I am stuck.
    Thanks...

    Here is the link for Nexus and Brocade interoperability Matrix
    http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix7.html#wp313498
    usually this table would show those models those have been tested and verified
    However I do not see  Brocade 5300 listed in the table . It could be, interoperability may have not been tested by both vendors perticularly to 5300 type Model.

  • Fabric with two Nexus-5548 and a brocade switch does not get fabric updates

    We have a fabric containing two Nexus 5548 and a Brocade 5000 switch in interop mode 2. When i make changes to the zoning, the first nexus (the fabric principal) and the brocade switch see the zone changes. The second Nexus switch does not see it. There are no error messages but  the change just can't be seen.  What can i do to find out, what goes wrong ?

    Ouch, deprecated is not the word i wanted to read
    We are using 5.1(3)N1(1a) on nexus-rz1-a
    and 6.0(2)N1(2) on nexus-rz2-a.
    The fabric can be seen :
    nexus-rz2-a# show fcs ie vsan 10
    IE List for VSAN: 10
    IE-WWN                   IE     Mgmt-Id  Mgmt-Addr (Switch-name)
    10:00:00:05:1e:90:57:27  S(Rem) 0xfffc01 10.88.133.110 (bc-san1)
    20:0a:00:2a:6a:72:ba:01  S(Loc) 0xfffc1c 10.88.133.105 (nexus-rz2-a)
    20:0a:54:7f:ee:7f:dc:01  S(Adj) 0xfffc0b 10.88.133.100 (nexus-rz1-a)
    [Total 3 IEs in Fabric]
    nexus-rz1-a# show fcs ie vsan 10
    IE List for VSAN: 10
    IE-WWN                   IE     Mgmt-Id  Mgmt-Addr (Switch-name)
    10:00:00:05:1e:90:57:27  S(Adj) 0xfffc01 10.88.133.110 (bc-san1)
    20:0a:00:2a:6a:72:ba:01  S(Adj) 0xfffc1c 10.88.133.105 (nexus-rz2-a)
    20:0a:54:7f:ee:7f:dc:01  S(Loc) 0xfffc0b 10.88.133.100 (nexus-rz1-a)
    [Total 3 IEs in Fabric]
    I try to distribute the zoneset this way:
    zoneset distribute vsan 10
    Zoneset distribution initiated. check zone status
    nexus-rz1-a# show zone status
    VSAN: 10 default-zone: deny distribute: full Interop: 2
        mode: basic merge-control: allow
        session: none
        hard-zoning: enabled broadcast: disabled
    Default zone:
        qos: none broadcast: disabled ronly: unsupported
    Full Zoning Database :
        DB size: 6291 bytes
        Zonesets:1  Zones:62 Aliases: 44
    Active Zoning Database :
        DB size: 10243 bytes
        Name: FABRIC1  Zonesets:1  Zones:60
    Status: Zoneset distribution completed at 08:06:00 UTC Dec  3 2013
    nexus-rz2-a# show zone status
    VSAN: 1 default-zone: deny distribute: active only Interop: default
        mode: basic merge-control: allow
        session: none
        hard-zoning: enabled broadcast: disabled
    Default zone:
        qos: none broadcast: disabled ronly: unsupported
    Full Zoning Database :
        DB size: 4 bytes
        Zonesets:0  Zones:0 Aliases: 0
    Active Zoning Database :
        Database Not Available
    Status:
    VSAN: 10 default-zone: deny distribute: full Interop: 2
        mode: basic merge-control: allow
        session: none
        hard-zoning: enabled broadcast: disabled
    Default zone:
        qos: none broadcast: disabled ronly: unsupported
    Full Zoning Database :
        DB size: 6291 bytes
        Zonesets:1  Zones:62 Aliases: 44
    Active Zoning Database :
        DB size: 10243 bytes
        Name: FABRIC1  Zonesets:1  Zones:60
    Status: Activation completed at 13:03:42 UTC Dec  2 2013

  • Prime Infrastructure 2.0 and Nexus 5548, SSH credentials fail

    Hi,
    I'm having problem getting the Prime Infrastructure 2.0 to login with SSH to a Nexus 5548 to do an inventory. I get "Wrong Telnet/SSH credentials". But when I use the same credentials from another SSH-client it works fine. I also tested to SSH from the console of the Prime-server and that also works fine.
    Any ideas???
    Regards,
    Stefan Lindkvist

    I have PI 2.0 working against Nexus 5k's in two different installations. See below for an example (click to enlarge).
    Have you put in an entry in both the login and enable fields (even though they are not separately required when logging in directly)?

  • Nexus 5500 VoIP cos 3 and FCoE

    Hi
    I have a requirment to do QoS for a DC that includes some VoIP as well FCoE with CNAs in the servers. I want to use COS 3 for the VoIP signalling and drop it in the same input and output quues to the servers as FCoE.
    so we have
    class-map type qos class-fcoe
    class-map type queuing class-fcoe
      match qos-group 1
    which is the default for FCoE and I have 50% bandwidth assoicated with it.
    policy-map type queuing
         class type queuing class-fcoe
           bandwidth percent 50
         class type queing someother class etc
    The issue is the "class-fcoe" is a default class and there doesnt seem to be anywhere I can edit it to add the VOIP control traffic to the same class or can I just add it here:
    class-map type queuing match any class-fcoe
      match qos-group 1
      match cos 3
    Thanks
    Pat

    Hmm
    From the UCS 8 SRND
    For instance, voice signaling traffic with L3 DSCP  value of CS3 is mapped to L2 CoS value of 3 by Nexus 1000V. All Fibre  Channel over Ethernet (FCoE) traffic is marked with L2 CoS value of 3 by  Cisco UCS. When voice signaling and FCoE traffic enter the Cisco  UCS 6100 Fabric Interconnect Switch, both will carry a CoS value of 3.  In this situation voice signaling traffic will share queues and  scheduling with the Fibre Channel priority class and will be given  lossless behavior. (Fibre Channel priority class for CoS 3 in the  UCS 6100 Fabric Interconnect Switch does not imply that the class cannot  be shared with other types of traffic.)
    This seems ti pmply you can run Call SIgnalling COS 3 in the same queueu as FCOE COS 3. I kow its talking about a 6100 fabric switch but thats very similar to a 5500.
    Could I not do something like:
    class-map type qos match-all voice-signal-global
       match-cos 3
    policy-map type qos classify-global
       class voice-signal-global
          set qos-group 1
       class class-fcoe
          set qos-group 1
    But then I cant see how to link this where we set the queuing bandwidth percentages as this uses the "class-fcoe"
    policy-map type queuing global-fcoe-queuing-in
       class type queuing class-fcoe
          bandwidth percent 50
    Could I create a class to replace "class-fcoe" and jsut match on qos-group 1 to define whats in it ?
    Regards
    Pat

  • C220 M4 w/ VIC1225 and Nexus 5548

    I have four UCS C220 M4 servers that each have a VIC 1225 and are connected up to a Nexus 5548.  I have set them to trunk ports and have set the appropriate VLANs in ESX and the portgroups.  I can ping the gateway and other hosts on the network, but for some reason I can't ping any of the other C220 M4 servers that have a VIC1225.  All of the C220's can ping other devices on the network, but not each other.  Is there some setting I need to modify on the VIC or switch?  Currently the VIC is running as Classical Ethernet mode.

    There is no special configuration to make connectivity work in the rack servers, I assume these servers are in standalone mode and not integrated with UCSM.
    What L3 device is doing your Inter-Vlan routing? Is it the N5K these servers are connected to or there is another device doing this job?   If it is the N5K, are all the servers in the same network segment? I mean, is there a single SVI or multiple?  can your Nexus 5K ping each of the servers?
    -Kenny

  • Nexus 5548 and Define static route to forward traffic to Catalyst 4500

    Dear Experts,
    Need your technical assistance for the Static routing in between Nexus 5548 and Catalyst 4500.
    Further I connected both Nexus 5548 with Catalyst 4500 as individual trunk ports because there is HSRP on Catalyst 4500. So I just took 1 port from each nexus 5548, make it trunk with the Core Switch (Also make trunk from each Switch each port). Change the speed on Nexus to 1000 because other side on Catalyst 4500 line card is 1G RJ45.
    *Here is the Config on Nexus 5548 to make port a Trunk:*
    N5548-A/ N5548-B
    Interface Ethernet1/3
    Switchport mode trunk
    Speed 1000
    Added the static route on both nexus for Core HSRP IP: *ip route 0.0.0.0/0 10.10.150.39 (Virtual HSRP IP )*
    But I could not able to ping from N5548 Console to core Switch IP of HSRP? Is there any further configuration to enable routing or ping?
    Pleas suggest

    Hello,
    Please see attached config for both Nexus 5548. I dont have Catalyst 4500 but below is simple config what I applied:
    Both Catalyst 4500
    interface gig 3/48
    switchport mode trunk
    switchport trunk encap dot1q
    On Nexus 5548 Port 1/3 is trunk
    Thanks,
    Jehan

  • NPV and FCoE-NPV

    Hi,
    If I wish to enable NPV on a Nexus 5548 (so it can integrate with a 3rd party SAN switch), do I also need to enable FCoE-NPV?
    Enable NPV:
    switch(config)# npv enable
    Enable FCoE:
    switch(config)# feature fcoe
    FCoE-NPV:
    switch(config)# feature fcoe-npv
    That is, to use 'npv enable', do I need to use 'feature fcoe-npv'?
    I am trying to use FC to connect to a legacy SAN, while using FCoE to connect to servers in UCS. I'm not sure if I understand correctly, but I don't think I need FCoE-NPV to for UCS, but I do need to globally enable NPV for the Brocade switch.
    One last thing... I've read that when enabling NPV the switch will erase the config and reboot. Why is this? Or does this only happen if the switch already has SAN config?
    Thankyou

    Thankyou. Here is some more information on our environment.
    Our legacy system consists of Dell rack servers (The ones that run ESX have HBA's), IBM storage and 2x Brocade 300 SAN switches. The Brocades are not connected, so they run as separate fabrics. Most FC devices have dual-HBA's, so they can connect to both fabrics.
    Our new environment (still being built) uses Cisco UCS B series blades, and Nexus 5548 switching. For storage we use NetApp (NFS and CIFS, no FC/FCoE/iSCSI).
    We would like to connect the legacy and new environments, so one backup system can be used. I'd like to use FC for our new tape library, and continue using FC for our legacy. I'd like to be able to present storage to ESXi VMs running on the UCS blades.
    After doing some research, I think that making the 5k's the 'core' fabric would be best, which means putting the Brocade's into AG Mode (NPV). The FC ports on the 5k's would be in NPIV mode.
    As I understand it, the Fabric Interconnects (in end-host mode) are also in NPV. Does this mean I need to use 'feature fcoe' on the 5548's, but not 'feature fcoe-npv'?
    Does this plan make sense? Unfortunately I'm a networking guy, not a storage guy, so some of this may be way off.
    Thanks again for your help

  • ETS and FCoE

    I have heard some folks argue that ETS (Enhanced Transmission  Selection) is NOT required to make FCoE work. I'm thinking specdifically  of the case in which a CNA is connected to a DCB-capable Ethernet  switch that is doing FIP Snooping, which is then uplinked to, say, a  Cisco Nexus. The argument goes that the DCB-capable switch does NOT  require ETS support to make this design work and be stable.
    THOUGHTS?
    Thanks

    Thankyou. Here is some more information on our environment.
    Our legacy system consists of Dell rack servers (The ones that run ESX have HBA's), IBM storage and 2x Brocade 300 SAN switches. The Brocades are not connected, so they run as separate fabrics. Most FC devices have dual-HBA's, so they can connect to both fabrics.
    Our new environment (still being built) uses Cisco UCS B series blades, and Nexus 5548 switching. For storage we use NetApp (NFS and CIFS, no FC/FCoE/iSCSI).
    We would like to connect the legacy and new environments, so one backup system can be used. I'd like to use FC for our new tape library, and continue using FC for our legacy. I'd like to be able to present storage to ESXi VMs running on the UCS blades.
    After doing some research, I think that making the 5k's the 'core' fabric would be best, which means putting the Brocade's into AG Mode (NPV). The FC ports on the 5k's would be in NPIV mode.
    As I understand it, the Fabric Interconnects (in end-host mode) are also in NPV. Does this mean I need to use 'feature fcoe' on the 5548's, but not 'feature fcoe-npv'?
    Does this plan make sense? Unfortunately I'm a networking guy, not a storage guy, so some of this may be way off.
    Thanks again for your help

  • Ask the Expert: Cisco Nexus 2000, 5000, and 6000 Series Switches

    with Cisco Expert Vinayak Sudame
    Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions how to configure and troubleshoot the Cisco Nexus 2000, 5000 and 6000 Series Switches with Cisco subject matter expert Vinayak Sudame. You can ask any question on configuration, troubleshooting, features, design and Fiber Channel over Ethernet (FCoE).
    Vinayak Sudame is a Technical Lead in Data Center Switching Support Team within Cisco's Technical Services in RTP, North Carolina. His current responsibilities include but are not limited to Troubleshooting Technical support problems and Escalations in the areas of Nexus 5000, Nexus 2000, FCoE. Vinayak is also involved in developing technical content for Cisco Internal as well as external. eg, Nexus 5000 Troubleshooting Guide (CCO), Nexus 5000 portal (partners), etc. This involves cross team collaboration and working with multiple different teams within Cisco. Vinayak has also contributed to training account teams and partners in CAE (Customer Assurance Engineering) bootcamp dealing with Nexus 5000 technologies. In the past, Vinayak's responsibilities included supporting MDS platform (Fiber Channel Technologies) and work with EMC support on Escalated MDS cases. Vinayak was the Subject Matter Expert for Santap Technologies before moving to Nexus 5000 support. Vinayak holds a Masters in Electrical Engineering with Specialization in Networking from Wichita State University, Kansas. He also holds Cisco Certification CCIE (#20672) in Routing and Switching.
    Remember to use the rating system to let Vinayak know if you have received an adequate response.
    Vinayak might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the  Data Center sub-community, Other Data Center Topics discussion forum shortly after the event.
    This event last through Friday July 12, 2013. Visit the community often to view responses to youe questions of other community members.

    Hi Vinayak,
    Output of "show cfs internal ethernet-peer database"
    Switch 1
    ETH Fabric
    Switch WWN              logical-if_index
    20:00:54:7f:ee:b7:c2:80 [Local]
    20:00:54:7f:ee:b6:3f:80 16000005
    Total number of entries = 2
    Switch 2
    ETH Fabric
    Switch WWN              logical-if_index
    20:00:54:7f:ee:b6:3f:80 [Local]
    20:00:54:7f:ee:b7:c2:80 16000005
    Total number of entries = 2
    Output of "show system internal csm info trace"
    Switch 1 in which "show cfs peers" show proper output
    Mon Jul  1 05:46:19.145339  (CSM_T) csm_sp_buf_cmd_tbl_expand_range(8604): No range command in buf_cmd_tbl.
    Mon Jul  1 05:46:19.145280  (CSM_T) csm_set_sync_status(6257): Peer RT status PSSed
    Mon Jul  1 05:46:19.145188  (CSM_T) csm_sp_handle_local_verify_commit(4291):
    Mon Jul  1 05:46:19.145131  csm_continue_verify_ac[597]: peer is not reachable over CFS so continuing with local verify/commit
    Mon Jul  1 05:46:19.145071  csm_tl_lock(766): Peer information not found for IP address: '172.16.1.54'
    Mon Jul  1 05:46:19.145011  csm_tl_lock(737):
    Mon Jul  1 05:46:19.144955  (CSM_EV) csm_sp_build_tl_lock_req_n_send(941): sending lock-request for CONF_SYNC_TL_SESSION_TYPE_VERIFY subtype 0 to Peer ip = (172.16.1.54)
    Mon Jul  1 05:46:19.143819  (CSM_T) csm_copy_image_and_internal_versions(788): sw_img_ver: 5.2(1)N1(2a), int_rev: 1
    Mon Jul  1 05:46:19.143761  (CSM_T) csm_sp_get_peer_sync_rev(329): found the peer with address=172.16.1.54 and sync_rev=78
    Mon Jul  1 05:46:19.143699  (CSM_T) csm_sp_get_peer_sync_rev(315):
    Mon Jul  1 05:46:19.143641  (CSM_EV) csm_sp_build_tl_lock_req_n_send(838): Entered fn
    Mon Jul  1 05:46:19.143582  (CSM_T) csm_set_sync_status(6257): Peer RT status PSSed
    Switch 2 in which "show cfs peers" does not show proper output
    Mon Jul  1 06:13:11.885354  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 77 seq 482
    Mon Jul  1 06:13:11.884992  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd channel-group 51 mode active, cmd pseq 357 seq 369
    Mon Jul  1 06:13:11.884932  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport trunk allowed vlan 2, 11, cmd pseq 357 seq 368
    Mon Jul  1 06:13:11.884872  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 357 seq 367
    Mon Jul  1 06:13:11.884811  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd description process_vpc, cmd pseq 357 seq 366
    Mon Jul  1 06:13:11.884750  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd channel-group 51 mode active, cmd pseq 352 seq 365
    Mon Jul  1 06:13:11.884690  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport trunk allowed vlan 2, 11, cmd pseq 352 seq 364
    Mon Jul  1 06:13:11.884630  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 352 seq 363
    Mon Jul  1 06:13:11.884568  (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd description process_vpc, cmd pseq 352 seq 362
    Mon Jul  1 06:13:11.884207  (CSM_EV) csm_sp_acfg_gen_handler(3011):  Preparing config into /tmp/csm_sp_acfg_1733916569.txt
    Mon Jul  1 06:13:11.878695  csm_get_locked_ssn_ctxt[539]: Lock not yet taken.
    Mon Jul  1 06:13:11.878638  (CSM_EV) csm_sp_acfg_gen_handler(2937): Recieved sp acfg merge request for type: running cfg
    Mon Jul  1 06:12:29.527840  (CSM_T) csm_pss_del_seq_tbl(1989): Freeing seq tbl data
    Mon Jul  1 06:12:29.513255  (CSM_T) csm_sp_acfg_gen_handler(3106): Done acfg file write
    Mon Jul  1 06:12:29.513179  (CSM_EV) csm_sp_acfg_gen_handler(3011):  Preparing config into /tmp/csm_sp_acfg_1733911262.txt
    Mon Jul  1 06:12:29.508859  csm_get_locked_ssn_ctxt[539]: Lock not yet taken.
    Mon Jul  1 06:12:29.508803  (CSM_EV) csm_sp_acfg_gen_handler(2937): Recieved sp acfg merge request for type: running cfg
    Mon Jul  1 05:53:17.651236  Collecting peer info
    Mon Jul  1 05:53:17.651181  Failed to get the argumentvalue for 'ip-address'
    Mon Jul  1 05:40:59.262736  DB Unlocked Successfully
    Mon Jul  1 05:40:59.262654  Unlocking DB, Lock Owner Details:Client:1 ID:1
    Mon Jul  1 05:40:59.262570  (CSM_T) csm_sp_del_buf_cmd(1713): Deleting comand with Id = 1
    Mon Jul  1 05:40:59.262513  DB Lock Successful by Client:1 ID:1
    Mon Jul  1 05:40:59.262435  Recieved lock request by Client:1 ID:1
    Mon Jul  1 05:40:41.741224  ssnmgr_ssn_handle_create_get: Session FSM already present, ID:1
    Mon Jul  1 05:40:41.741167  ssnmgr_handle_mgmt_request: Create/Get request received for session[process_n5kprof]
    show cfs lock gives no output.
    Just to further clarify, we have 4 5548UP switches in the same management vlan. 2 switches are in one location lets say location A and they are CFS peers and are working fine.
    These two switches which are having problem are in location B. All the switches are in the same vlan. Essentially the all CFS multicast messages will be seen by all 5548 switches as they are in the same vlan. I am assuming that this might not create any problems as we specify the peers in the respective configurations. Or do we have to change the CFSoIPv4 multicast addresses in location B or may be configure a different region.
    Regards.

  • FC ports on nexus 5548?

    Hi, I would like to know how many maximum FC ports can one have on a Nexus 5548 (N5K-C5548UP) without any expansion module? I have the FC_FEATURES_PKG license installed.

    Cisco Nexus 5548UP Switch
    The Cisco Nexus 5548UP (Figure 2) is a 1RU 10 Gigabit Ethernet, Fibre Channel, and FCoE switch offering up to 960 Gbps of throughput and up to 48 ports. The switch has 32 unified ports and one expansion slot.

  • UCS FI 6248 to Nexus 5548 San port-channel - not working

    Hi all,
    I'm sure I am missing something fairly obvious and stupid but I need several sets of eyes and help.
    Here is the scenario:
    I want to be able to create san port-channels between the FI and Nexus.  I don't need to trunk yet as I can't even get the channel to come up.
    UCS FI 6248:
    Interfaces fc1/31-32
    Nexus 5548
    interfaces fc2/15-16
    FI is in end-host mode and Nexus is running NPIV mode with fport-channel-trunk feature enabled.
    I'm going to output the relevants configurations below.
    Nexus 5548:
    NX5KA(config)# show feature | include enabled
    fcoe                  1         enabled
    fex                   1         enabled
    fport-channel-trunk   1         enabled
    hsrp_engine           1         enabled
    interface-vlan        1         enabled
    lacp                  1         enabled
    lldp                  1         enabled
    npiv                  1         enabled
    sshServer             1         enabled
    vpc                   1         enabled
    interface san-port-channel 133
      channel mode active
      no switchport trunk allowed  vsan all
      switchport trunk mode off
    interface fc2/15
      switchport trunk mode off
      channel-group 133 force
    no shutdown
    interface fc2/16
      switchport trunk mode off
      channel-group 133 force
    no shutdown
    NX5KA# show vsan membership
    vsan 1 interfaces:
        fc2/13            fc2/14          
    vsan 133 interfaces:
        fc2/15            fc2/16            san-port-channel 133
    vsan 4079(evfp_isolated_vsan) interfaces:
    vsan 4094(isolated_vsan) interfaces:
    NX5KA# show san-port-channel summary
    U-Up D-Down B-Hot-standby S-Suspended I-Individual link
    summary header
    Group  Port-      Type    Protocol               Member Ports
           Channel
    133    San-po133  FC      PCP      (D)  FC       fc2/15(D)    fc2/16(D)   
    UCS Fabric Interconnect outputs:
    UCS-FI-A-A(nxos)# show san-port-channel summary
    U-Up D-Down B-Hot-standby S-Suspended I-Individual link
    summary header
    Group  Port-      Type    Protocol               Member Ports
           Channel
    133    San-po133  FC      PCP      (D)  FC       fc1/31(D)    fc1/32(D)   
    UCS-FI-A-A(nxos)#
    UCS-FI-A-A(nxos)# show run int fc1/31-32
    !Command: show running-config interface fc1/31-32
    !Time: Fri Dec 20 22:58:51 2013
    version 5.2(3)N2(2.21b)
    interface fc1/31
      switchport mode NP
      channel-group 133 force
      no shutdown
    interface fc1/32
      switchport mode NP
      channel-group 133 force
      no shutdown
    UCS-FI-A-A(nxos)#
    UCS-FI-A-A(nxos)# show run int san-port-channel 133
    !Command: show running-config interface san-port-channel 133
    !Time: Fri Dec 20 22:59:09 2013
    version 5.2(3)N2(2.21b)
    interface san-port-channel 133
      channel mode active
      switchport mode NP

    !Command: show running-config interface san-port-channel 133
    !Time: Sat May 16 04:59:07 2009
    version 5.1(3)N1(1)
    interface san-port-channel 133
      channel mode active
      switchport mode F
      switchport trunk mode off
    Changed it as you suggested...
    Followed the order of operations for "no shut"
    Nexus FC -> Nexus SAN-PC -> FI FC -> FI SAN-PC.
    Didn't work:
    NX5KA(config-if)# show san-port-channel summary
    U-Up D-Down B-Hot-standby S-Suspended I-Individual link
    summary header
    Group  Port-      Type    Protocol               Member Ports
           Channel
    133    San-po133  FC      PCP      (D)  FC       fc2/15(D)    fc2/16(D)
    NX5KA(config-if)#
    Here is the output as you requested:
    NX5KA(config-if)# show int san-port-channel 133
    san-port-channel 133 is down (No operational members)
        Hardware is Fibre Channel
        Port WWN is 24:85:00:2a:6a:5a:81:00
        Admin port mode is F, trunk mode is off
        snmp link state traps are enabled
        Port vsan is 133
        1 minute input rate 1256 bits/sec, 157 bytes/sec, 0 frames/sec
        1 minute output rate 248 bits/sec, 31 bytes/sec, 0 frames/sec
          3966 frames input, 615568 bytes
            0 discards, 0 errors
            0 CRC,  0 unknown class
            0 too long, 0 too short
          2956 frames output, 143624 bytes
            0 discards, 0 errors
          46 input OLS, 41 LRR, 73 NOS, 0 loop inits
          257 output OLS, 189 LRR, 219 NOS, 0 loop inits
        last clearing of "show interface" counters never
        Member[1] : fc2/15
        Member[2] : fc2/16
    NX5KA(config-if)#
    NX5KA(config-if)# show int brief
    Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                      Mode   Trunk                          Mode  Speed  Channel
                             Mode                                 (Gbps)
    fc2/13     1      auto   on      sfpAbsent        --     --           --
    fc2/14     1      auto   on      sfpAbsent        --     --           --
    fc2/15     133    F      off     init             swl    --           133
    fc2/16     133    F      off     init             swl    --           133

  • Telephony Issues on Nexus 5548

    Dear Viewers,
    I have Nexus 5548 devices in one of my client data centers and i have one 3750 switch to which all of these Avaya voice servers connect.
    The 3750 switch was initially connected through a L2 Link to a 6509 catalyst switch and the telephony applications were working correctly.
    The problem arises when i move this 3750 layer 2 link to a Nexus 5548 (OS version 5.1(3)N1 switch. All telephony calls coming from the outside (External calls) are not working as required but the internal calls work as usual.
    What is odd is that when i migrate this L2 link back to the 6509 switch, all works as usual. This is just a layer 2 connection and i am wondering why this is not possible.
    The vlan is accepted on all relevant trunks. I also deactivated igmp snooping on this voice vlan on the Nexus 5548 thinking it would help but in vain.
    Any ideas and suggestions are welcome.
    regards.
    Alain

    This is my radius config......  on a 5K
    radius-server timeout 7
    radius-server host 10.28.42.20 key 7 "Password" auth-port 1645 acct-port 1646 authentication accounting
    radius-server host 10.28.42.21 key 7 "Password" auth-port 1645 acct-port 1646 authentication accounting
    aaa group server radius Radius-Servers
     server 10.28.42.20
     server 10.28.42.21
    aaa authentication login default group Radius-Servers
    ip radius source-interface Vlan1
    aaa authentication login default fallback error local
    And it is currently working. On the radius server i also had to do this to make the users admins once logged in:
    https://supportforums.cisco.com/document/137181/nexus-integration-admin-access-free-radius

Maybe you are looking for