From: Scott Morris (swm@emanon.com)
Date: Sun Nov 23 2003 - 19:54:24 GMT-3
The explorer wait time is one method of making sure that you wait long
enough (or not) for all stations to respond to the reachability request.
So it's used in conjuntion with load-balancing to be sure you get all
the responses you should be getting. It is not a method of
load-balancing itself.
Otherwise, it is going to depend on your scenario. You can use cost in
the local or remote peer statements. You can use circuit-weight as
well.
If you are talking about where two peers share a common ethernet between
them, you can use the ethernet redundancy (interface command - dlsw
transparent redundancy-enable (mcast-MAC) master-priority (#)) to
determine who the master for that network is. The two peers chat in the
background and figure out who is in control. The lower priority number
wins. Default is 100.
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
CISSP, JNCIS, et al.
IPExpert CCIE Program Manager
IPExpert Sr. Technical Instructor
swm@emanon.com/smorris@ipexpert.net
http://www.ipexpert.net
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Fernando, Emil
Sent: Sunday, November 23, 2003 5:40 PM
To: ccielab@groupstudy.com
Subject: Controlling peer selection
Hi Guys,
I am planning to sit for the lab on coming Friday. I am wondering if
someone can help me to understand selecting a dlsw+
peer over a another one without using Cost. Let me put more details
about this. There are two peers to a same destination and are not
configured with either cost or circuit weight. If I need to prefer one
circuit over the other one. I saw that with explorer-wait-time it can be
done. Can some please explain me how this can be done.
Regards
Emil
This e-mail is privileged and may contain confidential information
intended only for the person(s) named above. If you receive this e-mail
in error, please notify the addressee immediately by telephone or return
e-mail. Although the sender endeavours to maintain a computer virus-free
network, the sender does not warrant that this transmission is
virus-free and will not be liable for any damages resulting from any
virus transmitted.
This archive was generated by hypermail 2.1.4 : Fri Dec 12 2003 - 12:29:16 GMT-3