Specifications

Chapter 3 Connecting on a LAN
Troubleshooting Connectivity to an Existing JACE Controller
Niagara Release 2.3
Niagara Networking & Connectivity Guide Revised: May 22, 2002
3–19
Step 5 Look for any IP addresses that fall outside the customer’s normal network address
range, and that are unfamiliar to you (i.e., not another host that you already know
about).
Since the JACE-NP is a Windows device, it sends out regular broadcast messages to
any master browser. These messages are sent to the broadcast address of the network
range the NP is in. For example, if the source address of the NP is 199.81.168.128
(with a Class C subnet mask of 255.255.255.0), then the broadcast address is
199.81.168.255. For an NP addressed as 172.20.15.1/255.255.0.0 (Class B), the
broadcast address is 172.20.255.255. For more information on broadcast addresses,
see the “Special IP Addresses” section on page 1-22.
Step 6 Change your engineering PC’s IP address to the same network range of a likely IP
address.
Step 7 Try to connect to the IP addresses with the Admin Tool or NetMeeting.
JACE-4/5 Since the JACE-4/5 does not run Windows as its OS, Windows networking will not
provide the name of a JACE-4/5. If a JACE-4/5 has been added to a DNS server (and
you know the name of it) you can still use the ping command to determine the IP
address. However, if you do not know the name or it is not in DNS, you can still
determine the IP address and subnet mask by connecting to the VxWorks target shell
and reading them, because they are displayed during the boot sequence.
Caution Be very careful when using the target shell on a JACE-4/5. You must log on
to the JACE with administrative privileges, which means you can change
many settings. Changes you make could have unexpected consequences,
including making the JACE inoperable.
Procedure 3-7 Determining an IP address of a JACE-4/5.
Step 1 Using Hyperterminal on your engineering station, connect to the VxWorks
command shell following Step 1 to Step 12 of Procedure 2-5.
Step 2 When you see text appear in the Hyperterminal window, do not break out of the boot
sequence as described in Step 13 of that procedure. Instead, allow the controller to
finish booting.
The controller displays startup messages similar what you see in the Standard Output
Window of the Admin Tool.
Step 3 When the controller stops displaying new messages, press ENTER to reach the
command prompt.
You see a prompt similar to the following:
->
Step 4 Using the scroll bars on the Hyperterminal window, scroll up until the section that
begins with the line Press any key to stop auto-boot... (see Figure 3-8).