TCPIP V5.4 Eco 2

[matthew robey]

After upgrading to VMS V7.3-2 and TCPIP V5.4 Eco 2 the Cluster Alias field (C_ADDR) now has the IP address of the interface.

$tcpip sho int we1/fu

Interface: WE1 IP_Addr: 192.168.AAA.BBB NETWRK: 255.255.255.ZZZ
BRDCST:192.168.XXX.YYY
Cluster
C_Addr: 192.168.AAA.BBB
C_NETWRK: 255.255.255.ZZZ
C_BRDCST: 192.168.XXX.YYY
Ethernet_Addr: 00-08-02-XX-YY-ZZ MTU: 1500

However when you look in the permanent database, the cluster alias is blank.

$tcpip sho conf int we1/fu
(As it is when you @tcpip$config)

Interface: WE1
IP_Addr: 192.168.AAA.BBB
NETWRK: 255.255.255.ZZZ
BRDCST: 192.168.XXX.YYY
C_Addr:
C_NETWRK:
C_BRDCST:

In the HELP it says you can:

$TCPIP set int WE1/NOCLUSTER, however when you do this, the error message states this command is no longer supported.

Whilst this isn't a critical issue, it screws up our noddy network monitor, as it thinks the system now has two network interfaces with the same address.

Matt

NB This feature is on all my standalone systems, and the clusters (which dont have a cluster alias.)

[cbkteam1]

Hi Matt,

Cluster Alias is no longer supported with TCPIP 5.4.. as far as I know.

Regards J.Rudyk

[Volker Halle]

Matthew,

the implementation of the TCPIP CLUSTER alias has changed in V5.4. You are now supposed to configure/delete/manage the cluster alias with the U*X style commands:

$ @SYS$MANAGER:TCPIP$DEFINE_COMMANDS
$ ifconfig -a ! show conf
$ ifconfig xxx alias x.x.x.x/nn ! create alias
$ ifconfig xxx -alias x.x.x.x ! delete alias

As a side-effect of this new implementation, the difference in the output of TCPIP SHOW INT/FULL may be explainable.

Volker.

[Jan van den Ende]

Bwahh!!!

I like solving cryptograms every once in a while, but I HATE to have to do that at work, and I even more HATE to be forced to remember which crytographic flag to use with which command!

Confuse the -a flag for blurp with the same flag for blurb and you may blow your system away. (and of course blurp as well as blurb fullfill functions that bear NO relation to the command name, and the more they look alike, the more different they are, and the more dangerous it is to confuse them :-( )

Can ANY VMS command PLEASE, PLEASE be supplied with VMS syntax??


And even worse, as in this case, REMOVING the existing VMS-style syntax?

Hey, Engeneering, this is

>>>"""Breaking existing code"""<<<

which we have grown to believe to NOT happen in VMS!!!


(of course, also supporting NIX syntax, and M$ syntax as well, for those who operate multy-platform and prefer the same syntax everywhere, is a nice feature, and constitutes VMSsy user-frienliness!)


Cheers.

Have one on me.

Jan