Fabric of interconnection to Bay iSCSI connection

I need to connect my fabric for interconnection to a new array of iSCSI.  There are a number of blades UCS that need to connect to iSCSI LUNS. The FI is currently connected to the rest of the network through switches to Nexus 7000 K.   Should I I plugged directly from the FI to the iSCSI array or go through the 7000 K and then to the table?

Hi, this is more a matter of design, you need to think about what will need access to the storage ISCCI matrix. For example, if a single UCS blaes will have access to this storage group, you can consider plug directly such as iscsi traffic must pass your N7Ks if the two fabrics are active. If you want another type of server such as HP or IBM to access storage, you should consider to connect the storage array to the N7Ks if your tissues are configured in end-host mode. Again, this will depend on your current implementation

Tags: Cisco DataCenter

Similar Questions

  • Fabric of interconnection in the care of the CF NPIV Switch mode? If anyone can confirm?

    Hello

    I'm working on a scenario where a client will make Direct Attach Storage for a pair of UCS fabric of interconnections. It will also need to connect a device of backup based on the CF to the FI. So let's run the s FI mode Switch CF.

    There apparently is a virtual machine on the blades which must have virtual HBA running in order to access their specific LUN.

    The question is whether the fabric interconnect (version 2.1(3b)) will support NPIV when running in the FC switch mode. Or the GUI or CLI Configuration guide mentions this, and I have not any FI to connect to check.

    Can anyone confirm this, either by pointing to a URL where it can be clarified or by connecting a FI Switch FC mode and by:

    connect nxos

    have SH

    or see the race |  feature Inc.

    and check if the npiv feature is enabled or not?

    Thanks a lot for your help

    Gustavo

    NPIV is by default active! See screenshot below

    Tanti saluti

    Walter.

  • EqualLogic iSCSI connection limit exceeded - implications?

    We have an EqualLogic SAN iSCSI which exceeded the limits of iSCSI connections. The limit is 1024, but we in 1612. The thing is that nothing seems to be affected. We can still add LUN/servers etc. We are likely to hit the problems? A kind of performance problem? There only seems to be a lot of documentation to anywhere! We are firmware 5.2.2.

    I don't know what we can do to reduce the number of connections, I want to know, is what happens if we don't? Because I can say nothing serious happened. We ignore it? Panic?

    Hello

    Joe is correct, it is very important that you respect the limits of the support of the table.  For you convenience, I suggest you upgrade to EQL FW 6.0.4 and HIT or MEM products for later upgrade.  Firmware 6.x and products current EQL MPIO now work together to better manage connections.  Especially when you are above the limit.  This coordination allows to automatically reduce the number of connections.

    I wonder if you use VMware ESX?   We see quiite often with ESX.  There are a number of strategies to reduce the number of without loss of performance.

    Feel free to open a folder from supported with Dell.   We can examine your environment and make specific recommendations to correct this problem.

    It is very important that you take into account of this.

    Kind regards

  • No link between IOM port 2/2/3 and fabric B interconnection

    Hello

    I am removing an uplink of the IOM to the fabric of interconnection in accordance with its not.  I tried to reset the module e/s and re - emphasize the chassis with no luck, it is still displayed in the GUI with the error message as in the subject.  We are running 2.0(1s).  The kit is not yet in production.

    Thanks for any help

    Hi barry,.

    The only way for you to clean up which will be de-Commission of the chassis in question and add it back again.

    Thank you!

    . / Afonso

  • FAS3220 and FAS2240 directly set on fabric of interconnection 6296UP

    Hello everyone

    I have the following architecture

    1 cisco Catalyst 6509-E

    1 cisco Catalyst 3560-x

    2 fabric of interconnection 6296UP

    1 FAS 3220 (primary storage)

    1 FAS2240 (backup of the vault)

    1 chassis cisco UCS 5108

    5 servers blades Cisco UCS B200M3

    Firmware version: 2.2 (3 c)

    Interconnection of fabric are set directly on the fabric of interconnection 6296up and ports are configured as storage FC ports

    My question is this:

    Can I zoning fabric interconnect with FAS3220 and FAS2240?

    May I present LUNS of FAS2240 and FAS3220 at the same time on the same startup strategy, same strategy of startup san and the same organization?

    Thanks for your help

    You can make the zoning on UCS:

    http://www.Cisco.com/c/en/us/support/docs/servers-unified-computing/UCS-...

    If it's really a good practice...

    CF sees WWNNs and WWPN.

    What would be the purpose of pointing both starting the 3220 s 2 and the 2240?

  • Can I use VDS with LACP to reduce on group SAN iSCSI connections?

    I'm trying to reduce the number of iSCSI connections to my EqualLogic storage group. I currently use a standard vSwitch with two ports vmk by server for SAN. Can I use a single vmk with VDS/LACP to reduce my by half by server iSCSI connections and still maintains band bandwidth/redundancy?

    I'm quite confident, it will work, but hoped for validation. Please correct me if I'm totally turned off, or if it would be not supported.

    My volumes cover several physical devices (20 paths for 7 volumes by iSCSI adapter). Can I assume that with load balancing on an OFFSET of the source and destination hash value, I would get at least some balancing between adapters?

    If you have several points of termination targets L2 - 4, Yes. For example an IP address, MAC address, unique ports or. Paths, volumes and devices are not relevant to the LACP.

    If I don't choose a LAG, I can't visualize how it would reduce my iSCSI for my storage pool connections. I'm setting targets on my Broadcom cards, the vmk connects through these cards. Is the logic that is smart enough to only connect the active paths on an adapter or another in an OFFSET? I do know that I have make sense more that I might have to play with a SHIFT on a host isolated for a bit and see exactly how it will behave.

    The adapters are more exposed. The LAG is a logical interface. Traffic can be sent or received through any physical adapter in the GAL.

    Note: I would not use an OFFSET for iSCSI on a vSphere host traffic: seriously, Stop Using Port channels for vSphere storage traffic. Wahl network

  • ISCSI connection failure causing ESXi 5.1 VMs at the stop

    Hi all

    At the hope that someone may have seen the problem that we encountered during the last 2 weeks.

    Our virtual machines are performing unexpected stops. Our Exchange Server rebooted twice today

    The closing time is information that we see our Equallogic logs:

    INFO APCEQLM1 09:35:19 7.2.15 26/07/2013. 7.2.24 | 7.2.29 session iSCSI to target '192.168.43.12:3260, iqn.2001-05.com.equallogic:4-52aed6-c7ca4349e-87b00217be35059e-lon-prod-vm-1' initiator ' 192.168.43.31:58797, iqn.1998 - 01.com.vmware:apcesxhost1 - 24c73c18 "was closed. | iSCSI initiator login failure. | No response on the connection for 6 seconds.

    We have 1 Equallogic PS4100X, run the latest firmware EQL 6.0.5. We have 2 switches Powerconnect 6224 stacked. Our table and switches are configured by DELL support.

    We followed the recommendations of DELL on vSphere storage ISCSI connection. I see that our vSwitches are correctly configured.

    Someone has any ideas why we find that this behavior? I have connected this with the support of DELL, but thought I would ask on the forums in case someone knows that it emits.

    Thanks in advance!

    Lee

    Hi Julie,.

    My apologies, I thought that I had updated this discussion with the fix. It was related to a problem of driver on one of our hosts. I logged a call with VMWare and they got the answer very quickly. The problem was our host NETWORK interface card tg3 driver. I've followed this article to resolve the problem:

    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2035701

    I hope it is of some use to you!

    Thank you

    Lee

  • iSCSI connection

    Can someone give me an idea about the best way to configure my connection iSCSI in vMware?

    I'm under ESXi 4.1. I have three ESX host. On each host, I have two other network connections to the outside for each host. It is advisable to configure a vmkernal port, assign an IP address and use a one as the main network connection and the other as secondary or load balancing, both.

    Or and im not having a chance at this moment doing this... install a second port of vmkernal using a separate virtual switch, assign it a second ip address and having only one main connection on for each virtual switch. Give me two connections to my iSCSI SAN for each host.

    Thank you

    Wayne

    Hi Wayne,

    The best way is to have a unique vSwitch with two other cards attached physical. Then, create two VMkernel ports for iSCSI connections. Take a look at the next section for a full description of this type of configuration.

    It will be useful.

    Concerning

    Franck

  • Connection no UCS server to the fabric of interconnection 6248

    We are migrating our VMS of Dell PowerEdge servers to Cisco UCS environment 620\710. The question has been ask if we can connect our Dell servers directly to the IF SFP ports + and/or the connection of TP will 10 GB. Is this possible? How does the FIs treat non - UCS servers?

    This is not supported! I guess you want to do vmotion and transfer your Dell to UCS Server VM. Just configure the appropriate network connectivity (vlan UCS to Northbound Dell server) and it should work.

  • Fabric of interconnections can be re - RPI?

    We decided to use another IP range and I was wondering if I need to do some sort of clear the config or do I go through the installation of transitional upward through the console and change IP addresses?  The original range of subnet 'management' that we were going to use is not available, so I never had with the VIP address.

    Certainlu you can change the IP without having to clear the system.  Remember that it is only a change of plan, not data management, you can do this without disrupting the traffic from your server.

    Here's how I suggest you do:

    1. connect to the Console of each FI with the admin account.

    2. find what FI's secondary by issuing:

    view the status of the cluster

    3. the issue of session from console secondary FI:

    fabric-interconnection of scope [a / b].

    4. set the new IP settings with:

    the value of subnet mask ip out-of-band [address-IP-New] [New-Netmak] gw [New-Bridge]

    buffer validation

    * Note: If the subnet mask and the gateway are not change, you can omit them in the above command.

    * At this point, you should be able to ping the new IP addresses assuming management upstream interface are configured correctly and assigned to the VLAN correct

    5. Repeat for the main fabric connect to the console session.

    6. set the new VIP by launching:

    staff system

    game virtual-ip x.x.x.x

    buffer validation

    7. test the connectivity with each IP & VIP address.

    8. If you have any questions, you should be able to use the console session to correct all errors with no disruption to service other than access UCSM.

    Kind regards

    Robert

  • Fabric of interconnection Port Mode

    During our first installation of our UCS deployment only two of our rising four that connect the fabric to the frame were connected. This was done by a contractor. Now, we have two other cables and get them connected but mode on ports are set to "Trunk" and "tissue" as not the rest. The role has been defined in the interface of the UCS, but fashion was not so easy. How can I change this way of fabric?

    Hi Dennis,

    But there is NO need to be set to 4. As mentioned, the chassis discovery policy determines what is the minimum number of links for a frame be discovered/usable. See you to have it set to 2, it is very good and you can keep it this way.

    The fact that you have only 3 cables from IOM to the interconnection of fabric, this is not a valid configuration, because only 1, 2 or 4 links are taken care of. You must increase the number of cable to 4 and then re - emphasize the chassis to activate the additional links.

    Let me know.

    Thank you

    Michael

  • Adding redundant fabric to interconnect with the existing FI

    For UCS, we have a fabric interconnect version 2.1, customer bought a FI more to add to the cluster configuration.

    The FI is delivered with the latest firmware, please let me know can downgrade us the new FI and forms a cluster or the upgrade of FI existing to the latest firmware.

    Please review best practices for cluster FI configuration.

    First change the old standalone cluster mode FI! Not sure if it is without service interruption. In any case, you must plan a maintenance window!

    Then, if your old FI minimum 2.1.3, you can add the other FI who, in the boot menu, see the FI counterpart and ask if it should cooperatively as a cluster member, synchronization first firmware (Assembly FI will have same firmware release like the old FI).

    Hope that's clear?

  • How to check the use of the channels of port on fabric of interconnection?

    Hi all

    Is there a mechanism to view and export the use of ports or port channel fabric Interconnect 6248.

    I need to export for the last 15 days. Is there a command or options in the GUI I can export it

    Greetings.

    Native statistics are unlikely to give you a historical trend for the period you're looking for.  See the monitoring/stats for the UCSM system section for more information on the rules of collection of statistics.  The default value for the period appears to be 2 hrs to watch statistics table.

    You can look something like manage performance UCSr, which can do a trend and will retain much historical perspective of production like detailed.

    For a short term in UCSM view, click the LAN tab, then a given port channel, in the right pane statistics, chart and "configure chart" to add in the box counters as "total number of bytes.

    Thank you

    Kirk...

  • groups and iSCSI connections to ports

    Hello

    We have a 5.1 esx server connected to an iSCSI-based storage device.

    the server is connected using two of the vmkernal iscsi ports.  each network card has a different ip address on the private iscsi vlan.  the configuration is according to the practices of bast vm using only one network by vmkernal port card.

    We have a migration of storage to another storage but I still have to intall it.  I would like to know if its possible to create two groups of ports additional vmkernal using the same NIC already connected to the iscsi storage.  new port groups on one vlan separate and different netwok so go looking, it seems right that I share two NICs for two networks different iscsi.

    as mentioned above, that I have not installed the hardware yet, but to test it a bit it looks like I can add groups of ports by using the network card and I was able to bind to the vmhbaxx with the adapter of storage with the path of staus as not used.  so I hope that when I connect the new buffer I would be if all goes well able to connect once I place a discovery?

    any comments welcome.

    Thank you

    I don't see why you shouldn't be able to do what you describe. It's a little unusual, but it should work to create adapters to VMK several on the same vSwitch and make the same active/unused configuration you already made, but put other id VLAN and IP address on the new adapters. Of course the two logical VMK adapters share the same network link, but you are fully aware of.

    As long as it is not indicated in some manual or KB article as a solution not supported, you should be fine.

  • pswitch iSCSI connection

    Hello

    When I create a vmkernel port-iscsi in one vlan or in another subnet what should I do in a physical switch to connect with the storage array?

    for example, the pswitch is 192.x.x.x network and my iscsi is 10.0.0.0.

    they are in the other subnet or can I also a vlan different.

    should what configuration I do the two conditions in the switch?

    With VLAN things are a little different as you will need to configure all ports of pSwitch with the same functions in the same VLAN.

    So in your case, you must Access your pSwitch management console and adding in the same VLAN, all ports involved in the iSCSI traffic i.e. all pSwitch ports that are connected to the iSCSI storage network cards and all pSwitch ports that are connected to ESXi natachasery used for iSCSI.

    Same story for vMotion.

    In any case VLAN and different IP subnets are not related since you can use the different IP classes in the same VLAN. VLAN tagging is, like switching, performed at level 2, so when the switch before images destination VLAN it doesen't review IP addresses but to only MAC address of destination and corresponding VLAN ID.

    Kind regards

    Paolo

Maybe you are looking for