Information for frequently asked questions on Arcstar Universal One Virtual
Registration Date: June 02,2015 / Update Date: June 23,2015
If you cannot connect to a destination UserNetwork, please check the settings by following the steps below.
[Step 1] Check the communication between the vClient and vCore
[Step 2] Check the settings of the destination UserNetwork
[Step 3] Check the settings of the vClient group
[Step 4] Check the communication from the destination UserNetwork
If you cannot connect even after checking the above
Descriptions here are based on an example with the following situation
as illustrated in the figure below.
- The customer applied for a simple design
- The customer wants to communicate from a vClient that belongs to a vClient group "Support Group"
- to "192.168.0.1" within a destination UserNetwork "Support NW."
|[Step 1]Check the communication between the vClient and vCore|
|[!] If no response to the ping|
|The vClient is not connected to the virtual network. Connect the vClient to the virtual network in reference to the following pages.
■I can’t connect to the Virtual Network via vApp.
■I can’t connect to the Virtual Network vAdapter.
|[Step 2] Check the settings of the destination UserNetwork|
|[!] If an incorrect address or gateway is set|
|Once registered, the address and gateway of the destination UserNetwork cannot be edited.
Please create a new destination UserNetwork with correct settings.
|[!]If not bound to vCore|
|On the graphical map, drag and drop the destination UserNetwork icon onto the vCore icon, and add a destination UserNetwork in "vCore Edit" screen > "User Network" tab.|
|[Step 3] Check the settings of the vClient group|
|[!]If no destination UserNetwork is set|
|Click "Add Row" to add a destination UserNetwork.|
|[Step 4] Check the communication from the destination UserNetwork|
|[!] If unable to communicate to vCore|
|Communication is not properly established between the destination UserNetwork and Universal One Virtual. Check settings including the following.
*In the host within the destination UserNetwork, information on the path to vSegment is properly registered.
*Your devices (e.g. FW) on the communication path permits communication to vSegment.
|If you cannot connect even after checking the above|
|(1)The result of traceroute
(2)vClientID that failed to connect to the destination UserNetwork
(3)Approximate time when the connection failed