Basic IT 2 (General IT Knowledge-2)
Download as PPTX, PDF1 like1,995 views
The document discusses the evolution of Unix operating systems including BSD and System V releases, and describes various storage technologies such as direct attached storage, storage area networks, network attached storage, RAID disk redundancy, and cloud computing. It also covers topics related to system fault tolerance, data center high availability clusters, virtualization, and Windows terminal services.
Basic IT 2 (General IT Knowledge-2)
- 4. BSD SVR5 http://www.rwc.uc.edu/thomas/Intro_Unix_Text/File_System.html
- 6. Contents of the Win32 Subsystem under Windows NT 3.51 Contents of the Win32 Subsystem under Windows NT 4 http://technet.microsoft.com/en-us/library/cc749980.aspx http://www.designswan.com/archives/from-window10-to-vista.html
- 7. Printing in Win NT
- 8. Direct-attached storage (DAS) storage area network (SAN) Network-attached storage (NAS) CIFS = Common Internet File System NFS = Network File System http://en.wikipedia.org/wiki/Storage_area_network
- 9. SCSI Fiber Channel ATA over Ethernet AFS = Andrew File System
- 10. DISK REDUNDANCY http://www.prepressure.com/library/technology/raid http://storage-system.fujitsu.com/global/services/system/glossary/raid/raid6/
- 11. http://technet.microsoft.com/en-us/library/cc722946.aspx http://en.wikipedia.org/wiki/Cloud_computing
- 12. System fault tolerance http://ixbtlabs.com/articles/clustering/ http://www.eveandersson.com/arsdigita/asj/oracle-fault-tolerance/ http://en.wikipedia.org/wiki/Inter-process_communication
- 13. Data Center High Availability Clusters Teaming Features (IN INTEL ANS CONTEXT – SEE INTEL LINK) Teaming Features include Failover protection, increased bandwidth throughput aggregation, and balancing of traffic among team members. Teaming Modes are AFT, SFT, ALB, Receive Load Balancing (RLB), SLA, and IEEE 802.3ad Dynamic Link Aggregation. Features available by using Intel's Advanced Networking Software (ANS) include: Fault Tolerance Uses one or more secondary adapters to take over for the primary adapter should the first adapter, its cabling or the link partner fail. Designed to ensure server availability to the network. Link Aggregation The combining of multiple adapters into a single channel to provide greater bandwidth. Bandwidth increase is only available when connecting to multiple destination addresses. ALB mode provides aggregation for transmission only while RLB, SLA, and IEEE 802.3ad dynamic link aggregation modes provide aggregation in both directions. Link aggregation modes requires switch support, while ALB and RLB modes can be used with any switch. Load Balancing The distribution of the transmission and reception load the among aggregated network adapters. An intelligent adaptive agent in the ANS driver repeatedly analyzes the traffic flow from the server and distributes the packets based on destination addresses. (In IEEE 802.3ad modes the switch provides load balancing on incoming packets.) Note: Load Balancing in ALB mode can only occur on Layer 3 routed protocols (IP and NCP IPX). Load Balancing in RLB mode can only occur for TCP/IP. Multicasts, broadcasts, and non-routed protocols are transmitted only over the primary adapter. http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/HA_Clusters/HAOv http://www.intel.com/support/network/sb/cs-009747.htm
- 14. Overview of single-server and distributed-server in WebSphere WebSphere Information Integrator Content Edition provides enterprise content integration capability to enable portals, collaborative applications, customer relationship management, and other key applications to work with distributed content and work processes throughout the extended enterprise. . is based on Java™ technology and designed to run in a J2EE environment, such as IBM® WebSphere Application Server http://publib.boulder.ibm.com/infocenter/discover/v8r4/index.jsp?topic=/com.ibm.websp
- 16. WINDOWS TERMINAL SERVER http://www.chippc.com/support/knowledge-base/answer.asp?id=611 http://technet.microsoft.com/en-us/library/cc751244.aspx
- 17. Windows NT Server Features Active Directory Service Interfaces -The Easy Way to Access and Manage LDAP-Based Directories (Windows NT 4.0) Configuring Windows NT Satellite Networking at Coho Winery Controlling the User Creating User Profiles Data Backup and Recovery Demand Dial Routing Dynamic Compulsory Tunneling with RADIUS and PPTP (Windows NT Server 4.0) Getting Started with the SNMP Service Guide to MS Windows NT 4.0 Profiles and Policies LAN and WAN Subnetworks Under IP - Lan Interconnection Managing File Systems and Drives MS Windows NT Load Balancing Service Whitepaper MS Point-to-Point Tunneling Protocol (Windows NT 4.0) NetWare Connectivity Network Design Manual - Storage for the Network: Designing an Effective Strategy Network Management for Microsoft Networks Using SNMP Reviewing Basic Network Traffic Concepts The Management of MS Cluster Server (MSCS) Computing Environments RAS and DUN Windows NT 4.0: Remote Access Server Routing in Windows NT 3.51 and 4.0 The New Task Scheduler (Windows 95 and Windows NT 4.0) TCP/IP Architecture TCP/IP Subnetting: Creating the 8-bit Subnetting Table for Class A, B, and C Networks Terminal Server Architecture Understanding User Accounts, Groups, Domains, and Trust Relationships Using the Windows NT Backup Utility MS Active Directory Service Interfaces (ADSI) (Windows NT 4.0) Windows NT Profiles
- 18. IT Security System Security, Network Security Integrity Availability Authentication Encryption Penetration testing / Hacking / Security Parameter Isolation / Quarantine Non-repudiation Intruder Detection Disaster Recovery Audit Log http://www.boran.com/security/
- 19. Important specifications and official pages The W3C pages on HTTP. RFC 1945, the specification of HTTP 1.0. RFC 2068, the specification of HTTP 1.1. RFC 1738, which describes URLs. The magic cookie specification, from Netscape. Proxy caches Web caching architecture, a guide for system administrators who want to set up proxy caches. How HTTP works A Distributed Testbed for National Information Provisioning, a project to set up a national US-wide cache system. Various The Mozilla Museum The registered MIME types, from IANA. HTTPTest. Try sending HTTP requests to various servers and see the responses. An overview of most web servers available. GET /slashdot.xml HTTP/1.1 The POST redirect problem. About the use of the word 'cookie' in computing. Host: www.slashdot.org More information about XML. About FTP URLs. User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; e A short Norwegian intro to HTTP. Accept: text/xml, text/html;q=0.9, image/jpeg, */*;q Accept-Language: en, fr;q=0.50 Accept-Encoding: gzip,deflate,compress,identity Accept-Charset: ISO-8859-1, utf-8;q=0.66, *;q=0.66 Keep-Alive: 300 Connection: keep-alive HTTP/1.1 200 OK Date: Fri, 20 Jul 2001 19:31:10 GMT Server: Apache/1.3.12 (Unix) mod_perl/1.24 Last-Modified: Fri, 20 Jul 2001 18:34:06 GMT ETag: "de47c-e5e-3b58799e" HTTP/1.0 404 Not found Accept-Ranges: bytes Server: Netscape-Enterprise/2.01 Content-Length: 3678 Date: Wed, 04 Jul 2001 20:35:17 GMT Connection: close http://www.w3.org/Protocols/ Content-length: 207 Content-Type: text/xml Content-type: text/html
- 21. Analogi SSL Algorithm Kunci A Pertama kali Dikunci & diisi kunci A Kunci B Copy kunci A masuk box dan dikunci pake gembok A Gembok pake Gembok B Dikunci gembok B & dikirim balik (simpan kunci B) Buka Gembok A Dibuka dan dikirim balik Buka Gembok B dan ambil kunci A Kirim Kunci B dg Gembok A Komunikasi dg kunci & gembok A & B
- 22. How SSL works
- 24. Datacenter
- 25. Datacenter Management Data center Designs Facilities: Room, Raised floor, Panels, Power, UPS, AC, cable trays, thermometer, Racks Wiring: Power and Data (UTP, STP, FO, KVM, etc.) Lighting, Building Control, Genset, Fire protector Grounding and Power conditions Network Infrastructure: DC-Hub Room interconnectivity, user & systems connections Data center Operations System Management Printing / Other Regular Batch Job Resource Shift / Scheduling Inventory and Asset Management Backup, Restore and Disaster Recovery Capacity Management: System and Facility Facility & Maintenance Access Control Environment Control Cleaning Service http://en.wikipedia.org/wiki/Data_center
- 26. NETWORKING
- 28. • Hub • Bridge • Switch • Router • L3 Switch • Gateway • Firewall • Load Balancers
- 32. http://nmap.org/book/tcpip-ref.html http://www.ietf.org/rfc.html
- 35. http://ciscoiseasy.blogspot.com/2010/08/lesson-6-example-of-tcpip-traffic-flow.html DHCP
- 37. Microsoft Operations Framework (MOF) http://technet.microsoft.com/en-us/library/cc506049.aspx
- 40. Config Mgmt
- 42. MOF model
- 49. Service Strategy provides advice and guidance on designing, developing and implementing service management - both as an operational capability within an organisation but also how to use that capability as a strategic asset. It tries to ensure that consideration is given as to why a particular activity is to be performed - before an organisation begins to think about how it will be performed. The core process in Service Strategy involves: Define the market Develop the offerings Develop strategic assets Prepare for execution
- 50. Service Design contains discussions on the roles, responsibilities and activities involved within the Service Design stage and also considers the impact of processes on the service designs produced. Service Design also describes the major processes involved within these design activities, including: • Service Catalogue Management • Service Level Management • Capacity Management • Availability Management • IT Service Continuity Management • Information Security Management • Supplier Management.
- 51. Service Transition is the controlled building, testing and deployment of a new or changed service which enables the planning, tracking and checking of progress against requirements at every stage through the service transition. The Service Transition stage of the lifecycle provides guidance on ensuring that the introduction, deployment, transfer and decommissioning of new or changed services is consistently well managed. Service Transition ensures that the transition processes are streamlined, effective and efficient so that the risks relating to the service in transition are minimised. Successful Service Transition depends on an effective understanding and application of the Change Management process as well as quality assurance, risk management and effective programme and project management. The Service Transition stage of the lifecycle receives input from the Service Design stage and provides output to the Service Operation stage. The main goals and objectives for Service Transition include: •Assisting organisations wishing to plan and manage service changes and deploy service releases into the production environment successfully. •Setting customer expectations on how the performance and use of the new or changed services can be used to enable business change. •Enabling the business change project or customer to integrate a release into their business processes and services. •Reducing variations in the predicted and actual performance of the transitioned services. •Reducing known errors and minimising the risks from transitioning the new or changed services into production. •Planning and managing resources to successfully establish a new or changed service into production within the predicted cost, quality and time estimates. •Ensuring minimal unpredicted impact on the production services, operations and support organisation. •Increasing the customer, user and service management staff satisfaction with the service transition practices. •Providing a consistent and rigorous framework for evaluating the service capability and risk profile before a new or changed service is released or deployed. •Establishing and maintaining the integrity of all identified service assets and configurations as they evolve through the service transition stage. •Providing efficient repeatable build and installation mechanisms that can be used to deploy releases to the test and production environments and re-built if required to restore service.
- 52. Service Operation is responsible for all aspects of managing the day-to-day operation of IT services, ensuring that processes and activities are operated (and continue to be operated) on a ‘business as usual’ basis. Its key purpose is to coordinate and perform the processes and activities that support the delivery of the IT services at the levels defined in the relevant Service Level Agreements. The scope of Service Operation covers the IT services, the service management processes, the underpinning technology used to deliver those services - and the people used to manage all of these aspects. Service Operation can be optimised in two different ways: Long term incremental improvement - monitoring performance over a period of time, analysing whether improvement actions are required, and then implementing those improvements via the Continual Service Improvement book Short term improvement activities - these are smaller actions, such as tuning, workload balancing, training, etc. Service Operation is supported by a number of processes and functions: Processes: Access Management, Event Management, Incident Management, Problem Management and Request Fulfilment Functions: Service Desk, Technical Management, IT Operations Management, Application Management. This list includes three new functions critical for executing process activities and managing service components. These are: Technical Management, which is the custodian of expertise related to all service components. Technical Management typically manages the infrastructure from Design through to Operation. Applications Management, which plays a similar role for software applications. Of particular importance is how this function interfaces with Application Development teams throughout the Software Management Lifecycle. IT Operations Management, which may be performed by the previous two functions, but is often centralized into a dedicated unit. This function executes routine activities, and monitors and controls the health of the infrastructure.
- 53. Continual Service Improvement is not a lifecycle stage, but a wrapper used throughout the whole service lifecycle. It has inputs and outputs for all lifecycle stages. It focuses on the overall health of Service Management within the organisation. Continual Service Improvement is the continual alignment and adjustment of IT Services to meet the changing business needs by identifying and implementing improvements to IT Services that support Business Processes. The main purpose and objectives for Continual Service Improvement include: the overall health of ITSM as a discipline the continual alignment of the portfolio of IT Services with the current and future business needs the maturity of the enabling IT processes required to support business processes in a continual Service Lifecycle model review, analyze and make recommendations on improvements across all lifecycle stages manage the improvement activities The scope of CSI is to: introduce the concepts and principles of CSI at a high level, ensuring buy-in define the value of CSI to the organisation define how and what methods and techniques will be used CSI has a cycle which covers the following steps: understanding and embracing the high-level business vision assessing the current situation and baselining the analysis determining the priorities for improvement determining the detailed plan for improvement verifying that measurements and metrics are working ensuring that changes are embedded into the organisation
- 54. ITIL Vendor Mgmt
- 55. Next Jan’11: PC Feb’11: OS Mar’11: Network Data & Voice Apr’11: Server May’11: .NET Jun’11: SAP BASIS Jul’11: SOA & SAP BW Aug’11: SAP MM Sept’11: SAP PS & PP Oct’11: SAP FICO Nov’11: SAP BPC Dec’11: IT Management 2012: Advanced and Applied matters