| Objective: | To obtain a position utilizing my experience in unix system administration, networking and/or Telecommunications. |
| Experience: | Hardware and software using the Intel x86 based processors, and ISA/PCI based architecture. System administration of Unix systems based on 4.3 BSD (FreeBSD), and Linux (mainly Debian and CentOS). Also familiar with OS/2, VAX/VMS, DOS, Windows 95/NT/XP/W2k as well as VMWare ESX and Server. |
| Networking (LAN & WAN via Ethernet, T1, OC3), using TCP/IP, and/or Netbios. Familiar with PPtP, VPN, NAT, DHCP, POP3, IMAP, SMTP, WWW, FTP, VoIP, SNMP, BGP, OSPF, HSRP, and VRRP. | |
| Programming C, PHP, structured BASIC, Visual Basic, and various small Perl, and shell scripts. | |
| Intecom and Nortel (81c) PBX system administration. |
| (July 2004-Present): | SUNY Alfred State College. Network Manager (changed departments within the college) Upgraded networking equipment to Cisco (3550, 3570, 2950), designed fault tolerant links at the layer 2 level, by providing two links to all academic buildings, tied to a redundant pair of routers. Wrote programs to monitor the network, graph switch usage, lookup IP/MAC locations. Re-wrote registration system for students to register their computers for use on the network. Mass upgraded wireless system for 802.11n using an Aruba Networks solution. |
(Nov 2000-July 2004): | ACES at SUNY Alfred State College. Telecommunications Technician; Add/Move/Changes, PBX & VM maintenance, surveillance cameras (Coax and IP Based), cable TV, premise wiring. Finally back here after they've been trying to get me back for almost the whole time I was in Las Vegas. I came back after I foresaw ISAT folding. |
(Jan 99-Nov 00): |
Internet Services and Training(ISAT). Technician/Network Engineer; Manage TCP/IP routes w/BGP, terminal servers, maintain and evaluate network statistics. Field repair of various customer networks, and computers. Company was bought out and liquidated. |
(1995-1998): |
ACES at SUNY Alfred State College. Telecommunications Technician; Add/Move/Changes, PBX & VM maintance, surveillance cameras, cable TV, premise wiring. |
|
(1994-Present): |
The Circuit's Edge. Network/Unix system administration for my own internet access service. We provide access (dialup and wireless), web hosting, and co-location. |
| (1992-1994): | Alfred State College, AS Degree, Major in Computer Information Systems. Courses include: C Programming, Business Administration, Accounting, Microcomputer Systems 1-3, advanced Spreadsheets & databases, advanced networking, and Internet configuration and services. |
| (1991-1992): | Completed course at Lewis A. Wilson Technology school: Digital electronics, and logic circuit designs. |
| (1990-1991): | Wilson Tech; learning minicomputer operations, Data processing, and peripheral operation and repair. Assisted instructor during classes. |
| (1989-1992): | Huntington High School. |
| Hobbies: | I own several x86 based machines using Os/2, WindowsXP, and FreeBSD (Unix) operating systems; mostly for testing purposes. |
| I enjoy repairing computers, and other such electronic systems. | |
| Radio Controlled model cars, and airplanes. |
In 1993 or so, I started experimenting with unix (Linux) after getting a handle on multi user/process systems (VMS). After knowing things a bit more, I moved on to OS/2 and noticed it's TCP/IP stack was implimented much of the same way as in unix, as well as it's TCP/IP configuration files and binaries layout. While maintaining my own OS/2 system, and routing packets through it and on to a friend's unix machine, I still maintained a user account on that machine as well.
In 1995, I started working for a small ISP (Internet Service Provider) in Syracuse, helping him to start up. This system was BSDI 2.0 (BSD4.3? compliant). I worked a great deal on setting up modems, PPP (Point to Point Protocol), NNTP (Network News Transfer Protocol) using INN, and various other small tasks.
A few months later, I expanded my public BBS (Bulletin Board System) to support Internet provision. My system runs on FreeBSD, and OS/2. The system and business has been growing steadily forcing me to upgrade more and more, and write more shell scripts, as well as keeping a closer monitor on how the system is running.
My networking skills started while working at Alfred State College in the computer center. I looked at how the wiring was layed out, went into various hubs, transceivers, and computers.
Although I took a course in Novell Netware (3.11), I have forgotten most of its inner workings due to lack of use. Currently I am working with an NT4.0 server, an OS/2 peer server, and various other small single domain shares. From operating system to operation system, its all pretty much the same, it might just take a day or two to get used to how a particular operating system handles permissions with files or volumes.
At home, my Windows 95 machine uses the bigger drives from my main OS/2 machine by way of startup profiles for my "normal" logon name. To do this I'm using Netbios over TCP/IP.
I am also experimenting with NAT (Network Address Translation), and firewalls. My home setup consists of a PC based router (FreeBSD connected to the internet via PPP, then using NAT for routing IP packets to the internal network depending on the port desired). Outgoing packets are unblocked, going through the NAT daemon, and firewall. My ISP business DOES have firewalling enabled in both directions, but on a not so "strict" level.
I came into the telecommunications area simply because while at college, they needed student help in the phone office area. Because of my ability to learn technical things quickly, I was able to solve problems faster, and stayed "employed" by them for a while. After I graduated, I was called back after a few months because the Phone office needed some help. I was then hired as a full time employee.
When I first started with the Telephone Office at Alfred State College, I was working on their Intecom S/10 series PBX. It was a pretty "basic" phone system with analog, and digital sets, T1 and analog trunking, rs-232 data features via the digital sets, call forwarding (busy, no answer or all), etc.. I got to know the system pretty well.
In August 1996, we bought a Nortel Option 81C PBX. This system has most of what the other had, with the addition of Voice Mail/Auto Attendant, ACD (Automatic Call Distribution), but was nowhere near as user friendly or accommodating to the user or PBX manager/programmer.
Because of this, I put my programming skills to work, and attached a PC system to the PBX, and wrote a custom program to monitor various events, and keep separate logs depending on the messages obtained. Currently it tracks all errors and alarms in one file, splits CDR (Call detail recording) in 3 files (local, off premise, and off-to-on premise calls), and invalid authorization codes are recorded in yet another file. These files get backed up monthly, and are used to look up various activities (harassing phone calls, hacked auth codes, etc..)
Aside from this, I also coded a handful of other programs to automate some basic tasks such as mass adding/removing auth. codes, converting the CDR from a remote PBX to be rated, and whatever else is needed. These programs are either written in C or BASIC depending on what is actually needed.