Hey Bob, see below of Cisco's explanation, but essentially you are having BRI0/0 "stay awake" to keep route tables active. Everything is good if this is what you are intending, as we do at my employer.
Routing Once defined, interesting packets must be routed properly for a call to be initiated. The routing process depends on two things: routing table entries and an "up" interface over which to route packets. Interfaces - up/up (spoofing) In order for packets to be routed to and through an interface, that interface must be up/up as seen in a show interfaces output: Montecito# show interfaces ethernet 0 Ethernet0 is up, line protocol is up Hardware is Lance, address is . . . What happens to a dialer interface that is not connected? If protocol is not up and running on the interface, the implication is that the interface itself will not be up. Routes which rely on that interface will be flushed from the routing table, and traffic will not be routed to that interface. The result is that no calls would be initiated by the interface. The solution to counter this possibility is to allow the state up/up (spoofing) for dialer interfaces. Any interface can be configured as a dialer interface. For example, a Serial or Async interface could be made into a dialer by adding the command dialer in-band or dialer dtr to the interface's configuration. These lines are unnecessary for interfaces that are by nature a dialer interface (BRIs and PRIs). The output for a show interface will look like this: Montecito# show interfaces bri 0 BRI0 is up, line protocol is up (spoofing) Hardware is BRI Internet address is . . . In other words, the interface "pretends" to be up/up so that associated routes will remain in force and so that packets can be routed to the interface. There are circumstances under which a dialer interface will not be up/up (spoofing). The show interface output may show the interface as being administratively down: Montecito# show interfaces bri 0 BRI0 is administratively down, line protocol is down Hardware is BRI Internet address is . . . Administratively down merely means that the interface has been configured with the command shutdown. This is the default state of any router interface when the router is booted for the very first time. To remedy this, use the interface configuration command no shutdown. Bob Perez wrote: >PX-VER-DE-RTR#sh int bri0/0 >BRI0/0 is up, line protocol is up (spoofing) > Hardware is PQUICC BRI with U interface > Internet address is 128.121.22.145/30 > MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, > reliability 255/255, txload 1/255, rxload 1/255 > Encapsulation PPP, loopback not set > Last input 00:00:02, output never, output hang never > Last clearing of "show interface" counters 1d00h > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 > Queueing strategy: weighted fair > Output queue: 0/1000/64/0 (size/max total/threshold/drops) > Conversations 0/1/16 (active/max active/max total) > Reserved Conversations 0/0 (allocated/max allocated) > 5 minute input rate 0 bits/sec, 0 packets/sec > 5 minute output rate 0 bits/sec, 0 packets/sec > 18810 packets input, 83842 bytes, 0 no buffer > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > 19653 packets output, 86964 bytes, 0 underruns > 0 output errors, 0 collisions, 0 interface resets > 0 output buffer failures, 0 output buffers swapped out > 3 carrier transitions >EPX-VER-DE-RTR# Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=28098&t=28091 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
