[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]

SDX 7.1.0 Release Notes > Release 7.1.0 > Known Behavior

Known Behavior

This section describes certain SDX software behaviors and related issues to emphasize how the system works.

ACP and NIC Installation

If either or both of these SDX components reside on the same system as another name server and that system becomes inaccessible, a redundant NIC or ACP is also inaccessible because clients cannot use the name server to resolve addresses and hostnames of the redundant NIC or ACP.

Reference: None

Aggregate Services

Reference: None

Configuration Updates

If you want to load the configuration for a specified hierarchy level:

If a file contains configuration statements other than those at and below the level identified by sdx:current=true, the command disregards the other statements.

If you enter a load command with the relative option and the file does not contain the text sdx:current=true, you receive a message indicating that the configuration cannot be loaded.

Reference: None

When you use the save command to save a configuration file, the file can include invalid data. This situation occurs because attributes that are not used in a configuration might be saved with no value in the configuration file. Attributes with no value are equivalent to undefined attributes and result in invalid data errors when you load the saved configuration.

When you use the load merge command to load a saved configuration that contains invalid data, you will see syntax error messages following a caret (^) which indicates the error location. These messages are followed by the Load Merge Complete message. All properly defined attributes are loaded, and the syntax error messages can safely be ignored.

For example, you might see the following error messages when you load a configuration that does not specify required values for options: 

                                                         ^

syntax error, expecting <data>.

                                                        ^

syntax error, expecting <data>.

                                                       ^

syntax error, expecting <data>.

                                                                        ^

syntax error, expecting <data>.

                                                                          ^

syntax error, expecting <data>.

                                                                        ^

syntax error, expecting <data>.

                                                                          ^

syntax error, expecting <data>.

                                                          ^

syntax error, expecting <data>.

Load Merge Complete

Reference: TIC 13650

Juniper Networks Database

We recommend that you configure two to four Juniper Networks databases as primary databases in a community. If you plan to use more than two Juniper Networks databases in a primary role and expect to have frequent updates to the Juniper Networks database, we recommend that you test your application scenario with a projected traffic load. For assistance testing your application scenario, contact Juniper Networks Professional Services or JTAC.

Reference: None

If you run Juniper Networks databases in community mode, the Juniper Networks database configured to be part of a community require hostname configuration.

You can either configure Domain Name System (DNS) and enter the hostnames into DNS or configure the names as static hostnames.

Reference: TIC 13364

When you change the mode of two Juniper Networks databases from standalone to community, and assign one a primary role and the other a secondary role, review the error log in the /var/UMC/jdb/log directory on the primary Juniper Networks database for the following message:

[22/Mar/2007:11:27:15 -0400] agmt="cn=champ2golem.kanlab.jnpr.net" 
(golem:389) - Can't locate CSN 46029ccc000000010000 in the changelog (DB 
rc=-30990). The consumer may need to be reinitialized.

Workaround: If you see a similar message, change the mode of the secondary Juniper Networks database from community to standalone, then back to community.

For information about configuring Juniper Networks databases, see the SRC-PE Getting Started Guide.

Reference: TIC 13371

If you change the role of a Juniper Networks database from primary to secondary, restart the Juniper Networks database after you set the role to secondary. If you do not restart the database, you receive a message similar to the following one at the CLI:

javax.naming.NamingException: [LDAP: error code 1 - Mapping tree node for 
o=umc is set to return a referral, but no referral is configured for it]; 
remaining name 'retailerName=default,o=users,o=UMC'

commit completed with the above exception(s).

Reference: TIC 13372

When you delete statements from the CLI for a Juniper Networks database assigned a secondary role, you can receive a message for ContextNotEmptyException such as:

[edit]

root@golem# commit 

javax.naming.ContextNotEmptyException: 
ou=local,retailerName=ldapcommret1,o=users,o=UMC cannot be deleted

commit completed with the above exception(s).



commit complete.

Workaround: Enter the commands to delete the same statements from a Juniper Networks database assigned a primary role. Whenever you delete statements for a Juniper Networks database, do so from a Juniper Networks database assigned a primary role.

Reference: TIC 13376

JPS

Reference: TIC 11909

Policy Editor

Workaround: To access the first entry field:

  1. Click the second input field.

The text that you typed appears in the second input field, and the first input field now allows text entry.

  1. Enter text in the first input field.

Reference: TIC 10610

SAE

If you delete the SAE shared properties group in the directory—that is, /SAE/POP-ID—this group cannot be re-created.

Reference: TIC12488

If you want to use the configuration group POP-ID for the SAE, edit the SAE shared properties at the [edit slot 0 sae] hierarchy level, then the group properties.

Workaround: Configure a group for POP-ID within the SAE. To do so:

  1. At the [edit slot 0 sae] hierarchy level, specify POP-ID.
    2. [edit slot 0 sae]

    user@host# set shared /SAE/POP-ID

    

    user@host# commit

    commit complete.
  2. Review the local properties.
    3. user@host# show 

    real-portal-address 10.10.4.24;

    shared /SAE/POP-ID;

    initial { 

      directory-connection { 

        url ldap://127.0.0.1:389/;

        principal cn=ssp,ou=Components,o=Operators,<base>;

        credentials ********;

        blacklist;

      }

      directory-eventing { 

        eventing;

        polling-interval 30;

      }

    }

    radius { 

      local-address 10.10.4.24;

      local-nas-id SAE.myCseries;

    }
  3. Change properties as needed (you must change at least one value to create the POP-ID group) and commit the configuration.
  4. Configure the group within a shared SAE configuration.
    5. [edit]

    user@host# edit shared sae group POP-ID

Reference: TIC12487

If you run the show sae slot 0 statistics process command shortly after you start the SAE, the CLI may become inoperative.

Workaround: Wait for several minutes after you start the SAE before you run the show sae slot 0 statistics process command. If the CLI becomes inoperative, press Ctrl+c, wait a few seconds, and enter the command again.

Reference: TIC13387

You can ignore messages similar to the one above.

Reference: TIC 12059

You can ignore messages similar to the one above.

Reference: TIC 10927

Reference: TIC 9612

Reference: TIC 9506

SDX Installation Program

Reference: TIC 10706

Updated Documentation for the NIC

Updated Documentation for the Juniper Networks Database

You can initialize a Juniper Networks database with data from a neighbor. This process takes the following actions on the database to be initialized:

To replace data on a neighbor database (for example, neighbor1):

Reference: TIC 14230

Updated Documentation for CoA Script Service

The following example is correct:

"start-stop.Acct-Session-Id=ifSessionId\nstart.vendor-specific.9.
252.string='\\\\x0bBOD1M'\nstop.vendor-specific.9.252.string=
'\\\\x0cBOD1M'\n"

Reference: TIC 14294

[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]