We have some older software rev's so I'm not sure what has changed but usually on a fully loaded chassis I will disable NMC chassis awareness and install 2 arcs. I then configure 1 of the arc's to control the even numbered slots and the other to control the odd numbered slots. If we loose an arc I know about it via our monitoring system and can go in and setup the other arc to control the entire chassis and move IP pools, ospf sendpolicies, etc to the working card. This obviously requires some human intervention but rarely do we loose an arc. We have more problems with the DSP's. Todd -----Original Message----- From: usr-tc-admin@mailman.xmission.com [mailto:usr-tc-admin@mailman.xmission.com]On Behalf Of Lewis Bergman Sent: Wednesday, July 31, 2002 10:35 AM To: usr-tc@mailman.xmission.com Subject: Re: [USR-TC] two arcs - Examples On Wednesday 31 July 2002 08:59 am, Stephen Rivera - WRCA.Net wrote:
I have a little info for you guys on this... example of a chassis with 12 quads, 1 DSP, 1 ARC and Netserver...for argument sake.. If I read him correctly, the commands and the sequence isn't the problem. I have found at least 8 examples in the docs and 5 more in the knowledgebase. The question is has anyone used some of these and what was the experience? Is there a reason _NOT_ to use chassis awareness which some of the examples require. Is there a problem with dynamic assignment by the NMC. Does the load balancing really work? How about the redundancy? Do the modems really transfer to the other HiperARC If so how long does the process take? Does one method transfer control quicker than another?
These are some of the questions that come to mind as I try to decide which of the examples to attempt. -- Lewis Bergman Texas Communications 4309 Maple St. Abilene, TX 79602-8044 915-695-6962 ext 115 _______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc