Finding IP Address

By default (with default config) the Vega will obtain its IP address via DHCP with network cable plugged into LAN 1

The methods below detail how to obtain the Vega's IP (based on the above DHCP description).
You can then use the IP address to log into the Vega's web interface

Requirements:

• Vega Gateway (any model)

• DHCP Server (Except in Method 4)

• Workstation running Windows or Linux, with 'nmap' installed.
  (Nmap windows download: http://nmap.org/dist/nmap-5.51-setup.exe)
  (Nmap Linux: see distro repos or find sources here http://nmap.org/download.html)

Method 1: Vega Scanner

To find your Vega just download and run the Vega Scanner utility. This will scan your entire subnet to find the Vega. For this to work the Vega must be set to DHCP (default) or a STATIC ip on the subnet directly attached to your Windows system. 

Download -> 

Method 2: Ping Sweep

To begin, connect your Vega device to your network using the LAN 1 interface. The device must be on the same subnet as the workstation you will be using to find the IP address.

1. Turn on the Vega.

2. Note the MAC address of the Vega Ethernet interface, which can be found on the sticker above the LAN port on the Vega.

3. For Linux users: run the following nmap command:
   
   nmap -sP <ip range>
   
   Some versions of Nmap will output the IP and MAC address of every device on the subnet which responded to a ping. If you search through this output for the MAC address of the Vega, you will be able to see the corresponding IP for the device. If you find this output does not contain the MAC address, you can check the system ARP Table by running this command:
   
   arp -a 
   
   Search for the Vega's MAC address in this output and you will be able to see the corresponding IP
   
   For Windows users: Run Zenmap and enter the command in the box as shown below. Make sure to adjust the IP address for the subnet you are on. The output will be visible in the “Nmap Output” tab. You can find the Vega's MAC there and see the corresponding IP.
   
   
   

   Open

   

   
   
   If you don't see the MAC addresses in the output, open the comand prompt by pressing 'Windows Key+R' and typing 'cmd' in the dialog box, then hit 'Enter'. You can give the following command to list the arp table:
   
   arp -a
   
   Find the Vega's MAC in that list and you will be able to see the corresponding IP.

4. Once you have the IP of the Vega, you can open a browser and navigate to that addess to configure the device. You can also access the device through SSH 

Method 3: DHCP Server logs

By default, when the Vega is connected to the network and powered on, it will request an IP address via DHCP. If you network has a DHCP server you can check the active leases or the logs from the server to find what IP the Vega acquired. The DHCP server keeps track of all device MAC addresses for which it has active leases. Simply search the logs/leases for the MAC address of the Vega LAN interface you have connected to the network, and that should yield the IP address to allow access to the web interface.

Method 4: No DHCP Server: Stateless Autoconfig

The Vega gateways support addressing through "Stateless Autoconfig" (link-local addressing, RFC 3927, Microsoft APIPA). Stateless autoconfig will be used when the device is connected to a network and unable to communicate with a DHCP Server. The Vega gateway will assign itself an IP in the 169.254.1.0/16 range. The last two octets of the IP will be based on the MAC address of the Vega LAN interface that is connected. This can be discovered by taking that last two bytes of the MAC address, converting each byte into decimal and using them in the last two octets of the IP. A detailed explanation can be found on page 4 of the Quick Config guide (Here)

Method 5: Find IP From FXS Ports (Analog Vega i.e. Vega50/5000/3000G/3050G/60G)

Vega FXS gateways allow you to determine the values of a number of IP parameters by dialing #1#1 from a directly connect analog handset. 

Once #1#1 has been dialed a prompt will tell you that the Vega is waiting for a 3 digit command. Below is a complete list of the valid 3 digit codes:

101 to hear the IP address of the LAN gateway
111 to hear the IP address of LAN 1
112 to hear the subnet mask for LAN 1
121 to hear the IP address of LAN 2
122 to hear the subnet mask for LAN 2
131 to hear the IP address of the tftp server