Search results for query: *

Thanks. What I ended up recommending was to create a static route to an unused network and point it to the BRI interface. I pulled the backup statements out of the serial int config and then pinged a host in that network. This brings up the dialer, but doesn't interfere with the other traffic.

Most of our routers are set up with ISDN backup connections which come up when the serial line drops. This is accomplished using the backup statement under the serial interface. Since I can no longer administratively shut the serial link down to force the ISDN to dial out (newer code prevents)...

I agree with tschouten that it is always a good idea to rate limit if you know what normal traffic looks like. I would recommend getting a sniffer on a port to see what is actually occuring. Also, if you have an idea what port you are dealing with, you can run the debug against an ACL to limit...

exec mode is OK for sh mac or sh cam dyn

Spanning tree loop detection is still in operation when portfast is enabled. The port would be set to blocking state if a loop was detected.

Portfast shortens the whole block/listen/learn/forward cycle, but doesn't disable spanning tree. It should be disabled wherever there is a chance of a loop - switches for sure, but servers can also be an issue if they start routing/bridging. I haven't seen it cause any issues with DHCP, but...

For Cat OS, show cam dyn