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:
To review the default NIC operating properties:
For example:
[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>";
}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:
For example:
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.