Similar Questions

• Failover problem Manager HA of the NAC

  Hi all

  I have a high availability manager high availability server of the NAC and NAC. When I try to active failover primary NAC Manager to secondary NAC Manager, NAC Server is not able to connect to the secondary NAC Manager. I don't know that ip connectivity is not a problem. When I try to do the NAC Manager primary such as active, the NAC server can connect to the main Manager of NAC. It seems that NAC Server cannot connect to the secondary NAC Manager.

  Does anyone have an idea?

  Thank you.

  have you checked certificates between them?

  you export the certificate of the secondary primary NAC NAC?

• The team of NIC failover problem

  Hi all

  We have a problem with the failover of vSwitches.

  Basically the problem is when I unplug the cable of the two physical natachasery associated with my vSwitch there is a loss of contents of a sachet.  The content of a packet loss creates no real problems but the biggest problem is when you plug the network cable from back in.  That's where we lose 10 packs, what causes host ESXi due relinquish in VCenter since I did the test on the uplink system and causing all virtual machines that are running under it restart on another Member of the same Cluster ESXi host.

  After a lot of reading these forums and Ken vSwitch debate blog http://kensvirtualreality.wordpress.com/2009/04/05/the-great-vswitch-debate%E2%80%93part-3/

  Using the default route based on the original virtual port code should work just fine without the need of any special Cisco switch configuration.

  We run ESXi 4.1 HP DL380 / DL360 servers.  This is the configuration for VMware and switch cisco so any help is greatly appreciated.

  VMware VSwitch and PortGroup configs are attached as images.

  Cisco config which only the two switchports connected to the specific ESXi is attached as a text file.

  What us has monitored him looking at the physical cisco switch when attempting to connect the network to switch the switchport cisco cable flashes orange so that network on ESXi reports linking as down and as soon as the switchport goes green ESXi comes back online.

  Any ideas or recommendations how to solve this are greatly appreciated.

  ... should work just fine without the need of any special Cisco switch configuration...

  There is an important parameter, you must configure. It is the spanning tree portfast

  See http://kb.vmware.com/kb/1003804 for more details

  André

• Failover problem SRM production running on both sites...

  I recently started an implementation of SRM. We have two data centers with production virtual machines running on two sites. We use Recoverpoint for replication.

  Last week, I put a vm of single test on a single data store itself and ran a test failover to the other site. I've got 5 data stores in the protected site running of the production virtual machine and about 15 stores of data in the site of "recovery" as well the production of the virtual computer running. I had a single VM running on a data store in the protected site of test and did a test failover on the site of "recovery."

  SRM/Recoverpoint eventually taking snapshots ALL my production, on the site of recovery (15 stores data) data warehouses which in turn confused the ESX servers and brought a lot of production VM running around this site down.

  Datstores in the recovering site showed duplicate... data store name as snapshot... of the data store name

  My understanding is THAT SRM should ONLY be slamming the data store that you no longer, is that correct?

  Not sure if the problem is with the SRA Recoverpoint in that it makes a change to LUNS or parameters of SRM which have been applied to the LVM on the hosts.

  I have a case open with VMware support and they say resignaturing is a global change and that's the way it works. Many things I've read that you can have prod virtual machines running on two sites. They say it's normal behavior.

  Anyone can shed some light on this?

  Please send me the newspaper.

  not wanting to take the path of your support call open I'll tell you what I saw.

  basically in your journal whenever you run test failover the recoverpoint THAT SRA is never working against a replica key unique lun. According to your descriptions above is correct because the recovery plan contains you only a single protection group and a single lun object.

  It means so I can only assume that at some point your SITE1VMFS volumes * that become suddenly resigned were running at some point LUNS that come from your table to site2 (clariion?) and were then separated (for data migration?) so that you now VM to Site1, those LUNS was then themselves (in the case of SITE1VMFS1 and SITE1VMFS2) re-re-replicated to Site2.

  However if after that replication first divide those LUNS was not manually resigned then if at any time later (for example, when you install SRM) something else happens and allows Site1 resignaturing on your hosts (like SRM) then these original LUN of 'split' with their old Site2 SCSI_DiskId will always be detected as snapshot LUNS per ESX since the vmkernel will see a subdomain of the 78 SCSI_DiskId byte is incompatible.

  Not sure if this is part of the origin of these LUNS Site1 at all, but what's in the newspapers, this theory is the only one that makes sense to me at the moment.

  hope that helps,

  Lee

