{# SPDX-License-Identifier: Apache-2.0 #} {# Copyright (C) 2025 Marcin Zieba #} {% extends 'base/layout.html' %} {% block title %}Attach Route-Policy — {{ object }}{% endblock %} {% block content %}
{% if preflight %} {# Block-with-override: this device's (NED, software) is known not to support some #} {# parts of the selected object. Show exactly what won't apply before letting the #} {# operator attach anyway. #}
Some parts won't apply on {{ object }}

Attaching {{ selected_label }} to {{ object }} {% if preflight.sw_version %}(software {{ preflight.sw_version }}){% endif %}. Based on this device's capability check, the following would be silently dropped when written to the device:

{% for u in preflight.unsupported %} {% endfor %}
ScopeElementVerdictDetail
{{ u.scope }} {{ u.element }} {% if u.status == "unsupported" %} {{ u.status }} {% else %} {{ u.status }} {% endif %} {{ u.detail|default:"—" }}

The rest of the object still applies. Attach anyway to write the supported parts now; the unsupported parts above won't reach the device.

{% csrf_token %} Cancel
{% else %}
Attach Route-Policy to {{ object }}

Attach an existing route-policy object (prefix-list / route-map / community-list / as-path) to {{ object }}. The device↔object link is the overlay, so one object can be attached to several devices. It is written to the device on the next Apply. Create new objects under Netbox Routing → Routing Objects first. Route-maps and community-lists are checked against this device's capabilities before attaching.

{% if candidates %}
{% csrf_token %}
Cancel
{% else %}

No unattached route-policy objects available. Create one first under Netbox Routing → Routing Objects.

{% endif %}
{% endif %}
{% endblock %}