Network Operations Technical Assistance Center Chapter 8, IOM Basic Training February 2006
1
Technical Assistance Center, or TAC TAC Mission Statement The TAC is committed to providing world class service and support that has unmatched value to our growing global customer base. We are dedicated to excellence and strive to make every customer a positive, reference-able account.
2
Technical Assistance Center TAC Hours of Operations/Contact Information The TAC is manned 24 hours, 7 Days a week. TAC Phone Number is 703 648-8151.
• •
The Phone line is answered 7 X 24. Voicemail monitored regularly
Instant Messenger is also used to communicate with customers and fellow employees.
3
TAC Roles and Responsibilities TAC Roles The TAC is the primary customer interface for any issues that come up after the service has been installed.
•
The TAC is responsible for coordinating resources required to address customer service issues.
•
TAC is responsible for issuing RMA’s to customers.
We coordinate software release roll-out with customers and Engineering. We provide customers with access to a variety of reference documentation on the TAC Web page. Each customer is provided a user name and login for the TAC Web page. Link:
tac.idirect.net
4
TAC Roles and Responsibilities TAC Web Page – Main Screen
5
TAC Roles and Responsibilities TAC Web Page – Software Releases
Extra emphasis on new releases and/or documents
6
TAC Roles and Responsibilities TAC Web Page
Network Operator Documentation broken up into categories
7
TAC Remote Access Remote Access Methods we use to support remote access
• • • •
GRE Tunnel VPN Client (Cisco, Pix Firewall) PC Anywhere through internet PC Anywhere through dial-up connection
Standardizing going forward
• • • •
VPN Client Preferred (If customer can support) GRE Tunnel PC Anywhere through internet PC Anywhere through dial-up connection
Issues
• • •
Ensure secure access for customers Keep Networks Isolated Greatly improves ability to provide efficient and effective support
8
Hub Equipment Fail Over Procedures Fail Over Procedures Protocol Processor Fail Over Procedure Obsolete PP Auto-Redundancy Now Fully Supported
Hub Line Card Fail Over Procedure Obsolete HLC Auto-Redundancy Now Fully Supported
NMS Server Fail Over Procedure Still Required No Auto Redundancy Today for NMS; Remains Manual Switchover
9
Network Operations Advanced Network Operations and Troubleshooting Tools
•
Putty Free software for implementing Telnet and SSH sessions with NMS and PP http://www.chiark.greenend.org.uk/~sgtatham/putty/
•
WinSCP Free software used to move files from Windows to Linux Servers http://winscp.sourceforge.net/eng/
•
Ethereal Free network protocol analyzer for Unix and Windows
http://www.ethereal.com/
•
UDPBlast - An iDirect SW tool used to test UDP traffic throughput & jitter
Upgrades
• • •
Software Upgrade Process Flow Upgrade Logical Sequence Problems that happen during upgrades
Commissioning Process
10
Network Operations Advanced Network Operations and Troubleshooting System Performance Monitoring
• • •
Traffic Stats Frequency Offset Symbol Offset
Trouble Shooting Tips
•
Spectrum Analyzer Set-Up for Zero Span
•
•
How to trouble shoot Viruses tcpdump
•
•
Zero Span, RBW 300 KHz, VBW 1 KHz, Sweep Time 200 Ms, 2 or 5 dB per Div
http://www.tcpdump.org/tcpdump_man.html
Remote Diagnostics Status of LED on the NetModem Screen shot of Boot Process Tech Note Remote Diagnostics NetModem Help listing 11
Inter-Facility Link (IFL) Coaxial Cabling
Maximum IFL cable length matrix
MAXIMUM IFL CABLE LENGTHS
1W NJRC Ku-Band 2W NJRC Ku-Band 4W NJRC Ku-Band
Comscope 5782 RG-6 Max Feet Meters 302.9 92.3 302.9 92.3 251.4 76.6
Comscope 5902 RG-11 Max Feet Meters 514.1 156.7 514.1 156.7 514.1 156.7
2W NJRC C-Band 5W NJRC C-Band 5W NJRC C-Band
302.9 273.2 279.0
514.1 514.1 514.1
Radio
92.3 83.3 85.1
156.7 156.7 156.7
Limited By RF RF DC RF DC DC
12
II+ Hub Line Card LED Indicators Label
LED State OFF
Purpose No M&C connection (or Hub Line Card is powered off if all 4 LEDs are off)
NET
Solid Green
M&C link established with Hub Line Card (from PC/laptop via LAN port connection)
OFF
Hub Line Card is powered off. (Note: HLC slot power controlled via NMS)
Solid Green
Booting cycle, or Hub Line Card is functioning properly.
Solid Red
Hub Line Card has detected a hardware fault or Application SW cannot be loaded.
STATUS
OFF
Modulator is disabled – (normal Rx only mode or Hub Line Card powered off if all 4 LEDs are off)
TX
Solid Green OFF
Hub Line Card modulator enabled. Demodulator is disabled. (or Hub Line Card is powered off if all 4 LEDs are off)
RX
Solid Yellow
Demodulator is enabled & configured as a Tx/Rx or Rx only (off also for ‘Standby’ mode)
Table 1 – II+ Hub Line Cards LED Indicators 13
Troubleshooting Using II+ Rear Panel LED Indicators
Label
Purpose
LED State OFF
Not ‘Acquired’ by the Network (or NMII+ is powered off if all 4 LEDs are off)
NET
Solid Green OFF STATUS
Solid Green
Acquired as part of the operational network NetModem is powered off Booting cycle, or NetModem is functioning properly
Solid Red
Self test sequence has detected a hardware fault or boot-up software loading error
OFF
NetModem modulator is disabled (or NMII+ is powered off if all 4 LEDs are off)
TX
Solid Green OFF RX
NetModem modulator enabled, (may ‘blink’ during initial acquisition phase) NetModem is powered off
Solid Yellow
Demodulator is enabled, but has not achieved TDM Frame Lock
Solid Green
Demodulator is enabled, and has achieved TDM Frame Lock on the outbound
Table 3 – NetModem Rear Panel LED Indicators 14
Troubleshooting Using II+ Front Panel LED Indicators Label
LED State OFF
POWER
Solid Green OFF
NETWORK
Blinking Yellow Solid Yellow Blinking Green Solid Green OFF
Purpose NetModem is powered off; no power applied NetModem has power applied ‘POWER’ LED on & boot-up sequence completed, indicates hardware failure Demodulator enabled, no outbound carrier detected (Rear RX LED Yellow) Demod. enabled, NetModem has acquired TDM Frame Lock (Rear RX Green) Modulator enabled, attempting to ‘acquire’ the network (Rear TX Green) NetModem has acquired the network, (Rear NET LED/all 4 rear LEDs Green) Normal operation is ‘off’, no problem detected
TEST
Blinking Yellow
Indicates a detected hardware failure during boot up, (Rear Status LED Red)
Table 4 – NetModem Front Panel LED Indicators
15
II+ Power LED: Not Illuminated ‘Power’ LED not illuminated Indication: Power not applied
Possible Cause(s): 1. External Power Supply (EPS) has no output 2. or, AC power cord not plugged in
Corrective Action(s): 1. Connect/plug in/replace EPS 2. Connect AC power cord
NOTE: The remaining discussion items assume a Solid Green Power LED in all cases 16
II+ Status LED: Solid Red ‘Status’ LED not illuminated, or is displayed as solid red Indication:
Red
Remote failed during hardware boot-up/FPGA load
Possible Cause: Corrupted Image(s) or Operating System problem
Corrective Action(s): Perform any or all of the following actions individually a) Reset remote II+ & observe boot sequence in console port session b) Reload Image(s) or ‘Options’ file as necessary c) Remove & Replace remote II+ ; Obtain RMA and return for repair/replacement if problem fails to clear
NOTE: The remaining discussion items assume a Solid Green Status LED in all cases 17
Network & RX LED: Flashing Yellow #1 ‘Network’ LED flashing Yellow RX LED solid Yellow Indication: Remote has not achieved TDM frame lock on the hub outbound, or downstream carrier Possible Cause(s)–Hub Side Failures:
Yellow
Green
Yellow
Hub outbound/downstream carrier down/not being transmitted a) Hub/teleport malfunction or TX power lower than required b) Transponder/satellite interference from adjacent carrier c) Rain fade at the hub or remote site location
Corrective Action(s): Coordinate with hub/teleport personnel & accomplish the following checks: a) Confirm hub/teleport equipment operational, and transmit level is correct b) Verify teleport sees no satellite interference (adjacent carriers, cross-pol, etc.) c) Verify weather is clear and/or wait until rain subsides and recheck 18
Network and RX LED: Flashing Yellow #2 ‘Network’ LED flashing Yellow RX LED also Flashing Yellow Indication: Remote has not achieved TDM frame lock on the hub outbound, or downstream carrier Possible Cause(s) – Remote Side Failures:
Yellow
Green
Yellow
VSAT antenna is not pointed/peaked properly on the satellite a) b) c) d)
Antenna has physically moved, or has never been peaked properly Missing +18 VDC from “RX In” port (power to LNB) Problem with receive IFL cable/connectors Incorrect or incompatible ‘Options’ file loaded
Corrective Action(s): Verify antenna pointing and repoint or repeak as necessary a) Physically repoint/repeak VSAT antenna b) Check for +18 VDC on “RX In” port on II+ and/or LNB end of IFL receive cable. (Do not damage power supply by shorting out center conductor). c) Verify/redo IFL cable connector(s). Ensure RX (not TX) cable is connected between “RX In” port on II+ and LNB (roll cables) d) Generate and apply known correct, or updated ‘Options’ file 19
Network and RX LED: Flashing Yellow #3 ‘Network’ LED flashing Yellow Yellow RX LED Flashing Yellow Indication: Remote has not achieved TDM frame lock on hub Green Yellow outbound, or downstream carrier Possible Cause(s) – Remote Side, RX Path Failure: Remote VSAT/LNB hardware and/or related configuration incorrect a) b) c) d)
Improperly installed LNB (waveguide port 90 degrees ‘out’ from feed assembly) Incorrect LNB installed; (higher stability PLL req’d for outbound =< 512 kbps) Correct LNB selected, but 10 MHz reference not enabled (some PLLs required) ‘Receive Stability’ parameter incorrect (used for calc of RX ‘Acquisition Range’)
Corrective Action(s): Verify VSAT/LNB hardware and/or related configuration parameters a) b) c) d)
Examine/correct LNB physical attachment to feed assembly Verify correct LNB requirement and replace, if necessary, DRO with PLL LNB Enable 10 MHz reference frequency, if required, for PLL LNB (some models) Enter correct LNB ‘Stability’ value in iBuilder, in MHz 20
Network LED: Solid Yellow RX LED: Solid Green ‘Network’ LED solid Yellow RX LED solid green Indication: Remote has achieved TDM frame lock on the downstream carrier but,
Yellow
Green
Green
a) Remote is NOT attempting to ‘acquire’ the network (TX LED never turns on). b) Considered normal operation if remote not configured as ‘Active’ in iBuilder
Possible Cause: Remote is not ‘Active’ in iBuilder, but should be Corrective Action: ‘Activate’ in iBuilder and/or ‘Apply Configuration Changes’ in iBuilder at the Network Level in the tree.
21
Network LED: Flashing Yellow/Green RX and TX LEDs: Solid Green ‘Network’ LED flashing (alternately Yellow & Green), but never changes The TX & RX LEDs are both illuminated Solid Green Indication:
Green/Yellow
Green Green Green
Remote has achieved TDM frame lock on the hub outbound, or downstream carrier and is attempting to ‘acquire’ (tune) to the network Considered normal unless excessive amount of time has passed & remote never acquires the network (LED state never changes)
Possible Cause(s): a) b) c) d)
Acquisition time slot congested; many remotes attempting may delay acquisition process Initial Frame Start Delay (FSD) value incorrectly calc’d ‘Mobile’ remote has not received proper GEO location input (GPS/manual) Tx power not sufficient/too high (remote ‘Initial Tx Power’ set too low/too high)
Corrective Action(s): a) b) c) d)
Observe, if remote fails to acquire (~3 min.), continue with remaining ‘Possible Cause’ items Verify iBuilder has correct ‘GEO Location’ coordinates for a fixed remote Connect GPS receiver to console port, or command line entry for latitude/longitude and hemispheres Manipulate transmit power as required & in controlled steps while observing acquisition process 22
Network LED: Flashing Yellow/Green RX and TX LEDs: Solid Green ‘Network’ LED flashing alternately Yellow & Green, but never changes The TX & RX LEDs are both illuminated Solid Green Indication:
Green/Yellow
Green Green Green
Remote has achieved TDM frame lock on the hub outbound, or downstream carrier and is attempting to ‘acquire’ (tune) to the network Considered normal unless an excessive amount of time has passed and the remote never acquires the network (LED state never changes)
Possible Cause(s): a) b) c) d) e)
Tx IFL not connected properly or connector/cable defective Missing +24 VDC from ‘TX Out’ port on rear of iNFINITI (power to BUC) Missing 10 MHz reference from II/II+ , (from ‘TX Out’ port also) Defective BUC Defective II/II+ modulator
Corrective Action(s): a) b) c) d) e)
Verify/redo TX IFL cable connector and/or TX and RX IFL cable is connected properly (roll cables) Check +24 VDC on ‘TX Out’ port and/or at BUC end of cable. If missing, check/replace External Power Supply (EPS). Verify 10 MHz option enabled for BUC configuration in iBuilder, if required Remove & Replace BUC; Obtain RMA and return for repair/replacement R & R II/II+ ; Obtain RMA and return for repair/replacement 23
Summary – II+ Remote Front Panel LED ‘Boot-Up’ thru ‘In Network’ Sequence Green
All 4 Green
(Front Panel II+)
Power/Status LEDs Solid Green All Rear Panel LEDs Solid Green (Remote II+ ‘In Network’) RX, TX Solid Green, Net Off RX Solid Green, TX, Net Off RX solid Yellow, TX, Net Off (remote II+ just after boot-up) (Rear Panel II+)
24
II+ ‘Boot-Up’ Sequence # 1 NetModem II+ Console Port Output Sequences, iDS v6.0.6 NOTE: ***
Conventions used in this document:
Å REMARKS - IN CAPS FOR DISPLAYED ENTRIES; NOT PART OF OUTPUT SEQUENCES SHOWN LABEL OF SPECIFIC TOPIC *** (ALSO NOT PART OF OUTPUT SEQUENCES) ***
PROMPT AFTER LOCAL/SERIAL 'admin' LOGIN
***
[RMT:5005] admin@serial > *** [RMT:5005] admin@serial > reset RST: Modem reset by serial
SOFT 'reset' CONSOLE COMMAND ISSUED *** Å SHOWS BOARD TYPE, BOARD S/N & ‘admin’ LOCAL LOGIN Å ‘reset' COMMAND ISSUED AT LOCAL CONSOLE PORT Å 'reset' COMMAND PROCESS INITIATED
*** 'reset', (or POWER CYCLE REBOOT) PROCESS FULLY OPERATIONAL 'REBOOT' *** Net Modem II Multi-Platform Bootloader version 2.0.0 Å BEGINS BY LOADING BOOTLOADER FILE Copyright (c) 2000,2001,2002 by iDirect, Inc. Dram test... Å SELF TEST ABORT FOR 'BOOTLOADER’ Hit to abort test % complete 0 25 50 75 100 Dram test completed successfully Å TEST COMPLETES; BOOTLOADER TAKES OVER Copying boot monitor code to ram....completed The bootloader reserved flash area is 0x80000 bytes The bootloader size is 0x6F3DC bytes Å THEN A PAUSE IN THE PROCESS AS . . . Retrieving application image from flash....successful. Å 'APPLICATION'IMAGE RETRIEVED (DECOMPRESSED) Application V6.0.6 is 1675128 bytes to be loaded at 0x01000000. Å CURRENT IMAGE VERSION REPORTED Copying application to RAM and starting..... Å COPIES TO RAM TO GO 'OPERATIONAL' NetModem Boot Monitor Å BOOT UP PROCESS CONTINUES ConsoleSessionMgr started... NetModem Model Type/Serial Number: II+.5005 Å MODEL TYPE AND SERIAL NUMBER REPORTED Loaded Modem Options... Å OPTIONS FILE LOADED FROM FLASH TO RAM Initializing Event Handling... Determining Modem Type: Remote Å DETERMINES OPTIONS FILE TYPE Initializing Hardware... (Continued on next page following)
25
II+ ‘Boot-Up’ Sequence # 2 Loading DQT FPGA ... 2plus-V106 Successfully loaded Å LOADS FPGA IMAGES; ALL SHOW SUCCESS Loading RX1 FPGA (SCPC) ... 2plus-V408 Successfully loaded Loading RX2 FPGA (SCPC) ... 2plus-V413 Successfully loaded Loading RX Lookup Table (SCPC) ... 2plus-V003 Successfully loaded Loading TX FPGA (TDMA) ... 2plus-V502 Successfully loaded SUCCESS: TX synthesizer locked Å 'TX synthesizer' SHOULD SHOW LOCK . . . SUCCESS: TX synthesizer locked Å FIRST ATTEMPT FAILURE OKAY IF LOCKED HERE Acquisition period Calculated: 1 Set to 10 Initializing HIFN... OK Å ENABLES 3DES ENCRYPTION CHIPSET Initializing RNG... OK Initializing iDirect Signature Verifier... ************************************* *** WARNING: Using Development only RSA Key! Starting StackManager-Thread... Power UCP is ON Å CONFIRMS UCP PROCESS ACTIVE Initial Tx Power is -8.00 Å 'INITIAL TX POWER' FROM OPTIONS FILE Demand/Rate: Frame Length = 124 Å OPTIONS FILE CONFIGURED FRAME LENGTH Receiver enabled ... Å DEMOD ENABLED Starting NMS-Thread... Starting ServiceMonitor-Thread... Starting NameServer-Thread... Starting DownloadMonitor-Thread... Starting ConsoleServer ... Enabled ConsoleServer... Starting Services... Starting Idle-Thread... Modem Ready
Å BOOT-UP COMPLETED; READY FOR TRAFFIC
Enabled ConsoleServer...
26
II+ Acquired Lock Sequence II+ Console once TDM Frame Lock achieved Acquired RXer TDM frame lock Å DEMOD ACHIEVED 'TDM FRAME LOCK' ON DOWNSTREAM CXR STP: Frame Length = 124 Timeplan Debug Param Address = 0x1199560 t:9485 Remote Received First Timeplan Å TIME PLAN PROVIDED TO REMOTE HDLC Address Updated to 8, CompressID to 7 ************* Transmitter On ************** Å MODULATOR ENABLED TxFPGA Scram: On TxBaseBandCfg: 0xD7 TxControlReg: 0x4400128f ******************************************* FLL Initial Value 0x8ed, Next Value 0x8ef Adjusted Value 0x969, TimeDiff 1372 at 16634 Initial Rx_Freq 1410000000 Actual Synth Freq 1406000000 Offset -27 Tuning Error 0 Rx Frequency Adjusted to 1409999973 Actual Synth Freq 1405666666 New Tuning err -333307 WARNING: Lost RXer lock Å CONTINUES FINE TUNE PROCESS Acquired RXer TDM frame lock Ethernet Link supports FULL duplex LAN-Link established Å LAN PORT ENABLED Calculated Hub FSD is 44495 Å FSD CALCULATION REPORTED ACQ!: SO( +4), FO( -7), PO( -2.0) <000082.426> Å UCP SWEEP COMMAND TCP Connection successful from addr: 192.168.0.100, assigned socket: 7 Å CONNECTION FROM NMS SERVER TCP Connection terminated on socket : 7 Å VALIDATES REMOTES OPTIONS FILE WITH NMS REMOTE HELLO Å INDICATES REMOTE ABLE TO NOW PASS TRAFFIC Username: Å 'ENTER' DEPRESSED REQUESTING LOGIN Username: admin Å 'admin' USERNAME & PASSWORD PROVIDED Password: ******* Å DEFAULT IS iDirect (IDS V6.0)
[RMT:5005] admin@serial >
*** SOFT 'reset' CONSOLE COMMAND ISSUED *** Å PROMPT SHOWS BOARD TYPE (RMT/HLC), BOARD SERIAL NUMBER & 'admin' LOGIN
27
II+ Bootloader Recovery Mode II+ Console reboot to Bootloader Recovery Prompt
[RMT:5005] admin@serial > reset RST: Modem reset by serial
*** SOFT 'reset' CONSOLE Å PROMPT SHOWS BOARD TYPE Å Å
*** SOFT 'reset', (OR POWER CYCLE REBOOT) Net Modem II Multi-Platform Bootloader version 2.0.0 Copyright (c) 2000,2001,2002 by iDirect, Inc. Dram test... Hit to abort test % complete 0 25 50 75 100 Dram test aborted Copying boot monitor code to ram....completed The bootloader reserved flash area is 0x80000 byte The bootloader size is 0x6F3DC bytes NetModem Boot Monitor Bootloader 2.0.0> Ethernet link: 100 Mbps full duplex Bootloader 2.0.0>
COMMAND ISSUED *** (RMT/HLC), BOARD SERIAL NUMBER & 'admin' LOGIN 'reset' COMMAND ISSUED AT CONSOLE PORT 'reset' COMMAND PROCESS INITIATED
REBOOT TO 'BOOTLOADER' PROMPT RECORDED *** Å BEGINS BY LOADING BOOTLOADER FILE Å 'DRAM' TEST (ABORT FOR 'BOOTLOADER') Å 'SPACEBAR' PRESSED TO ABORT DRAM TEST Å TEST ABORTS/BOOTLOADER LOADED INTO RAM Å BOOT-UP SEQUENCE HALTS WITH 'BOOTLOADER' LOAD Å 'BOOTLOADER' PROMPT; LAN PORT ENABLED
28
iNFINITI Hub Line Card LEDs Label
Power LED
LED State
Purpose
Modulator (M1) TX LED
OFF
Power is not being provided via chassis slot. Modify-Chassis to enable power to slot.
Solid Green
Hub Line Card (HLC) is receiving power from the installed chassis slot.
OFF
Hub Line Card is powered off. (Note: HLC slot power controlled via NMS, see above)
Solid Green
Booting cycle, or HLC is functioning properly; may indicate ‘Standby’ if TX off.
POWER Demodulator (D1) Status LED
STATUS
Solid Red OFF TX
Solid Green
iNFINITI
TM
HLC
Hub Line Card has detected a hardware fault or Application SW cannot be loaded properly. Modulator is disabled – (normal Rx only mode or Hub Line Card powered off if all 4 LEDs are off) Hub Line Card modulator enabled.
Table 2 – iNFINITI Hub Line Cards LED Indicators
29
iNFINITI Series 3000, 5000 & 7000 Troubleshooting Using Front Panel LEDs
Table 5 – iNFINITI Front Panel LED Indicators
LED Status Indicators
NET LED will continue flashing Yellow until the remote achieves TDM Frame lock on the Downstream Carrier and the modulator is enabled
30
iNFINITI Series 3000, 5000 & 7000 Troubleshooting Using Front Panel LEDs
FLASHING
31
iNFINITI Power LED: Not Illuminated ‘Power’ LED not illuminated Indication:
*
Power not applied
Possible Cause(s): 1. External Power Supply (EPS) has no output 2. or, AC power cord not plugged in
Corrective Action(s): 1. Connect/plug in/replace EPS 2. Connect AC power cord
NOTE: The remaining discussion items assume a Solid Green Power LED in all cases * Series 3000 shown; analysis applies to Series 5000 & 7000 as well throughout 32
iNFINITI Status LED: Solid Red ‘Status’ LED not illuminated, or is displayed as solid red Indication:
Red
iNFINITI failed during hardware boot-up/FPGA load
Possible Cause: Corrupted Image(s) or Operating System problem
Corrective Action(s): Perform any or all of the following actions individually a) Reset iNFINITI & observe boot sequence in console port session b) Reload Image(s) or ‘Options’ file as necessary c) Remove & Replace iNFINITI ; Obtain RMA and return for repair/replacement if problem fails to clear
NOTE: The remaining discussion items assume a Solid Green Status LED in all cases 33
Network and RX LED: Flashing Yellow #1 ‘Network’ LED flashing Yellow RX LED Flashing Yellow Indication: Yellow iNFINITI has not achieved TDM frame lock on the hub outbound, or downstream carrier Possible Cause(s) – Hub Side Failures:
Yellow
Hub outbound/downstream carrier down/not being transmitted a) Hub/teleport malfunction or TX power lower than required b) Transponder/satellite interference from adjacent carrier c) Rain fade at the hub or remote site location
Corrective Action(s): Coordinate with hub/teleport personnel & accomplish the following checks: a) Confirm hub/teleport equipment operational, and transmit level is correct b) Verify teleport sees no satellite interference (adjacent carriers, cross-pol, etc.) c) Verify weather is clear and/or wait until rain subsides and recheck 34
Network and RX LED: Flashing Yellow #2 ‘Network’ LED flashing Yellow RX LED also Flashing Yellow Indication: iNFINITI has not achieved Yellow Yellow TDM frame lock on the hub outbound, or downstream carrier Possible Cause(s) – Remote Side Failures: VSAT antenna is not pointed/peaked properly on the satellite a) b) c) d)
Antenna has physically moved, or has never been peaked properly Missing +18 VDC from “RX In” port (power to LNB) Problem with receive IFL cable/connectors Incorrect or incompatible ‘Options’ file loaded
Corrective Action(s):
Verify antenna pointing and repoint or repeak as necessary a) Physically repoint/repeak VSAT antenna b) Check for +18 VDC on “RX In” port on iNFINITI and/or LNB end of IFL receive cable. (Do not damage power supply by shorting out center conductor). c) Verify/redo IFL cable connector(s). Ensure RX (not TX) cable is connected between “RX In” port on iNFINITI and LNB (roll cables) d) Generate and apply known correct, or updated ‘Options’ file 35
Network and RX LED: Flashing Yellow #3 ‘Network’ LED flashing Yellow RX LED Flashing Yellow Indication: iNFINITI has not achieved Yellow Yellow TDM frame lock on hub outbound, or downstream carrier Possible Cause(s) – Remote Side, RX Path Failure: Remote VSAT/LNB hardware and/or related configuration incorrect a) b) c) d)
Improperly installed LNB (waveguide port 90 degrees ‘out’ from feed assembly) Incorrect LNB installed; (higher stability PLL req’d for outbound =< 512 kbps) Correct LNB selected, but 10 MHz reference not enabled (some PLLs required) ‘Receive Stability’ parameter incorrect (used for calc of RX ‘Acquisition Range’)
Corrective Action(s): Verify VSAT/LNB hardware and/or related configuration parameters a) b) c) d)
Examine/correct LNB physical attachment to feed assembly Verify correct LNB requirement and replace, if necessary, DRO with PLL LNB Enable 10 MHz reference frequency, if required, for PLL LNB (some models) Enter correct LNB ‘Stability’ value in iBuilder, in MHz 36
Network LED: Flashing Yellow RX LED: Solid Green ‘Network’ LED flashing Yellow RX LED solid green Indication: iNFINITI has achieved TDM frame lock on the SCPC outbound, or downstream carrier but,
Green
Yellow
a) iNFINITI is NOT attempting to ‘acquire’ the network b) Considered normal operation if remote not configured as ‘Active’ in iBuilder
Possible Cause: iNFINITI is not ‘Active’ in iBuilder, but should be Corrective Action: ‘Activate’ in iBuilder and/or ‘Apply Configuration Changes’ in iBuilder at the Network Level in the tree.
37
Network LED: Flashing Yellow RX and TX LEDs: Solid Green ‘Network’ LED flashing Yellow, but never changes The TX & RX LEDs are both illuminated Solid Green Indication:
Green
Yellow
iNFINITI has achieved TDM frame lock on the hub outbound, or downstream carrier & is attempting to ‘acquire’ (tune) to the network Considered normal unless excessive amount of time has passed & remote never acquires the network (LED state never changes)
Possible Cause(s): a) b) c) d)
Acquisition time slot congested; many remotes attempting may delay acquisition process Initial Frame Start Delay (FSD) value incorrectly calc’d ‘Mobile’ remote has not received proper GEO location input (GPS/manual) Tx power not sufficient/too high (iNFINITI ‘Initial Tx Power’ set too low/too high)
Corrective Action(s): a) b) c) d)
Observe, if iNFINITI fails to acquire (~3 min.), continue with remaining ‘Possible Cause’ items Verify iBuilder has correct ‘GEO Location’ coordinates for a fixed remote Connect GPS receiver to console port, or command line entry for latitude/longitude and hemispheres Manipulate transmit power as required & in controlled steps while observing acquisition process 38
Network LED: Flashing Yellow RX and TX LEDs: Solid Green ‘Network’ LED flashing Yellow The TX & RX LEDs are both illuminated Solid Green Indication:
Green
Yellow
iNFINITI has achieved TDM frame lock on the hub outbound, or downstream carrier & is attempting to ‘acquire’ (tune) to the network Considered normal unless an excessive amount of time has passed and the remote never acquires the network (LED state never changes)
Possible Cause(s): a) b) c) d) e)
Tx IFL not connected properly or connector/cable defective Missing +24 VDC from ‘TX Out’ port on rear of remote (power to BUC) Missing 10 MHz reference from iNFINITI , (from ‘TX Out’ port also) Defective BUC Defective remote modulator
Corrective Action(s):
a) Verify/redo TX IFL cable connector and/or TX and RX IFL cable is connected properly (roll cables) b) Check +24 VDC on ‘TX Out’ port and/or at BUC end of cable. If missing, check/replace External Power Supply (EPS). c) Verify 10 MHz option enabled for BUC configuration in iBuilder, if required d) Remove & Replace BUC; Obtain RMA and return for repair/replacement e) R & R iNFINITI ; Obtain RMA and return for repair/replacement 39
Summary - iNFINITI Front Panel LED ‘Boot-Up’ thru ‘In Network’ Sequence
Green
Green
Power/Status LEDs Solid Green All Front Panel LEDs Solid Green (iNFINITI ‘In Network’) NET LED will continue flashing Yellow until the remote achieves TDM Frame lock on the Downstream Carrier and the modulator is enabled
RX Solid Green, TX Solid Green RX Solid Green, TX Off RX Flashing Yellow, TX Off (iNFINITI just after boot-up) 40
iNFINITI Series* 3000, 5000 & 7000 Troubleshooting Rear Panel LEDs Input Power Indicates the presence of DC power to the remote from the External Power Supply (EPS)
LNB Power Indicates DC Power is being provided to the LNB via the remote’s ‘RX In’ port and the receive IFL cable
BUC Power Indicates DC Power is being provided to the BUC via the remote’s ‘TX Out’ port and the transmit IFL cable *
BUC & LNB Power LEDs may be off due to this remote being configured for use on an IF/Bench Test network (DC power NOT required)
Series 5000 Remote Shown
41
*** Thank You *** 42
