Network Device Vendor Management in rConfig V8

Vendor management in rConfig V8 provides a structured approach to organizing and identifying network device manufacturers across your infrastructure. Understanding which vendors produce your network equipment is fundamental to effective device management, as it enables targeted configuration strategies, standardized backup procedures, and vendor-specific automation workflows.

The vendor collection serves as a foundational data layer that connects to devices, connection templates, and reporting mechanisms throughout rConfig. By maintaining accurate vendor information, organizations can segment their network infrastructure logically, apply vendor-specific configurations, and generate meaningful reports based on manufacturer distribution.

rConfig V8 ships with a comprehensive list of common network equipment vendors pre-configured, providing immediate usability while allowing full customization to match your specific environment.

When to Use Vendors

Use the Vendors list whenever you need to tag devices by manufacturer for filtering, reporting, or vendor-specific automation, or when onboarding a manufacturer that isn’t already in the pre-configured list. If you’re looking to group devices by role or platform instead (routers, switches, IOS vs. JunOS), use Command Groups or Tags alongside vendor data rather than in place of it.

Prerequisites

Before adding, editing, or deleting a vendor, confirm you have:

• Permission to manage Vendors in your rConfig role
• The exact vendor name you want to standardize on, checked against the existing list to avoid near-duplicate entries

No other prerequisites are required. Vendors have no dependency on other inventory objects.

Understanding Vendor Collections

Purpose and Architecture

Vendor labels function as categorical identifiers that tag devices according to their manufacturer. This categorization creates several operational advantages:

Device Organization: Vendors provide a natural grouping mechanism for devices in your inventory. When managing hundreds or thousands of network devices, the ability to filter and view devices by manufacturer streamlines daily operations and simplifies infrastructure visualization.

Configuration Standardization: Different vendors often require specific connection protocols, command syntaxes, and configuration approaches. By associating devices with vendors, you can apply manufacturer-specific connection settings and connection templates.

Reporting and Analytics: Vendor-based reporting allows network teams to analyze infrastructure composition, identify vendor concentration risks, assess licensing requirements, and plan hardware refresh cycles based on manufacturer distribution.

Automation Workflows: Automated backup schedules, compliance checks, and configuration deployment scripts can leverage vendor information to apply appropriate methods and syntax for each manufacturer’s equipment.

Data Model Integration

The vendor collection integrates with multiple components within rConfig V8:

• Device Records: Each device in rConfig can associate with a vendor, creating a link between inventory and manufacturer
• Command Groups: Vendors and Command Groups are independent classification dimensions; use them together for a two-dimensional view (manufacturer and role/platform) of your inventory
• Connection Templates: Vendor-specific connection parameters can be pre-configured and applied during device onboarding
• Reporting Engine: The reporting system uses vendor data as a key dimension for generating infrastructure analysis and compliance reports

Managing Vendors

Viewing the Vendor Collection

Navigate to Inventory → Vendors to access the complete list of configured vendors. The vendor listing displays every manufacturer currently defined in your rConfig instance.

The vendor table provides key information including:

• ID: Internal record identifier, sortable
• Vendor Name: The manufacturer name or designation, sortable
• Devices: A badge list of every device currently associated with this vendor, each linking directly to that device
• Actions: Edit and delete controls for the vendor record

Adding New Vendors

Tip

Before adding a new vendor, verify it doesn’t already exist under a similar name or abbreviation. Duplicate vendor entries can fragment your device inventory and complicate reporting.

To create a new vendor entry:

1. Click the Add Vendor button in the vendors listing interface
2. Enter the vendor name in the Vendor Name field
3. Click Save to create the vendor record

Naming Best Practices:

• Use the official manufacturer name consistently (e.g., “Cisco Systems” not “Cisco Inc.” or “CISCO”)
• Avoid abbreviations unless they are the vendor’s official designation (e.g., “HP” is acceptable, but spell out lesser-known vendors)
• If a vendor undergoes acquisition or rebranding, agree on a single name internally rather than creating a second entry for the new name

The new vendor immediately becomes available for device assignment and appears in dropdown menus throughout the application.

Editing Vendor Information

Existing vendor records can be modified to correct spelling errors or standardize naming:

1. Locate the vendor in the vendors listing
2. Click the Edit action button for the desired vendor
3. Modify the vendor name
4. Click Save to apply changes

Caution