• RADIUS with c2950G failover problem

  Hello

  I use a DOT1X authentication based on the two Windows of IAS servers.

  My access switches are C2950 and I want to work with several Radius Server for high availability purposes.

  But when my primary IAS server falls down (is declared dead when debug radius messages), try my switch to connect with each other and it does not work.

  I have the following messages:

  "10:22:57.412 Sep 12 UTC: RADIUS: signed new package (key: ciscomgt;). rctx: 0x80DA94

  18)

  10:22:57.412 Sep 12 UTC: RADIUS: try Server following (10.4.20.112:1812, 1813) for

  id157

  10:22:57.412 Sep 12 UTC: RADIUS: Fail-over refused to (10.4.20.112:1812, 1813)

  id157

  10:22:57.412 Sep 12 UTC: RADIUS: no response for id 157

  It's still in "swing state" with each other.

  With I try separately, the works of two servers correctly. When I try with a C2970 platform that works too. Are there special recommendations with the C2950?

  Thanks for your help

  Hi Gilou,

  Please add the following command and if possible try again failover

  RADIUS deadtime server 1

  Let me know how it goes

  Kind regards

  ~ JG

  Note the useful messages

• Controllers of the array failover (Dell md3020i, esxi5) and VAAI

  We lack 6 5.1 esxi hosts that use the vmfs5 storage provided via iscsi from a double controller Dell md3020i.  Our charge approximately 900 inputs/outputs, but can boost 1800 IOPS / s.

  During periods of high load, our virtual disks to failover from one controller to another.  This does not stop time, but produced a few problems on the virtual disk of balancing on the controllers.  We have opened a folder with Dell, and they see mistakes ancient IO from esxi hosts.  Dell is investigating a possible firmware (not yet released) was updated and also suggesting an update of firmware of the hard drive.  They also mentioned that we can almost be the ability of the matrix (in terms of IOPS / s).

  We also opened a case of VMware support.  They recommend that we disable VAAI. (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1033665).  But all what I have read talks about the benefits of performance of the VAAI and our table officially support it.  I ran this suggestion by Dell, and they disagree - recommend us keep active VAAI.

  So, we are stuck with what to do next.  Suggestions from the community on VAAI or other changes to help with our table failover problem?

  Thank you

  I don't think that VAAI is a problem. It could due to an overload on the disk due to the IOs, it is moving to the other controller. Please update the firmware...

  You have excerpts from newspapers pointing to older IOs that shows problems with ESXi

• Failover of DAG 2013 Exchange in Outlook problem

  Hi guys,.

  I'm trying to configure DAG for the first time on Exchange 2013.  Here's what I did:
  -Installed Exchange 2013 std on two virtual machines

  -Set up a witness server

  -Created the DAG (server name, directory witness and he has assigned an IP address)

  -J' have set up my databases and added the copy of database

  -Checked DAG health Active confirmed and index as healthy state

  -Verification of databases is mounted

  Here's the problem I have...

  When I powerdown one of the exchange servers, after that the exchange server starts to close Outlook (2013), poster "folder updated XX: XX."  trying to connect.
  When I check the connection status in Outlook on the workstations, it shows the status of 'Connection' and after a few minutes (between 5 and 10), it finally connects and everything works fine.

  I tried researching this issue and that you have used the following command in the hope, would solve the problem, but it does not

  [PS] C:\>get-OutlookAnywhere | Set-OutlookAnywhere - InternalHostname mail.labtest.co.uk - InternalClientsRequireSsl $false

  My questions are:
  1. I guess that's not just that it takes more than 5 minutes for Outlook to connect when the failover of DAG?  What additional steps need to be checked to prevent this (as I thought that take seconds to scan more)

  2. If a witness server goes down / fail, does that mean that all Email clients will stop working (IE send/receive)

  If this is the case, is it possible to configure a failover of witness? or is it something that should be created in case of failure?

  Thanks a lot for any intervention in the present.

  Hello

  Your question is beyond the scope of this community.

  I suggest that repost you your Question in Exchange for TechNet Forums.

  https://social.technet.Microsoft.com/forums/Exchange/en-us/home?category=ExchangeServer

  Or here:

  https://social.technet.Microsoft.com/forums/Exchange/en-us/home?Forum=exchangesvrgeneral

  See you soon.

