RE: OSPF adjacencies [7:57410]

2002-11-14 Thread _ OneZero543 _
I must admit that I only quickly scanned your post the first time and
assumed that the trouble was MTU size.

The IP OSPF MTU-IGNORE command (IOS 12.1(3))is a drastic measure for rare
occasions, but Cisco IOS does not allow changes to the physical MTU size, so
if you did have a mismatch (with IOS 12.0(3) and later) and could not change
the non-cisco device to match the cisco device, your only options would be
to reload an earlier version of the IOS or ignore the MTU size on the cisco
device. This command needs only be on the cisco router interface.

Upon futher investigation of your post and ignoring recent changes you may
have made, such as changing or adding ACL's, NAT, m/f or application
changes, you might want to check the interface types. Your sample debug is
very simular to that of classic point-to-point multicast vs
point-to-multipoint unicast trouble that plagues OSPF ADJ with multiple
routers. DBD's intended for one router are being multicast to all routers.
Solution to this problem - make sure your all your interfaces send unicasts.

I am, of course, speaking of router to router trouble and the above may not
apply, but I am happy to contribute what little I know.



Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=57430t=57410
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: OSPF adjacencies [7:57410]

2002-11-13 Thread _ OneZero543 _
Why Not Try - IP OSPF MTU-IGNORE on the router(s). Don't try matching 4096.
Later


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=57421t=57410
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Must Know..to pass [7:56923]

2002-11-05 Thread _ OneZero543 _
I had TWO tigers and NO gun on mine!


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=56954t=56923
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame Relay [7:56953]

2002-11-05 Thread _ OneZero543 _
Rich,

No, you are not missing anything - NBMA without neighbor statements over
serial links SHOULD not work and in most cases, won't.

Welcome to my world!

Chances are that you experiencing EpisodeOSPF the Phantom neighbor

I have fought this for over 6 months while studying. The dead interval keeps
renewing and the neighbors SEEM to be up, but, if you clear the OSPF process
or reload the routers, the connections should die - even before you reload
the routers the routes should have been unreachable - EXCEPT in the case of
another connection between the routers.

Another OSPF goodie!

If you have an ehternet or other broadcast connection, as well as the NBMA
serial link the little hellos for the NBMA connections piggyback on the
broadcast connection and bring up the neighbors anyway (even if in different
areas! and a traceroute will show a direct connection!)in this case the
neighbors remain after clearing or reloading and are reachable. (This
behavior is probably not OEM design) Just two of many OSPF quirks!

You have the concept! keep your eye on the prize!




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=56956t=56953
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: TEI_ASSIGNED and MULITPLE_FRAME_ESTABLISHED [7:56961]

2002-11-05 Thread _ OneZero543 _
Both are/or could be correct: the following is from CISCO on isdn -

Quote
Status of ISDN Layer 2 with Terminal Endpoint Identifier (TEI) number and
multiframe structure state. The valid TEI number range is 64 to 126. The
most often seen Layer 2 states are MULTIPLE_FRAME_ESTABLISHED and
TEI_ASSIGNED.

A state=MULTIPLE_FRAME_ESTABLISHED indicates there is data link connectivity
to the telco ISDN switch. This is the state that you should see under normal
operations. Any other state usually indicates a problem on the circuit.

A state=TEI_ASSIGNED indicates that the router has lost connectivity to the
switch. This is normal if the telco (commonly in Europe) deactivates Layers
1 and 2 when there are no active calls.

I hope this clears thigs up a bit!


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=56963t=56961
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: TEI_ASSIGNED and MULITPLE_FRAME_ESTABLISHED [7:56961]

2002-11-05 Thread _ OneZero543 _
As for the extra TEI (TEI 0 = invalid state) this may always be present
while waiting to connect - you can visit cisco and read about ISDN
troubleshooting at the following link.

http://www.cisco.com/warp/public/129/bri_sh_isdn_stat.html;


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=56964t=56961
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]