In addition when just come into operation the system

This preview shows page 32 - 44 out of 75 pages.

In addition, when just come into operation, the system will more or less experience some minor errors or problems. Therefore, I would like the partner to set up a copper box with the installation side to maintain and check twice a month, and check continuously until 1 year after operating the system to ensure the system works stability. And to avoid errors that lead to data loss, I recommend that users back up data once a week, starting from system boot until 1 year later. After 1 year, when the system is completely stable, in order to be able to use the system effectively, I recommend maintenance and inspection every two months; Backup data once a month. After 3 years of use, I recommend that users replace some devices such as switches, access points and expand the capacity of the server. And I would like to announce that system users should not upgrade the device and expand the system for 1 year since starting the system because the system is not completely stable, the upgrade will lead to conflicts and collapse. The system has to be completely reconfigured and it is very difficult to configure each and every system. Users can upgrade and expand the system after more than 1 year of use. And when upgrading or expanding, I recommend system users to upgrade devices and expand the number of concurrent users to increase by 5 times compared to when the new system works, because the system cannot connect continuously upgrading for a short time. And the time between next upgrade is enough for the system to stabilize for users to continue upgrading and expanding. Test Plan: - Step 1: Ping test, the network uses DHCP service so we have to check the IP of the device before pinging + First: Ping to Printer: Ping from PC Staff 1 (IP: 10.2.10.15) to Printer 1 (IP: 10.2.10.28), Printer 2 (IP: 10.2.10.4) and Printer 3 (IP: 10.2.10.30)
Images 20: Test Ping to Printer 1
Images 21: Test Ping to Printer 2
Images 22: Test Ping to Printer 3 + Second: Ping from PC Staff 1 to PC MAAS 1 (IP: 10.2.10.22) and PC S1 (IP: 10.2.10.27) is PC of Vlan Staff.
Images 23: Test Ping in Vlan Staff
Images 24: Test Ping in Vlan Staff + Third: Ping from PC 1 (IP: 10.2.12.23) to PC 28 (IP: 10.2.12.60) of Vlan Labroom.
Images 25: Test Ping in Vlan Labroom - Step 2: Ping to check connected + Fisrt: Ping connected in LAN network: ping between Vlans. Because Vlan Classroom is Vlan use to connect with access point, so we don’t ping to Vlan Classroom. And we have two result that is Ping form Vlan Staff to Vlan Labroom and vice versa. Ping form PC Staff 1 (IP: 10.2.10.15) to PC 1 (IP: 10.2.12.23) and vice versa.
Images 26: Test Ping in LAN network
Images 27: Test Ping in VLAN network + Second: Ping connected internet: ping connected to server from LAN network. Ping from PC Staff 1 (IP: 10.2.10.15) to Server (IP: 10.3.1.4)
Images 28: Test Ping from LAN network to Internet 2.7 The P7
Images 29: Demo Network System 2.8 The P8 - Configure for Firewall Server + Check the configuration of the Firewall Server:
ciscoasa> ciscoasa>en Password: ciscoasa#show run ciscoasa#show running-config : Saved : ASA Version 8.4(2) !

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture