Ability to search for cable labels

[themmini]

Ability to search for labels on ports for patch panels - patch ports are labeled in a datacentre with a serial number. Ability to search DCIM for that label when performing operations + audits/reconciliation.

Not sure if someone has an alternative method.

[candlerb]

Cables, interfaces and frontports can all have "labels" set on them. Global search doesn't work across these, but it works if you search directly on them (e.g. go to Devices > Front Ports, Filter)

Are you therefore saying that you want these to be available in global search? It seems reasonable to me, but similar requests have been rejected before: see #6798, #4757. Open issues which may be relevant: #7016, #6003.

As a workaround, maybe you could write a Custom Script which prompts you for a keyword, and then searches labels across cables, interfaces, frontports and rearports.

[themmini]

Global search would be handy - for example labeling all the ports across your organisation then searching for that label to find the two ports that are connected. I guess you can search across all patch panels.

…

________________________________ From: Brian Candler ***@***.***> Sent: Tuesday, December 14, 2021 8:37:17 PM To: netbox-community/netbox ***@***.***> Cc: Mini Man ***@***.***>; Author ***@***.***> Subject: Re: [netbox-community/netbox] Ability to search for cable labels (Discussion #8059) Cables, interfaces and frontports can all have "labels" set on them. Global search doesn't work across these, but it works if you search directly on them (e.g. go to Devices > Front Ports, Filter) Are you therefore saying that you want these to be available in global search? It seems reasonable to me, but similar requests have been rejected before: see #6798<#6798>, #4757<#4757>. Open issues which may be relevant: #7016<#7016>, #6003<#6003>. As a workaround, maybe you could write a Custom Script which prompts you for a keyword, and then searches labels across cables, interfaces, frontports and rearports. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#8059 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACYAS6MI7242LFMA65ZMEA3UQ4F43ANCNFSM5J7WRC6Q>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[empusas]

I find it confusing to even show the cable ID. The ID is a consecutive number assigned when the object is created that has very limited practical use for the user. If you delete and recreate the same cable, it gets a new ID assigned and you got zero influence on the ID.
Using the label instead would be a much better option as this is usually assigned by the cabling team that physically marks the cable exactly with that.

[candlerb]

That's exactly what happens today. The cable ID is only shown for cables with no label. If you set the label, that is shown instead.