hi all,

This is a veired situation for me. Im having a 7200 with a lot of bri ports. One of 
the ports(BRI 3/4) is shutdown administratively. When I use show config command it 
dosent display the statistics of that port, nor am I able to enter into the interface 
configuration mode (on the global config prompt I used " int bri 3/4 " ), it gives the 
error saying " cannot access ISDN channels ". Im "able" to do the same for all the 
other ports except this one using the same command.

Interesting thing here is I get an output when I say " show int bri 3/4 ". Below is 
the output !!

sh int bri3/4

BRI3/4 is administratively down, line protocol is down
  Hardware is BRI
  Internet address is XXXXXXXXXXX
  MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation PPP, loopback not set
  Keepalive set (10 sec)
  LCP Closed
  Closed: IPCP
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 18
  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
     5 packets input, 520 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
     5 packets output, 520 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions                                               =
     =20

Sounds silly to me.. any bright Ideas ??

Aditya Kedia



_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to