• Problems of AX150i cluster and failover

  Hi all.

  I tried to implement cluster failover on Win2003 x 64 with AX150i.

  We already have a cluster configured with an AXE so I now it is not working properly.

  The problem is that when I create a cluster node owns the disks and another should see drives but have no rights over them except wait for them to be released from the first node, but on my setup when the first node appropriating on diskettes, disks on the other node start to fail, they become unavailable , cluster service who sees and stops, so the second node becomes unavailable too.

  I have the latest firmware installed, latest PowerPath and the latest Microsoft iScsi initiator installed.

  Any suggestion would be appreciated.

  Thank you

  Concerning

  Amar

  
  

• PIX 515E failover restart problems

  Thursday, November 23, we went from the PIX cluster to version 7.1 (2) 6.2 (2) with the default memory (64 MB) in each PIX. The Active PIX then suffered what appeared to be leaking memory (attributed to process ARP Thread). This continued for a few days? with the result that we force reloaded the Active PIX every 8 hours to ensure the continuity of the service. Monday 27 after a reload? It has been noticed that the Active PIX leaked is more memory per process threads ARP? the same day, we went from the cluster PIX to 128 MB of memory. Then, we have had failovers active / standby every 2 hours? that seems to be attributed to missed? Hello? in the e-mail of failover? We decided then to configure LAN failover on the PIX cluster. In the process of activation of this secondary feature PIX (which was the current asset) crashed

  You have any explanation as to why these events took place.

  Hi Carlton,

  I can tell you that maybe the method you used to upgrade starts the chain of problems. I used for the migration of these products and I've never met before. In general I WINS configurations, program a service stop and I leave the unit of failover working alone while I do the upgrade of the unit the ex-active. After the upgrade, I had loaded the software configuration I saved before and made the customizations.

  For the PIX without restrictions, is real memory of 128 MB required. For the restricted permission, you can use the default of 64 MB.

  After that, you can place the active unit instead of the recovery. You improve the unit of failover so and connect again in active, already in production and restart the synchronization.

  For all my clients, it worked.

  It will be useful. If Yes, please rate.

  Kind regards

  Rafael Lanna

