11-29-2016 03:43 PM - edited 03-05-2019 07:34 AM
Hi, I am trying to verify how the current qos setting is working on this old router that has a t1 circuit. I have questions since I am unfamiliar with the way this old 1861 is configured and no one here does either.. LOL
1. the router has switchports and all switchport interfaces are configured with the inbound qos but nothing is connected to those switchports. for qos to work on this network does these switchports need to be configured? when i do a cdp nei i see a layer 2 switch which has all the clients connected to it. jsut want to confirm that these ports for any reason on this old router would require to be configured with service policy when nothing is connected. one reason i ask is when i do a sho int on the switch port it has FastEthernet0/1/0 is up, line protocol is down
2. I tried to configure the service policy on the vlan inteface where i thought it should be based on what this is intended for client utilization. but couldnt apply the service policy on the int vlan 10 interface and I couldnt. typically on my 2911 routers that i have configured router on a stick with vlans i would apply the service policy.
What would be the command to apply the qos on the 1861? or is this old router not capable?
(config-if)#service-policy output SHAPE-INBOUND
Configuration failed!
typically on my 2911 routers that i have configured router on a stick with vlans i would apply the service policy.
1861
ios C1861 Software (C1861-ADVIPSERVICESK9-M), Version 15.1(2)T2, RELEASE SOFTWARE (fc1)
class-map match-any INBOUND
match access-group name SHAPE-INBOUND-WAN
policy-map SHAPE-INBOUND
class INBOUND
shape average 128000
interface FastEthernet0/1/0
switchport access vlan 10
no snmp trap link-status
service-policy output SHAPE-INBOUND
FastEthernet0/1/0 is up, line protocol is down
Hardware is Fast Ethernet, address is c89c.1d1f.82c2 (bia c89c.1d1f.82c2)
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed
ARP type: ARPA, ARP Timeout 04:00:00
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: 0
Queueing strategy: Class-based queueing
Output queue: 0/1000/0 (size/max total/drops)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
ho policy-map SHAPE-INBOUND
Policy Map SHAPE-INBOUND
Class INBOUND
Average Rate Traffic Shaping
cir 128000 (bps)
SpoWA1-662#sho policy-map int fa0/1/0
FastEthernet0/1/0
Service-policy output: SHAPE-INBOUND
Class-map: INBOUND (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name SHAPE-INBOUND-WAN
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 128000, bc 512, be 512
target shape rate 128000
Class-map: class-default (match-any)
53242 packets, 4099634 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 53242/4099634
11-30-2016 12:31 AM
Hello,
according to the document below ((go to Table 1), Class-Based Traffic Shaping and Generic Traffic Shaping are not suppported on SVIs on the 1861 router. Committed Access Rate and Policing are supported...
http://www.cisco.com/c/en/us/products/collateral/routers/1800-series-integrated-services-routers-isr/prod_white_paper0900aecd8064c9f4.html
Your FastEthernet interface being up/down just means that it is administratively up, (as opposed to administratively down after issuing the 'shut' command). Service policies applied to an interface in that state have no effect or impact. It is good practice to shut ('shut') down interfaces that are not in use...
12-16-2016 11:01 AM
Thank you! that's what I figured.
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