Reviewing and Changing Operating Properties for the NIC (SRC CLI)
Before you configure a NIC configuration scenario, review the default operating properties and change values as needed. Operating properties are configured for a slot.
The following topics provide procedures for reviewing and changing operating properties for NIC with the SRC CLI:
Reviewing the Default NIC Operating Properties
To review the default NIC operating properties:
- From configuration mode, access the configuration statement
that specifies the configuration for the NIC on a slot.[edit]user@host# edit slot number nic
For example:
[edit]user@host# edit slot 0 nic - Run the show command.
[edit slot 0 nic] user@host# show base-dn o=umc; java-runtime-environment ../jre/bin/java; java-heap-size 128m; snmp-agent; hostname DemoHost; initial { dynamic-dn "ou=dynamicConfiguration, ou=Configuration, o=Management,<base>"; directory-connection { url ldap://127.0.0.1:389/; backup-urls ; principal cn=nic,ou=Components,o=Operators,<base>; credentials ********; timeout 10; check-interval 60; } directory-eventing { eventing; signature-dn <base>; polling-interval 15; event-base-dn <base>; dispatcher-pool-size 1; } static-dn "l=OnePop,l=NIC, ou=staticConfiguration, ou=Configuration, o=Manage ment,<base>"; }
Changing NIC Operating Properties
In most cases you can use the default NIC operating properties. Change the default properties if needed for your environment.
To change NIC operating properties:
- From configuration mode, access the configuration statement
that specifies the configuration for the NIC on a slot.[edit]user@host# edit slot number nic
For example:
[edit]user@host# edit slot 0 nic - (Optional) If you store data in the directory in a location
other than the default, o=umc, change this value.[edit slot 0 nic]user@host# set base-dn base-dn
- (Optional) Configure the garbage collection functionality
of the Java Virtual Machine.[edit slot 0 nic]user@host# set java-garbage-collection-options java-garbage-collection-options
- (Optional) If you determine that additional memory is
needed, change the maximum memory size available to the (Java Runtime
Environment) JRE.[edit slot 0 nic]user@host# set java-heap-size java-heap-size
By default, the JRE can allocate 128 MB. Set to a value lower than the available physical memory to avoid low performance because of disk swapping.
If you use an SAE plug-in agent, we recommend that you increase the JVM max heap to a value in the range 400–500 MB.
If you need help to determine the amount of memory needed, contact Juniper Networks Customer Services and Support.
- (Optional) Specify the name of the NIC scenario that you
want to configure. The default scenario is OnePop. [edit slot 0 nic]user@host# set scenario-name scenario-name
- (Optional) Enable viewing of SNMP counters through an
SNMP browser.[edit slot 0 nic]user@host# set snmp-agent
- (Optional) Change the name of the NIC host. Use the default
name of the NIC host configured for a NIC scenario. In most cases,
the NIC host name is DemoHost.[edit slot 0 nic]user@host# set hostname hostname
- (Optional) Change the initial properties.
See Configuring Basic Local Properties.
Related Documentation
- Reviewing and Changing Operating Properties for NIC (C-Web Interface)
- Configuring the NIC (SRC CLI)
- Configuration Statements for the NIC
- Changing NIC Configurations (SRC CLI)
- Verifying Configuration for the NIC (SRC CLI)