North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: IS-IS reference
KISS - keep things as simple as possible... OSPF is an open protocol, and it's very simple in case if you have not 500 routers and 1000 flapping routes in the network - what do you searching the headache for? Multicast routing depends more from the options you have from the hardware vendor - choose the simplest and more standard method and turn it on... PS. From my lectures to the students, quote: --- The most complex routing method is STATIC - it's easy to implement (for the HW vendor) but most difficult to configure. The simplest routing is just dynamic routing in the plain schema (for example, 'router ospf 1/network 0.0.0.0 255.255.255.255 - just 2 lines for the CISCO, compare to the static' - may be it can argue someone do not use the static at all -:) --- On Mon, 13 Sep 1999, Jack Crowder wrote: > Date: Mon, 13 Sep 1999 11:29:58 -0700 > From: Jack Crowder <[email protected]> > To: [email protected] > Subject: IS-IS reference > > > I was wondering if I could talk with someone who has recently implemented > IS-IS. I'm attempting to move a small NSP away from static routing and > based on their topology - OSPF would have to be configured all in Area 0. > > Since the technology provided by this NSP to their customers will include > multicast services (video specifically), I thought that I should consider > IS-IS while the slate is relatively clean. > > If there is someone who has implemented this routing on their network that > I could ask a few questions of (practical experience), I would appreciate it. > > Jack Crowder > [email protected] > > Aleksei Roudnev, Network Operations Center, Relcom, Moscow (+7 095) 194-19-95 (Network Operations Center Hot Line),(+7 095) 230-41-41, N 13729 (pager) (+7 095) 196-72-12 (Support), (+7 095) 194-33-28 (Fax)
|