Table of Contents
Advertisement
Subscriber Traffic Processor IP Ranges
Assigning subscribers to a specific traffic processor can be implemented in either of the following
scenarios:
•
•
In such cases the SCE platform (based on management configuration) can ensure that the various IP
addresses (either ranges or single IPs) of each subscriber will actually be handled by the same traffic
processor. This is accomplished by assigning a subscriber IP range (or specific IP address) to a
configured Traffic Processor IP Range (TIR). Since each TIR is assigned to a traffic processor, the
relevant subscriber IP range is also assigned to the matching traffic processor. Note that all ranges and
single IPs of a specific subscriber must be assigned to the same traffic processor at any given time.
It is assumed that editing TIR configuration (addition or removal) is done infrequently. Also, that it is
generally done either before the relevant IP ranges are in use or after they are no longer in use.
Subscriber Mapping Modes
The introduction of the TIR functionality provides two possible modes of subscriber mapping:
•
•
TIRs functionality is not necessarily applicable to all subscribers. Therefore, while the user may choose
to assign relevant subscribers to traffic processors via TIRs (TIRs subscriber mapping), the remaining
subscribers are processed as usual (legacy subscriber mapping).
Subscriber Mapping Conflicts
It is important to note that while both subscriber mapping modes can co-exist in one deployment, any
individual subscriber can be processed only in one mode or the other. The same subscriber cannot be
processed partially using TIRs subscriber mappings and partially using legacy subscriber mappings. The
resulting conflicting subscriber mappings will be rejected.
Another cause of conflicting subscriber mappings is when a subscriber is assigned a new range or single
IP that is associated with a traffic processor, different from that with which the subscriber is already
associated.
Conflicting mapping are rejected (any other subscriber mappings are accepted as is) in both cases below:
•
•
Cisco SCE 2000 and SCE 1000 Software Configuration Guide
9-30
All the IP ranges of a given CMTS/BRAS are configured to be processed by the same traffic
processor. This can only be done if one SCE platform is handling several CMTS/BRAS (otherwise
there is a load-balancing issue).
The service provider can control the IP range from which the subscriber IP address is allocated based
on additional criteria such as the subscriber type. In this case, the range can be used by the SCE
platform to assign subscribers to a particular traffic processor, independent of the definition of the
subscriber network ID.
Legacy subscriber mapping — ensures that all mappings of a single subscriber reach the same traffic
processor by internal means, using a hash on the subscriber IP and/or using specific subscriber rules
on the IP/range when required
TIR subscriber mapping — generally (regarding any relevant subscribers) configures all mappings
in a specific range to reach the same traffic processor, reducing the need for internal specific rule
resources per subscriber.
Conflict between mappings of a single mapping request.
Additive subscriber mappings that conflict with existing mappings.
Chapter 9
Managing Subscribers
OL-7827-12
Advertisement
Table of Contents
