- play_arrow Login Classes and Login Settings
- play_arrow User Accounts
- play_arrow Passwords for User Access
- play_arrow Trusted Platform Module
- play_arrow User Authentication
- play_arrow Remote Access Management
- play_arrow Access Control
- Access Control Authentication Methods
- Preventing Unauthorized Access to EX Series Switches Using Unattended Mode for U-Boot
- Preventing Unauthorized Access to EX Series Switches Using Unattended Mode for U-Boot
- RADIUS Server Configuration for Authentication
- RADIUS over TLS (RADSEC)
- 802.1X Authentication
- MAC RADIUS Authentication
- Service-Type Attribute and Jumbo Frame Handling Overview
- 802.1X and RADIUS Accounting
- Example: Setting Up 802.1X for Single-Supplicant or Multiple-Supplicant Configurations on an EX Series Switch
- Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors on an EX Series Switch
- Interfaces Enabled for 802.1X or MAC RADIUS Authentication
- Static MAC Bypass of 802.1X and MAC RADIUS Authentication
- Configuring PEAP for MAC RADIUS Authentication
- Captive Portal Authentication
- Flexible Authentication Order on EX Series Switches
- Server Fail Fallback and Authentication
- Authentication Session Timeout
- Central Web Authentication
- Dynamic VLAN Assignment for Colorless Ports
- VoIP on EX Series Switches
- play_arrow Configuring IEEE 802.1x Port-Based Network Access Control
- play_arrow Device Discovery
- play_arrow Domain Name Security
- play_arrow Permission Flags
- access
- access-control
- admin
- admin-control
- all
- clear
- configure
- control
- field
- firewall
- firewall-control
- floppy
- flow-tap
- flow-tap-control
- flow-tap-operation
- idp-profiler-operation
- interface
- interface-control
- maintenance
- network
- pgcp-session-mirroring
- pgcp-session-mirroring-control
- reset
- rollback
- routing
- routing-control
- secret
- secret-control
- security
- security-control
- shell
- snmp
- snmp-control
- system
- system-control
- trace
- trace-control
- view
- view-configuration
- play_arrow Configuration Statements and Operational Commands
Configuring LLDP-MED on MX Series Routers in Enhanced LAN Mode
Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) is an extension of LLDP. Starting with Junos OS Release 14.2, the router uses LLDP-MED to support device discovery of VoIP telephones and to create location databases for these telephone locations.
LLDP-MED is turned on by default on MX Series routers.
This topic describes:
Enabling LLDP-MED on Interfaces
LLDP-MED is enabled on all interfaces by default. If it is disabled, you can enable LLDP-MED by configuring it on all interfaces or on specific interfaces.
To configure LLDP-MED on all interfaces or on a specific interface:
[edit protocols lldp-med] user@router# set interface (LLDP-MED) ge-0/0/2.0
Configuring Location Information Advertised by the Router
You can configure the location information that is advertised from the router to the LLDP-MED device. You can specify a civic-based location (geographic location) or a location based on an ELIN (Emergency Location Identification Number):
To specify a location by geography:
content_copy zoom_out_map[edit protocols lldp-med] user@router# set interface ge-0/0/2.0 location civic-based country-code US user@router# set interface ge-0/0/2.0 location civic-based ca-type 1 ca-value “El Dorado County” user@router# set interface ge-0/0/2.0 location civic-based ca-type 2 ca-value CA user@router# set interface ge-0/0/2.0 location civic-based ca-type 3 ca-value Somerset user@router# set interface ge-0/0/2.0 location civic-based ca-type 6 ca-value “Mount Aukum Road” user@router# set interface ge-0/0/2.0 location civic-based ca-type 19 ca-value 6450 user@router# set interface ge-0/0/2.0 location civic-based ca-type 21 ca-value “Holiday Market”
To specify a location using an elin string:
content_copy zoom_out_map[edit protocols lldp-med] user@router# set interface ge-0/0/2.0 location elin 4085551212
Configuring for Fast Start
You can specify the number of LLDP-MED advertisements sent from the router in the first second after it has detected an LLDP-MED device. The default is 3; to set it to another value:
[edit protocols lldp-med] user@router# set fast-start 6
If an interface is configured as a VoIP interface, then the router does not wait for an attached phone to identify itself as an LLDP-MED device before it performs an LLDP-MED fast start after a graceful Routing Engine switchover (GRES) or a reboot. Instead, it immediately performs an LLDP-MED fast start after a GRES or reboot. This behavior prevents certain models of IP phones from resetting after a GRES.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.
