tcp/ip changes

[Dan Martin_1]

When making changes to the tcp/ip network interface, should I use UCX, TCPIP, or the regular system prompt? Would this work?

TCPIP> set configuration interface WE0 /host= /network_mask= /broadcast_mask=

to set the default route:

TCPIP> stop routing
TCPIP> set noroute
TCPIP> set route /default_route /permanent

and how would I set the ethernet duplex parameters?

Thanks,
Dan

[Uwe Zessin]

On first look the commands seem te be OK, but they are just stored in the configuration files.

To make sure that the configuration was successful and correct I suggest you stop and then restart the TCP/IP software or simply reboot the whole system and then verify the changes. This makes sure that they are still valid when the system is doing an unexpected reboot (crash, power cycle).

[Rebecca Putman]

Uwe's suggestion is good; alternatively, if you use @SYS$MANAGER:TCPIP$CONFIG and first stop the TCP/IP network, then use the menus to change things, then restart the network, you won't have to reboot. And, the changes will be permanent, so during a reboot things will be fine.

[Antoniov.]

Hi Dan,
your command shuld work fine without reboot; however as Uwe posted reboot grant you for restart system.
To change ethernet value, AFAIK, you need go into SRM console then reboot system.
Suppose you have EWA0 ethernet device, you can type (at SRM level)
>>> SHOW EWA0*
If I remember, EWA0_MODE is NIC mode (Twin,Fast,etc); to know what write, type
>>> SET EWA0_MODE
system answer with all valid values an then you can type
>>> SET EWA0_MODE

Antonio Vigliotti

[Uwe Zessin]

It is possible to change the ethernet device characteristics via LANCP, but I prefer a direct setup in the SRM console, too.

[Mobeen_1]

Dan,
If you are performing tcpip shutdown and startup, make sure that you are on the console :-)

rgds
Mobeen

[Uwe Zessin]

A DECnet or LAT link will not be disrupted. You could also put the commands into a DCL procedure and run it in a bach job.

[Willem Grooters]

Some word of warning.

Stopping and starting TCPIP when ANY program requiring it is active - think of a webserver and other programs using TCPIP for communications - isn't a good idea. It will cause all open connections to be lost including running Telnet and FTP sessions, and may leave your system littered with (a lot of) BG-devices . In that case you may have to stop and start these servers and programs as well. This may cause other unforeseen problems with these programs!

I would suggest to create a commandprocedure to start TCPIP and related programs (in that order), and one to disable services, shutdown the programs and finally TCPIP (again, in that order) to prevent these problems. To be run (of course) when impact is lowest, and when you are really sure this doesn't interrupt running connections that you need open.

(I must admit, it's a matter of experience ;-))

Willem

[Uwe Zessin]

Agreed, that's why I suggested a nice clean reboot. And while your are at console level, you can change the interface's mode as well ;-)

[Dan Martin_1]

Ladies and Gents,

The feedback is much appreciated and let me know that, after a little research about VMS I was indeed on the right track.

Since this is needed for a server move, I can do everything cleanly with a reboot.

Thanks for the feedback.

Dan