EdgeSWG routing domains limitations and overview

search cancel

book

calendar_today

ISG Proxy

Recent changes to routing domains limitations have been provided:

The routing domains feature has the following limitations:

Overlapping subnets between routing domains are not supported.
The following traffic, services, and features can use only the default routing table:

All Edge SWG appliance management traffic, such as Health-checks, NTP, SNMP, SMTP (email), Event log & Access log uploads, Subscriptions downloads (content-filter database), and heartbeats.
WCCP configuration on the appliance.
Authentication realms that are configured on the appliance, except for IWA-BCAAA and LDAP to which you can configure the routing domain to be used. IWA-BCAAA and LDAP realms are also supported for multi-tenant authentication.
All requests originating from the appliance (such as subscriptions, access log upload, and support case upload).

All Health-checks happen in the default routing domain, including the Health-checks for Authentication realms (including IWA-BCAAA and LDAP) and DNS even when they specify a routing domain.
All proxy services and management services are available in all routing domains, which including the SGAC management UI.

For the reference:

thumb_up Yes

thumb_down No