Editing a vendor name affects every device currently associated with that vendor, since they all reference the same vendor record. The change is immediate. Confirm the rename is intentional before saving.

Deleting Vendors

1. Navigate to the vendor you wish to remove
2. Click the Delete action button
3. Confirm the deletion in the warning dialog

Caution

Deleting a vendor does not delete the devices associated with it, but it does remove their vendor association immediately and cannot be undone. Reassign affected devices to the correct vendor first if you want to preserve that classification, since there is no confirmation step that blocks deletion when devices are still linked.

Video Tutorial

Vendor-Device Relationships

Assigning Vendors to Devices

When creating or editing device records, you associate each device with its corresponding vendor:

1. In the device creation or edit form, locate the Vendor dropdown field
2. Select the appropriate manufacturer from the list
3. Save the device record to establish the vendor association

The vendor assignment influences several device behaviors:

• Default Connection Settings: If vendor-specific connection templates exist, they can be applied during onboarding
• Configuration Syntax: Some advanced features use vendor information to format commands appropriately
• Reporting and Filtering: Vendor-based filtering and reporting can automatically include devices as they are added

Viewing Vendor-Associated Devices

To see all devices associated with a particular vendor:

1. Navigate to the Devices section
2. Apply the vendor filter in the device listing
3. Select the desired vendor from the filter dropdown

The device list updates to show only devices from that manufacturer, enabling vendor-focused operations and analysis. You can also see the same list directly from the Vendors page, in the Devices column for that vendor’s row.

Use Cases and Practical Applications

Multi-Vendor Environment Management

Organizations operating multi-vendor networks benefit significantly from structured vendor management:

Scenario: A large enterprise operates Cisco routers at branch locations, Juniper switches in data centers, and Palo Alto firewalls at network perimeters.

Implementation: Create separate vendor records for each manufacturer. Associate devices correctly during onboarding. Use vendor filters during troubleshooting to isolate issues to specific equipment types. Generate vendor-specific reports to track configuration compliance across different platforms.

Vendor Standardization Initiatives

Network teams planning infrastructure standardization can leverage vendor data for transition planning:

Scenario: An organization decides to standardize on a single switching vendor to reduce operational complexity and training requirements.

Implementation: Use vendor filtering to identify non-standard equipment. Track migration progress by monitoring the device list per vendor over time. Use vendor associations to prioritize configuration backups for equipment scheduled for replacement.

License and Support Management

Vendor information supports contract and licensing workflows:

Scenario: Maintenance contracts and support agreements are vendor-specific and require accurate device inventories per manufacturer.

Implementation: Use the vendor filter to generate accurate device inventories for license audits. Export vendor-segmented device lists for procurement and contract renewal processes.

Compliance and Audit Requirements

Regulatory compliance often requires detailed inventory documentation including manufacturer information:

Scenario: Security frameworks mandate maintaining accurate inventories including device manufacturers, models, and versions.

Implementation: Vendor fields provide required manufacturer data for compliance reports. Automated backups ensure device configurations are regularly captured. Vendor-based filtering enables auditors to quickly locate specific equipment types for review.

Best Practices

Vendor Naming Conventions

Establish and document consistent naming standards for your organization:

• Use official legal names as they appear on the manufacturer’s website
• Maintain consistent capitalization and spacing
• Document common abbreviations in organizational procedures
• Create an internal reference guide mapping informal names to official vendor records

Regular Vendor Audits

Periodically review your vendor list to maintain data quality:

• Identify and merge duplicate vendor entries (reassign devices, then delete the duplicate)
• Delete vendors no longer represented in your infrastructure once no devices reference them
• Update vendor names to reflect corporate rebrands or acquisitions
• Verify vendor-device associations remain accurate after infrastructure changes

Integration with Asset Management

Coordinate vendor data between rConfig and other asset management systems:

• Ensure vendor names match across all systems to enable data correlation
• Use consistent vendor identifiers if integrating via the API
• Document any name mapping required between systems
• Establish a single source of truth for vendor information

Documentation and Training

Ensure team members understand vendor management practices:

• Document organizational standards for vendor naming and management
• Include vendor selection in device onboarding training
• Explain the impact of vendor data on reporting and automation
• Provide examples of correct vendor assignments for common equipment

Troubleshooting

Duplicate Vendor Entries

