Disabling a multiprotocol LAN interface. ifconfig down doesn't work

[Jose Lizcano_2]

Hi folks,

Briefly about the situation:

I've got a LAN interface with IP over ETH and
also CLNS over ETH, not RFC1006 (CLNS over TCP/IP)
Both protocols share the same interface without
interfering each other.

HP10.20 : I can disable the interface by "ifconfig lanX down" and none of the protocols will work. The linkloop command also says nobody is answering from outside. The effect is as if
the lan cable was plugged off.

HP11.0 : The same command "ifconfig down" only works for IP protocol. Either CLNS still works and linkloop also sends ETH frames outside.

tried browsing thru the manuals unsuccessfully.
lanadmin, etc. "ifconfig unplumb" did not work.

Any clue? How can I totally disable the interface? don't mind to disable the
hardware if necessary. But not the land card,
as it has several interfaces and I only wanted to disable one of them.

Cheers,

[Ian Dennison_1]

Jose,

Do you have access to "SAM"? If you highlight the card in the Network Interfaces section and see what Actions are available, it may detect what type of card it is and disable it using the appropriate commands.

Share and Enjoy! Ian

[Tim D Fulford]

have you tried

ifconfig lanX 0.0.0.0

Tim

[Massimo Bianchi]

Hi,
i'm totally ignorant in NSAP and CLNS, but doing a search i found some references to a command

/opt/ots/bin/osistop


sounds like something can help you...

HTH,
Massimo

[Massimo Bianchi]

Hi,
another thought.

If you look at the startup script, you should find which script enable/disable the NSAP/CLNS.

You can check and use that commands.
Massimo

[Suresh Patoria]

Hi,

If u want to totally disable the lan interface than edit the /etc/rc.config.d/netconf file

over there you put the all enntries of lan interfaces equal to 0

this might be help u

[Caesar_3]

Hello!

Maybe you need to check for a patch that
will upgrate the driver for you net card.
This could solve the problem, because the ifconfig lanX down should off the card
and if it's not done then it's some bug.

Caesar

[Jose Lizcano_2]

Hi all,
Thanks to everyone for answering to this issue.

Ian,
There's an option in SAM for disabling the LAN
interface, which has the same effect that the
ifconfig lanX down. The CLNS packets are still
being broadcast outbound.

Tim, Yes, I tried the command unsuccessfully.

Massimo,
This is the output from that command:
host,sys,root # /opt/ots/bin/osistop
This command no longer stops OTS, only OSI services.

host,sys,root #


Suresh,
The netconf is read in boot time, or doing
/sbin/init.d/net start
which launches the ifconfig with the proper
parameters. I tried everything with the ifconfig
command.

Caesar,
We have three different platforms with the same problem, K580, R390 and L2000. The net cards
harware is different in every of them. I don't
believe they all have the same hardware bug.

We are now getting officially help from HP on
the issue, as part of our support contract on
HP-OV and OTS.

Thanks again to everyone for their responses and their time.

Jose

[rick jones]

indeed on 11.x, ifconfig only affects the operation of IP over the interface. it will not affect DLPI applications, or anything else other than IP and ARP. an ifconfig lanN down will only down IP/ARP on an interface. things like linkloop or DLPI will still work through the interface.

now, if you go through and manage to get all subsystems which have bound to an interface to unbind (as does an ifconfig lanN unplumb for IP/ARP) then the driver will still receive some traffic from the NIC - things like broadcasts will still go through.

the only way I know of to completely shut-of any and all possibility of communication through a NIC is to either remove the driver from the kernel, or disconnect the cable.

11.x "thickens" the interface between drivers and ULPs - hence "ifconfig" only doing things with IP and not the driver itself. I suspect that a request to enhance lanadmin to provide a way to shutdown a card will need to be made. Lanadmin is the interface for interfacing with drivers/NICs.

Now, in that vein, one way to effectively terminate all comms through an interface might be to use lanadmin to make the NIC settings completely incompatible with the other end of the cable. If the other end is hardcoded say to 100FD, you might use lanadmin to configure the interface to 10HD. Now, if the other end is set to autoneg and autosense, that method will not be completely effective. The other side will speedsense down to the "right" speed, and even with a duplex mis-match, some traffic can get through.

And for fibre Gigabit cards, you cannot (iirc) force a mismatch to begin with since they only ever do 1000 megabit operation.

[Jose Lizcano_2]

Perhaps my initial question was not totally
explaining the whole thing.
Just a bit clarification: In 10.20 I was needing to get down the lan card because
it is the only way to stop the ES HELLOs broadcasting from the HP system. 10.20 did not
allow to stop OTS once started in boot time.

Upgraded to 11.x and found that this feature
in the lanconfig was removed and that the
OTS still couldn't be stopped.

The vendor now has brought the solution with
the patch PHNE_27889, which added the proper
thing to the platform, having then a otsstop
command. This patch doesn't defaulty come with
HP11.0 and that's why I've been struggling
and wasting long hours. couldn't believe that
a removed feature on 10.20 didn't have its
counterpart on 11.0

Thanks to the people in the forum for your aid.