Month: May 2007

How-To Remote NDC

How-To Remote NDC

This is one of those things i learned from the 1-week DNS Training in Cebu. 🙂

1. From the primary DNS,
$ rndc-confgen

2. Cut the first part the of statement to rndc.conf and the second part which has a comment (hash) to named.conf. Make sure to remove the comment starting from the “key” statement before using it.

rndc.conf

# Start of rndc.conf
key "rndc-key" {
algorithm hmac-md5;
secret "Va09oAxfsx45hgo4Q=="; (sample only)
};

options {
default-key "rndc-key";
default-server 127.0.0.1;
default-port 953;
};
# End of rndc.conf

named.conf

# Use with the following in named.conf, adjusting the allow list as needed:
key "rndc-key" {
algorithm hmac-md5;
secret "0zXjzZt0y9ofd6GPH7go4Q==";
};

controls {
inet 127.0.0.1 port 953;
allow { 127.0.0.1; } keys { "rndc-key"; };
};
# End of named.conf

You could also place the second part to a file then use “include” statement in your named.conf to specify that file.
include "/var/named/master/myrndc-key.txt";

3. Test your setup in the primary server, using either of these commands. (You cannot use this in another terminal YET!)
$ rndc -s localhost -c rndc.conf status
$ rndc -s 127.0.0.1 -c rndc.conf status

Note: these other commands may be used as well but for test purposes, just use the status parameter to prevent any unwanted changes to your name server.
rndc -s -c rndc.conf reload | stop | trace | flush

The output should be similar below:
number of zones: 7
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 26/1000
tcp clients: 0/100
server is up and running

4. The ff. steps allow Remote NDC. Edit your named.conf and (1) change 127.0.0.1 to your primary nameserver’s IP address, (2) add your secondary DNS to the allow statement.

controls {
inet 192.168.1.2 port 953
allow { 127.0.0.1; 192.168.1.2; 192.168.1.3; } keys { "rndc-key"; };
};

5. Copy rndc.conf to your secondary DNS.
$ scp rndc.conf :/path/to/var/named/

6. Edit rndc.conf and change the default-server IP to that of your primary nameserver’s.
default-server 192.168.1.2;

7. Test your setup using
$ rndc -s 192.168.1.2 -c rndc.conf status

8. Debugging. Assuming you have the correct key and ip addresses in the config files but still get the ff. error
rndc: connect failed: connection refused
make sure your time is synchronized.
If you have a time server, do the ff. commands and see if the time on both servers are synchronized.
$ ntpdate
$ date

Remote X Dilemmas

Remote X Dilemmas

I was pretty confident i can run all my simulations and layout in this machine.
I have no one to blame though. I simply run one of the programs (nclaunch) and jumped to the conclusion that it can.

So this morning when i ran the other tool, my world fell apart.
> seultra -m=1200 &

Got this error…
***********
CADENCE Program Disaster:
Pseudo color graphics card not detected.
Session aborts.
***********

A little consultation with Google Man carried me to a page with the explanation below.

Solution: You are using a Linux machine. These are not currently equipped graphically to handle Silicon Ensemble. Please use a sun or windows machine.

Jeesh!

Apparently, Cadence tools are 8-bit based. A 24-bit color depth workstation cannot support pseudo color mapping to run these tools at the same time. Thus, i need a video card with a Linux driver to address the 8-bit overlay problem. At least that’s what this forum suggests. Tried with 256 colors for 8-bit display but to no success.

Now what other options do i have but to use two workstations, a Windows-based system for pnr and a Linux desktop for all others. There might be other ways though, but what choice does a poor cramming girl has?

How-To: Windows Time Synchronization

How-To: Windows Time Synchronization

I tried to configure my windows desktop to synchronize with a test NTP server. This should be easy enough. Just go to Date and Time Properties -> Internet Time then check Automatically synchronize… and choose your NTP server. Mine however, flashed an error in synchronizing message.

Seconds after syncing another system with FC6 OS (ntpdate -u), which by the way worked instantly, we figured out the problem’s with my Windows settings. Here’s a quick fix (for personal/future use).

Open a command line and issue the ff. commands:

  1. w32tm /unregister
  2. w32tm /register
  3. net start w32time

If the service is not running, or you get an error trying to manually start Windows Time in the Services Tool, you may need to issue this command.

  • svchost -k netsvcs