DX - Load Balancing & Application Acceleration
Reply
Contributor
NDCool
Posts: 243
Registered: ‎11-26-2007
0

Cluster in DX

Hi All,

 

i have some issue from my customer about their clusters.

They already set each ip will have maximum connection is 20 and weight 1, example for this ip's 10.121.2.229

cluster settings

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

but, when we saw at that ip's statistics the connection will be more than we set.

cluster statistics

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

why it can be like that ?

now they have monitoring tools to see how many connection on thier http server, some time the server get connection more than they set on dx.

when we active snmp on dx, it's possible to monitoring each cluster ip's connections with snmp tools ?? which snmp tools can be used ?

 

thanks

Andi.

 

 

 

Regards,

ND
Recognized Expert
MattS
Posts: 205
Registered: ‎11-06-2007
0

Re: Cluster in DX

Hi,

 

 

The stats screen is reporting the DX connections to the target server.  As the DX could have up to to 20 active client requests at a time, the DX could open up more than 20 connections to the target server if previously opened connections were not fully closed.  Note also that by default the DX maintains 6 standing connections to the server, so you should always see a minimum of 6 target server connections.   Basically, as the DX is proxying the client requests there is not a direct correlation between the amount of client connections and the target server connections, especially if multiplexing of the client requests is occurring (enabled by default by  'set cluster <name> connbind enabled')

 

SNMP will give more detailed statistics on client-side connections.   The MIB is available via the WebUI at the bottom of the page of Admin ->SNMP where the 'Download MIBs' dropdown menu is.   The DX-STATS-MIB has per cluster statistics:

 

ClusterIOStatsEntry ::=
        SEQUENCE {
        clusterIOStatsIndex
           Integer32,
        clusterIOStatsListenSessionActive
           Counter64,
        clusterIOStatsListenSessionTotal
           Counter64,
        clusterIOStatsListenSessionRefused
           Counter64,
        clusterIOStatsListenReqActive
           Counter64,
        clusterIOStatsListenReqTotal
           Counter64,
        clusterIOStatsListenBytesIn
           Counter64,
        clusterIOStatsListenBytesOut
           Counter64,
        clusterIOStatsTargetBytesIn
           Counter64,
        clusterIOStatsTargetBytesOut
           Counter64,
        clusterIOStatsListenDeadStickyThost
           Counter64,
        clusterIOStatsListenDeletedStickyThost
           Counter64,
        clusterIOStatsTargetDownStickyThost
           Counter64
        }

 

 

 

I loaded this MIB in a MIBbrowser and found the OID for these variables starts with 1.3.6.1.4.1.6213.2.4.2.1, so I copied the DX MIBs to the default MIB directory on a FreeBSD box (/usr/local/share/snmp/mibs) and then do the following snmpwalk:

 

 

$ snmpwalk -v2c -m +DX-STATS-MIB -c public 172.26.31.206 1.3.6.1.4.1.6213.2.4.2.1
 

[admin@victoria /tftpboot/DX/MIBs/5.3.6]$ snmpwalk -v2c -m +DX-STATS-MIB -c public 172.26.31.206 1.3.6.1.4.1.6213.2.4.2.1
DX-STATS-MIB::clusterIOStatsListenSessionActive.1 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenSessionActive.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenSessionTotal.1 = Counter64: 10330
DX-STATS-MIB::clusterIOStatsListenSessionTotal.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenSessionRefused.1 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenSessionRefused.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenBytesIn.1 = Counter64: 1186041
DX-STATS-MIB::clusterIOStatsListenBytesIn.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenBytesOut.1 = Counter64: 4276724
DX-STATS-MIB::clusterIOStatsListenBytesOut.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsTargetBytesIn.1 = Counter64: 3580161
DX-STATS-MIB::clusterIOStatsTargetBytesIn.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsTargetBytesOut.1 = Counter64: 2012432
DX-STATS-MIB::clusterIOStatsTargetBytesOut.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenDeadStickyThost.1 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenDeadStickyThost.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenDeletedStickyThost.1 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenDeletedStickyThost.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsTargetDownStickyThost.1 = Counter64: 0
DX-STATS-MIB::clusterIOStatsTargetDownStickyThost.2 = Counter64: 0

