# Configuring Bridged IP

To configure an ATM interface using bridged IP encapsulation:

1. Configure a physical interface.
   host1(config)#interface atm 0/1
2. Configure the subinterface.
   host1(config-if)#interface atm 0/1.20
3. Configure a PVC on the subinterface by specifying the virtual circuit descriptor (VCD), the virtual path identifier (VPI), the virtual channel identifier (VCI), and the encapsulation type.
   host1(config-if)#atm pvc 10 22 100 aal5snap
4. Configure bridged IP encapsulation.
   host1(config-if)#encapsulation bridge1483
5. Assign an IP address and subnet mask to the PVC.
   host1(config-subif)#ip address 192.168.10.20 255.255.255.0

   | Note: You can also assign an IP template to the interface or create an unnumbered interface instead of assigning an IP address. For details, see Configuring IP in JunosE IP, IPv6, and IGP Configuration Guide.

6. (Optional) Use the appropriate show commands to verify your configuration.
   host1#show atm interface 0/1 host1#show atm vc 0/1 10 host1#show atm subinterface 0/1.20

   For more information about using these commands, see Monitoring ATM in Configuring ATM .

atm pvc

- Use to configure a PVC on an ATM interface.
- The following fields are mandatory:
  - vcd—Unique number that identifies a virtual circuit in the range 1–2147483647. The VCD value has no relationship to the VPI and VCI values and has meaning only to the E Series router.
  - vpi—8-bit field in the ATM cell header. The VPI value is unique on a single link, not throughout the ATM network, because it has meaning only to the E Series router. The VPI value must match the value on the ATM switch.

    | Note: Do not set both the VPI and VCI values to zero.

  - vci—16-bit field in the ATM cell header. The VCI value is unique on a single link, not throughout the ATM network, because it has meaning only to the router. You cannot set both the VPI and VCI to 0.
  - encapsulation type:
    - aal5snap—Specifies a logical link control (LLC) encapsulated circuit. An LLC/Subnetwork Access Protocol (LLC/SNAP) header precedes the protocol datagram.
    - aal5muxip—Specifies a multiplexed circuit used for IP only.
- Example
  host1(config-if)#atm pvc 10 22 100 aal5snap
- Use the no version to remove the specified PVC.
- See atm pvc.

encapsulation bridge1483

- Use to configure bridged IP as the encapsulation method on an interface.
- Use the unrestrictedProxyArp keyword to allow the router to perform unrestricted processing of ARP requests even if the route is on the same interface on which the request is received. See Proxy ARP for details.
- Example
  host1(config-if)#encapsulation bridge1483
- Use the no version to remove bridged IP as the encapsulation method on the interface.
- See encapsulation bridge1483.

interface atm

- Use to configure an ATM interface.
- To specify an ATM interface for ERX7xx models, ERX14xx models, and ERX310 router, use the slot/port.[subinterface ] format.
  - slot—Number of the chassis slot
  - port—Port number on the I/O module
  - subinterface—Number of the subinterface in the range 1–2147483647
- To specify an ATM interface for E120 and E320 routers, use the slot/adapter/port[.subinterface ] format.
  - slot—Number of the chassis slot
  - adapter—Identifier for the IOA within the E320 chassis, either 0 or 1, where:
    - 0 indicates that the IOA is installed in the right IOA bay (E120 router) or the upper IOA bay (E320 router).
    - 1 indicates that the IOA is installed in the left IOA bay (E120 router) or the lower IOA bay (E320 router).
  - port—Port number on the IOA
  - subinterface—Number of the subinterface in the range 1–2147483647
- For more information, see Creating a Basic Configuration in Configuring ATM .
- Examples
  host1(config)#interface atm 3/1.20 host1(config)#interface atm 5/0/1.20
- Use the no version to remove the ATM subinterface or the logical interface.
- See interface atm.