Home |  About Us |  News |  Print |  Sitemap
Intermate

Q:No contact to IAPS after relocating to another network

Question:
I need to connect to an IAPS IPDS again, after it has been connected to another network. I do not know which IP address it had in the other network, and none of the methods from the Getting Started guides seems to work?

 

Answer:
The IAPS unit is default configured to obtain an IP address by DHCP.

1. Unknown static IP address:
If you know there is a static IP address configured in the IAPS, and the IP address is unknown, do the following:

Attach the device in your current network and start up the Appliance Launcher on a PC that is connected in the same subnet. the Appliance Launcher will detect the IAPS via UDP.

Note that Cisco network device management software typically will prevent applications that are designed to broadcast UDP from working as designed. In that case you need to connect your PC via a cross wired Ethernet cable to the IAPS LAN port, in order to make the Appliance Launcher detect the IAPS. Note that the PC's Network adapter settings must be configured to use a fixed IP address in order for the UDP to work (typically a PC would be configured for DHCP). The static IP address could be 10.0.0.2 with a subnet mask of 255.255.255.0.

2. Still unreachaeble.
If the IAPS is configured for DHCP or you are not sure if it is configured with a static IP address, do the following.

If the IAPS is configured for DHCP and you are trying to get contact to it in a network that does not have a DHCP server, or where the DHCP server will only assign IP address to certain types of equipment, you may have a problem immediately detecting the IAPS with the Appliance Launcher.

If the IAPS can not reach a DHCP server, it will give up an fall back to its default static address 10.0.0.1. You may have to wait up to 5 minutes before the IAPS gives waiting for a DHCP server and assigns this static IP address. Only then the IAPS will respond to the Appliance Launcher broad casts.

Note that Cisco network device management software typically will prevent applications that are designed to broadcast UDP from working as designed. In that case you need to connect your PC via a cross wired Ethernet cable to the IAPS LAN port, in order to make the Appliance Launcher detect the IAPS. Note that the PC's Network adapter settings must be configured to use a fixed IP address in order for the UDP to work (typically a PC would be configured for DHCP). The static IP address for your PC could be set to 10.0.0.2 with a subnet mask of 255.255.255.0. After powering on the IAPS in this configuration you can, after a couple of minutes, repetitively select "Search" in the Appliance Launcher. Within 5 minutes the Appliance Launcher should have discovered the IAPS device.

3. Specific for IAPS IPDS with firmware G50-10-101
The firmware version G50-40-101 has a bug that prevents accessing it with the Appliance Launcher.
If the IAPS was loaded with this firmware and configured with DHCP, you can connect it to your network and let it get a DHCP assigned address. Check your DHCP server's lease log to determine what IP address it received.
If the IAPS was loaded with this firmware and configured with a static IP address, you will only be able to access it on that address. In that case you will have two options:
  1. Create a subnet identical to that of the IAPS,
      and reach it on its current static address:
  2. If you do not know the static address, you will need to return the
      IAPS to Creo for resetting in the production environment. For that
      you will need to fill a RMA form

4. Still no luck
There may be some more severely wrong with the IAPS device, and you may have to return it to Creo for resetting in the production environment. For that you will need to fill a RMA form.




Site Map  |   Copyright  |   Legal  |   Privacy Policy
All rights reserved. This site is best viewed using either I.E. 6.x and higher or Netscape 7.x and higher or Safari.