Just some general advice / info: TC7 is your mpip server you say. So every arc including itself (TC7) is pointed to TC7 as the server. And every arc has ALL of the other arc's, including the "server" listed as a client. I'll put a complete MPIP setup at the end. NTP is enabled and working on all the arcs? I recommend changing the ospf priorities on all the arc's to 0 so it doesn't get confused and try to become the DR: set ospf interface <ip of box> router_priority 0 MPIP SETUP: When setting up MPIP on the Hiper Arcs you will have to designate one of the Harcs as the server for the group. It will keep track of where all the channels are and who they belong to. The rest of the Harcs, including the one designated as the server will be setup as clients. (It's a client too.) add mpip server <ip_address of server> sharedsecret <somesecret> priority 1 Remember to do this on all the arcs. Keep the sharedsecret the same. On the Harc that is going to be the server, make sure the server state is on set mpip server_state on Now, on each Hiper Arc, including the server you need to add the ip address of all the Hiper Arc's in the group. add mpip client <ip_address> sharedsecret <somesecret> type hiper By default all Hiper Arc's are set to default server_state=off and client_state=on Only the Harc acting as the server will have both server and client state on, else it should be off, on. set NTP primary_server<ip address of NTP server> enable ntp save all NOTE: Daylight Savings Time does not work on the HiPer ARC until version 5.1.99. Verify Setup show mpip settings list mpip servers list mpip clients show ntp settings Todd -----Original Message----- From: usr-tc-admin@mailman.xmission.com [mailto:usr-tc-admin@mailman.xmission.com]On Behalf Of Joshua Coombs Sent: Tuesday, November 26, 2002 10:59 AM To: usr-tc@mailman.xmission.com Subject: [USR-TC] MPIP + OSPF Hell I currently administer a pool of 8 TC1000 chassis, and have been pulling hair out trying to stabilize OSPF. What we are seeing is some TC's refuse to ack some LSA reannouncements from the DR, causing it to eventually drop and restart OSPF sessions at random times. Every now and then this 'corrective' action taken by the DR will trip up a batch of TC's and 5 or 6 will all drop OSPF and reload their sessions. These hiccups are quite noticable to our dual channel ISDN customers (whom also seem to trigger the activity.) Our setup is as follows: 8 TC ARCs, all in the same ospf area (not the backbone) with one addition ospf neighbor, a Cisco router that acts as the DR and ABR to the backbone area. TC7 is the mpip server for the group, all chassis are clients with eachother. Dual channel callers are just as likely to land across chassis as they are to land with both links on one chassis. All callers get subnet/route info, if any (99% just use a single link, and get an ip from the dynamic pool) from ppp, we do not do any routing exchange (OSPF, RIP, BGP, etc) with any customers via dialup. This problem manifested when we turned up ISDN on this network. Before there were no multi-link customers dialing in, and the setup was fairly stable. Since turning up MPIP however, we have multiple ospf session failures a day and our customers are getting quite annoyed with the pauses or unusable connections they cause. Can anyone point me to a good walkthrough on a 'proper' MPIP setup so I can verify that I'm in compliance there, and does anyone have any other suggestions on how to fix this mess? We're currently running 4.5 Joshua Coombs _______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc