iSCSI vNIC etc.

Similar Questions

• iSCSI vNIC a requirement?

  If I do not intend to start from an array of iSCSI, what I have to go an extra step and configure iSCSI vNIC for use in vSphere or I'm sure with only created vNic standard with the appropriate settings for Jumbo frames, etc...?

  I think before UCS 2.0 that was sufficient, but talk with TAC, it sounds like the vNIC iSCSI is now required with vSphere...

  Is there an advantage to create iSCSI vNIC (beyond starting from an iSCSI array).

  Thanks in advance,

  Lewis Benton

  vNIC iSCSI is only necessary if you do iSCSI initialization.

  If you do not have the iSCSI initialization you need not of a vNIC iSCSI in your service profile.

  If you want frames set to the vNIC and be sure to put it also on the QOS policy

  Louis

• ISCSI Boot B200 M2 need, but get 'not enough available vNIC.

  Hello

  I'm trying to implement initialization iSCSI ESXi on a B200 M2 w / M71KR-Q card above.

  I add vNIC A and B (each linked to a fabric respectively), but trying to implement a vNIC iSCSI - I get the error «not enough vNIC» available

  Looking around, it seems that M71KR-Q only can support 2 vNIC (which I also confirmed by trying to add a third, same error message as above).

  I just thought that since the overlay of iSCSI vNIC real - it works.

  However, even when adding just 1 vNIC and trying to superimpose a vNIC top iSCSI - I get the "there not enough resources overall, not enough vNIC available" error message.

  Does anyone know if it is even possible to initializing iSCSI on B200-M2 w / M71KR-Q on?

  Thanks in advance!

  Petar

  Please refer to this document in the section documents iSCSI boot https://supportforums.cisco.com/docs/DOC-18756 it is very detailed, I tell myself.

  initializing iSCSI is only supported on CiscoVIC and Broadcom mezz cards. It is not supported on the M71KR-Q Qlogic Gen - 1 mezz.

  Dave

• iSCSI Boot target IP Question

  Hi all

  Setting up iSCSI starts for the first time and had a question.

  Installation: Blades UCS about a pair of N5K (vPC) with a double NetApp controller connected.  There are 4 UCS vNIC - two for only iSCSI (as the VLAN native) and two for everything else.

  The blades odd dΘmarrez since LUN on NetApp controller and the blades even dΘmarrez since LUN on NetApp B controller.

  So my question.  When I make for an odd Blade (for example) iSCSI targets, do I have both A and B "NIC" s point on A controller's IP?  Or NIC - A point on A controller and IP point of NIC - B to B controller IP?  I was not sure that, in this example, the controller would hold unit number logic that this odd blade is starting from.

  Thank you!

  Hi Ian

  You can add up to two iSCSI vNIC startup strategy. A vNIC acts as the source of primary iSCSI boot, and the other acts as the source of secondary iSCSI boot.

  "point of NIC - A controller - A IP and NIC B points to the IP Address of the controller of B ' YES.

  You would create another strategy of starting for blades, with the primary order / trade school.

