Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 1 views

    Arti 16

    Uploaded by

    vidit mehta
    arti_16

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Arti 16

    Uploaded by

    vidit mehta
    1 views3 pages
    arti_16

    Original Title

    arti_16

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    arti_16

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    1 views3 pages

    Arti 16

    Uploaded by

    vidit mehta
    arti_16

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 3

    VDOM

    Chapter 9Labs
    - Troubleshooting the BIG-IP System 9-1
    3-7

    Lab 9.2 - SNMP Alerts and Traps


    Objectives:

     Configure the BIG-IP system to send traps to an SNMP management console and view trap
    messages using tcpdump
     Estimated time for completion: 25 minutes

    Lab Requirements:

     Although there is no SNMP management console in the classroom, you can designate your PC as
    an SNMP trap destination, and then use tcp dump to view the output from SNMP traps.

    Configure Traps

    Configure a destination for traps

    1. Configure a destination for traps triggered on BIG-IP. Choose to use EITHER the
    Configuration utility (a) OR tmsh (b) to carry out this step.
    a. Use the Configuration utility to set up a trap destination….

    Configuration utility

    System » SNMP »Traps » Destination and click Create

    Record Properties section


    Version v1
    Community Public (with a capital “P”)
    Destination 10.10.X.30
    Port 162
    When complete, click Finished

    b. …OR use tmsh to set up a trap destination and display the results, then quit tmsh.
    (Substitute your station number for “X” in both locations.) For example:
    (tmos)# modify /sys snmp v1-traps add { tsX {host 10.10.X.30
    community Public} }
    (tmos)# list /sys snmp

    1 VDOM Labs www.vdomlabs.com


    Administering BIG-IP v11 9-1
    3-7
    VDOM
    9-2 Labs Chapter 9 - Troubleshooting the BIG-IP System
    3-7

    Prepare to view trap messages

    2. Use an existing or open a new SSH session to the BIG-IP system, and log in as root.
    3. Start tcpdump to capture your trap traffic.
    config# tcpdump –ni external –Xs 200 udp and host 10.10.X.30 and port 162

    Cause traps to be triggered

    4. Change the receive string of the My_HTTP monitor such that it marks all the pool members in
    http_pool down.
    Q. Did trap messages appear immediately in your tcpdump output? Why or
    why not?

    5. On your tcpdump window, press the <Enter> key several times to insert some space between the
    previous set of trap messages and any new ones that are generated.
    6. Change the receive string of the My_HTTP monitor again such that it marks all the pool
    members in http_pool up again.
    Q. Did trap messages appear immediately in your tcpdump output? Why or
    why not?

    7. Stop your tcpdump by pressing<Ctrl-C>.


    8. Go look at the SNMP alerts that are pre-configured on BIG-IP.
    config# less /etc/alertd/alert.conf

    Optional tcpdump Lab Steps


    Use the tcpdump command to examine BIG-IP local traffic:
    9. Capture the traffic between BIG-IP and the pool member 172.16.20.2:80. Once you start the
    tcpdump, open a session with http://10.10.X.100 and refresh the screen a few times. How
    frequently does the TCP connection (syn/syn-ack/ack) appear in your tcpdump output? Is the
    TCP connection process apparent?
    10. Capture the traffic between your PC and BIG-IP on port 22 (SSH). Limit the number of packets
    that are captured. Did your tcpdump output show a connection process?

    2 VDOM Labs www.vdomlabs.com


    9-2 Administering BIG-IP v11
    3-7
    VDOM Labs 3-7

    Expected results and troubleshooting

    As with the remote syslog server lab, when you configured the My_HTTP monitor such that the health
    check would fail for all pool members, you had to wait for the period defined by the monitor’s timeout
    value before the log messages are generated that trigger the SNMP trap messages. However, when you
    reset My_HTTP to allow for a successful test to all pool members, as soon as the BIG-IP system receives
    a successful test response, he marks the pool member available. As statuses change, a series of local
    traffic log messages are written that, in turn, trigger more SNMP trap messages.
    Depending on how far down in the alert.conf file you scrolled, you may or may not have come across the
    SNMP traps that relate to an LTM virtual server becoming unavailable or available.

    Clean-up at end of lab

    11. Delete the SNMP trap destination 10.10.4.30 you created at the start of this lab. Use the same
    method as you used to create the destination: either the GUI (System » SNMP : Traps :
    Destination) or tmsh: tmsh modify /sys snmp v1-traps delete { tsX}

    (Optional) Continue with Lab 9.3: Remote Syslog Server Lab

    Administering BIG-IP v11 11-9


    3 VDOM Labs www.vdomlabs.com
    3-7

    You might also like