ed 5769- summer day 2

Day 2 July 5, 2011
The first task was to review our setting on our Alcatel switch. We did have to reset the Cooltime software as we were having troubles with the serial to USB connecting to the correct COM port. Once we got thing running and setup our UN and PW we had to run some CLI commands such as 1) aaa authentication default local 2)write memory 3)copy working certified
These commands were run and our switch did hold the Ip address 192.168.10.254. This process allowed us to connect to the Alcatel Layer 3 switch to simulate WAN environment. Once this process was done we were able to open up a browser using the Ip address 192.168.10.254. This opened up a graphic user face to connect to the Alcatel layer 2 switch with the Un admin Pw switches. The right Ip address was identified on this gui for our switch.
The second task was to have 2 computers attached to the network via static Ip setup. This was not an issue as both Sandie and I have had lots of experience with static Ip addressing using Windows Xp, and now Vista and 7.
These Ip’s are 192.168.10.100 and 105. The common subnet mask was 25.255.255.0. The gateway was 192.168.10.254, which directed to the Alcatel switch which we had setup on Monday. The DNS server was 142.66.33.100/101.
We did do the project on 2 computers pinging addresses as was identified in our assignment. We disconnected our port 1 connection of the Alcatel switch, making a local connection between the 2 computers through the switch.
Our results are as follows. We will be discussing the outcome of our results on Wednesday.
There were a few connection parameters that were unexpected Screen shots are becoming my best friend !!!

These were the observations of our 8 ip ping experiments
1. private address no connection
2. different networks on same subnet but only routing through layer 2 switch
3. class C private and on different networks
4. private address
6. Class B private,
7. same network, same submask Class B private connection
8. same network, same submask Class B private connection