Badge Configuration Workstation

So lets just pretend we have a Vocera implementation coming up, we know we are getting a bunch of badges and we have our servers ready for installation. One piece that gets missed from time to time is the Badge Configuration Workstation, or BCWS. Here is why we need one and how to set one up.

When new badges arrive from Vocera, or an old badge is reset to factory defaults, it will boot up with the following information:

• The only SSID the badge will look for is "vocera"
• The badge will TAKE an IP of 10.X.X.X with or without DHCP present
  
• It will look for a Vocera Server at 10.0.0.1
• It will load firmware from that IP if offered and a copy of badge.properties
  

If our production SSID is "supersecrethiddenssid" and our VS is on an IP of 192.168.1.1 it's safe to say a factory badge will never find it.

Vocera's answer to this situation is a BCWS. The idea is this:

• Configure a thick AP with SSID = vocera
• Connect that AP via Ethernet crossover to a PC with an IP of 10.0.0.1
  
• On that PC run the badge configuration portion of VS
• Load the production data values into the Badge Properties Editor

Simple enough. In the real world I see three approaches frequently:

1. Old PC and a thick AP setup for the task
2. Admin's laptop and mini AP configured when needed
3. Overkill over-engineering

The most common approach is to grab an old desktop PC from a junk pile and a thick AP that was pulled out during LWAPP conversion, cut a crossover cable and load it up. If we go this route I suggest the following:

1. Install a fresh copy of XP Professional SP2 on the PC
2. Set the NIC to 10.0.0.1 with a subnet mask of 255.0.0.0
3. You can leave the default gateway blank
4. Disable Windows Firewall
5. Connect a Ethernet crossover cable between the workstation and the AP
6. Setup AP with ssid "vocera" completely open
7. Insert the Vocera Server media and run the installer with only Badge Utilities selected (unselect Vocera Server) and take all defaults
8. I recommend turning the antenna power down to the lowest level possible
   

A few things on the PC itself. The official Vocera media is DVD, make sure the PC has a DVD-ROM. If it has CD-ROM or no optical drive you can load via USB, make sure it has USB ports and drivers if needed. I've seen lots of old PC's used for this, it's amazing to me how many times that neither of these requirements are met.

Once you have XP running on the PC you can connect it via the CROSSOVER CABLE (I like red for crossover cables) to the AP. If you need an AP and you like Cisco, you can get one of these ACCESS POINTS and put this configuration on it:

*** BEGIN CONFIG

enable
Cisco
conf t
int bvi1
ip add 10.0.0.2 255.0.0.0
exit
int dot11radio 0
ssid vocera
authenticaion open
no shut
exit
exit
wri mem
reload
yes
*** END CONFIG

In a minute or two you the AP will be online and ready for connections.

So for a half time review, we have a fresh install of XP on a PC and a crossover Ethernet cable connecting it to a AP serving the SSID of "vocera" and a pile of badges to flash.

Before we can actually flash them, lets create our badge.properties file. On the PC go to: Start->Programs->Vocera->Badge Utilities->Badge Properties Editor

You will see a DOS kicker then a GUI. You will need to choose your badge type, B1000 or B2000, and put in all production settings. Be very careful to make sure this accurately represents your production wireless and Vocera settings. When you are done save and exit the Badge Properties Editior.

Now: Start->Programs->Vocera->Badge Utilities->Badge Configuration Utility

You will see the command window open and load the settings, scroll up and check them (encryption keys will be encrypted.) If it looks good, slap the battery in the badge and watch it scroll by. If your VS settings are correct, the badge should settle on a display of "Logged Out" and connected to the active VS if you check the menu on the badge.

All of this assumed a dedicated PC and AP for the role of BCWS. Another option I mentioned was using the sys admin's laptop and mini AP. If you go this route do the following:

1. Set NIC to 10.0.0.1 with a subnet mask of 255.0.0.0
2. Disable any firewall running
3. Install Badge Utilities off the Vocera Server DVD
4. Connect to AP via crossover (if you need an AP look HERE)
5. Follow remain directions above

The only trick is remembering to set your IP before flashing badges.

I suggest you stick with option #1 for most environments, or sometimes option #2 is a little better for people who with many sites on a campus to support AND who go everywhere with laptop in hand.

The final option I mentioned is all the trickery that sharp people put into their own networks. This is outside of the scope of what I support for clients, and I may be mistaken but I don't think Vocera Support would be quick to jump into problems of this nature so I will skip it entirely for this post.

If you have comments or questions about the role of the BCWS please post them below!