• The network connectivity of RedHat 6.4 Installer

  Please excuse my lack of knowledge in this area as this is all new to us (UCS, SAN and Linux).

  We have a UCS chassis with blade series B200 and start ISCSI disks on a HP 43000 storage nodes.

  With the help of the CISCO rep, we set up the profiles Server UCSM and parms ISCSI boot, etc. and installed Redhat 6.4 - Basic Configuration.  I'm now trying to configure the network access server and this is, I'm stuck and I wonder if a step is missed in our configuration.

  On the side of UCSM, it conversely fabric is assigned IPs xxx.xxx.34.71 and 34,72 with a VIP address to 34,70.  Both A & B fabrics are connected to our network switches and are also directly connected to our isolated SAN switches.

  We have created a pool of MAC and a POOL of IP (xxx.xxx.34.73 80) and created two VLAN VLAN20 and 21.

  In service profiles, I see:

  -two vNIC ISCSI, one for each switch fabric

  VLAN21 (Native) being for fabric sw A & B routes (xx.xx.0.21 & xx.xx.0.41) to ISCSI storage to start nodes. No adapter policy is set.

  -4 vNIC FabA and B - Dev, FabA and B-ISCSI. There is no configuration policy dynamics vNIC connection or LAN connectivity

  The FabX-Dev are assigned to the VLAN20 and ISCSI-FabX are assigned to VLAN21

  I see the blades in the tab LAN USCM, receive an IP address from the IP pool (for example. xx.xx.34.73)

  Seen this configuration, I now install the OS and once completed, I see eth0, ane ibft is already configured

  However when I run system-config-network, I see eth0, 2 and 3 are labelled Cicso VIC Ethernet NIC and eth1 is just Ethernet.

  Eth2 and 3 are configured for dhcp while eth0 is not.

  At this point, I can reboot and launch a KVM of USCM session. I can ping the IP assigned to the blade, but permission denied trying to ssh in as root.

  I tried to configure eth1 at xxx.xxx.43.60, but get a device is not present when you do an ipup eth1. I also tried to configure eth3 with the same IP address, but it does not work too.

  What Miss me?

  Norm

  Hello

  If you have decided to dedicate a NIC for iSCSI traffic (say KEEN 767), you should be allowing to the VLAN necessary under the Service profile > vNIC > VLAN article.

  Similarly, you must allow VLAN necessary in other vNIC.

  The OS point of view, you configure the IP address and associate it to the respective network interfaces.

  Padma

