How to create a test bed and what is the difference between Test Bed and Test Environment?

Question

I'm very new to freediameter. But I'm having some knowledge in freeradius. I believe that diameter is also similar like radius with some additional behaviors.

I have downloaded freediameter and installed properly. But I stuck after that. In radius we can have radtest option to test the basic authentication. But here I don't know how to test the basic authentications to authenticate the user.

When I surf on that, I have found like we need to include DiamEAP extensions also to verify the authentication
And came to know we need to configure mysql since it doesn't have flat file support like radius.

So I start to install mysql also. I have seen the testbed for EAP in TBEAP link. Again I confused with the setup. Is there any simple technique to test the AAA in freediameter. I'll explain my project needs below. Kindly help me how can I proceed with that.

• I need to implement the authenticate the port MAC (during state change) using freeDiameter protocol.
• I'll use SDN setup for that, using opendaylight controller. Once i get the port notification from the switch i'll send the username , password info to freediameter client. with that user name and password diameter client needs to send the Access-request packet to freediameter server. The server should validate those info's and return back with Access-Accept/Access-reject messages. Using that info i'll take decision to enable the swicth port or not.
  (I explained the terms in radius, sorry not sure with corresponding terms in freediameter).

For this what conf file I need to edit? What information it should have. How to test the client and server with users information. Please give some clear picture about the setup for my need.

My setup details.
diamEAP - 1.0.0
freediameter - 1.1.4
Ubuntu - 12.04

Answer 1

Test Environment: This includes the entire testing environment, for example, simulators, emulators, memory checkers, hardware probes, software tools, and all other items needed to support execution of the tests.

Test Bed: A test bed is an environment that contains all the hardware and software needed to test a software component or a software system.

Creating a test bed:
A test bed is a non-production area where you can test your changes. Upgrade the test bed before you upgrade your production databases.

If you plan to perform an in-place upgrade, that is specifying the same database as the source and target, you should test it first using the test bed. You can skip Step 2 in the following instructions with an in-place upgrade.

If you are performing a standard upgrade, not an in-place upgrade, the procedure for upgrading the test databases is almost identical to upgrading production databases.

To create a test bed based on your production databases:

1. Back up your Rational® ClearQuest® schema repository and user databases.
2. Create new, empty vendor databases for each schema repository and user database, as described in the topic "Vendor database configuration." Create the new databases in a new test directory or on a test server. These new databases are referred to as the test bed in the rest of this section.
   
   
   • Create empty databases only. Do not use the vendor database tools to move or copy the data. Rational ClearQuest updates the data structure and moves it into the new databases as part of the upgrade process.
   • Do not perform this step if you are performing an in-place upgrade or using Microsoft Access.
3. If you use Rational ClearQuest Web, shut down your Web server, stop any scheduled Rational ClearQuest MultiSite synchronization jobs, and disconnect all users from Rational ClearQuest by using one of these techniques:
   
   
   • Use the administrator's tool to log users off the database, if the database vendor provides such a tool.
   • For Windows systems, check the Task Manager Process List of each client and server computer. If any of the following processes is running, use the Task Manager to end it:
4. Copy your existing production schema repository and user databases to the test bed databases. Use the Rational ClearQuest installutil utility with the options convertschemarepo and convertuserdb. For more information, see the "Reference pages" in the Rational ClearQuest Online Help.
   The convert options with installutil cause Rational ClearQuest to lock the original production databases. If you need to unlock them, see the information about installutil unlockschemarepo and installutil unlockuserdb commands in the "Reference pages" topics of the Rational ClearQuest Online Help.
5. For each database in the test bed, create another new, empty vendor database. These databases, which are referred to as the test upgrade set in the rest of this section, are the databases that you upgrade to.