|
Obj # |
730 Network Management Using ManageWise 2.6
|
|
|
|
Section 1 = The Purpose and Benefits of Using ManageWise |
|
|
1 |
Describe the role of network management. Gather information:
Analyze data:
Perform preventative maintenance:
Complete repairs:
Re-engineer
existing systems, replace inadequate systems, and expand existing systems |
|
|
2 |
Explain the management tasks supported by ManageWise. ASSET INVENTORY AND MANAGEMENT - (MW Inventory Manager)
· Automatic discovery (NetExplorer software) discover routers, servers, and workstations, regardless of protocol
SERVER MONITORING AND MANAGEMENT - (NW Management Agent)
DESKTOP MANAGEMENT - (Desktop Manager software)
NETWORK DISCOVERY (NetExplorer software) ·
Function: discovers IP, IPX, and LANalyzer Agent
information ·
Location: funs on at least 1 server on the
internetwork NETWORK TRAFFIC ANALYSIS AND MANAGEMENT - (NW LANalyzer software)
NETWORK-WIDE VIRUS PROTECTION - (Cheyenne InocuLAN AntiVirus)
|
|
|
3 |
List the ManageWise components.
ManageWise
Console provides the
graphical user interface (GUI) that allows you to manage your internetwork. |
|
|
|
Section 2 = Installing and Configuring ManageWise
|
|
4 |
Install ManageWise on a NetWare server and a Windows workstation. Verify system requirements:
Verify MW Console system requirements:
Collect MW Server and Console information: ·
User account
and password (Admin equivalent) ·
NetExplorer
server name (3.12, 4.1x or later) ·
Update
autoexec.ncf? ·
Update
container or system login script? ·
MW 2.6
supports only NW 5 and NW 4.1x as MW servers ·
MW setup
automatically updates AUTOEXEC.NCF, NET$LOG.DAT, AUTOEXEC.BAT, WIN.INI files
Prepare your system for installation: ·
verify minimum
system requirements for the server ·
unload
antivirus software on server ·
unload MW
software on server ·
if upgrading,
consult MWREADME.wri ·
verify minimum
system requirements for the MW console WS ·
shutdown all
applications in Windows ·
map a drive to
MW server Install and configure the MW software: ·
NetExplorer
·
NW Management
Agent ·
NW LANalyzer
Agent ·
Desktop
Management Tools ·
InocuLAN
·
MW Console ·
TrendComplete/SyncComplete |
|
5 |
Install the ManageWise product manuals
|
|
6 |
Describe the post-installation procedure for ManageWise. ·
Synchronize
the MW_LOGIN.DAT file on all servers ·
Enable the
LANalyzer Agents ·
Enable IP
packet forwarding, if necessary ·
Update MW_AUTO.NCF
file on all servers ·
Restart all
Netware servers ·
In MW Console
select All|Network Segments, select network - Configure|Network
Segment|Start Polling |
|
7 |
Describe the modifications made to AUTOEXEC.NCF, MW_AUTO.NCF, MW_LOGIN.DAT, container Login Script, and System Login Script during ManageWise installation. During MW installation the following changes are made:
·
NMBASE.NCF ·
NETXPLOR.NCF ·
NMA2.NCF ·
MW_AUTO.NCF
(Desktop Management) ·
START4.NCF
(InocuLAN)
·
load user ·
load ldinv.nlm
file=sys:mw\ldt ·
load ldiscan
inv_serv=<server> file=sys:mw\ldt scannow
REM === ManageWise Desktop Management Include file for System Login
===
REM ---- MANAGEWISE 2.6 -----
- similar to the changes to container login script. |
|
|
Section 3 = Using ManageWise to Create a Database of System Components
|
|
8 |
Explain the ManageWise components and files that are responsible for the network discovery process. ·
NetExplorer: runs on NetExplorer server ·
NetExplorer
Manager: runs on Managewise Console
Station ·
NetExplorer
writes discovered information to: SYS:\NMDISK\NETXPLOR.DAT and NXPDISK.DAT ·
NetExplorer
Server send records to SYS:\NMDISK\NETXPLOR.DAT to NetExplorer Manager
on a MW Console station ·
NetExplorer
Manager stores records in MW database on MW Console ·
NETXPLOR.NCF: search add sys:\nmdisk load sys:\nmdisk\nxplanz collects info from LANalyzer Agents ·
Discovery
process: o IP discovery (using local router table info discover
other routers and so on) o IPX discovery (NetExplorer server IPX address, LAN type of network boards, SAP. Then the same for each device listed in directory or bindery) Working directory sys:\nmdisk\nxpwork o Protocol-independent discovery (NXPLANZ identifies NW LANalyzer Agents, LANalyzer Agent on segment discover devices by MAC address in packets, NXPLANZ retrieves MAC address data by SNMP) o during initial discovery cycle, these modules run sequentially. Later they run concurrently (only new or changed data are send to NETXPLOR.NLM). o initial discovery can take from a couple of
hours to several days. |
|
9 |
Explain the function of the LANalyzer Console.
|
|
10 |
Explain the function of the NetExplorer Console.
simultaneously to one NetExplorer Server - NetExplorer
System Status shows
overall status with 2 values: o
Initial cycle
in progress: at least 1 discovery module (NXPIP, NXPIPX, or NXPLANZ) has not
yet completed its first cycle o
Initial cycle
completed: all modulaes have completed at least 1 pass -
Module status shows status of each module (NXPIP, NXPIPX, and NXPLANZ)
and the number of
cycles each module has completed. Status values: o
Not Loaded o
Waiting to
Start o
Running o
Suspended o
Completed o
Unknown
|
|
|
Section 4 = Evaluating the Database
|
|
11 |
Prepare a detailed internetwork map through the use of the default Internetwork and Segment Maps. Network documentation should include:
MW automatically creates Internetwork and Segment maps based on info it gathers from NXPIPX (and NXPIP and NXPLANZ if running) Internetwork map (File|Open|Internetwork map) references Segment map (File|Open|Segment map) that segment. |
|
12 |
List all the discovered IP and IPX network addressess using ManageWise View All Tables. 1. View|All|IP
Networks network |
|
13 |
List all the discovered Media Access Control (MAC) addresses using Desktop Manager.
|
|
14 |
Inventory the internetwork's hardware and software using Desktop Manager's Query tool.
Tools|Query
! SYS:\MW\LDT\Changes.log is not enabled by
default. |
|
15 |
Use SyncComplete to create a unified database, post queries, and generate reports.
|
|
|
Section 5 = Troubleshooting Login Problems |
|
16 |
Verify that the server is accepting login attempts. ·
On the segment
map, double-click the icon for <server>. ·
In the
<server> configuration window, double-click the System Summary
icon ·
Verify that Login
State is set to enabled. |