• No network traffic VM being withdrawn and any data store Info

  I am running a trial of Foglight Enterprise visualization and upward and running things and an agent installed to my VMWare vCenter server infrustructure.  He shoots a lot of info, but none of the basic data store info is pulled (not the stuff that requires the Foglight for integration of storage) and none of the information network is taken for the individual virtual machine.  Guests and parents have netowrk showing traffic, but nothing on the side of the virtual machine.  The environment is configured with dvswitches for data, iscsi, vmotion, etc..  Any idea of what might happen, or I can look at?

  I see some errors in the agent log if I pull it down on data warehouses... Here's a sample:

  ERROR [Quartz [0] - 6] com.quest.agent.esx.task.HardwareTask - DatastoreInfo is missing for Datastore:datastore - 162
  2015-03-17 13:57:16.165 ECHO ERROR [Quartz [0] - 6] com.quest.agent.esx.task.HardwareTask - DatastoreInfo is missing for Datastore:datastore - 131
  2015-03-17 13:57:16.165 ECHO ERROR [Quartz [0] - 6] com.quest.agent.esx.task.HardwareTask - DatastoreInfo is missing for Datastore:datastore - 10985

  But apart from that, I don't see much... I do not see what seems to be warnings of Java, like this:

  2015-03-17 13:57:17.291 ECHO [Quartz [0] - 6] WARN com.quest.agent.esx.task.ESXAgentTask - inventory and relationship - FGLAM submission error: null
  java.lang.NullPointerException
  at com.quest.vmware.agent.history.samples.VMWHostVirtualSwitch__IMPL.__addPropertiesToNodeTree(VMWHostVirtualSwitch__IMPL.java:2418)
  at com.quest.vmware.agent.history.samples.VMWHostVirtualSwitch__IMPL.__addToNodeTree(VMWHostVirtualSwitch__IMPL.java:2348)
  at com.quest.vmware.agent.history.samples.VMWESXServerNetwork__IMPL.__addPropertiesToNodeTree(VMWESXServerNetwork__IMPL.java:1339)
  at com.quest.vmware.agent.history.samples.VMWESXServerNetwork__IMPL.__addToNodeTree(VMWESXServerNetwork__IMPL.java:1078)
  at com.quest.vmware.agent.history.samples.VMWESXServer__IMPL.__addPropertiesToNodeTree(VMWESXServer__IMPL.java:5015)
  at com.quest.vmware.agent.history.samples.VMWESXServer__IMPL.__addToNodeTree(VMWESXServer__IMPL.java:4213)
  at com.quest.vmware.agent.history.samples.VMWCluster__IMPL.__addPropertiesToNodeTree(VMWCluster__IMPL.java:10666)
  at com.quest.vmware.agent.history.samples.VMWCluster__IMPL.__addToNodeTree(VMWCluster__IMPL.java:10010)
  at com.quest.vmware.agent.history.samples.VMWClusterCollection__IMPL.__addPropertiesToNodeTree(VMWClusterCollection__IMPL.java:780)
  at com.quest.vmware.agent.history.samples.VMWClusterCollection__IMPL.__addToNodeTree(VMWClusterCollection__IMPL.java:702)
  at com.quest.vmware.agent.history.samples.VMWVirtualCenter__IMPL.__addPropertiesToNodeTree(VMWVirtualCenter__IMPL.java:9298)
  at com.quest.vmware.agent.history.samples.VMWVirtualCenter__IMPL.__addToNodeTree(VMWVirtualCenter__IMPL.java:8979)
  at com.quest.vmware.agent.history.samples.VMWModel__IMPL.__addPropertiesToNodeTree(VMWModel__IMPL.java:1304)
  at com.quest.vmware.agent.history.samples.VMWModel__IMPL.__addToNodeTree(VMWModel__IMPL.java:974)
  at com.quest.vmware.agent.history.samples.VMWModel__IMPL.buildSubmission(VMWModel__IMPL.java:919)
  at com.quest.vmware.agent.history.samples.VMWModel__IMPL.submit(VMWModel__IMPL.java:810)
  at com.quest.agent.esx.task.HardwareTask.submitData(HardwareTask.java:813)
  at com.quest.agent.esx.task.ESXAgentTask.submit(ESXAgentTask.java:208)
  at com.quest.agent.esx.task.ESXAgentTask.run(ESXAgentTask.java:201)
  at com.quest.agent.esx.ESXAgent.runTask(ESXAgent.java:518)
  at com.quest.agent.esx.ESXAgent.esxHardwareCollection(ESXAgent.java:718)
  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:606)
  at com.quest.glue.core.services.EquivalenceInvocationHandler.invoke(EquivalenceInvocationHandler.java:76)
  at com.quest.glue.core.agent.AgentInteractionHandler.invoke(AgentInteractionHandler.java:177)
  to com.sun.proxy. $Proxy65.esxHardwareCollection (unknown Source)
  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:606)
  at com.quest.glue.core.agent.scheduler.CollectorCallback.invokeCollector(CollectorCallback.java:246)
  at com.quest.glue.core.agent.scheduler.CollectorCallback.execute(CollectorCallback.java:146)
  to com.quest.glue.common.util.scheduler.quartz.QuartzScheduler$ ScheduledTaskSequentialJob.execute (QuartzScheduler.java:738)
  at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
  to java.util.concurrent.ThreadPoolExecutor$ Worker.run (ThreadPoolExecutor.java:615)
  at java.lang.Thread.run(Thread.java:745)

  Thanks in advance!

  -Jake

  Hey Jake,

  I don't know what could cause this problem, it's a bit you added the role of travel data store for the Foglight service account in vCenter. Could you please create a Service request with support?
  https://support.software.Dell.com/

  Could you also attach a support package for FglAM to the case? Please put the number of file here, or send it to me via private message.

  Thank you.

  Gaston.

