interface-type (Protocols OSPF)
Syntax
interface-type (nbma | p2mp | p2mp-over-lan | p2p) {
ipsec-sa;
ldp-synchronization {
(disable | enable);
hold-time;
}
metric;
mtu;
neighbor address {
eligible;
}
no-advertise-adjacency-segment;
no-eligible-backup;
no-eligible-remote-backup;
no-interface-state-traps;
no-neighbor-down-notification;
node-link-protection;
passive {
traffic-engineering {
remote-node-id;
remote-node-router-id;
}
}
poll-interval;
priority;
retransmit-interval;
secondary;
te-metric;
topology (default | ipv4-multicast | name);
transit-delay;
bandwidth-based-metrics;
bfd-liveness-detection;
dead-interval;
demand-circuit;
disable;
dynamic-neighbors;
flood-reduction;
hello-interval;
link-protection;
own-router-lsa;
}
Hierarchy Level
[edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name protocols ospf3 realm (ipv4-multicast | ipv4-unicast | ipv6-multicast) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf3 realm (ipv4-multicast | ipv4-unicast | ipv6-multicast) area area-id interface interface-name], [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols ospf3 realm (ipv4-multicast | ipv4-unicast | ipv6-multicast) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name], [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4-multicast | ipv4-unicast | ipv6-multicast) area area-id interface interface-name]
Description
Specify the type of interface.
By default, the software chooses the correct interface type based on the type of physical interface. Therefore, you should never have to set the interface type. The exception to this is for NBMA interfaces, which default to an interface type of point-to-multipoint. To have these interfaces explicitly run in Nonbroadcast multiaccess (NBMA) mode, configure the nbma interface type, using the IP address of the local ATM interface.
In Junos OS Release 9.3 and later, a point-to-point interface can be an Ethernet interface without a subnet.
Default
The software chooses the correct interface type based on the type of physical interface.
Options
| nbma (OSPFv2 only) | Nonbroadcast multiaccess (NBMA) interface |
| p2mp | Point-to-multipoint interface |
| p2mp-over-lan | Point-to-multipoint over LAN mode |
| p2p | Point-to-point interface |
The remaining statements are explained separately. See CLI Explorer.
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.
Support for OSPFv3 for interface type p2p only introduced
in Junos OS Release 9.4. You cannot configure other interface
types for OSPFv3.
Support for OSPFv3 for interface type p2mp is introduced
in Junos OS Release 18.1R1.
Support for OSPFv3 for interface type p2p only introduced
in Junos OS Release 9.4 for EX Series switches.