ヨタ助

携帯用ページ http://www.google.co.jp/gwt/x?u=http%3a%2f%2funipass.blogspot.com&btngo=go&source=wax&ie=utf-8&oe=utf-8

Monday, May 30, 2011

Sham-link & MPLS enable

### R4 - R5 間で "mpls ip" enable 前 ###

R5#os sham
Sham Link OSPF_SL0 to address 18.18.100.4 is up
Area 0 source address 18.18.100.5
  Run as demand circuit
  DoNotAge LSA allowed. Cost of using 1 State POINT_TO_POINT,
  Timer intervals configured, Hello 10, Dead 40, Wait 40,
    Hello due in 00:00:00

R4#sh ip ospf sham-links
Sham Link OSPF_SL1 to address 18.18.100.5 is up
Area 0 source address 18.18.100.4
  Run as demand circuit
  DoNotAge LSA allowed. Cost of using 1 State POINT_TO_POINT,
  Timer intervals configured, Hello 10, Dead 40, Wait 40,
    Hello due in 00:00:03

### R4 - R5 間で "mpls ip" enable 後 ###

"Adjacency State FULL" を確認する必要あり。


R5#os sham
Sham Link OSPF_SL0 to address 18.18.100.4 is up
Area 0 source address 18.18.100.5
  Run as demand circuit
  DoNotAge LSA allowed. Cost of using 1 State POINT_TO_POINT,
  Timer intervals configured, Hello 10, Dead 40, Wait 40,
    Hello due in 00:00:05
    Adjacency State FULL (Hello suppressed)
    Index 2/3, retransmission queue length 0, number of retransmission 0
    First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
    Last retransmission scan length is 0, maximum is 0
    Last retransmission scan time is 0 msec, maximum is 0 msec



R4#os sham
Sham Link OSPF_SL1 to address 18.18.100.5 is up
Area 0 source address 18.18.100.4
  Run as demand circuit
  DoNotAge LSA allowed. Cost of using 1 State POINT_TO_POINT,
  Timer intervals configured, Hello 10, Dead 40, Wait 40,
    Hello due in 00:00:02
    Adjacency State FULL (Hello suppressed)
    Index 2/3, retransmission queue length 0, number of retransmission 0
    First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
    Last retransmission scan length is 0, maximum is 0
    Last retransmission scan time is 0 msec, maximum is 0 msec

posted by kimiyone @ Monday, May 30, 2011  0 Comments

Sunday, May 22, 2011

score report

Advanced Services

 First Hop router Redundancy
 Security
 QoS
 NTP
 DHCP


Optimized the Network

 IP SLA
 Netflow
 SNMP
 System Logging
 EEM
 Core Dump
 File Transfer Services
 IP Source Tracker

posted by kimiyone @ Sunday, May 22, 2011  0 Comments

Tuesday, May 03, 2011

NTP Testing

BB3 (204.12.1.254) が元々の master clock.
SW1 と R5 は ntp server 204.12.1.254 で時刻同期していたが、
BB3 (204.12.1.254 ) への経路が down

R5 が
 ntp master 5
 ntp peer 148.1.57.7 (SW1)
の設定をしていることから、R5 は自分 (127.127.7.1) を masterとする一方で
SW1 (148.1.57.7) も見に行っている（しかし、SW1 は Stratum 6 であるため、
R5 は SW1 を master clock として認めない。

SW1 は R5 側から Peer の設定をしてあるため、R5 と同期しようとする
BB3 が Stratum 4 で残っているが、reachable ではないため、reachable かつ
正常稼働している R5 (148.1.57.5) と同期。



Rack1SW1#sh ntp asso

      address         ref clock     st  when  poll reach  delay  offset    disp
+ 148.1.57.5       204.12.1.254      5    34    64  376   -23.7   11.19    17.2
*~204.12.1.254     127.127.7.1       4   507    64  200     7.8   23.79  16000.
 * master (synced), # master (unsynced), + selected, - candidate, ~ configured
Rack1SW1#sh ntp asso

      address         ref clock     st  when  poll reach  delay  offset    disp
* 148.1.57.5       204.12.1.254      5    62    64  376   -23.7   11.19    17.2
 ~204.12.1.254     127.127.7.1       4   535    64    0     7.8   23.79  16000.
 * master (synced), # master (unsynced), + selected, - candidate, ~ configured

Rack1SW1#sh ntp asso de
148.1.57.5 dynamic, our_master, sane, valid, stratum 5
ref ID 204.12.1.254, time C0295462.3CBD3979 (01:14:10.237 UTC Fri Mar 1 2002)
our mode passive, peer mode active, our poll intvl 64, peer poll intvl 64
root delay 8.13 msec, root disp 25.38, reach 377, sync dist 59.082
delay -23.70 msec, offset 11.1856 msec, dispersion 17.79
precision 2**18, version 3
org time C0295673.37899BC9 (01:22:59.216 UTC Fri Mar 1 2002)
rcv time C0295673.3CDCCCD6 (01:22:59.237 UTC Fri Mar 1 2002)
xmt time C0295651.41FDA9FD (01:22:25.257 UTC Fri Mar 1 2002)
filtdelay =    48.02  -23.70  -15.69   -7.66    3.92   36.35   -7.74   13.06
filtoffset =    3.21   11.19   -0.77  -12.71  -18.61    9.48   -3.94   -4.76
filterror =     0.53    1.51    2.49    3.46    4.44    5.42    6.39    7.37

204.12.1.254 configured, insane, invalid, stratum 4
ref ID 127.127.7.1, time C0295429.A2C06A68 (01:13:13.635 UTC Fri Mar 1 2002)
our mode client, peer mode server, our poll intvl 64, peer poll intvl 64
root delay 0.00 msec, root disp 0.03, reach 0, sync dist 28.458
delay 7.81 msec, offset 23.7948 msec, dispersion 16000.00
precision 2**18, version 3
org time 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
rcv time 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
xmt time 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
filtdelay =     0.00    0.00    0.00    0.00    0.00    0.00    0.00    0.00
filtoffset =    0.00    0.00    0.00    0.00    0.00    0.00    0.00    0.00
filterror =  16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0