• Generational UCS/VMWare

  Hello

  I'm looking for clarification on how the Palo VIC presents the vNIC, how say/control which card vNIC to which ports physical and how best to configure my environment for VMWare.

  Summary of material:

  Blades (full-width) B250 with 2 cards of Palo VIC

  5108 chassis with double FEX (double uplinks from each FEX)

  2 x 6120 controllers with 2 x 10 Gbit links rising each to a pair of Nexus s 5020

  Summary of the software:

  UCS 1.3.0 boot loader, the kernel/system 4.1 version (3) N2(1.2d)

  VMWare vSphere Enterprise Plus 4.1

  According to my interpretation, Cisco and VMWare recommend against bandwidth limiting the interfaces - but prefer to go with actions and ability to burst.

  Therefore, my desired construction is the following:

  for each of the 4 available in B250 blade 10gbit interfaces, I want to have 2 vNIC (1 for VM distributed vSwitch [6Gbit minimum actions, 802. 1 q trunks], 1 for iSCSI [4 Gbit minimum actions, access port/no 802. 1 q trunk]). This means that my Service profile must define 8 vNIC altogether.

  Q1: How can I make sure that I get 1 'data' and 1 'iscsi' vNIC per physical port?

  Q2: how to set a policy to set the minimum bandwidth on each vNIC?

  Q3: How do I control/make sure the binding order correct so that I can script my configuration of vSphere?

  Generation of VMWare will be vswitch distributed containing all the 'data' vNIC, allowing control of network IO with actions defined to manage the various allowances for groups of data ports, console and VMotion. The vNIC iSCSI will each receive a VMKernel port dedicated.

  Thank you very much in advance for any help.

  Our installation program is not the same, but the principles can be applied as we also CIV.  To make sure that we had the installation of ports properly, I put into service six vNIC in UCSM to each host.  I put in service the first vNIC of fabric and the second vNIC fabric B - do not check the box "Fabric Failover"...  Repeat for other network cards for four.  This will give you 4 vNIC by fabric.  Note MAC addresses and which tissue they are attached.

  Then, in case of VC and to configure your hosts, enter the network cards and line up the vmnic and MAC addresses so that you know how they trace.  When you configure your vSwitches, just make sure you add a vmnic from fabric and a fabric vmnic B.    Do this for the Service Console, vmkernel and VM switches.

  If you make this unique environment of VIC inas, it will ensure that your vswitches are attached to every tissue.  I guess you can do this same thing with two VICs, since each card may appear independently in UCSM.

  As for the bandwidth mgmt and others, check out http://bradhedlund.com/ its recent messages are on the networks of the UCS.

  Adam

• vSphere client 5.5 cloning vm

  New on vsphere practising on my 5.5 nested ESXi

  In host A, I clone a virtual machine to the same host and correct received validation. When I try to clone the host b, I get a data store is not available... I understand, the VM data store is to Host1.

  In a real environment, you copy the "VMFS files to another host" to be able to clone the virtual machine?

  just try to understand when and in what scenario clone you a machine...

  Thank you

  Hello

  In a real environment, you would probably use a form of storage shared which may see the two hosts. You can set this in a laboratory quite easily using something like OpenFiler, which is a storage operating system that can be run as a virtual machine and the present storage on the network.

  I use an openfiler in my lab viewed 100% using the workstation (nested ESXi hosts, vCenter, nested OpenFiler VM using NFS and iSCSI, AD, etc.)

  The reasons that you might want to clone a machine are varied. A simple example, I can think of would be if you want to take a copy of a Production machine and then fire up, like an isolated stand-alone server / network to solve problems that you may have on this subject.

  I am happy to answer any other questions you might have!

• Build test lab

  Hello

  I currently have a server VMware ESXi 5.1 home with an Intel Core i7 - 3770S (65 watts) CPU with two network adapters.  The server runs at 28 idle watts (2 SSDS) which is very effective (machine 24/7).  I also have access to iSCSi, NFS, etc..

  I intend to add a second host to make more tests and to learn before I break things at work.  I'm looking at two options.  To build another host exactly as the current computer, or go with two machines additional NUC for a smaller footprint.

  Are there limits as to have a NETWORK adapter on a host computer?  None of the other things I should be aware of?  I read online before you post :).

  Thank you

  TT

  If used only for a lab environment there is no problems with the use of a single NETWORK card - I think the challenges you will face is if ESXi 5 will have the drivers to support hardware in the NECK - I'd build a machine identical to what you already have - this way you will be able to test with all features of vSphere including vMotion and DRS.

