BEGINNING AND INTERMEDIATE STEPS ON PREPARING BLACKBOARD SYSTEM CONNECTIVITY FOR AUTOMATED...
-
Upload
alexander-barton -
Category
Documents
-
view
219 -
download
0
Transcript of BEGINNING AND INTERMEDIATE STEPS ON PREPARING BLACKBOARD SYSTEM CONNECTIVITY FOR AUTOMATED...
BEGINNING AND INTERMEDIATE STEPS ON PREPARING BLACKBOARD SYSTEM CONNECTIVITY
FOR AUTOMATED REDUNDANCY/FAIL-OVER CAPABILITY
STRATEGY, IMPLEMENTATION, DOCUMENTATION
ABOUT THIS PRESENTATION
This session will show you what GW has done to prepare its connectivity for redundancy and fail-over. Much of what we discuss can be applied at schools looking for more robust and modularized connectivity but who are not planning on implementing a fail-over strategy soon. We will go over different versions, permutations and reasoning behind our current setup as many of these can offer useful insight for the wide range of circumstances that Bb schools represent. This session is more or less a sequel to the fail-over server presentation given by GW last year.
The George Washington UniversityThe “one-card” system had been in place for seven years with a
large existing infrastructure, multiple privileges & accounts and approximately 1000 devices including IPCs, terminal servers
Security 379 Activity 43POS68 Vending 57MDTs120Laundry 51VTS 8Copiers/Microfiche 48
Interfaces: Follett JDA Bookstore POS, Pharos Uniprint, MDT, Catapult POS, Campus Video Solutions TIABlackboard Transaction System –UNIX Edition,
OUR SERVER
Just kidding!
Why should you work on your connectivity.
Money Money Money Face
How much does your system take-in in one day.
Look at it backwards. What is real cost of precautions in terms of daily revenue.
What happens to that money if system is down- it doesn’t get spent through you.
Liability and safety concerns
Money Money Money
Face
Imagine how you will look if you haven’t been pushing for upgrades, redundancy, stable and re-routable communications.
Imagine how your boss will look.
Do you want to be the one that didn’t seem to be concerned?
DIVERSITY OF LEGACY DIVERSITY OF LEGACY COMMUNICATIONS COMMUNICATIONS
AND THEIR PROBLEMSAND THEIR PROBLEMS
DIVERSITY OF LEGACY COMMUNICATIONS AND THEIR PROBLEMS
Terminal Servers Line Drivers Dry pairs Modems RS 485 RS 232 Serial FDIs (BSI) Private
connections
DIVERSITY OF LEGACY COMMUNICATIONS AND THEIR PROBLEMS
Special connectors- inventory and repair procedures Proprietary devices – inventory and repair cycling Multiple service cost models – IP dedicated unconditioned house pairs
(dry pairs) Dedicated unconditioned Phone Co.
pairs (dry LADA circuits) Analog house pairs (dial tone). Analog Phone Co. pairs (dial tone). Documentation/accounting difficulties. Specialized Technical training/familiarization Lots of single points of failure.
THE QUICK THE QUICK DISCONNECTDISCONNECT
THE QUICK DISCONNECT
This was our first step to making the system more modular. We had bought a second server and it was configured. Data migration, patching, database update intervals were big issues but not the focus here.
We realized that even though we had plans to cut down the times and uncertainty of these other issues, to swap out our server, even if we put it in the same place would take us a long time of plugging and unplugging.
The potential for mistakes was big.
THE QUICK DISCONNECT
FIREWALLDATACARD
UNIPRINTNET SWITCH
UNCOND.
ANALOG
QUICK DISCONNECT CABLE TO INFRASTRUCTURE
PERMANENT INTERNAL CABINET INTERCONNECT WIRING
F I B E R
- -----25 PR.---- LOCAL COPPER COPPER
(AMPHENOL)
So we came up with this plan of consolidating all of the outside connections onto one point.
In order to do this we had to add something that is the bane of any technicians existence. We had to add extra connection points.
Normally this would have been a really bad thing, but in this case, it cleaned up all of our wiring and made out switchover time really short -- 10 minutes.
THE QUICK DISCONNECT
FIREWALLDATACARD
UNIPRINTNET SWITCH
UNCOND.
ANALOG
QUICK DISCONNECT CABLE TO INFRASTRUCTURE
PERMANENT INTERNAL CABINET INTERCONNECT WIRING
F I B E R
- -----25 PR.---- LOCAL COPPER COPPER
(AMPHENOL)
1 ANALOG CONNECTION BLOCK2 DRY CIRCUIT CONNECTION BLOCK3 MEDIA CONVERTER4 MEDIA CONVERTER5 DATACARD JACK6 NETWORK SWITCH JACK7 UNIPRINT GATEWAY (LOCAL-SERIAL)8 SERVER1 FIREWALL CONNECTION 9 SERVER2 FIREWALL CONNECTION
DRY CIRCUIT CONNECTION BLOCK (RJ12)1-4 GWORLD LOOP LAD CIRCUITS5 BSI6 TEST LAD
QUICK CONNECTION WIRING DIAGRAMConnection mounting board inside of Server 1and Server 2 cabinets
ANALOG CONNECTION BLOCK (RJ12)1-8 MDT MODEM 9 BLACKBOARD SUPPORT - SERVER1 10 BLACKBOARD SUPPORT - SERVER211 TEST MDT12-13 OCP MODEM
THE QUICK DISCONNECT
WHAT’S SO GREAT WHAT’S SO GREAT ABOUT IP?... ABOUT IP?...
AND WHY SHOULD I PAY FOR AND WHY SHOULD I PAY FOR IT?IT?
WHAT’S SO GREAT ABOUT IP AND WHY SHOULD I PAY FOR IT.
Your networking people will understand it.
Your connections can be repaired and replaced more easily
Many of your circuit paths may already exist.
Better reporting by Bb IP devices and network devices
You may be able to share costs with other departments for Techs, equipment and circuit paths.
WHAT’S SO GREAT ABOUT IP AND WHY SHOULD I PAY FOR IT.
Fewer service cost models.
You can incorporate or help develop universally applied documentation.
Potential for redundancy and incorporation into Networking’s overall plans.
Potential for sharing exclusive connections with other vital services.
Get yourself in line with where most of the future development is going.
It’s all going that way anyway.
Universal edition is coming to a Campus near you.
One of the great features of the coming Universal edition is the fact that you will no longer need an NP. The NP is an expensive, proprietary, hard to configure and connect, potential single point of failure. Bb, I’m sure, and GWU in any case will be working on redundancy and failover strategies for the Universal Edition’s new NP configuration. Dependency on serial communications can prevent you from being able to take advantage of some of these features.
WHAT’S SO GREAT ABOUT IP AND WHY SHOULD I PAY FOR IT.
Incentives- Methods of attack
Plans can coincide w/future upgrades of system Propose and if needs be – let it get shot down Mention other systems may be able to take
advantage – get allies. IP -Its all gonna go that way anyway. Maybe you can start a wider initiative and make
yourself look really good.
WHAT’S SO GREAT ABOUT IP AND WHY SHOULD I PAY FOR IT.
CONVERSION TO CONVERSION TO IPCONVERTERSIPCONVERTERS
CONVERSION TO IPCONVERTERS
CAMPUS BUILDINGGWORLD HUB
485 CONV.
LINE DRIVER
SECURITY SECURITY SECURITY
LAUNDRY COPIER OTHER
RJ45JACK
RJ45JACK
RJ45JACK
RJ45JACK
MEDIA CONV.
REMOTE IP CONV.
RJ45
485BLDGNET
FIBER LINE TO CAMPUS FIBER NET
PATCH CABLES
QUICK SWITCH INVOLVES REMOVING 485 CONVERTER’S RJ45 PLUGS FROM JACKS FROM AND INSERTING PLUGS FROM IP CONVERTER
QUICK SWITCH GWORLD IN-BUILDING CONNECTION SCHEME (GENERAL)
IP
BJK 09/29/01
For conversion of our serial, RS485 circuits over to IP connections using IP Converters, we used a staged approach where, with a very short down time, we first converted the existing connections to be modular . We created some inexpensive intermediate connector assemblies that allowed us to continue running over the old connectivity system until the pieces for the IP connectivity were in place. Then, with another very short downtime, we switched over. The hidden beauty of this conversion method is that if for any reason you have a problem with the switch over to IPConverters, you can fall back to your original hardware in seconds.
CONVERSION TO IPCONVERTERS
CONVERSION TO IPCONVERTERS
GWORLD REMOTE HUBSITE RJ45 INSTALLATION(PRE-CONVERSION)
DEVICE CABLES
485 CONVERTER’S SINGLE TB10 CAN HAVE MULTIPLE DEVICE CABLES CONNECTED.TERMINALS 1-5 AND 6-10 ARE DUPLICATE SETS.STANDARD WIRING
TB10 PIN CAT 5 COLOR BELDEN COLOR FUNCTION1 / 6 WH/OR WHITE R-2 / 7 OR/WH GREEN R+3 / 8 GRN/WH SHEILD SHEILD4 / 9 WH/BU RED T-5 /10 BU/WH BLACK T+
10 9 8 7 6 5 4 3 2 1
485 CONVERTER’S TB10
CURRENT RS485 CONVERTER HOOK UP
CONVERSION TO IPCONVERTERS
10 9 8 7 6 5 4 3 2 1
485 CONVERTER’S TB10
RJ45PLUGS
TB10 PIN CAT 5 WIRE COLOR FUNCTION1 / 6 WH/OR R-2 / 7 OR/WH R+3 / 8 GRN/WH SHEILD4 / 9 WH/BU T-5 /10 BU/WH T+
Create intermediate cable assemblies.
CONVERSION TO IPCONVERTERS
RJ45 PIN CAT 5 BELDEN FUNCTION1 WH/OR WHITE R-2 OR/WH GREEN R+4 BU/WH BLACK T+5 WH/BU RED T-6 GRN/WH SHEILD SHEILD3* N/A N/A N/A
RJ45 jacks should be set as uniformly as possible (preferably in rows) and separated by loop and marked for loop number and address(s). Wires can be either cat 5 or Belden type. Color codes will have two standards.485 converter pins can hold more than one wire as depicted, RJ45 jacks should not (one cable per RJ45 jack).
RJ45 SCREW TERNINAL
JACK
RJ45 SCREW TERNINAL
JACK
1
2
3
4
8
7
6
5
DEVICE CABLES
Make it modular.
CONVERSION TO IPCONVERTERS
CAMPUS BUILDINGGWORLD HUB
485 CONV.
LINE DRIVER
SECURITY SECURITY SECURITY
LAUNDRY COPIER OTHER
RJ45JACK
RJ45JACK
RJ45JACK
RJ45JACK
MEDIA CONV.
REMOTE IP CONV.
RJ45
485BLDGNET
FIBER LINE TO CAMPUS FIBER NET
PATCH CABLES
QUICK SWITCH INVOLVES REMOVING 485 CONVERTER’S RJ45 PLUGS FROM JACKS FROM AND INSERTING PLUGS FROM IP CONVERTER
QUICK SWITCH GWORLD IN-BUILDING CONNECTION SCHEME (GENERAL)
IP
BJK 09/29/01
The Meshed NetworkThe Meshed Network
The Meshed Network
Work around power outages and connectivity problems Can be made to be self-re-routable Allows relatively easy connectivity for location changes of
components of you system (server, carding, administrations stations)
Network metrics, monitoring, balancing
The Meshed Network
IP routers in a meshed network
IP routers in a meshed network
The Meshed NetworkThe Meshed NetworkWith repeaters for common leg runsWith repeaters for common leg runs
The Meshed Network
With repeaters for common leg runs
The Meshed Network
With repeaters for common leg runs
IP Router switches with repeaters for common leg runs
BALONEY HALLSWITCH ROOM
EXISTINGSWITCH
BALONEY HALLSWITCH ROOM
EXISTINGSWITCH
Loop 1
Loop 2
Loop 3
Loop 4
COMMON HUB OTHER HOPS BALONEY HALLSWITCH ROOM
EXISTINGSWITCH
Loop 1
Loop 2
Loop 3
Loop 4
COMMON HUB OTHER HOPS
REPEATER
FIRST STEP
Loop 1
Loop 2
Loop 3
Loop 4
COMMON HUB OTHER HOPS
REPEATER
FINAL CONFIGURATION
CURRENT CONFIGURATION
Easy conversion process
Use one existing loop connection that has a common path as the trunk for the repeater.
IP Router switches with repeaters for common leg runs
1 Assign VLAN jurisdictions to switch/router and repeater locations.2 Create schedule of IPC IP address changes that will conform to VLAN structure and submit to GWorld Applications Administrators.3 Create schedule of loops whose fiber cabling will be re-used for repeater connectivity. (See attached drawings)4 Submit list of backup and normal power requirements and their locations to Ron Schreiber for approval and comment.5 Install repeaters in racks of respective buildings.6 Submit conversion schedule to GWorld Applications Administrators for approval.7 Convert loops:
Document and confirm repeater fiber path for one repeater and stage parts for conversion. Disconnect fiber of loop to be re-used, attach repeater, re-attach loop and check for proper operation. Patch in remaining loops to be connected through repeater and check. Remove all parts of obsoleted loop infrastructure. Submit documentation of current and retired infrastructure to Ron Schreiber.
GWORLD MESHED NETWORKREPEATER INSTALLATION STEP
BJK 12/07/05
DRAFT
SYSTEM/BUSINESS CONTINUANCE SYSTEM/BUSINESS CONTINUANCE DOCUMENTATIONDOCUMENTATION
STRATEGIES AND PITFALLS STRATEGIES AND PITFALLS
SYSTEM/BUSINESS CONTINUANCE DOCUMENTATIONSTRATEGIES AND PITFALLS
When adding, giving back or fixing circuits, documentation can save you time and money.
Accounting Work description Diagnostic aid
SYSTEM/BUSINESS CONTINUANCE DOCUMENTATIONSTRATEGIES AND PITFALLS
For disaster recovery, documentation could make a huge difference in the time it takes to get your system back into a working condition
SYSTEM/BUSINESS CONTINUANCE DOCUMENTATIONSTRATEGIES AND PITFALLS
For justifying decisions or defending decisions,
documentation can really make stating your case a lot easier.
1 Assign VLAN jurisdictions to switch/router and repeater locations.2 Create schedule of IPC IP address changes that will conform to VLAN structure and submit to GWorld Applications Administrators.3 Create schedule of loops whose fiber cabling will be re-used for repeater connectivity. (See attached drawings)4 Submit list of backup and normal power requirements and their locations to Ron Schreiber for approval and comment.5 Install repeaters in racks of respective buildings.6 Submit conversion schedule to GWorld Applications Administrators for approval.7 Convert loops:
Document and confirm repeater fiber path for one repeater and stage parts for conversion. Disconnect fiber of loop to be re-used, attach repeater, re-attach loop and check for proper operation. Patch in remaining loops to be connected through repeater and check. Remove all parts of obsoleted loop infrastructure. Submit documentation of current and retired infrastructure to Ron Schreiber.
GWORLD MESHED NETWORKREPEATER INSTALLATION STEP
BJK 12/07/05
DRAFT
SYSTEM/BUSINESS CONTINUANCE DOCUMENTATIONSTRATEGIES AND PITFALLS
DISADVANTAGES
•Time consuming to create and maintain
SYSTEM/BUSINESS CONTINUANCE DOCUMENTATIONSTRATEGIES AND PITFALLS
Three types of drawing documentation used by GW
MSWORD Drawings very portable to just
about anyone. Not widely used for drawing. Easy to use but somewhat
methods are somewhat arcane.
Exportable into Visio (some objects translate better than others).
Moderate learning curve.
SYSTEM/BUSINESS CONTINUANCE DOCUMENTATIONSTRATEGIES AND PITFALLS
Three types of drawing documentation used by GW
MSVISIO Requires that you purchase
Visio Not everyone has it (not as
portable) Focus of software is drawing
(more features). Moderate learning curve.
SYSTEM/BUSINESS CONTINUANCE DOCUMENTATIONSTRATEGIES AND PITFALLS
Three types of drawing documentation used by GW
AUTOCAD Drawings portable only to
other Autocad
users or through viewers with varying editing features.
Very expensive Big learning curve. Used by many
Architecture/engineering firms
SUMMARYSUMMARY
SUMMARY
A few years ago we had a system that
could not be moved had all sorts of special
connections was understood by very
few people
SUMMARY
These steps we have taken have made it so that, with a little preparation, we can put critical system devices in a number of places.
SUMMARY
Documentation has given us recognition as a team that can play well with others.
1 Assign VLAN jurisdictions to switch/router and repeater locations.2 Create schedule of IPC IP address changes that will conform to VLAN structure and submit to GWorld Applications Administrators.3 Create schedule of loops whose fiber cabling will be re-used for repeater connectivity. (See attached drawings)4 Submit list of backup and normal power requirements and their locations to Ron Schreiber for approval and comment.5 Install repeaters in racks of respective buildings.6 Submit conversion schedule to GWorld Applications Administrators for approval.7 Convert loops:
Document and confirm repeater fiber path for one repeater and stage parts for conversion. Disconnect fiber of loop to be re-used, attach repeater, re-attach loop and check for proper operation. Patch in remaining loops to be connected through repeater and check. Remove all parts of obsoleted loop infrastructure. Submit documentation of current and retired infrastructure to Ron Schreiber.
GWORLD MESHED NETWORKREPEATER INSTALLATION STEP
BJK 12/07/05
DRAFT
SUMMARY
We cut down on down time for several kinds of transitions.
FIREWALLDATACARD
UNIPRINTNET SWITCH
UNCOND.
ANALOG
QUICK DISCONNECT CABLE TO INFRASTRUCTURE
F I B E R
- -----25 PR.---- LOCAL COPPER COPPER
(AMPHENOL)
SUMMARY
We are poised to take advantage of many of the features that will come with the Universal Edition.
NP
ENDEND
FUNNY CLOTHESFUNNY CLOTHES
GWORLD DIR. GWORLD DIR. KEN KEN
PIMENTELPIMENTEL
GWORLD ASST. GWORLD ASST. DIR. DIR.
JAMES WHITEJAMES WHITE
Thank You!Suzanne Werner
Bio: Has been working at The George Washington University for three years as the Senior Applications Administrator for the GWorld Card program. She has a BA in Computer Science from Rutgers University and
has over 8+ years experience working with various Unix systems. She is a New Jersey native with a passion for writing and playing her own music and has traveled across the country playing in several bands.
Steve Nichols202-994-0421
[email protected]: Has been working at The George Washington University for three years as an Applications Administrator for the GWorld Card program. An alumnus of the Virginia Military Institute, he has over 8+ years working in
various IT fields for both the government and private sector. A Virginia native, he enjoys the outdoors and is a die-hard Washington Redskins fan.
Brendan Kelly202-994-1711
[email protected]: Has been working at The George Washington University for seven years in various technical positions for the GWorld Card program. He attended Northeastern University’s Electrical Engineering program and has over 20 years experience working with various device control and computer systems. He is a Connecticut native and
spent 15 years in and around Boston. He enjoys skiing and starting projects.