Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

DLSW+ Traffic Classification

I have two Ethernet segments and pair of DLSW+ routers between them. I would like to implement traffic classification, but all my traffic flows through high or low priority queues. Why ?

sap-priority-list 1 normal smac 0000.3049.d7f0

dlsw local-peer peer-id 172.16.1.1

dlsw remote-peer 0 tcp 172.16.1.3 priority

dlsw bridge-group 1 sap-priority 1

R1#sho dlsw pe

Peers: state pkts_rx pkts_tx type drops ckts TCP uptime

TCP 172.16.1.3

High priority CONNECT 4627 359 conf 0 1 0 00:25:00

Medium priority CONNECT 0 0 conf 0 - 0 00:25:00

Normal priority CONNECT 0 0 conf 0 - 0 00:25:00

Low priority CONNECT 8 6 conf 0 - 0 00:25:00

Total number of connected peers: 1

Total number of connections: 4

Many thanks.

P.S. 0000.3049.d7f0 (noncanonical format) is MAC address of Ethernet connected host.

3 REPLIES
New Member

Re: DLSW+ Traffic Classification

It's kind of hard to tell if there's a problem from the information you included. Your configuration looks ok.

Are you sure there was data traffic sent from the mac address you configured?

Other traffic (sabme, keep-alives) besides actual data traffic will still be sent over the high priority connection.

I'd suggest starting a session and sending some data traffic and look closely at the results. If you still see a problem, open a case with the TAC and give them more info - sh dlsw circuit detail, etc.

New Member

Re: DLSW+ Traffic Classification

For data traffic generation I use IPX & IP ping. It's not real SNA traffic, but it is the best I can get. There are no errors in MAC address because only one device is connected to Ethernet port on R1 and I see this MAC in show dlsw reachability local.

R1#sho dlsw ci det

Index local addr(lsap) remote addr(dsap) state uptime

1476395013 0000.3049.d7f0(AA) 00a0.bbcf.0f10(AA) CKT_ESTABLISHED -

PCEP: 813054C8 UCEP: 813060FC

Port:TB1 peer 172.16.1.3(2065)

Flow-Control-Tx CW:22, Permitted:35; Rx CW:22, Granted:36; Op: Incr

Congestion: Low(02), Flow Op: Half: 0/0 Reset 0/0

RIF = --no rif--

3959422982 0000.3049.d7f0(E0) 00a0.bbcf.0f10(E0) CKT_ESTABLISHED -

PCEP: 8102D208 UCEP: 81306480

Port:TB1 peer 172.16.1.3(2065)

Flow-Control-Tx CW:21, Permitted:32; Rx CW:21, Granted:32; Op: Incr

Congestion: Low(02), Flow Op: Half: 0/0 Reset 0/0

RIF = --no rif--

Bronze

Re: DLSW+ Traffic Classification

I think the problem is with the type of traffic you are using to test. DLSW will always send it own control traffic as high priority and explorers as low priority. Becaus IPX traffic is not supported by DLSW, only the contol and explorer traffic will ever be sent. This is why the circuit only ever gets as far as CKT_ESTABLISHED and never goes to CONNECTED.

332
Views
0
Helpful
3
Replies
CreatePlease login to create content