Rack1SW1#


Rack1R5#sh ntp asso

      address         ref clock     st  when  poll reach  delay  offset    disp
+~127.127.7.1      127.127.7.1       4    51    64  377     0.0    0.00     0.0
+~148.1.57.7       204.12.1.254      5    42    64  376    -7.7   -3.21    12.8
*~204.12.1.254     127.127.7.1       4   473    64  200     8.1   12.07  16000.
 * master (synced), # master (unsynced), + selected, - candidate, ~ configured

Rack1R5#sh ntp asso

      address         ref clock     st  when  poll reach  delay  offset    disp
*~127.127.7.1      127.127.7.1       4    58    64  377     0.0    0.00     0.0
+~148.1.57.7       204.12.1.254      5    49    64  376    -7.7   -3.21    17.2
 ~204.12.1.254     127.127.7.1       4   544    64    0     8.1   12.07  16000.
 * master (synced), # master (unsynced), + selected, - candidate, ~ configured
Rack1R5#

Rack1R5#sh ntp asso de
127.127.7.1 configured, our_master, sane, valid, stratum 4
ref ID 127.127.7.1, time C0295688.3788A45C (01:23:20.216 UTC Fri Mar 1 2002)
our mode active, peer mode passive, our poll intvl 64, peer poll intvl 64
root delay 0.00 msec, root disp 0.00, reach 377, sync dist 0.153
delay 0.00 msec, offset 0.0000 msec, dispersion 0.02
precision 2**18, version 3
org time C0295688.3788A45C (01:23:20.216 UTC Fri Mar 1 2002)
rcv time C0295688.3788A45C (01:23:20.216 UTC Fri Mar 1 2002)
xmt time C0295688.37888866 (01:23:20.216 UTC Fri Mar 1 2002)
filtdelay =     0.00    0.00    0.00    0.00    0.00    0.00    0.00    0.00
filtoffset =    0.00    0.00    0.00    0.00    0.00    0.00    0.00    0.00
filterror =     0.02    0.99    1.97    2.94    3.92    4.90    5.87    6.85
Reference clock status:  Running normally
Timecode:

148.1.57.7 configured, insane, invalid, stratum 6
ref ID 148.1.57.5, time C0295673.3CDCCCD6 (01:22:59.237 UTC Fri Mar 1 2002)
our mode active, peer mode passive, our poll intvl 128, peer poll intvl 64
root delay 31.83 msec, root disp 54.37, reach 376, sync dist 92.239
delay -7.74 msec, offset -3.2092 msec, dispersion 18.10
precision 2**18, version 3
org time C0295691.4247359D (01:23:29.258 UTC Fri Mar 1 2002)
rcv time C0295691.43D97305 (01:23:29.265 UTC Fri Mar 1 2002)
xmt time C02956B3.378F304B (01:24:03.217 UTC Fri Mar 1 2002)
filtdelay =    26.93    4.20   -7.74    0.27    4.03   -7.95   27.73    3.49
filtoffset =    7.33  -25.12   -3.21    8.74   18.56   12.67  -13.79    9.54
filterror =     0.47    1.45    2.43    3.40    4.38    5.36    6.33    7.31

204.12.1.254 configured, insane, invalid, stratum 4
ref ID 127.127.7.1, time C0295429.A2C06A68 (01:13:13.635 UTC Fri Mar 1 2002)
our mode client, peer mode server, our poll intvl 64, peer poll intvl 64
root delay 0.00 msec, root disp 0.03, reach 0, sync dist 19.257
delay 8.13 msec, offset 12.0710 msec, dispersion 16000.00
precision 2**18, version 3
org time 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
rcv time 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)
xmt time C02956A2.37885700 (01:23:46.216 UTC Fri Mar 1 2002)
filtdelay =     0.00    0.00    0.00    0.00    0.00    0.00    0.00    0.00
filtoffset =    0.00    0.00    0.00    0.00    0.00    0.00    0.00    0.00
filterror =  16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0 16000.0

Rack1R5#

posted by kimiyone @ Tuesday, May 03, 2011  0 Comments

Remote Shell Command

R1 (remote shell commander)
ip rcmd remote-username RCP
ip rcmd source-interface Loopback0

R3 (remote shell target)
ip rcmd rcp-enable
ip rcmd rsh-enable
ip rcmd remote-host Rack1R3 150.1.1.1 Rack1R1 enable
ip rcmd remote-host RCP 150.1.1.1 Rack1R1 enable

VerifiRack1R1#deb ip tcp rcmd
RCMD transactions debugging is on

Rack1R1#rsh 150.1.3.3 /user Rack1R3 sh run int se0/0

Line has invalid autocommand "sh run int se0/0"

Rack1R1#
*Mar  1 02:21:19.783: RCMD: [1023 -> 150.1.3.3:514] send \0
*Mar  1 02:21:19.783: RCMD: [1023 -> 150.1.3.3:514] send Rack1R1\0
*Mar  1 02:21:19.783: RCMD: [1023 -> 150.1.3.3:514] send Rack1R3\0
*Mar  1 02:21:19.783: RCMD: [1023 -> 150.1.3.3:514] send sh run int se0/0\0
*Mar  1 02:21:19.791: RCMD: [1023 <- 150.1.3.3:514] recv

Rack1R1#rsh 150.1.3.3 /user Rack1R3 sh run int se1/1

Building configuration...

Current configuration : 76 bytes
!
interface Serial1/1
 no ip address
 shutdown
 serial restart-delay 0
end
cation from commander R1

