DynagenでCCIEを目指す

INE Workbook Volume I QoS 確認用トラフィックの生成

最終更新：2011年07月03日 16:10

it_certification

- view

管理者のみ編集可

確認用トラフィックの生成

10.2. Weighted Queueing (WFQ)

INE記載の確認方法が効きません。SW2からR6へのhttp通信が以下の通り失敗してしまいます。

Rack8SW2#debug ip tcp transactions
TCP special event debugging is on
Rack8SW2#
Rack8SW2#
Rack8SW2#
Rack8SW2#copy http://cisco:cisco@155.8.146.6/c2600-adventerprisek9-mz.124-10.bin null:
Loading http://***********@155.8.146.6/c2600-adventerprisek9-mz.124-10.bin !
%Error reading http://cisco:cisco@155.8.146.6/c2600-adventerprisek9-mz.124-10.bin (Broken pipe)
Rack8SW2#
 *Mar  1 01:22:11.528: TCB0391D1A4 created
 *Mar  1 01:22:11.528: TCB0391D1A4 setting property TCP_NO_DELAY (0) 34E5ACC
 *Mar  1 01:22:11.528: TCB0391D1A4 setting property TCP_NONBLOCKING_WRITE (7) 34E5B88
 *Mar  1 01:22:11.528: TCB0391D1A4 setting property TCP_NONBLOCKING_READ (8) 34E5B88
 *Mar  1 01:22:11.528: TCB0391D1A4 setting property TCP_KEEPALIVE (4) 34E5A90
 *Mar  1 01:22:11.528: TCB0391D1A4 setting property TCP_NO_DELAYACK (9) 34E5B88
 *Mar  1 01:22:11.528: TCP: Random local port generated 64180, network 1
 *Mar  1 01:22:11.528: TPA: Reserved port 64180 in Transport Port Agent for TCP IP type 1
 *Mar  1 01:22:11.536: TCP: sending SYN, seq 470134722, ack 0
 *Mar  1 01:22:11.536: TCP0: Connection to 155.8.146.6:80, advertising MSS 536
 *Mar  1 01:22:11.536: TCP0: state was CLOSED -> SYNSENT [64180 -> 155.8.146.6(80)]
 *Mar  1 01:22:11.545: TCP0: state was SYNSENT -> ESTAB [64180 -> 155.8.146.6(80)]
 *Mar  1 01:22:11.545: TCP0: tcb 391D1A4 connection to 155.8.146.6:80, received MSS 536, MSS is 536
 *Mar  1 01:22:12.727: TCP: checksum failure <155.8.146.6,80> <155.8.58.8,64180>
 *Mar  1 01:22:15.722: TCP: checksum failure <155.8.146.6,80> <155.8.58.8,64180>
 *Mar  1 01:22:19.707: TCP: checksum failure <155.8.146.6,80> <155.8.58.8,64180>
 *Mar  1 01:22:27.659: TCP0: state was ESTAB -> FINWAIT1 [64180 -> 155.8.146.6(80)]
 *Mar  1 01:22:27.659: TCP0: sending FIN
 *Mar  1 01:22:27.676: TCP: checksum failure <155.8.146.6,80> <155.8.58.8,64180>
 *Mar  1 01:22:27.684: TCP0: state was FINWAIT1 -> FINWAIT2 [64180 -> 155.8.146.6(80)]
 *Mar  1 01:22:27.726: TCP0: bad seg from 155.8.146.6 -- Application closed: port 64180 seq 6611017 ack 470134918 rcvnxt 6611017 rcvwnd 4128 len 536
 *Mar  1 01:22:27.726: TCP: sending RST, seq 470134918, ack 0
 *Mar  1 01:22:27.726: TCP0: state was FINWAIT2 -> CLOSED [64180 -> 155.8.146.6(80)]
 *Mar  1 01:22:27.726: TPA: Released port 64180 in Transport Port Agent for TCP IP type 1 delay 240000
 *Mar  1 01:22:27.726: TCB 0x391D1A4 destroyed
 *Mar  1 01:22:27.735: TCP: sending RST, seq 470134919, ack 0
 *Mar  1 01:22:27.735: TCP: sent RST to 155.8.146.6:80 from 155.8.58.8:64180
Rack8SW2#

通信に失敗する原因は、R4, R5間のMTU sizeが小さすぎる事に起因します。WFQに関する設定を確認するために、mtuの設定を一時的に削除します。

R4:
interface Serial0/1/0
 no ip mtu

R5:
interface Serial0/1/0
 no ip mtu

WEQの設定を確認します。R5 s0/0/0をshutdownし、R6/SW2間, R1/SW4間でのHTTP通信を発生させまる。

R1:
policy-map MARK
 class class-default
  set ip precedence 3
!
interface FastEthernet0/0
 service-policy output MARK
!
ip http server
ip http path flash:


R5:
class-map match-all IP_PREC3
 match ip precedence 3
class-map match-all IP_PREC1
 match ip precedence 1
!
policy-map METER
 class IP_PREC1
 class IP_PREC3
!
interface FastEthernet 0/0
 service-policy input METER
!
interface Serial0/0/0
 shutdown
!
interface Serial0/1/0
 service-policy input METER
!


R6:
policy-map MARK
 class class-default
  set ip precedence 1
!
interface FastEthernet0/0.146
 service-policy output MARK
!
ip http server
ip http path flash:
!
copy http://cisco:cisco@155.5.146.1/c2600-adventerprisek9-mz.124-10.bin flash:


