NEXUS Multicast questions

I have a question in regards to multicast support for the NEXUS 1000V/4001i/5548 w/L3 Daughter card.  Before the questions a quick background:  We are in the process of buying a IBM blade center with the aforementioned network pieces.  We are a modeling and simulations site and the servers we use primarily communicate via multicast.  Typically 6 class C’s worth of multicast addresses are reserved for this per event.  I was looking at doing layer 3 on the 5548’s but it has a limitation of 2000 multicast entries and I’m not even sure what that means i.e per VLAN/VRF or just total.  We have 4 suites - so if we run two events at the same time we will bust that number quick.  So we will continue to do layer 3 at the 6509’s for mcast and the nexus family will handle it at layer 2.
My real questions and concerns are these:
The 4001i states it will hold 1000 IGMP (Snooping) entries. What happens when it exceeds this number?  Should we just turn IGMP snooping off and let it flood everything in that VLAN (I have my concerns with that).
I cannot find any multicast limitations on the 1000v – are there any?
Any advice/help will be greatly appreciated. 
Thanks
Brad

Ex,
Yes, all three Nexus products are available for order as of today.
As for Fabric Path, it's currently only supported on the Nexus 7K, with the F1 Line cards running NXOS 5.1 or later.  Fabric Path will be available on the 5548/5596 running 5.1(3)N1(1) codename "Fairhaven" release of NXOS.  Currenlty targeting mid-late 2011.
FYI - Fabric Path will require a separate license.
Regards,
Robert