Rack1R3#deb ip tcp rcmd
RCMD transactions debugging is on
Rack1R3#      
*Mar  1 02:21:14.039: RCMD: [514 <- 150.1.1.1:1023] recv \0
*Mar  1 02:21:14.039: RCMD: [514 <- 150.1.1.1:1023] recv Rack1R1\0Rack1R3\0sh run int se0/0\0
*Mar  1 02:21:14.039: RCMD: [514 -> 150.1.1.1:1023] send
Rack1R3#
*Mar  1 02:21:21.607: RCMD: [514 <- 150.1.1.1:1016] recv \0
*Mar  1 02:21:21.611: RCMD: [514 <- 150.1.1.1:1016] recv Rack1R1\0Rack1R3\0sh run int se1/1\0
*Mar  1 02:21:21.611: RCMD: [514 -> 150.1.1.1:1016] send
Rack1R3#
Rack1R3#srs ip rcmd

posted by kimiyone @ Tuesday, May 03, 2011  0 Comments

Sunday, May 01, 2011

Lock-and-Key Security for Dynamic Access Lists

Lock-and-Key configuration

Point
 - create Dynamic ACL with required traffic (TELNET or Web access) using Extended ACL
 - create username with "autocommand access-enable timeout 5" command
 - add entries need to be permitted for management, routing protocol, etc. Or just permit "ip any any" at the bottom of the ACL entries.

Reference
Cisco IOS Security Configuration Guide: Securing the Data Plane

posted by kimiyone @ Sunday, May 01, 2011  0 Comments

Control Plane Protections

3 types of sub-interfaces

1) Control-plane host sub-interface

2) Control-plane transit sub-interface

3) Control-plane cef-exception sub-interface


1) Control-plane host sub-interface

directly destined for 1 of router's interface
Example,
  • tunnel termination traffic
  • Management protocols (SSH, SNMP, etc)
  • Routing protocols (BGP, OSPF, EIGRP, etc)
* Non-IP based Layer 2 protocols (ARP, CDP, etc) is classified in CEF-execption sub-interface.

** The port-filter feature policy can be applied only to the control-plane host subinterface

2) Control-plane transit sub-interface

software switched by the Route Processor (RP). traffic which is not destined to the router itself, but traversing traffic.

3) Control-plane CEF-exception sub-interface

This control-plane subinterface receives all traffic that is either redirected as a result of a configured input feature in the CEF packet forwarding path for process switching or directly enqueued in the control plane input queue by the interface driver (i.e. ARP, L2 Keepalives and all non-IP host traffic). Control Plane Protection allows specific aggregate policing of this type of control plane traffic.

posted by kimiyone @ Sunday, May 01, 2011  0 Comments

Thursday, April 21, 2011

Multicast configuration pit hall

1) 
RP Address の Typo
RP Address の RIB 上の状態 (/24なのか、/32なのか？)
RP Address の Interface で ip pim mode の設定漏れ

 →上記のどれかが間違っている場合には、 LHR で debug ip mpacket の出力が
    not RPF や RPF check / lookup が fail する

2) 
IGMP Interface での ip pim (sparse/dense) mode の設定漏れ

 →RP や Source までの RPT で Out Interface が Null のままとなる

posted by kimiyone @ Thursday, April 21, 2011  0 Comments

WB Vol.1 Multicast - Auto Listener - Test


### Configuration ###
%% R1 %%
Loopback0
 ip address 150.1.1.1 255.255.255.0
!
interface FastEthernet0/0
 ip address 155.1.1.1 255.255.255.0
 ip pim sparse-mode
!
interface FastEthernet0/1
 ip address 155.1.12.1 255.255.255.0
 ip pim sparse-mode
!
ip pim autorp listener

%% R2 %%

interface Loopback0
 ip address 150.1.2.2 255.255.255.0
 ip pim sparse-mode
!
interface FastEthernet0/0
 ip address 155.1.12.2 255.255.255.0
 ip pim sparse-mode
!
interface FastEthernet0/1
 ip address 155.1.23.2 255.255.255.0
 ip pim sparse-mode
!
ip pim autorp listener
ip pim send-rp-announce Loopback0 scope 16

%% R3 %%

interface Loopback0
 ip address 150.1.3.3 255.255.255.0
 ip pim sparse-mode
!
interface FastEthernet0/0
 ip address 155.1.23.3 255.255.255.0
 ip pim sparse-mode
!
interface FastEthernet0/1
 ip address 155.1.34.3 255.255.255.0
 ip pim sparse-mode
!
ip pim autorp listener
ip pim send-rp-discovery Loopback0 scope 16

%% R4 %%


interface Loopback0
 ip address 150.1.4.4 255.255.255.0
!
interface FastEthernet0/0
 ip address 155.1.34.4 255.255.255.0
 ip pim sparse-mode
!
interface FastEthernet0/1
 ip address 155.1.4.4 255.255.255.0
 ip pim sparse-mode
 ip igmp join-group 224.10.10.10
!
ip pim autorp listener




### Verification ###
R1#ping 224.10.10.10

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.10.10.10, timeout is 2 seconds:

Reply to request 0 from 155.1.34.4, 28 ms
Reply to request 0 from 155.1.34.4, 36 ms


R1#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
       L - Local, P - Pruned, R - RP-bit set, F - Register flag,
       T - SPT-bit set, J - Join SPT, M - MSDP created entry,
       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
       U - URD, I - Received Source Specific Host Report,
       Z - Multicast Tunnel, z - MDT-data group sender,
       Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
 Timers: Uptime/Expires
 Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.10.10.10), 00:04:40/stopped, RP 150.1.2.2, flags: SPF
  Incoming interface: FastEthernet0/1, RPF nbr 155.1.12.2
  Outgoing interface list: Null

(155.1.1.1, 224.10.10.10), 00:00:16/00:03:16, flags: FT
  Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0, Registering
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 00:00:16/00:03:13

(155.1.12.1, 224.10.10.10), 00:03:41/00:02:43, flags: PT
  Incoming interface: FastEthernet0/1, RPF nbr 0.0.0.0
  Outgoing interface list: Null

