Scribd Logo
Upload

Welcome to Scribd!

  • 723 views

    A10 Points To Remember Before Operating The Load Balancer

    Uploaded by

    sanju_81
    The document provides an overview of commands and configurations for operating an A10 load balancer. It discusses checking device information and active/standby status, installing and removing real servers, and monitoring resources, traffic, and health. Traps sent for failures and statistical MIBs for monitoring traffic, disks, processors and memory are also outlined.

    Copyright:

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

    A10 Points To Remember Before Operating The Load Balancer

    Uploaded by

    sanju_81
    723 views13 pages
    The document provides an overview of commands and configurations for operating an A10 load balancer. It discusses checking device information and active/standby status, installing and removing real servers, and monitoring resources, traffic, and health. Traps sent for failures and statistical MIBs for monitoring traffic, disks, processors and memory are also outlined.

    Original Description:

    a10 slb

    Original Title

    A10 Points to Remember Before Operating the Load Balancer

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document provides an overview of commands and configurations for operating an A10 load balancer. It discusses checking device information and active/standby status, installing and removing real servers, and monitoring resources, traffic, and health. Traps sent for failures and statistical MIBs for monitoring traffic, disks, processors and memory are also outlined.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    723 views13 pages

    A10 Points To Remember Before Operating The Load Balancer

    Uploaded by

    sanju_81
    The document provides an overview of commands and configurations for operating an A10 load balancer. It discusses checking device information and active/standby status, installing and removing real servers, and monitoring resources, traffic, and health. Traps sent for failures and statistical MIBs for monitoring traffic, disks, processors and memory are also outlined.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 13
    At a glance
    Powered by AI
    The document discusses various commands, configurations, and monitoring techniques for operating an A10 load balancer.

    Some important commands include show version, show ha, and ha force-self-standby for checking active/standby status and performing switches. Other commands configure real servers, service groups, and more.

    You can monitor resource usage with commands like show cpu and show memory. Traffic can be monitored on a virtual server, service group, server, or interface level with commands like show slb virtual-server.

    A10 Points to remember before

    operating the load balancer


    We will summarize the minimum knowledge necessary for operating the A10
    series of A10.

    ※ BIG-IP will be famous as a device that provides similar functions.

    ◆ Command
    ※ The transition to the enable mode is omitted

    【Equipment information】
    ● Confirm version, other device information
    # show version

    [Operation, operation during failure]


    ● Confirm whether Active or Standby
    # show ha

    ● Active / standby switching


    Whether Active or Standby is also displayed at the prompt.
    The command is executed on the active side.
    # configure
    (config) # ha force-self-standby

    ● Active / standby switch back


    On the Standby side, the previous setting is invalidated,
    (config) # no ha force-self-standby

    Execute the command below again on the switched new active side.
    (config) # ha force-self-standby
    ● Real server installation
    # configure
    (config) # slb server $ Real server name
    (config-real server) # enable

    ● Detachment of real servers


    # configure
    (config) # slb server $ Real server name
    (config-real server) # disable

    ● Change number of connections


    # configure
    (config) # slb server $ Real server name
    (config-real server) # conn-limit XXXX

    【resource】
    · Display utilization rate for each Data CPU core
    # show cpu

    ● Display memory usage rate


    # show memory system

    【traffic】
    ● Display load balancing status on a virtual server basis
    # show slb virtual-server
    ※ past statistics (maximum traffic etc etc) can not
    be watched without putting the extended-stats key

    For checking the health check status, it is easier to add a bind option
    # show slb virtual-server bind

    ● Display load balancing status by service group


    # show slb service-group
    ● Display load balancing status on a server basis
    # show slb server

    ● Server health check status display


    # show health stat

    ● Interface status and display of various counters


    # show statistics interface

    ● Summary display of SLB session


    # show session brief

    Display of persistence table


    # show session persist src-ip / dst-ip

    It is also possible to delete the persistence table.


    By initializing the table there is a possibility that the bias of the traffic etc.
    can be made homogeneous.
    # clear session persist src-ip / dst-ip

    ● Arp table display


    # show arp

    ● MAC table display


    # show mac

    ● Display IP FIB table


    # show ip fib

    ● Display IP Rouging Table (RIB)


    # show ip route

    ● Status display of L2 / 3 packet processing


    # show slb switch
    【CONFIG】
    ● Configuration confirmation
    # show startup-config

    # show running-config

    ● Save
    # write memory

    ● Configuration synchronization
    Perform on the active side.
    (config) # ha sync all to-running-config

    (config) # ha sync all to-startup-config

    【debug】
    ● View saved system logs on AX disk
    # show log

    ● Output a snapshot of the current system and process related status


    information
    # show techsupport

    ● Check main unit temperature, FAN, power supply status


    # show environment

    ● Saving log information


    # backup log ftp: //*.*.* .* / max_backup.tgz
    User name []? ****
    Password []? ****
    ※ tftp, ftp, scp, rcp possible for uploading protocols
    Packet capture
    Change the mode.
    # axdebug

    Settings for defining (narrowing down) the filter to be captured


    (axdebug) # filter 1
    (axdebug - filter: 1) # ip 1.2.3.4 / 32

    Definition of the number of packets to capture


    ax (axdebug) # count <0-65535>
    * The default is 3000 packets. 0 with no upper limit on setting

    Definition of capture time


    (axdebug) # timeout <0-65535>
    * Set in minutes. Default 5 minutes. 0 with no upper limit on setting

    Start capture
    (axdebug) # capture non-dispaly save <file name>

    Check status of capture


    (axdebug) # show axdebug status

    Confirm capture file


    (axdebug) #show axdebug file

    Stop capture
    ( axdebug) # no axdebug

    Exporting the capture file


    ( axdebug) # export axdebug file_name?
    use-mgmt-port Use management port as source port
    tftp: Remote file path of tftp: file system (Format:
    tftp: // host / file)
    ftp: Remote file path of ftp: file system (Format:
    ftp: // [user @] host [: port] / file)
    scp: Remote file path of scp: file system (Format:
    scp: // [user @] host / file)
    rcp: Remote file path of rcp: file system (Format:
    rcp: // [user @] host / file)
    * Capture file is exported with ZIP compressed in pcap format

    Delete capture file


    ( axdebug) # delete <file_name>

    ◆ Change settings
    【Update white and black list】
    In some cases you may be controlling a server that sorts
    based on the IP address of the connection source.
    Leave the procedure to update the IP list.

    Let's assume that in slb template policy we define as follows.

    It manages the IP address group which is ip_list (name is


    ip_list_old)
    When the source IP address matches in the list,
    Skip to http_match group.

    slb template policy bwlist_http


    bw-list name ip_list_old
    bw-list id 1 service-group http_match
    (Short)

    Update this IP list as follows.


    Before change: ip_list_old
    Before change: ip_list_new
    1. Import of IP list Beforehand, IP list must be placed in
    arbitrary server.

    IP list example
    network xxx 0/24 1
    network yyy 0/24 1
    network zzz 0/24 1
    ※ The last number is the id of the bw-list specified in
    template's policy.

    # import bw-list ip-list_new scp: // <ID> @


    <server address> / <path> / <list name>

    2. Check the IP list


    # show bw-list
    Applied i-list is displayed

    # show bw-list ip-list_new detail


    * In the GUI, all lines are not displayed due to the
    specifications, so check from the CLI

    3. Update the IP list


    Replace with ip_list_new.
    New IP list is applied immediately after command execution.
    # conf terminal
    (config) # slb template policy bwlist_http
    bw-list name ip_list_new
    4. Delete unnecessary IP list
    # conf terminal
    (config) # no bw-list ip_list_old

    In fact, for back-off, leave at least one generation ago, delete


    items two generations ago,
    The policy should be better.

    5. Save configuration

    6. There are two caveats before config sync synchronization.


    · Procedure 1 (IP list import) must be performed also on peer
    devices
    · Also, make IP list names available on both devices

    ◆ TRAP contents when failure occurs


    ● trap contents
    Warning message OID

    Level CRITICAL
    axSystemShutdown
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.2
    axFan1Failure
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.4
    axFan2Failure
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.5
    axFan3Failure
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.6
    axUpperPowerSupplyFailure
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.9
    axLowerPowerSupplyFailure
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.10
    axPrimaryHardDiskFailure
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.11
    axSecondaryHardDiskFailure
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.12
    axSystemRestart.
    1.3.6.1.4.1.22610.2.4.3.12.2.1.15
    axHAStandby .1.3.6.1.4.1.22610.2.4.3.12.2.2.1
    axServerDown.
    1.3.6.1.4.1.22610.2.4.3.12.2.2.6
    axServiceDown.
    1.3.6.1.4.1.22610.2.4.3.12.2.2.4
    axVirtualServerPortDown
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.12

    Level NOTICE
    axSystemTempHigh
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.3
    axHardDiskUsageHigh
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.13
    axMemoryUsageHigh
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.14
    axSystemDropPacketEvent
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.16
    axSystemControlCpuHigh
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.18
    axSystemDataCpuHigh
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.19
    axHAActive .1.3.6.1.4.1.22610.2.4.3.12.2.2.2
    axHAActiveActive
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.3
    axServerConnLimit
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.8
    axServiceConnLimit
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.10
    axServerConnRateLimit
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.19
    axServiceConnRateLimit
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.20
    axNetworkTrunkPortsThreshold
    .1.3.6.1.4.1.22610.2.4.3.12.2.3.1
    axApplicationBufferReachLimit
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.14
    axVirtualServerReachConnLimit
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.17
    axVirtualServerPortReachConnLimit
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.15
    axVirtualServerPortReachConnRateLimit
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.16
    axVirtualServerReachConnRateLimit
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.18

    Level INFO
    axSystemStart.
    1.3.6.1.4.1.22610.2.4.3.12.2.1.1
    axSystemRelieveDropPacketEvent
    .1.3.6.1.4.1.22610.2.4.3.12.2.1.17
    axServiceUp.1.3.6.1.4.1.22610.2.4.3.12.2.2.5
    axServerUp .1.3.6.1.4.1.22610.2.4.3.12.2.2.7
    axServerConnResume
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.9
    axServiceConnResume
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.11
    axVirtualServerPortUp
    .1.3.6.1.4.1.22610.2.4.3.12.2.2.13

    ◆ mib for obtaining statistical information


    【traffic】
    ● axVirtualServerStatTable
    Get the virtual server statistics table.

    axVirtualServerStatName
    .1.3.6.1.4.1.22610.2.4.3.4.2.1.1.2

    axVirtualServerStatCurConns
    .1.3.6.1.4.1.22610.2.4.3.4.2.1.1.9

    ● axServiceGroupStatTable
    Get the service group statistics table. This table shows statistics for service
    groups.

    axServiceGroupStatName
    .1.3.6.1.4.1.22610.2.4.3.3.2.1.1.1

    axServiceGroupStatCurConns
    .1.3.6.1.4.1.22610.2.4.3.3.2.1.1.7

    ● axServiceGroupMemberStatTable
    Get the service group member statistics table.

    axServiceGroupMemberStatName
    .1.3.6.1.4.1.22610.2.4.3.3.4.1.1.1
    axServiceGroupMemberStatCurConns
    .1.3.6.1.4.1.22610.2.4.3.3.4.1.1.11

    【disk】
    ● axSysDiskTotalSpace
    The space is measured in Megabytes (MB).
    .1.3.6.1.4.1.22610.2.4.1.4.1

    ● axSysDiskFreeSpace
    The space is measured in MB.
    .1.3.6.1.4.1.22610.2.4.1.4.2

    【Processor】
    ● axSysAverageControlCpuUsage
    Description Gets the average control CPU utilization over the last 5
    seconds.
    .1.3.6.1.4.1.22610.2.4.1.3.4

    ● axSysAverageDataCpuUsage
    Description Gets the average data CPU utilization over the last 5 seconds.
    .1.3.6.1.4.1.22610.2.4.1.3.5

    【memory】
    ● axSysMemoryTotal
    Memory is measured in Kilobytes (Kb).
    .1.3.6.1.4.1.22610.2.4.1.2.1

    ● axSysMemoryUsage
    Memory is measured in Kb.
    .1.3.6.1.4.1.22610.2.4.1.2.2
    Contributor alpha.netzilla Time: 1: 57
    Email ThisBlogThis! Share to Twitter Share to Facebook Share
    to Pinterest
    Label: L4

    You might also like