From: Nick Shah (nshah@xxxxxxxxxxxxxx)
Date: Sat Aug 24 2002 - 23:15:47 GMT-3
Priority keyword just opens 4 ports/queues, you still need to "map traffic"
to those 4 queues.
The way to do this is locaddr priority lists and/or sap priority lists.
And then you have to map those ports/queues (1981, 1982, 1983 & 2065) to
different priority queues, to acheive the desired results.
rgds
Nick
----- Original Message -----
From: kpalmer <kip.palmer@verizon.net>
To: <ccielab@groupstudy.com>
Sent: Sunday, August 25, 2002 11:23 AM
Subject: dlsw ports application
> I don't get it. I'm definitely missing something.
> I can't get any packets queued in anything but 2065.
>
> If someone could look at my config and point my error,
> I could take this rope from around my neck!
>
> I put ICMP in a normal queue and pinged bridge port to
> bridge port 1000 packets, 1600 bytes and all 2065 high?
>
> Thanks...
>
> r1-----frame--------r7
>
> r1#sh dlsw peers
> Peers: state pkts_rx pkts_tx type drops ckts TCP
> uptime
> TCP 223.7.7.7
> High priority CONNECT 280 268 conf 0 0 0
> 02:12:05
> Medium priority CONNECT 0 0 conf 0 - 0
> 02:12:05
> Normal priority CONNECT 0 0 conf 0 - 0
> 02:12:05
> Low priority CONNECT 0 0 conf 0 - 0
> 02:12:05
> TCP 223.8.8.8 DISCONN 0 0 conf 0 0 -
> -
> Total number of connected peers: 1
> Total number of connections: 4
>
> =======r1
>
> dlsw local-peer peer-id 223.1.1.1 promiscuous
> dlsw remote-peer 0 tcp 223.7.7.7 priority
> dlsw bridge-group 1
>
>
> interface loop 0
> 223.1.1.1
>
> interface Ethernet0
> ip address 129.45.80.225 255.255.255.248
> bridge-group 1
>
> interface Serial0
> encapsulation frame-relay
> frame-relay traffic-shaping
> frame-relay lmi-type ansi
> !
> interface Serial0.1 multipoint
> ip address 129.45.80.241 255.255.255.248
> frame-relay map ipx 87.0007.0007.0007 107 broadcast
> frame-relay map ipx 87.0008.0008.0008 108 broadcast
> frame-relay map ip 129.45.80.242 108 broadcast
> frame-relay map ip 129.45.80.243 107 broadcast
> frame-relay interface-dlci 107
> class toR6
> frame-relay interface-dlci 108
> class toR6
>
> map-class frame-relay toR6
> frame-relay cir in 56000
> frame-relay cir out 64000
> frame-relay bc in 56000
> frame-relay bc out 8000
> frame-relay mincir in 56000
> frame-relay mincir out 64000
> frame-relay adaptive-shaping becn
> frame-relay priority-group 16
>
>
> access-list 112 permit icmp any any
> access-list 200 permit 0x0D0D 0x0000
> priority-list 16 protocol dlsw high lt 1600
> priority-list 16 protocol ip normal list 112
> priority-list 16 protocol ip low tcp ftp
> priority-list 16 protocol ip low tcp ftp-data
> priority-list 16 protocol ip high udp ntp
>
> bridge 1 protocol ieee
>
>
> ====r7
>
> dlsw local-peer peer-id 223.7.7.7 promiscuous
> dlsw remote-peer 0 tcp 223.1.1.1 priority
> dlsw bridge-group 1
>
> interface loop 0
> 223.7.7.7
>
> interface Ethernet0
> ip address 129.45.80.217 255.255.255.248
> bridge-group 1
>
> bridge 1 protocol ieee
>
> =======making sure traffic is taking the desired path
>
> r1#traceroute 129.45.80.217
>
> Type escape sequence to abort.
> Tracing the route to 129.45.80.217
>
> 1 129.45.80.243 16 msec * 16 msec
> r1#
> ======show dlsw peers
> after pinging BGroup 1 interface on R7 from R1 1000 packets 1500 bytes
>
> r1#sh dlsw peers
> Peers: state pkts_rx pkts_tx type drops ckts TCP
> uptime
> TCP 223.7.7.7
> High priority CONNECT 280 268 conf 0 0 0
> 02:12:05
> Medium priority CONNECT 0 0 conf 0 - 0
> 02:12:05
> Normal priority CONNECT 0 0 conf 0 - 0
> 02:12:05
> Low priority CONNECT 0 0 conf 0 - 0
> 02:12:05
> TCP 223.8.8.8 DISCONN 0 0 conf 0 0 -
> -
> Total number of connected peers: 1
> Total number of connections: 4
>
>
>
>
>
>
> Kip Palmer
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Privacy Notice:
>
> This message is intended only for the use of the individual or entity to
> whom it is addressed
> and may contain information that is privileged, confidential, or exempt
> from disclosure under
> applicable federal or state law. If the reader of this message is not
> the intended recipient
> or the employee or agents responsible for delivering the message to the
> intended recipient you
> are hereby notified that any dissemination, distribution, or copying of
> this message is strictly prohibited. If you have received this
> communication in error,
> please return to:kip.palmer@verizon.net. THANK YOU!
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:36 GMT-3