Comtech EF Data CTOG-250 - Manual (Page 137)

CTOG-250 Comtech Traffic Optimization Gateway Revision 1
Ethernet-based Remote Product Management MN-CTOG250
7–35
The entries in this table are displayed based on which traffic has matched to this QoS Group.
The user-defined subnets entered into the QoS page need to be equal to or a superset of any of
the routes from the remotes – i.e., there must be no overlaps. The user-defined VLAN ID must
be an exact match.
The examples that follow illustrate how the locally attached subnets associated with each
Ethernet will be reported as routes, unless the Management IP address has not been changed;
in which case, it will ignore that value.
The examples that follow illustrate how the locally attached subnets associated with each
Ethernet will be reported as routes, unless you have not changed the Management IP address;
in which case, it will ignore that value:
Example #1
QoS Subnet
192.168.1.0/24
Remote Management IP Address 192.168.1.1
Remote’s Reported Routes 192.168.1.0/27
84.0.50.24
Result Remote 192.168.1.1 will be added when traffic to
that remote is sent through the CTOG-250
Example #2
QoS Subnet
192.168.0.0/16
Remote 1 Management IP Address 192.168.1.1
Remote 1 Reported Routes
192.168.1.0/27
84.0.5.0/24
Remote 2 Management IP Address 192.168.1.1
Remote 2 Reported Routes
192.168.2.0/24
84.0.5.0/24
Result Remote 192.168.1.1 and 192.168.2.1 will be added
Example #3
QoS Subnet
192.168.1.0/24
Remote 1 Management IP Address 192.168.1.1
Remote 1 Reported Routes 92.168.1.0/23
84.0.5.0/24
Result Remote 192.168.1.1 will NOT be added because
the 192.168.1.0/23 route is not completely
"covered" by the QoS Subnet.