Cisco SCE 2000 4/8xFE Bedienungsanleitung Seite 19

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 28
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 18
RELEASE SCOS 2.5
Release Notes for Cisco Service Control Operating System (SCOS) 2.5.10
OL-7085-08
19
RELEASE SCOS 2.5
Multi CPE Management in Cable Environments
In a cable environment, the SCE platforms now allows association of a number of Customer
Premises Equipment (CPE) devices into a single home network (that is, behind a single cable
modem). This allows attributing a number of CPEs to a single subscriber-context and applying
a single policy to this subscriber context. This is also relevant for cases where each CPE uses
multiple global IP addresses (unlike a residential gateway NAT setup allowing all CPE
machines to share an IP address).
SCOS 2.5 removes previous limitations of the number of subscribers assigned multiple IP
addresses in the SCE 1000 and SCE 2000. The system ensures that all IP addresses used by
each CPE come from a common pool of addresses, typically assigned with their downstream
CMTS / SMTS device/ blade. The system requires that the subscriber with multiple CPEs be
configured to a single traffic processor (a single PPC in the SCE).
Assigning subscribers to a specific traffic processor can be implemented in either of the
following ways:
Configure all IP ranges of a given CMTS / SMTS to be processed by the same traffic
processor. This can be performed only if one SCE platform handles several CMTS/SMTS
units, otherwise load-balancing cannot be performed properly.
The service provider controls 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.
The SCE platform can be configured such that the IP address range of each subscriber is
actually handled by the same traffic processor. This is achieved by assigning the IP
addresses or range to a configured Traffic Processor IP Range (TIR) and the corresponding
traffic processor. All IPs of a specific subscriber must be assigned to the same traffic
processor at any given time.
The introduction of the TIR functionality provides two possible modes of subscriber mapping:
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 configures all mappings for subscribers in a specific
range to reach the same traffic processor, reducing the need for internal specific rule
resources per subscriber.
TIRs functionality can be applied only to relevant subscribers. That is, some subscribers are
assigned to traffic processors via TIR, while the subscribers without multiple CPE equipment
are processed as usual (legacy subscriber mapping).
Seitenansicht 18
1 2 ... 14 15 16 17 18 19 20 21 22 23 24 ... 27 28

Kommentare zu diesen Handbüchern

Keine Kommentare