User`s guide

240
Entity
Instance
Parameter
Values
Equivalent Web Parameter
udpecho n dstip Valid hostname
Send a UDP packet to IP
address a.b.c.d port n every s
seconds
udpecho n dstport 0 - 65535
Send a UDP packet to IP
address a.b.c.d port n every s
seconds
udpecho n interval 0 - 2147483647
Send a UDP packet to IP
address a.b.c.d port n every s
seconds
udpecho n locport 0 - 65535 Use local port n
udpecho n userouting OFF,ON Route via Routing table
udpecho n ifent PPP,ETH Interface x,y
udpecho n ifadd
Valid interface
instance
0 - 4294967296
Interface x,y
udpecho n onlyis OFF,ON
Only send packet when the
interface is “In Service”
udpecho n nodata OFF,ON
Do not send any data with the
UDP packet
QoS
Configuration – Network > QoS
The Quality of Service (QoS) functionality provides the means of prioritising different types
of IP traffic. It is generally used to ensure that low priority applications do not “hog” the
available bandwidth to the detriment of those having a higher priority. For example, this
might mean that EPOS transactions carried out over XOT will be prioritised over HTTP-type
traffic used for Internet access. Without some form of QoS, all IP packets are treated as
being equal, i.e. there is no discrimination between applications.
The IP packet Type of Service (TOS) field is used to indicate how a packet should be
prioritised. Using the top 6 bits of the TOS field, a router that supports QoS will assign a
Differentiated Services Code Point (DSCP) code to the packet. This may take place within
the router when it receives the packet or another router closer to the packet source may
have already assigned it. Based on the DSCP code, the router will assign the packet to a
priority queue. There are currently four such queues for each PPP instance within the router
and each queue can be configured to behave a particular way so that packets in that queue
are prioritised for routing according to predefined rules.
There are two principal ways in which prioritisation may be effected:
A priority queue can be configured to allow packets to be routed at a specific data rate
(providing that queues of a higher priority are not already using the available bandwidth)
Weighted Random Early Dropping (WRED) of packets may be used as queues become busy,
in an attempt to get the TCP socket generating the packets to “back off” its transmit timers,
thus preventing the queue overflow (which would result in all subsequent packets being
dropped).