Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring the Same IP Address on Multiple Interfaces

By default, all interfaces are assumed to be point-to-point (PPP) interfaces. For all interfaces except aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet, you can explicitly configure an interface to be a point-to-point connection.
You can configure the same IPv4 address on multiple physical interfaces. When you assign the same IPv4 address to multiple physical interfaces, the operational behavior of those interfaces differs, depending on whether they are implicitly or explicitly point-to-point . This topic describes how to configure the same IPv4 address on multiple interfaces and how to view their operational status after such a configuration has been committed.

To configure the same IPv4 address on one or more interfaces specify the same value for the address option in the family inet statement:

You can include this statement at the following hierarchy level:

[edit interfaces interface-name unit logical-unit-number family inet]

• Configuring same IPv4 address on implicitly PPP interfaces:

  [edit]user@host# show

  ge-0/1/0 { unit 0 {family inet {address 200.1.1.1/24;}}}
  ge-3/0/1 { unit 0 {family inet {address 200.1.1.1/24;}}}
  The sample output shown below for the above configuration reveals that only ge-0/1/0.0 was assigned the same IPv4 address 200.1.1.1/24 and its link state was up, while ge-3/0/1.0 was not assigned the IPv4 address, though its link state was up, which means that it will be operational only when it gets a unique IPv4 address other than 200.1.1.1/24.

  show interfaces terse

  user@host> show interfaces terse ge*

  Interface               Admin Link Proto    Local                 Remote
          ge-0/1/0                up    up
          ge-0/1/0.0              up    up   inet     200.1.1.1/24
                                     multiservice
          ge-0/1/1                up    down
          ge-3/0/0                up    down
          ge-3/0/1                up    up
          ge-3/0/1.0              up    up   inet
                                     multiservice

• Configuring same IPv4 address on explicitly PPP interfaces:

  [edit]user@host# show

  so-0/0/0 { unit 0 {family inet {address 200.1.1.1/24;}}}

  so-0/0/3 { unit 0 {family inet {address 200.1.1.1/24;}}}
  The sample output shown below for the above configuration reveals that both so-0/0/0.0 and so-0/0/3.0 were assigned the same IPv4 address 200.1.1.1/24 and that their link states were down, which means that to make them operational atleast one of them will have be configured with a unique IPv4 address other than 200.1.1.1/24.

  show interfaces terse

  user@host> show interfaces terse so*

  Interface               Admin Link Proto    Local                 Remote
  so-0/0/0                up    up
  so-0/0/0.0              up    down inet     200.1.1.1/24
  so-0/0/1                up    up
  so-0/0/2                up    down
  so-0/0/3                up    up
  so-0/0/3.0              up    down inet     200.1.1.1/24
  so-1/1/0                up    down
  so-1/1/1                up    down
  so-1/1/2                up    up
  so-1/1/3                up    up
  so-2/0/0                up    up
  so-2/0/1                up    up
  so-2/0/2                up    up
  so-2/0/3                up    down