Save to Dashboard. Your contact details will be kept confidential and will not be shared outside Cisco. If we need additional information regarding your feedback, we will contact you at this email address. Toggle navigation Cisco Content Hub. Command Explorer. Topics Navigation. Recent Chapters. Top Viewed. Finding Feature Information Your software release may not support all the features documented in this module. Figure 1.
Figure 2. Ability to inject high-bandwidth content such as video in a Fast or Gigabit Ethernet network. Router config-bba-group vendor-tag remote-id service. Router config-bba-group vendor-tag dsl-sync-rate service. Router config-bba-group end. Router config bba-group pppoe rmt-id-tag Router config-bba-group vendor-tag remote-id service Router config-bba-group vendor-tag dsl-sync-rate service Router config-bba-group nas-port-id format c! Standards Standard Title No new or modified standards are supported by this feature.
Technical Assistance Description Link The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.
Access to most tools on the Cisco Support website requires a Cisco. Otherwise, there can be traffic drops when the Designated multicast forwarder picked by satellite does not align to the Unicast Active Host. These are the different terms associated with the Multicast offload solution. It is scoped over a satellite.
Designated Multicast Forwarder : Each satellite selects a host as the designated multicast forwarder and replicates multicast packets for all receivers satellite access ports for route S, G from the designated multicast forwarder. This term applies to the simple ring Satellite nV System topology. Backup Multicast Forwarder : Multicast packets received from Backup Multicast forwarder are not replicated on the satellite for access ports. Active Unicast Host : The unicast customer data traffic is switched through Active Unicast Host while traversing through the satellite.
Standby Unicast Host : In case of a lost connection to Active Unicast Host due to failures such as cut cables or connection interface failure, the Standby unicast host shall become the new Active Unicast Host. The joins received on the satellite access ports reach the active host and gets processed by the IGMP snoop module.
This keeps the IGMP protocol state for receivers joining over satellite access ports in sync across both hosts in the case of dual host topology.
In the case of dual host topology, the hosts independently offload eligible routes to the relevant satellite devices through SDAC. This includes the list of local ports that have expressed interest in this route. The joins also get propagated to the core by each of the hosts dual host topology , if they have an active link to the core.
This allows better convergence in case of a redundancy switchover on the satellites. When traffic from the source is received on the host, a special indication in the satellite The host then transmits the packet out of a dynamically elected primary OLE for each route S,G on a specific bridge domain. Then, the satellite devices locally replicate the traffic to all the intended local receivers on that device.
As the same traffic stream comes in from both the hosts in the case of dual host topology , the satellites pick a designated multicast forwarder at discovery and continue to replicate from that host until that host goes away or loses its core connectivity. These illustrations show the multicast offload functionality on Satellite nV System that use hub and spoke topologies. These are the behavior of the Multicast offload during various satellite topology events:.
Split brain : During a split brain event, the hosts function independently and the system behaves as two separate chains with IGMP snoop sync broken between satellites and each host offloading to its own set of satellites. On recovery, there is reconciliation and some reprogramming that can result in traffic loss as IGMP snoop protocol states sync up.
RSP failover : This is expected to be hitless for traffic going over routes that have been offloaded already. New joins during the failover may experience the same set of events and traffic impact as the split brain condition. Ring break and Recovery : On ring breakage, any satellites aligned to other host as designated multicast forwarder has to realign to the remaining host on the ring.
This can have a minimal sub-second for L2 core traffic impact on a stable system where the routes are already synchronized. On recovery, there is no revertive switchover and so there must be no traffic impact. For the Dual host topology systems connecting to an Layer 3 core through BVI, the current recommendation is to align all satellites to a single host as Unicast active. Under redundancy group configuration, there is an option to configure a backbone interface.
Multiple backbone interfaces can be configured depending on the number of links from the Host to the core. ICCP protocol keeps a watch over the link states of these interfaces and if all of these backbone interfaces go down, then a core isolation event is notified to the client.
Any satellite which still expect this host to be the designated multicast forwarder can then switchover to the other host as core connectivity is lost. In order to avoid traffic downtimes during flaps, this event is triggered only for core link up to down condition and is non-revertive. A satellite device stays with a host as a designated multicast forwarder until it goes down and does not switch back if the previous host that triggered a switchover comes up.
These are the maximum scale capabilities of Multicast Offload Solution:. The maximum number of rings over which the same offloaded route can be downloaded is The maximum number of offloaded routes for each satellite or ring is In identifying target DSL communications network edge equipment [] , an operator interacting with the bulk DSL service provisioning configuration tool in a network management context, is presented with a managed entity selection panel exemplary shown in FIG.
In accordance with the exemplary embodiment of the invention, functionality provided by a group of view panel components is combined to define the exemplary managed entity instance selection module having the exemplary user interface [] The managed entity selection module combines functionality of a tree , filter , list view panel components, and possibly that of a parameter inspection view panel component Once retrieved, the list of target entities is presented in the list view panel as will be described herein below.
In identifying a group of target network equipment, the containment hierarchy [] , under NMS management is displayed in the tree view panel , and may be navigated by interacting with the tree view panel The selection of an entity of the displayed containment hierarchy creates a selection context including all dependent containment hierarchy entities.
Exemplary selection contexts include, but are not limited to: network partition, network node typically DSLAM , shelf, interface card typically line cards , port, physical link, local loop, data link, etc. The variety of selection contexts is only limited by the level of modeling provided for network management in the containment hierarchy The inclusion of dependent containment hierarchy entities in the selection context may further be refined via interaction with the filter view panel [] Various combinations of filter criteria and perhaps filter values may be employed in: network node DSLAM , shelf, interface card line card , port, physical link local loop , data link, etc.
Validation of identified target entities is provided via the list view panel [] The containment hierarchy , besides storing dependence relationships between managed entities, also stores managed entity specifiers holding identifiers and operational parameter values. In accordance with an exemplary implementation, all dependent branches of the containment hierarchy in the selection context are traversed to extract a list of managed entity target references based on the filter criteria and filter values.
The extracted list target entities is displayed in the list view panel For example, the parameter view panel displays a subscriber identification telephone number in selecting a DSL port on a DSL line card If a list of target entities is retrieved [] from a file, the list is displayed in the list view panel By traversing the containment hierarchy [] in a network management context; the intricacies of multi-vendor equipment are hidden to the operator.
This enables novice personnel to operate the solution therefore reducing downtime. Having identified [] the target entities to be configured, the operator is provided with the opportunity to select a configuration job to be applied to the identified target entities via interaction with an exemplary PCR specification view panel shown in FIG. The operator interacts with the PCR specification view panel [] to either select a configuration job or to specify a file holding a configuration job definition.
Typically the configuration job includes a group of configuration commands to be executed on each target in the list, but the invention is not limited thereto. The specification of the configuration job in the DSL configuration context includes custom configuration templates and profiles, and facilities may be provided for defining thereof.
A filter option may be provided to identify a configuration template from a group of configuration templates. The operator is provided with the opportunity to tailor the TurnUpSubscriber configuration template in defining the PCR. In particular, a DSL port train-up speed may be specified by exemplary selecting a service profile.
The DSL CPE [] operational parameters including but not limited to: bandwidth, content encapsulation, quality of service, connection identification including virtual private network identification , and transport protocol may be specified. The definition of a cross-connect at the DSLAM may be requested to convey data from the local loop over the data link In requesting the setup of a data link a particular BRAS may further be specified. Operational parameters may further be specified for service activation at the BRAS including, but not limited to: content encapsulation, quality of service, and connection identification including virtual private network identification.
Having specified the configuration job [] , the PCR may be saved Scheduling information may be entered including start and end times. The start and end specification format provides for date and time of day specifications.
If the start time is left unspecified, then the PCR, once defined and stored is expected to take effect immediately. If the end time is left unspecified then the PCR is expected to take as long as it needs to complete processing unhindered.
The specification of scheduling information may also request periodic execution of the PCR at a specified interval. The operator is provided with the option to specify the frequency in populating the PCR.
Policy information may also be specified. Although start and end times may be specified, when servicing PCRs in the network management context, it may not always be possible or desirable to comply with the start and end times, for example if the network infrastructure under management is experiencing a network failure, a lot of signaling bandwidth is being used up in restoring the network.
A best time frame specification gives an indication as to when else the PCR may be run. For example, residential DSL services should be configured between to on weekdays when the subscribers are at work, and business DSL services should be changed between and when businesses are closed. Policy information may also include the specification of a rate at which target entities are to be configured. Using too high a rate may overburden the service provider's network [] with a lot of signaling and configuration traffic.
A minimum rate is typically specified to ensure that all targets are configured within a configuration time window. The configuration job may optionally be validated before it is performed on the target list. The operator is provided with the opportunity to request validation [] of the configuration job and also to specify a validation job.
Validation is typically used to reduce the risk of erroneous configurations being performed. A validation job may include a group of commands which may test a particular condition on the target entity without limiting the invention thereto. An exemplary test would include testing whether the target DSL ports [] are activated but not in use so that configuration changes will not affect currently provisioned services.
The validation job may include commands requesting that the current configuration of each target DSL port entity be saved and stored potentially to be used later if the execution of the configuration job fails. The operator is further provided with the opportunity to specify what actions are to be taken in case errors are encountered during PCR execution step [] An option enables the trapping of errors when performing configuration changes on the target entities. The execution of the PCR may be automatically stopped on detecting a first error.
Stopping the PCR execution, as will be presented herein below, suppresses processing the next target entity in the target list. The configuration changes performed up to and including the detected error may be optionally undone to reverse the effect of undesired configuration changes.
The programmable configuration management infrastructure further keeps track of the target entities processed, and the status of the configuration job performed on each target entity including encountered errors. The bulk DSL service provisioning configuration tool receives completion reports and error notifications on a per-PCR basis and on a per-target entity basis.
Encountering errors in performing the configuration job is expected even if validation was successful. Log In to Comment. View This Post. Hi Randika, Congratulations for your iniative. Good work. Regards, Elias. August 7, at AM. Great work. February 22, at AM. There are some basic commands for ccent beginners. Follow Following Unfollow.
0コメント