- Support for Channelized OC3/STM1 (Multi-Rate) Circuit
Emulation MIC with SFP (ACX4000)—The ACX4000 Universal
Access Routers support the Channelized OC3/STM1 (Multi-Rate) Circuit
Emulation MIC with SFP (model number ACX-MIC-4COC3-1COC12CE).
The key features supported are:
- Structure-Agnostic TDM over Packet (SAToP)
- Pseudowire Emulation Edge to Edge (PWE3) control word
for use over an MPLS packet-switched network (PSN)
- Support for 6-port Gigabit Ethernet Copper/SFP
MIC (ACX4000)—The ACX4000 Universal Access Routers
support the 6-port Gigabit Ethernet Copper/SFP MIC. The 6-port Gigabit
Ethernet Copper/SFP MIC features six tri-speed (10/100/1000 Mbps)
Ethernet ports. Each port can be configured to operate in either RJ45
or SFP mode and can support PoE.
- Support for chassis management (ACX4000)—The ACX4000 Universal Access Routers support the following
CLI operational mode commands:
- show chassis alarms
- show chassis craft-interface
- show chassis environment
- show chassis environment pem
- show chassis fan
- show chassis firmware
- show chassis fpc pic-status
- show chassis hardware (clei-models | detail | extensive | models)
- show chassis mac-addresses
- show chassis pic fpc-slot fpc-slot pic-slot pic slot
- show chassis routing-engine
- restart chassis-control (gracefully | immediately | soft)
- request chassis feb restart slot slot-number
- request chassis mic mic-slot mic-slot fpc-slot fpc-slot (offline | online)
- request chassis pic offline fpc-slot fpc-slot pic-slot pic-slot
- User-defined alarms (ACX Series)—On
an ACX Series router, the alarm contact port (labeled ALARM) provides
four user-defined input ports and two user-defined output ports. Whenever
a system condition occurs—such as a rise in temperature, and
depending on the configuration, the input or output port is activated.
To view the alarm relay information, issue the show chassis craft-interface command from the Junos OS command-line interface.
- Support for Ethernet synthetic loss measurement
(ACX Series)—You can trigger on-demand and proactive
Operations, Administration, and Maintenance (OAM) for measurement
of statistical counter values corresponding to ingress and egress
synthetic frames. Frame loss is calculated using synthetic frames
instead of data traffic. These counters maintain a count of transmitted
and received synthetic frames and frame loss between a pair of maintenance
association end points (MEPs).
The Junos OS implementation of Ethernet synthetic loss measurement
(ETH-SLM) is fully compliant with the ITU-T Recommendation Y.1731.
Junos OS maintains various counters for ETH-SLM PDUs, which can be
retrieved at any time for sessions that are initiated by a certain
MEP. You can clear all the ETH-SLM statistics and PDU counters.
- Support for Network Address Translation (ACX Series)—Network Address Translation (NAT) is a method for modifying
or translating network address information in packet headers. Either
or both source and destination addresses in a packet may be translated.
NAT can include the translation of port numbers as well as IP addresses.
ACX Series routers support only source NAT for IPv4 packets. Static
and destination NAT types are currently not supported on the ACX Series
routers.
 |
