J-series Services Router Features

This section describes the new J-series Services Routers features, available with the JUNOS 8.5R3 release. For more information, see the following manuals:

• J2320, J2350, J4350, and J6350 Services Router Getting Started Guide
• J2300, J4300, and J6300 Services Router Getting Started Guide
• J-series Services Router Basic LAN and WAN Access Configuration Guide
• J-series Services Router Advanced WAN Access Configuration Guide
• J-series Services Router Administration Guide

Platform and Infrastructure

• Support for bidirectional NAT—You can now specify the Network Address Translation (NAT) type for a particular term in a NAT rule as either traditional (symmetric) NAT or full-cone NAT, in which all requests from the same internal IP address are mapped to the same external IP address. Port mapping is also supported, but not required. To configure this feature, include the nat-type statement at the [edit services nat rule rule-name term term-name] hierarchy level. By default, symmetric NAT is supported.

Interfaces and Chassis

• Support for high-density TIMs—J-series Services Routers now support the following high-density Telephony Interface Modules (TIMs) for Avaya VoIP service:
  • TIM508—Avaya TIM with 8 analog telephone ports. You can configure these ports as direct inward dialing (DID) trunk ports.
  • TIM516—Avaya TIM with 16 analog telephone ports. You can configure 8 of these ports as DID trunk ports.
  • TIM518—Avaya TIM with 8 analog telephone ports and 8 analog trunk ports. You can configure some or all of the line ports as analog DID trunk ports.
• USB modem support for WAN backup—A USB modem interface can now back up a primary Internet connection. You can configure J-series Services Routers to fail over to a USB modem connection when the primary connection experiences interruptions in Internet connectivity. The USB modem interface supports all features that WAN interfaces support. For example:
  • Class of service (CoS)
  • Services such as Network Address Translation (NAT), stateful firewall filters, and Generic Routing Encapsulation (GRE) tunneling
  • Packet capture (PCAP), sampling, and tcpdump
  • Interface statistics

  To specify whether dial-in calls are for management console access or routable calls, include the dialin (console | routable) statement at the [edit interfaces umd0 modem-options] hierarchy level.

• Routing policy for source-class and destination-class usage—You can now configure routing policy for source-class usage (SCU) and destination-class usage (DCU) on J-series Services Routers. SCU counts packets sent to customers by performing lookup on the IP source address. DCU counts packets from customers by performing lookup on the IP destination address. Configure the routing policy at the [edit policy-options policy-statement statement-name] hierarchy level. Enable packet counting on an interface at the [edit interfaces interface-name unit unit-number family family-name accounting] hierarchy level.