Symptom: Multiple similar vendor names exist in the system (e.g., “Cisco”, “Cisco Systems”, “Cisco Inc.”)

Cause: Inconsistent data entry during device onboarding or migration from previous systems

Resolution:

1. Identify all variant names for the same vendor
2. Determine which name should be the standard
3. Reassign all devices from variant vendors to the standard vendor
4. Delete the duplicate vendor entries
5. Update documentation to prevent future duplicates

Missing Vendor in Device Assignment

Symptom: Required vendor doesn’t appear in the vendor dropdown when creating devices

Cause: The vendor hasn’t been created yet, or the device form hasn’t refreshed its vendor list

Resolution:

1. Verify the vendor exists in the vendors collection
2. If it doesn’t exist, create it following the adding vendors procedure
3. Refresh the device form and verify the vendor now appears
4. If issues persist, clear browser cache and retry

Devices Show No Vendor After a Vendor Is Deleted

Symptom: A device that previously had a vendor assigned now shows no vendor

Cause: The vendor record was deleted. Deleting a vendor removes the association from every device that referenced it; it does not delete the devices themselves, and rConfig does not block the deletion just because devices are still linked

Resolution:

1. Re-open each affected device and assign the correct vendor
2. Going forward, reassign devices to a different vendor before deleting the old one, to avoid this cleanup step

Performance Considerations

Large Vendor Collections

Organizations with extensive vendor lists (50+ vendors) should consider these optimization strategies:

Search and Filtering: Use the search functionality in vendor dropdowns rather than scrolling through long lists.

Regular Cleanup: Schedule periodic reviews to consolidate vendors and remove unused entries. A lean vendor list improves data entry speed and reduces user confusion.

Integration Points

API Access

Vendor data is accessible via the rConfig V8 API, enabling integration with external systems. Requests are authenticated with an apitoken header rather than a Bearer token.

Retrieving Vendors:

curl -X GET "https://your-rconfig-instance/api/v1/vendors" \
  -H "apitoken: YOUR_API_TOKEN"

Creating Vendors:

curl -X POST "https://your-rconfig-instance/api/v1/vendors" \
  -H "apitoken: YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"vendorName":"Arista Networks"}'

The vendor record accepts only a vendorName field. API integration enables synchronization with CMDB systems, automated vendor creation during device discovery, and integration with procurement workflows. See the REST API reference for full authentication details.

Reporting Integration

Vendor data serves as a key dimension in the rConfig reporting engine:

• Generate vendor distribution reports showing infrastructure composition
• Create vendor-specific compliance reports for audit purposes
• Export vendor-segmented device lists for procurement and planning

Related Documentation

• Devices - Device management and vendor associations
• Command Groups - Device categorization alongside vendor classification
• Reports - Generating vendor-based reports and analytics
• REST API - Programmatic vendor management

Quick Reference

Common Tasks

Task	Navigation	Action
Add Vendor	Inventory → Vendors → Add Vendor	Enter name and save
Edit Vendor	Inventory → Vendors → Edit (specific vendor)	Modify name and save
Delete Vendor	Inventory → Vendors → Delete (specific vendor)	Confirm deletion
View Associated Devices	Inventory → Vendors (Devices column), or Devices → Filter by Vendor	Select vendor from filter

Vendor Management Workflow

1. Initial Setup: Review pre-configured vendors and add any missing manufacturers
2. Device Onboarding: Select appropriate vendor during device creation
3. Regular Maintenance: Audit vendor list quarterly to maintain data quality
4. Reporting: Leverage vendor data for infrastructure analysis and planning
5. Integration: Connect vendor data with external asset management systems via the API

Summary

Vendor management in rConfig V8 provides essential organizational structure for network device inventory. By maintaining accurate vendor information, organizations enable targeted device management, standardized configurations, meaningful reporting, and effective automation workflows.

Key takeaways:

• Vendors serve as fundamental categorization for network devices based on manufacturer
• Pre-configured vendor list provides immediate functionality with full customization options
• Vendor associations influence device connections, configurations, and reporting
• Regular vendor audits maintain data quality and prevent duplicate entries
• Deleting a vendor is immediate and unconditional; it removes the association from any linked devices but does not delete those devices
• Following naming conventions and best practices ensures long-term data consistency

Effective vendor management establishes a solid foundation for scalable network configuration management, enabling teams to organize, analyze, and operate multi-vendor infrastructure efficiently.