show services traffic-load-balance statistics
Syntax
show services traffic-load-balance statistics <extensive> <group group-name> <instance instance-name> <num-instances number> <real-service real-service-name> <summary> <virtual-service virtual-service-name>
Description
The basic form of the command displays the list of real servers associated with this group and traffic statistics, including packet count and byte count
Options
none | Display information about the load-balancing statistics in brief. |
extensive | (Optional) Display extensive information about the traffic load-balancing statistics. |
group group-name | (Optional) Display load-balancing statistics for a specified group of load-balancer servers. |
instance instance-name | (Optional) Display load-balancing statistics for a specific traffic load balancer (TLB) instance. |
num-instances number | (Optional) Display load-balancing statistics for a specified number of TLB instances. |
real-service real-service-name | (Optional) Display load-balancing statistics for a specified load balancer serve. |
summary | (Optional) Display summary information about the traffic load-balancing statistics. |
virtual-service virtual-service-name | (Optional) Display load-balancing statistics for a specified TLB virtual service. |
Required Privilege Level
view
Output Fields
Table 1 lists the output fields for the show services traffic-load-balance
statistics
command. Output fields are listed in the approximate
order in which they appear.
Field Name |
Field Description |
Level of Output |
---|---|---|
|
Name of the traffic load balancer (TLB) instance that contains the load-distribution-related configuration settings. |
All levels |
|
Name of the services interface used for the TLB instance to provide one-to-one redundancy for server health monitoring. For MS-MPC services card, this is the name of the aggregated multiservices (AMS) interface or “ms-slot/pic/port”. For Next Gen Services and the MX-SPC3 services card, this is the name of the VMS interface or “vms-slot/pic/port”. |
All levels |
|
Inter-process communications (IPC) status between the TLB daemon (traffic-dird) and the health checking daemon (net-monitord).
|
All levels |
|
Logical interface type. |
All levels |
|
Time that the programmed VIP routes are kept intact after connectivity between traffic-dird and net-monitord daemons is lost. If connectivity is not reestablished within this time, all the VIP routes are withdrawn. |
All levels |
|
Name of the virtual service for the TLB instance. The virtual service provides an address that is associated with the group of servers to which traffic is directed. |
none
|
|
Name of the virtual service for the TLB instance. The virtual service provides an address that is associated with the group of servers to which traffic is directed. |
|
|
Name of the routing instance used for the virtual service. |
none
|
|
IP address of the virtual service. |
none
|
|
IP address of the virtual service. |
|
|
Operational state of the virtual service. |
|
|
Number of packets originating from the clients that the TLB instance virtual service processes for load balancing to next-hop servers. |
|
|
Number of bytes originating from the clients that the TLB instance virtual service processes for load balancing to next-hop servers. |
|
|
Number of packets returning from the next-hop servers that the TLB instance virtual service processes and forwards to the clients. |
|
|
Number of bytes returning from the next-hop servers that the TLB instance virtual service processes and forwards to the clients. |
|
|
Virtual service processing mode.
|
none
|
|
Server group name used for the virtual service. |
none
|
|
Number of the subunit of the multiservice interface used for health checking. |
none
|
|
Number of times the status of the TLB server group was down. |
|
|
Virtual service protocol, either tcp or udp. In translated mode, packets destined to the virtual service IP address+port number+protocol are load balanced and then replaced by the real service IP address and server listening port number. |
none
|
|
Virtual service port number. In translated mode, packets destined to the virtual service IP address+port number+protocol are load balanced and then replaced by the real service IP address and server listening port number. |
none
|
|
Real service port number that replaces the virtual service port number. In translated mode, packets destined to the virtual service IP address+port number+protocol are load balanced and then replaced by the real service IP address and server listening port number. |
none
|
|
Index number of the demultiplexing next hop for the virtual service. Index number is unique for a VIP, routing-instance, and protocol combination. The demultiplexing next hop is responsible for port-based demultiplexing of traffic to the load-balancing next hop for session distribution. |
none
|
|
Client connection identifier assigned to the TLB daemon (traffic-dird) by the firewall daemon (dfwd) when the daemons are successfully connected. |
|
|
Time, in seconds, that passes after the traffic-dird daemon comes up until the traffic-dird programs the distribution table on the Packet Forwarding Engine. |
|
|
Indicates whether the option that allows a server to rejoin the group automatically when it comes up is enabled or not. |
|
|
Routing metric assigned to the virtual service. A lower metric makes a route more preferred. |
|
|
Number of times the status of the virtual service was down. |
|
|
Hash key parameter used for load balancing. Hash keys supported in the ingress direction are protocol, source IP address, and destination IP address. |
|
|
Index number of the next-hop for the virtual service. A group of servers function as a pool for next-hop session distribution. |
none
|
|
Period of time for which the virtual service is up, in the format number-of-days hh:mm:ss. |
none
|
|
Starting in Junos OS Release 16.1R6 and 18.2R1, number of real servers that are up for the specified virtual service or server group. |
none |
|
Starting in Junos OS Release 16.1R6 and 18.2R1, number of real servers that are down for the specified virtual service or server group. |
none |
|
Number of packets originating from the clients that the TLB instance virtual service processes for load balancing to next-hop servers. |
none
|
|
Number of bytes originating from the clients that the TLB instance virtual service processes for load balancing to next-hop servers. |
none
|
|
Number of packets returning from the next-hop servers that the TLB instance virtual service processes and forwards to the clients. |
none
|
|
Number of bytes returning from the next-hop servers that the TLB instance virtual service processes and forwards to the clients. |
none
|
|
Number of network monitoring profiles that are used to monitor the health of servers used in TLB session distribution. |
|
|
Number of real services that are functional and active. |
|
|
Total number of real services in different states. |
|
|
Unique index number associated with the network monitoring profile. Network monitoring profiles are used to monitor the health of servers used in TLB session distribution. |
|
|
Name configured for the network monitoring profile. |
|
|
Probe type used to examine the health of servers. TLB supports ICMP, TCP, and HTTP health check probes to monitor the health of servers in a group. |
|
|
Frequency, in number of seconds, at which health check probes are sent. |
|
|
Number of failure retries, after which the real service is tagged as down. |
|
|
Number of successful retries after which the real service is tagged as up. |
|
|
Name of the TLB server (also referred to as real service). The name is the identifier for a server to which sessions can be distributed using the server distribution table in conjunction with the session distribution API. |
none |
|
IP address of the configured real service. |
none |
|
Operational state of the TLB server. |
none |
|
Number of packets originating from the clients that the TLB instance virtual service sends to the real service. |
none |
|
Number of bytes originating from the clients that the TLB instance virtual service sends to the real service next-hop server. |
none |
|
Number of packets returning from the real service next-hop server that the TLB instance virtual service processes and forwards to the clients. |
none |
|
Number of bytes returning from the real service next-hop server that the TLB instance virtual service processes and forwards to the clients. |
none |
|
Name of the real service used for traffic load-balancing. |
|
|
Name of the routing instance on which the real service is configured. |
|
|
IP address of the configured real service. |
|
|
Name of the server group for real service. |
|
|
Administrative state of the real service, such as |
|
|
Operational state of the real service, such as |
|
|
Number of probes for which the status of the server whose health is checked is observed to be up. If a server group is configured for dual health check, a real service is declared to be UP only if both health-check probes are simultaneously UP; otherwise a real service declared to be DOWN. |
|
|
Number of probes for which the status of the server whose health is checked is observed to be down. |
|
|
Number of events that caused a server that was previously down and later operational to rejoin a group of real services for load-balancing. |
|
|
Number of TLB events that identified a virtual service or real service to be up. |
|
|
Number of TLB events that identified a virtual service or real service to be down. |
|
|
Number of packets originating from the clients that the TLB instance virtual service sends to the real service. |
|
|
Number of bytes originating from the clients that the TLB instance virtual service sends to the real service next-hop server. |
|
|
Number of packets returning from the real service next-hop server that the TLB instance virtual service processes and forwards to the clients. |
|
|
Number of bytes returning from the real service next-hop server that the TLB instance virtual service processes and forwards to the clients. |
|
|
Number of health-monitoring probes sent from the TLB health check daemon. |
|
|
Number of health-monitoring probes sent from the TLB health check daemon that were successful. |
|
|
Number of health-monitoring probes attempted to be sent from the TLB health check daemon that failed. |
|
|
Number of health-monitoring probes attempted to be sent from the TLB health check daemon that were unsuccessfully initiated. |
|
|
Status of the health-check probe, such as |
|
|
Number of health-check probe requests transmitted from the TLB health check daemon. |
|
|
Number of successful health-check probe requests transmitted from the TLB health check daemon. |
|
|
Number of failed health-check probe requests transmitted from the TLB health check daemon. |
|
|
Number of times the TLB health check daemon was unable to initiate transmission of a extensive health-check probe. |
|
|
Number of health-check probe requests transmitted from the TLB health check daemon that were consecutively successful. |
|
|
Number of health-check probe requests transmitted from the TLB health check daemon that failed for two successive times. |
|
Sample Output
- show services traffic-load-balance statistics
- show services traffic-load-balance statistics extensive
- show services traffic-load-balance statistics summary
show services traffic-load-balance statistics
user@host> show services traffic-load-balance statistics Traffic load balance instance name : lb1 Multi services interface name : ms-3/0/0 Interface state : UP Interface type : Multi services Route hold timer : 180 Active real service count : 0 Total real service count : 100 Traffic load balance virtual svc name : v1 IP address : 0.0.0.0 Virtual service mode : Layer-2 based Direct Server Return mode Routing instance name : internal-client-vrf Traffic load balance group name : g1 Health check interface subunit : 40 Demux Nexthop index : N/A Nexthop index : 840 Up time : 2d 19:09 Real Server Up count : 1 Real Server Down count : 1 Total packet sent count : 0 Total byte sent count : 0 Real service Address Sts Packet Sent Byte Sent Packet Recv Byte Recv r11 203.0.113.11 UP 0 0 0 0 r10 203.0.113.10 UP 0 0 0 0 Traffic load balance virtual svc name : v2 IP address : 192.0.2.11 Virtual service mode : Translate mode Routing instance name : msp-tproxy-forwarding1 Traffic load balance group name : g2 Health check interface subunit : 50 Protocol : tcp Port number : 8080 Server Listening Port Number : 8084 Demux Nexthop index : 536 Nexthop index : 539 Up time : 2d 19:06 Total packet sent count : 0 Total byte sent count : 0 Total packet received count : 0 Total byte received count : 0 Real service Address Sts Packet Sent Byte Sent Packet Recv Byte Recv r12 203.0.113.12 UP 0 0 0 0 r13 203.0.113.13 UP 0 0 0 0
show services traffic-load-balance statistics extensive
user@host> show services traffic-load-balance statistics extensive Traffic Load Balance General Information DFW client-id : 39 Traffic load balance instance name : lb1 Multi services interface name : ms-3/0/0 Interface state : UP Interface type : Multi services Route hold timer : 180 Active real service count : 0 Total real service count : 100 Traffic load balance virtual svc name : v1 IP address : 0.0.0.0 Virtual service mode : Layer-2 based Direct Server Return mode Routing instance name : internal-client-vrf Traffic load balance group name : g1 Traffic load balance group warmup time: 15 Traffic load balance group auto-rejoin: TRUE Health check interface subunit : 40 Traffic load balance group down count : 1 Route metric : 1 Virtual service down count : 1 Traffic load balance hash method : source Network monitoring profile count : 1 Active real service count : 2 Total real service count : 2 Demux Nexthop index : N/A Nexthop index : 840 Up time : 2d 19:09 Total packet sent count : 0 Total byte sent count : 0 Total packet received count : 0 Total byte received count : 0 Network monitoring profile index : 1 Network monitoring profile name : prof1 Probe type : ICMP Probe interval : 5 Probe failure retry count : 5 Probe recovery retry count : 3 Traffic load balance real svc name : r11 Routing instance name : server-vrf10 IP address : 203.0.113.11 Traffic load balance group name : g1 Admin state : UP Oper state : UP Network monitoring probe up count : 1 Network monitoring probe down count : 0 Total rejoin event count : 0 Total up event count : 1 Total down event count : 0 Real Service packet sent count : 0 Real Service byte sent count : 0 Total probe sent : 47939 Total probe success : 47918 Total probe fail : 21 Total probe sent failed : 0 Network monitoring profile index : 1 Network monitoring profile name : prof1 Probe type : ICMP Probe state : UP Probe sent : 47939 Probe success : 47918 Probe fail : 21 Probe sent failed : 0 Probe consecutive success : 10090 Probe consecutive fail : 0 Traffic load balance real svc name : r10 Routing instance name : server-vrf10 IP address : 203.0.113.10 Traffic load balance group name : g1 Admin state : UP Oper state : UP Network monitoring probe up count : 1 Network monitoring probe down count : 0 Total rejoin event count : 0 Total up event count : 1 Total down event count : 0 Real Service packet sent count : 0 Real Service byte sent count : 0 Total probe sent : 47939 Total probe success : 47917 Total probe fail : 22 Total probe sent failed : 0 Network monitoring profile index : 1 Network monitoring profile name : prof1 Probe type : ICMP Probe state : UP Probe sent : 47939 Probe success : 47917 Probe fail : 22 Probe sent failed : 0 Probe consecutive success : 10090 Probe consecutive fail : 0 Traffic load balance virtual svc name : v2 IP address : 192.0.2.11 Virtual service mode : Translate mode Routing instance name : msp-tproxy-forwarding1 Traffic load balance group name : g2 Traffic load balance group warmup time: 15 Traffic load balance group auto-rejoin: TRUE Health check interface subunit : 50 Traffic load balance group down count : 1 Protocol : tcp Port number : 8080 Server Listening Port Number : 8084 Route metric : 1 Virtual service down count : 1 Traffic load balance hash method : source-destination Network monitoring profile count : 1 Active real service count : 2 Total real service count : 2 Demux Nexthop index : 536 Nexthop index : 539 Up time : 2d 19:07 Total packet sent count : 0 Total byte sent count : 0 Total packet received count : 0 Total byte received count : 0 Network monitoring profile index : 1 Network monitoring profile name : prof1 Probe type : ICMP Probe interval : 5 Probe failure retry count : 5 Probe recovery retry count : 3 Traffic load balance real svc name : r12 Routing instance name : server-vrf10 IP address : 203.0.113.12 Traffic load balance group name : g2 Admin state : UP Oper state : UP Network monitoring probe up count : 1 Network monitoring probe down count : 0 Total rejoin event count : 0 Total up event count : 1 Total down event count : 0 Real Service packet sent count : 0 Real Service byte sent count : 0 Real Service packet received count : 0 Real Service byte received count : 0 Total probe sent : 47939 Total probe success : 47916 Total probe fail : 23 Total probe sent failed : 0 Network monitoring profile index : 1 Network monitoring profile name : prof1 Probe type : ICMP Probe state : UP Probe sent : 47939 Probe success : 47916 Probe fail : 23 Probe sent failed : 0 Probe consecutive success : 10089 Probe consecutive fail : 0 Traffic load balance real svc name : r13 Routing instance name : server-vrf10 IP address : 203.0.113.13 Traffic load balance group name : g2 Admin state : UP Oper state : UP Network monitoring probe up count : 1 Network monitoring probe down count : 0 Total rejoin event count : 0 Total up event count : 1 Total down event count : 0 Real Service packet sent count : 0 Real Service byte sent count : 0 Real Service packet received count : 0 Real Service byte received count : 0 Total probe sent : 47939 Total probe success : 47910 Total probe fail : 29 Total probe sent failed : 0 Network monitoring profile index : 1 Network monitoring profile name : prof1 Probe type : ICMP Probe state : UP Probe sent : 47939 Probe success : 47910 Probe fail : 29 Probe sent failed : 0 Probe consecutive success : 6283 Probe consecutive fail : 0
show services traffic-load-balance statistics summary
user@host> show services traffic-load-balance statistics summary Traffic load balance instance name : tlb_sdg Multi services interface name : ms-8/3/0 Interface state : UP Interface type : Multi services Route hold timer : 180 Active real service count : 0 Total real service count : 100 Virtual service Address Sts Packet Sent Byte Sent Packet Recv Byte Recv DNS-VIP1-TCP 198.51.100.1 Up 13182260 709736171 11951566 732469940 DNS-VIP1-UDP 198.51.100.1 Up 2683203 163675383 2683101 262943898 HTTP-80-ADDRESS-VIP 203.0.113.156 Up 363080548 25152313876 282072340 280409712450 HTTP-8080-ADDR-VIP 203.0.113.157 Up 363198700 25318638843 282030640 280388777065 Secure-Ent-443-VIP 203.0.113.158 Up 30561467 3012763619 28007583 3992807922 Simple-Ent-80-VIP 203.0.113.159 Up 155857682 11558785554 89649255 79217609518 Traffic load balance instance name : tlb_sdg_v6 Multi services interface name : ms-8/3/0 Interface state : UP Interface type : Multi services Route hold timer : 180 Virtual service Address Sts Packet Sent Byte Sent Packet Recv Byte Recv DNS-VIP1-TCP-V6 2001:db8:a::300 Up 25118146 1829085032 24172053 2088425092 DNS-VIP1-UDP-V6 2001:db8:a::300 Up 1318497 108116747 1319249 386274267 HTTP-80-ADDR-VIP-V6 2001:db8:a::100 Up 368696950 33051271152 282178604 287789935055 HTTP-8080-ADD-VIP-V6 2001:db8:a::100 Up 368797597 33217998028 281989122 287768684085 Sec-Ent-443-VIP-V6 2001:db8:a::200 Up 0662649 3622545250 28080924 4531356641
Release Information
Statement introduced in Junos OS Release 16.1.
num-instances
option added in Junos OS Release 16.1R6
and 18.2R1 on MX Series.
Support added in Junos OS 19.3R2 for Next Gen Services with the MX-SPC3 services card.