(*, 224.0.1.39), 04:57:11/stopped, RP 0.0.0.0, flags: D
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 04:57:11/00:00:00

(150.1.2.2, 224.0.1.39), 00:00:51/00:02:08, flags: PT
  Incoming interface: FastEthernet0/1, RPF nbr 155.1.12.2
  Outgoing interface list: Null

(*, 224.0.1.40), 04:57:26/stopped, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 04:57:26/00:00:00
    FastEthernet0/0, Forward/Sparse, 04:57:26/00:00:00

(150.1.3.3, 224.0.1.40), 00:13:02/00:02:03, flags: LT
  Incoming interface: FastEthernet0/1, RPF nbr 155.1.12.2
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 00:13:02/00:00:00

R1#


R2#sh ip mroute
IP Multicast Routing Table

(*, 224.10.10.10), 04:56:36/00:03:10, RP 150.1.2.2, flags: S
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 04:56:36/00:03:10

(155.1.1.1, 224.10.10.10), 00:00:37/00:02:22, flags:
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.12.1
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 00:00:37/00:03:10

(155.1.12.1, 224.10.10.10), 00:00:37/00:03:00, flags: T
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.12.1
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 00:00:37/00:03:10

(*, 224.0.1.39), 04:57:32/stopped, RP 0.0.0.0, flags: DC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 04:57:32/00:00:00
    FastEthernet0/0, Forward/Sparse, 04:57:32/00:00:00

(150.1.2.2, 224.0.1.39), 04:57:12/00:02:47, flags: T
  Incoming interface: Loopback0, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/0, Prune/Sparse, 00:13:12/00:01:52
    FastEthernet0/1, Forward/Sparse, 04:57:12/00:00:00

(*, 224.0.1.40), 04:57:32/stopped, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 04:57:32/00:00:00
    FastEthernet0/1, Forward/Sparse, 04:57:32/00:00:00
    FastEthernet0/0, Forward/Sparse, 04:57:32/00:00:00

(150.1.3.3, 224.0.1.40), 00:13:23/00:02:47, flags: LT
  Incoming interface: FastEthernet0/1, RPF nbr 155.1.23.3
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 00:13:23/00:00:00
    Loopback0, Forward/Sparse, 00:13:23/00:00:00

R2#

R3#
R3#sh ip mroute
IP Multicast Routing Table

(*, 224.10.10.10), 04:57:02/00:02:45, RP 150.1.2.2, flags: S
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.23.2
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 04:57:02/00:02:45

(155.1.1.1, 224.10.10.10), 00:01:03/00:02:26, flags:
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.23.2
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 00:01:03/00:03:25

(155.1.12.1, 224.10.10.10), 00:01:03/00:02:25, flags:
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.23.2
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 00:01:03/00:03:24

(*, 224.0.1.39), 04:57:38/stopped, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 00:13:49/00:00:00
    FastEthernet0/1, Forward/Sparse, 04:57:39/00:00:00
    FastEthernet0/0, Forward/Sparse, 04:57:39/00:00:00

(150.1.2.2, 224.0.1.39), 00:16:38/00:02:27, flags: LT
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.23.2
  Outgoing interface list:
    Loopback0, Forward/Sparse, 00:13:50/00:00:00
    FastEthernet0/1, Forward/Sparse, 00:13:50/00:00:00

(*, 224.0.1.40), 04:57:44/stopped, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 00:13:50/00:00:00
    FastEthernet0/1, Forward/Sparse, 04:57:44/00:00:00
    FastEthernet0/0, Forward/Sparse, 04:57:44/00:00:00

(150.1.3.3, 224.0.1.40), 00:13:49/00:02:14, flags: LT
  Incoming interface: Loopback0, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 00:13:49/00:00:00
    FastEthernet0/1, Forward/Sparse, 00:13:49/00:00:00

R3#

R4#sh ip mroute
IP Multicast Routing Table

(*, 224.10.10.10), 04:57:29/stopped, RP 150.1.2.2, flags: SJCL
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.34.3
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 04:57:29/00:02:03

(155.1.1.1, 224.10.10.10), 00:01:30/00:01:35, flags: LJT
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.34.3
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 00:01:30/00:02:03

(155.1.12.1, 224.10.10.10), 00:01:30/00:01:35, flags: LJT
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.34.3
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse, 00:01:30/00:02:03

(*, 224.0.1.39), 04:54:05/stopped, RP 0.0.0.0, flags: DC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 04:54:05/00:00:00

(150.1.2.2, 224.0.1.39), 00:02:05/00:00:54, flags: PTX
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.34.3
  Outgoing interface list: Null

(*, 224.0.1.40), 04:58:03/stopped, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 04:58:03/00:00:00

(150.1.3.3, 224.0.1.40), 00:14:16/00:02:48, flags: PLTX
  Incoming interface: FastEthernet0/0, RPF nbr 155.1.34.3
  Outgoing interface list: Null

R4#


## Verification -2 ##

R1#sh ip pim rp
Group: 224.10.10.10, RP: 150.1.2.2, v2, uptime 00:15:26, expires 00:02:25
R1#sh ip pim rp map
PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4
  RP 150.1.2.2 (?), v2v1
    Info source: 150.1.3.3 (?), elected via Auto-RP
         Uptime: 00:15:40, expires: 00:02:12
R1#

R2#sh ip pim rp
Group: 224.10.10.10, RP: 150.1.2.2, v2, v1, next RP-reachable in 00:00:54
R2#sh ip pim rp map
PIM Group-to-RP Mappings
This system is an RP (Auto-RP)

Group(s) 224.0.0.0/4
  RP 150.1.2.2 (?), v2v1
    Info source: 150.1.3.3 (?), elected via Auto-RP
         Uptime: 00:15:51, expires: 00:01:58
R2#

