interface ge-2/2/4.0;
interface ge-2/2/6.0;
}
}
}
}
}
}
You verify your configuration by using two related commands:
•
show dhcp relay binding routing-instance vs1 bridge-domains bd1
•
show dhcp relay binding routing-instance vs1 bridge-domains bd1 detail
user@router1> show dhcp relay binding routing-instance vs1 bridge-domains bd1
2 clients, (2 bound, 0 selecting, 0 renewing, 0 rebinding)
IP address Hardware address Type Lease expires at
192.168.1.1 00:00:00:42:a8:e3 active 2008–12–12 15:56:04 PST
192.168.1.2 00:00:00:42:a8:e4 active 2008–12–12 15:56:10 PST
user@router1> show dhcp relay binding routing-instance vs1 bridge-domains bd1 detail
2 clients, (2 bound, 0 selecting, 0 renewing, 0 rebinding)
Clients bindings information:
IP address : 192.168.1.1
Hardware address : 00:00:00:42:a8:e3
Type : active
Lease expires at : 2008–12–12 15:56:04 PST
State : bound
interface : ge—2/2/6.0
IP address : 192.168.1.2
Hardware address : 00:00:00:42:a8:e4
Type : active
Lease expires at : 2008–12–12 15:56:10 PST
State : bound
interface : ge—2/2/4.0
Related
Documentation
• DHCP Relay Agent
• MX Series Router as a Layer 2 DHCP Relay Agent on page 73
• Example: Configuring DHCP Relay in a Bridge Domain VLAN Environment on page 74
Copyright © 2012, Juniper Networks, Inc.76
Junos OS 12.1 MX Series 3D Universal Edge Routers Solutions Guide
To Next Page
Loading...
Need help?
General
