i'm afraid not. MTU is 1500 on every interface.
Nice try though!
-----Original Message-----
From: Kevin Wigle [mailto:[EMAIL PROTECTED]]
Sent: 20 March 2001 16:29
To: McCallum, Robert; 'Ccielab' (E-mail); Cisco@Groupstudy. Com
(E-mail); a bratchell; graham; john bermingham; jolash; kash; martin;
nigel; paul frost; peter norberg; phil
Subject: Re: ISIS / IRB and BVI interfaces
ok, not the exact situation but similar.
We built a circuit that bridges ATM with a LAN extension service.
This required a BVI on the core router. The far end was just another
Ethernet router for all intents and purposes.
Now, I haven't yet touched ISIS or clns - but when we first tried to get
OSPF working across the link it would not form an adjacency. Show ip ospf
neigh revealed EXSTART/DR on the remote router.
On the core router a bridge-group is defined and the ATM sub-interfaced
placed into it.
This immediately set the mtu for the BVI to 4470 bytes - of course we didn't
know that at the time!
On the remote router we observed "debug ip ospf adj" and one of the errors
we saw was words to the effect: "Nbr x.x.x.x has larger interface MTU"
Checked everything, saw the BVI at 4470 and changed it with the command "mtu
1500".
Pop! OSPF formed its adjacency and everything works fine.
Perhaps this is something to look into for your situation.
Kevin Wigle
----- Original Message -----
From: "McCallum, Robert" <[EMAIL PROTECTED]>
To: "'Ccielab' (E-mail)" <[EMAIL PROTECTED]>; "Cisco@Groupstudy. Com
(E-mail)" <[EMAIL PROTECTED]>; "a bratchell" <[EMAIL PROTECTED]>;
"graham" <[EMAIL PROTECTED]>; "john bermingham"
<[EMAIL PROTECTED]>; "jolash" <[EMAIL PROTECTED]>; "kash"
<[EMAIL PROTECTED]>; "martin" <[EMAIL PROTECTED]>; "nigel"
<nigel.p.o'[EMAIL PROTECTED]>; "paul frost" <[EMAIL PROTECTED]>; "peter
norberg" <[EMAIL PROTECTED]>; "phil" <[EMAIL PROTECTED]>
Sent: Tuesday, March 20, 2001 10:39 AM
Subject: ISIS / IRB and BVI interfaces
> Hello,
>
> a little while ago robert devito posted a problem very similar to the one
> that I am now experiencing. At the time I tried to help to fix his
problem
> but I am unsure if Robert got a solution from anyone. I said at the time
> that he was mad to try it but unfortunately now I have to do it for "live"
> work. For those of you who never read Roberts initial problem it is very
> similar to the one below..... please help if you can.
>
>
> 1 router. 1 interface is bridged with clns clients on it. the other
> interface is routed with a isis server.
>
> The solution should be as easy as enabling IRB and to route clns.
Problem.
>
> ISIS tries in vain to establish adjacencies with these clients. It
> constantly sits in the INIT state.
>
> People on the first post wrote back to say try to do bridge irb and maybe
> the circuits aren't t correct etc etc. All of these whilst useful did not
> work as they were already configured properly.
>
> My hunch (and its a scary one), What type of interface is a BVI? We all
> know that ISIS will only operate correctly over a point to point or a
> broadcast network and I reckon this is why no adjacencies will ever form
> over this interface..... does this sound right?
>
> ANY HELP ON THIS WOULD BE MUCH APPRECIATED. THIS IS A NIGHTMARE OF A
> PROBLEM.
>
> Robert McCallum
>
> A bus station is where a bus stops.
> A train station is where a train stops.
> On my desk, I have a work station...
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]