I'm managing many Homeoffices connected wit h a 836 without any problems. My local provider sometimes has problems with their realms in userid's, so I thought I could create a second dialer interface configured with a different (e.g. call by call) account.
But everytime I do this, the 836 only connects to the last dialer interface. When I set it to shut it never dials the first one. Also changing the accounts from 0 to 1 lets me only dial the second dialer. I've tested it on 12.3T and 12.4T. With, and without CEF and most dialer-watch examples, Everything doensn't work.
thanks for you answer! I've set 0.0.0.0 to dialer 1 with metric 10 and 0.0.0.0 to dialer 0 with metric 20. My thought was that Cisco will router to dialer 0 automatically when dialer 1 changed to down. Disabling the metric will result in a packetloss of 50% because the Cisco wants to send the packets over both lines.
You probably shouldn't bother too much as all existing connections will die anyway when there is a switchover to another dialer. This is because the existing nat translations will be invalid on the other dialer. This also implies that you will be reconnecting using a different IP which is equivalent to a new session when seen from the connected Internethost.
I don't want to use it for 24h disconnects. My first DialUp provider sometimes has problems with his infrastructure and the connections is down for about half an hour. So I want to keep the downtime as short as possible and connect to another one. It's ok if the clients lose their connections for a short time, but I can't dial in (over ISDN) to all customers and activate the second dialer connection.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...