Nexus 1000v repo is not available

Hi everyone.
Cisco Yum repo for nexus 1000v is not available at the moment. I am wondering, is it Ok and Cisco finished it experiment with free Nexus1k or I need to contact someon (who?) to ask him to fix this problem.
PS Link to the repo: https://cnsg-yum-server.cisco.com/yumrepo

Let's set the record straight here - to avoid confusion.
1. VEMs will continue to forward traffic in the event one or both VSM are unavailable - this requires the VEM to remain online and not reboot while both VSMs are offline. VSM communication is only required for config changes (and LACP negociation prior to 1.4)
2.  If there is no VSM reachable, and a VEM is reboot, only then will the System VLANs go into a forwarding state.  All other non-system VLANs will remain down. This is to faciliate the Chicken & Egg theory of a VEM being able to initially communicate with a VSM to obtain its programming.
The ONLY VLANs & vEth Profiles that should be set as system vlans are:
1000v-Control
1000v-Packet
Service Console/VMkernel for Mgmt
IP Storage (iSCSI or NFS)
Everything else should not be defined as a system VLAN including VMotion - which is a common Mistake.
**Remember that for a vEth port profile to behave like a system profile, it must be define on BOTH the vEth and Eth port profiles.  Two factor check.  This allows port profiles that maybe are not critical, yet share the same VLAN ID to behave differently.
There are a total of 16 profiles that can include system VLANs.  If you exceed this, you can potentially run into issues with the Opaque data pushed from vCenter is truncated causing programming errors on your VEMs.  Adhering to the limitations above should never lead to this situation.
Regards,
Robert

