Re: [TCPIP V5.4] Session Disconnects (and DISCONNECT)

From: Matt Muggeridge (Matt.Muggeridge_at_hp.com)
Date: 02/23/04 

Date: Mon, 23 Feb 2004 02:50:48 GMT

You are right, it doesn't appear in our documentation... and subsequently is
not officially supported. I will also be adding this to our requirements.
I tend to use the 'abort' command from time to time, but from your
demonstration, it clearly needs a little more work.

> What does the asterisk indicate. A pending ABORT ?

That is an indication that the address is considered "at home" on that
interface. This is important for failSAFE, whereupon an interface recovers,
it requests that its 'children' also return home.

Matt. 

-- 
-------------------------------------------------------------
OpenVMS TCP/IP Engineering
Enterprise Computing Group
Hewlett-Packard Company
Gold Coast, AUSTRALIA
-------------------------------------------------------------
"Peter 'EPLAN' LANGSTOEGER" <peter@langstoeger.at> wrote in message
news:newscache$akqeth$ak32$1@news.sil.at...
> In article <v5dZb.67309$Wa.21061@news-server.bigpond.net.au>, "Matt
Muggeridge" <Matt.Muggeridge@hp.com> writes:
> >Oh, I should have also mentioned this command, in case it meets your
> >immediate needs:
> >
> >    $ ifconfig ie0 10.10.10.10 abort
> >
> >This will abort all connections to the 10.10.10.10 address on interface
ie0.
>
> It does indeed meet my immediate needs (if it works of course).
> But the enhancements to DISCONNECT are still on my wish list (greater
> flexibility) and if they are there, then this abort becomes obsolete.
>
> btw Where is this documented ? I didn't find it so far.
> If not, is it supported already (and only documentation missing) ?
> Did it already exist in TCPIP V5.3 (ECO ?) ?
>
>
> Now to my first tries:
>
> --------------------------------------------------------------------------
------
> $ ucx ifconfig we0 alias 1.2.3.4
> $ ucx ifconfig -a
> LO0: flags=100c89<UP,LOOPBACK,NOARP,MULTICAST,SIMPLEX,NOCHECKSUM>
>      inet 127.0.0.1 netmask ff000000 ipmtu 4096
>
> TN0: flags=80<NOARP>
>
> TN1: flags=80<NOARP>
>
> WE0: flags=8000c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
>      inet 1.2.3.4 netmask ff000000 broadcast 1.255.255.255 ipmtu 1500
>      inet 192.168.50.81 netmask ffffff00 broadcast 192.168.50.255 ipmtu
1500
>
> $ ucx ifconfig we0 1.2.3.4 abort
> 1.2.3.4: aborting 53 tcp connection(s)
> --------------------------------------------------------------------------
------
> 53 connections ? There wasn't even one existing yet.
> OTOH no connection was disconnected and so it is only a cosmetical
problem.
> --------------------------------------------------------------------------
------
> $ ucx ifconfig -a
> LO0: flags=100c89<UP,LOOPBACK,NOARP,MULTICAST,SIMPLEX,NOCHECKSUM>
>      inet 127.0.0.1 netmask ff000000 ipmtu 4096
>
> TN0: flags=80<NOARP>
>
> TN1: flags=80<NOARP>
>
> WE0: flags=8000c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
>     *inet 1.2.3.4 netmask ff000000 broadcast 1.255.255.255 ipmtu 1500
>      inet 192.168.50.81 netmask ffffff00 broadcast 192.168.50.255 ipmtu
1500
>
> $ ucx ifconfig we0 -alias 1.2.3.4
> --------------------------------------------------------------------------
------
> What does the asterisk indicate. A pending ABORT ?
>
> And now with a connection (to itself via this address) again:
> --------------------------------------------------------------------------
------
> $ ucx ifconfig we0 1.2.3.4 abort
> Unexpected error in status, deleting TCB (QIO).
> Possibly in TIME_WAIT state of 120 seconds for BG device: 0.
> Unable to abort connections for address 1.2.3.4:
> --------------------------------------------------------------------------
------
> OTOH after the 120 seconds passed, this message came and the session
aborted.
>
>
> Means, there is room for improvement but so far seems usable. Thanks for
this.
>
> -- 
> Peter "EPLAN" LANGSTOEGER
> Network and OpenVMS system specialist
> E-mail  peter@langstoeger.at
> A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist

Relevant Pages

  • Re: convincing a client to go with dotNet instead of Access project
    ... That would be good documentation to have... ... > -learning curve for language, APIs, deployment management, etc ... > -Access really tops out with performance after six concurrent connections ... >> I believe a dotNet solution is better, but I'm trying to be as ...
    (microsoft.public.dotnet.general)
  • Re: DC Site Connections
    ... The technet AD design documents seemed a little weak to me. ... DCs and I can see the connections 'to' and 'from' the DCs. ... I have a hub name and a spoke name standard ... Some documentation seems to hint the the KCC will look at the sites, ...
    (microsoft.public.windows.server.active_directory)
  • Re: [TCPIP V5.4] Session Disconnects (and DISCONNECT)
    ... It does indeed meet my immediate needs. ... flexibility) and if they are there, then this abort becomes obsolete. ... $ ucx ifconfig we0 alias 1.2.3.4 ... Unable to abort connections for address 1.2.3.4: ...
    (comp.os.vms)
  • Re: I am sick of windows firewall
    ... or a software firewall panacea. ... It also allows incoming connections to any listening ports - after all, ... And how do you suppose they get documentation? ...
    (comp.security.firewalls)
  • RE: [PHP] Re: Understanding persistent connections with oci8
    ... documentation is misleading here with the intent of the ... Subject: Re: Understanding persistent connections with oci8 ... But what should happen if there are idle connections and the timeout is ...
    (php.general)