Configure Peer Interfaces on OSPF and RSVP

After you establish LMP peers, add peer interfaces to OSPF and RSVP. A peer interface is a virtual interface used to support a control adjacency between two peers. OSPF and RSVP form adjacencies between peers by using the peer interfaces instead of the physical interfaces.

Because actual protocol packets are sent and received by peer interfaces, the peer interfaces can be signaled and advertised to peers like any other interface enabled for RSVP and OSPF. The peer interface name must match the peer name configured in LMP. To configure RSVP signaling for LMP peers, include the peer-interface statement at the [edit protocols rsvp] hierarchy level. To configure OSPF routing for LMP peers, include the peer-interface statement at the [edit protocols ospf area area-number] hierarchy level.

[edit]

protocols {

    rsvp {

        peer-interface peer-name {                                    # Configure the name of your LMP peer.

    }

    ospf {

        area area-number {

            peer-interface peer-name {                                    # Configure the name of your LMP peer.

        }

    }

}

 When adding the virtual peer interfaces to RSVP and OSPF, do not configure the corresponding physical control channel interface in either protocol. If the interface all option is used, you must disable the protocols manually on the control channel interface. 

  
 To disable OSPF, use the disable statement at the [edit protocols ospf area area-number interface interface-name] hierarchy level.
  
 To disable RSVP, use the disable statement at the [edit protocols rsvp interface interface-name] hierarchy.