Stop IP on a decserver

[Wim Van den Wyngaert]

I found a decserver that has IP enabled, DHCP enabled and has received an address (not from me). I want to stop IP without rebooting.
(get message "internet address already set)

Possible ?

Wim

[John Abbott_2]

Hi Wim,

SET (volatile mode)
DEFINE (Permanent)
CHANGE (both)

SET PRIV
CHANGE INTERNET DISABLED

The book says reboot required, but it's worded for all commands SET/DEFINE/CHANGE so SET *might* work in volatile mode (sorry I can't try it out for you).

You can disable DHCP volatile

SET INTERNET DHCP DISABLED

Hope this helps
John.

[Wim Van den Wyngaert]

John,

I tried to disable IP using SET INTERNET address NONE and INTERNET DISABLE. Both said the same (address assigned).

Wim

[John Abbott_2]

I used our spare 90M... you can only use DEFINE INTERNET DISABLE & reboot. In fact, several other SET INTERNET x commands do not work if an IP address already exists.

Out of ideas.

[Wim Van den Wyngaert]

I rebooted a DS700.
List internet shows :
>state disabled
>internet address 0.0.0.0
>subnet mask 0.0.0.0
>dhcp disables

After the boot
>State enabled
>internet address 65.77.0.0
>subnet mask 255.0.0.0
>dhcp disabled

I did (before the boot):
define int add none
define int dhcp disa
define int disa

What did I miss ?

Wim

[John Abbott_2]

Can't see anything unreasonable... just a thought, are there any tcp listener ports ?
SHOW PORT ALL (under services offered, does it say: Listener nnnn) or any reports with a default protocol of TELNET ? Maybe one of these prevented it working.

[Wim Van den Wyngaert]

Removed community : NOK
Disabled SNMP : NOK
Purged TCP/TELNET listeners : NOK
Defined telnet list 23 port cons dis : NOK
Defined telnet list 23 connect dis : NOK

But this last one is strange.

show telnet list 23
shows connections disabled

while
list telnet list 23
shows connections enabled.

(God do I hate decservers)

Wim

[Jan van den Ende]

Wim,

"(God do I hate decservers)"

Should that not be "Do I hate the combination of IP and decservers"?

Proost.

Have one on me.

jpe

[Wim Van den Wyngaert]

Jan : no.

There are a lot of command interfaces on VMS that I don't like.

ucx/tcp (just a mix of everything, everyone had the right to implement it his way))
sda (too complicated)
backup (too messy and complicated)
decserver (idem)
ncl (too complicated to get joined info but I like the consistency)
...

IS ANYONE SEEING "STATE DISABLED" when doing show int on his decserver ?

Wim
(still stuck with IP)

[John Abbott_2]

Hi Wim, I'm out of the office today, but I will try my luck with our spare DS tomorrow lunchtime for you.

Regards
John.

[Wim Van den Wyngaert]

I think I got it. Thank you Google.
I'm using version 2.1.

Incorrect IP address assigned when booting from Flash RAM -- When Network Access Software Version 2.3A or 2.3B boots from Flash RAM on an Access Server unit that has no IP address defined in NVRAM, the
IP address becomes set to a constant and bogus value of 65.77.0.0. It cannot be cleared (i.e. IP disabled), but it can be manually changed to a legal value. This affects DS700, DS900 and AS316 units. DS90TL and DS90M units are not affected. This problem has been fixed in Version 2.3B.01, which is identified on the Access
Server displays as software base level BL49-62a.

[Terry Yeomans]

Wim,
the easiest way is to type
DEF INT MASK NONE
DEF INTER ADDRESS NONE
INIT DELAY 0
This will clear out your internet details and reboot as well (which is needed to complete the job).
Regards Terry.

[Colin Butcher]

http://www.digitalnetworks.net/dr/dnas/3.2/documentation/CG-DNAS0-00.pdf might prove useful.

I think that you're trying to do the impossible. I think that you need to restart the DECserver in order to remove the IP address.

So, use DEFINE and then restart it. You'll want to test that it restarts correctly anyway.

[Wim Van den Wyngaert]

Terry : doesn't work.

Colin : that's what I just found out. But even with reboot it doesn't work.

Wim

[Terry Yeomans]

Wim,
well it's always worked ok for us when we've done typo errors on a server.
The only other option I can think of is to re-initialize the server.
Power cycle the server, then immediately push an object into the hole at the bottom of the server. You will then have a flashing light at the top end of the server, then release.
Hope this isn't an already tried method.
Regards Terry.

[Wim Van den Wyngaert]

Correction on version number.

TSM is version 2.1.

But the terminal server(s) having the problem have 2.3a. I have some with 2.2 and they don't have the problem.

So I guess it is the quoted problem.

Wim

[Wim Van den Wyngaert]

I did a tcp trace and found that nodes that received 65.77.0.0 with dhcp disabled no longer have traffic.

The tcp counters on the decserver confirm this.

However, I do get counter of 1 connection dropped and 1 even 17 connections dropped.
But not increasing. While they don't have IP.

Wim