Note:
In ACX Series routers, NAT is supported only on the ACX1100
AC-powered router.
|
- Support for inline service interface (ACX
Series)—Junos OS for ACX Series Universal Access
Routers support inline service interface. An inline service interface
is a virtual physical interface that resides on the Packet Forwarding
Engine. The si- interface makes it possible to provide
NAT services without a special services PIC.
To configure inline NAT, you define the service interface as
type si- (service-inline) interface. You must also reserve
adequate bandwidth for the inline interface. This enables you to configure
both interface or next-hop service sets used for NAT.
|
Note:
In ACX Series routers, you can configure only one inline services
physical interface as an anchor interface for NAT sessions: si-0/0/0.
|
- Support for IPsec (ACX Series)—You can configure IPsec on ACX Series Universal Access Routers.
The IPsec architecture provides a security suite for the IP version
4 (IPv4) network layer. The suite provides functionality such as authentication
of origin, data integrity, confidentiality, replay protection, and
nonrepudiation of source. In addition to IPsec, Junos OS also supports
the Internet Key Exchange (IKE), which defines mechanisms for key
generation and exchange, and manages security associations. IPsec
also defines a security association and key management framework that
can be used with any network layer protocol. The security association
specifies what protection policy to apply to traffic between two IP-layer
entities. IPsec provides secure tunnels between two peers.
|
Note:
IPsec is supported only on the ACX1100 AC-powered router.
|
- Support for ATM OAM F4 and F5 cells (ACX Series)—ACX Series routers provide Asynchronous Transfer Mode (ATM)
support for the following Operations, Administration, and Maintenance
(OAM) fault management cell types:
- F4 alarm indication signal (AIS) (end-to-end)
- F4 remote defect indication (RDI) (end-to-end)
- F4 loopback (end-to-end)
- F5 AIS
- F5 RDI
- F5 loopback
ATM OAM is supported on ACX1000, ACX2000, and ACX2100 routers,
and on 16-port Channelized E1/T1 Circuit Emulation MICs on ACX4000
routers.
Junos OS supports the following methods of processing OAM cells
that traverse through pseudowires with circuit cross-connect (CCC)
encapsulation:
- Virtual path (VP) pseudowires (CCC encapsulation)
- Port pseudowires (CCC encapsulation)
- Virtual circuit (VC) pseudowires (CCC encapsulation)
For ATM pseudowires, the F4 flow cell is used to manage the
VP level. On ACX Series routers with ATM pseudowires (CCC encapsulation),
you can configure OAM F4 cell flows to identify and report virtual
path connection (VPC) defects and failures. Junos OS supports three
types of OAM F4 cells in end-to-end F4 flows:
- Virtual path AIS
- Virtual path RDI
- Virtual path loopback
For OAM F4 and F5 cells, IP termination is not supported. Also,
Junos OS does not support segment F4 flows, VPC continuity check,
or VP performance management functions.
For OAM F4 cells, on each VP, you can configure an interval
during which to transmit loopback cells by including the oam-period statement at the [edit interfaces interface-name atm-options vpi vpi-identifier] hierarchy
level. To modify OAM liveness values on a VP, include the oam-liveness statement at the [edit interfaces interface-name atm-options vpi vpi-identifier] hierarchy
level.
- Support for CESoPSN on Channelized OC3/STM1 (Multi-Rate)
Circuit Emulation MIC with SFP (ACX Series)—You
can configure structure-aware TDM CESoPSN on the Channelized OC3/STM1
(Multi-Rate) Circuit Emulation MIC with SFP (model number: ACX-MIC-4COC3-1COC12CE)
on ACX Series routers. This rate-selectable MIC can be configured
as four OC3/STM1 ports or one OC12/STM4 port.
- Support for Point-to-Point Protocol encapsulation
(ACX Series)—You can configure Point-to-Point
Protocol (PPP) encapsulation on physical interfaces on ACX Series
routers. PPP provides a standard method for transporting multiprotocol
datagrams over a point-to-point link. PPP uses the High-Speed Data
Link Control (HDLC) protocol for its physical interface and provides
a packet-oriented interface for the network-layer protocols.
PPP is supported on the following MICs on ACX Series routers:
- On ACX1000 routers with 8-port built-in T1/E1 TDM MICs.
- On ACX2000 and ACX2100 routers with 16-port built-in T1/E1
TDM MICs.
- On ACX4000 routers with 16-port Channelized E1/T1 Circuit
Emulation MICs.
On ACX Series routers, E1, T1, and NxDS0
interfaces support PPP encapsulation.
- Support for Ethernet link aggregation (ACX Series)—Junos OS for ACX Series Universal Access Routers support Ethernet
link aggregation for Layer 2 bridging. Ethernet link aggregation is
a mechanism for increasing the bandwidth of Ethernet links linearly
and improving the links' resiliency by bundling or combining multiple
full-duplex, same-speed, point-to-point Ethernet links into a single
virtual link. The virtual link interface is referred to as a link
aggregation group (LAG) or an aggregated Ethernet interface. The LAG
balances traffic across the member links within an aggregated Ethernet
interface and effectively increases the uplink bandwidth. Another
advantage of link aggregation is increased availability, because the
LAG is composed of multiple member links. If one member link fails,
the LAG continues to carry traffic over the remaining links.
- 16-port Channelized E1/T1 Circuit Emulation MIC
(ACX4000)—ACX4000 Universal Access Routers support
the 16-port Channelized E1/T1 Circuit Emulation MIC (model number
ACX-MIC-16CHE1-T1-CE).
The key features supported on this MIC are:
- Structure-Agnostic TDM over Packet (SAToP)
- ATM encapsulation—Only the following ATM encapsulations
are supported on this MIC:
- ATM CCC cell relay
- ATM CCC VC multiplex
- ATM pseudowires
- ATM quality-of-service (QoS) features—traffic shaping,
scheduling, and policing
- ATM Operation, Administration, and Maintenance
- ATM (IMA) protocol at the T1/E1 level with up to 16 IMA
(Inverse Multiplexing for ATM) groups. Each group can have 1-8 IMA
links.
- Support for PIM and IGMP in global domain (ACX
Series)—Junos OS for ACX Series Universal Access
Routers supports Protocol Independent Multicast (PIM) and Internet
Group Management Protocol (IGMP) messages for multicast data delivery.
ACX Series routers are used as a leaf in the multicast distribution
tree so that subscribers in the global domain can directly connect
to the ACX Series routers through IPv4 interfaces. ACX Series routers
can also be used as a branch point in the tree so that they are connected
to other downstream ACX Series or MX Series routers and send multicast
data according to the membership established through the PIM or IGMP
messaging.
|
Note:
ACX Series routers support only sparse mode. Dense mode on ACX
series is supported only for control multicast groups for autodiscovery
of rendezvous point (auto-RP).
|
You can configure IGMP on the subscriber-facing interfaces to
receive IGMP control packets from subscribers, which in turn triggers
the PIM messages to be sent out of the network-facing interface toward
the rendezvous point (RP).
|
Note:
ACX Series routers do not support IPv6 interfaces for multicast
data delivery and RP functionality.
|
- Support for dying-gasp PDU generation (ACX Series)—Junos OS for ACX Series Universal Access Routers supports
the generation of dying-gasp protocol data units (PDUs). Dying gasp
refers to an unrecoverable condition such as a power failure. In this
condition, the local peer informs the remote peer about the failure
state. When the remote peer receives a dying-gasp PDU, it takes an
action corresponding to the action profile configured with the link-adjacency-loss event.
ACX Series routers can generate and receive dying-gasp packets.
When LFM is configured on an interface, a dying-gasp PDU is generated
for the interface on the following failure conditions:
- Power failure
- Packet Forwarding Engine panic or a crash
- Support for logical tunnels (ACX Series)—Logical tunnel (lt-) interfaces provide quite different
services depending on the host router. On ACX Series routers, logical
tunnel interfaces enable you to connect a bridge domain and a pseudowire.
To create tunnel interfaces, an FPC and the corresponding Packet
Forwarding Engine on an ACX Series router must be configured to be
used for tunneling services at the [edit chassis] hierarchy
level. The amount of bandwidth reserved for tunnel services must also
be configured.
To create logical tunnel interfaces and the bandwidth in gigabits
per second to reserve for tunnel services, include the tunnel-services bandwidth (1g | 10g) statement at the [edit chassis fpc slot-number pic number] hierarchy
level.
- Support for PPP encapsulation on Channelized OC3/STM1
(Multi-Rate) Circuit Emulation MIC with SFP (ACX Series)—On ACX4000 routers, you can configure Point-to-Point Protocol
(PPP) encapsulation on physical interfaces on Channelized OC3/STM1
(Multi-Rate) Circuit Emulation MIC with SFP. PPP provides a standard
method for transporting multiprotocol datagrams over a point-to-point
link. PPP uses the High-Speed Data Link Control (HDLC) protocol for
its physical interfaces and provides a packet-oriented interface for
the network-layer protocols.
On ACX Series routers, E1, T1, and NxDS0
interfaces support PPP encapsulation.
IP class of service (CoS) is not supported on PPP interfaces.
All the traffic is sent to the best effort queue (queue 0) and CoS
code points are not processed. Also, fixed classifiers are not supported.
PPP is supported only for IPv4 networks.
- Support for dual-rate SFP+ modules (ACX Series)—ACX2000, ACX2100, and ACX4000 routers support the dual-rate
SFP+ optic modules. These modules operate at either 1 Gbps or 10
Gbps speeds. When you plug in the module to the small form-factor
pluggable plus (SFP+) slot, the module can be set at either 1 Gbps
or 10 Gpbs.
ACX Series routers use the 2-port 10-Gigabit Ethernet (LAN)
SFP+ MIC in the following two combinations:
- 2-port 10-Gigabit Ethernet (LAN) SFP+ uses BCM84728 PHY
on ACX 2100/ACX4000 routers.
- 2-port 10-Gigabit Ethernet (LAN) SFP+ uses BCM8728/8747
on ACX2000 routers.
To configure an xe port in 1-Gigabit Ethernet mode
, use the set interfaces xe-x/y/z speed 1g statement.
To configure an xe port in 10-Gigabit Ethernet mode, use
the set interfaces xe-x/y/z speed 10g statement. The default
speed mode is 1-Gigabit Ethernet mode.
- Support for inverse multiplexing for ATM (IMA)
on Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP
(ACX Series)—You can configure inverse multiplexing
for ATM (IMA) on the Channelized OC3/STM1 (Multi-Rate) Circuit Emulation
MIC with SFP (model number: ACX-MIC-4COC3-1COC12CE) on ACX Series
routers. You can configure four OC3/STM1 ports or one OC12/STM4 port
on this rate-selectable MIC.
- Support for TDR for diagnosing cable faults (ACX
Series)-—Junos OS for ACX Series Universal Access
Routers supports Time Domain Reflectometry (TDR), which is a technology
used for diagnosing copper cable states. This technique can be used
to determine whether cabling is at fault when you cannot establish
a link. TDR detects the defects by sending a signal through a cable,
and reflecting it from the end of the cable. Open circuits, short
circuits, sharp bends, and other defects in the cable reflects the
signal back at different amplitudes, depending on the severity of
the defect. TDR diagnostics is supported only on copper interfaces
and not on fiber interfaces.
TDR provides the following capabilities that you can use to
effectively identify and correct cable problems:
- Display detailed information about the status of a twisted-pair
cable, such as cable pair being open or short-circuited.
- Determine the distance in meters at which open or short-circuit
is detected.
- Detect whether or not the twisted pairs are swapped.
- Identify the polarity status of the twisted pair.
- Determine any downshift in the connection speed.
- Support for Layer 2 security (ACX Series)—ACX Series routers support bridge family firewall filters.
These family filters can be configured at the logical interface level
and can be scaled up to 124 terms for ingress traffic, and 126 terms
for egress traffic.
- Support for Ethernet Local Management Interface
protocol (ACX Series)—The Ethernet Local Management
Interface (E-LMI) protocol on ACX Series Universal Access Routers
supports Layer 2 circuit and Layer 2 VPN Ethernet virtual connection
(EVC) types.
Junos OS for ACX Series Universal Access Routers support E-LMI
only on provider edge (PE) routers.
- Support for Layer 2 control protocols and Layer
2 protocol tunneling (ACX Series)—You can configure
spanning tree protocols to prevent Layer 2 loops in a bridge domain.
Layer 2 control protocols for ACX Series Universal Access Routers
include the Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol
(RSTP), Multiple Spanning Tree Protocol (MSTP), VLAN Spanning Tree
Protocol (VSTP), and Link Layer Discovery Protocol (LLDP). ACX Series
routers can support up to 128 STP instances, which includes all instances
of VSTP, MSTP, RSTP and STP.
Layer 2 protocol tunneling (L2PT) is supported on ACX Series
routers. L2PT allows Layer 2 protocol data units (PDUs) to be tunneled
through a network. L2PT can be configured on a port on a customer-edge
router by using MAC rewrite configuration. MAC rewrite is supported
for STP, Cisco Discovery Protocol (CDP), VLAN Trunk Protocol (VTP),
IEEE 802.1X, IEEE 802.3ah, Ethernet Local Management Interface (E-LMI),
Link Aggregation Control Protocol (LACP), Link Layer Discovery Protocol
(LLDP), Multiple MAC Registration Protocol (MMRP), and Multiple VLAN
Registration Protocol (MVRP) packets.
- Support for Layer 2 bridging (ACX Series)—Junos OS for ACX Series Universal Access Routers supports
Layer 2 bridging and Q-in-Q tunneling. A bridge domain is created
by adding a set of Layer 2 logical interfaces in a bridge domain to
represent a broadcast domain. Layer 2 logical interfaces are created
by defining one or more logical units on a physical interface with
encapsulation as ethernet-bridge or vlan-bridge. All the member ports of the bridge domain participate in Layer
2 learning and forwarding. You can configure one or more bridge domains
to perform Layer 2 bridging. You can optionally disable learning on
a bridge domain.
|
Note:
ACX Series routers do not support the creation of bridge domains
by using access and trunk ports.
|
On ACX Series routers, you can configure E-LAN and E-LINE services
on bridge domains. When you configure E-LAN and E-LINE services by
using a bridge domain without a vlan-id statement, the
bridge domain should explicitly be normalized by an input VLAN map
to a service VLAN ID and TPID. Explicit normalization is required
when a logical interface’s outer VLAN ID and TPID are not the
same as the service VLAN ID and TPID of the service being configured.
- Support for IEEE 802.1ad classifier (ACX Series)—Junos OS for ACX Series Universal Access Routers supports
the IEEE 802.1ad classifier. Rewrite rules at the physical interface
level support the IEEE 802.1ad bit value. The IEEE 802.1ad classifier
uses IEEE 802.1p and DEI bits together. On logical interfaces, only
fixed classifiers are supported.
You can configure either IEEE 802.1p or IEEE 802.1ad classifiers
at the physical interface level. You can define the following features:
- IEEE 802.1ad classifiers (inner or outer)
- IEEE 802.1ad rewrites (outer)
|
Note:
You cannot configure both IEEE 802.1p and IEEE 802.1ad classifiers
together at the physical interface level.
|
ACX Series routers support the IEEE 802.1ad classifier and rewrite
along with the existing class-of-service features for Layer 2 interfaces.
- Support for OAM with Layer 2 bridging as a transport
mechanism (ACX Series)—Junos OS for ACX Series
Universal Access Routers supports the following OAM features that
use Layer 2 bridging as a transport mechanism:
- IEEE 802.3ah LFM—IEEE 802.3ah link fault management
(LFM) operates at the physical interface level and the packets are
sent using Layer 2 bridging as a transport mechanism.
- Dying-gasp packets—Dying-gasp PDU generation operates
at the physical interface level. Dying-gasp packets are sent through
the IEEE 802.3ah LFM-enabled interfaces.
- IEEE 802.1ag and ITU-T Y.1731 protocols on down MEPs—IEEE
802.1ag configuration fault management (CFM) and ITU-T Y.1731 performance-monitoring
OAM protocols, which are used for end-to-end Ethernet services, are
supported only on down maintenance association end points (MEPs).
The ITU-T Y.1731 protocol supports delay measurement on down MEPs
but does not support loss measurement on down MEPs.
- Support for Storm Control—Storm
control is supported on ACX Series routers. Storm control is only
applicable at the IFD level for ACX Series. When a traffic storm is
seen on the interface configured for storm control, the default action
is to drop the packets exceeding the configured bandwidth. No event
is generated as part of this. Storm control is not enabled on the
interface by default.
- Support for RFC 2544-based benchmarking tests
(ACX Series)—Junos OS for ACX Series Universal
Access Routers support RFC 2544-based benchmarking tests for E-LINE
and ELAN services configured using bridge domains. RFC 2544 defines
a series of tests that can be used to describe the performance characteristics
of network interconnecting devices. RFC 2544 tests methodology can
be applied to a single device under test, or a network service (set
of devices working together to provide end-to-end service). When applied
to a service, the RFC 2544 test results can characterize the service-level-agreement
parameters.
RFC 2544 tests are performed by transmitting test packets from
a device that functions as the generator or the initiator. These packets
are sent to a device that functions as the reflector, which receives
and returns the packets back to the initiator.
ACX Series routers support RFC 2544 tests to measure throughput,
latency, frame loss rate, and back-to-back frames.
With embedded RFC 2544, an ACX Series router can be configured
as an initiator and reflector.
- You can configure RFC 2544 tests on the following underlying
services:
- Between two IPv4 endpoints.
- Between two user-to-network interfaces (UNIs) of Ethernet
Virtual Connection (EVC), Ethernet Private Line (EPL, also called
E-LINE), Ethernet Virtual Private Line (EVPL), EVC (EPL, EVPL).
- Support for IEEE 802.1ag and ITU-T Y.1731
OAM protocols on up MEPs (ACX Series)—Junos OS
for ACX Series Universal Access Routers supports IEEE 802.1ag configuration
fault management (CFM) and ITU-T Y.1731 performance-monitoring OAM
protocols on up maintenance association end points (MEPs). CFM OAM
protocol is supported on link aggregation group (LAG) or aggregated
Ethernet (AE) interfaces. The ITU-T Y.1731 protocol supports delay
measurement on up MEPs but does not support loss measurement on up
MEPs.
|
Note:
ACX Series routers do not support ITU-T Y.1731 OAM protocol
on AE interfaces.
|
- Support for Ethernet alarm indication signal
(ACX Series)—Junos OS for ACX Series Universal
Access Routers support ITU-T Y.1731 Ethernet alarm indication signal
function (ETH-AIS) to provide fault management for service providers.
ETH-AIS enables you to suppress alarms when a fault condition is detected.
Using ETH-AIS, an administrator can differentiate between faults at
the customer level and faults at the provider level. When a fault
condition is detected, a maintenance end point (MEP) generates ETH-AIS
packets to the configured client levels for a specified duration until
the fault condition is cleared. Any MEP configured to generate ETH-AIS
packets signals to a level higher than its own. A MEP receiving ETH-AIS
recognizes that the fault is at a lower level and then suppresses
alarms at current level the MEP is in.
ACX Series routers support ETH-AIS PDU generation for server
MEPs on the basis of the following defect conditions:
- Loss of connectivity (physical link loss detection)
- Layer 2 circuit or Layer 2 VPN down
- Support for Ethernet ring protection switching
(ACX Series)--You can configure Ethernet ring protection
switching (ERPS) on ACX Series routers to achieve high reliability
and network stability. The basic idea of an Ethernet ring is to use
one specific link, called the ring protection link (RPL), to protect
the whole ring. Links in the ring will never form loops that fatally
affect the network operation and services availability.
ACX Series routers support multiple Ethernet ring instances
that share the physical ring. Each instance has its own control channel
and a specific data channel. Each ring instance can take a different
path to achieve load balancing in the physical ring. When no data
channel is specified, ERP operates only on the VLAN ID associated
with the control channel. G.8032 open rings are supported.
ACX Series routers do not support aggregate Ethernet–based
rings.
To configure Ethernet ring protection switching, include the protection-ring statement at the [edit protocols] hierarchy level.
- Support for integrated routing and bridging
(ACX Series)—Junos OS for ACX Series Universal
Access Routers supports integrated routing and bridging (IRB) functionality.
IRB provides routing capability on a bridge domain. To enable this
functionality, you need to configure an IRB interface as a routing
interface in a bridge domain and then configure a Layer 3 protocol
such as IP or ISO on the IRB interface.
ACX Series routers support IRB for routing IPv4 packets. IPv6
and MPLS packets are not supported.
- Support for IGMP snooping (ACX Series)—Junos OS for ACX Series routers support IGMP snooping functionality.
IGMP snooping functions by snooping at the IGMP packets received by
the switch interfaces and building a multicast database similar to
that a multicast router builds in a Layer 3 network. Using this database,
the switch can forward multicast traffic only to the downstream interfaces
of interested receivers. This technique allows more efficient use
of network bandwidth, particularly for IPTV applications. You configure
IGMP snooping for each bridge on the router.
- Support for unicast reverse path forwarding (ACX
Series)—For interfaces that carry IPv4 or IPv6
traffic, you can reduce the impact of denial-of-service (DoS) attacks
by configuring unicast reverse path forwarding (RPF). Unicast RPF
helps determine the source of attacks and rejects packets from unexpected
source addresses on interfaces where unicast RPF is enabled.
Reverse path forwarding is not supported on the interfaces that
you configure as tunnel sources. This limitation affects only the
transit packets exiting the tunnel.
To configure unicast reverse path forwarding, issue the rpf-check statement at the [edit interfaces interface-name unit logical-unit-number family inet] hierarchy level. RPF fail filters are not supported
on ACX Series routers. The RPF check to be used when routing is asymmetrical
is not supported.
- Support for disabling local switching in bridge
domains (ACX Series)—In a bridge domain, when
a frame is received from a customer edge (CE) interface, it is flooded
to the other CE interfaces and all of the provider edge (PE) interfaces
if the destination MAC address is not learned or if the frame is either
broadcast or multicast.
To prevent CE devices from communicating directly include the no-local-switching statement at the [edit bridge-domains bridge-domain-name] hierarchy level. Configure the
logical interfaces in the bridge domain as core-facing (PE interfaces)
by including the core-facing statement at the [edit interfaces interface-name unit logical-unit-number family family] hierarchy level to specify
that the VLAN is physically connected to a core-facing ISP router
and ensure that the network does not improperly treat the interface
as a client interface. When local switching is disabled, traffic from
one CE interface is not forwarded to another CE interface.
- Support for hierarchical VPLS (ACX Series)—Hierarchical LDP-based VPLS requires a full mesh of tunnel
LSPs between all the PE routers that participate in the VPLS service.
Using hierarchical connectivity reduces signaling and replication
overhead to facilitate large-scale deployments. In a typical IPTV
solution, IPTV sources are in the public domain and the subscribers
are in the private VPN domain.
For an efficient delivery of multicast data from the IPTV source
to the set-top boxes or to subscribers in the private domain using
the access devices (ACX Series routers in this case), P2MP LSPs and
MVPN are necessary. Because VPLS and MVPN are not supported on ACX
routers, an alternative approach is used to achieve hierarchical VPLS
(HPVLS) capabilities. The subscriber devices are connected to a VPLS
or a Layer 3 VPN domain on the ACX Series (access) router and they
are configured to import the multicast routes. The support for PIM
snooping in Layer 3 interfaces, IGMP snooping in Layer 2 networks,
IRB interfaces, and logical tunnel interfaces enables HVPLS support.
No comments:
Post a Comment