Will be setting up multiple 5550 IP consoles. I understand the amount of programming time to configure remote blf's across a multiple-node cluster, etc. Question: If the shared blf lists created for the 1st console reside on a network drive, is the installation time reduced for additional consoles? Also, can the console operators 'toggle' between use of the shared versus private blf lists? Thanks -
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
5550 Install complexity
- Thread starter jazwinner
- Start date
I'm not sure what you mean by BLF list residing on a Network Drive. The only way I know of to create BLF appearances for a console is to create BLF appearances on a Phone set's keys on the same system as the monitored sets system. The keys can be programmed on Phantom sets or phantom PKM's but the maximum per set is 120 lamps (5224 set with dual PKM). To get the lamps to display properly on a remote system involves programming the remote BLF form to designate the phone on the remote system that has the appearances.
When I attempted to do this with a simple system (2 Controllers totaling 250 users) it took nearly 4 hours to get it all programmed and that was utilizing the import /export features of release 7.
As systems are added the workload increases dramatically in much the same way as the clustering programming increases with size.
If you had 10 systems for example you would need to create the BLF on 10 different systems and 9 different entries in the remote blf list.
Too much work in my mind.
Once it is all done it then has to be maintained. I have submitted DCR's to Mitel regarding this with no results
*******************************************************
Consistancy... Is only a virtue when you're not a total screwup.
When I attempted to do this with a simple system (2 Controllers totaling 250 users) it took nearly 4 hours to get it all programmed and that was utilizing the import /export features of release 7.
As systems are added the workload increases dramatically in much the same way as the clustering programming increases with size.
If you had 10 systems for example you would need to create the BLF on 10 different systems and 9 different entries in the remote blf list.
Too much work in my mind.
Once it is all done it then has to be maintained. I have submitted DCR's to Mitel regarding this with no results
*******************************************************
Consistancy... Is only a virtue when you're not a total screwup.
- Thread starter
- #3
From the 3300 SysAdmin Tool help:
By default, the Console BLF Configuration file (blfList.cfg) is installed on the hard drive of the console PC. During the installation wizard, you can click Browse and install the blfList.cfg file on a network server if you want the consoles to share the same Busy Lamp Field appearances.
I understand the time involved in setting up multiple blfs on multiple systems. Are any of these steps consolidated by using EM/OPS Mgr?
By default, the Console BLF Configuration file (blfList.cfg) is installed on the hard drive of the console PC. During the installation wizard, you can click Browse and install the blfList.cfg file on a network server if you want the consoles to share the same Busy Lamp Field appearances.
I understand the time involved in setting up multiple blfs on multiple systems. Are any of these steps consolidated by using EM/OPS Mgr?
OK I get you now, The Config file will only contain the lamps that the console detects.
Saving the file to a network drive will only be useful for consoles that reside on the same controller.
The BLF's will still need to be manually setup as I previously described. OPSMan or Eman does not help with this process.
The Import tool can be extremely helpful however.
It will still be extremely difficult to manage new phones and deletions to keep everything in check.
Again, way too much work for me.
*******************************************************
Consistancy... Is only a virtue when you're not a total screwup.
Saving the file to a network drive will only be useful for consoles that reside on the same controller.
The BLF's will still need to be manually setup as I previously described. OPSMan or Eman does not help with this process.
The Import tool can be extremely helpful however.
It will still be extremely difficult to manage new phones and deletions to keep everything in check.
Again, way too much work for me.
*******************************************************
Consistancy... Is only a virtue when you're not a total screwup.
- Status
Similar threads
- Locked
- Question
- Locked
- Question