1 Summary of Supported Features

This chapter provides an overview of Oracle Communications IP Service Activator support for Juniper M-series and T-series devices.

Supported IP Service Activator Features

This section provides an overview of how the various features and configurations modelled in IP Service Activator are mapped to and supported on Juniper hardware.

IP Service Activator supports the provisioning of a rich set of advanced features on Juniper hardware including QoS, a wide range of tunnelling protocols (MPLS VPNs, Layer 2 Martini VPNs, and MPLS LSPs), and routing protocols including eBGP, OSPF, RIP and static routing.

Note:

The provisioning and configuration features supported by IP Service Activator require the Internet Processor II ASIC. This is standard on all Juniper models except early versions of M20 and M40 devices, where it is optional.

The Juniper M-series Device Driver also supports the Configuration Template Module (CTM) which helps you to streamline the activation of services on network objects through the use of pre-defined or customized templates. For details, see the Configuration Template Module online Help.

QoS and Access Control Support

Table 1-1 lists the QoS and access control features that IP Service Activator supports on Juniper devices. For full details about these features and the way in which they are implemented, see Chapter 7, "Configuring QoS and Access Control Features".

Table 1-1 Supported QoS and Access Control Features

Type	IP Service Activator Feature	Internet Processor II
Policy rule	Access rules	Y
Policy rule	Classification rules	N
Policy rule	Policing rules	N
Marking	DiffServ codepoints (0-63)	N
Marking	IPv4 Precedence field	N
Marking	IPv4 ToS bits	N
Marking	MPLS experimental bits	N
Marking	MPLS Topmost experimental bits	N
Traffic classification	IP Address (source/destination)	Y
Traffic classification	IP Port (source/destination)	Y
Traffic classification	IP Protocol	Y
Traffic classification	Packet marking traffic type	Y
Traffic classification	URL traffic type	N
Traffic classification	MIME traffic type	N
Traffic classification	Application protocol traffic type	N
Traffic classification	Domain Name traffic type	N
PHB groups	Rate Limiting	Y
PHB groups	WRED	N
PHB groups	WFQ	N
PHB groups	WRR	Y
PHB groups	Priority Queuing	N
PHB groups	ATM Traffic Shaping	N
PHB groups	FRTS Traffic Shaping	N
PHB groups	MQC	N

MPLS VPN Support

Table 1-2 lists the MPLS VPN features that IP Service Activator supports on Juniper devices. For full details about these features and the way in which they are implemented, see Chapter 5, "Configuration of MPLS VPNs".

Table 1-2 Supported MPLS VPN Features

