Hi, On Sun, Oct 06, 2013 at 06:08:15PM +0300, M K wrote: > R1#sh run int s0/0.123Building configuration... > Current configuration : 201 bytes!interface Serial0/0.123 multipoint ip > address 192.168.123.1 255.255.255.0 snmp trap link-status frame-relay map ip > 192.168.123.3 103 broadcast frame-relay map ip 192.168.123.2 102 broadcast
Uh. Could you try to get a reasonable mail client? Your mails are just arriving as condensed gibberish, and I'm not going to spend my time trying to work out what the original might have been, only to *then* spend more time trying to answer your question. As for the original question - I assume it has something to do with the NBMA nature of FR and limiting flooding on common interfaces. I'm fairly sure that a search for "OSPF frame-relay example" turns up something useful on cisco.com... like this one... http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094051.shtml title is "Problems with Running OSPF in NBMA and Broadcast Mode over Frame Relay". gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgpR0ZHosRBpz.pgp
Description: PGP signature
_______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
