Integration Tasks

To integrate the JUNOSe router into the SDX network, you must:

1. Configure the SAE to manage the JUNOSe router.
2. Configure the JUNOSe router to interact with the SAE.
3. Add the JUNOSe router and its virtual routers to the directory.

Configuring the SAE to Manage JUNOSe Routers

To configure the SAE to manage a JUNOSe router, you must install the SDX software and configure the SAE to interact with the JUNOSe router. For information about these tasks see the SDX Software Basics Guide and SDX Components Guide, Vol. 1, Chapter 2, Configuring the SAE.

Configuring the JUNOSe Router to Interact with the SAE

You should be familiar with the CLI for the JUNOSe router. The JUNOSe router employs an SDX client to interact with the SAE. See JUNOSe Broadband Access Configuration Guide and JUNOSe Command Reference Guide for complete information about configuring the SDX client on the JUNOSe router. To begin configuration of the SDX client on the JUNOSe router, Telnet to the router and access Global Configuration mode:

host1#configure terminal

Configuring the SNMP Server on the JUNOSe Router

The various scripts in the SDX software use SNMP to get necessary information. For example, staticRoute route script uses SNMP to install the route for the virtual IP address. The poolPublisher script uses SNMP to read the IP pools.

Access to the SNMP server by an SNMP client is governed by a proprietary SNMP community table that identifies those communities that have read-only, read-write, or administrative permission to the SNMP MIB stored on a particular server.

When an SNMP server receives a request, the server extracts the client's IP address and the community name. The SNMP community table is searched for a matching community. If a match is found, its access list name is used to validate the IP address. If the access list name is null, the IP address is accepted. A nonmatching community or an invalid IP address results in an SNMP authentication error.

To configure the SNMP agent:

1. Switch to the virtual router for which you want to create an SDX client.

host1#(config)virtual-router <vrName>

2. Enable the SNMP agent.

host1:<vrName>#(config)snmp-server

3. Configure at least one authorized SNMP read-write community (SNMPv1/v2c), which provides SNMP client access.

host1:<vrName>(config)#snmp-server community boston rw

4. (Optional) Configure a read-only community.

host1:<vrName>#(config)snmp-server public ro

On the SAE side, you use SDX Admin to configure the community string(s) for individual VRs where an SNMP server has been configured. The community string(s) are stored in the directory for that VR under o=umc, o=Network, orderedCimKeys=<edge device>. If a VR does not exist on the JUNOSe router or the community strings have not been configured for the VR, then the SAE uses the default community values configured in the SAE property object:

• Router.read-only.community.string
• Router.read-write.community.string

These global default values are configurable via the Router tab of the SDX Configuration Editor.

You can optionally configure other settings for the SNMP server on the JUNOSe router. See the documentation for the JUNOSe router for more information.

Starting the SDX Client on the JUNOSe Router

To start the SDX client:

1. Switch to the virtual router for which you want to create an SDX client.

host1(config)#virtual-router <vrName>

2. Enable the SDX client.

host1:<vrName>(config)#sscc enable cops-pr

3. Set the primary address from the configuration directory.

host1:<vrName>(config)#sscc primary address <ipAddress> port 3288

Stopping the SDX Client on the JUNOSe Router

To stop the SDX client:

host1:<vrName>(config)#no sscc enable

Adding JUNOSe Routers to the Directory

You must add each JUNOSe router that the SAE manages to the directory. For information about this procedure, see SDX Objects Guide, Chapter 4, Managing Routers and Virtual Routers.