Similar Messages

  • VN-Link Hardware require Nexus 1000v yes or not?

    I have a problem about VN-Link Hardware. When i create port profile on UCS Manager and Create Port Profile Client then vCenter will create Port Group too. But when i apply network in Virtual Machine by select Port Group in vCenter i can't see Virtual Maching Guest in VM tab on UCS Manager.
    Finally question VN-Link Hardware require Nexus 1000v install on ESX yes or not? in UCS Manager GUI document say need require DVS Switch.

    Thank you for reply. I have successfully turn on VN-Link hardware by follow this video --> http://tinyurl.com/23p896k
    and i have install Nexus 1000v VEM in ESX for turn on VN-Link hardware.
    I need test performance of CNA Card (palo) and report to my CEO.
    - How to test it?
    - What is tool for test?
    PS.Sorry for English language

  • Nexus 1000v Layer3 Control not coming up

    For info, I run 4.2(1)SV1(4) as a VM and not the appliance.
    I tried this morning to migrate a small environment to the Nexus L3 control instead of L2 for a certain requirement. We have two ESX in the with the Nexus 1000v running sucessfully for months on L2.
    I tried to follow the procedure that is in this document. I followed this script:
    Created a layer3 control0 interface with an IP in vlan951.
    So I had my VMWare guy move a VMKernel interface of each ESX host to this profile:
    port-profile type vethernet VLAN951
      vmware port-group VLAN951
      capability l3control
      switchport mode access
      switchport access vlan 951
      system vlan 951
      no shutdown
      state enabled
    Then modified the svs domain like such:
    svs-domain
    no control vlan
    no packet vlan
    svs mode 13 interface control0
    I made sure that I have layer-2 connectivity between the VSM host and the rest ESX hosts is OK, but I am not certain how you actually assign a layer 2 vlan to the control0 interface... Is it supposed to broadcast on all the VLANs? Or is it a correlation of the port-profile config and svs-domain that does that?
    In any case, my two VEM go down and do not come back up once I am in l3 mode. I had to revert back to L2.
    Any help would be appreciated.
    Regards,
    Simon T.

    Hi Simon,
    Since you are using ctrl0 as the layer 3 interface, you need to assign the IP address under the ctrl0 interface (interface ctrl0). This IP address should be able to communicate with the vmk interface's IP address.
    Regards,
    Shankar

  • Nexus 1000v vsm secondary not recognized

    I deployed the seondary vsm but when it came up the primary vsm still does not recognize that there is a standby.
    I went through the ovf and selected seondary and only entered the vsm domain id and the admin password.
    after the power on the master did not see the secondary
    any idea?

    Hi Tony,
    In order for this VSM to see its peer, you need to configure it for system redundancy role Primary. 
    As shown in the output, it is currently running in standalone mode.
    Once we reconfigure the first deployed VSM as primary, the two VSMs should see each other (given they have L2 connectivity)
    Nexus1000v# show system redundancy status
    Redundancy role
          administrative:   standalone
             operational:   standalone
    Redundancy mode
          administrative:   HA
             operational:   None
    This supervisor (sup-1)
        Redundancy state:   Active
        Supervisor state:   Active
          Internal state:   Active with no standby
    Other supervisor (sup-2)
        Redundancy state:   Not present
    Nexus1000v# con
    Nexus1000v(config)# system redundancy role primary
    After this change, the VSMs will negotiate and the secondary will reboot. When the secondary comes back up, we should see that they have paired.
    Nexus1000v(config)# show redundancy status
    Redundancy role
          administrative:   primary
             operational:   primary
    Redundancy mode
          administrative:   HA
             operational:   HA
    This supervisor (sup-1)
        Redundancy state:   Active
        Supervisor state:   Active
          Internal state:   Active with HA standby
    HTH,
    Joe

  • Can a Nexus 1000v be configured to NOT do local switching in an ESX host?

    Before the big YES, use an external Nexus switch and use VN-Tag. The question is when there is a 3120 in a blade chassis that connects to the ESX hosts that have a 1000v installed on the ESX host. So, first hop outside the ESX host is not a Nexus box.
    Looking for if this is possible, if so how, and if not, where that might be documented. I have a client who's security policy prohibits switching (yes, even on the same VLAN) within a host (in this case blade server). Oh and there is an insistance to use 3120s inside the blade chassis.
    Has to be the strangest request I have had in a while.
    Any data would be GREATY appreciated!

    Thanks for the follow up.
    So by private VLANs, are you referring to "PVLAN":
    "PVLANs: PVLANs are a new feature available with the VMware vDS and the Cisco Nexus
    1000V Series. PVLANs provide a simple mechanism for isolating virtual machines in the
    same VLAN from each other. The VMware vDS implements PVLAN enforcement at the
    destination host. The Cisco Nexus 1000V Series supports a highly efficient enforcement
    mechanism that filters packets at the source rather than at the destination, helping ensure
    that no unwanted traffic traverses the physical network and so increasing the network
    bandwidth available to other virtual machines"

  • Cisco Nexus 1000v Virtual Switch for Hyper-V Availability

    Hi,
    Does anyone have any information on the availability of the Cisco Nexus 1000v virtual switch for Hyper-V. Is it available to download from Cisco yet? If not when will it be released? Are there any Beta programs etc?
    I can download the 1000v for VmWare but cannot find any downloads for the Hyper-V version.
    Microsoft Partner

    Any updates on the Cisco Nexus 1000v virtual switch for Hyper-V? Just checked on the Cisco site, however still only the download for VMware and no trace of any beta version. Also posted the same question at:
    http://blogs.technet.com/b/schadinio/archive/2012/06/09/windows-server-2012-hyper-v-extensible-switch-cisco-nexus-1000v.aspx
    "Hyper-V support isn't out yet. We are looking at a beta for Hyper-V starting at the end of February or the begining of March. "
    -Ian @ Cisco Community
    || MCITP: EA, VA, EMA, Lync SA, makes a killer sandwich. ||

  • After upgarde Nexus 1000V the product Name still not update on vSphere Client

    Hi All,
    I encounter the problem after i upgrade the Nexus 1000v to new version 1.1a, but the vSphere Client console sill remain the old version Nexus 1000v 4a. Anyone know how to change it?
    Attached screen capture for your reference.
    Regards,
    Jason

    Hi,
    Thank you for posting in Windows Server Forum.
    From your description it seems that you are facing issue only with windows 8\8.1. So firstly suggest you to check with application support team, whether they have whole support for application with newer version. Also check once with application support team
    regarding this issue.
    This issue occurs because the local taskbar does not receive the EVENT_OBJECT_NAMECHANGE event from the system due to a timing issue. The EVENT_OBJECT_NAMECHANGE is needed to update the taskbar title information.
    More information (For reference).
    The taskbar may not show the application name correctly when using a Terminal Server RemoteApp
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • Cisco Nexus 1000v on Hyper-v 2012 R2

    Dears;
    I have deployed Cisco Nexus 1000v on Hyper-v hosts 2012 R2, and I'm in phase of testing and exploring feature, while doing this I removed the Nexus Virtual Switch {VEM} from HOST, it disappeared from host but I couldn't use the uplink attached previously with the switch as it sees it still attached on Nexus 1000v. I tried to remove it by several ways finally the host gets unusable and I had to setup the host again.
    the question here; there is no mention on cisco documents for how to uninstall or remove the VEM attached to a host, can any one help in this ?
    Thanks
    Regards

    Zoning is generally a term used with fibre channel, but I think I understand what you mean.
    Microsoft Failover Clusters rely on shared storage.  So you would configure your storage so that it is accessible from all three nodes of the cluster.  Any LUN you want to be part of the cluster should be presented to all nodes.  With iSCSI,
    it is recommended to use two different IP subnets and configure MPIO.  The LUNs have to be formatted as NTFS volumes.  Run the cluster validation wizard once you think you have things configured correctly.  It will help you find any potential
    configuration issues.
    After you have run a cluster validation and there aren't any warnings left that you can't resolve, build the cluster.  The cluster will form with the available LUNs as storage to the cluster.  Configure the storage to be Cluster Shared Volumes
    for the VMs, and left the witness as the witness.  By default, the cluster will take the smallest LUN to be the witness disk.  If you are just using the cluster for Hyper-V (recommended) you do not need to assign drive letters to any of the disks. 
    You do not need, nor is it recommended to use, pass-through disks.  There are many downsides to using pass through disks, and maybe one benefit, and that one is very iffy.
    . : | : . : | : . tim

  • Port-security and Nexus 1000v

    Is there really any true need for port-security on Nexus 1000v for vethernet ports? Can a VM be assigned a previously used vethernet port that would trigger a port-security action?

    If you want to prevent admins or malicious users from being able change the mac address of a VM then port-security is a useful feature. Especially in VDI environments where users might have full admin control of the VM and can change the mac of the vnic.
    Now about veths ports. A veth gets assigned to a VM and stays with that VM. A veth is only released when either the nic on the VM is deleted or the nic is assigned to another port-profile on the N1KV or a port-group on a vSwitch or VMware DVS. Now when the veth is released it does not retain any of the piror information. It's freed up and added to a pool of available veths. When a veth is needed for a VM in either the same port-profile or a different port-profile the free veth will be grabbed and initialized. It does not retain any of the previous settings.
    So assigning a VM to a previsously used veth port should not trigger a violation. The MAC should get learned and traffic should be able to flow.

  • Nexus 1000v port-channels questions

    Hi,
    I’m running vCenter 4.1 and Nexus 1000v and about 30 ESX Hosts.
    I’m using one system uplink port profile for all 30 ESX Host; On each of the ESX host I have 2 NICs going to a Catalyst 3750 switch stack (Switch A), and another 2 NICs going to another Catalyst 3750 switch stack (Switch B).
    The Nexus is configured with the “sub-group CDP” command on the system uplink port profile like the following:
    port-profile type ethernet uplink
    vmware port-group
    switchport mode trunk
    switchport trunk allowed vlan 1,800,802,900,988-991,996-997,999
    switchport trunk native vlan 500
    mtu 1500
    channel-group auto mode on sub-group cdp
    no shutdown
    system vlan 988-989
    description System-Uplink
    state enabled
    And the port channel on the Catalyst 3750 are configured like the following:
    interface Port-channel11
    description ESX-10(Virtual Machine)
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 500
    switchport trunk allowed vlan 800,802,900,988-991
    switchport mode trunk
    switchport nonegotiate
    spanning-tree portfast trunk
    end
    interface GigabitEthernet1/0/18
    description ESX-10(Virtual Machine)
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 500
    switchport trunk allowed vlan 800,802,900,988-991
    switchport mode trunk
    switchport nonegotiate
    channel-group 11 mode on
    spanning-tree portfast trunk
    spanning-tree guard root
    end
    interface GigabitEthernet1/0/1
    description ESX-10(Virtual Machine)
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 500
    switchport trunk allowed vlan 800,802,900,988-991
    switchport mode trunk
    switchport nonegotiate
    channel-group 11 mode on
    spanning-tree portfast trunk
    spanning-tree guard root
    end
    Now Cisco is telling me that I should be using MAC pinning when doing a trunk to two different stacks , and that each interface on 3750 should not be configured in a port-channel like above,  but should be configured as individual trunks.
    First question: Is the above statement correct, are my uplinks configured wrong?  Should they be configured individually in trunks instead of a port-channel?
    Second questions: If I need to add the MAC pinning configuration on my system uplink port-profile can I create a new system uplink port profile with the MAC pinning configuration and then move one ESX host (with no VM on them) one at a time to that new system uplink port profile? This way, I could migrate one ESX host at a time without outages to my VMs. Or is there an easier way to move 30 ESX hosts to a new system uplink profile with the MAC Pinning configuration.
    Thanks.

    Hello,
    From what I understood, you have the following setup:
         - Each ESX host has 4 NICS
         - 2 of them go to a 3750 stack and the other 2 go to a different 3750 stack
         - all 4 vmnics on the ESX host use the same Ethernet port-profile
              - this has 'channel-group auto mode on sub-group cdp'
         - The 2 interfaces on each 3750 stack are in a port-channel (just 'mode on')
    If yes, then this sort of a setup is correct. The only problem with this is the dependance on CDP. With CDP loss, the port-channels would go down.
    'mac-pinning' is the recommended option for this sort of a setup. You don't have to bundle the interfaces on the 3750 for this and these can be just regular trunk ports. If all your ports are on the same stack, then you can look at LACP. The CDP option would not be supported in the future releases. In fact, it is supposed to be removed from 4.2(1)SV1(2.1) but I still see the command available (ignore 4.2(1)SV1(4) next to it) - I'll follow up on this internally:
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_2_1_1/interface/configuration/guide/b_Cisco_Nexus_1000V_Interface_Configuration_Guide_Release_4_2_1_SV_2_1_1_chapter_01.html
    For migrating, the best option would be as you suggested. Create a new port-profile with mac-pinning and move one host at a time. You can migrate VMs off the host before you change the port-profile and can remove the upstream port-channel config as well.
    Thanks,
    Shankar

  • Nexus 1000v: Control VLAN must be same VLAN as ESX hosts?

    Hello,
    I'm trying to install nexus 1000v and came across the below prerequisite.
    The below release notes for Nexus 1000v states
    VMware and Host Prerequisites
    The VSM VM control interface must be on the same Layer 2 VLAN as the ESX 4.0 host that it manages. If you configure Layer 3, then you do not have this restriction. In each case however, the two VSMs must run in the same IP subnet.
    What I'm trying to do is to create 2 VLANs - one for management and the other for control & Data (as per latest deployment guide, we can put control & data in the same vlan).
    However, I wanted to have all ESX host management same VLAN as the VSM management as well as the vCenter Management. Essentially, creating a management network.
    However, from the above "VMWare and Host Prerequisites", does this means I cannot do this?
    I need to have the ESX host management same VLAN as the control VLAN?
    This means that my ESX host will reside in a different VLAN than my management subnet?
    Thanks...

    Control vlan is a totally seperate VLAN then your System Console. The VLAN just needs to be available to the ESX host through the upstream physical switch and then make sure the VLAN is passed on the uplink port-profile that you assign the ESX host to.
    We only need an interface on the ESX host if you decide to use L3 control. In that instance you would create or use an existing VMK interface on the ESX host.

  • Poor connection issue sends message "Verizon customer is not available" to callers rather than to VM!

    My phone is my business.  It's the only way I have for clients to reach me to schedule appointments.  Most of my clients are new at this point.  While my latest of 5 replacement phones don't drive me AS crazy with connection issues, it's driving my husband crazy as he daily gets told I'm not available and can't even leave a voicemail (which is usually yelling at me to dump this piece of crap phone).  If he gets that message daily, I wonder how many clients I'm losing from getting the message as well!!  With corporate discounts of 25%, I have still spent over $450 on this phone, all but the screen saver at the Verizon store.  I was given the option of "upgrading" to a Razr last time.  PLEASE!  The CR tried telling me it was newer (don't think so, pretty sure it was on the display right next to my Nexus in Dec), better camera (very debatable, and with much lesser quality screen, who cares about more mp?!), and that I bought my phone 8-9 months ago but it had been available much longer.  Umm, I bought it the week it was released.  I don't think 2 days can be considered "much longer".
    I'm going to try the switch to straight CDMA that seems to work for some with connection dropping, because I can't afford clients getting that message (they understand being sent to voicemail if I'm in a session), but... I bought this phone with a price tag of $299, paid another 99 for insurance, screen saver, gel case, extra battery and charger when my first phone port was shot after 7 months waiting for replacement, and luckily haven't bothered w/ screen savers for the weekly replacements or I'd have to add another $100 to the cost.  This is a flagship phone with a flagship starting contract cost, and the best they can do is send out refurbs that have the same issue over and over.  My guess is the turnover is so great they don't go through the normal testing and repairs of typical refurbs.  Take these refurbs off the market when they're returned with bad radio!  I'd consider a GS3, Razr Maxx, or maybe even the upcoming RazrM (though that would def be a downgrade considering the starting cost and we don't know yet of what issues it will have, but I like the size and battery life), though it sucks that I'd be spending another $50 just on case and screen saver.
    Anyone else experience the unavailable issue and get it resolved? I'm so tired of calling tech support.  And why can't they just put the phone number right on the "contact us" page like normal companies??

        I certainly understand the need to have an operable device!  Please DM me your name and mobile number, so I may further assist you.  Thank you!
    TominqueB_VZW
    Please follow us on Twitter @VZWSupport

  • OVM 3.3.1:  NFS storage is not available during repository creation

    Hi, I have OVM Manager  running on a separate machines managing 3 servers running OVM server  in a server pool. One of the server also exports a NFS share that all other machines are able to mount and read/write to. I want to use this NFS share to create a OVM repository but so far unable to get it to work.
    From this first screen shot we can see that the NFS file system was successfully added under storage tab and refreshed.
    https://www.dropbox.com/s/fyscj2oynud542k/Screenshot%202014-10-11%2013.40.00.png?dl=0
    But its is not available when adding a repository as shown below. What can I did to make it show up here.
    https://www.dropbox.com/s/id1eey08cdbajsg/Screenshot%202014-10-11%2013.40.19.png?dl=0
    No luck with CLI either.  Any thoughts?
    OVM> create repository name=myrepo fileSystem="share:/" sharepath=myrepo - Configurable attribute by this name can't be found.
    == NFS file system refreshed via CLI === 
    OVM> refresh fileServer name=share
    Command: refresh fileServer name=share
    Status: Success
    Time: 2014-10-11 13:28:14,811 PDT
    JobId: 1413059293069
    == file system info
    OVM> show fileServer name=share
    Command: show fileServer name=share
    Status: Success
    Time: 2014-10-11 13:28:28,770 PDT
    Data:
      FileSystem 1 = ff5d21be-906d-4388-98a2-08cb9ac59b43  [share]
      FileServer Type = Network
      Storage Plug-in = oracle.generic.NFSPlugin.GenericNFSPlugin (1.1.0)  [Oracle Generic Network File System]
      Access Host = 1.2.3.4
      Admin Server 1 = 44:45:4c:4c:46:00:10:31:80:51:c6:c0:4f:35:48:31  [dev1]
      Refresh Server 1 = 44:45:4c:4c:46:00:10:31:80:51:c6:c0:4f:35:48:31  [dev1]
      Refresh Server 2 = 44:45:4c:4c:47:00:10:31:80:51:b8:c0:4f:35:48:31  [dev2]
      Refresh Server 3 = 44:45:4c:4c:33:00:10:34:80:38:c4:c0:4f:53:4b:31  [dev3]
      UniformExports = Yes
      Id = 0004fb0000090000fb2cf8ac1968505e  [share]
      Name = share
      Description = NFS exported /dev/sda1 (427GB) on dev1
      Locked = false
    == version details ==
    OVM server:3.3.1-1065
    Agent Version:3.3.1-276.el6.7Kernel Release:3.8.13-26.4.2.el6uek.x86_64
    Oracle VM Manager
    Version: 3.3.1.1065
    Build: 20140619_1065

    Actually, OVM, as is with all virtualization servers, is usually only the head on a comprehensive infrastructure. OVM seems  quite easy from the start, but I'd suggest, that you at least skim trough the admin manual, to get some understanding of the conecpts behind it.  OVS thus usually only provides the CPU horse power, but not the storage, unless you only want to setup a single-server setup. If you plan on having a real multi-server setup, then you will need shared storage.
    The shared storage for the server pool, as well as the storage repository can be served from the same NFS server without issues. If you want to have a little testbed, then NFS is for you. It lacks some features that OCFS2 benefits from, like thin provisioning, reflinks and sparse files.
    If you want to remove the NFS storage, then you'll need to remove any remainders of any OVM object, like storage repositories or server pool filesystems. Unpresent and storage repo and delete it afterwards… Also, I hope that you didn't  create the NFS export directly on the root of the drive, since OVM wants to remove any file on the NFS export and on any root of ony volume there's the lost-found folder, which OVM, naturally, can't remove. Getting rid of such a storage repo can be a bit daunting…
    Cheers,
    budy

  • Nexus 1000v .jar file missing from Nexus1000v.5.2.1.SV3.1.1

    Hello ALL!
    I am trying to install and configure Nexus 1000v, for the first time and looking to configure the second stage of linking the Nexus 1000v switch to vCenter and from tutorials and white papers say to continue the install using a .jar file. However not seeing this file in the latest release in 1000v zip file.
    I can see this .jar file in the version 4 release and re-downloaded the v5 just incase it was corrupt and from a different machine; no .jar file.
    %windir%\Nexus1000v.5.2.1.SV3.1.1-pkg\Nexus1000v.5.2.1.SV3.1.1.zip\Nexus1000v.5.2.1.SV3.1.1\VSM\Install
    Cant find the white papers for v5, has anything changed?
    HELP!!
    JC

    Check this:
    http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus1000/sw/5_2_1_s_v_3_1_1/install_upgrade/workflow/nexus_1000v_r_5_2_1_s_v_3_1_1.html
    2-All files for this release can be found here:
    http://www.cisco.com/c/en/us/support/switches/nexus-1000v-switch/model.html
    HTH

  • Cluster Not Available error when booting OVM server DOM0 from USB

    Hi all,
    I have been wanting to run OVM 2.2 from a USB stick for a while now. I ran through the install CD today and saw there was a 'minimal USB install' option on the installation screen. So I plugged in a 4GB USB stick, rebooted, and ran the USB install.
    After a while, the install completed, OVM booted up perfectly it seemed, and I was happy.
    The server had no local storage apart from this USB stick as we are going to be hooking it up to an iSCSI target for guest VM storage.
    This was a new lab setup, so I got the VM Manager running on another system, connected to the USB booted OVM server, and went to create a pool.
    Running the 'test connection' that worked fine.
    Trying to add the pool - failed. I got the error 'Cluster Not Available'
    On the OVM server I did a repos.py -l and nothing gets listed.
    I understand that for HA you need a repository with shared storage. However, before I have used these same install CDs with a singe local hard disk, to get OVM server running, and it did so fine.
    So what's different with the USB disk install that means you don't get a repository?
    Do I have to create a special repository LUN, manually connect the OVM server to this, and then use repos.py to create it?
    Cheers,
    Jeff

    Ok I have read, re-read related parts of the underground manual and have hit a brick wall with the 'simple' task of setting up a NIC for dedicated iSCSI traffic. The manual does not cover this task in the iSCSI SAN section.
    So I'm in a catch 22.
    My OVM server boots up, with it's single management NIC configured, but once booted - I don't want to connect to the iSCSI target via this network - I need it completely closed off.
    I want to use another NIC (or bond of two) for dedicated iSCSI traffic to and from the OVM Server.
    However, the underground manual strangely only seems to cover a single NIC configuration! It looks like he assumes you are going to be running iSCSI on your management NIC, which I can only think is incredibly bad practice.
    I have installed OVM with the linux asknetwork - this did not give me the option to configure additional interfaces.
    I then manually edited /etc/sysconfig/network-scripts/ifcfg-eth1 on the OVMServer, restarted network, restarted the entire box - I can ping my new NIC / IP locally from within the OVM server, but I can not connect to the iSCSI target, nor can I ping the iSCSI NIC on the OVM server from the target.
    This is such a simple thing to try to achieve - super frustrating...
    Jeff

Maybe you are looking for