SDX 6.4.x Network Guide > Reviewing the NIC Configuration > Router Access Agents

Router Access Agents

Router access agents communicate with a JUNOSe router through SNMP and can obtain information from the routing tables. These agents are active.

The SDX software supports one type of router access agent that obtains from the JUNOSe Open Shortest Path First (OSPF) MIB the mapping of an IP pool to the router interface to which a subscriber connects. This router access agent obtains the information from the router as follows:

1. The agent establishes an SNMP session with its associated router and accesses the relevant routing tables.
2. The agent filters the entries in the tables and stores the data that the filter accepts.
3. The agent may use the data in a routing table directly or may use data in routing tables to access data in the forwarding table and other routing tables.
4. When the agent has the data it requires, it publishes an event.
5. The agent also registers to receive the appropriate SNMP traps.
6. When the agent receives an SNMP trap from the router, it filters that trap. If the filter accepts the trap, the agent generates data and publishes the event.

Reviewing the Configuration of Router Access Agents

To use SDX Configuration Editor to review the configuration for NIC router access agents:

1. In the navigation pane, select a NIC configuration file.
2. Click the Agents tab, and expand the Router Access Agent section.
3. Review the entries in the fields.

See Router Access Agent Fields.

Router Access Agent Fields

In SDX Configuration Editor, you can modify the following fields in the Router Access Agent section of the Agents pane in a NIC configuration file.

Resolvers List

• Names of NIC resolvers to which this agent sends events.
• Value—Comma-separated list of paths to NIC resolvers relative to the Static Configuration object.
• Example—/realms/assignedIp/B1, /realms/assignedIp/A1
• Property name—pushToServer

Roles List

• Names of the NIC roles.
• Value—Comma-separated list of roles in the format <realmName>:<roleName>

• <realmName>—Name of realm
• <roleName>—Name of role

• Property name—pushToRole

Primary Router ID

• IP address of the JUNOSe router on which the OSPF link-state advertisement (LSA) database resides.
• Value—IP address
• Example—127.0.0.1
• Property name—snmpRouterId

SNMP Port

• TCP port on the JUNOSe router to which the agent connects.
• Value—Number of TCP port
• Default—161
• Property name—snmpPort

Local Port

• TCP/IP port on which the agent listens for SNMP traps.
• Value—Number of TCP port
• Default—162
• Property name—localPort

SNMP Community String

• SNMP community string that identifies the group of JUNOSe routers with which the agent can establish SNMP sessions.
• Value—Text string
• Default—Public
• Property name—snmpCommunityString

SNMP Timeout Value

• Time after which the agent terminates SNMP operation.
• Value—Number of seconds in the range 0-4294967295
• Default—5
• Property name—snmpTimeout

SNMP Retries Value

• Number of times that the agent tries to complete an SNMP operation.
• Value—Integer in the range 0-4294967295
• Default—3
• Property name—snmpRetries

Event Filter

• Filter that determines which LSAs in the OSPF table or in the trap the agent should receive. This filter is similar to an LDAP filter.
• Value—Filter := '(' <fexp> ')'

• fexp := (<list-op> <filter>+) | (! <filter>) | (<att-name> = <value>)

• <list-op>—'!' is the not operator, '&' the and, and '|' the or.
• <att-name>—Name of the OSPF object type as specified in the LSA database or the OSPF traps. The following attributes are available: ospfRouterId, ospfLsdbArea, ospfLsdbType, ospfLsdbLsid, ospfLsdbRouterId.
• <value>—Any string representation of a value accepted by the object.

• Guidelines—The following characters are reserved. Precede them with a '\' (backslash) if you use them in a string: '*', '(', ')', '!', '&', '|', and '='.
• Example—(|(ospfLsdbType=4)(ospfLsdbType=5))
• Property name—eventFilter

Network Data Types

• Data types that the agent publishes. For names of data types, see Chapter 10, NIC Resolution Process.
• Value—<key> or <key>, <value>

• <key>—Name of data key
• <value>—Name of data value

• Example—IpPool, InterfaceId
• Property name—networkDataTypes

Publishing Interval

• Interval at which the NIC agent sends updates to the NIC resolvers.
• Value—Number of seconds in the range 0-2147483647
• Default—60
• Property name—publishingInterval

Event Life Expectancy

• Length of time that data is valid after the NIC proxy receives data associated with events published by this agent
• Value—Number of seconds in the range 0-4294967295

• 0—Data does not expire
• Other values—Actual life expectancy of data

• Default—0
• Property name—eventLifeExpectancy