Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


passive (Protocols IS-IS)


Hierarchy Level


Advertise the direct interface addresses on an interface or into a level on the interface without actually running IS-IS on that interface or level.

This statement effectively prevents IS-IS from running on the interface. To enable IS-IS on an interface, include the interface statement at the [edit protocols isis] or the [edit routing-instances routing-instance-name protocols isis] hierarchy level. To disable it, include the disable statement at those hierarchy levels. The three states—enabling, disabling, or not running IS-IS on an interface—are mutually exclusive.


Configuring IS-IS on a loopback interface automatically renders it as a passive interface, irrespective of whether the passive statement was used in the configuration of the interface.

If neither passive mode nor the family iso option is configured on the IS-IS interface, then the routing device treats the interface as not being operational, and no direct IPv4/IPv6 routes are exported into IS-IS. (You configure the family iso option at the [edit interfaces interface-name unit logical-unit-number] hierarchy level.)


By default, IS-IS must be configured on an interface or a level for direct interface addresses to be advertised into that level.


remote-node-id address

IP address of the remote link.

remote-node-iso iso-id

ISO ID of the remote node.


The options remote-node-id address and remote-node-iso iso-id do not apply under the [edit routing-instances routing-instance-name protocols isis] hierarchy level.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced before Junos OS Release 7.4.

remote-node-id address option introduced in Junos OS Release 14.2.

remote-node-iso iso-id option introduced in Junos OS Release 14.2.