Today's agenda seemed overwhelming on paper, but for John and I, all went well. No technical issues today, just fingers that didn't seem to hit the right keys on the keyboard. Yes, our Layer 2 switch had held the address for our VLAN 1. Whew, initial success. John and I have also worked out the idiosyncracies of CoolTerm. Buttons must be chosen in a particular order or it can become a bit oppositional and show us a bit of attitude. We hit an all time record for logging on to the Webview interface.
Using Cool Term, our next step was to add our next hop, the Layer 3 switch, or VLAN 2. We practiced this code several times as our typing changed vlan to van and the address mask from 255.255.0.0 to 255.255.255.0. As I have said before, it is all in the details. This is never more true when doing technical work of this nature. Things must be checked and double-checked. Multi-tasking is not a good option when attempting setup of this nature. The technician should be 100% focused.
After we had set a static address on our workstation 1 (John's laptop) we verified that we had a connection to our switch. (We did learn a quick trick this morning. John's laptop does not like to accept a new static address and we have been setting the address and restarting to get it to accept the new address. Aah, the joys of Vista. Today we learned that we can set the address, disconnect the patch cable for ten seconds and reconnect and, yes, it will pick up the new address. This is much more efficient than restarting!)
To establish our new Vlan, we simply needed to enter the command VLAN 2.
The second step of this procedure is then to give this new VLAN an address. The command to accomplish this is ip interface vlan -2 address 10.0.10.254 mask 255.255.255.0 vlan 2.
Our layer 2 switch, vlan 1, was connected to vlan 2 through Port 1 on Vlan 1.
Next, we needed to set the gateway point that undeliverable packets are to be sent to. The command for this was ip static-route 0.0.0.0 mask 0.0.0.0 gateway 192.168.10.254.
We also needed to tell our system how we were connected. vlan 2 port default 8/1
As always when making changes to the configuration on the Alcatel. Use the write memory command and the copy working certified. Those commands that had been so elusive on that first day are now second nature.
We double checked the Webview to ensure that both lans were being recognized and they were.
The preparation for Server 2008, or mini exercise 2B was an easy task. An inventory of your server hardware needed to be made in preparation for finding drivers and ensuring that we met minimum hardware specs for the software. Recording technical specs on any new piece of hardware is always good practice.
The Dell site did contain some useful information but the majority of our information came from a BIOS check and physical viewing. If the device manager and system tools of the Control Panel had not been disabled, this also would have been a good source of information. For our server, we are going to be using the DELL Optiplex 755. The technical specs of our particular PC can be found at this link.
We were next to research a minimum of three sites that would assist us in our installation.
The three most useful site we found were
1. http://en.wikipedia.org/wiki/Server_2008
This site had good technical specifications.
2. http://www.petri.co.il/how-to-install-windows-server-2008-step-by-step.htm
This site was an excellent visual resource. It was a step-by-step guide with many screen shots.
3. http://www.microsoft.com/download/en/details.aspx?id=17157
This site has further downloads for specific issues.
The actual install was a fairly easy procedure. The setup wizard was very user-friendly and naturally sequential. Tomorrow we are looking forward to finding drivers! Should be fun since the Optiplex isn't normally associated with server functions. Stay tuned for a comprehensive technical guide. Promises to be a real page turner.
Using Cool Term, our next step was to add our next hop, the Layer 3 switch, or VLAN 2. We practiced this code several times as our typing changed vlan to van and the address mask from 255.255.0.0 to 255.255.255.0. As I have said before, it is all in the details. This is never more true when doing technical work of this nature. Things must be checked and double-checked. Multi-tasking is not a good option when attempting setup of this nature. The technician should be 100% focused.
After we had set a static address on our workstation 1 (John's laptop) we verified that we had a connection to our switch. (We did learn a quick trick this morning. John's laptop does not like to accept a new static address and we have been setting the address and restarting to get it to accept the new address. Aah, the joys of Vista. Today we learned that we can set the address, disconnect the patch cable for ten seconds and reconnect and, yes, it will pick up the new address. This is much more efficient than restarting!)
To establish our new Vlan, we simply needed to enter the command VLAN 2.
The second step of this procedure is then to give this new VLAN an address. The command to accomplish this is ip interface vlan -2 address 10.0.10.254 mask 255.255.255.0 vlan 2.
Our layer 2 switch, vlan 1, was connected to vlan 2 through Port 1 on Vlan 1.
Next, we needed to set the gateway point that undeliverable packets are to be sent to. The command for this was ip static-route 0.0.0.0 mask 0.0.0.0 gateway 192.168.10.254.
We also needed to tell our system how we were connected. vlan 2 port default 8/1
As always when making changes to the configuration on the Alcatel. Use the write memory command and the copy working certified. Those commands that had been so elusive on that first day are now second nature.
We double checked the Webview to ensure that both lans were being recognized and they were.
The preparation for Server 2008, or mini exercise 2B was an easy task. An inventory of your server hardware needed to be made in preparation for finding drivers and ensuring that we met minimum hardware specs for the software. Recording technical specs on any new piece of hardware is always good practice.
The Dell site did contain some useful information but the majority of our information came from a BIOS check and physical viewing. If the device manager and system tools of the Control Panel had not been disabled, this also would have been a good source of information. For our server, we are going to be using the DELL Optiplex 755. The technical specs of our particular PC can be found at this link.
We were next to research a minimum of three sites that would assist us in our installation.
The three most useful site we found were
1. http://en.wikipedia.org/wiki/Server_2008
This site had good technical specifications.
2. http://www.petri.co.il/how-to-install-windows-server-2008-step-by-step.htm
This site was an excellent visual resource. It was a step-by-step guide with many screen shots.
3. http://www.microsoft.com/download/en/details.aspx?id=17157
This site has further downloads for specific issues.
The actual install was a fairly easy procedure. The setup wizard was very user-friendly and naturally sequential. Tomorrow we are looking forward to finding drivers! Should be fun since the Optiplex isn't normally associated with server functions. Stay tuned for a comprehensive technical guide. Promises to be a real page turner.
Posts
No comments:
Post a Comment