This command enables unique ISA treatment of transit prefix subscribers configured on the opposite (remote) side of the system from the parent SAP or spoke SDP. Provisioning a transit sub as remote-aa-sub within a transit prefix policy enables the ISA to treat any network IP-based transit subs in the following ways:
treats packets for the parent AA subscriber independent of whether transits are also configured (stats and policers for parent work as usual)
subsequently, treats the same packet as a transit-sub packet when matching to a configured transit sub (stats, policers)
allows natural direction of the packet for both the parent AA subscriber and the transit-AA subscriber, as shown in Figure: Static-remote-aa-sub usage topology, where a packet from a remote client to a local server is seen as to-sub for the parent, and from-sub for the transit sub that is logically at the far end site
corrects directionality of packet ID for all AA subscribers and allows for correct operation of app-filter flow-setup-direction