So this is another of those documents that you will probably never have to use but..
I came across an issue on a 100.1 system where a newly installed ALE-30h just kept getting to 4/5 (updating) and rebooting, you could see the handset requesting the bin file but it never got a response from the system.
After chasing my tail for too long I noticed that the handset was looking for the bin8458P & noe8458P files from the OxE, now the files on the OxE are 84x9P so the PABX had no idea what it was looking for.
Checking on a 101.1 system I found that a symbolic link exits on that which directs requests for 8458P files to the 84x9P files.
To begin, when a TFTP request come through from a handset the request is looked for in /usr2/downbin, for the IP handsets the real files mostly in usr2/downbin/standard/ and as a lot of the sets share binaries to stop duplication there are symbolic links setup to allow a call for an individual file to be redirected to the ‘real’ file.
For instance, the 8028/8038/8068 share the same firmware so any request ends up at the bin80x8N or noe80x8N files.
To accomplish this a link is set to direct the request for the bin8028N file from /usr2/downbin/ to /usr2/downbin/standard/
Then a second link is put in /usr2/downbin/standard to point that request to the actual file so that a request for bin8028/8038/8068 ends up with bin80x8N
Eyes glazing over yet, well they will soon 😊
Now if you ever want /need to mess with this then here is how, using my issue as the example:
As I said the new handset was asking for the 8458P files which the system knew nothing about so I had to create the links in the system, here are the steps:
- Go to /usr2/downbin
- Elevate to root
- Enter ln -s ‘link destination’ ‘link name’ so (the -s specifies symbolic rather than a hard link)
ln -s standard /bin8458P bin8458P
ln -s standard/noe8458P noe8458P - Then change the ownership of the links to match the rest
chown -h root:sys bin8458P
chown -h root:sys noe8458P - Now descend to /standard
- ln -s bin84x9P bin8458P
ln -s noe84x9P noe84x9P - Repeat step 4
- If you do an ls -al it should show if you have stuffed it up like below
Here I had done /standard/noe8458P in the initial setup as well as not having yet created the file in standard/
So for me it was flashing red to say that the link was broken.
Other options
To remove use either
rm ‘link-name’
or
unlink ‘link-name’
To edit
ln -sf ‘new destination’ link-name (the -sf allows you to change the destination of the link)
That’s it!
