SCGlobal Nanocruise

Technical Agenda
July 17 & 19, 2001

Objective:

July 17 - This nanocruise will 1) conduct audio leveling for the network, 2) run Distributed PowerPoint
July 19 - This nanocruise will 1) conduct audio leveling for the network and for the telco, 2) if time allows will run DPPT

When:

July 17
8:00-10:00 AM Mountain
9:00-11:00 AM Central
1400-1600 UTC

July 19
8:00-10:00 AM Mountain
9:00-11:00 AM Central
1400-1600 UTC

Where:

Virtual Venue: Talus
Audio IP address, port, and ttl: 233.54.207.8/17008 ttl 127
Video IP address, port, and ttl: 233.54.207.9/17008 ttl 127

Distributed PowerPoint

Test slides may be downloaded from:
http://www.ahpcc.unm.edu/Computing/ag/nano7172001.ppt

DPPT server will be:
sagndisplay.ahpcc.unm.edu

Telco Bridge:

The Albuquerque High Performance Computing Center will serve as the telco bridge.

Telco Conference Number:

Please connect to both RAT and telco for backup.
1-877-711-3694, code 200244

Agenda:

The agenda is short, but the troubleshooting process usually takes some time. Please double check that your presets in Gentner are 1) Bridge, 2) Telco only, 3) Network only

Instructions:

1. Activate AG nodes as normal
2. Meet in Talus Virtual Venue as usual, but double check that your node’s Gentner is using Preset 3 for network audio and Preset 2 for telco.
3. Run through role call which includes: audio, video, and MUD acknowledgements

-Role call will be in alphabetical order

4. Download test dppt slides from:
5. On Display Station, edit config.bat to make server = sagndisplay.ahpcc.unm.edu
6. On Display Station, open a command prompt
7. In command prompt, change directory to dppt folder
8. In command prompt, client <full path to dppt>/nano7172001.ppt then WAIT FOR SERVER AND MASTER TO BE ACTIVATED. Announcement will be in the MUD.
9. Watch for slide changes – they will be announced in the MUD.
10. Use MUD to report any failures to receive slide changes.

Troubleshooting - First Draft:

This is a first draft. Email me with improvements: jshuckra@ahpcc.unm.edu

Troubleshooting is a process. It is a systematic analysis of facts. It uses empirical facts rather than "gut" feelings. Use the following troubleshooting guide as a process of diagnosing rather than as solving symptoms. This brief description hopes to get Access Grid operators thinking in terms of a system rather than a symptom. The scientific method is a systematic process of examining facts, deriving empirical realities, and solving problems. It keeps the technical support personnel focused on a process.

Step 1:
LISTEN to what people are telling you. They have valuable clues.

Step 2:
ASK people what they feel might be the problem. You might be surprised at their accuracy.

Step 3:
RECREATE the problem. This indicates the general equipment involved with the problem. You can focus on the equipment surrounding the problem.

Step 4:
ISOLATE the problem. Reset each piece of equipment back to default. One by one, change their settings to the desired state. You have most likely found the problem when you recreate the symptom.

Step 5:
CORRECT the problem.

Step 6:
NOTIFY the user and your boss that the problem is fixed.

Step 7:
DOCUMENT the problem in the operators log book.

Replication

The problem must be replicable in order to be scientifically diagnosed.

Isolation

Following the pathway of the respective problem, test one variable at a time; treat everything else as a constant. For example, the pathway of an audio problem would be microphones, echo cancellation, rat, line leveller, network, speakers.

Frequently Spotted Problems