where the indexes at the end of the name .1 and .2 reference the two dfferent clusters I have configured.

 

 

You can use SNMP to poll these values to monitor the cluster statistics, for example you could use MRTG/Cricket to tgraph these values over time.

New User
monachus
Posts: 2
Registered: ‎03-27-2009
0

Re: Cluster in DX

We have 2 DX 3280s and I'm unable to get stats off of them.  When I snmpwalk the clusterStats OID it shows me only the names of my clusters and if they're Up.  I don't get any statistics that the MIB shows me I should (and what you see in your example below).  Is there some additional DX magic that has to happen in order for the statistics to appear in SNMP?

 

Adrian

Recognized Expert
MattS
Posts: 205
Registered: ‎11-06-2007
0

Re: Cluster in DX

 

 I think the problem is that you are using SNMPv1 for the snmpwalk rather than SNMPv2c.  v1 can only read 32 bit counters while v2c supports 32 and 64 bit counters.   With snmpwalk you use the -v switch to set which version to use, so for SNMPv1 I see:

 

 

$ snmpwalk -v1 -m +DX-STATS-MIB -c public 172.26.31.206 1.3.6.1.4.1.6213.2.4.2
DX-STATS-MIB::clusterSSLStatsClusterName.1 = STRING: foo
DX-STATS-MIB::clusterSSLStatsClusterName.2 = STRING: 1
DX-STATS-MIB::clusterSSLStatsClusterName.3 = STRING: 2
DX-STATS-MIB::clusterOperStatusClusterName.1 = STRING: foo
DX-STATS-MIB::clusterOperStatusClusterName.2 = STRING: 1
DX-STATS-MIB::clusterOperStatusClusterName.3 = STRING: 2
DX-STATS-MIB::clusterOperStatusStatus.1 = INTEGER: up(1)
DX-STATS-MIB::clusterOperStatusStatus.2 = INTEGER: down(0)
DX-STATS-MIB::clusterOperStatusStatus.3 = INTEGER: down(0)

 

If I use -v2c I receive more detail:

 

$ snmpwalk -v2c -m +DX-STATS-MIB -c public 172.26.31.206 1.3.6.1.4.1.6213.2.4.2 | less
DX-STATS-MIB::clusterIOStatsListenSessionActive.1 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenSessionActive.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenSessionActive.3 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenSessionTotal.1 = Counter64: 2
DX-STATS-MIB::clusterIOStatsListenSessionTotal.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenSessionTotal.3 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenSessionRefused.1 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenSessionRefused.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenSessionRefused.3 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenBytesIn.1 = Counter64: 46
DX-STATS-MIB::clusterIOStatsListenBytesIn.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenBytesIn.3 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenBytesOut.1 = Counter64: 4351172
DX-STATS-MIB::clusterIOStatsListenBytesOut.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenBytesOut.3 = Counter64: 0
DX-STATS-MIB::clusterIOStatsTargetBytesIn.1 = Counter64: 4351198
DX-STATS-MIB::clusterIOStatsTargetBytesIn.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsTargetBytesIn.3 = Counter64: 0
DX-STATS-MIB::clusterIOStatsTargetBytesOut.1 = Counter64: 4367338
DX-STATS-MIB::clusterIOStatsTargetBytesOut.2 = Counter64: 0
DX-STATS-MIB::clusterIOStatsTargetBytesOut.3 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenDeadStickyThost.1 = Counter64: 0
DX-STATS-MIB::clusterIOStatsListenDeadStickyThost.2 = Counter64: 0
<cut>

New User
monachus
Posts: 2
Registered: ‎03-27-2009
0

Re: Cluster in DX

Genius.  I should have seen that.  We normally use snmp v1 for the devices we poll.  Thanks!
Copyright© 1999-2013 Juniper Networks, Inc. All rights reserved.