R3#sh ip pim rp
Group: 224.10.10.10, RP: 150.1.2.2, v2, v1, uptime 00:16:02, expires 00:02:53
R3#sh ip pim rp map
PIM Group-to-RP Mappings
This system is an RP-mapping agent (Loopback0)

Group(s) 224.0.0.0/4
  RP 150.1.2.2 (?), v2v1
    Info source: 150.1.2.2 (?), elected via Auto-RP
         Uptime: 00:16:03, expires: 00:02:52
R3#

R4#sh ip pim rp
Group: 224.10.10.10, RP: 150.1.2.2, v2, v1, uptime 00:16:11, expires 00:02:36
R4#sh ip pim rp map
PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4
  RP 150.1.2.2 (?), v2v1
    Info source: 150.1.3.3 (?), elected via Auto-RP
         Uptime: 00:16:13, expires: 00:02:34
R4#

posted by kimiyone @ Thursday, April 21, 2011  0 Comments

WB Vol.1 Multicast - 8.5 PIM Assert

Without any treatment for Assertion

R1

(*, 239.6.6.6), 00:00:35/stopped, RP 0.0.0.0, flags: DC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Serial0/0.1, Forward/Sparse-Dense, 00:00:35/00:00:00
    FastEthernet0/0, Forward/Sparse-Dense, 00:00:35/00:00:00

(155.7.108.10, 239.6.6.6), 00:00:19/00:02:42, flags: PT
  Incoming interface: Serial0/0.1, RPF nbr 155.7.0.5
  Outgoing interface list:
    FastEthernet0/0, Prune/Sparse-Dense, 00:00:20/00:02:39

R4 (Assertion Winner)

(*, 239.6.6.6), 00:00:29/stopped, RP 0.0.0.0, flags: DC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Serial0/1/0, Forward/Sparse-Dense, 00:00:29/00:00:00
    FastEthernet0/1, Forward/Sparse-Dense, 00:00:29/00:00:00

(155.7.108.10, 239.6.6.6), 00:00:13/00:02:48, flags: T
  Incoming interface: Serial0/1/0, RPF nbr 155.7.45.5
  Outgoing interface list:
    FastEthernet0/1, Forward/Sparse-Dense, 00:00:13/00:00:00, A

R5

(*, 239.6.6.6), 00:00:05/stopped, RP 0.0.0.0, flags: D
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Serial0/0/0, Forward/Sparse-Dense, 00:00:05/00:00:00
    Serial0/1/0, Forward/Sparse-Dense, 00:00:05/00:00:00
    FastEthernet0/0, Forward/Sparse-Dense, 00:00:05/00:00:00

(155.7.108.10, 239.6.6.6), 00:00:05/00:03:29, flags: T
  Incoming interface: FastEthernet0/0, RPF nbr 155.7.58.8
  Outgoing interface list:
    Serial0/1/0, Forward/Sparse-Dense, 00:00:05/00:00:00
    Serial0/0/0, Prune/Sparse-Dense, 00:00:04/00:03:24

With changing distance of OSPF

R1 (Assertion Winner)

router ospf 1
 router-id 150.7.1.1
 log-adjacency-changes
 network 150.7.0.0 0.0.255.255 area 0
 network 155.7.0.0 0.0.255.255 area 0
 distance 80

 (*, 239.6.6.6), 00:49:25/stopped, RP 0.0.0.0, flags: DC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Serial0/0.1, Forward/Sparse-Dense, 00:49:25/00:00:00
    FastEthernet0/0, Forward/Sparse-Dense, 00:49:25/00:00:00

(155.7.108.10, 239.6.6.6), 00:00:13/00:02:47, flags: T
  Incoming interface: Serial0/0.1, RPF nbr 155.7.0.5
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse-Dense, 00:00:14/00:00:00, A

R4

(*, 239.6.6.6), 00:49:32/stopped, RP 0.0.0.0, flags: DC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Serial0/1/0, Forward/Sparse-Dense, 00:49:32/00:00:00
    FastEthernet0/1, Forward/Sparse-Dense, 00:49:32/00:00:00

(155.7.108.10, 239.6.6.6), 00:00:20/00:02:45, flags: PT
  Incoming interface: Serial0/1/0, RPF nbr 155.7.45.5
  Outgoing interface list:
    FastEthernet0/1, Prune/Sparse-Dense, 00:00:19/00:02:40

R5

(*, 239.6.6.6), 00:00:21/stopped, RP 0.0.0.0, flags: D
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Serial0/0/0, Forward/Sparse-Dense, 00:00:21/00:00:00
    Serial0/1/0, Forward/Sparse-Dense, 00:00:21/00:00:00
    FastEthernet0/0, Forward/Sparse-Dense, 00:00:21/00:00:00

(155.7.108.10, 239.6.6.6), 00:00:21/00:02:45, flags: T
  Incoming interface: FastEthernet0/0, RPF nbr 155.7.58.8
  Outgoing interface list:
    Serial0/1/0, Prune/Sparse-Dense, 00:00:20/00:02:39
    Serial0/0/0, Forward/Sparse-Dense, 00:00:21/00:00:00

posted by kimiyone @ Thursday, April 21, 2011  0 Comments

WB Vol.1 Multicast - 8.4 PIM Sparse-Dense Mode

R6 (FHR)

(*, 224.0.1.40), 00:33:08/00:02:26, RP 150.7.5.5, flags: SJPCL
  Incoming interface: FastEthernet0/0.146, RPF nbr 155.7.146.4
  Outgoing interface list: Null

R4

(*, 239.0.0.1), 00:00:48/stopped, RP 0.0.0.0, flags: D
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Serial0/1/0, Forward/Sparse-Dense, 00:00:48/00:00:00
    FastEthernet0/1, Forward/Sparse-Dense, 00:00:48/00:00:00

(155.7.146.6, 239.0.0.1), 00:00:48/00:02:16, flags: T
  Incoming interface: FastEthernet0/1, RPF nbr 155.7.146.6
  Outgoing interface list:
    Serial0/1/0, Forward/Sparse-Dense, 00:00:48/00:00:00

