50 | Virtual Server Networkingw w w . d e l l . c o m | s u p p o r t . d e l l . c o m DiscoveryThe discovery process starts after you enter the no disable command on the interfaceand ends 10 minutes after connectivity is established between the switch andhypervisor. If no connectivity is established, the switch attempts to connect for threeminutes and then stops. Refer to Connectivity for more details on this process.After you enable the link between a switch and a hypervisor, the switch uses adiscovery mechanism to learn VMAC and VLAN information from the hypervisor.The discovery process also starts in the following conditions:• You enter the shutdown and no shutdown commands on a VSN-enabled port.The discovery process resumes on the individual port only, not on all enabledports.• You enter the disable and no disable commands in hypervisor configurationmode for a specified type of hypervisor connection. The discovery process isresumed on all enabled ports.• An update arrives from a hypervisor. The discovery process resumes on allVSN-enabled ports.In order for a switch to learn VLAN information from a hypervisor:• Incoming traffic must be received on the VSN-enabled ports.• There must be at least one VMAC configured on the hypervisor so that the VCAPtable can capture the VMAC entries for each VSN-enabled port.The following log messages are displayed when the discovery process is interruptedand when it starts again.Message 1Nov 28 11:34:19: %STKUNIT0-M:CP %VSNMGR-5-VSN_DISCOVERY_SUSPENDED:Hypervisor macs not seen on Te 0/25. Discovery suspended.Message 2Nov 28 11:40:36: %STKUNIT0-M:CP %VSNMGR-5-VSN_DISCOVERY_RESUMED: Detectedconfig change in Hypervisor. Discovery of Hypervisor macs resumed on Te 0/25.ConnectivityIf a network server is not reachable, a log message is displayed and the VSN agenttries periodically to establish the connection with the hypervisor. The initial logmessage is:Message 3Xen-Citrix:Connection error for hypervisor testing:LOGIN FAILURE