> - Downloads
> - Configuring NIC Test Data (SRC CLI)
> - Related Topics
> - Planning a NIC Implementation
> - NIC Configuration Scenarios
> - High Availability for NIC
> - Configuring NIC Test Data (C-Web Interface)

> # Configuring NIC Test Data (SRC CLI)

> To test a resolution without NIC, you can configure a NIC proxy stub to take the place of the NIC. The NIC proxy stub comprises a set of explicit mappings of data keys and values in the NIC proxy configuration. When the SAE (or another SRC component configured to use a NIC proxy stub) passes a specified key to the NIC proxy stub, the NIC proxy stub returns the corresponding value. When you use a NIC proxy stub, no NIC infrastructure is required.

> For example, you can specify a subscriber’s IP address that is associated with a particular SAE. When the SRC component passes this IP address to the NIC proxy stub, the NIC proxy stub returns the corresponding SAE.

> To use the NIC proxy stub for the SAE:

> 1. In configuration mode, navigate to the NIC proxy configuration and specify the type of key you want to map to a value.
>    `
>    [edit shared sae configuration nic-proxy-configuration name]
>    user@host# set resolution key-type key-type
>    `

>    For example, to specify the key ip for the ip NIC proxy configuration:

>    `
>    [edit shared sae configuration nic-proxy-configuration ip]
>    user@host# set resolution key-type ip
>    `
> 2. Enable a NIC proxy stub for a resolution.
>    `
>    [edit shared sae configuration nic-proxy-configuration ip]
>    user@host# set test-nic-bindings user-test-bindings
>    `
> 3. Specify the values of the keys for testing. These statements are available at the Expert CLI editing level.
>    `
>    [edit shared sae configuration nic-proxy-configuration ip]
>    user@host# set test-nic-bindings key-values name value
>    `

>    where:

>    - name—Indicates the NIC data value for the proxy.
>    - value—Specifies a value for the NIC data type.

>    For example, to set up a login name to IP mapping for login name jane@virneo.com to the IP address 192.0.2.30:

>    `
>    [edit shared sae configuration nic-proxy-configuration ip]
>    user@host# set test-nic-bindings key-values jane@virneo.com 192.0.2.30
>    `

>    For example, to set up an IP to SAE ID mapping for IP address 190.0.2.30 to SAE ID identified by the URL for the CORBA IOR corbaloc::10.227.7.145:8801/SAE:

>    `
>    [edit shared sae configuration nic-proxy-configuration ip]
>    user@host# set test-nic-bindings key-values 192.0.2.30 corbaloc::10.20.7.145:8801/SAE
>    `

>    | Note: The SAE writes the value of the CORBA IOR to the var/run directory. The IP address in the corbaloc URL can be adjusted to the IP address or DNS name of the SAE.

>    You can use the key ANY_KEY to match any key for any key type. For example, if you want all IP addresses to resolve to the same SAE:

>    `
>    [edit shared sae configuration nic-proxy-configuration ip]
>    user@host# set test-nic-bindings key-values ANY_KEY corbaloc::10.20.7.145:8801/SAE
>    `

> #### Published: 2009-09-15

> Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.