R5 (RP for 224.10.10.10, but no RP for 239.0.0.1. It's dense mode group)

(*, 239.0.0.1), 00:00:51/stopped, RP 0.0.0.0, flags: D
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Serial0/1/0, Forward/Sparse-Dense, 00:00:51/00:00:00
    FastEthernet0/0, Forward/Sparse-Dense, 00:00:51/00:00:00

(155.7.146.6, 239.0.0.1), 00:00:51/00:02:14, flags: T
  Incoming interface: Serial0/1/0, RPF nbr 155.7.45.4
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse-Dense, 00:00:51/00:00:00

SW2

(*, 239.0.0.1), 00:01:10/stopped, RP 0.0.0.0, flags: D
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Port-channel1, Forward/Sparse-Dense, 00:01:10/00:00:00
    Vlan58, Forward/Sparse-Dense, 00:01:10/00:00:00

(155.7.146.6, 239.0.0.1), 00:01:10/00:02:06, flags: T
  Incoming interface: Vlan58, RPF nbr 155.7.58.5
  Outgoing interface list:
    Port-channel1, Forward/Sparse-Dense, 00:01:10/00:00:00

SW4 (LHR)

(*, 239.0.0.1), 00:02:32/stopped, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Vlan10, Forward/Sparse-Dense, 00:02:32/00:00:00
    Port-channel1, Forward/Sparse-Dense, 00:02:32/00:00:00

(155.7.146.6, 239.0.0.1), 00:01:04/00:01:58, flags: LT
  Incoming interface: Port-channel1, RPF nbr 155.7.108.8
  Outgoing interface list:
    Vlan10, Forward/Sparse-Dense, 00:01:04/00:00:00, H

posted by kimiyone @ Thursday, April 21, 2011  0 Comments

WB Vol.1 Multicast - 8.3 PIM Sparse Mode

R6 (Multicast Source, FHR)


(*, 224.10.10.10), 00:07:27/stopped, RP 150.7.5.5, flags: SPF
  Incoming interface: FastEthernet0/0.146, RPF nbr 155.7.146.4
  Outgoing interface list: Null
-> it is because no multicast receiver below R4

(155.7.146.6, 224.10.10.10), 00:02:54/00:02:56, flags: PFT
  Incoming interface: FastEthernet0/0.146, RPF nbr 0.0.0.0
  Outgoing interface list: Null
-> FHR does not have OIL interface??

R4

 (*, 224.10.10.10), 00:08:06/stopped, RP 150.7.5.5, flags: SP
  Incoming interface: Serial0/1/0, RPF nbr 155.7.45.5
  Outgoing interface list: Null
-> it is because no multicast receiver below R4

(155.7.146.6, 224.10.10.10), 00:03:32/00:02:49, flags: T
  Incoming interface: FastEthernet0/1, RPF nbr 155.7.146.6
  Outgoing interface list:
    Serial0/1/0, Forward/Sparse, 00:03:32/00:02:54

R5 (RP Router)

(*, 224.10.10.10), 00:08:41/00:02:33, RP 150.7.5.5, flags: S
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 00:08:41/00:02:33

(155.7.146.6, 224.10.10.10), 00:01:09/00:02:24, flags: T
  Incoming interface: Serial0/1/0, RPF nbr 155.7.45.4
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 00:01:09/00:03:21

SW2

(*, 224.10.10.10), 00:07:06/00:03:16, RP 150.7.5.5, flags: S
  Incoming interface: Vlan58, RPF nbr 155.7.58.5
  Outgoing interface list:
    Port-channel1, Forward/Sparse, 00:07:06/00:03:16

(155.7.146.6, 224.10.10.10), 00:00:20/00:03:09, flags:
  Incoming interface: Vlan58, RPF nbr 155.7.58.5
  Outgoing interface list:
    Port-channel1, Forward/Sparse, 00:00:20/00:03:16

SW4 (Multicast Receiver, LHR)

(*, 224.10.10.10), 00:07:52/stopped, RP 150.7.5.5, flags: SJCL
  Incoming interface: Port-channel1, RPF nbr 155.7.108.8
  Outgoing interface list:
    Vlan10, Forward/Sparse, 00:07:52/00:02:20, H

(155.7.146.6, 224.10.10.10), 00:00:08/00:02:59, flags: LJT
  Incoming interface: Port-channel1, RPF nbr 155.7.108.8
  Outgoing interface list:
    Vlan10, Forward/Sparse, 00:00:09/00:02:50, H

posted by kimiyone @ Thursday, April 21, 2011  0 Comments

Sunday, April 10, 2011

RSVP memo

end-to-end QoS model, mimic of circuit-switched network

RSVP is signaling protocol to request certain QoS capabilities from the networks

PSTN と比べるとコール中にnetworkを予約し、コール後に開放する形。
DiffServ QoS model とは反対の考え方

RSVP の中心となる考え方は Flow (a unidirectional stream of packets)
Host X -> Host Y
Host X sends RSVP request (PATH message) to nearest router
 = asks to establish QoS-aware path downstream to Host Y

Requestを受信したrouterは PATH message 内の parameter と available resourceを比較し、すべてokの場合は requestをさらに Host Y に近い routerに転送する。
最後には Host Yに到達し、HostY は Reservation request (RESV message) を Host Xへ
応答する。

Path 内のそれぞれのrouterは要求された QoS parameterが提供可能かどうか確認する、
そして、Requestを上流へ転送する

Senderが Reserve messageを受信すると、いよいよ senderがデータを QoS-capable pathに沿って送る準備ができることを知る。

各routerでは事前にQoS parameterが設定されている。
Flow は unidirectional であることから、2つの reservationがそれぞれの報告に必要になる、packet交換が双方向である場合は。

integrated Services model の場合は、Best Effort, Guaranteed Rate and Controlled Loadが提供される
Best Effort: Qos treatmentを要求しない
Guaranteed Rate: 帯域と遅延のFlowを提供、最も厳しい要求の type of service
Controlled Load: 軽い負荷のネットワークで使われる。帯域は保証されるが、遅延は無保証。

RSVP Reservation: Flowspec と Filterspec
Flowspec: Rspec と Tspec structure から成る
Rspec (Reservation specification) は Class of Service で、予約要求を定義
Tspec (Traffic specification) は Traffic計測のための Token Bucket parameterを定義。 average rateや Burst sizeを定義
これらの structures は Receiverから上流の Senderへのrequestの一部
SenderからのRSVP path は Tspec structureが入っており、それにより経路上のrouterは自分たちのリソースが new flowの bitrateを収容できるか確認する。

Filterspec Structure は sender filterを定義
基本的に、Receiverが準備した reservationをどのリソースが使うことを許されるか、を指定。
通常は communicationは1:1であるが、複数のReceiverに送りたいとき、そして、
それを1つの Reservationをshareしたいときも考えられる。例えば、
many-to-many の conferenceなど。

3つのタイプのfilterがあり、 Fixed Filter (FF), Shared Explicit (SE) and Wildcard Filter (WF).
FF は1つのはっきりとしたreservationを利用するソースが特定されていて、Tspec structure parameter (rate, burst, etc) は single flow にだけ適用される
複数のsenderが居る場合には、receiverは1つずつ別々のreservationを確立する必要がある。

SEは複数のはっきりとしてソースが同じ reservationを使うように特定される。receiverは送信元の IP Address を reservation message 内で指定する

WF はどの senderも reservation を利用することができる。IP Addressの特定は不要。


RSVPはscalabilityに欠ける。Nの二乗のflowが必要になるからである。
しかし、receiverがmulticastの場合には、 RSVPは "reservation merging"という機能が使える。
これは複数の受信者が同じmulticast groupを共有しており、同じsenderに対して reservationを作成する場合、senderへ向かう tree に沿って、上流へ propagateする。
その他の機能拡張は aggregate reservationsが追加されたことであるが、standard RSVP仕様では実装されない。

RSVP は soft-state protocol である。つまり router は RSVP reservationを保持するが、それは routerが RSVP PATH/RESV messageを受信している間だけ。
default では all routerはmessageをバラバラに、30秒間隔で送信。もしも router が特定の RSVP state を持って居る場合、PATH と RESV messageを送りつづけることになる。
もし、PATH が上流から、RESV が下流側から重心されなくなったら、routerは持っていたstateをtimeoutさせる。

RSVP configurationは単純で、single command で RSVP bandwidth と per-flow bandwidth を定義する。 ip rsvp bandwidth
このコマンドは RSVP を enable にし、さらに利用可能にする bandwidth も指定する。
RSVPを interfaceで有効にしないと、routerはRSVP messageをその interface上では
acceptも originateもしない。


上述のコマンドのparameterをどれかでも省略すると、defaultでは interface bandwidth の75%をRSVPに使用し、同量をper-flowでも使用する。

posted by kimiyone @ Sunday, April 10, 2011  0 Comments

Sunday, April 03, 2011

IP SLA

IP SLAs with SNMP traps


(1)
<< Settings >>
 ip sla reaction-configuration

<< debug snmp packet & console messages >>

*Mar  1 01:40:49.727: SNMP: Queuing packet to 10.10.128.130
*Mar  1 01:40:49.727: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 1
 rttMonCtrlAdminTag.1 = 
 rttMonHistoryCollectionAddress.1 = 0A 0A  07 07   
 rttMonCtrlOperConnectionLostOccurred.1 = 1
*Mar  1 01:40:49.743: SNMP: Queuing packet to 10.10.128.130
*Mar  1 01:40:49.743: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 5
 rttMonCtrlAdminTag.1 = 
 rttMonHistoryCollectionAddress.1 = 0A 0A  07 07   
 rttMonCtrl.19.1.2.1 = 8
 rttMonCtrl.19.1.10.1 = 1
 rttMonCtrl.19.1.9.1 = 1
 rttMonCtrl.19.1.5.1 = 0
 rttMonCtrl.19.1.6.1 = 0
SW2#
 rttMonEchoAdminEntry.33.1 = 00 00  00 00  
*Mar  1 01:40:49.979: SNMP: Packet sent via UDP to 10.10.128.130
*Mar  1 01:40:50.235: SNMP: Packet sent via UDP to 10.10.128.130

(2)
<< Settings >>
 ip sla reaction-configuration
 snmp-server enable traps ipsla

<< debug snmp packet & console messages >>
*Mar  1 01:37:34.715: SNMP: Queuing packet to 10.10.128.130
*Mar  1 01:37:34.719: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 1
 rttMonCtrlAdminTag.1 = 
 rttMonHistoryCollectionAddress.1 = 0A 0A  07 07   
 rttMonCtrlOperConnectionLostOccurred.1 = 1
*Mar  1 01:37:34.731: SNMP: Queuing packet to 10.10.128.130
*Mar  1 01:37:34.731: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 5
 rttMonCtrlAdminTag.1 = 
 rttMonHistoryCollectionAddress.1 = 0A 0A  07 07   
 rttMonCtrl.19.1.2.1 = 8
 rttMonCtrl.19.1.10.1 = 1
 rttMonCtrl.19.1.9.1 = 1
 rttMonCtrl.19.1.5.1 = 0
 rttMonCtrl.19.1.6.1 = 0
 rttMonEchoAdminEntry.33.1 = 00 00  00 00  
*Mar  1 01:37:34.971: SNMP: Packet sent via UDP to 10.10.128.130
*Mar  1 01:37:35.227: SNMP: Packet sent via UDP to 10.10.128.130

<< Comparison & Result >>
snmp packets are same as condition (1).

(3)
<< Settings >>
 ip sla reaction-configuration
 ip sla logging traps

<< debug snmp packet & console messages >>
*Mar  1 01:45:04.687: %RTT-4-OPER_CLOSS: condition occurred, entry number = 1
*Mar  1 01:45:04.703: SNMP: Queuing packet to 10.10.128.130
*Mar  1 01:45:04.703: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 1
 rttMonCtrlAdminTag.1 = 
 rttMonHistoryCollectionAddress.1 = 0A 0A  07 07   
 rttMonCtrlOperConnectionLostOccurred.1 = 1
*Mar  1 01:45:04.719: SNMP: Queuing packet to 10.10.128.130
*Mar  1 01:45:04.719: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 5
 rttMonCtrlAdminTag.1 = 
 rttMonHistoryCollectionAddress.1 = 0A 0A  07 07   
 rttMonCtrl.19.1.2.1 = 8
 rttMonCtrl.19.1.10.1 = 1
 rttMonCtrl.19.1.9.1 = 1
 rttMonCtrl.19.1.5.1 = 0
 rttMonCtrl.19.1.6.1 = 0
 rttMonEchoAdminEntry.33.1 = 00 00  00 00  
*Mar  1 01:45:04.739: %RTT-3-IPSLATHRESHOLD: IP SLAs(1): Threshold Occurred for connectionLoss
SW2#
*Mar  1 01:45:04.955: SNMP: Packet sent via UDP to 10.10.128.130
*Mar  1 01:45:05.211: SNMP: Packet sent via UDP to 10.10.128.130

<< Comparison & Result >>
new 2 messages appear
*Mar  1 01:45:04.687: %RTT-4-OPER_CLOSS: condition occurred, entry number = 1
*Mar  1 01:45:04.739: %RTT-3-IPSLATHRESHOLD: IP SLAs(1): Threshold Occurred for connectionLoss

when it's recovered
*Mar  1 01:49:04.687: %RTT-4-OPER_CLOSS: condition cleared, entry number = 1   
*Mar  1 01:49:04.735: %RTT-3-IPSLATHRESHOLD: IP SLAs(1): Threshold Cleared for connectionLoss


(4)
<< Settings >>
 ip sla reaction-configuration
 snmp-server enable traps syslog

<< debug snmp packet & console messages >>
same as condition (2)

<< Comparison & Result >>
same as condition (2)

(5)
<< Settings >>
 ip sla reaction-configuration
 ip sla logging traps
 snmp-server enable traps syslog

** All of 3 commands above are required.



<< debug snmp packet & console messages >>
*Mar  1 01:55:04.687: %RTT-4-OPER_CLOSS: condition occurred, entry number = 1
*Mar  1 01:55:04.723: SNMP: Queuing packet to 10.10.128.130
*Mar  1 01:55:04.727: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 1
 rttMonCtrlAdminTag.1 = 
 rttMonHistoryCollectionAddress.1 = 0A 0A  07 07   
 rttMonCtrlOperConnectionLostOccurred.1 = 1
*Mar  1 01:55:04.747: SNMP: Queuing packet to 10.10.128.130
*Mar  1 01:55:04.747: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 10.10.128.129, gentrap 6, spectrap 5
 rttMonCtrlAdminTag.1 = 
 rttMonHistoryCollectionAddress.1 = 0A 0A  07 07   
 rttMonCtrl.19.1.2.1 = 8
 rttMonCtrl.19.1.10.1 = 1
 rttMonCtrl.19.1.9.1 = 1
 rttMonCtrl.19.1.5.1 = 0
 rttMonCtrl.19.1.6.1 = 0
 rttMonEchoAdminEntry.33.1 = 00 00  00 00  
*Mar  1 01:55:04.767: %RTT-3-IPSLATHRESHOLD: IP SLAs(1): Threshold Occurred for connectionLoss
*Mar  1 01:55:04.775: SNMP: Queuing packet to 10.10.128.130
*Mar  1 01:55:04.775: SNMP: V1 Trap, ent ciscoSyslogMIB.2, addr 10.10.128.129, gentrap 6, spectrap 1
 clogHistoryEntry.2.15 = RTT
 clogHistoryEntry.3.15 = 5
 clogHistoryEntry.4.15 = OPER_CLOSS
 clogHistoryEntry.5.15 = condition occurred, entry number = 1
 clogHistoryEntry.6.15 = 690469
*Mar  1 01:55:04.791: SNMP: Queuing packet to 10.10.128.130
*Mar  1 01:55:04.791: SNMP: V1 Trap, ent ciscoSyslogMIB.2, addr 10.10.128.129, gentrap 6, spectrap 1
 clogHistoryEntry.2.16 = RTT
 clogHistoryEntry.3.16 = 4
 clogHistoryEntry.4.16 = IPSLATHRESHOLD
 clogHistoryEntry.5.16 = IP SLAs(1): Threshold Occurred for connectionLoss
 clogHistoryEntry.6.16 = 690476
*Mar  1 01:55:04.979: SNMP: Packet sent via UDP to 10.10.128.130
*Mar  1 01:55:05.235: SNMP: Packet sent via UDP to 10.10.128.130
*Mar  1 01:55:05.491: SNMP: Packet sent via UDP to 10.10.128.130
*Mar  1 01:55:05.747: SNMP: Packet sent via UDP to 10.10.128.130


<< Comparison & Result >>
Configuration below at SW2 is required.

## SW2 (Trap sendor) ##
ip sla logging traps
ip sla 1
 tcp-connect 10.10.7.7 5000 source-ip 10.10.8.8
 tos 96
 timeout 1000
 threshold 3000
 frequency 15
ip sla reaction-configuration 1 react connectionLoss threshold-type consecutive 1 action-type trapOnly
ip sla schedule 1 start-time now
snmp-server enable traps syslog
snmp-server host 10.10.128.130 public

## SW1 (Trap Receiver) ##
ip sla responder
ip sla responder tcp-connect ipaddress 10.10.7.7 port 5000

posted by kimiyone @ Sunday, April 03, 2011  0 Comments