• SRM hypervisor replication Requirments

  Hello

  We are currently looking to implement a SRM solution between or Production and DR sites.

  • Currently in our environment VMware 5.1 our ESXi clusters are connected to an IBM XIV Gen II through 8 GB Fiber Channel.
  • Our two sites are connected via an MPLS connection.
  • We have not all capable routing FC or FCIP SAN switches, and we are not able to buy a.

  As much as we Vcenters and storage available on both sites can us always replicate VMs via the MPLS connection via RS 5 hypervisor type replication?

  Can someone brief explain me what protocol or process exactly MRS uses to replicate virtual machines if it isn't level storage: IE FCIP, iSCSI, NFS, etc.. ?

  Hypervisor SRM replication essentially "VSphere replication is" without Automation, test, additional features etc.?

  Thank you!

  That's right-

• Need help to understand the network of vSphere environment

  Hello

  I need your help in understanding the network environment in vSphere. Please see the diagram and the text below:

  

  NIC #1 - Management Port (access from client vsphere, vCenter server)

  NIC #2 - Port of VMkernal (for iSCSI, vMotion, etc.)

  NIC #3 -?

  #4 – CARTE NETWORK INTERFACE?

  Q1 how allow external users to access services over the ESX host? (for example, IIS, FTP, Exchange, NFS)

  Q2, what will be the role of the other two network cards? Is it connected to the physical switch?

  * Ask you all to please help me by sharing your knowledge / experience on the network portion, you have made in your environment as NIC how, what to do with that. *

  I really need to understand the networking of concepts in vSphere, hope that your help!

  
  

  Best regards: Yash

  With an additional NIC with 2 port a general configuration might look like this:

  vSwitch0 - vmnic0, vmnic1 (connected to different physical switches)

  Network VMkernel management

  VMotion VMkernel network (own IP network, own VLAN)

  Better if they is configured as active / standby.

  vSwitch1 - vmnic2, vmnic3 (connected to different physical switches)

  Trade VM

  vSwitch2 - vmnic4, vmnic5 (connected to different physical switches)

  VMkernel iSCSI (own IP network, own VLAN)

  Ideal if it is added to the component Multipath iSCSI, which is quite easy to vSphere 5.

• Lost AutoDeploy configuration

  Hello everyone.

  I have a Server Blade vSphere with AutoDeploy 5 for about a month now. I have it configured (deposit, package HA, deployrule based on the MAC address, the host, answer file profile) and it worked very well.

  I rebooted it many times, he come always correctly, the virtual machines are running well with vMotion, software iSCSI, VDS, etc.. Standard features.

  Now I want to configure my other blades using AutoDeploy (new deployrule, same profile host, new answer file) and everything goes wrong.

  When I want to list everything related to AutoDeploy, it returns no value. Get-ESXImageProfile, Get-ESXSoftwareChannel, Get-DeployRule, Get-DeployRuleSet, etc. cmdlets return any value (and no error).

  Now, I dare not to restart this ongoing performance Blade Server, because I fear it will come back to the top.

  What is going on? It is just a display bug, or is it worse? How can I solve this problem?

  Ideas and suggestions welcome.

  FT

  Check that the config looks good on the deployment server.  It's good doc for general troubleshooting

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=2000988

  Also check the rules etc for questions.  It's good info on these orders.

  http://blogs.VMware.com/vSphere/2012/01/Troubleshooting-Auto-deploy-rules.html

  AutoDeploy GUI is a nice addition to use this product in your environment.  I had a more stable global deployment, using this tool than without it.

  http://labs.VMware.com/flings/autodeploygui

  Worst case it is not too painful if you come to remove the AutoDeploy (clean any old directories as needed) and then reinstall.  You have to re-create your deployment rules, but it is not too big of a deal as long as you don't have to restart servers while you are in the process of reconstruction.

