- play_arrow Working With Network Director
- play_arrow About Network Director
- play_arrow Installing Network Director
- play_arrow Accessing Network Director
- play_arrow Understanding Network Director System Administration and Preferences
- play_arrow Getting Started with Network Director
-
- play_arrow Working with the Dashboard
- play_arrow About the Dashboard
- play_arrow Using the Dashboard
- play_arrow Dashboard Widget Reference
-
- play_arrow Working in Deploy Mode
- play_arrow About Deploy Mode
- play_arrow Deploying and Managing Device Configurations
- Deploying Configuration to Devices
- Managing Configuration Deployment Jobs
- Deploy Configuration Window
- Importing Configuration Data from Junos OS Configuration Groups
- Enabling High-Frequency Traffic Statistics Monitoring on Devices
- Configuring Network Traffic Analysis
- Approving Change Requests
- Enabling SNMP Categories and Setting Trap Destinations
- Understanding Resynchronization of Device Configuration
- Resynchronizing Device Configuration
- Managing Device Configuration Files
- Creating and Managing Baseline of Device Configuration Files
- play_arrow Deploying and Managing Software Images
- play_arrow Managing Devices
- play_arrow Setting Up Zero Touch Provisioning for Devices
-
- play_arrow Monitoring Devices and Traffic
- play_arrow About Monitor Mode
- play_arrow Monitoring Traffic
- play_arrow Monitoring Client Sessions
- play_arrow Monitoring Devices
- play_arrow Monitoring and Analyzing Fabrics
- play_arrow Monitoring Virtual Networks
- play_arrow General Monitoring
- play_arrow Monitor Reference
- 802.11 Packet Errors Monitor
- Access vs. Uplink Port Utilization Trend Monitor
- Current Sessions Monitor
- Current Sessions by Type Monitor
- Error Trend Monitor
- Equipment Summary By Type Monitor
- Node Device Summary Monitor
- Port Status Monitor
- Port Status for IP Fabric Monitor
- Port Utilization Monitor
- Power Supply and Fan Status Monitor
- Resource Utilization Monitor for Switches, Routers, and Virtual Chassis
- Top Users Monitor
- Top Sessions by MAC Address Monitor
- Session Trends Monitor
- Status Monitor for Junos Fusion Systems
- Status Monitor for Layer 3 Fabrics
- Status Monitor for Switches and Routers
- Status Monitor for Virtual Chassis
- Status Monitor for Virtual Chassis Members
- Top Talker - Wired Devices Monitor
- Traffic Trend Monitor
- Unicast vs Broadcast/Multicast Monitor
- Unicast vs Broadcast/Multicast Trend Monitor
- User Session Details Window
- Virtual Chassis Topology Monitor
- VC Equipment Summary By Type Monitor
-
- play_arrow Using Fault Mode
- play_arrow About Fault Mode
- play_arrow Using Fault Mode
- play_arrow Fault Reference
-
- play_arrow Working in Report Mode
- play_arrow About Report Mode
- play_arrow Creating and Managing Reports
- play_arrow Report Reference
-
- play_arrow Working with Network Director Mobile
- play_arrow About Network Director Mobile
- play_arrow Getting Started with Network Director Mobile
- play_arrow Working in the Network Director Mobile Dashboard Mode
- play_arrow Working in the Network Director Mobile Devices Mode
-
Adding and Managing OUI Data in Network Director
Network Director uses Link Layer Discovery Protocol (LLDP) to detect the type of network device (such as desktop computer, VoIP phone, or network servers) in a campus network. However, network printers are an exception as most printers do not use LLDP. As a result, Network Director might not be able to identify the device as a printer. This is where the organizationally unique identifier (OUI) of printers come into play. OUI is formed using the first three octets of the device MAC address. OUI is unique to a vendor or manufacturer and can be identified globally.
You can build a database of OUIs that Network Director can use to identify the device type. During the topology discovery, if the LLDP-based discovery does not identify the device type, Network Director looks up in the OUI database to see whether there is a match. If Network Director finds a matching entry, the device is notated as a printer in the network topology. If there is no match, the device is marked as an unknown device.
To add and manage OUI data: