Hi Csickles,
I kan see what you mean - to some degree at least - only this is not my problem in this case.
In this specific case, we are building wired internet access to several hundred customers. All of those resceive fiberbased access to the net through a converter into a RB150 that distributes services to IP based telephony and data access.
On the ATA unit (we are using the Sipura/Linksys SPA2102) the WAN MAC address is printed on a barcode label on the unit itself. This allows for scanning the units “ID” (MAC address) barcode into our selfmade deployment application that configures the ATA with all needed information and stores this information in the central Access database.
On the Routerboard however, the only information printet by barcode is the “serialnumber” or whatever. The information does not contain any MAC address of the Board.
This means that when deploying the RB150 unit, we have to use eg. netinstall or in another way obtain the unit’s MAC address and enter this information “by hand” thus enabeling lots and lots of typo errors in this process.
IF the information about the router on the barcode was a MAC address - OR there is a “Serialnumber → MAC addresses assigned” database available, these typos could be omitted by simply scanning the unit’s barcode before Netinstalling it (or API v3 or…)
Without the barcode, we have to rely on attaching a serial cable to each and every board, setting the netboot option in bios, getting the MAC through the Netinstall (or whatever) and first then make the “dedicated” settings for exactly that user by typing the MAC address.
IF the barcode where to display the MAC address, we could simply:
- Scan the MAC address to “some application”
- Use this information to obtain the correct setup for excactly this routerboard.
- Based on the MAC address, register all needed information regarding this router.
A table or database containing the MAC address(es) assigned the Serialnumber on the barcode could do the same trick.
This is NOT a question of lazyness but a “quality of large scale deployment” issue because a barcode would identify the Routerboard uniquely without potential “typos”.
I can see that the “serialnumber” does that too but in our world of TFTP, MAC and IP the MAC address is the only unique number that may logically be used for this issue.
Any advice?
/Niels