[ Pobierz całość w formacie PDF ]
.and mainframe networks to work together.The approach taken depends partly onAchieving Interoperabilitywhether the NOS is primarily a LAN- or ain Enterprise Networksmainframe-based system.Interoperability refers to the ability of two LAN-based operating systems (for exam-different networks to communicate and ple, Novell s NetWare or Banyan s VINES)work together, regardless of whether these generally use their native protocol stack tonetworks use the same network architecture.communicate with the LAN end of theThis is vital to the success of enterprise enterprise network.For example, a NetWarenetworks.server might use NCP (NetWare Core Proto-In most cases, the difficulties arise when col) and the IPX/SPX protocols to communi-trying to connect the PC-based departmental cate with stations on an Ethernet networkand local-area networks (LANs) with the and to provide file and print services to thesecentralized and mainframe-based MIS (man- workstations.Lower-level communicationsagement information system), or corpo- can be accomplished through ODI (Openrate, networks.This is because these two Data-link Interface) drivers.This allows theNetwork, Heterogeneous 681server to support other protocol stacks (for with a NOS (for example, NetWare), it isaexample, the AppleTalk or TCP/IP stacks) possible to provide greater processing powerwhen communicating with Macintosh or on the server so that some of the criticalbUNIX-based clients.applications can be done on servers insteadcTo communicate with the mainframe end of mainframes.UnixWare can provide appli-of the enterprise network, NOSs may use a cation server capabilities, and NetWare candgateway that supports a protocol stack and provide file and printer services.networking architecture compatible with the Another benefit of this type of integrationemainframe environment.Because the main- is that storage and data can be distributed.fframe will often be an IBM, the gateway will For example, files or data may be managedgenerally use the SNA (Systems Network by UnixWare or by the NetWare server,gArchitecture) protocols.depending on available storage and on userWith this approach, the server (with its needs.Also, applications and processing hgateway) sits between the LAN and the power can be distributed.Workstations canimainframe.The server provides the usual run their personal applications just as on afile and printing services to the LAN; the LAN, but can get access to the capabilitiesjmainframe may provide processing for of the UnixWare system if necessary.klarger tasks.Workstations generally runBROADER CATEGORYtheir own applications.lNetworkMainframe-based operating systems(such as MVS, VSE, or VMS) generally use a mmodule that makes it possible to treat the Network, Front-EndnLAN as just another session for the main-A network of high-performance, special-frame.For example in IBM environments,opurpose workstations (such as graphics orthe SNA s APPC (Advanced Program to Pro-engineering machines).For maximum band-pgram Communication) component allows awidth, such machines will be connectedLAN (for example, a Token Ring network)using optical fiber.qto communicate with the mainframe as if theLAN were just another device on the main-rNetwork, Global-Area (GAN)frame s network.In this approach, the LANsis just another node on the mainframe s net-SEEwork.The mainframe provides print, file,GAN (Network, Global-Area )tand application services for its nodes.uIntegrating a 32-Bit Operating System with a NOS Network, HeterogeneousvA network that is using multiple protocols atThe distributed computing capabilities ofthe network layer.In contrast, a homoge-wa 32-bit operating system such as UNIXneous network uses a single protocol at theprovide another way to create and controlxnetwork layer.enterprise networks.By integrating a 32-bitoperating system (for example, UnixWare)yz682 Network, HomogeneousSEE ALSONetwork, HomogeneousInfrared TransmissionA network that is using a single protocol atthe network layer.In contrast, a heteroge-Network Managementneous network uses multiple protocols at theThe purpose of network management is tonetwork layer.automate the processes of monitoring andadjusting the performance of a network, asNetwork, Host-Basedwell as providing reports about networkactivity.Network management modelsA network in which control of the networkare built around managed objects, which areis concentrated or centralized in a main-any network elements that can be used orframe.If the controller node is a PC, the net-monitored.These models generally specifywork is said to be server-based.Host-basedthe kinds of attributes managed objects mustnetworks are examples of centralized net-have and the kinds of functions associatedworks, and are in contrast to distributedwith them [ Pobierz całość w formacie PDF ]
zanotowane.pl doc.pisz.pl pdf.pisz.pl odbijak.htw.pl
.and mainframe networks to work together.The approach taken depends partly onAchieving Interoperabilitywhether the NOS is primarily a LAN- or ain Enterprise Networksmainframe-based system.Interoperability refers to the ability of two LAN-based operating systems (for exam-different networks to communicate and ple, Novell s NetWare or Banyan s VINES)work together, regardless of whether these generally use their native protocol stack tonetworks use the same network architecture.communicate with the LAN end of theThis is vital to the success of enterprise enterprise network.For example, a NetWarenetworks.server might use NCP (NetWare Core Proto-In most cases, the difficulties arise when col) and the IPX/SPX protocols to communi-trying to connect the PC-based departmental cate with stations on an Ethernet networkand local-area networks (LANs) with the and to provide file and print services to thesecentralized and mainframe-based MIS (man- workstations.Lower-level communicationsagement information system), or corpo- can be accomplished through ODI (Openrate, networks.This is because these two Data-link Interface) drivers.This allows theNetwork, Heterogeneous 681server to support other protocol stacks (for with a NOS (for example, NetWare), it isaexample, the AppleTalk or TCP/IP stacks) possible to provide greater processing powerwhen communicating with Macintosh or on the server so that some of the criticalbUNIX-based clients.applications can be done on servers insteadcTo communicate with the mainframe end of mainframes.UnixWare can provide appli-of the enterprise network, NOSs may use a cation server capabilities, and NetWare candgateway that supports a protocol stack and provide file and printer services.networking architecture compatible with the Another benefit of this type of integrationemainframe environment.Because the main- is that storage and data can be distributed.fframe will often be an IBM, the gateway will For example, files or data may be managedgenerally use the SNA (Systems Network by UnixWare or by the NetWare server,gArchitecture) protocols.depending on available storage and on userWith this approach, the server (with its needs.Also, applications and processing hgateway) sits between the LAN and the power can be distributed.Workstations canimainframe.The server provides the usual run their personal applications just as on afile and printing services to the LAN; the LAN, but can get access to the capabilitiesjmainframe may provide processing for of the UnixWare system if necessary.klarger tasks.Workstations generally runBROADER CATEGORYtheir own applications.lNetworkMainframe-based operating systems(such as MVS, VSE, or VMS) generally use a mmodule that makes it possible to treat the Network, Front-EndnLAN as just another session for the main-A network of high-performance, special-frame.For example in IBM environments,opurpose workstations (such as graphics orthe SNA s APPC (Advanced Program to Pro-engineering machines).For maximum band-pgram Communication) component allows awidth, such machines will be connectedLAN (for example, a Token Ring network)using optical fiber.qto communicate with the mainframe as if theLAN were just another device on the main-rNetwork, Global-Area (GAN)frame s network.In this approach, the LANsis just another node on the mainframe s net-SEEwork.The mainframe provides print, file,GAN (Network, Global-Area )tand application services for its nodes.uIntegrating a 32-Bit Operating System with a NOS Network, HeterogeneousvA network that is using multiple protocols atThe distributed computing capabilities ofthe network layer.In contrast, a homoge-wa 32-bit operating system such as UNIXneous network uses a single protocol at theprovide another way to create and controlxnetwork layer.enterprise networks.By integrating a 32-bitoperating system (for example, UnixWare)yz682 Network, HomogeneousSEE ALSONetwork, HomogeneousInfrared TransmissionA network that is using a single protocol atthe network layer.In contrast, a heteroge-Network Managementneous network uses multiple protocols at theThe purpose of network management is tonetwork layer.automate the processes of monitoring andadjusting the performance of a network, asNetwork, Host-Basedwell as providing reports about networkactivity.Network management modelsA network in which control of the networkare built around managed objects, which areis concentrated or centralized in a main-any network elements that can be used orframe.If the controller node is a PC, the net-monitored.These models generally specifywork is said to be server-based.Host-basedthe kinds of attributes managed objects mustnetworks are examples of centralized net-have and the kinds of functions associatedworks, and are in contrast to distributedwith them [ Pobierz całość w formacie PDF ]