mutli-homing behavior with primary path disabled in the network.

Anand N Ilkal <anandnilkal@gmail.com> Mon, 22 November 2010 09:58 UTC

DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=S5Fi9jkf7t2onMw6x3no2tCjEFkb7hQQdA9ftvkA6juZv14TKiv0mhvPie69kHujCD XAmkYR39nG/Lwekje1SyRB55D0LDF1JPOZJE9ObMnvg2w2hHy14P3nfZv/Yfofm8/q+b qyBz7G4yxTuJyJXOvJ1xNzdU2ONdgV3v462xc=
MIME-Version: 1.0
Message-ID: <AANLkTim1oV9DWvCSQ_x_3rUaGGN1N8XnczL9f1=a-qkk@mail.gmail.com>
Subject: mutli-homing behavior with primary path disabled in the network.
From: Anand N Ilkal <anandnilkal@gmail.com>
To: tsvwg@ietf.org
Content-Type: multipart/alternative; boundary="001485f777ee6ebf930495a15012"
Precedence: list
Date: Mon, 22 Nov 2010 09:58:45 -0000

Hello,

I have a multi-home association between Node A(IP1, IP2) and Node B(IP3,
IP4). IP1 and IP3 are configured as primary IP's.

A static route is configured between Node A and Node B for IP1 and IP3.
Hence it will always take this path for message exchange.
Now at the intermediate node this route is disabled. Hence no message reach
other end using IP1 and IP3.

It is observed that even HEARTBEAT's are not exchanged between IP1 and IP3.
Since secondary path is available, the messages are
exchanged between IP2 and IP4. in addition to this all message are tried on
the primary path first and then are sent on the secondary path.

1. How long SCTP tries sending message on primary path? or it tries for the
lifetime of the association?
2. How the decision of forbiding primary path is taken? is this the job of
SCTP layer or IP layer beneath it? or it wont take such decision?
3. when is the message exchange is resumed on primary path?


-- 
with regards,
Anand kumar Ilkal

mutli-homing behavior with primary path disabled … Anand N Ilkal