Max-reserved bandwidth confusion
Hi all,
Can someone please help me to understand bandwidth reservation for CBWFQ.
By default you cannot allocate more than 75% of the interface bandwidth to your classes. My question is what is the point? theoretically it is reserved for your routing protocols etc.etc. but in reality if the interface is saturated isn't that extra 25% used by whatever traffic anyway? it not like you guarantee a maximum of 75%, you guarantee a minimum of 75% so the additional 25% is still up for grabs, it's just that it's not reserved for any class in particular.
hope the question makes sense.
Thanks,
Andres
Hi Andres,
On low speed links, WFQ is the default. So in the case that you have a link with less than 768 kbps, it will be running WFQ. With WFQ, it's not so much 'up for grabs'. WFQ is based on packet size, DSCP values, and time in queue.
Generally, router control packets aren't very large, and by default they are usually in the DSCP 48-64 range, which is very high. So in this case, the control packets are very high priority.
As well, control packets are marked with a special tag on the backplane of most routers (platform specific) to give an even high level of precedence within the router.
When the max-reserved bandwidth is a very high value, it is more likely for the traffic to have a higher interference with these two methods (particularly the first).
hth,
nick
Similar Messages
-
Available bandwindth and 'max-reserved bandwidth'
Is the max-reserved bandwidth only important when working with Qos classes and the bandwidth statement? Is the default 75% available bandwidth only used then?
In other words if I have a 100MB link with a service policy applied for Voice, Call-Control and video. After that I notice the available bandwidth on thie 100MB link is 61280 kilobits/sec.
If I put in a 'max-reserved bandwidth 95' would I reclaim another 20MB of bandwidth for the class-default? Would leaving 5% on the 100MB link for routing and other stuff be acceptable?
Here is the config and show commands:
class-map match-any Call-Control
match ip dscp cs3
match ip dscp af31
class-map match-any Video
match ip dscp af41
class-map match-any Voice
match ip dscp ef
policy-map QOS_classes_to_ACN
class Voice
priority 10000
class Call-Control
bandwidth 500
class Video
bandwidth 3220
class class-default
fair-queue
random-detect
interface FastEthernet6/0
description 100MB Link to ACN
ip address xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx
ip route-cache flow
no ip mroute-cache
load-interval 30
duplex full
speed 100
service-policy output QOS_classes_to_ACN
ROC-RT7206-QMOE#sh int f6/0
FastEthernet6/0 is up, line protocol is up
Hardware is i82543 (Livengood), address is 00b0.4a28.3ca8 (bia 00b0.4a28.3ca8)
Description: 100MB Link to ACN
Internet address is xxx.xxx.xxx.xxx/xx
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 183/255, rxload 21/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:03, output 00:00:00, output hang never
Last clearing of "show interface" counters 01:13:30
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 5211742
Queueing strategy: Class-based queueing
Output queue: 70/1000/64/5211742 (size/max total/threshold/drops)
Conversations 2/35/256 (active/max active/max total)
Reserved Conversations 2/2 (allocated/max allocated)
Available Bandwidth 61280 kilobits/sec <--- Available bandwidth
30 second input rate 8615000 bits/sec, 6860 packets/sec
30 second output rate 71788000 bits/sec, 7484 packets/sec
31692173 packets input, 4263195179 bytes
Received 1204 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog
0 input packets with dribble condition detected
34536300 packets output, 2513155446 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped outHere is the output of show policy-pam int:
ROC-RT7206-QMOE#sh policy-map int f6/0
FastEthernet6/0
Service-policy output: QOS_classes_to_ACN
Class-map: Voice (match-any)
3417571 packets, 934178998 bytes
30 second offered rate 1722000 bps, drop rate 0 bps
Match: ip dscp ef (46)
3417571 packets, 934178998 bytes
30 second rate 1722000 bps
Queueing
Strict Priority
Output Queue: Conversation 264
Bandwidth 10000 (kbps) Burst 250000 (Bytes)
(pkts matched/bytes matched) 1908656/521903140
(total drops/bytes drops) 0/0
Class-map: Call-Control (match-any)
615085 packets, 48926098 bytes
30 second offered rate 84000 bps, drop rate 0 bps
Match: ip dscp cs3 (24)
588857 packets, 47299978 bytes
30 second rate 81000 bps
Match: ip dscp af31 (26)
26228 packets, 1626120 bytes
30 second rate 2000 bps
Queueing
Output Queue: Conversation 265
Bandwidth 500 (kbps) Max Threshold 64 (packets)
(pkts matched/bytes matched) 337953/26882724
(depth/total drops/no-buffer drops) 0/0/0
Class-map: Video (match-any)
146136 packets, 82165408 bytes
30 second offered rate 90000 bps, drop rate 0 bps
Match: ip dscp af41 (34)
146136 packets, 82165408 bytes
30 second rate 90000 bps
Queueing
Output Queue: Conversation 266
Bandwidth 3220 (kbps) Max Threshold 64 (packets)
(pkts matched/bytes matched) 81687/45950190
(depth/total drops/no-buffer drops) 0/0/0
Class-map: class-default (match-any)
35227089 packets, 47492000208 bytes
30 second offered rate 87718000 bps, drop rate 14714000 bps
Match: any
Queueing
Flow Based Fair Queueing
Maximum Number of Hashed Queues 256
(total queued/total drops/no-buffer drops) 0/5171786/0
exponential weight: 9
class Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
0 30181523/39910255774 1297726/1944176143 3893194/5836883998 20 40 1/10
1 0/0 0/0 0/0 22 40 1/10
2 0/0 0/0 0/0 24 40 1/10
3 0/0 0/0 0/0 26 40 1/10
4 0/0 0/0 0/0 28 40 1/10
5 0/0 0/0 0/0 30 40 1/10
6 1213/88749 0/0 0/0 32 40 1/10
7 0/0 0/0 0/0 34 40 1/10
rsvp 0/0 0/0 0/0 36 40 1/10 -
Max-reserved-bandwidth 100% for the interface
According to CCO as following text, the remaining 25 percent of bandwidth is used for overhead, including Layer 2 overhead, control traffic, and best-effort traffic. I want to know why cisco choose 25 percent. why not 30% or 20%?
If I config the max-reserved-bandwidth 100% for the interface, does it will effect the routing protocol? also effect the network conectivity?
thanks for your answer
=======
Usage Guidelines for max-reserved-bandwidth
The sum of all bandwidth allocation on an interface should not exceed 75 percent of the available bandwidth on an interface. The remaining 25 percent of bandwidth is used for overhead, including Layer 2 overhead, control traffic, and best-effort traffic.
If you need to allocate more than 75 percent for RSVP, CBWFQ, LLQ, IP RTP Priority, Frame Relay IP RTP Priority, and Frame Relay PIPQ, you can use the max-reserved-bandwidth command. The percent argument specifies the maximum percentage of the total interface bandwidth that can be used.
If you do use the max-reserved-bandwidth command, make sure that not too much bandwidth is taken away from best-effort and control traffic.
The max-reserved-bandwidth command is intended for use on main interfaces only; it has no effect on virtual circuits (VCs) or ATM permanent virtual circuits (PVCs).Kevin,
this is the wrong group for this question.
Gilles. -
Viewing MAX-reseved-bandwidth on Cisco 7600 router
Hi everybody
I have been searching a command that will shows us the max-reseved bandwidth ( In the context of QOS) on cisco 7600.
I appreciate your help
Thanks
ciscoR1#show version
Cisco IOS Software, c7600rsp72043_rp Software (c7600rsp72043_rp-ADVIPSERVICESK9-M), Version 15.1(3)S5, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Tue 12-Feb-13 13:17 by prod_rel_team
ROM: System Bootstrap, Version 12.2(33r)SRD5, RELEASE SOFTWARE (fc1)
BOOTLDR: Cisco IOS Software, c7600rsp72043_rp Software (c7600rsp72043_rp-ADVIPSERVICESK9-M), Version 15.1(3)S5, RELEASE SOFTWARE (fc2)Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
I'm uncertain, but on a 7600 with 15.x IOS, it's likely QoS is following the HQF changes, and if so, max-reserved-bandwidth has really been deprecated. -
Hello,
I have a site that has a T1 - I need to reserve the bandwidt for all internet traffic to 90% of that T1, while allowing the voice traffic which is on a specific port to use all 100% of the bandwidth. Please advise on to the best way to achieve this.
Any assistance with achieving this would be greatly appreciated.Hello Michael,
This will need to be done with QoS priority with Policing or shaping.
Please follow the next document:
http://brian-kayser.blogspot.com/2010/10/doing-asa-quality-of-service-qos.html
That should do it for you.
Julio -
Hi all,
could someone tell me if it is possible to reserve a precise amount of bandwidth for a given vlan on the Aironet1240AG ? If yes, could someone tell me how ?
Thanks in advanceHi,
It seems that it is not possible to reserve a bandwidth for a specific VLAN. these APs are layer 2 devices with limited capabiltites. -
UCS F port trunking and reserved VSAN confusion
We have an existing UCS infrastructre where all the FI's FC ports are connected to the MDS9513 as one to one connection ( no port channel or trunking) and the FI is working as "end host mode" . We are planning to move some crtical production application to the UCS infrastrcture and becuse of that we would like to use the FC port chanelling and F-port trunking. While reading some documents I found that there are some restriction on UCS for VSAN numbering while using the FI for F-port trunking . As per the following doc http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/cli/config/guide/2.0/b_UCSM_CLI_Configuration_Guide_2_0_chapter_010101.html#concept_5223F7F368524A39AB1A47B9F8BFEC8A
it says donot configure VSAN ID range from 3840 to 4079 . The MDS 9513 is running NX-OS 4.2(3) . Our existing MDS SAN infrstructure already have 2 VSANs with ID number 4000 and 4001 ( Both of these VSANS are usied for some storage replication unrelated to UCS). In the UCS we alreay have 2 VSANS' ( 200 and 201) and are planning to create 2 more ( 300 and 301). My question is if I configure the FI's for F-port truncking/FC port channeling then what will happen to my existing VSAN 4000 and 4001 on the MDS9513 SAN
Thanks
RKIf you are asking how long it will take to enable f-port trunk and how disruptive it will be? It's not lengthy, but, it will cause the link to stop passing traffic and cause SCSI retrys. Your server will know it happened. If your fc multipathing is operating properly there will be no outage.If there are any configuration issues, the link may be down for an extended period, further compounding this disruption in traffic.
You initially asked about two features, f-port trunk and f-port channel. These are seperate features and require different configuration changes. It's best to add one feature at a time, not both in the same configuration change. Each change will be disruptive.
Do one fabric at a time. Ensure the f-port trunk is fully functional before doing the f-port channel, making sure it is functional before starting work on the second fabric.If your multipathing is operating as it should, there will be no outage. If there is any doubt schedule an outage window.
Dave -
Bandwidth allocation | default class|CBWFQ
Hi everybody
Let say we have 100 mig circuit. Max -reserved bandwidth is 100 mig as well. We make following allocations:
Class A
bandwidth 20
Class B
bandwidth 60
Class Default.
1)We did not make any bandwidth allocations for default class. Assuming We are congested ( i.e class A, class B ), What is the maximum bandwidth Class Default can use?
2) Let say we are congested ( classA,classB) but there is no traffic in default class. How will this unused 20 mig will be distributed among these classA and class B?
++++++++++++++++++++++++++++++++++
I am getting confusing answers:
For example:
From one of theblog ( Dont want pick on author so did not quote it)
You'll want to configure a bandwidth command under the class class-default Otherwise, IOS will divide any unallocated bandwidth equally among all classes; this can result in the class-defaulthaving a very small amount of bandwidth.
Cisco QOS Documentation says:
http://www.cisco.com/en/US/docs/ios/qos/command/reference/qos_cr.pdf
From the above link:
The following output from theshow policy-map interfacecommand on serial interface 3/2 shows that 500 kbps of bandwidth is guaranteed for the class
named voice1. The classes named class1 and class2 receive 50 percent and 25 percent of the remaining bandwidth, respectively. Any unallocated bandwidth
is divided proportionally among class1, class2, and any best-effort traffic classes
Which One is true statement?
If Cisco documentation is correct, then what proportion of unallocated bandwidth is given to default class as there is no bandwidth percentage configured under default class.
ThanksDisclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
#2 If there's just traffic for classes A and B, they will proportionally share it 20:60 or 1:3 (or 25%:75%). (NB: the former is assuming they want "more". If not, actual usage might not reflect bandwidth allocation. For example, if class B only used/wanted 50% of link, class A could obtain the other 50%.)
#1 recall finding some blog that really went deep into what class-default gets when you don't explicitly allocate bandwidth. I also recall it may have been IOS version dependent and whether FIFO or FQ was defined in class-default (this also was pre-HQF).
It was very complicated, and IMO, best avoided by defining bandwidth in class-default, if class-default usage, relative to other defined classes, is important to your QoS policy.
Generally, if something isn't clearly documented as expected behavior, I avoid relying on "discovered" actual behavior, because it might change with next IOS release. -
Hi, I had setup a lab in which I had a 2514 router connected to my cable modem for internet access. When i did this, the most I could download through it was about 2Mbps, on the 10Mbps cable line (and 10Mbps AUI port). I was just wondering if this is all due to hardware limitations- being 10BaseT half duplex AUI interface? - or could it be a combination of issues. I dont have the config for the router anymore, just wondering what the most likley cause of only getting about 20% of throughput. I had tried playing with QoS policy maps and max-reserved bandwidth settings, but to no avail.
***Cliffs notes: Should i expect maximum throughput of a 2514 10BaseT ethernet port to be about 2Mbps?The attached documents shows the 2500 series good for only about 2 Mbps with 64 byte packets. I still use a 2501 for TTCP tests which I've seen top out at about 5 Mbps (using the 10 Mbps AUI port).
-
Router Dead , when i applied QOS on virtual-temp interface for vpn !!
hi all ,
i have a simple brief topology below :
PSTN======(R1-7206)>F1=======F2>(R2-7604 catalyst)>>>F1=========Internet
i have two router
R2========>MLS 7604
R1======>cisco 7204
on R2 , Im doing matching to QOS by dscp , im matching acls ips from internet with dscp values :
here is CONFIG for matching :
Gateway7600#sh policy-map LLQX
Policy Map LLQX
Class YOUTUBE
set ip dscp af43
Class FACEBOOKVIDEOS
set ip dscp af33
Class HTTP
set dscp af23
Class DNSQOS
set dscp af13
Class class-default
set ip dscp af11
================
Gateway7600#sh class-map
Class Map match-all FACEBOOKVIDEOS (id 7)
Match access-group name facebookvideos
Class Map match-all DNSQOS (id 8)
Match access-group name dnsqos
Class Map match-all HTTP (id 6)
Match access-group name browsing
Class Map match-any class-default (id 0)
Match any
Class Map match-all YOUTUBE (id 5)
Match access-group name youtube
Gateway7600#
=========================================================
on this router i applied this policy map on interfaxce F1 in direction
and here matching is well :
Gateway7600#sh policy-map interface gigabitEthernet 1/5 in
GigabitEthernet1/5
Service-policy input: LLQX
class-map: rate-limit (match-all)
Match: access-group name rate-limit
police :
4088000 bps 384000 limit 384000 extended limit
Earl in slot 1 :
139044930 bytes
30 second offered rate 143032 bps
aggregate-forwarded 134420937 bytes action: transmit
exceeded 4623993 bytes action: drop
aggregate-forward 22544 bps exceed 0 bps
class-map: YOUTUBE (match-all)
Match: access-group name youtube
set dscp 38:
Earl in slot 1 :
132693939697 bytes
30 second offered rate 212144928 bps
aggregate-forwarded 132693939697 bytes
class-map: FACEBOOKVIDEOS (match-all)
Match: access-group name facebookvideos
set dscp 30:
Earl in slot 1 :
10726758352 bytes
30 second offered rate 20682720 bps
aggregate-forwarded 10726758352 bytes
class-map: HTTP (match-all)
Match: access-group name browsing
set dscp 22:
Earl in slot 1 :
56874058537 bytes
30 second offered rate 92669832 bps
aggregate-forwarded 56874058537 bytes
class-map: DNSQOS (match-all)
Match: access-group name dnsqos
set dscp 14:
Earl in slot 1 :
160308954 bytes
30 second offered rate 303552 bps
aggregate-forwarded 160308954 bytes
class-map: class-default (match-any)
Match: any
set dscp 10:
Earl in slot 1 :
67394864030 bytes
30 second offered rate 126884864 bps
aggregate-forwarded 67394864030 bytes
=================================================================================
now the problem is below
on router 7200 , it is LNS router connected with LAC roiuter for ADSL customers.
now here is config of policy map on 7200 router:
R11#sh policy-map
Policy Map MATCH_MARKS
Class MATCH_YOUTUBE
bandwidth 220000 (kbps)
Class MATCH_FACEBOOKVIDEOS
bandwidth 20000 (kbps)
Class MATCH_HTTP
bandwidth 100000 (kbps)
=========================================================
R1#sh class-map
Class Map match-all MATCH_FACEBOOKVIDEOS (id 2)
Match ip dscp af33 (30)
Class Map match-all MATCH_HTTP (id 3)
Match ip dscp af23 (22)
Class Map match-any class-default (id 0)
Match any
Class Map match-all MATCH_YOUTUBE (id 1)
Match ip dscp af43 (38)
==========================================================
here is virtual-template interface before i apply the QOS
R1#sh running-config interface virtual-template 1
Building configuration...
Current configuration : 352 bytes
interface Virtual-Template1
bandwidth 1000000
ip unnumbered Loopback0
ip tcp adjust-mss 1412
ip policy route-map private
no logging event link-status
qos pre-classify
peer default ip address pool bitsead1 bitsead2
ppp mtu adaptive
ppp authentication pap vpdn
ppp authorization vpdn
ppp accounting vpdn
max-reserved-bandwidth 90
end
=========================================
when i apply the command
(service-poliy output MATCH_MAKRS ) under virtual-template interface i have console logs :
Insufficient bandwidth 149760 kbps for the bandwidth guarantee (220000)
Insufficient bandwidth 149760 kbps for the bandwidth guarantee (220000)
Insufficient bandwidth 149760 kbps for the bandwidth guarantee (220000)
also i have
*Jul 9 22:28:38.242: Interface Virtual-Access2551 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 9 22:28:38.250: Interface Virtual-Access627 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 9 22:28:38.258: Interface Virtual-Access786 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 9 22:28:38.266: Interface Virtual-Access623 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 9 22:28:38.274: Interface Virtual-Access2559 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 9 22:28:38.282: Interface Virtual-Access2281 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 9 22:28:38.290: Interface Virtual-Access142 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 9 22:28:40.262: %SYS-2-INTSCHED: 'suspend' at level 3 -Process= "VTEMPLATE Background Mgr", ipl= 3, pid= 278, -Traceback= 0x756FF0z 0x3439C58z 0x2778D70z 0x2CACCD0z 0x2CC63E0z 0x2CC7FF8z 0x2CADC74z 0x2CBE058z 0x2CA0340z 0x2CA04F8z 0x2E0BB18z 0x2D23378z 0x2D1825Cz 0x2D18738z 0x2E66FE0z 0x2D971ACz
*Jul 9 22:28:40.262: %SYS-2-INTSCHED: 'suspend' at level 3 -Process= "VTEMPLATE Background Mgr", ipl= 3, pid= 278, -Traceback= 0x756FF0z 0x3439C58z 0x2778D70z 0x2CACD28z 0x2CC63E0z 0x2CC7FF8z 0x2CADC74z 0x2CBE058z 0x2CA0340z 0x2CA04F8z 0x2E0BB18z 0x2D23378z 0x2D1825Cz 0x2D18738z 0x2E66FE0z 0x2D971ACz
after i apply it ,
the cpu is 100 % and the router got down !!!
now
what is the problem ????
here is ios for 7200 router
R1#sh version
Cisco IOS Software, 7200 Software (C7200P-ADVENTERPRISEK9-M), Version 12.4(24)T7, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Tue 28-Feb-12 12:53 by prod_rel_team
ROM: System Bootstrap, Version 12.4(12.2r)T, RELEASE SOFTWARE (fc1)
Bras1 uptime is 13 weeks, 1 day, 9 hours, 24 minutes
System returned to ROM by reload at 16:24:51 GMT+3 Tue Jun 17 2003
System image file is "disk2:c7200p-adventerprisek9-mz.124-24.T7.bin"
Last reload reason: Reload Command
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
[email protected].
Cisco 7206VXR (NPE-G2) processor (revision A) with 917504K/65536K bytes of memory.
Processor board ID 36858624
MPC7448 CPU at 1666Mhz, Implementation 0, Rev 2.2
6 slot VXR midplane, Version 2.11
Last reset from power-on
PCI bus mb1 (Slots 1, 3 and 5) has a capacity of 600 bandwidth points.
Current configuration on bus mb1 has a total of 0 bandwidth points.
This configuration is within the PCI bus capacity and is supported.
PCI bus mb2 (Slots 2, 4 and 6) has a capacity of 600 bandwidth points.
Current configuration on bus mb2 has a total of 0 bandwidth points.
This configuration is within the PCI bus capacity and is supported.
Please refer to the following document "Cisco 7200 Series Port Adaptor
Hardware Configuration Guidelines" on Cisco.com <http://www.cisco.com>
for c7200 bandwidth points oversubscription and usage guidelines.
1 FastEthernet interface
3 Gigabit Ethernet interfaces
2045K bytes of NVRAM.
250880K bytes of ATA PCMCIA card at slot 2 (Sector size 512 bytes).
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
==============================================================================
wish to Help ASAP
regardshi ,
i did
the same issue ,
i did a TEST policymap that has 30 percent gurantee
but the same result!!!!!!!!!!!!!!!!
the router god down agian !
here is logs :
take effect on the queueing features configured via service-policy
*Jul 11 02:40:33.605: Interface Virtual-Access1896 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:33.797: Interface Virtual-Access1317 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:33.809: Interface Virtual-Access993 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:33.817: Interface Virtual-Access1699 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:33.981: Interface Virtual-Access254 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:33.993: Interface Virtual-Access687 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.001: Interface Virtual-Access35 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.009: Interface Virtual-Access160 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.017: Interface Virtual-Access1337 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.029: Interface Virtual-Access1670 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.037: Interface Virtual-Access1948 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.049: Interface Virtual-Access1669 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.109: Interface Virtual-Access1334 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.117: Interface Virtual-Access151 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.125: Interface Virtual-Access761 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.137: Interface Virtual-Access810 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.197: Interface Virtual-Access1522 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.237: Interface Virtual-Access1692 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.257: Interface Virtual-Access368 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.305: Interface Virtual-Access1758 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.317: Interface Virtual-Access2061 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.325: Interface Virtual-Access1203 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.337: Interface Virtual-Access188 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.345: Interface Virtual-Access1975 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.357: Interface Virtual-Access1172 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.509: Interface Virtual-Access1647 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.517: Interface Virtual-Access458 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.609: Interface Virtual-Access608 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.621: Interface Virtual-Access2128 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.633: Interface Virtual-Access1167 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.641: Interface Virtual-Access487 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.653: Interface Virtual-Access1793 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.665: Interface Virtual-Access2280 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.769: Interface Virtual-Access839 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.781: Interface Virtual-Access2311 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.793: Interface Virtual-Access1788 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.857: Interface Virtual-Access8 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.869: Interface Virtual-Access2243 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:34.881: Interface Virtual-Access580 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:35.057: Interface Virtual-Access6 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:35.065: Interface Virtual-Access1331 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:35.077: Interface Virtual-Access1235 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:35.177: Interface Virtual-Access1748 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:35.189: Interface Virtual-Access2262 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Jul 11 02:40:35.205: Interface Virtual-Access2136 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
i want to ask a question , could this be from IOS ???? -
Router Crashes after entering "show run" or similar commands
Hello,
Im having a problem with my Company router C3845-ADVSECURITYK9-M, software Version 15.1(4)M. After i issue "show run" it tends to crash in middle of output, router restarts itself to be precise....same thing happened when i tried "show stack" afterwards, it happened several times when trying to show running config, so im guessing it has some problem when trying to display large outputs...i have never heard of such thing though so im asking for advice,
These are some informations i gathered:
show version:....
System returned to ROM by error - a Software forced crash, PC 0x60AD4710 at 14:10:56 CET-SUM Wed Aug 13 2014
xxxx#sh env
SYS PS1 is present.
Fan status: Normal
Input Voltage status: Normal
DC Output Voltage status: Normal
Type: AC
Thermal status: Normal
SYS PS2 is absent.
AUX(-48V) PS1 is absent.
AUX(-48V) PS2 is absent.
Fan 1 OK
Fan 2 OK
Fan 3 OK
Fan Speed Setting: Normal
Alert settings:
Intake temperature warning: Enabled, Threshold: 55
Core temperature warning: Enabled, Threshold: 70 (CPU: 90)
Board Temperature: Normal
Internal-ambient temperature = 38, Normal
CPU temperature = 50, Normal
Intake temperature = 32, Normal
Backplane temperature = 29, Normal
Voltage 1(3300) is Normal, Current voltage = 3284 mV
Voltage 2(5150) is Normal, Current voltage = 5153 mV
Voltage 3(2500) is Normal, Current voltage = 2525 mV
Voltage 4(1200) is Normal, Current voltage = 1203 mV
xxxx#sh logg
Syslog logging: enabled (0 messages dropped, 120 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
No Active Message Discriminator.
No Inactive Message Discriminator.
Console logging: level debugging, 62 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 178 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled
No active filter modules.
Trap logging: level informational, 181 message lines logged
Logging to 10.254.0.49 (udp port 514, audit disabled,
link up),
181 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 10.254.8.44 (udp port 514, audit disabled,
link up),
181 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Log Buffer (1000000 bytes):
*Aug 13 12:33:24.867: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0 State changed to: Initialized
*Aug 13 12:33:24.871: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0 State changed to: Enabled
*Aug 13 12:33:25.635: %LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to reset
*Aug 13 12:33:25.635: %LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state to reset
*Aug 13 12:33:25.927: %LINEPROTO-5-UPDOWN: Line protocol on Interface Onboard VPN, changed state to up
*Aug 13 12:33:26.635: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up
*Aug 13 12:33:26.635: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*Aug 13 12:33:27.787: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
*Aug 13 12:33:27.787: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Aug 13 13:33:29.023: %SYS-6-CLOCKUPDATE: System clock has been updated from 12:33:29 UTC Wed Aug 13 2014 to 13:33:29 MET Wed Aug 13 2014, configured from console by console.
*Aug 13 14:33:29.023: %SYS-6-CLOCKUPDATE: System clock has been updated from 13:33:29 MET Wed Aug 13 2014 to 14:33:29 CET-SUM Wed Aug 13 2014, configured from console by console.
*Aug 13 14:33:30.471: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:0, changed state to down
*Aug 13 14:33:30.471: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:1, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:2, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:3, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:4, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:5, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:6, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:7, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:8, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:9, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:10, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:11, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:12, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:13, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:14, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:16, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:17, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:18, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:19, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:20, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:21, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:22, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:23, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:24, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:25, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:26, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:27, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:28, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:29, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:30, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:15, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:0, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:1, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:2, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:3, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:4, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:5, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:6, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:7, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:8, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:9, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:10, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:11, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:12, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:13, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:14, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:16, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:17, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:18, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:19, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:20, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:21, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:22, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:23, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:24, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:25, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:26, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:27, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:28, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:29, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:30, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:15, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:0, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:1, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:2, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:3, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:4, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:5, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:6, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:7, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:8, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:9, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:10, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:11, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:12, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:13, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:14, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:16, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:17, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:18, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:19, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:20, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:21, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:22, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:23, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:24, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:25, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:26, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:27, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:28, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:29, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:30, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:15, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:0, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:1, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:2, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:3, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:4, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:5, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:6, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:7, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:8, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:9, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:10, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:11, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:12, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:13, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:14, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:16, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:17, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:18, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:19, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:20, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:21, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:22, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:23, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:24, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:25, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:26, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:27, changed state to down
*Aug 13 14:33:30.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:28, changed state to down
*Aug 13 14:33:30.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:29, changed state to down
*Aug 13 14:33:30.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:30, changed state to down
*Aug 13 14:33:30.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:15, changed state to down
*Aug 13 14:33:30.731: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up
*Aug 13 14:33:31.535: %LINK-3-UPDOWN: Interface Serial0/1/0:1, changed state to down
*Aug 13 14:33:31.795: %LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to reset
*Aug 13 14:33:31.999: %LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state to reset
*Aug 13 14:33:32.599: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:1, changed state to down
*Aug 13 14:33:32.799: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to down
*Aug 13 14:33:32.999: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
*Aug 13 14:33:34.811: %QOS_CLI_DEPRECATE-4-MAX_RESERVED_BW: max-reserved-bandwidth on interface has been deprecated. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
*Aug 13 14:33:34.815: Interface Serial0/1/0:1 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Aug 13 14:33:35.795: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
*Aug 13 14:33:35.795: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Aug 13 14:33:36.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up
*Aug 13 14:33:36.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*Aug 13 14:33:36.811: %LINK-5-CHANGED: Interface Serial0/1/0:1, changed state to administratively down
*Aug 13 14:33:37.419: %LINK-5-CHANGED: Interface Dialer1, changed state to administratively down
*Aug 13 14:33:38.055: %SYS-5-CONFIG_I: Configured from memory by console
*Aug 13 14:33:38.491: %SYS-5-RESTART: System restarted --
Cisco IOS Software, 3800 Software (C3845-ADVSECURITYK9-M), Version 15.1(4)M, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 24-Mar-11 17:29 by prod_rel_team
*Aug 13 14:33:38.495: %SNMP-5-COLDSTART: SNMP agent on host xxxx is undergoing a cold start
*Aug 13 14:33:38.519: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Aug 13 14:33:38.699: %SYS-6-BOOTTIME: Time taken to reboot after reload = 158 seconds
*Aug 13 14:33:38.859: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
*Aug 13 14:33:38.867: %CONTROLLER-5-UPDOWN: Controller E1 0/0/1, changed state to up
*Aug 13 14:33:38.875: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Aug 13 14:33:38.875: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Aug 13 14:33:38.879: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Aug 13 14:33:38.879: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*Aug 13 14:33:38.879: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is ON
*Aug 13 14:33:38.896: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up
*Aug 13 14:33:39.140: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.254.0.49 port 514 started - CLI initiated
*Aug 13 14:33:39.140: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.254.8.44 port 514 started - CLI initiated
*Aug 13 14:33:40.860: %LINK-3-UPDOWN: Interface Serial0/0/0:15, changed state to up
*Aug 13 14:33:40.868: %LINK-3-UPDOWN: Interface Serial0/0/1:15, changed state to up
*Aug 13 14:33:40.884: %LINK-3-UPDOWN: Interface Serial1/0:15, changed state to up
*Aug 13 14:33:41.684: %CSM-5-PRI: add PRI at 0/0/1:15 (index 0)
*Aug 13 14:33:41.688: %CSM-5-PRI: add PRI at 0/0/0:15 (index 1)
*Aug 13 14:33:51.648: %CSM-5-PRI: add PRI at 1/0:15 (index 2)
*Aug 13 14:34:14.956: %HSRP-5-STATECHANGE: GigabitEthernet0/0.400 Grp 0 state Standby -> Active
*Aug 13 14:34:15.164: %HSRP-5-STATECHANGE: GigabitEthernet0/0.400 Grp 2 state Standby -> Active
*Aug 13 14:34:15.484: %HSRP-5-STATECHANGE: GigabitEthernet0/0.400 Grp 3 state Standby -> Active
*Aug 13 14:34:21.600: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.85.212 on GigabitEthernet0/1.86 from LOADING to FULL, Loading Done
*Aug 13 14:34:27.728: %HSRP-5-STATECHANGE: GigabitEthernet0/0.400 Grp 4 state Standby -> Active
*Aug 13 14:20:02.780: %SYS-5-PRIV_AUTH_FAIL: Authentication to privilege level 15 failed by xxxx on vty0 (xxxx)
*Aug 13 14:21:50.405: %SYS-5-CONFIG_I: Configured from console by av-vilenko on vty0 (xxxx)i made some changes, but nothing that would or could cause this. And besides according to my collegues its not a recent problem (before i joined the company), it goes back at least a year or more...but ofc. since router is working fine untill you try to show the config noone bothered to resolve the issue they just kept their hands off it -.-
-
Upgrading from 12.x to 15.x on 2800
Hello we have a 2800 appliance, and we'd like to upgrade from this IOS version:
c2800nm-adventerprisek9_sna-mz.124-15.T17.bin
To this one from 15.x, c2800nm-advsecurityk9-mz.151-4.M7.bin.
Is there any license we'd need to install to be able to do this ? I fear that maybe if we upgrade, the 2800 is going to have temporary licenses for 60 Days in version 15.x
Regards.You should be able to upgrade with no issue. The only caveat that I ran into was that qos policies are calculated differently than with 12.4. It no longer uses max-reserved-bandwidth, and you have to put your bandwidth statement in the class default if you're nesting policies.
HTH,
John
*** Please rate all useful posts *** -
WRR QoS unused traffic classes
We are planning QoS for the enterprise LAN and MPLS core. At present, there are 5 traffic classes identified and no VoIP traffic. We could allocate resources and bandwidth for 5 queues and deploy such configs. But I guess it's worth defining all 8 classes and allocate queue limits and bandwidth to them. Later it will be easier to mark the new traffic and classify it into the unused queues without modifying the wrr config.
67xx 1p7q8t line card
Q3 and Q8(PQ) will not be used. 5+15% is allocated to them.
priority-queue queue-limit 15
wrr-queue queue-limit 30 15 5 10 15 5 5
wrr-queue bandwidth percent 30 15 5 10 15 5 5
I'm not sure if the allocated bandwidth and queue limit for the unused queues will affect the existing traffic and limit the aggregated traffic quantity. Will the 5 classes be able to fill the bandwidth until there is no congestion? What happens in case of congestion? Can the traffic excess 80% or not? (For simplicity, 100% is regarded as a fraction of link capacity defined by max-reserved-bandwidth)Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Generally, unless you're shaping or policing, bandwidth sharing commands provide a minimum bandwidth guarantee, and unused bandwidth can be used by other queues. Also when working with more than one queue, relative ratios are usually preserved. So, for instance, if q1 was configured for 25%, q2 for 25% and q3 for 50%, if q2 had no traffic, and q1 and q3 wanted all they could have, they would split the bandwidth 1:2 or 1/3 to 2/3. -
I have a 7204 core router with two uplinks. Initially, the one uplink was a singular uplink via PPPoE so we built our outbound NAT translations on it as well as our VPN sessions.
As of today, we have two links. The second link has much less bandwidth and is only setup as a backup link. What we have setup is as follows:
ip sla monitor 100
type echo protocol ipIcmpEcho <**HOST ON END OF PPPoE LINK**> source-interface Dialer1
timeout 1000
threshold 100
frequency 30
ip sla monitor schedule 100 life forever start-time now
track 100 rtr 100 reachability
interface FastEthernet1/0.110
description Link to BackupLink
encapsulation dot1Q 110
ip address <**STATIC_IP_ISSUED_BY_UPSTREAM**> 255.255.255.0
ip nat outside
ip virtual-reassembly
interface Dialer1
bandwidth 30000
ip address negotiated
ip access-group WAN-InboundACL in
no ip redirects
ip mtu 1492
ip flow ingress
ip flow egress
ip nat outside
ip virtual-reassembly
encapsulation ppp
load-interval 30
dialer pool 1
dialer-group 1
no cdp enable
ppp authentication pap callin
ppp pap sent-username <**PPPoE_USERNAME**> password 7 <**PPPoE_PASSWORD**>
crypto map RemoteAccessVPN
max-reserved-bandwidth 90
service-policy output QoS_Outbound
ip route 0.0.0.0 0.0.0.0 Dialer1 track 100
ip route 0.0.0.0 0.0.0.0 FastEthernet1/0.110 100
ip nat inside source route-map OutboundNatBackup interface FastEthernet1/0.110 overload
ip nat inside source route-map OutboundNat interface Dialer1 overload
ip access-list extended VPN_Selector
remark ACL for VPN
permit ip 192.168.80.0 0.0.3.255 192.168.5.0 0.0.0.255
ip access-list extended OutBoundACL
permit ip 192.168.80.0 0.0.15.255 any
route-map OutboundNatBackup deny 20
match ip address VPN_Selector
route-map OutboundNatBackup permit 990
match ip address OutBoundACL
match interface FastEthernet1/0.110
route-map OutboundNat deny 20
match ip address VPN_Selector
route-map OutboundNat permit 990
match ip address OutBoundACL
As you can see we have the primary link monitored and it will flip the default route if the primary link's monitoring goes down to the far end (I know i can do this with an "event manager applet" however I am looking to just get the simple things working). I am wondering if, since I have the second link, do I need to match on the dialer interface on the old route-map OutboundNAT for each entry? Also, any ideas as to what to do to make the VPNs come up across the new link. I am guessing I setup a second crypto peer on the far end but how do I set this end to only have the VPN up on the primary path unless the primary path is down?I have a 7204 core router with two uplinks. Initially, the one uplink was a singular uplink via PPPoE so we built our outbound NAT translations on it as well as our VPN sessions.
As of today, we have two links. The second link has much less bandwidth and is only setup as a backup link. What we have setup is as follows:
ip sla monitor 100
type echo protocol ipIcmpEcho <**HOST ON END OF PPPoE LINK**> source-interface Dialer1
timeout 1000
threshold 100
frequency 30
ip sla monitor schedule 100 life forever start-time now
track 100 rtr 100 reachability
interface FastEthernet1/0.110
description Link to BackupLink
encapsulation dot1Q 110
ip address <**STATIC_IP_ISSUED_BY_UPSTREAM**> 255.255.255.0
ip nat outside
ip virtual-reassembly
interface Dialer1
bandwidth 30000
ip address negotiated
ip access-group WAN-InboundACL in
no ip redirects
ip mtu 1492
ip flow ingress
ip flow egress
ip nat outside
ip virtual-reassembly
encapsulation ppp
load-interval 30
dialer pool 1
dialer-group 1
no cdp enable
ppp authentication pap callin
ppp pap sent-username <**PPPoE_USERNAME**> password 7 <**PPPoE_PASSWORD**>
crypto map RemoteAccessVPN
max-reserved-bandwidth 90
service-policy output QoS_Outbound
ip route 0.0.0.0 0.0.0.0 Dialer1 track 100
ip route 0.0.0.0 0.0.0.0 FastEthernet1/0.110 100
ip nat inside source route-map OutboundNatBackup interface FastEthernet1/0.110 overload
ip nat inside source route-map OutboundNat interface Dialer1 overload
ip access-list extended VPN_Selector
remark ACL for VPN
permit ip 192.168.80.0 0.0.3.255 192.168.5.0 0.0.0.255
ip access-list extended OutBoundACL
permit ip 192.168.80.0 0.0.15.255 any
route-map OutboundNatBackup deny 20
match ip address VPN_Selector
route-map OutboundNatBackup permit 990
match ip address OutBoundACL
match interface FastEthernet1/0.110
route-map OutboundNat deny 20
match ip address VPN_Selector
route-map OutboundNat permit 990
match ip address OutBoundACL
As you can see we have the primary link monitored and it will flip the default route if the primary link's monitoring goes down to the far end (I know i can do this with an "event manager applet" however I am looking to just get the simple things working). I am wondering if, since I have the second link, do I need to match on the dialer interface on the old route-map OutboundNAT for each entry? Also, any ideas as to what to do to make the VPNs come up across the new link. I am guessing I setup a second crypto peer on the far end but how do I set this end to only have the VPN up on the primary path unless the primary path is down? -
Sh policy-map LLQ counters showing strange results.
I've config'd LLQ for video conferencing across a dual-T1 multilink connection. When I have a video conf. session going, the Class-map counters for 'packets', 'match' and 'pkts matched' under queueing being exactly the same. This is supposed to show either that all packets are being processed switched - which they aren't, or that there is congestion on the link, but there isn't. There is nothing else going across the link except my telnet session I use to get the counters. I would have expected all counters, except Class-default, to be zero under the queueing area, and then when I flood the link with large file transfers, the other class queueing counters to begin incrementing - but all counters are equal even without congestion. This doesn't help me prove that my QOS LLQ is working properly. What gives?
Here is the config and some outputs:
policy-map WAN-multilink
class Voice
priority 90
class Video
bandwidth 460
class Call-Control
bandwidth 27
class class-default
fair-queue
random-detect
policy-map QOS_classes
class Voice
priority 90
class Video
bandwidth 460
class Call-Control
bandwidth 27
class class-default
fair-queue
interface Multilink1
ppp multilink
ppp multilink fragment delay 20
ppp multilink interleave
ppp multilink group 1
max-reserved-bandwidth 95
service-policy output WAN-multilink
interface Serial0/2/0
bandwidth 1536
encapsulation ppp
no fair-queue
service-module t1 timeslots 1-24
ppp multilink
ppp multilink group 1
max-reserved-bandwidth 95
interface Serial0/3/0
bandwidth 1536
encapsulation ppp
no fair-queue
service-module t1 timeslots 1-24
ppp multilink
ppp multilink group 1
max-reserved-bandwidth 95
MDF-VoIP-RT2811#sh int stats
Multilink1
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 2175 179609 2436 237735
Route cache 7519 3809321 7416 2108198
Total 9694 3988930 9852 2345933
MDF-VoIP-RT2811#sh policy-map int mu 1
Multilink1
Service-policy output: WAN-multilink
Class-map: Voice (match-any)
2037 packets, 411126 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip dscp ef (46)
2037 packets, 411126 bytes
5 minute rate 0 bps
Queueing
Strict Priority
Output Queue: Conversation 264
Bandwidth 90 (kbps) Burst 2250 (Bytes)
(pkts matched/bytes matched) 2037/411126
(total drops/bytes drops) 0/0
Class-map: Video (match-any)
1919 packets, 1087702 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip dscp af41 (34)
1919 packets, 1087702 bytes
5 minute rate 0 bps
Match: ip precedence 4
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
Output Queue: Conversation 265
Bandwidth 460 (kbps) Max Threshold 64 (packets)
(pkts matched/bytes matched) 1919/1087702
(depth/total drops/no-buffer drops) 0/0/0
Class-map: Call-Control (match-any)
430 packets, 31418 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip dscp cs3 (24)
430 packets, 31418 bytes
5 minute rate 0 bps
Match: ip precedence 3
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
Output Queue: Conversation 266
Bandwidth 27 (kbps) Max Threshold 64 (packets)
(pkts matched/bytes matched) 430/31418
(depth/total drops/no-buffer drops) 0/0/0
Class-map: class-default (match-any)
4669 packets, 612771 bytes
5 minute offered rate 3000 bps, drop rate 0 bps
Match: any
Queueing
Flow Based Fair Queueing
Maximum Number of Hashed Queues 256
(total queued/total drops/no-buffer drops) 0/0/0
exponential weight: 9In accordance with the above, you would need to apply the policy to the subinterface.
As my collegue clearly depicts, you should be able to combine the two pvc's into one, that would also be the scenario where the policy comes in action. When you are sending voice over a dedicated pvc there is little need to prioritize the flow. This equals the configuration where you have a dedicated leased line for voice.
regards,
Leo
Maybe you are looking for
-
iPad1 can not install software 4.3.2 update - message - due to corrupt backup - but when I go to delete backup there is no backup in the device section of itunes under preferences
-
How to re-register my ipod to my computer
so my friend gave me his ipod (he deleted all his songs before giving it to me) and i want to put music on it. when i plug it in itunes recognizes the ipod but i can not transfer music to it. i tried checking off the manually manage music button and
-
Alt-tab is supposed to display the icons for the applications that are running. If I keep the alt key depressed, the icons are supposed to stay visible. But on my system, they are only visible for a couple of seconds, and then the window for the icon
-
Is there a wy to turn off cover flow?
I know its a great way to browse music. But I just never use it. I find it faster to just select the song or artist of what I want to listen to. I don't like when I'm lying down or just trying to use it when I'm on my side and I can only browse in co
-
The default Access type when uploading a file is "Open", which means anyone can access the file if they have the URL (or guess it). Surely this should be "Restricted" until you decide to open the file? Or at the very least, an option in the preferenc