Cisco Systems OL-4387-02 manual Restrictions for SSG Port-Bundle Host Key

Models: OL-4387-02

1 110
Download 110 pages 54.42 Kb
Page 45
Image 45
Restrictions for SSG Port-Bundle Host Key

Chapter 6 Service Connection

SSG Port-Bundle Host Key

For each TCP session between a subscriber and the SESM server, SSG uses one port from the port bundle as the port map. Port mappings are flagged as eligible for reuse on the basis of inactivity timers, but are not explicitly removed once assigned. The number of port bundles is limited, but you can assign multiple SSG source IP addresses to accommodate more subscribers.

SSG assigns the base port of the port bundle to a port map only if SSG has no state information for the subscriber or if the state of the subscriber has changed. When the SESM server sees the base port of a port bundle in the host key, SESM queries SSG for new subscriber state information.

For more information, refer to the SSG Port-Bundle Host Key, Release 12.2(4)B feature module.

Restrictions for SSG Port-Bundle Host Key

The SSG Port-Bundle Host Key feature has the following restrictions:

You must separately enable the SSG Port-Bundle Host Key feature at the SESM and at all connected SSG nodes.

To enable the SSG Port-Bundle Host Key feature, you must reload SSG and restart the SESM.

When you change the port-bundle length, the change does not take effect until after the router reloads.

All SSG source IP addresses configured using the ssg port-map source ip command must be routable in the management network where the SESM resides.

For each SESM server, all connected SSG nodes must have the same port-bundle length.

RFC 1483, local bridged, or routed clients cannot have overlapping IP addresses, even across different interfaces.

Enabling the SSG Port-Bundle Host Key feature requires additional PXF processing.

The Cisco 10000 router’s SSG software and forwarding software handle multiple users attached to a single Cisco IOS interface in different ways, which could result in users receiving services that they did not select. After the first user logs on, all subsequent user logon attempts are rejected. Although the logon is rejected and thus the ability to select services, all users can access the services to which the first user is subscribed. User traffic is not rejected, only the user’s authorization attempt. The traffic from all users is logged in the statistics of the first user. Traffic to the second and subsequent user(s) is treated as transparent passthrough and is forwarded to these users, but it does not affect the SSG accounting. The ssg show host command displays the first user.

For users attached to multipoint interfaces on the access side, the Cisco 10000 router authorizes the first user and then rejects the authorization attempts of subsequent users. The router only rejects the authorization attempts, not the user traffic. The router treats all subsequent users as the first user logged on, allowing access to the services to which the first user is subscribed. However, subsequent users cannot select services. The traffic from all users is logged in the statistics of the first user. Traffic to the second and subsequent user(s) is treated as transparent passthrough and is forwarded to these users, but it does not affect the SSG accounting. The ssg show host command displays the first user.

Cisco 10000 Series Router Service Selection Gateway Configuration Guide

 

OL-4387-02

6-7

 

 

 

Page 45
Image 45
Cisco Systems OL-4387-02 manual Restrictions for SSG Port-Bundle Host Key