• Problem with VPN L2L and RA in a failover configuration

  I use two ASA 5540 in failover active-standby configuration. These boxes (primary and secondary) are used to establish some L2L and VPN RA (remote access). The active area run the OSPF process.

  The problem is when the failover (blocking just to the bottom of the active area, or "active failover" running in a secondary zone) all L2L be restored in a secondary zone. The only way I can do this (re-connect) removes the configuration of IPP (Reverse injectable way) (for example. ("no card crypto rprbbe_map 3 don't set reverse-road") and the configuration of IPP ("card crypto rprbbe_map 3 Road opposite the value"). After this the connection is re-established.

  In RA guests the session persists on a failover event, but the customer loses access. To resolve this problem, the customer needs to disconnect and reconnect.

  Anyone has any experience with this kind of (L2L and RA) VPN configuration using failover?

  Behavior seems buggy.

  What version do you use?

• Problem with Oracle fail safe 4.1.1 on W2k8 R2 Cluster Failover and Oracle 11.2.0.4 database

  Hi all

  I'm doing some tests on a Windows 2008 (64-bit) R2 two-node failover Cluster.

  I installed and configured successfully bone and the Failover Cluster feature.

  So I followed Oracle Doc-ID 1916391.1 to perform the installation and configuration of Oracle 11.2.0.4 database and Oracle Fail Safe 4.1.1

  After a successful (via Fail Safe Manager) validation of cluster and group, now I'm trying to validate the stand-alone database, but I'm stuck with this error (output in verbose mode of PowerShell):

  PS C:\Users\demo > Test-OracleClusterAvailableDatabase TESTDB - SysPwd (Read-Host-AsSecureString-Prompt "SYS Password ')-verbose

  SYS password: *.

  DETAILES: FS-10915: NODE1: from verification of autonomous resources TESTDB

  DETAILES: FS-10371: NODE1: run the initialization processing

  DETAILES: FS-10371: NODE2: run the initialization processing

  DETAILES: FS-10372: NODE1: resource owner information collection

  DETAILES: FS-10372: NODE2: resource owner information collection

  DETAILES: FS-10373: NODE1: determine the owner of the TESTDB resource node

  DETAILES: FS-10374: NODE1: collection of cluster information required to perform the specified operation

  DETAILES: FS-10374: NODE2: collection of cluster information required to perform the specified operation

  DETAILES: FS-10375: NODE1: analysis of the cluster information required to perform the specified operation

  DETAILES: FS-10378: NODE1: preparation for the configuration of resource TESTDB

  TH: FS-10349: database TESTDB instance is not alive. You want to stop and restart the database instance?

  Confirmation

  Operation does?

  Running dell' operation sulla "Test-OracleClusterAvailableDatabase' likelihood 'TESTDB '.

  [S] Sì Sì [T] a [N] no [U] tutti a tutti [O] Sospendi [?] Guida (he valore predefinito e "S"):

  DETAILES: FS-10350: from the TESTDB database

  Test-OracleClusterAvailableDatabase: OCIEnvNlsCreate failed

  
  

  Riga: 1 car: 1

  + Test-OracleClusterAvailableDatabase - SysPwd TESTDB (Read-Host - AsSecureString - P...)

  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: DeviceError: (TESTDB:ResourceDatabase) [Test-OracleClusterAvailableDatabase], PowerShell

  Exception

  + FullyQualifiedErrorId: Process, Oracle.FailSafe.PowerShell.TestOracleClusterAvailableDatabase

  Test-OracleClusterAvailableDatabase: FS-10999: an internal programming error

  Riga: 1 car: 1

  + Test-OracleClusterAvailableDatabase - SysPwd TESTDB (Read-Host - AsSecureString - P...)

  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: DeviceError: (TESTDB:ResourceDatabase) [Test-OracleClusterAvailableDatabase], PowerShell

  Exception

  + FullyQualifiedErrorId: Process, Oracle.FailSafe.PowerShell.TestOracleClusterAvailableDatabase

  Test-OracleClusterAvailableDatabase: FS-10160: impossible to verify the Oracle of standalone TESTDB database

  Riga: 1 car: 1

  + Test-OracleClusterAvailableDatabase - SysPwd TESTDB (Read-Host - AsSecureString - P...)

  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: DeviceError: (TESTDB:ResourceDatabase) [Test-OracleClusterAvailableDatabase], PowerShell

  Exception

  + FullyQualifiedErrorId: Process, Oracle.FailSafe.PowerShell.TestOracleClusterAvailableDatabase

  Test-OracleClusterAvailableDatabase: FS-10818: provider of resources of the database Oracle failed in preparing for

  treatment for TESTDB resource configuration

  Riga: 1 car: 1

  + Test-OracleClusterAvailableDatabase - SysPwd TESTDB (Read-Host - AsSecureString - P...)

  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: DeviceError: (TESTDB:ResourceDatabase) [Test-OracleClusterAvailableDatabase], PowerShell

  Exception

  + FullyQualifiedErrorId: Process, Oracle.FailSafe.PowerShell.TestOracleClusterAvailableDatabase

  Test-OracleClusterAvailableDatabase: FS-10890: Oracle Services for MSCS failed during the verifyStandalone operation

  Riga: 1 car: 1

  + Test-OracleClusterAvailableDatabase - SysPwd TESTDB (Read-Host - AsSecureString - P...)

  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: DeviceError: (TESTDB:ResourceDatabase) [Test-OracleClusterAvailableDatabase], PowerShell

  Exception

  + FullyQualifiedErrorId: Process, Oracle.FailSafe.PowerShell.TestOracleClusterAvailableDatabase

  Attached is the log of the OFS Cluster Dump (no error in my opinion).

  I surfed around but I can't find anything to solve the problem.

  I think something about the language of the (Italian) OS and Oracle NLS settings (AMERICAN. AMERICA), but obviolsly I'm not sure about this.

  Thanks in advance for any suggestion,

  Alessandro

  Message modificato da 1d457339-524e-4aa5-94aa-fd7d1ae98732 updated: attached is also output trace of the fss.

  Hello Alessandro.

  Solution to the issue is:

  Patch 20744940: 4.1.1.1: ORACLE FAIL SAFE VERSION 4.1.1 PATCH SET 1

• Problem of cluster Failover MS after physical RDM conversion to VMDK

  Hello

  Last week I had to migrate 7 x 2-nodes virtual MS Failover clusters to a new data center. All clusters have been configured with the configuration of the cabin and all shared disks were in physical RDM mode.

  The target data center does not RDM disks so I had to convert all RDM disks VMDK files and use config before the migration of the IPC.

  I used vmkfstools to convert VMDK eagdrzeroedthick RDM files.

  5 clusters have been migrated successfully, but two cluster got strange question even if the procedure for all groups was the same.

  So in two groups, I have a problem where the second node in the cluster can not put online some of the shared disks. The first nodes in the clusters have no problem with the disks/SSP.

  But when I try to failover of all services, the second node may not bring online disc 1 or 2 shared, even if she can put the other shared disks online.

  VMKernel.log is not errors or warnings. I checked the configuration of virtual machines and everything seems OK.

  Any ideas what I could check?

  Just in case anyone else is facing the same problem.

  I could not find the root cause of the problem, even if it's without a doubt the conversion that triggered the problem. However, we found quite a simple solution - added new shared VMDK files, copied the files over and replaced the defective discs.

• Failover ethernet configuracao problema

  OLA pessoal,

  Tenho pouca experiencia com VMWare vSphere 5.5 e estou um ambiente wave tenho Doi serve switches interligados com several VLAN e um servidor com quatro interfaces of rede.

  Estou tentando configurar because interface of rede para as funcionem com load balance e failover. Para isso, configurando an e estou porta porta 1 management network para portas para 2,3,4 have other redes.

  A porta 1, colocando estou no em uma switch VLAN especifica.

  While that as portas 2,3 e 4, colocando estou no switch o tipo of porta com permissao para todas as trunk VLAN.

  No vSphere, no port group than criei e configurei uma VLAN especifica, configurado a seguinte esta forma:

  Teaming e failover:

  • Balance the load = route from the originating virtual port
  • Network failure = link state only
  • Notify = yes switch
  • Failback = yes

  Problema e quando retiro um back cai, todos falham links.

  Alguem but experienced poderia me speak qual a pratica neste caso boa?

  Obrigado,

  Andson Gomes

  Cara,

  Primeiro EU gostaria Organizations o seguinte para seu ambiente vSwitch design.

  Supondo Quebec City as while not ESXi are conectadas da seguinte forma:

  vmnic0-> Switch Fisico #1

  vmnic1-> switch #2 Fisico

  vmnic2-> Switch Fisico #1

  vmnic3-> switch #2 Fisico

  EU criaria 02 (DOI) toggle tolls, o vSwitch0 e o vSwitch1, sendo o teriamos todo o trafego members vSwitch0 e vMotion e o vSwitch1 todo o trafego das maquinas tolls.

  An imagem abaixo mostra but or menos como ficaria:

  

  SE voce nao quer criar 02 (DOI) switches tolls, você ainda pode ter redundancia links rising doing a configuracao seguinte:

  Members PortGroup: vmnic0 ativo e vmnic1 Eve vmnic2/vmnic3 sem uso

  VMotion PortGroup: vmnic1 ativo e vmnic0 Eve vmnic2/vmnic3 sem uso

  PortGroup das Máquinas tolls: ativo vmnic2/vmnic3, e vmnic0/vmnic1 sem uso

  As too configuracoes do NIC Teaming EU mudaria only the failback:

  Balance the load = route from the originating virtual port

  Network failure = link state only

  Notify = yes switch

  Failback = no

  Da forma você falou acima, o tem uma placa, portanto não possui redundancia... only the members PortGroup voce nao sober says also to usa vMotion, use e caso não pode only para vMotion PortGroup o ignorar.

  Sober o seu problema em if qual o seu spend fisico? E da Cisco? POIS gostaria self possible da uma take na configuracao.

  Por ultimo, qual tipo vSwitch voce using ta? Standard or distributed?

• Problem with EqualLogic / MPIO / failover

  We ran a few tests in our environment with results less than ideal. Our environment is made up of 6 vSphere4 hosts a cluster connected to approximately 10 VMFS volumes. Each host has a vSwitch dedicated with two natachasery, 3 vmkernel NIC ports and each NETWORK adapter is connected to a different physical switch. We put the path of Round Robin policy so each volume has 6 paths of assets. On the side of EqualLogic, we have 3 members in a group, a pool for this group, and the controllers are connected to / balanced between these same two physical switches (5020 Nexus). This was based on the guide from the EqualLogic site. http://www.equallogic.com/resourcecenter/assetview.aspx?id=8453

  Our problem is when we try to test the failover / availability by simulating a failure of the switch. The EqualLogic group sees many timeouts / connection errors, but there still NIC is active on the active controller, so there is no controller failover. The hosts lose one of the two network adapters on the storage vSwitch, but even with a NETWORK card and online all VMFS volumes disappear from all hosts. When we make the switch online, all VMFS volumes return without taking corrective measures and virtual machines appear as if nothing happened. Try to use virtual machines, we see performance degradation until we have rescan / clean storage communication and then everything returns to normal.

  We are at a loss on where to start. We followed the recommendations of EqualLogic and of course being the guy from VMware that I pointed to storage. The hosts always show active paths when this happens and errors are the waiting times of connection which is the other reason, I think it would be good to start on the side storage. Someone out there with similar configurations which may have run into something similar?

  +The physical switches are independent.- + Overall, it's really jumping on me. All that I have worked with in EQL, you need to have some sort of connection between these two switches for balancing to work properly. When you say independent what do you mean? By doc of Dell, it indicates that the two switches need a group LAG/Etherchannel or stacked to take advantage of the LB correctly on the berries... I just have two PS4000 and set up with two 5424 PC with an offset of 4GB with no problems. The rest of your looks of thin configuration, should not have other problems on the side of VMware, it's certainly side of the switch.

  Maybe someone with more experience high-end Cisco can chime on what type of configuration you need between switches. I may be an another Dell doc that treats the necessary switching configurations.

• Failover of network problem

  Working with a new installation that consists of a blade HP c7000 with (3) BL680c performer enclosre esx4 set up as a single cluster. Each server has 4 NIC, vmnic0, and 1 in a vSwitch for console vmotion and service, vmnic2 and 3 in a vswitch for VM. The NETWORK card is configured in active/active failover configuration. I use VLAN tagged at the vswitches. The networking of the enclosure consists of (2) HP Virtual Connect 1/10 Gb Ethernet modues in bays 1 and 2. Vmnic0 Yes and 2 card in Bay 1 and vmnic1 and 3 card in bay 2. On the interconnections, there are 4 external ports on each switch configured as a shared uplink defined all the VLANS, each patched in a trunk group etherchannel on a single Cisco 2960. If the two etherchannels are patches for the same 2960.

  During the test I have a slight problem of failover. If I pull the plug on one of the 4 ports interconnections, maybe I'm wasting a ping of the virtual machine. However, when I plug the 4 patch cables back in, I will lose up to 6 or 7 pings when the switch fails in return. What seems to happen is that when I plug 4 connection cables and a link is established, the ESX servers try to fail, to the side of the virtual Connect 4 ports does not immediately active mode but prefer to go standby first, and assets, then a few seconds later. I think what is happening is that the ESX Servers detect the link and start trying not to return before that ports have actually been made available on the switch of VC.

  There is a pdf drawing attached to the basic configuration.

  Does anyone know if there is a way this problem could be solved, the ESX network or on the HP VC config config?

  Thank you.

  Dan

  I recommend that you open a file with CV.  This should not happen with Smart Link.  Smart Link should allow only a downlink if there is an active uplink.

  ITMT, try beacon as suggested probing.

  JP