IP SLAの設定例
以下のネットワーク構成でのIP SLAの設定を考えます。
- R5からR1経由でR2に対してTelnetの応答時間をIP SLAで計測する。計測間隔は3分。
- R5からR4経由でR3に対してTelnetの応答時間をIP SLAで計測する。計測間隔は3分。
- IP SLAの宛先はLoopback0のIPアドレスとする。
- R5からIP SLAでHost1への接続性を1分間隔で確認する。
- IP SLAのモニタリングはすぐに開始し、継続して行うようにする。
目次
Step1:R2へのTelnetを計測するIP SLAの設定
R5からR2 Loopback0へのTelnetの応答時間を計測するためのIP SLAポリシーを
設定します。
R5
---------------------------------------------------------------------- ip sla monitor 1 type tcpConnect dest-ipaddr 192.168.0.2 dest-port 23 frequency 180 ----------------------------------------------------------------------
Step2:R3へのTelnetを計測するIP SLAの設定
R5からR3 Loopback0へのTelnetの応答時間を計測するためのIP SLAポリシーを
設定します。
R5
---------------------------------------------------------------------- ip sla monitor 2 type tcpConnect dest-ipaddr 192.168.0.3 dest-port 23 frequency 180 ----------------------------------------------------------------------
Step3:Host1への接続性を確認するIP SLAの設定
R5からHost1への接続性を確認するためのIP SLAポリシーを設定します。
R5
---------------------------------------------------------------------- ip sla monitor 3 type echo protocol ipIcmpEcho 192.168.0.3 ----------------------------------------------------------------------
Step4:IP SLAスケジュールの設定
Step3で定義したIP SLAポリシーのスケジュールを設定します。すぐに
開始して、確認を継続的に行います。
R5
---------------------------------------------------------------------- ip sla monitor schedule 1 life forever start-time now ip sla monitor schedule 2 life forever start-time now ip sla monitor schedule 3 life forever start-time now ----------------------------------------------------------------------
Step5:IP SLA Responderの設定
R2、R3でIP SLA Responderを有効化して、IP SLAパケットに応答できるように
します。
R2/R3
---------------------------------------------------------------------- ip sla monitor responder ----------------------------------------------------------------------
Step6:IP SLAの確認
R5でIP SLAの確認を行います。
show ip sla monitor configurationで設定されているIP SLAポリシーを確認
します。show ip sla monitor statisticsでIP SALの統計情報を確認します。
R5
---------------------------------------------------------------------- R5#show ip sla monitor configuration SA Agent, Infrastructure Engine-II Entry number: 1 Owner: Tag: Type of operation to perform: tcpConnect Target address: 192.168.0.2 Source address: 0.0.0.0 Target port: 23 Source port: 0 Operation timeout (milliseconds): 60000 Type Of Service parameters: 0x0 Control Packets: enabled Operation frequency (seconds): 180 Next Scheduled Start Time: Start Time already passed Group Scheduled : FALSE Life (seconds): Forever Entry Ageout (seconds): never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Number of history Lives kept: 0 Number of history Buckets kept: 15 History Filter Type: None Enhanced History: Entry number: 2 Owner: Tag: Type of operation to perform: tcpConnect Target address: 192.168.0.3 Source address: 0.0.0.0 Target port: 23 Source port: 0 Operation timeout (milliseconds): 60000 Type Of Service parameters: 0x0 Control Packets: enabled Operation frequency (seconds): 180 Next Scheduled Start Time: Start Time already passed Group Scheduled : FALSE Life (seconds): Forever Entry Ageout (seconds): never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Number of history Lives kept: 0 Number of history Buckets kept: 15 History Filter Type: None Enhanced History: Entry number: 3 Owner: Tag: Type of operation to perform: echo Target address: 192.168.0.3 Request size (ARR data portion): 28 Operation timeout (milliseconds): 5000 Type Of Service parameters: 0x0 Verify data: No Operation frequency (seconds): 60 Next Scheduled Start Time: Start Time already passed Group Scheduled : FALSE Life (seconds): Forever Entry Ageout (seconds): never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Number of history Lives kept: 0 Number of history Buckets kept: 15 History Filter Type: None Enhanced History: R5#show ip sla monitor statistics Round trip time (RTT) Index 1 Latest RTT: 56 ms Latest operation start time: *00:45:27.567 UTC Fri Mar 1 2002 Latest operation return code: OK Number of successes: 3 Number of failures: 1 Operation time to live: Forever Round trip time (RTT) Index 2 Latest RTT: 72 ms Latest operation start time: *00:45:30.523 UTC Fri Mar 1 2002 Latest operation return code: OK Number of successes: 3 Number of failures: 1 Operation time to live: Forever Round trip time (RTT) Index 3 Latest RTT: 48 ms Latest operation start time: *00:46:33.599 UTC Fri Mar 1 2002 Latest operation return code: OK Number of successes: 11 Number of failures: 0 Operation time to live: Forever ----------------------------------------------------------------------