Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel

In this section:

Table of Contents
maxLevel4
minLevel2


Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
JIRAIDAUTHSBX-131440
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c87e188912017e590a028f0021, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c87e188912017e590a028f0021, userName='null'}

Overview

The SBC Core includes the native Linux commands The SBC is enhanced to include the native Linux commands ping and traceroute (and their IPv6 variants) from the SBC command line interface. To use the commands at the SBC application level, log on to the SBC as an application administrator.

These commands are useful to test node connectivity and other network issues without leaving the application command line.

Info
titleNote

For an HA pair configuration, you can run CLI commands ping and traceroute (and their IPv6 versions) from the active CE; a switchover is needed required to run the CLI commands from the standby CE.

The enhancement is useful when you want to use the commands to test node connectivity and other network issues without leaving the application command line.

Command Syntax

Info
titleNote

The commands, options, and syntax available from the SBC CLI are exactly same as Linux and Unix platforms.

Command Syntax

Note
Info
title

  • For IPv6 addresses, use ping6 and traceroute6.
  • Execute the commands without entering the configure private mode of the SBC.

ping

Code Block
> ping 
	[-LRUbdfnqrvVaAD] 
	[-c <count>] 
	[-i <interval>] 
	[-w <deadline>] 
	[-p <pattern>] 
	[-s <packetsize>] 
	[-t <ttl>] 
	[-I <interface>] 
	[-M <pmtudisc-hint>] 
	[-m <mark>] 
	[-S <sndbuf>] 
	[-T <tstamp-options>] 
	[-Q <tos>] 
	[hop1 ...] 
	<destination_IPv4_address>

ping6

Code Block
> ping6 
	[-LRUbdfnqrvVaAD] 
	[-c <count>] 
	[-i <interval>] 
	[-w <deadline>] 
	[-p <pattern>] 
	[-s <packetsize>] 
	[-t <ttl>] 
	[-I <interface>] 
	[-M <pmtudisc-hint>] 
	[-m <mark>] 
	[-S <sndbuf>] 
	[-T <tstamp-options>] 
	[-Q <tos>] 
	[hop1 ...] 
	<destination_IPv6_address>

traceroute

Code Block
> traceroute 
	[ -46dFITnreAUV ] 
	[ -f <first_ttl> ] 
	[ -g gate,... ] 
	[ -i <device> ] 
	[ -m <max_ttl> ] 
	[ -N <squeries> ] 
	[ -p <port> ] 
	[ -t <tos> ] 
	[ -l <flow_label> ] 
	[ -w <waittime> ] 
	[ -q <nqueries> ] 
	[ -s <src_addr> ] 
	[ -z <sendwait> ] 
	[ --fwmark=<num> ] 
	host 
	[ <packetlen> ]

traceroute6

Note
titleAttention

The traceroute6 command is not supported in SBC release versions 9.2.x to 11.0.x. It is supported from SBC version 11.1.x onwards.


Code Block
> traceroute6 
	[ -46dFITnreAUV ] 
 	[ -d ]  			---Use SO_DEBUG socket option
	[ -f <first_ttl> ] 
	[ -g gate,... ] 
	[ -i <device> ] 	---Bind to <device>
	[ -m <max_ttl><hops> ] 		---Use maximum <hops>
	[ -n ] -N <squeries> ] 				---No dns name resolution
	[ -p <port> ] 		---Use destination <port>
	[ -t <tos> ] 
	[ -l <flow_label> ] 
	[ -w <waittime> ] 
	[ -q <nqueries> ]  <nprobes> ] 	---Number of probes
 	[ -r ]   			---Use SO_DONTROUTE socket option
	[ -s <src_addr> ] <address> ]	---Use source <address> 
  	[ -v ]  			---Verbose output
	[ -w <timeout> ]	---Time to wait for response
	[ -z <sendwait> ] 
	[ --fwmark=<num> ] 
	host 
	[ <packetlen> ]

 


Parameter Descriptions

For parameter descriptions and other information on the ping and traceroute commands commands and their IPv6 variants, refer to the Linux manual pages on the internetInternet. Alternatively, you may refer to the manual pages installed as part of the Linux platform on the SBC. To access the manual pages installed on the SBC:

  1. Log on to the SBC as root.
Execute
  1. Issue the command:

    Code Block
    # man <command>


Configuration Examples

Info
titleNote
  • For IPv6 addresses, use ping6 and traceroute6.
  • Execute Issue the commands without entering the configure private mode of the SBC.

ping

Code Block
> ping -c 3 10.31.200.50

PING 10.31.200.50 (10.31.200.50) 56(84) bytes of data.
64 bytes from 10.31.200.50: icmp_req=1 ttl=255 time=5.28 ms
64 bytes from 10.31.200.50: icmp_req=2 ttl=255 time=5.69 ms
64 bytes from 10.31.200.50: icmp_req=3 ttl=255 time=4.34 ms--- 10.31.200.50 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 4.340/5.106/5.693/0.566 ms

ping6

Code Block
> ping6 -c 2 0000:0000:0000:0000:0000:0000:0000:0001

PING 0000:0000:0000:0000:0000:0000:0000:0001(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.031 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.060 ms--- 0000:0000:0000:0000:0000:0000:0000:0001 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.031/0.045/0.060/0.016 ms

traceroute

Code Block
> traceroute 10.31.200.50

traceroute to 10.31.200.50 (10.31.200.50), 30 hops max, 60 byte packets
1 10.31.200.50 (10.31.200.50) 9.487 ms 9.493 ms 9.491 ms

traceroute6

Note
titleAttention

The traceroute6 command is not supported in SBC release versions 9.2.x to 11.0.x. It is supported from SBC version 11.1.x onwards.


Code Block
> traceroute6 0::0.0.0.0

traceroute to 0::0.0.0.0 (::), 30 hops max, 80 byte packets
1 localhost (::1) 0.033 ms 0.009 ms 0.008 ms

 

pagebreak