Re: Use of target-server in large networks
- From: "LarryC" <larry@xxxxxxxxxx>
- Date: 28 Jun 2006 07:57:57 -0700
Hi:
You network looks similar to mine, except my desktop PC replaces your
"sun/solaris with Tornado". We have a similar local Sun that acts as a
bootserver.
Perhaps is it the frag problem mentioned in the FAQ.
lc
ReneeTeunissen wrote:
Hi:
I run a setup similar to yours and it works OK. See the MTU issue
below from the FAQ - it does sound familiar.
Sounds like there are route issues getting back from your board. One
thing I always do it set up a registry server on my PC that has the
address of my PC in it - ie tornado->tools->options->tornado registry,
select remote and put your pc's IP in there. Then the target knows
your IP address. I got this a while ago from the FAQ and it helps on
nets with gateways.
I assume your target can ping your Tornado host? Duplicate IPs can
certainly cause problems.
Good luck
LC
Q: Why am I getting a WTX Error 0x100de (AGENT_COMMUNICATION_ERROR)?
A: This can be caused by the Cisco Deterministic Network Extender,
which mucks about with MTU setting, causing Target Server transfers
to
fail for various reasons (the reduced MTU causes the packets from
the
target server to be fragmented, and WDB can't handle fragmented
packets).
(From: Pete Flugstad, peteflugstad@xxxxxxxxxxxxxxxx)
Note: Another solution is to use SetMTU.exe utility provided by Cisco
to restore the original MTU setting
Next to the above mentined problem it can also be caused by a lack of
target server memory. This can be the case if loading small files
works
but large files get stuck with this error. The solution then is to
increase the target server memory cache
Q: When I start the Targetserver I get an WTX error. It also says
synchronisation stopped. How can I fix this?
A: One solution to this problem is to use the remote registry, even if
you are using a target server on your local machine. This can be
done
by setting the remote registry and using the real IP address of the
host as the IP address for the remote registry.
Basically, "localhost" gets stored in the Windows registry for the
name
of the machine running the Tornado registry. The WTX tools on the host
resolve localhost to the ip address 127.0.0.1 and pass this down to
the
target. The target then tries to communicate with 127.0.0.1 to enable
the symbol table synchronization but ends up talking to itself and not
the Windows host. Neat "feature".
If your Windows machines has multiple ethernet interfaces and the
target is located on a non-primary interface, this still won't be
enough. The machine name will get resolved to an ip address that the
target doesn't know about. You will need to execute a routeNetAdd on
the target before connecting the target server in order to get symbol
table synchronization to work
ReneeTeunissen wrote:
Hi,
I try to connect to a target server across a network with a lot of
network components (routers and alike) between the tornado
application
and the sun-server which acts like bootserver and has a direct
ethernet
connection to the cpu-boards.
Problem, if I run tornado deom the bootderver it works just fine, if
I
run tornado from my development station, it gets a list of all
targets
which are registered in the registry-deamon (wtxregd).
If I click a target, the tornado launch says "target server not
responding".
Our local support engineer says that the protocol of the
targetserver
cant handle possible MTU / IP-fragmentation changes in the network,
and
the MTU should not be changed. For some reason I dont think the
system
admin is gonna change hos policiy about this.
My question is, if any of you know this isssue and have
workarounds for
it. Or are all of you just running Tornado on a system that shares a
physical network with the bootserver??
I thought about (ssh/netcat) tunneling the hole thing, but didnt get
that working yet. idears and solutions are more then welcome.
Cheers,
Renee.
--
Hi,
No, the target board cant ping the machine running Tornado. I was hping
to use the target-server as a kind of proxy between the machine which is
"gateway" bewteen the target-network and the compagny network.
The network lookslike this:
[sun/solaris with tornado]--[large compagny network]--
[sun/solaris,controlling targets]--[small network]--[1-30 VxWorks
targetboards]
As said, I thought installing a target server on the controller sun
might function as an appliction proxy between the two networks (for
debugging).
I'm aware that I need a target server for every board I wish to debug.
Cheers,
Renee
--
.
- References:
- Use of target-server in large networks
- From: ReneeTeunissen
- Re: Use of target-server in large networks
- From: LarryC
- Re: Use of target-server in large networks
- From: ReneeTeunissen
- Use of target-server in large networks
- Prev by Date: Can i have two same class IP address in target?
- Next by Date: Re: It it possible to open file inside task?
- Previous by thread: Re: Use of target-server in large networks
- Next by thread: system is restarting in serial port isr
- Index(es):
Relevant Pages
|