• Change the name of a data store?

  Hello

  Is it possible to change the display name of a data store NFS I have 8 nodes in a cluster connected to?  This is for aesthetic reasons only - consistency of the naming convention.  Just curious, if I renamed the store of data for data store in vSphere VCenter, did change the display name for each host?  Or I have to change the display name to each host using the "hosts and Clusters".  Just curious to know if I can do that, while virtual machines are run with no negative effect... or should I stop literally all of the virtual machines to do this.

  Thanks in advance.

  Hello

  You can change the name of data warehouses (NFS, iSCSI, FC etc.) at any time and without any negative effects.

  Just right click, rename it to your heart's content!

  See you soon,.

• Network lost after restart of host settings

  I have vcenter that works as a virtual machine on host #1 (vsphere 4.1 u1)

  I used vcenter to configure networking on the host #1 and was able to connect to the San and run a virtual machine of the SAN.

  About 10-15 minutes later, I stop the virtual machine of vcenter, put the host in maintenance mode and rebooted the host.

  After startup, the host no longer has network (vswitches, iscsi, config, etc.) settings and as such, cannot see SAN data warehouses.

  I do not understand why this has happened.

  I had already installed 4.1 on my other 2 hosts literally 10 minutes before it happened, and now I have an unpleasant feeling in the pit of my stomach.

  Using ESX or ESXi?

  Because ESXi works in the virtual disk, and it updated the config files not in real time.

  See: http://communities.vmware.com/thread/265019

  André

• difference between a command ping and vmkping in hosts esxi 4.1

  Hello

  I can't enter the vmkping command and the command ping when it is used in virtualization, esxi hosts, but correct me if I am wrong in my assumption

  1. the vmkernel which is the firmware if you like vsphere suite that manages all communications between the physical host computer and comments, is the hypervisor if you like, correct?

  2. the vmkernel has its own virtual ip stack that manages all vmotion, iscsi and fiber storage correct traffic?

  3 Let's say I have two esxi hosts (esx1 and 2) using two NICs to uplink where vmnic0 on both esxi hosts are virtual machine port groups and the vmnic 1 is used for the port of vmkernel on esi 1 and 2.

  the standard command ping ping ip addresses on both hosts of esxi vmkernel, but she would not use the internal ip stack of vmkernels to check the communication between the two ports uplink vmkernel, instead it uses the co-location host tcp/ip stack to resolve the IP address connectivity and would only check each link port communication.

  by using the vmkping command, it connects esx1 host using putty for example and issues a command vmkping to ESX2 to host esx1, which uses its own tcp/ip stack of vmkernel to achieve a connection from esx2, so indeed the ping moves port vmkernel esx1 directly on the port of uplink of the esx2 and back again check connection of storage correct

  apologies if I didn't explain better, but if you need additional information on my question let me know.

  Thak you.

  Hello

  Yes you are right. The VMkernel is hypervisor - the thing that makes the magic of the work of virtualization.

  The VMkernel has an IP stack to do the things that you have mentioned: vMotion, iSCSI, NFS, etc. which do not exist as on the VMkernel interfaces. Often, but not always, these IP addresses are not accessible outside the VMkernel. For example, if you run an isolated network dedicated to these services. Essentially by issuing a vmkping you issue a ping from the VMkernel interface for another interface, VMkernel not necessarily another interface.

  Compare this with the ping who seems just the Service Console interface.

  If we look at a simple ESX build - two hosts (ESXA and ESXB) with two NICs (vmnic0 and vmnic1). On the ESXA and B, we have the Service Console running vmnic0 with the natachasery connected to a switch. We perform a cross on the cable between the hosts connected to vmnic1 and have configured it for vMotion. In this scenario if you issue a ping from host you a submission in response to the Service Console of IP and other devices on the same subnet connected to the switch. However if you ping the address of vMotion you won't because it is on another inaccessible network - in steps vmkping.

  Trust that this assistance.