Menu

#87 FR: pradmin should validate new loccode names

not_assigned
open
nobody
2013-06-04
2004-12-22
No

I am not sure whether name validation is done by
pradmin when
creating new loccodes.

I ran into an instance where pradmin allowed using a
underscore when creating a new loccode name and this
caused problems for the script am-update when it tried
to update AM .

Need to ensure that underscore character is not
allowed when naming loccodes.

This is because the am placeholders for unused
ipaddress in BOOTP pool uses the > loccode as part of
the name and AM doesn't allow it. So the script (
am-update ) that updates AM fails when updating these
entries..

Here is an example
(turambar:/var/spool/ceps/logs/am-reconcile/update.log ) :-
>
> # Add printer-menlo_brennan-172-30-157-81 at
172.30.157.81
> # Networks: 172.30.157.64/26
> # -f=int-add -name=printer-menlo_brennan-172-30-157-81
> -ipaddress=172.30.157.81
> ERROR: The Interface Name field should only contain
alphanumerics and
> hyphens
>
>

Discussion

  • Adam Crews

    Adam Crews - 2005-01-07
    • summary: pradmin should validate new loccode names --> FR: pradmin should validate new loccode names
     
  • Kiran Yagnavajhala

    Ticket moved from /p/ceps/feature-requests/89/

    Can't be converted:

    • _milestone: not_assigned
    • _priority: 5
     

Log in to post a comment.