SW2:
ip http client password cisco
ip http client source-interface Loopback 0
copy http://155.5.146.1/c2600-adventerprisek9-mz.124-10.bin null:


SW4:
ip http client password cisco
ip http client source-interface Loopback 0
copy http://155.5.146.1/c2600-adventerprisek9-mz.124-10.bin null:

precedence 1とprecedence 3の通信量の比率が1:2になっている事を確認します。

Rack5R5#clear counters
Clear "show interface" counters on all interfaces [confirm]
Rack5R5#
May 29 01:00:33.999: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console
Rack5R5#
Rack5R5#
Rack5R5#show policy-map interface Serial 0/1/0
 Serial0/1/0

  Service-policy input: METER

    Class-map: IP_PREC1 (match-all)
      393 packets, 227940 bytes
      5 minute offered rate 86000 bps
      Match: ip precedence 1

    Class-map: IP_PREC3 (match-all)
      786 packets, 455880 bytes
      5 minute offered rate 26000 bps
      Match: ip precedence 3

    Class-map: class-default (match-any)
      8 packets, 3008 bytes
      5 minute offered rate 0 bps, drop rate 0 bps
      Match: any
Rack5R5#

10.3. Legacy RTP Reserved Queue

INE記載の確認方法では、MOS値がRTP Reserved Queueにより変化する事を確認できません。
私の場合は、以下の通り2つのHTTP通信を発生させRTP Reserved Queueを確認しました。

R1:
no policy-map MARK
!
ip sla monitor 1
 type jitter dest-ipaddr 155.5.45.5 dest-port 16384 codec g729a
 timeout 100
 frequency 1
ip sla monitor schedule 1 life forever start-time now

R5:
 ip sla responder

R6:
no policy-map MARK
!
policy-map MARK
 class class-default
  set ip precedence 7
!
interface FastEthernet0/0.146
 service-policy output MARK

SW2:
ip http client password cisco
ip http client source-interface Loopback 0
copy http://155.5.146.6/c2600-adventerprisek9-mz.124-10.bin null:

RTP Reserved Queueを設定していない状態では、udp jitterがtimeoutしている事が確認できます。(timeout値を大きめに設定すればMOS値を測定できたかもしれません)

Rack5R1#show ip sla monitor statistics
Round trip time (RTT)   Index 1
        Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: 01:44:29.562 UTC Sun May 29 2011
Latest operation return code: Timeout
RTT Values
        Number Of RTT: 0
        RTT Min/Avg/Max: 0/0/0 ms
Latency one-way time milliseconds
        Number of one-way Samples: 0
        Source to Destination one way Min/Avg/Max: 0/0/0 ms
        Destination to Source one way Min/Avg/Max: 0/0/0 ms
Jitter time milliseconds
        Number of Jitter Samples: 0
        Source to Destination Jitter Min/Avg/Max: 0/0/0 ms
        Destination to Source Jitter Min/Avg/Max: 0/0/0 ms
Packet Loss Values
        Loss Source to Destination: 0           Loss Destination to Source: 0
        Out Of Sequence: 0      Tail Drop: 0    Packet Late Arrival: 0
Voice Score Values
        Calculated Planning Impairment Factor (ICPIF): 0
        Mean Opinion Score (MOS): 0
Number of successes: 4
Number of failures: 5
Operation time to live: Forever


Rack5R1#

INE模範解答通りの設定を投入します。

R4:
interface Serial0/1/0
 no hold-queu out
 fair-queue
 max-reservation-bandwidth 100
 ip rtp reservation 16384 16383 128

通信品質が改善され、timeoutが発生さず、MOS値も充分良い値を示しています。

Rack5R1#show ip sla monitor statistics
Round trip time (RTT)   Index 1
        Latest RTT: 60 ms
Latest operation start time: 01:46:35.961 UTC Sun May 29 2011
Latest operation return code: OK
RTT Values
        Number Of RTT: 1000
        RTT Min/Avg/Max: 28/60/100 ms
Latency one-way time milliseconds
        Number of one-way Samples: 0
        Source to Destination one way Min/Avg/Max: 0/0/0 ms
        Destination to Source one way Min/Avg/Max: 0/0/0 ms
Jitter time milliseconds
        Number of Jitter Samples: 999
        Source to Destination Jitter Min/Avg/Max: 3/23/65 ms
        Destination to Source Jitter Min/Avg/Max: 1/1/11 ms
Packet Loss Values
        Loss Source to Destination: 0           Loss Destination to Source: 0
        Out Of Sequence: 0      Tail Drop: 0    Packet Late Arrival: 0
Voice Score Values
        Calculated Planning Impairment Factor (ICPIF): 11
MOS score: 4.06
Number of successes: 6
Number of failures: 9
Operation time to live: Forever


Rack5R1#

「INE Workbook Volume I QoS 確認用トラフィックの生成」をウィキ内検索

人気記事ランキング

最近更新されたページ

新規Wikiランキング

最近作成されたWikiのアクセスランキングです。見るだけでなく加筆してみよう！

人気Wikiランキング

atwikiでよく見られているWikiのランキングです。新しい情報を発見してみよう！

全体ページランキング

最近アクセスの多かったページランキングです。話題のページを見に行こう！

INE Workbook Volume I QoS 確認用トラフィックの生成

確認用トラフィックの生成

10.2. Weighted Queueing (WFQ)

10.3. Legacy RTP Reserved Queue

メインコンテンツ

更新履歴

@Wiki