09-12-2013 02:45 AM - edited 03-07-2019 03:26 PM
Hello Community,
Can someone please explain why the BW on Dialer1 is 56 Kbit/Sec, while the Virtual-Access2 (that the Dialer 1 is bound to) has a BW of 448 kbit/s?
uk01340-rm01-ald#conf t
Enter configuration commands, one per line. End with CNTL/Z.
uk01340-rm01-ald(config)#end
uk01340-rm01-ald#show int dial 1
Dialer1 is up, line protocol is up (spoofing)
Hardware is Unknown
Internet address is 80.229.xxx.xx/30
MTU 1500 bytes, BW 56 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 255/255, rxload 255/255
Encapsulation PPP, LCP Closed, loopback not set
Keepalive set (10 sec)
DTR is pulsed for 1 seconds on reset
Interface is bound to Vi2
Last input never, output never, output hang never
Last clearing of "show interface" counters 2d23h
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/0/16 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 42 kilobits/sec
5 minute input rate 672000 bits/sec, 91 packets/sec
5 minute output rate 358000 bits/sec, 62 packets/sec
11406560 packets input, 1877304168 bytes
9925735 packets output, 18446744072806663030 bytes
Bound to:
Virtual-Access2 is up, line protocol is up
Hardware is Virtual Access interface
MTU 1500 bytes, BW 448 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 216/255, rxload 255/255
Encapsulation PPP, LCP Open
Open: IPCP
PPPoATM vaccess, cloned from Dialer1
Vaccess status 0x44
Bound to ATM0/1/0 VCD: 1, VPI: 0, VCI: 38, loopback not set
Keepalive set (10 sec)
DTR is pulsed for 5 seconds on reset
Interface is bound to Di1 (Encapsulation PPP)
Last input 00:00:00, output never, output hang never
Last clearing of "show interface" counters 2d23h
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 672000 bits/sec, 92 packets/sec
5 minute output rate 380000 bits/sec, 89 packets/sec
11429126 packets input, 1875972366 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
9925741 packets output, 3392079954 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
And if I were to monitor the interface, should I monitor the Dialer 1 interface or the Virtual-Access 2 interface?
Cheers
Carlton
09-15-2013 07:59 PM
Carlton
I do not have an authoritative answer, but here is what makes sense to me. Both interfaces are virtual interfaces and therefore do not have any physical implementation from which a realistic and accurate bandwidth can be determined. So Cisco must make a choice about what to use for the interface bandwidth. Dialer interfaces have been around a long time and in their beginning were closely associated with ISDN. So the choice of 56K is appropriate for them. The virtual access interface is much more recent and is not so much associated with any physical interface. So Cisco has chosen a higher value for the bandwidth, which is in keeping with the tendency to use higher and higher capacity media in our networks.
HTH
Rick
09-15-2013 08:30 PM
What is the exact model of this router?
If this is a xDSL router, issue the command "sh atm dsl".
09-19-2013 03:42 AM
Leo,
Sorry for the delayed response.
Please find the information as requested:
uk01340-rm01-ald#show version
Cisco IOS Software, C1900 Software (C1900-UNIVERSALK9-M), Version 15.1(4)M4, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Tue 20-Mar-12 17:58 by prod_rel_team
ROM: System Bootstrap, Version 15.0(1r)M15, RELEASE SOFTWARE (fc1)
uk01340-rm01-ald uptime is 5 days, 19 hours, 46 minutes
System returned to ROM by power-on
System restarted at 15:52:45 BST Fri Sep 13 2013
System image file is "usbflash0:c1900-universalk9-mz.SPA.151-4.M4.bin"
Last reload type: Normal Reload
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
Cisco CISCO1921/K9 (revision 1.0) with 487424K/36864K bytes of memory.
Processor board ID FTX16378390
1 DSL controller
1 Ethernet interface
2 Gigabit Ethernet interfaces
1 ATM interface
1 terminal line
1 Virtual Private Network (VPN) Module
DRAM configuration is 64 bits wide with parity disabled.
255K bytes of non-volatile configuration memory.
249840K bytes of USB Flash usbflash0 (Read/Write)
uk01340-rm01-ald#show atm interface atM 0/1/0
Interface ATM0/1/0:
AAL enabled: AAL5,, Maximum VCs: 4, Current VCCs: 1
VCIs per VPI: 1024,
Max. Datagram Size: 1658
PLIM Type: ADSL - 448Kbps Upstream, DMT, TX clocking: LINE
146173 input, 216668 output, 14275586 IN fast, 11353720 OUT fast
Avail bw = 448
Config. is ACTIVE
uk01340-rm01-ald#
Cheers
09-19-2013 04:09 AM
uk01340-rm01-ald#show atm interface atM 0/1/0
Errrr ... That's not the command I was asking. What is the output to the command "sh atm dsl"? This output will tell you your sychronized speed with your ISP.
09-19-2013 05:37 AM
Hi Leo
I don't have that option:
uk01340-rm01-ald#show atm ?
acircuit ATM Attachment circuit information
arp-server ATM ARP Server Table
async Display ATM Async Interface Information
bundle ATM bundle information
capabilities ATM capabilities
cell-packing ATM cell-packing information
class-links ATM vc-class links
ilmi-configuration Display Top level ILMI
ilmi-status Display ATM Interface ILMI information
interface Interfaces and ATM information
map ATM static mapping
oam ATM oam
pvc ATM PVC information
traffic ATM statistics
vc ATM VC information
vlan Display VLAN to PVC bindings
vp ATM VP information
Carlton
09-19-2013 05:52 AM
Or was it "sh DSL ATM".
Sent from Cisco Technical Support Nintendo App
09-20-2013 04:51 PM
Hi,
Try
show controller vdsl
Regards,
Alex.
Please rate useful posts.
09-20-2013 12:49 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide