media="all">
"; for ($i = 0; $i < count($nav); $i++){ if ($dirMax >= $pthSize){ if(($nav[$i][2] != 1) && (getfilepath($nav[$i][1]) == $parsedpath)) echo "Help : ".$nav[$i][0]; if (parsefilepath($nav[$i][1]) == $dirs[$pthSize]){ if ((getfilepath($nav[$i][1]) != $pth) || getfilepath($nav[$i][1]) != $pth."index.php") echo "Help : "; if (getfilepath($nav[$i][1]) == $parsedpath) echo $nav[$i][0]; else { echo "".$nav[$i][0]." : "; for ($j = 0; $j < count($nav[$i][3]); $j++){ if(getfilepath($nav[$i][3][$j][1]) == $parsedpath) echo $nav[$i][3][$j][0]; if(parsefilepath($nav[$i][3][$j][1]) == $dirs[$pthSize + 1]) { if ((getfilepath($nav[$i][3][$j][1]) == $parsedpath));// echo $nav[$i][3][$j][0]; else { echo "".$nav[$i][3][$j][0]." : "; for($k = 0; $k < count($nav[$i][3][$j][3]); $k++) { if(getfilepath($nav[$i][3][$j][3][$k][1]) == $parsedpath) echo $nav[$i][3][$j][3][$k][0]; if (parsefilepath($nav[$i][3][$j][3][$k][1]) == $dirs[$pthSize+2] && getfilebase($nav[$i][3][$j][3][$k][1]) == $path_parts["basename"]) { if (getfilepath($nav[$i][3][$j][3][$k][1]) == $parsedpath) ; //echo $nav[$i][3][$j][3][$k][0]; else if (parsefilepath($nav[$i][3][$j][3][$k][1]) == $dirs[$pthSize+3] && $nav[$i][3][$j][3][$k][2] == 1) { for ($l = 0; $l < count($nav[$i][3][$j][3][$k][3]); $l++){ if (getfilepath($nav[$i][3][$j][3][$k][3][$l][1]) == $parsedpath) echo "".$nav[$i][3][$j][3][$k][0]." : "; echo $nav[$i][3][$j][3][$k][3][$l][0]; } } } } } } } } } } } echo ""; ?>

Forward sFlow packets to a remote machine for analysis. This feature is typically used in conjunction with the sflowtool to perform ad-hoc traffic studies.

Note: Traffic data from sFlow, NetFlow and HP XRMON sources can be forwarded as sFlow packets.

WARNING: Never forward sFlow to the local host on ports 6343-6353. These are the ports that Traffic Server uses to receive sFlow packets and forwarding to them will create a loop. If you want to analyze the data locally use ports in a different range, for example 7343. The -p option to sflowtool allows it to receive data on non-standard ports, for example sflowtool -p 7343 will listen for sFlow packets on UDP port 7343.

Enabled

Select to enable forwarding of sFlow packets for this entry.

Agent

Specify the agents to be monitored. This is specified by the domain name or IP address of the switch to be monitored. If a subnet is specified then all the agents in that subnet will be monitored. For example, 
Agent = 10.0.0.1 will forward traffic data collected from the 10.0.0.1 switch
Agent = 10.0.0.1/24 will monitor traffic data collected from all switches in the 10.0.0.1/24 subnet. 
Agent = 0.0.0.0/0 will monitor traffic data collected from all switches in the network.

Address

The IP address of the collector to send the sFlow packets to. 127.0.0.1 or localhost will direct sFlow packets to the machine running Traffic Server. Never send sFlow packets to the local host on ports 6343-6353 (see warning above).

Port

The UDP port number to send sFlow packets to. By default sFlow uses port 6343. Never send sFlow packets to the local host on ports 6343-6353 (see warning above).