isis default

From: polarccie@yahoo.co.uk
Date: Mon Jul 14 2003 - 14:37:06 GMT-3

• Next message: Alvarez, Rolando [NCSUS]: "RE: Creating Tunnel Interfaces"
• Previous message: boby2kusa@hotmail.com: "Re: Creating Tunnel Interfaces"
• Next in thread: Jonathan V Hays: "RE: isis default"
• Maybe reply: Jonathan V Hays: "RE: isis default"
• Maybe reply: asadovnikov@comcast.net: "RE: isis default"
• Maybe reply: R&S Groupstudy: "RE: isis default"
• Maybe reply: Leroy Harvey: "RE: isis default"
• Maybe reply: Robert Laidlaw: "Re: isis default"
• Maybe reply: Peter van Oene: "Re: isis default"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi group...
in a topology like

       r2s0
r1------ -------r3

this is the isis over nbma...
r123 are in the same isis area.
r1-r2 has a l1/l2 neighborship and
r2-r3 has a l1 neighborship...

when i, default-information-originate on r2...
i can not get r3 receive the default...although r1 receives it.

i checked the archieves
tried clns routing on neighboring interfaces,
another isis neighbor for r2 in a different area.still nothing.

thank you.

• Next message: Alvarez, Rolando [NCSUS]: "RE: Creating Tunnel Interfaces"
• Previous message: boby2kusa@hotmail.com: "Re: Creating Tunnel Interfaces"
• Next in thread: Jonathan V Hays: "RE: isis default"
• Maybe reply: Jonathan V Hays: "RE: isis default"
• Maybe reply: asadovnikov@comcast.net: "RE: isis default"
• Maybe reply: R&S Groupstudy: "RE: isis default"
• Maybe reply: Leroy Harvey: "RE: isis default"
• Maybe reply: Robert Laidlaw: "Re: isis default"
• Maybe reply: Peter van Oene: "Re: isis default"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:39 GMT-3