Re: [Planetlab-users] Reporting slice access problems

[Steve M. <sm...@cs...>]

Emil,

1) Every PlanetLab node has a single name in the database.  Periodically
(a couple of times a day maybe) I generate a table showing me various
status items for each node.  When I see that a node is not behaving as
expected I go investigate - since that is driven by the list of nodes
derived from the database my mental map is from database names to
unexpected behaviour.  I generally don't remember DNS aliases or IP
addresses very well, so if you refer to a node by a name other than what's
in the database I have to go look it up in my table.

2) I am familiar with the 'host' command.

steve



On Wed, 21 Jan 2004, Emil Sit wrote:

> > 2) when you tell us the nodes that you cannot login to please tell us the
> > DNS names e.g., planetlab-1.cs.princeton.edu, rather than the IP
> > addresses.  You will often get a faster response because we can tell you
> > right away, for example, that planetlab11.millennium.berkeley.edu does not
> > have its CD-ROM mounted, but matching 169.229.50.89 makes us go search a
> > list of nodes.
>
> Just for clarification, will any equivalent DNS name suffice?
> For example, berkeley3.plab.lcs.mit.edu? Or berkeley3.lists.planet-lab.org?
> Does it have to be planetlab3.millennium.berkeley.edu?  I want to make
> sure that I'll get the fastest response possible if I ever have a
> problem; sometimes I use these aliases in my scripts and they don't
> report the CNAME of the host.
>
> Incidentally, you might find the 'host' command useful:
>
> $ host 169.229.50.89
> 89.50.229.169.IN-ADDR.ARPA domain name pointer planetlab11.Millennium.Berkeley.EDU
>
> And if you have a whole big list of IP addresses, you can relatively
> easily reverse-resolve them using adnsresfilter [*].
>
> [*] http://rpmfind.net/linux/rpm2html/search.php?query=adns
>