Example: Configuring ES-IS for CLNS
This example shows how to create a routing instance and enable ES-IS for CLNS on all interfaces.
Before you begin, configure the network interfaces. See Interfaces User Guide for Security Devices.
The configuration instructions in this topic describe how to create a routing-instance called aaaa, set the end system configuration timer for the interfaces to 180, and set a preference value to 30 for ES-IS.
CLI Quick Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the  hierarchy level, and then enter commit from configuration mode.
The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.
To configure ES-IS for CLNS:
- Configure the routing instance.user@host# edit routing-instances aaaa
- Enable ES-IS on all interfaces.[edit routing-instances aaaa]user@host# set protocols esis interface all
- Configure the end system configuration timer.[edit routing-instances aaaa]user@host# set protocols esis interface all end-system-configuration-timer 180
- Configure the preference value.[edit routing-instances aaaa]user@host# set protocols esis preference 30
From configuration mode, confirm your configuration by entering the show routing-instances command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
If you are done configuring the device, enter commit from configuration mode.
Confirm that the configuration is working properly.
Verifying Routing-Instance for CLNS
Verify that the policy options are enabled for the routing instance.
From operational mode, enter the show routing-instances command.
Verifying ES-IS for CLNS
Verify that ES-IS is enabled.
From operational mode, enter the show protocols command.