Type	IP Service Activator Feature	Internet Processor II
VRF table	User-defined VRF table name	Y
VRF table	VRF re-use/reduction	Y
VRF table	User-defined RD numbers	Y
VRF table	User-defined RT numbers	Y
VRF table	RDs per VPN	Y
VRF table	VRF route limit (max routes	Y
VRF table	Co-existence with pre-defined VRFs	Y
VRF table	Pre-defined export maps	Y
PE-PE peering (iBGP)	iBGP peering optional	Y
PE-PE peering (iBGP)	Maximum paths	Y
PE-PE peering (iBGP)	Extended/standard community attributes (This feature is not available on Juniper M-series or T-series devices.)	N
PE-PE peering (iBGP)	PE-PE MD5 authentication	Y
PE to CE connectivity	eBGP	Y
PE to CE connectivity	OSPF	Y
PE to CE connectivity	RIP	Y
PE to CE connectivity	Static routing	Y
eBGP configuration	AS override	Y
eBGP configuration	Allow AS in	Y
eBGP configuration	Extended/standard community attributes (This feature is not available on Juniper M-series or T-series devices.)	N
eBGP configuration	Local preference	Y
eBGP configuration	PE-CE authentication	Y
eBGP configuration	Prefix filters	Y
eBGP configuration	Prefix limit	Y
eBGP configuration	Site of origin	Y
eBGP configuration	Multi-path load sharing	Y
eBGP configuration	Route dampening	Y
eBGP configuration	Route redistribution into eBGP	Y
OSPF	Route redistribution into OSPF	Y
OSPF	Domain Tag	Y
RIP	Route redistribution into RIP	Y
Static configuration	Global routes	Y
Static configuration	Permanent routes	Y

Layer 2 Martini VPN Support

Table 1-3 lists the Layer 2 Martini VPN features that IP Service Activator supports on Juniper devices. For full details about these features and the way in which they are implemented, see Chapter 6, "Configuring Layer 2 Martini VPNs".

Table 1-3 Supported Layer 2 Martini VPN Features

Type	IP Service Activator Feature	Internet Processor II
Layer 2 Martini VPN	Layer 2 Martini VPN	Y
Layer 2 Martini VPN	Provisioned sub-interfaces	Y
Layer 2 Martini VPN	Virtual Circuit ID	Y
Encapsulation	Frame Relay ATM AAL5	Y
Encapsulation	Frame Relay ATM Cell	Y
Encapsulation	Frame Relay	Y
Encapsulation	Ethernet	Y
Encapsulation	Ethernet VLAN	Y

MPLS Label Switched Path (LSP) Support

Table 1-4 lists the MPLS LSP features that IP Service Activator supports on Juniper devices.

Table 1-4 Supported MPLS LSP Features

Type	IP Service Activator Feature	Internet Processor II
Tunnel	Hold and Setup Priority	Y
Tunnel	Admin Groups (Coloring)	Y
Tunnel	IGP Metric	Y
Tunnel	LDP	Y
Protection	Fast Re-Route	Y
Protection	Node and Link Protection	Y
Paths	Primary and Secondary Paths	Y
Paths	Next Hop Lists	Y
Paths	Exclude Address Lists	Y
Paths	Dynamic and Explicit Paths	Y

Supported Juniper M-series and T-series Hardware and Software

The Juniper M-series Device Driver is effectively capable of configuring any JUNOS-based device. The exact capabilities that can be supported by IP Service Activator depend on the device model, the operating system that it is running and the interface.

If you are using, or wish to use, different hardware or software from that defined here, please contact Global Customer Care.

Supported Devices

The Juniper M-series Device Driver supports Junos-based M- and T-series devices.

Supported JUNOS Versions

Refer to IP Service Activator Release Notes for your IP Service Activator software release for support information for the specific releases of the JUNOS operating system.

Juniper-supported Interface Types

Juniper devices support a wide range of interfaces. The Juniper device driver supports a subset of these interfaces. For information on Juniper interface types available, consult the Juniper website:

http://www.juniper.net

Table 1-5 summarizes support for interface types on those Juniper M-series and T-series devices that are supported by IP Service Activator.

Table 1-5 Interface Types Supported on Juniper M-series and T-series Devices

Supported Juniper Interface Configuration Prefix	Physical Interface
ae	aggregated Ethernet
as	aggregated Sonet/SDH
at	ATM
ds	DS0
e1	E1
e3	E3
fe	Fast Ethernet
fx	management internal ethernet interfaces
ge	Gigabit Ethernet
gr	Generic Route Encapsulation (GRE) tunnel
ip	IP-overIP encapsulation tunnel
lo	Loopback
ml	Multilink
mt	Multicast tunnel
so	SONET/SDH
t1	T1
t3	T3
vt	Virtual loopback tunnel

Supported Traffic Types

Table 1-6 lists the traffic classification types that are supported on Juniper M-series devices.

Table 1-6 Traffic Types Supported on Juniper M-series Devices

Traffic Type	Supported on Juniper M-series
Port/IP protocol	Y
DiffServ codepoint	Y
IP Precedence	N
MPLS experimental bits	N
Domain	N
Application	N
Sub-application	N
URL	N
MIME	N

Enhanced Command Threshold Control for Juniper Device Driver

The Juniper Device Driver (JDD) command threshold is used to monitor configuration differences between routing-instance and interface counts. It was previously able to address only one criteria at a time, whereby the user was unable to select routing-instance and interface at the same time.

To address this issue, JDD configuration thresholding has been enhanced to monitor routing-instance deletions that affect a certain number of interfaces, and block the configuration based on that specific number of interfaces crossing the threshold value for service-instance, on a per service-instance basis.

The enhanced command threshold control in JDD is to extend the logic for the routing-instance. The Command Threshold configured in the device properties is checked against each of the following criteria:

• Number of routing-instances that are getting deleted.

• Number of interfaces linked to a routing-instance that is getting deleted.

  Note:

  The user must check every routing-instance that is getting deleted one by one.

If one of the above numbers exceeds the threshold, then the changes must be blocked. This feature is supported only on Juniper Device Driver.