This project involves implementing HSMS driver under
Windows NT operating system. The driver development project involves following
components,
1.
HSMS
Session Component
2.
HSMS
- TCP/IP Interface Component
3.
TCP/IP
Transport Component
The HSMS Session Component (HSMSSession) is the main
interface visible to the user of the HSMS driver. HSMSSession takes SECS II (or
whatever) messages from the user, builds HSMS messages, and transmits them to
the peer HSMS driver using the HSMSMessage and HSMSTransport Components. It
also receives HSMS messages sent by the peer, parses them for error checking
and interpretation. The interpretation in this case could mean conversion to
SECS II messages to be delivered to the user.
The interface component (let's call it HSMSMessage)
sits between the HSMSSession
Component and the TCP/IP Transport component (let's
call it HSMSTransport). The job of HSMSMessage is to package HSMS messages
coming from the HSMSSession in appropriate TCP/IP packets for transmission, and
unpackage the TCP/IP packets to build HSMS messages to be given to HSMSSession.
The HSMS driver on the Link Manager will need to
communicate over TCP/IP with
its remote HSMS counterpart running on Windows NT.
This communication would
be provided by the HSMSTransport Component.
Design and
development of a module on Windows NT 3.51 for a Network Storage Management
system (SMS). The module has a Requestor (client) and a Responder (server)
side, and it handles communication among other pieces of the SMS and makes it
network transparent. It also provides port-mapping facility for network
services. Protocols supported: TCP/IP, IPX/SPX. Developed in Visual C++. Ported
the Requestor side to Windows 3.1 using NetWare Client SDK.
This module
is the Server component of a network storage management system and it mediates
access to the file systems or databases being backed up or restored, via a
platform-independent API. Development on Solaris 2.4 in object oriented C. Also
developed a Motif-based test tool.
Customization of an HTTP server for management of
scientific information for a research lab. The management included publication
of technical papers, interactive operations using CGI scripts, and review
reporting using HTML forms. Prototype was developed on a Linux system.
Conducted
requirement analysis and initial design study for the following components of a
network storage management product for the purpose of porting it to the Solaris
2.4 platform.
NetWare Semaphores, NetWare Transport Layer Interface (TLI), Database
subsystem,
Queue Management System (QMS), NetWare Service Advertisement Protocol (SAP).
This was a
port of a SCO Unix-based STREAMS driver to a Trusted PC-based SVR4 Unix. The
target Ethernet was a modified version of the IEEE 802.2 Spec with provisions
for security and encryption.
The
Security Option as described in RFC 1108 for the Internet Protocol (Ver 4) was
implemented for Solaris 2.4 operating system for the Intel PC. The software
also included software for processing CIPSO (Commercial Security).
Development
of trusted TCP/IP protocol software based on the Defense Department's
DNSIX 3.0 Specification. The
development was done for Sequent's multi-processor Dynix (ptx 2.1) system. The
software included a STREAMS module, two STREAMS pseudo drivers, modifications
to TCP/UDP/IP layers, two daemon (server) programs, and user interface (Motif
GUI) for administration.
MP Kernel Debugging
Maintenance and debugging of Motorola 4.3 88K Unix
system.
[ Home | Areas Of Work | S/WSkills | Employment | EmailMPI | Search ]