Similar Messages

  • Cisco WVC210 WLAN Camera - multicasting question

    Hello,
    it act's about the CISCO WC210 WLAN Camera, I would be really happy, if somebody could help us to eliminate our problem 
    Informatiom
    We are using the WVC210 WLAN-Cameras (http://ww:w.cisco.com/en/US/products/ps9948/), this camera has a web server, so is accessible over a normal web-browser, to see the video transmission.
    We just set it up with a normal WLAN-Router, so the camera is connected wireless to the router, and this router is connected to the internet (WAN).
    With the cisco video-software or the web-interface, it's now possible to stream the video.
    Our questions:
    Now we like to stream the Video on our Website, so people what visit our site can take a look at our company and so on.
    We are able to stream the Video with the MJEPG-Format, like the camera web-interfaces offers...
    The problem is, with normal ip-transfer method, each user would connect directly to the camera and increases the data-transfer, the internet-connection will than overload easily.
    But the camera supports multi-casting,  so the camera only transmit one data stream and all clients connected to this stream will receive the packages.
    Our problem is, we do not have any knowledge about multi-casting and how it works, the camera has a normal ip-address and a pre-configured multicast address with group name, so how can we connect a client to this multicast group, without increasing the data-transfer with each new user?
    Would you recommend us to use the multicast function of this camera or put a server between the camera and the website?
    Could you give as advice or some kind of tutorial, how we can set up this multicast service and easily get a player for the stream on our website, without using many plug ins or special apps ?
    Looking forward for your help, thank you all
    Regards
    Markus
    P.s.: You can also reply in german

    Hi, your general understanding of multicast is correct, but I don't think there is any multicast in general use on the Internet today.  In the mid 1990's there was a thing called MBONE that experimented with this idea for basically the same application as you describe- to multicast video.  Check Google or wikipedia for some history of MBONE in case you are interested. That said, you should be able to use the multicast ability on your own LAN/WAN environment if that helps you at all.
    I think the way people stream video to many users via the Internet today is essentially by having a lot of bandwidth and CPU.  You could probably find places to host your video and 'rebroadcast' it via their servers and Internet bandwidth.   Take a look a qik.com for an example of something that might help you.  There must be other services similar to qik that can 'rebroadcast' video streams that you only send one stream to them and they let multiple users see it.  I would expect to pay something for this service, but you might find free, ad supported services.
    Good luck and let us know what you end up doing.
    brandon

  • Nexus Lab Question

    Just getting wet around the ears on the Nexus line and have two small labs with a couple simple questions:
    Environment 1:
    1. Single N5K.
    2. Cisco UCS C-Series C220 M3 w/VIC1225.
    3. VNX SAN
    As a test, I would like to leverage the NIC virtualization technology to "unify" both normal LAN and iSCSI traffic.  Obviously wouldn't be using vPC as I only have a single switch in this lab.  Should this be possible is my only question?  Just looking for reassurance.
    Environment2:
    1. Two N5K w/L3
    3. Two B22 FEX Modules
    4. Dell M620 w/QLogic 10GB CNA
    5. VNX SAN
    As a test, I would like to leverage the NIC virtualization technology to "unify" both normal LAN and iSCSI traffic as well as vPC.  Has anyone successfully connected QLogic vNICs to N5K with vntag on the switchport?
    Sorry for the noob questions but really want to ensure I don't start this by banging my head early.
    Thanks,
    D

    Padma, again thanks for the feedback but I think I must still be missing something.  Here is what I have:
    1. Dell M620 Blade server
    2. QLogic CNA with iSCSI HBA offloading capabilities (Dual 10GB ports) - 8200 series I believe
    3. Pair of Cisco Nexus B22 FEX in Dell chassis
    4. Pair of Cisco N5Ks
    I want to utilize the dual 10GB ports for both LAN and iSCSI rather than using an completely separate NIC in another fabric slot of my chassis.  This would reduce my cabling, power, etc.  With that said, are you saying all I need to do is create a separate VLAN for iSCSI, have the CNA iSCSI HBA offload the processing and have the N5Ks provide QoS to that specific iSCSI VLAN?  Is it that simple?

  • Nexus Design Question

    Here's the scenario:
    We're working on a new DC design. Dual 6509VSS in core, dual Nexus 5k and 14 FEXs. The 2ks will be dual attached to the 5ks.
    Now, I read somewhere else that the 5k is limited to a maximum of 16 vPCs.
    So the question comes up... does that mean that the current design with a vPC to the core VSS, the peer vPC and all 14 vPCs to the FEX are topping us out?
    Also, all of the designs I've seen have only 2 5ks peering together. Can you have 3 or 4 5ks peer together?
    Thanks.

    I have to make the same design: VSS + 2x N5000. Currently i don't plan to connect the N5000 w. VPC upstream to C6500-VSS (i do plan VPC downstream). I plan to connect each N5000 individually to the VSS chassis with 2x 10G MEC. On the N5000, this is just a local portchannel. Since the connection between the N5000 is only used for VPC and is not considered as a real L2 link, there is no STP loop in this design.
    If the downsteam devices alternate their active/passive links between N5-1 and N5-2, both N5s will carry traffic.
    PS. i have more confidence in a simple portchannel. You don't want VPC problems (crash/early deployment problems) on the uplinks to VSS, basically isolating your datacenter or risking L2 loops.
    PPS. one remark i still have here is: on the N5K, you don't want to connect the uplinks towards VSS on adjacent ports using the same port-group. If the port-group ASIC fails, you will be blackholing traffic in the datacenter as the downstream interfaces will remain up. On C3750 switches, this is solved by Link State Tracking, however this is not supported on N5K, which i really regret. But Cisco says: we don't need Link State Tracking on N5K, as the N5K supports VPc to work around this....However, i feel this is not an excuse to not implement LinkStateTracking in N5K. VPc indeed is usefull if the upstream switches are L2 connected, however, if the upstreams are VSS switches a simple portchannel with link state tracking would suffice and have faster convergence....
    regards,
    Geert

  • Nexus 6004: Question about port-profile type port-channel

    I'm setting up a new deployment of Nexus 6004 switches and want to utilize port-profiles as much as possible to simplify management down the road.
    All uplinks to other switches, routers and firewalls will be connected using VPC:s. On the port-channels (vpc) the only thing that will change over time is the allowed vlans.
    It seems that port-profiles of the type port-channel does not behave in the same way as those with type ethernet, at least not when adding vlans.
    If I modify the port-profile using "switchport trunk allowed vlan add XXX" it will delete the previous config and only retain "switchport trunk allowed vlan add XXX", and not merge it with the previous config as is expected. 
    Question: Is this a bug or is it working as intended?
    RH_N6K4_01(config-sync)# switch-profile rh
    Switch-Profile started, Profile ID is 1
    RH_N6K4_01(config-sync-sp)# port-profile type port-channel FIREWALL-UPLINK
    RH_N6K4_01(config-sync-port-prof)# switchport trunk allowed vlan 3
    RH_N6K4_01(config-sync-port-prof)# verify 
    Verification Successful
    RH_N6K4_01(config-sync-sp)# commit
    Verification successful...
    Proceeding to apply configuration. This might take a while depending on amount of configuration in buffer.
    Please avoid other configuration changes during this time.
    Commit Successful
    RH_N6K4_01(config-sync)# show port-profile 
    SHOW PORT_PROFILE
    port-profile FIREWALL-UPLINK
     type: Port-channel
     description: 
     status: enabled
     max-ports: 512
     inherit: 
     config attributes:
      switchport mode trunk
      switchport trunk allowed vlan 3
     evaluated config attributes:
      switchport mode trunk
      switchport trunk allowed vlan 3
     assigned interfaces:
    ===================================
    RH_N6K4_01(config-sync-sp)# port-profile type port-channel FIREWALL-UPLINK
    RH_N6K4_01(config-sync-port-prof)# switchport trunk allowed vlan add 84
    RH_N6K4_01(config-sync-port-prof)# verify 
    Verification Successful
    RH_N6K4_01(config-sync-sp)# commit 
    Verification successful...
    Proceeding to apply configuration. This might take a while depending on amount of configuration in buffer.
    Please avoid other configuration changes during this time.
    Commit Successful
    RH_N6K4_01(config-sync)# show port-profile 
    SHOW PORT_PROFILE
    port-profile FIREWALL-UPLINK
     type: Port-channel
     description: 
     status: enabled
     max-ports: 512
     inherit: 
     config attributes:
      switchport mode trunk
      switchport trunk allowed vlan add 84
     evaluated config attributes:
      switchport mode trunk
      switchport trunk allowed vlan add 84
     assigned interfaces:
    Expected behavior here would be "switchport trunk allowed vlan 3,84". This only occurs when using "port-profile type port-channel" not when using "port-profile type ethernet"

    <> is template syntax and is generally the type of object a container holds..   So it is defining that the MSGQUEUE type is a deque holding struct_buffer*'s.

  • A follow-up Multicasting question (brh0001?)

    But does the fact that I can't use my LocalHost to multicast internaly, mean that I must be connected to the web throughout the simulation??
    (Otherwise I got "Network unreachable".)
    Mustn't there be some alternative?
    Thanx.

    Yep, I am trying to run the whole process on the same machine.
    In fact it's the first project I run on LINUX and I haven't got the right modem for net connection from there...
    Thanx-a -lot, anyway.

  • Multicast questions

    Good Morning.
    We were looking to deploy wireless VoIP phones into our environment. These phones have a PTT feature which utilizes Multicast.
    I was looking into configuring Multicast mode on the wireless controller and access points in our network. Do you think this is necessary or at least recommended for the PTT application or do I just let the unicast mode continue to function.
    Also if we do enable multi-cast mode and videostream it is not supported on the Flex AP's. Would the Flex AP's still join the controllers or would we have to move the Flex AP's to another controller?

    Saravanan Lakshmanan wrote:Does the Flex AP's default to Multicast-Unicast even if Multicast-Multicast is set on the global controller config?//No, it doesn't receive Multicast packets from WLC.Let see what're the parameters that can affect Multicast forwarding:#WLC platform.#Global AP Multicast mode config at WLC.#Mode of the AP - Local, Flexconnect central switching.#With flex Local switching, it doesn't even send/receive the packet to/from WLC, so it doesn't matter what Multicast mode is configured on wlc. Multicast support on different WLC platforms:#WLC 5500/WiSM2/8500 supports both Multicast and Unicast mode.#WLC 2500 supports Multicast to Multicast only.#WLC 7500 & vWLC supports Multicast to Unicast only. Supports Flex APs only. #Flexconnect mode AP can't join Multicast group address configured at WLC -> AP mode Multicast to Multicast. Since it is not joined to the Multicast group, it can't receive Multicast packet that are sent by WLC(and Multicast packet sent by flex central switching will be received by local mode APs only). If Multicast needs to be forwarded for flexconnect central switching then configure AP mode Multicast to Unicast. Remember, it is global config that's applicable for local mode AP also. #WLC 5500/WiSM2/8500 supports both Multicast and Unicast mode.//When mix of local mode AP and flex central switching is used where flex centrally switched wlan need to forward/receive Multicast traffic then need to set "AP Multicast mode to Unicast only". (With Multicast mode enabled, WLC can't send one copy to the Multicast address and individual copies to the Flex mode APs.) #WLC 2500 supports Multicast to Multicast only.//Flex central switched APs can't receive Multicast packets since it doesn't support Unicast mode. Use Flex local switching as workaround in this case. #WLC 7500 & vWLC supports Multicast to Unicast only. Supports Flex APs only.//It supports only Flex APs, so Multicast to Unicast is the only applicable config that is allowed. Since it is not cco documented, will try to address this on Multicast section of config guide.
    So I read this again. Say we have Flex Central switching then we MUST configure AP unicast if the clients on the Flex AP need to be able to stream multicast? So if that is the case then the client just wont be able to join the multicast group?

  • Nexus 7K question regarding N7K-F132XP-15

    Dear expert,
    I work in Cisco lab and doing performance demo on mobile packet core solutions. We have a Next 7000 10 slot chassis with 3 32 port 10G modules(N7K-M132XP-12L). Since N7K-M132XP-12L limit total bandwidth to 80G, we want to get several new 32 port 1G and 10G F module(N7K-F132XP-15). I have a few questions through:
    1, Can N7K-F132XP-15 and N7K-M132XP-12L co-exist in same chassis? My feeling is "yes" but want to confirm.
    2, N7K-F132XP-15 can have 230G bandwidth to switch fabric given 5 switch fabric installed, how does 230G distribute to each goup of 8 ports(or 4 ports maybe)? I know for N7K-M132XP-12L, group of 4 ports share 10G, any such limitation for  N7K-F132XP-15?
    3, N7K-F132XP-15 appears to be less expensive than N7K-M132XP-12L even it has more bandwidth, do I loss something compare to N7K-M132XP-12L?
    Thanks a lot
    Ning Chen
    Technical Marketing Engineer
    Cisco

    Hi Ning
    I can help out on a few, so to answer:
    1) Yes, you can have both N7K-F132XP-15 and N7K-M132XP-12L in the same chassis
    2) I'm not sure on this one, will have to look into some specs on it.  Perhaps someone else knows, feel free to chime in
    3) Keep in mind the N7K-F132XP-15 (F1 module) is not very comparable to N7K-M132XP-12L(M1 module).  F1 modules are L2 only, so no routing is done on the linecard itself.  F1 can do fabricpath where as M1 cannot.
    Depending on what you want to do with the module the M1 may be a better choice.  If you are looking at pure L2 then F1 is fine, and then you can even take advantage of FabricPath, however if you want to do any L3 you need the M1 modules.
    Hope that helps
    Chad

  • Nexus 5500 Questions

    Hello -
    Are the Nexus 5548P, 5548UP and 5596UP switches shipping?
    Also, do they offer Fabric Path?
    Thanks

    Ex,
    Yes, all three Nexus products are available for order as of today.
    As for Fabric Path, it's currently only supported on the Nexus 7K, with the F1 Line cards running NXOS 5.1 or later.  Fabric Path will be available on the 5548/5596 running 5.1(3)N1(1) codename "Fairhaven" release of NXOS.  Currenlty targeting mid-late 2011.
    FYI - Fabric Path will require a separate license.
    Regards,
    Robert

  • After using the terminal,wireless connection is gone

    Yesterday I was looking online to see ''how can I transfer pictures,files from my Nexus 7 tablet to my desktop computer with the usb cable''..
    I've found several support forums like this one I'm using right now,someone has already asked a question like mine so I followed the best answer,
    I typed the commands in the terminal as the helper suggested,then I restarted my desktop pc,after that it didn't connect any more,it connects wireless usually,but since yesterday no connection:(
    I still have the page/link that shows the answer I've followed (the top one) :
    http://askubuntu.com/questions/207569/how-do-i-connect-a-nexus-7-to-transfer-files
    thank you!!

    Hello mediterranean,
    Thank you for contacting Mozilla Support. Are you having trouble getting a wireless connection on your Ubuntu machine? This is probably not the best forum for Ubuntu or Nexus 7 questions, but you might try taking a look at this article:
    http://askubuntu.com/questions/247993/cant-connect-to-any-wireless-connection-after-updating
    Cheers,
    Patrick

  • Technical quicktime support?!

    where do i get fast & cheap technical support concerning my quicktime & multicast questions?
    i have a quicktime pro serial number.

    Hmmmm, exactly what to do consider cheap?
    If you have AppleCare then technical support is FREE for 3 years. If you don't have AC, then tech support I believe is around $40.<--- Cheap enough for ya?
    Apple Discussions is FREE.
    <img src="http://i33.tinypic.com/2pt3yia.gif">

  • Cant reach wlc

    hi,
    we have two wlc connected to two Nexus (WLC1 hangs off Nexus 1 and WLC 2 hangs off Nexus 2). Both Nexus are connected using vPC. when i connect an AP to join to the network for some reason the AP cant only see one WLC. so the first time it connects to WLC 1 then if i connect an AP using the same lead it wont connect to WLC1 and will need to connect to WLC2 (i removed the AP and connceted by laptop and found that i cant ping wlc 1 and hence it wouldnt connect)
    but if i can ping both wlc from another port in the switch which has not been used for an AP. so once i use a port to connect an AP to connect to network, it will only ping 1 wlc. So is there any sort of load balancing that could be configured that will allow round robin methond of connecting AP's. I tried looking at the settings on WLC but cant seem to find any (except for under LOAD BALANCING, it says default settings)
    Thanks

    Honestly, that sounds more like a Nexus/Switching question than a wireless one.
    HTH,
    Steve
    Please remember to rate useful posts, and mark questions as answered

  • WDS & MDT 2012 Integration Questions: Do I need an install image on WDS if I'm multicasting from MDT

    I'm running WDS & MDT 2012 on Server 2012 for my deployment solution.  I have a few questions about what happens when you integrate WDS & MDT.
    Perhaps this is a simple question, but if WDS multicasts the installation image from MDT, do I need to have an image in the installation folder of WDS?  I have the "Enable multicasting" box checked whenever I update my deployment share
    Also, my server is running X64 architecture, so I have the x64 WAIK installed.  but I'm having issues editing the unattend.xml on my server because my images are all X86.  Keeping in mind that I already have the X64 WAIK installed, can i install
    the X86 WAIK tools on my server?

    Sorry, that's two questions you only get one... Just kidding...
    FOr MDT, you don't import the images into the WDS console, you just need to add a Multicast namespace.
    http://keithga.wordpress.com/2014/04/23/multicasting-with-mdt/
    AS for the unattend.xml edit issue, that is known:
    http://blogs.technet.com/b/deploymentguys/archive/2009/08/27/windows-7-waik-and-custom-images.aspx
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • DMVPN w/ Multicasting setup/questions

    Hello
    I have a lot of questions, so bare with me as i puke them out of my head.
    I have been doing some testing with DMVPN inconjuction with multicasting video (Hub and spoke, w/ no spoke to spoke). The test setup is using 2 cisco 2811 w/out the vpn module.  I understand the performance hit with not having the module. With that being said here are my questions.
    1. With encryption on both the HUB and spoke routers are using 90-97% cpu (8Mb multicast stream).  With encryption off, the Hub is around 60%, and spoke around 75%.  Here is where i'm confused.  If i send that same stream as a unicast stream, w/ encryption on, both the Hub and spoke are only using around 30-35% cpu.  Why is there so much more cpu need when its a multicast stream?
    2. In the current config i'm seeing input, throttles, and ignore errors on the Hub and spoke.  The Hub has these errors on the LAN interface, and the spoke has these errors on the WAN interface. All other interfaces are totally clean.  I have checked and there are no duplex or speed mismatches.  Any ideas?
    HUB:
    Current configuration : 1837 bytes
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    hostname Hub
    boot-start-marker
    boot-end-marker
    logging message-counter syslog
    enable password
    no aaa new-model
    clock timezone Central -6
    dot11 syslog
    ip source-route
    ip cef
    no ip domain lookup
    ip name-server 8.8.8.8
    ip multicast-routing
    no ipv6 cef
    multilink bundle-name authenticated
    voice-card 0
    archive
    log config
      hidekeys
    interface Tunnel1
    bandwidth 100000
    ip address 192.168.11.1 255.255.255.0
    no ip redirects
    ip mtu 1400
    no ip next-hop-self eigrp 1
    ip pim sparse-mode
    ip nhrp map multicast dynamic
    ip nhrp network-id 1
    ip nhrp holdtime 450
    no ip route-cache cef
    ip tcp adjust-mss 1360
    no ip split-horizon eigrp 1
    delay 1000
    tunnel source FastEthernet0/0
    tunnel mode gre multipoint
    tunnel key 100000
    tunnel bandwidth transmit 100000
    tunnel bandwidth receive 100000
    interface FastEthernet0/0 (WAN)
    ip address 216.x.x.x 255.255.255.192
    ip pim sparse-mode
    load-interval 30
    duplex auto
    speed auto
    interface FastEthernet0/1 (LAN)
    ip address 128.112.64.5 255.255.248.0
    ip pim sparse-mode
    load-interval 30
    duplex auto
    speed auto
    router eigrp 1
    network 128.112.0.0
    network 192.168.11.0
    auto-summary
    ip forward-protocol nd
    ip route 0.0.0.0 0.0.0.0 216.x.x.x
    ip http server
    ip http authentication local
    ip http secure-server
    ip pim rp-address 128.112.64.5 10
    access-list 10 permit 239.10.0.0 0.0.255.255
    snmp-server community public RO
    Spoke:
    Current configuration : 1857 bytes
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    hostname Spoke
    boot-start-marker
    boot-end-marker
    logging message-counter syslog
    enable password
    no aaa new-model
    clock timezone central -6
    dot11 syslog
    ip source-route
    ip cef
    no ip domain lookup
    ip multicast-routing
    no ipv6 cef
    multilink bundle-name authenticated
    voice-card 0
    archive
    log config
      hidekeys
    interface Tunnel1
    bandwidth 100000
    ip address 192.168.11.2 255.255.255.0
    no ip redirects
    ip mtu 1400
    ip pim sparse-mode
    ip nhrp map 192.168.11.1 216.x.x.x
    ip nhrp map multicast 216.x.x.x
    ip nhrp network-id 1
    ip nhrp holdtime 450
    ip nhrp nhs 192.168.11.1
    no ip route-cache cef
    ip tcp adjust-mss 1360
    no ip split-horizon eigrp 1
    delay 1000
    tunnel source FastEthernet0/0
    tunnel destination 216.x.x.x
    tunnel key 100000
    tunnel bandwidth transmit 100000
    tunnel bandwidth receive 100000
    interface FastEthernet0/0 (WAN)
    ip address 65.x.x.x 255.255.255.192
    ip pim sparse-mode
    load-interval 30
    duplex auto
    speed auto
    interface FastEthernet0/1  (LAN)
    ip address 128.124.64.1 255.255.248.0
    ip pim sparse-mode
    ip igmp join-group 239.10.10.10
    load-interval 30
    duplex auto
    speed auto
    router eigrp 1
    network 128.124.0.0
    network 192.168.11.0
    auto-summary
    ip forward-protocol nd
    ip route 0.0.0.0 0.0.0.0 65.x.x.x
    no ip http server
    no ip http secure-server
    ip pim rp-address 128.112.64.5 10
    access-list 10 permit 239.10.0.0 0.0.255.255
    snmp-server community public RO

    Joe,
    You ask the right question.
    CPU ultization = CPU consumed by processes + IO operations (in a huge simplification - CEF) 
    Typically when a packet is processed by router we expect it to be be processed by CEF, i.e. very fast.
    Packet is not processed by CEF:
    - when there is something missing to route the packet properly (think missing ARP/CAM entry) i.e. additional lookup needs to be done.
    - a feature requests that a packet is for processing/mangling
    - Packet is destined to the router
    (And several other, but those are the major ones).
    When a packet is recived, but cannot be processed by CEF, we "punt the packet to CPU" this in turn will cause the CPU for processes to go up.
    Now on the spoke this seems to be the problem:
    Spoke#show ip cef switching stati       Reason                          Drop       Punt  Punt2HostRP LES Packet destined for us             0       1723          0RP LES Encapsulation resource             0    1068275          0
    There were also some failures on one of the buffer outputs you've attached.
    Typically at this stage I would suggest:
    1) "Upgrade" the device to 15.0(1)M6 or 12.4(15)T (latest image in this branch) and check if the problem persists there.
    2) If it does, swing it by TAC. I don't see any obvious mistakes, but I'm just a guy in a chair same as you ;-)
    Marcin

  • Design question, UCS and Nexus 5k - FCP

    Hi,
    I need some advice from (Mainly a Nexus person); I have drawn and attached the proposed solution (below).
    I am designing a solution with 3 UCS chassis, Nexus 5K and 2X NetApp 3240 (T1 and T2). FC will be used to access disk on the SAN. Also, Non UCS compute will need access to the T2 SAN only. (UCS will access T1 and T2). It is a requirement for this solution that non UCS devices do not connect to the same Nexus switches that the UCS chassis use.
    UCS Compute:
    the 3 X chassis will connect to 2 X 6296 FIs which will cross connect to the a 2 X Nexus 5K through a FC port channel, the Nexus 5Ks will be configured in NPIV mode to provide access to the SAN. FC from each Nexus 5K to the NetApp controllers will be provided through a total of 4 X FC Port Channels (2 FC member ports per PC) from each nexus 5K one going to controller A and the other to controller B.
    Non UCS compute:
    These will connect directly through their HBAs to their own Nexus 5Ks and then to the T2 SAN, these will be zoned to never have access to the T1 SAN.
    Questions:
    1-      As the UCS compute will need to have access to the T1, what is the best way to connect the Nexus 5Ks on the LHS in the image below to the Nexus on the RHS (This should be FC connection).
    2-      Can fiber channel be configured in a vPC domain as Ethernet? Is this a better way for this solution?
    3-      Is FC better than FCoE for this solution? I hear FCoE is still not highly recommended.
    4-      Each NetApp controller is only capable of pushing 20GBps max, this is why each port channel connecting to each controller is only 2 members. However, I’m connecting 4 port channel members from each Fabric Interconnect (6296) to each Nexus switch. Is this a waste? Remember that connectivity form each FI is also required to the T2 SAN.

    Max,
    What you are implementing is traditional FlexPod design with slight variations.
    I recommend to look at FlexPod design zone for some additional material if you have not done so yet.
    http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns743/ns1050/landing_flexpod.html
    To answer your questions:
    1) FC and FCoE do not support vPC. If UCS needs to have access to T1, then there is no need to have ISL between sites. If UCS needs to have access to T1 and T2, then best option would be to set up VSAN trunking on N5K and UCS and configure vHBAs accordingly.
    2) Both should work just fine. If you go with FCoE, then UCS would need to be on the latest version for multi-hop FCoE support.
    3) If you only worried about storage throughput then yes, you will never utilize 40Gb PO if your source will be 20Gb PO. What are your projected peak and average loads on this network?

Maybe you are looking for