000 - LinkStar - Troubleshooting Guide

LinkStar LinkStar IP LinkStar Troubleshooting Guide
LinkStar Troubleshooting Guide
Purpose:
The purpose of this document is to provide an overview of the ViaSat LinkStar system as a whole and provide
troubleshooting aides for use on the ViaSat LinkStar system.
Scope:
The comments in this guideline are for reference only in order to aide an operator in basic RCST and LinkStar
hub troubleshooting. The comments neither are stated policy nor replace any comments set forth in ViaSat
LinkStar manuals, technical notes, release notes or procedures. Those documents, which might be referenced
below, can be found on the ViaSat Customer Extranet website at http://extranet.viasat.com/vsat.
References:
ViaSat LinkStar manuals, technical notes, release notes or procedures, which can be found on the ViaSat
Customer Extranet website at http://extranet.viasat.com/vsat.
1) LinkStar User Manual

a. Document ID USR00091_A http://extranet.viasat.com/vsat/linkstar/manuals/
2) RCST Installation Guide
a. Document ID ING00076_d http://extranet.viasat.com/vsat/linkstar/guides/
3) LinkStar Software Release notes
a. Dependent on version http://extranet.viasat.com/vsat/linkstar/releasenotes/
4) Sun Server Maintenance Procedure
a. Document ID 1025541_002 http://extranet.viasat.com/vsat/linkstar/procedures/
5) RCST Power alignment in an operational network
6) Upgrading Software in a LinkStar Hub
7) Various Customer Service Bulletins
a. Dependent on Bulletins http://extranet.viasat.com/vsat/linkstar/bulletins/
8) Cisco Ethernet Troubleshooting Guide
a. Web document http://www.cisco.com/warp/public/473/46.html
Contact Information:
ViaSat Network Operations Center http://extranet.viasat.com/vsat/service/noc/
noc-carlsbad@viasat.com (888) 272-7232 or +1-760-476-2600
ViaSat Proprietary 1038741_000 (July 28, 2005
1
Table of Contents – LinkStar Troubleshooting Guide

LINKSTAR TROUBLESHOOTING GUIDE .....................................................................................1
PURPOSE: ..............................................................................................................................................1
SCOPE:....................................................................................................................................................1
REFERENCES: ......................................................................................................................................1
1) LinkStar User Manual................................................................................................................................................ 1
2) RCST Installation Guide ............................................................................................................................................ 1
3) LinkStar Software Release notes ............................................................................................................................... 1
4) Sun Server Maintenance Procedure ........................................................................................................................... 1
5) RCST Power alignment in an operational network.................................................................................................... 1
6) Upgrading Software in a LinkStar Hub...................................................................................................................... 1
7) Various Customer Service Bulletins .......................................................................................................................... 1
8) Cisco Ethernet Troubleshooting Guide ...................................................................................................................... 1
CONTACT INFORMATION: ..............................................................................................................1

ViaSat Network Operations Center ..................................................................................................................................... 1
LINKSTAR HCE (HUB COMMON EQUIPMENT) .........................................................................6

Sun Servers ............................................................................................................................................................. 6
NCC..................................................................................................................................................................................... 6
RNCC .................................................................................................................................................................................. 6
TCP ACC or TCP PEP ........................................................................................................................................................ 6
Policy Based Router ................................................................................................................................................ 6
PBR ..................................................................................................................................................................................... 6
Cisco 3660 PBR .................................................................................................................................................................. 6
Cisco 7206 PBR .................................................................................................................................................................. 6
Cisco Switches ........................................................................................................................................................ 6
Cisco 3550 TX Rack Switch ............................................................................................................................................... 6
Cisco 3550 RX Rack Switch ............................................................................................................................................... 7
RF Equipment ......................................................................................................................................................... 7
GPS...................................................................................................................................................................................... 7
ITDU ................................................................................................................................................................................... 7
GCU..................................................................................................................................................................................... 7
DVB Modulator ................................................................................................................................................................... 7
IP Encapsulation...................................................................................................................................................... 7
IPE....................................................................................................................................................................................... 7
LINKSTAR KNOWLEDGE BASE ARTICLES ................................................................................8
LINKSTAR HUB HARDWARE RELATED ISSUES .......................................................................8
Cisco PBR/Switch Specific Issues .......................................................................................................................... 8
1) Problem symptom: Inconsistent LinkStar hub connectivity issues ............................................................................ 8
2) Problem symptom: Excessively high PBR CPU utilization....................................................................................... 8
Sun Server Specific Issues .................................................................................................................................... 10
1) Problem symptom: NCC/RNCC Handovers............................................................................................................ 10
2) Problem symptom: Sun Server disk space usage increases...................................................................................... 11
3) Problem symptom: NCC/RNCC/TCP PEP SNMP Failures .................................................................................... 11
4) Problem symptom: Other processes on the NCC are running in CPU Real Time mode ......................................... 13
5) Problem symptom: RNCC not running in CPU Real Time mode............................................................................ 13
1038741_000 (July 28, 2005) ViaSat Proprietary
2
6) Problem symptom: TCP PEP not running in CPU Real Time and with CPU Priority............................................. 14
TDU/ITDU Specific Issues ................................................................................................................................... 16
1) Problem symptom: Intermittent ITDU and/or GCU alarms, network failures ......................................................... 16
2) Problem symptom: Solid TDU alarm, LinkStar NMS Console indicates Uplink Chain Failure ............................. 16
3) Problem symptom: Solid ITDU alarm, LinkStar NMS Console indicates Uplink Chain Failure ............................ 16
4) Problem symptom: ITDU ASI Rate change, LinkStar Hub is unstable ................................................................... 17
IPE Specific Issues................................................................................................................................................ 17
1) Problem symptom: IPE Manager Data Rate change, LinkStar Hub is unstable ...................................................... 17
2) Problem symptom: After SMR Software upgrade, LinkStar Hub is unstable.......................................................... 17
Modulator Specific Issues ..................................................................................................................................... 17
1) Problem symptom: Modulator Symbol and/or FEC Rate change, LinkStar Hub is unstable................................... 17
RCST/GCU Specific Issues .................................................................................................................................. 17
1) Problem symptom: RCSTs on a specific GCU are down......................................................................................... 17
LinkStar Process Specific issues ........................................................................................................................... 18
1) Problem symptom: Linkstar Processes do not recover after power failure .............................................................. 18
2) Problem symptom: After an RNCC restart, only a portion of the network recovers ............................................... 19
3) Problem symptom: Linkstar LDAP process not recover after power failure ........................................................... 19
LINKSTAR NETWORK RELATED ISSUES ..................................................................................20

NMS Specific Issues ............................................................................................................................................. 20
1) Problem symptom: LinkStar NMS Satellite Software download fails for one RCST.............................................. 20
2) Problem symptom: LinkStar NMS Satellite Software download not working on the network................................ 20
3) Problem symptom: File Not Available message on LinkStar NMS Active Alarm Viewer ..................................... 20
4) Problem symptom: LinkStar NMS Console is blank ............................................................................................... 21
5) Problem symptom: LinkStar NMS Console BTP Graph not displaying.................................................................. 21
6) Problem symptom: LinkStar NMS Console - Unable to process … message on diagnostic screens....................... 22
7) Problem symptom: Various RCSTs do not gain TX Sync ....................................................................................... 22
8) Problem symptom: Incorrect/inconsistent information in a User Group after a User Group change....................... 22
9) Problem symptom: After upgrading to 1.0.8.14, GCU Specific Static routes fail ................................................... 22
10) Problem symptom: Ability to limit users on the LinkStar NMS Console ........................................................... 23
RNCC Specific Issues ........................................................................................................................................... 24
1) Problem symptom: Static and Multicast Routes are deleted every Saturday night.................................................. 24
2) Problem symptom: Slow RCST bandwidth de-allocation times .............................................................................. 24
TCP PEP Specific Issues....................................................................................................................................... 25
1) Problem symptom: TCP PEP Failures due to Multicast traffic................................................................................ 25
2) Problem symptom: TCP PEP communication failures ............................................................................................ 26
3) Problem symptom: RCSTs are passing intermittent TCP traffic ............................................................................. 26
GCU Specific Issues ............................................................................................................................................. 27
1) Problem symptom: Incorrect TxP(dBm) Readings on GCU tfpr reports ................................................................. 27
2) Problem symptom: Newly added GCU Down Alarm.............................................................................................. 27
IPE Specific Issues................................................................................................................................................ 27
1) Problem symptom: SkyAlarm is showing an Alarm for the IMS Agent.................................................................. 27
2) Problem symptom: SkyAlarm is showing an Alarm for the TS In port................................................................... 27
RCST Specific Issues ............................................................................................................................................ 28
1) Problem symptom: High packet loss seen at the RCSTs ......................................................................................... 28
2) Problem symptom: RCSTs are unable to browse the Internet or pass any TCP traffic............................................ 28
VLAN/VPN Specific Issues.................................................................................................................................. 28
1) Problem symptom: VLAN/VPN requirements/troubleshooting .............................................................................. 28
2) Problem symptom: A newly added VLAN(s) fails to pass traffic ........................................................................... 29
3) Problem symptom: VLAN/VPN fails after new RCST to that VPN Membership is added .................................... 30
4) Problem symptom: Cisco 3660 PBR Memory utilization is high after VRFs are configured.................................. 30

3
5) Problem symptom: VLAN traffic fails with Cisco CEF enabled............................................................................. 31

6) Problem symptom: Intermediate VLAN traffic fails................................................................................................ 31
7) Problem symptom: Management (native) traffic fails beyond the Ethernet interface of a RCST ............................ 31
8) Problem symptom: Unable to configure the Max Data Rate on a specific RCST.................................................... 32
RCST SPECIFIC ISSUES ...................................................................................................................32
1) Problem symptom: Unknown RCST root user password......................................................................................... 32
2) Problem symptom: How to reset the root or guest user passwords on all RCSTs ................................................... 33
3) Problem symptom: RCST Is in TX Sync however not passing traffic..................................................................... 34
4) Problem symptom: RCST Is in TX Sync however passing very little to no traffic ................................................. 34
5) Problem symptom: High packet loss on a specific RCST ........................................................................................ 34
6) Problem symptom: RCST IP Accounting records not being collected .................................................................... 35
7) Problem symptom: RCST unable to gain TX Sync while in Maritime mode .......................................................... 35
8) Problem symptom: ss and prt ipqos RCST commands have different output displays............................................ 35
9) Problem symptom: VPN Membership information remains after RCST is deleted................................................. 35
10) Problem symptom: Traffic fails with MTU greater than 1476 ............................................................................ 36
11) Problem symptom: IP Supernetting is not supported on RCSTs......................................................................... 37
ADDITIONAL TROUBLESHOOTING INFORMATION .............................................................38

LinkStar Users Manual – Appendix B .................................................................................................................. 38
Document ID USR00091_A http://extranet.viasat.com/vsat/linkstar/manuals/............................................................ 38
1) Connecting to devices Page B-1 ................................................................................................................. 38
2) Troubleshooting GCUs Page B-1................................................................................................................ 38
3) Troubleshooting RCSTs Page B-3 .............................................................................................................. 38
a) General Approach Page B-3.................................................................................................................................... 38
b) Troubleshooting Page B-3...................................................................................................................................... 38
c) Local RCST Communications Page B-4.................................................................................................................. 38
d) Network Synchronization Page B-4 ........................................................................................................................ 38
e) All LEDs Off Page B-4 .......................................................................................................................................... 38
f) SAT LED Off Page B-5 ......................................................................................................................................... 38
g) SAT LED Blinking Page B-5 .................................................................................................................................. 38
h) SAT LED Off Page B-4 ......................................................................................................................................... 38
4) Monitoring Hub Link Conditions Page B-7 ................................................................................................. 38
a) GPS/10 MHz Reference Page B-7 .......................................................................................................................... 38
b) DVB Modulator Page B-7 ...................................................................................................................................... 38
c) TDU Page B-8....................................................................................................................................................... 38
d) IPE Page B-8 ......................................................................................................................................................... 38
e) Multiplexer Page B-8 ............................................................................................................................................. 38
f) GCU Page B-8 ...................................................................................................................................................... 38
g) Link Troubleshooting: Outbound Page B-9 ............................................................................................................. 38
h) Link Troubleshooting: Inbound Page B-9................................................................................................................ 38
i) Link Troubleshooting: Outbound Page B-9 ............................................................................................................. 38
j) Link Monitoring Page B-9 ..................................................................................................................................... 38
5) Monitoring Burst Reception Page B-10 ...................................................................................................... 38
6) Redundancy Equipment Page B-11............................................................................................................. 38
a) I/O Link Initial State of LEDs Page B-11................................................................................................................ 38
b) I/O Link Troubleshooting Page B-11...................................................................................................................... 38
7) Terminal Server Page B-12 ........................................................................................................................ 38
8) Modulator Redundancy Switch Page B-12 .................................................................................................. 38
a) Slow Switching Page B-12..................................................................................................................................... 38
b) Installing Configuration File Page B-12 .................................................................................................................. 38

4
9) IP Encapsulator Page B-13 ......................................................................................................................... 38

a) SMR Redundancy Page B-12.................................................................................................................................. 38
10) LDAP Installation Page B-14................................................................................................................. 38
USEFUL COMMANDS .......................................................................................................................39
Cisco Switch troubleshooting commands ............................................................................................................. 39
show int status ................................................................................................................................................................... 39
show int Fa0/X .................................................................................................................................................................. 39
show vlan or show vlan brief............................................................................................................................................. 39
show ver ............................................................................................................................................................................ 39
show controllers ethernet-controller fastEthernet .............................................................................................................. 39
Sun Server Solaris (UNIX) commands ................................................................................................................. 39
prstat .................................................................................................................................................................................. 39
df........................................................................................................................................................................................ 39
netstat................................................................................................................................................................................. 39
ls ........................................................................................................................................................................................ 39
APPENDIX A – CISCO 3660 POLICY BASED ROUTER CONFIGURATION .........................40

APPENDIX B – CISCO 7206 POLICY BASED ROUTER CONFIGURATION .........................42
APPENDIX C – CISCO 3550 TX RACK SWITCH CONFIGURATION .....................................45
APPENDIX D – CISCO 3550 RX RACK SWITCH CONFIGURATION .....................................48

5
LinkStar HCE (Hub Common Equipment)

Sun Servers
NCC
The NCC (Network Control Center) manages the overall control of a LinkStar hub as well as the database of the
LinkStar RCSTs (Return Channel Satellite Terminal). The NCC can manage up to 10 RNCCs (Regional
NCCs), each supporting up to 8,000 RCSTs, for a total of up to 80,000 RCSTs in one LinkStar network.
RNCC
The RNCC manages the bandwidth allocation for the RCSTs in its region. The RNCC also maintains traffic
statistics and accounting records for the entire LinkStar network.
TCP ACC or TCP PEP
The TCP ACC (TCP Accelerator) or TCP PEP (TCP Performance Enhancement Proxy) is provided with every
LinkStar Network to overcome the latency limitations of TCP/IP over satellite links. The TCP PEP runs on a
specially configured workstation which is part of the transmit HCE and connects to the hub gateway router. The
TCP PEP receives eligible TCP packets, and utilizes several industry standard techniques to maximize the use of
outbound and inbound links. This processing increases the throughput of each TCP connection between a server
and a client. In addition, TCP PEP runs its own SNMP manager for monitor and control purposes.
Policy Based Router

PBR
As part of the LinkStar TCP Acceleration system design, a PBR (Policy Based Router) is loaded with a default
policy configuration that establishes interface connectivity and transport protocols to separate TCP packets from
non-TCP packets. In the first part of this acceleration process, TCP packets are forwarded to the Sun
workstation TCP Accelerator. The TCP acceleration software then “PEP”s, or accelerates, the packets using
Comsat Laboratories’ proprietary protocol Performance Enhancement Protocol (PEP), then returns the PEP’ed
packets for transmission over the satellite.
Cisco 3660 PBR
The original LinkStar hubs were previously shipped with a Cisco 3660 PBR as the main routing component of
the hub. Please view Appendix A for the default configuration of the Cisco 3660 PBR.
Cisco 7206 PBR
The current LinkStar hubs are now being shipped with a Cisco 7206 PBR as the main routing component of the
hub. The main reason for doing so is due to the feature rich software developments and enhancements for
customer use, such as the VLAN (Virtual LAN) implementation. For VLAN implementation, the Cisco PBR
needs to be configured with VRFs (VPN routing/forwarding). VRFs are supported on the Cisco 3660 PBR,
however no more than 2 to 3 VRFs should be configured. VRFs on the Cisco 3660 PBR, when configured,
consume a high amount of memory and CPU utilization. Therefore it is recommended to upgrade to the Cisco
7206 PBR. Please view Appendix B for the default configuration of the Cisco 7206 PBR.
Cisco Switches
The LinkStar hub employs the Cisco 3500 XL and 3550 series of switches. The 3500XL Layer 2 switch has
since been phased out by Cisco and was replaced with the 3550 Layer 3 switch. The switches are the main
components that provide the connectivity to all of the LinkStar hub devices.
Cisco 3550 TX Rack Switch
The Cisco 3550 TX (Transmit) Rack Switch provides connectivity to the entire LinkStar hub and it’s
components. Please view Appendix C for the default configuration of the Cisco 3550 TX Rack Switch.

6
Cisco 3550 RX Rack Switch

The Cisco 3550 RX (Receive) Rack Switch provides connectivity for the GCUs (Gateway Channel Unit) and
the return IP traffic to the PBR for proper packet handling and on to the external IP network. Please view
Appendix D for the default configuration of the Cisco 3550 RX Rack Switch.
RF Equipment
GPS
The LinkStar Hub incorporates timing using a high stability GPS (Global Positioning Satellite)-based clock
reference. The GPS receiver supplies a 10MHz clock to the LinkStar Intelligent Timing Distribution Unit
(ITDU). The GPS receiver also provides the clock to the DVB modulator to
ensure stability of the DVB signal.
ITDU
The ITDU generates a Network Clock Reference (NCR) using the Program Clock Reference (PCR) mechanism
and inserts it into the MPEG stream. Under DVB-RCS (Digital Video Broadcast-Return Channel Satellite), the
ITDU assumes an additional responsibility of inserting DVB-RCS tables in the outbound. The RNCC instructs
the ITDU to transmit the tables in the outbound. The ITDU multiplexes tables and the NCR with its DVB-ASI
(DVB-Asynchronous Serial Interface). Optionally, the tables and NCR generated by the ITDU can be
multiplexed with other traffic externally using a DVB multiplexer. In typical configurations, the IP
Encapsulator DVB ASI Out is connected the DVB ASI In of the ITDU.
GCU
The GCU (Gateway Channel Unit) receives and demodulates the inbound TDMA signal, extracting the IP
packets. The ITDU is connected to the GCUs to synchronize the TDMA frames with the NCR.
DVB Modulator
The DVB modulator receives the aggregate DVB stream from the ITDU, modulates it to the 70/140 MHz
Intermediate Frequency (IF), and sends it to the uplink RF chain.
IP Encapsulation
IPE
The PBR has a connection to the outbound link via the IP Encapsulator (IPE). Normal LinkStar hubs are
configured with the SkyStream SMR (Source Media Router) as its IPE device. The IPE receives outbound IP
packets, inserts them into MPEG2-TS packets after performing Multi Protocol Encapsulation (MPE), and
creates an outbound IP over DVB stream. The output of the IPE is provided to the DVB ASI input of the ITDU.

7
LinkStar Knowledge Base Articles

LinkStar Hub Hardware Related Issues
Cisco PBR/Switch Specific Issues
1) Problem symptom: Inconsistent LinkStar hub connectivity issues
Component: Cisco PBR, TX/RX Switches, Sun Servers
Category: Hardware
Software Version: All
Description: Sun servers perform handovers, traffic is lost, and GCUs indicate outages
Problem Resolution: The causes of inconsistent connectivity could be caused by the following
1) Verify that the TX and RX Switch port settings are configured properly
a. Common problems with NCC/RNCC/TCP PEP connectivity and
redundancy issues can be traced to disk usage (listed above) or TX
Switch port settings
2) Each of the ports that a NCC/RNCC/TCP PEP and the SkyStream SMRs
connect to should be configured as Auto Duplex, Auto Speed
a. The only ports that should be configured as Full Duplex, 100 Mbits/s
on the TX Switch are those that are connected directly to the PBR and
the RX Switch trunk ports
b. If there is bandwidth manager placed between the PBR and the TX
Switch (normally port Fa0/16), the bandwidth manager ports should be
configured as Full Duplex, 100 Mbits/s as well
3) Please see the TX and RX Switch configurations listed below as well as the
switch troubleshooting commands, in the Useful Commands area
2) Problem symptom: Excessively high PBR CPU utilization
Component: PBR
Category: Hardware
Description: Network operating, customers complaining of slow service, DNS query
timeouts
Problem Resolution: This might happen due to excessive NAT (Network Address Translation)
Translations on the PBR or an excessively high connection count from users on
the network. This could also be related to a DoS or DDoS (Denial of Service or
Distributed DoS)
1) Check the PBR for excessive NAT translations that might be related to
virus/worm/Trojan traffic
2) Check user connection counts via the Allot NetEnforcer
a. Use the acstat -i command on the Allot NetEnforcer via CLI and log
the output to a text file
b. Place the information into a spread sheet
c. Sort the information by source IP address and attempt to isolate
offenders by looking at the number and/or types of connections by
destination port ID
d. Disable those sites, NAT translations will decrease, PBR CPU
utilization returns to normal
3) Refer to the LinkStar IP Quality of Service (QoS) application note, ViaSat
Document ID APN00019, located at
http://extranet.viasat.com/vsat/linkstar/notes/ for Flow Profile and QoS
implementation

8
4) Implement gateway/edge/border router access-lists to block known exploits

to prevent malware (virus/worm/Trojan) traffic from entering the LinkStar
hub
a. It is best to implement this on the inbound interface of the
gateway/edge/border router from the ISP (Internet Service Provider)
connection to block the traffic prior to traversing the PBR and/or the
TCP PEP
b. Please use this access-list as a guide only, as every LinkStar IP network
address ranges need to be considered, etc prior to implementation.
deny icmp any any redirect
deny ip 127.0.0.0 0.255.255.255 any <--Prevents IP Spoofing of RFC 1918 address ranges
deny ip AA.BB.CC.0 0.0.0.255 any <--Prevents IP Spoofing of RCST address ranges
deny ip DD.EE.FF.0 0.0.0.255 any <--Prevents IP Spoofing of RCST address ranges
deny ip 224.0.0.0 31.255.255.255 any
deny ip host 0.0.0.0 any
deny udp any any eq tftp <-- Part of Microsoft RPC DCOM block
deny udp any any eq 77
deny tcp any any range 135 139 <-- Microsoft RPC DCOM block
deny udp any any range 135 139 <-- Microsoft RPC DCOM block
deny tcp any any eq 445 <-- Microsoft RPC DCOM block
deny udp any any eq 445 <-- Microsoft RPC DCOM block
deny tcp any any eq 707 <-- W32/Nachi.worm/W32/Welchia.worm block
deny udp any any range 995 999 <-- CAN-2003-719,CAN-2004-120 http://cve.mitre.org/cve
deny udp any any range 1025 1027 <-- Microsoft RPC issues block
deny tcp any any range 1433 1434 <-- Microsoft-SQL-Server block
deny udp any any range 1433 1434 <-- Microsoft-SQL-Server/Slammer block
deny tcp any any eq 3128 <-- MyDoom.C / Doomjuice block
deny tcp any any eq 3306 <-- mysql block
deny tcp any any eq 6129 <-- Dameware Remote Admin - possible buffer overflows
deny tcp any any eq 8967 <-- Dabber Worm backdoor
deny udp any any eq 8998 <-- W32.sobig block
deny tcp any any eq 11768 <-- DIPNET trojan backdoor block - MS04-011 exploit
deny tcp any any eq 15118 <-- DIPNET trojan backdoor block - MS04-011 exploit
deny tcp any any eq 20168 <-- W32.HLLW.Lovgate block
permit ip any any
c. Create and apply the access-list to the Internet facing interface of a
gateway/edge/border router
i) This will block the offending traffic prior to entry into the LinkStar
hub. The example below shows how to place the access list into
interface FastEthernet0/0 of a router, using access-list 110
ii) Enter in privileged EXEC mode
(1) Router # configure terminal
(2) Router(config)#
(3) Create the access list
Router(config)# access-list 110 deny icmp any any redirect
Router(config)# access-list 110 deny ip 127.0.0.0 0.255.255.255 any
Router(config)# access-list 110 deny ip AA.BB.CC.0 0.0.0.255 any
Router(config)# access-list 110 deny ip DD.EE.FF.0 0.0.0.255 any
Router(config)# access-list 110 deny ip host 0.0.0.0 any
Router(config)# access-list 110 deny udp any any eq tftp
Router(config)# access-list 110 deny udp any any eq 77
Router(config)# access-list 110 deny tcp any any range 135 139
Router(config)# access-list 110 deny udp any any range 135 139
9
Router(config)# access-list 110 deny tcp any any eq 445

Router(config)# access-list 110 deny tcp any any range 1433 1434
Router(config)# access-list 110 permit ip any any
Router(config)#
(4) Apply the access-list to the Internet facing interface of a
gateway/edge/border router
(a) Router(config)# int fa0/0
(b) Router(config-if)# ip access-group 110 in
(5) Return to privileged EXEC mode and write the configuration to
memory
(a) Router(config-if)# exit
(b) Router# write memory
(6) (Optional) Save your entries in the configuration file
(a) Router# copy running-config startup-config
5) Reference http://www.cisco.com/go/safe for these and other safe
networking recommendations and best practices
Sun Server Specific Issues
1) Problem symptom: NCC/RNCC Handovers
Component: NCC/RNCC
Category: Hardware
Description: NCCs or RNCCs initiate handovers to the redundant device
Problem Resolution: NCC/RNCC Redundancy issues can arise due to various conditions present on
the servers themselves or the connectivity between them
1) Please view the areas titled Disk Space and Ethernet Connectivity in this
manual, which will address 2 major problem areas that cause NCC/RNCC
handovers
2) The RNCCs should also be running in CPU Real Time mode
3) Also, please ensure that the /etc/system file has these 2 statements located
within the file:
set memscrub_span_pages=4
set tod_validate_enable=1
a. The /etc/system file must be edited via the VI editor, while logged in as
root
b. If the statements were not present however need to be added, the Sun
server must be rebooted (reboot command while logged in as root) in
order to be implemented
c. Ensure that the LinkStar processes have been stopped prior to rebooting
d. Ensure that the NCC and/or RNCC devices have the correct software
patch applied
10
4) More information on this is described in the ViaSat Customer Service

Bulletin NCC/RNCC Connection Manager (ConMgr) Switchover
document ID 1033496_001, which can be found here:
http://extranet.viasat.com/vsat/linkstar/bulletins/
2) Problem symptom: Sun Server disk space usage increases
Component: NCC/RNCC/TCP PEP
Category: Hardware
Description: Partition usage on the Sun Servers increases
Problem Resolution: This is related to the Sun Server Maintenance procedure, ViaSat document ID
1025541_002 which can be found here:
http://extranet.viasat.com/vsat/linkstar/procedures/. The / and /home partitions
should not show excessive usage
1) Make sure that the RCST IP accounting files located in the
/home/linkstar/etc.customer_rncc1e/etc directory do not contain more than
60 – 90 days of accounting information
a. The df command displays the amount of disk space occupied by
mounted or unmounted file systems, the amount of used and available
space, and how much of the file system's total capacity has been used.
i) Use the df –k command to display current partition usage listed in
Kilo Bytes:
Some disk partitions are set up as follows:
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c1t1d0s0 10086988 72159 9913960 1% /
/dev/dsk/c1t1d0s4 10086988 804782 9181337 9% /usr
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
/dev/dsk/c1t1d0s5 10086988 682198 9303921 7% /var
swap 3079968 8 3079960 1% /var/run
swap 3080816 856 3079960 1% /tmp
/dev/dsk/c1t1d0s7 12031180 769633 11141236 7% /data
/dev/dsk/c1t1d0s6 16140362 6630312 9348647 23% /home
/dev/dsk/c1t1d0s3 10086988 12148 9973971 1% /opt
While other disk partitions are set up as follows:

Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c1t1d0s0 5546850 1169182 4322200 22% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
swap 1841392 8 1841384 1% /var/run
swap 1847224 5840 1841384 1% /tmp
/dev/dsk/c1t1d0s4 255487 1041 228898 1% /data
/dev/dsk/c1t1d0s3 10084696 2425483 7558367 25% /home
3) Problem symptom: NCC/RNCC/TCP PEP SNMP Failures

Component: NCC/RNCC/TCP PEP
Category: Hardware
Description: SNMP Trap messages fail; NMS Changes to the TCP PEP do not get
propagated to the TCP PEP; SNMP Subagent continuously restarts (flaps)
Problem Resolution: SNMP communications is used throughout the LinkStar system for sending trap
messages and to aid in the configuration of network devices. There are
occasions where the SNMP Master Agent is not configured correctly or not
started, which causes SNMP to fail (SNMP Subagent flaps)

11
1) To prevent the SNMP Subagent from flapping, ensure that the SNMP
Master Agent (/etc/init.d/init.snmpdx) is configured correctly
a. Connect to the NCC/RNCC/TCP PEP, and at the CLI (Command Line
Interface) prompt, log in as super user
b. Edit the /etc/init.d/init.snmpdx file with the vi editor
c. Ensure that the /etc/init.d/init.snmpdx file appears as below
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/linkstar/snmp/lib
export LD_LIBRARY_PATH
case "$1" in
'start')
if [ -f /home/linkstar/snmp/conf/snmpdx.rsrc -a -x /home/linkstar/snmp/b
in/snmpdx ]; then
/home/linkstar/snmp/bin/snmpdx -y -c /home/linkstar/snmp/conf -a
/home/linkstar/snmp/conf/snmpdx.acl -o /home/linkstar/snmp/conf/enterprises.oid
fi
d. Once the changes have been made, save the file and exit out of vi editor
mode
e. Remain logged in as super user mode for the next step
2) Restart the SNMP Master Agent after the parameters in the
/etc/init.d/init.snmpdx file have been modified/verified
a. /etc/init.d/init.snmpdx start
i) The following message appears after the SNMP Master Agent has
been restarted:
REG_AGENT_IS_ALIVE
3) Log out of super user mode
a. At the telnet (#) prompt, type exit
4) While logged in as linkstar, restart the SNMP Subagent by killing the
process on the NCC/RNCC/TCP PEP
a. Issue an lstar_stat on the NCC/RNCC (or tcpspoof_stat on the TCP
PEP) and note the PID for the SNMP Subagent process
PROCESS STATUS PID
------- ------ ---
NCC process UP 14189
Java Adapter for NCC UP 14249
SNMP subagent for NCC UP 14365
NMS Server UP 14316
Map Server UP 14244
X Server UP 14233
LDAP Server UP 14200
b. Issue the following command “kill -9 pid_of_snmp_subagent_process",
replacing pid_of_snmp_subagent_process with the actual PID noted in
step 3) a. above, in this case 14365
c. Wait several moments for cron to respond to restart the SNMP
Subagent
5) SNMP will now function properly
6) Repeat the above steps on every NCC/RNCC/TCP PEP server
a. The devices do not have the LinkStar processes stopped or started in
order to implement the change
7) After any NCC/RNCC/TCP PEP reboot, ensure that the SNMP Subagent
process is operating
a. At a telnet prompt, issue ps –eaf | grep snmp
b. An example output from the NCC would be as follows:
[ncc1:~] ps -eaf | grep snmp

12
root 303 1 0 May 25 ? 0:39 /home/linkstar/snmp/bin/snmpdx -y -c

/home/linkstar/snmp/conf -a /home/linkstar
linkstar 12177 1 0 May 25 ? 0:37 /home/linkstar/release/lstar-
2.0.8.nccsnmpd -q 8000 -t 8001 -c /home/linkstar/s
4) Problem symptom: Other processes on the NCC are running in CPU Real Time mode
Component: NCC
Category: Software
Software Version: 1.0.8.16
Description: NCCs should be running in CPU Real Time mode
Problem Resolution: In order to reduce problems with the NCC services, only the NCC should be
running in CPU Real Time mode, as opposed to other processes running in
CPU Real Time mode
1) To view the CPU priority status of the NCC, issue prstat -a, and in the
output make sure the PRI (priority) for the NCC process is shown as 100,
which indicates that the NCC is running in CPU Real Time mode
a. The expectant results of the prstat –a command is as follows:
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
12145 linkstar 244M 223M sleep 26 11 0:00.04 9.6% java/165
12023 linkstar 512M 507M sleep 52 2 0:02.04 1.9% ns-slapd/46
12012 linkstar 13M 12M sleep 100 - 3:32.33 0.3% lstar-2.0.8.ncc/1
7187 linkstar 1944K 1408K run 53 2 0:00.01 0.1% fping/1
b. If other processes are running in CPU Real Time mode according to the
outputs given above, modifications will need to be made to the
/viasat/tcpspoof_prio_cronjob file, while logged in as root
i) Connect to the NCC, and at the CLI prompt, log in as super user
ii) Edit the /viasat/bin/ncc_prio_cronjob file with the vi editor
iii) Make the following changes to the file. The “ORIGINAL” lines
shown below are for reference purposes, and the updates are
highlighted in red:
ORIGINAL:
PROCESSPID=`$PS $PSOPTIONS | grep "lstar-.*ncc " | \
egrep -v '(grep|nccexec|is_ncc_active)' | \
awk '{print $1}'`
MODIFIED:
PROCESSPID=`$PS $PSOPTIONS | grep "lstar-.*ncc " | \
egrep -v '(grep|nccexec|is_ncc_active|update_ncc_dbs)' | \
awk '{print $1}'`
iv) Once the changes have been made, save the file and exit out of vi
editor mode
v) Log out of super user mode
vi) To verify that the changes made have been implemented, wait
several moments for cron to respond, and then follow the steps 1) a.
c. Repeat the above steps on the other NCC as well
5) Problem symptom: RNCC not running in CPU Real Time mode
Component: RNCCs
Category: Software
Description: RNCC should be running in CPU Real Time mode however is not
Problem Resolution: In order to reduce problems seen with Late BTP segments on the GCUs, ensure
that the RNCCs are running in CPU Real Time mode. Starting in LinkStar
software version 1.0.8.15, both the NCC and RNCC are automatically
configured to run in CPU Real Time mode. To configure the RNCC manually
to run in CPU Real Time mode, perform the following steps:

13
1) Issue an lstar_stat on the active RNCC and note the PID for the RNCC
process
PROCESS STATUS PID
------- ------ ---
RNCC process for Region 0x1e UP 26186
Java Adapter for RNCC for Region 0x1e UP 26222
SNMP subagent for Region 0x1e UP 26689
IPE Manager for Region 0x1e UP 8037
Java Adapter for IPE Manager for Region 0x1e UP 8059
PEP Manager for Region 0x1e UP 26679
Java Adapter for PEP Manager for Region 0x1e UP 26255
Trap Manager for Region 0x1e UP 26684
Java Adapter for TRAP Manager for Region 0x1e UP 26272
NMS Server UP 26533
2) Log in as root super user using the "su" command
3) Issue the following command "priocntl -s -c RT -i pid pid_of_rncc",
replacing pid_of_rncc with the actual PID noted in step 1 above, in this
case 26186
4) Exit out of the super user mode
5) Type prstat -a, and in the output make sure the PRI for the RNCC process
is shown as 100
a. This means that the RNCC process is running in CPU Real Time mode.
Type the letter q or use control c (^c) to stop the prstat output
b. Below is an example of the RNCC process running in CPU Real Time
mode, as seen via the prtstat –a command:
3061 linkstar 12M 12M sleep 100 - 1:21.36 3.6% lstar-1.0.8.11.r/1
11953 linkstar 3752K 3360K run 23 2 0:00.00 0.5% ps/1
20177 linkstar 34M 19M run 53 2 0:00.00 0.2% java/12
25971 linkstar 1088K 752K sleep 0 2 0:48.54 0.1% nccexec/1
Note: If there is a RNCC switch or restart, the above process needs to be repeated on the active RNCC. You
can also perform the same actions on the offline (standby) RNCC, so in the event of a RNCC handover, the
LinkStar RNCC process will already be running in CPU Real Time mode
6) Problem symptom: TCP PEP not running in CPU Real Time and with CPU Priority
Component: TCP PEP
Category: Software
Software Version: 1.0.8.14
Description: TCP PEP is not running in CPU Real Time mode with CPU Priority
Problem Resolution: In order to reduce problems with jitter (large variations between the minimum
and maximum RTT of packets), the TCP PEP should be running in CPU Real
Time mode with priority
1) To view the CPU priority status of the active TCP PEP, issue the following
command:
a. [tcpacc1:~] tcpspoof_stat
b. The expectant result is to have the RTPRI status indicate 50. The
number 50 equals a high CPU priority for the TCP PEP process
PROCESS STATUS PID
------- ------ ---
TCP PEP Process UP 21343
TCP PEP SNMP Subagent UP 21354
REAL TIME PROCESSES:
PID RTPRI TQNTM
21343 50 100

14
2) To view the CPU Real Time mode/priority status of the active TCP PEP is
to issue prstat -a, and in the output make sure the PRI (priority) for the TCP
PEP process is shown as 150, with the results of the prstat command
a. The expectant results of the prstat –a command is as follows:
21343 linkstar 38M 37M sleep 150 - 75:35.47 8.9% lstar-1.0.8.16./1
26781 linkstar 1536K 1192K cpu0 58 0 0:00.00 0.2% prstat/1
26703 linkstar 1472K 1176K sleep 51 0 0:00.00 0.1% csh/1
26712 linkstar 2424K 1680K sleep 48 0 0:00.00 0.0% bash/1
227 root 2800K 2024K sleep 58 0 0:00.00 0.0% nscd/15
3) If other processes are running in CPU Real Time mode according to the
outputs given above, modifications will need to be made to the
/viasat/tcpspoof_prio_cronjob file, while logged in as root
a. Connect to the TCP PEP, and at the CLI (Command Line Interface)
prompt, log in as super user
b. Edit the /viasat/tcpspoof_prio_cronjob file with the vi editor
c. Make the following changes to the file. The “ORIGINAL” lines shown
below are for reference purposes, and the updates are highlighted in
red:
ORIGINAL:
SPOOFERPID=`$PS $PSOPTIONS | grep "lstar-.*tcpacc" | \
egrep -v '(grep|tcpspoofexec|is_tcpspoofer_active)' | \
awk '{print $1}'`
if [ "$SPOOFERPID" != "" ] ; then

$PRIO -s -c RT -i pid $SPOOFERPID
fi
MODIFIED:
SPOOFERPID=`$PS $PSOPTIONS | grep "lstar-.*tcpacc$ " | \
egrep -v
'(grep|tcpspoofexec|is_tcpspoofer_active|update_tcpspoof_dbs )' | \
awk '{print $1}'`
if [ "$SPOOFERPID" != "" ] ; then

$PRIO -s -c RT -p 50 -i pid $SPOOFERPID
fi
d. Once the changes have been made, save the file and exit out of vi editor
mode
e. Log out of super user mode
f. To verify that the changes made have been implemented, wait several
moments for cron to respond, and then follow the steps 1) a. and 1) b.
and 2) a.
g. This process is fixed with TCP PEP software release 1.0.8.14p3
4) Please ensure that the /etc/system file has this statement located within the
file:
set memscrub_span_pages=4
a. The /etc/system file must be edited via the vi editor, while logged in as
root
b. If the statement was not present however needs to be added, the Sun
server must be rebooted (reboot command while logged in as root) in
order to be implemented
c. Ensure that the TCP PEP processes have been stopped (tcpspoof_stop)
prior to rebooting
5) Repeat the above steps on the other TCP PEP as well

15
TDU/ITDU Specific Issues

1) Problem symptom: Intermittent ITDU and/or GCU alarms, network failures
Component: ITDUs
Category: Hardware
Description: A non-redundant LinkStar Network fails or if redundant, chain failures occur
Problem Resolution: Possible ITDU hardware issue
1) Connect a PC via the console port to the ITDU and capture the output to a
text log file for analysis
2) Verify proper equipment grounding
3) Ensure all power cords, GPS inputs and Frame Sync timing cables are
connected properly
4) Ensure all power cords, GPS inputs and Frame Sync timing cables do not
have any weight stress on them
2) Problem symptom: Solid TDU alarm, LinkStar NMS Console indicates Uplink Chain Failure
Component: TDUs
Category: Hardware
Description: The uplink chain status on the LinkStar NMS Console is red; the TDU does
NOT indicate an alarm condition on the front panel LEDs
Problem Resolution: Possible TDU hardware issue
connected properly
4) If the TDU is not continuously rebooting, from rttelnet on the active
RNCC, issue a do restore_tdu_a or do restore_tdu_b, depending on which
uplink chain indicates as being down
5) If the TDU is continuously rebooting, it will need to be replaced via RMA
3) Problem symptom: Solid ITDU alarm, LinkStar NMS Console indicates Uplink Chain Failure
Component: ITDUs
Category: Hardware
Description: The uplink chain status on the LinkStar NMS Console is red, or the uplink
chains switch for no apparent reason
Problem Resolution: Possible TDU hardware issue
1) Connect a PC via the console port to the ITDU
a. Ensure that all of the default parameters are correct in the ITDU
bootconf (pconf), ASI rate is correct, etc
2) If the ITDU is rebooting, connect a PC via the console port to the ITDU
and capture the output to a text log file for analysis
connected properly
6) If the ITDU is not continuously rebooting, from rttelnet on the active
RNCC, issue a do restore_tdu_a or do restore_tdu_b, depending on which
uplink chain indicates as being down
7) If the ITDU is continuously rebooting, it will need to be replaced via RMA
16
4) Problem symptom: ITDU ASI Rate change, LinkStar Hub is unstable

Component: ITDUs
Category: Hardware
Description: A non-redundant LinkStar Network fails or if redundant, chain failures occur.
RCSTs lose TX Sync or take excessive time to gain TX Sync
Problem Resolution: If the ASI Rate was changed due to a DVB symbol rate change, the LinkStar
Hub Uplink Chain Delay needs to be recalculated. In some cases the network
will come up but the clocking may not be at the center of the span, causing
RCSTs to lose TX Sync or take excessive time to gain TX Sync
IPE Specific Issues
1) Problem symptom: IPE Manager Data Rate change, LinkStar Hub is unstable
Component: NMS/IPE
Category: Software/Hardware
Description: A non-redundant LinkStar Network fails or if redundant, chain failures occur.
RCSTs lose TX Sync or take excessive time to gain TX Sync
Problem Resolution: If the IPE Manager Data Rate was changed due to a DVB symbol rate change,
the LinkStar Hub Uplink Chain Delay needs to be recalculated. In some cases
the network will come up but the clocking may not be at the center of the span,
causing RCSTs to lose TX Sync or take excessive time to gain TX Sync
2) Problem symptom: After SMR Software upgrade, LinkStar Hub is unstable
Component: IPE
Category: Hardware
Software Version: Any to Any Version
Description: After upgrading the SkyStream SMR from any version to any version, the
LinkStar system becomes unstable. A non-redundant LinkStar Network fails or
if redundant, chain failures occur. RCSTs lose TX Sync or take excessive time
to gain TX Sync
Problem Resolution: If the SMR software was upgraded from any version to any version, the
LinkStar Hub Uplink Chain Delay needs to be recalculated. In some cases the
network will come up or RCSTs might lose TX Sync or take excessive time to
gain TX Sync
Modulator Specific Issues
1) Problem symptom: Modulator Symbol and/or FEC Rate change, LinkStar Hub is unstable
Component: Modulator
Category: Hardware
Description: RCSTs lose TX Sync or take excessive time to gain TX Sync
Problem Resolution: If the Symbol and/or FEC Rate were changed on the modulator, the LinkStar
Hub Uplink Chain Delay needs to be recalculated. In some cases the network
will come up but the clocking may not be at the center of the span, causing
RCSTs to lose TX Sync or take excessive time to gain TX Sync
RCST/GCU Specific Issues
1) Problem symptom: RCSTs on a specific GCU are down
Component: GCU
Category: Hardware

17
Description: The RNCC is assigning the Bursts to the GCU; A Spectrum Analyzer trace
indicates the RCSTs are transmitting bursts and are being received at the output
of the L-Band splitter at the correct power level and frequency
Problem Resolution: This could be RF related
1) Replace the RF Cable from a known good working GCU
2) Check to see if the RCSTs on that GCU have been restored to service
a. If the RCSTs do not restore to service, connect to the GCU and ensure
that the bootconf (pconf) parameters are correct
i) Ensure that the population ID is correct
ii) Ensure that the RXAtten field is configured appropriately for this
LinkStar network
3) It is possible that there are other issues that might cause these symptoms.
Please contact the ViaSat Network Operations Center for further assistance
LinkStar Process Specific issues
1) Problem symptom: Linkstar Processes do not recover after power failure
Component: NCC/RNCC
Category: Hardware
Description: /home/linkstar/nccexec.ncc.ncc1or2.log or
/home/linkstar/nccexec.rncc_1e.rncc1 or rncc2.log indicates processes up
except Tomcat server, LDAP keeps restarting every 2 minutes. lstar_stat
indicates all processes in Standby except down for SNMP
Problem Resolution: Enable logging on the mounted partitions to ensure a safe recovery of data in
the event of a severe power loss issue
1) Issue lstar_stop on the affected device
2) Ensure that the /etc/vfstab has “logging” enabled for the partitions, to
enable consistency of the partitions
3) While logged in as root, or super user, edit the /etc/vfstab file. Some of the
lines look like:
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
# Some lines that have been removed...
#
/dev/dsk/c1t1d0s0 /dev/rdsk/c1t1d0s0 / ufs 1 no -
/dev/dsk/c1t1d0s3 /dev/rdsk/c1t1d0s3 /home ufs 1 yes -
4) In reading the lines, the output equals:
Device to mount = /dev/dsk/c1t1d1s0
Device to fsck = /dev/rdsk/c1t1d0s0
Mount point = /
FS type = ufs
fsck pass = 1
Mount at boot = no
Mount option = (none, specified by the hyphen)
5) To enable logging:
The option is called 'logging' and should be listed under the 'Mount option' column. Note that all it means is that
the hyphens in the last column of the lines that begin with '/dev/dsk/...' need to be replaced with the word
'logging'. So, the file will now look like:
# Some lines that I have not shown here...
/dev/dsk/c1t1d0s0 /dev/rdsk/c1t1d0s0 / ufs 1 no logging
/dev/dsk/c1t1d0s3 /dev/rdsk/c1t1d0s3 /home ufs 1 yes logging

18
6) After this, type the 'sync' command and then type 'reboot' to restart the
machine. The next time the machine comes up, the logging feature will be
enabled
7) After logging has been enabled and the server has been rebooted, restart the
LinkStar processes
Note: Make sure that the spelling of 'logging' is correct. If /etc/vfstab is damaged, unpredictable behavior may
occur
2) Problem symptom: After an RNCC restart, only a portion of the network recovers
Component: RNCCs
Category: Hardware
Description: Some RCST records that were on the NMS are no longer present
Problem Resolution: Remove temporary LinkStar database files from the RNCC
1) From rttelnet issue the “showhealth” command
2) If the numbers of GCUs and/or RCSTs from the showhealth report do not
match what is configured on the NMS, check the
home/linkstar/etc.<hubname>_rncc1e/etc/db for .tdb files
3) The RNCC will use these before pulling the information from LDAP
during a network restart
4) Delete all of the .tdb files except RnccConf.tdb and almAdapterInfo.tdb
files, and then restart the RNCC
5) The RnccConf.tdb file should contain the following entries ONLY and
nothing else
6) If there are other entries in that file, edit the file with the vi editor and copy
and paste the below entries into that file
Name : "CustomerRNCC1e"
regionid : 0x1e
ipaddr : 192.168.2.1
AdminStatus : 0
;;
7) After the file has been edited with the correct information, stop the RNCC
(lstar_stop) and then restart the RNCC (lstar_start)
3) Problem symptom: Linkstar LDAP process not recover after power failure
Component: NCC/RNCC
Category: Software
Description: /home/linkstar/nccexec.ncc.ncc1or2.log indicates processes up except Tomcat
server, LDAP keeps restarting every 2 minutes. The lstar_stat output indicates
all processes in Standby except down for SNMP
Problem Resolution: LDAP corruption occurred due to abrupt power failure on the NCCs. LDAP is
attempting to recover, and could take 1+ hours
1) Create an LDIF on both NCCs for safety and for import
2) De-install/re-install LDAP (might have to be done on both NCCs)
3) Import the LDIF on the last known running NCC
4) Re-initialize LDAP replication, verify processes

19
LinkStar Network Related Issues

NMS Specific Issues
1) Problem symptom: LinkStar NMS Satellite Software download fails for one RCST
Component: RNCCs/RCSTs
Category: Software
Description: Terminal acquires but will not accept new software or firmware as defined on
the LinkStar NMS Console
Problem Resolution: Possible software/firmware bank mismatch
1) From rttelnet, send terminal in question an lmep command (sendterm
0xAABB lmep)
2) If the output displayed is a “split" condition where one bank is (E) and the
other bank is (P), then the software or firmware banks need to be reset in
order to allow the RCST to accept the download
3) Issue the lmesetprisw 0 or 1 or lmesetprifw 0 or 1 command to correct the
condition, and then reset terminal and re-issue satellite download
2) Problem symptom: LinkStar NMS Satellite Software download not working on the network
Category: Software
Description: Terminal acquires but will not accept new software or firmware as defined on
the LinkStar NMS Console
Problem Resolution: It is possible that are too many software and/or firmware downloads configured
on the LinkStar NMS Console
1) Verify proper settings on the NMS
2) Delete unnecessary downloads
a. There should be at least 1 Region (0x011efffe) download for RCST
software and 1 Region (0x011efffe) download for RCST firmware
b. Individual RCST downloads should not be needed, since a Region
broadcast will take care of all RCSTs on the network
3) Problem symptom: File Not Available message on LinkStar NMS Active Alarm Viewer
Component: NCCs/RNCCs
Category: Software
Description: After enabling a LinkStar NMS Software download, a “File Not Found”
message appears on the LinkStar NMS Active Alarm Viewer
Problem Resolution: The software file is not located in the correct directory or a prepterm needs to
be completed on the rcst-software_version.term.exe file
1) All RCST software and firmware releases are located on the NCCs for
LinkStar software versions 1.0.8.11 and below or on the RNCCs for
LinkStar software versions 1.0.8.14 and above
a. Irregardless of software version, the files will be located in the
/home/linkstar/release directory of the respective servers
2) If the rcst-software_version.term.cmz file does not exist in the
/home/linkstar/release directory, a prepterm command must be issued on
the rcst-software_version.term.exe file. An example follows below:
a. [rncc1:~/release] prepterm rcst4-1.0.8.16p4.term.exe
b. This creates a term.cmz file, such as rcst4-1.0.8.16p4.term.cmz

20
4) Problem symptom: LinkStar NMS Console is blank

Component: NMS
Category: Software
Description: When an option on the LinkStar NMS Console is selected, such as the
Population view or TDMA Carrier set, and the right hand view shows only a
green page with no information
Problem Resolution: This is an indication that the LinkStar NMS Console has lost connectivity with
the online NCC. The workaround for this is to close the NMS Console and log
back in
1) The issue could be due to connectivity issues between the PC that has the
NMS Console and the online NCC
2) An NCC handover occurred
3) There is a possibility of a Sun server issue on the NCC where disk space is
running out or the NCC is running out of processes. Please view the
Ethernet Connectivity and Disk Space issues described in this manual
4) One other possibility that might cause this could be due to the amount of
NMS Connections open on the active NCC
a. To view the active connections, issue the following command from the
online NCC via command line: netstat -a | grep 30000
i) This command will list all active connections to the NCC for
LinkStar NMS Console sessions
ii) If there are an excessive amount of connections, a workaround is to
restart the NMS server on the online NCC. To do this, perform the
following:
(1) Issue an lstar_stat on the active NCC and note the PID for the
NMS Server process
PROCESS STATUS PID
------- ------ ---
NCC process UP 14189
Java Adapter for NCC UP 14249
SNMP subagent for NCC UP 14365
NMS Server UP 14316
Map Server UP 14244
X Server UP 14233
LDAP Server UP 14200
(a) Issue the following command “kill -9 pid_of_nms_server",
replacing pid_of_nms_server with the actual PID noted in
step 1 above, in this case 14316
(b) Issue the lstar_stat command to verify that the NMS Server
process restarts, which is performed by cron. A new PID
will be issued once the server has restarted
(c) Once the NMS Server has restarted, log back into the
LinkStar NMS Console
5) Problem symptom: LinkStar NMS Console BTP Graph not displaying
Component: NMS
Category: Software
Description: The LinkStar NMS Console BTP Performance screen does not display any
TDMA Carrier information
Problem Resolution: Most likely, the cause of this is similar to the causes described above in the
Blank NMS Console issue. The workaround will be to restart the LinkStar
NMS Console server as described above

21
6) Problem symptom: LinkStar NMS Console - Unable to process … message on diagnostic

screens
Component: NMS
Category: Software
Description: The LinkStar NMS Console Diagnostic Screen times out or presents an error
while running a diagnostic command
Problem Resolution: There might be occasions where the diagnostic screens might report an error
where it is unable to process the requested action
1) Most likely, the cause of this is similar to the causes described above in the
Blank NMS Console issue
2) The workaround will be to restart the LinkStar NMS Console server as
described above
7) Problem symptom: Various RCSTs do not gain TX Sync
Component: NMS
Category: Software
Description: RCSTs that are known to be transmitting do not gain TX Sync
Problem Resolution: This could be due to mis-configuration on the NMS, causing AB (Acquisition
Burst) starvation
1) If User Groups are used, verify all RCST configurations
a. Ensure that RCSTs that are part of a User Group are assigned to the
correct TDMA Carrier ID or are configured as Automatic TDMA
Carrier Assignment mode
2) If all configurations have been verified, contact the ViaSat Network
Operations Center for technical assistance
a. Debugging commands can be issued to discover offending RCSTs to
aid in network recovery
8) Problem symptom: Incorrect/inconsistent information in a User Group after a User Group
change
Component: NMS
Category: Software
Description: After a change has been submitted in a User Group and it is closed prior to the
screen refreshing, incorrect and/or inconsistent information might appear in that
User Group
Problem Resolution: This will happen if the User Group window is closed prior to the window being
refreshed
1) This condition will cause problems since the operation was stopped prior to
being completed properly
2) The proper method is to wait for the screen to refresh after the “Submit”
button is pressed, prior to closing the User Group window
3) If the above steps were not followed and a network anomaly exists, please
contact the ViaSat Network Operations Center for assistance
9) Problem symptom: After upgrading to 1.0.8.14, GCU Specific Static routes fail
Component: GCU, NMS
Category: Software
Software Version: 1.0.8.14 and above
Description: GCU specific static routes fail after upgrading to 1.0.8.14 or above

22
Problem Resolution: GCU specific static routes are no longer supported on LinkStar software
versions 1.0.8.14 and above. The static routes must now be applied to the hub
level, instead of independently on the GCUs
1) Prior to upgrading the LinkStar hub to 1.0.8.14 or above, delete the GCU
specific static routes and add them to the hub level static routes on the
NMS
2) The hub level static routes can be found here:
a. LinkStar NMS Console  expand RNCC 0x<RegionID> or LinkStar
RNCC 0x<RegionID>  Select Hub 0x<RegionID>  Configuration
 IP Static Route Configuration
b. Add the static routes as appropriate according to the configurations that
are necessary to permit the intended traffic to reach it’s destination
10) Problem symptom: Ability to limit users on the LinkStar NMS Console
Component: NMS
Category: Software
Description: The need might arise to limit the visibility to certain LinkStar NMS Console
users to view only portions of the LinkStar NMS Console
Problem Resolution: Write access can be restricted to the User Group Set, Carrier Sets, Flow Profile
Set, IP QoS Queue Set and Hub Set. View access can be restricted to
population views
1) On the LinkStar NMS Console, select Network  Administration 
OperatorGroup Set
2) Select Configuration  Add, and create the authorized Operator Group
a. Add in the required data for the Group Name: and Description: fields
b. Select Submit
3) On the LinkStar NMS Console, select Network  Administration 
Operator Set
4) Select Configuration  Add, and create the authorized Operator
a. Add in the required data for the User Id:, User Name:, Description:,
Password:, Re-enter Password:, IP Address:, IP Mask:, and Telephone:
fields
b. In the "Unassigned Groups:" field, select the newly created
OperatorGroup and move it to the "Assigned Groups:" field
c. Select Submit
5) Select the appropriate permissions for this new user/group in both the NCC
and RNCC
a. Select NCC  Utility  Permissions
b. For the group that needs to be restricted, select Read Only
c. For all other groups, select Inherited
d. Select RNCC 0x1e or LinkStar RNCC 0x1e  Utility  Permissions
e. For the group that needs to be restricted, select Read Only
f. For all other groups, select Inherited
6) Select the appropriate permissions for this new user/group for the
population(s) that the group needs access to or needs to be restricted
a. Select the Population(s) Utility  Permissions
b. For the group that needs to be restricted, select Read Only or No
Access, as appropriate
7) Select the appropriate permissions for this new user/group for the Software
Download Set
a. Select the Software Download Set  Utility  Permissions

23
b. For the group that needs to be restricted, select Read Only or No

Access, as appropriate
RNCC Specific Issues
1) Problem symptom: Static and Multicast Routes are deleted every Saturday night
Component: RNCC
Category: Software
Software Version: 1.0.8.11 – 1.0.8.15
Description: Every Saturday night at midnight RNCC time, the Static and Multicast Routes
on the LinkStar network are deleted from the SkyStream SMR
Problem Resolution: This is due to a sporadic issue with the interaction between the SMR Route
Flush process and IPE manager start time. If the IPE Manager on the RNCC
has been started within +/-10 minutes of the top of the hour, then this problem
occurs when the accounting file write timer expires, which causes all of the
routes to be deleted. To fix this condition, follow these steps:
1) Kill the PID of the IPE manager process, causing it to restart it again
sometime between the times of XX:20 and XX:40, where XX is any hour
of the day
a. For example, the IPE Manager can be restarted at 03:22, 07:36 or 15:25
etc
b. The time can be seen by issuing the “date” command on the RNCC
2) When the time is between the XX:20 and XX:40, kill the IPE Manager
process
a. Issue an lstar_stat on the active RNCC and note the PID for the IPE
Manager process
PROCESS STATUS PID
------- ------ ---
RNCC process for Region 0x1e UP 26186
Java Adapter for RNCC for Region 0x1e UP 26222
SNMP subagent for Region 0x1e UP 26689
IPE Manager for Region 0x1e UP 8037
Java Adapter for IPE Manager for Region 0x1e UP 8059
PEP Manager for Region 0x1e UP 26679
Java Adapter for PEP Manager for Region 0x1e UP 26255
Trap Manager for Region 0x1e UP 26684
Java Adapter for TRAP Manager for Region 0x1e UP 26272
NMS Server UP 26533
b. Issue the following command “kill -9 pid_of_ipe_manager", replacing
pid_of_ipe_manager with the actual PID noted in step 1 above, in this
case 8037
c. Issue the lstar_stat command to verify that the IPE Manager process
restarts, which is performed by cron
d. A new PID will be issued once the server has restarted
3) Verify that the IPE Manager has restarted and that the routes have been
repopulated, by checking the ipelog
a. The ipelog is located in the
/home/linkstar/etc.hubname_rncc1e/etc/ipelog directory.
b. Issue tail –f ipelog in that directory to tail the output of the ipelog file
2) Problem symptom: Slow RCST bandwidth de-allocation times
Category: Software
24
Description: Bursts remain assigned to the RCSTs even though the RCST is not transmitting
data
Problem Resolution: There are parameters that can be changed to allow for quicker de-allocation of
bandwidth from RCSTs on a LinkStar Region level
1) Change BWFactors from 0x3c02 (60%/02%) to something like 0x3c14
(60%/20%)
a. This will de-allocate CIR/BoD bursts more quickly
b. Please take care when adjusting the values, as this could be detrimental
to the operations of the LinkStar network
2) Decrease the DeallocDelay from its default of 10 seconds to a shorter value
of 6 seconds
a. Do not set the value to anything under 6 seconds, as this could be
detrimental to the operations of the LinkStar network
3) Contact the ViaSat Network Operations Center for assistance in making the
necessary changes, and to properly configure these changes into the
LinkStar database
TCP PEP Specific Issues
1) Problem symptom: TCP PEP Failures due to Multicast traffic
Component: TCP PEP, PBR, TX Switch
Category: Software
Description: Multicast traffic that is allowed to flow towards the TCP PEP will cause the
TCP PEP to crash
Problem Resolution: Ensure that the LinkStar hub is properly configured to prevent Multicast traffic
from flooding the TCP PEP
1) Ensure via a VLAN/PBR Policy that no multicast traffic is passed to the
PEP
a. One way of achieving this is by not allowing VLAN 1 on the trunk port
between the hme0 interface and PBR interface Fa0/1 (Multicast Traffic
in LinkStar software release 1.0.8.12 and above can only flow on
Management VLAN 1)
b. This also restricts TCP traffic flowing on the Management VLAN (1)
from passing through to the TCP PEP
i) In order to avoid this, the native VLAN on this trunk port should be
defined to a number other than VLAN 1
ii) Using a VLAN ID such as VLAN 999 for the native VLAN
prevents this issue from occurring
iii) It is imperative to note that VLAN 999 should not be configured as
a user VLAN by the customer and no normal traffic should be
passed on this VLAN. If for whatever reason the there is a need to
use VLAN 999 as a traffic VLAN identifier, then the native VLAN
ID of 999 should be replaced in the TX Switch and PBR
configuration by some other number not used in the network
iv) It is also imperative to note that VLAN 3 should not be configured
as a user VLAN by the customer and no normal traffic should be
passed on this VLAN. VLAN 3 is used for the connection between
the PBR Fa1/0 interface and interface hme1 of the TCP PEP. It
should not be used to pass normal traffic as a configured VLAN in
the customer network
v) Use the show vlan or show vlan brief command on the TX Switch
(Cisco 3550 or 3750) to verify which VLANs are configured and
their status
25
*** Any VLANs used in the TX switch configurations to achieve traffic separation should not be used by
the customer as configured VLANs in their network ***
2) Problem symptom: TCP PEP communication failures
Component: NMS
Category: Software
Description: TCP PEP communication failures occur. SNMP Trap messages are not passed
to the LinkStar NMS Console
Problem Resolution: Ensure that the LinkStar NMS Console TCP PEP Manager Configuration
screen has the correct community string configured
1) On the LinkStar NMS Console, select RNCC 0x<RegionID> or LinkStar
RNCC 0x<RegionID>  Configuration  TCP PEP Manager
Configuration
2) Leave that window open, since it will be needed in the next steps to copy
the data
3) On the LinkStar NMS Console, open the TCP PEP Manager Configuration
screen again
a. Select RNCC 0x<RegionID> or LinkStar RNCC 0x<RegionID> 
Configuration  TCP PEP Manager Configuration
4) On the second screen, in the “Community String for SNMP Read/Write
Access:” field, type in the word “public”, without the “” marks
5) On the second screen, disable the TCP PEP Manager
a. Deselect the check mark in the “Enable TCP PEP Manager:” box
b. Select the Submit button at the bottom of the page
6) After the screen refreshes, enter in the IP Address data from screen one
onto the second screen
7) Select the Submit button at the bottom of the page
8) After the screen refreshes, the SNMP Community screen is now configured
to public
a. TCP PEP SNMP Trap communications should now function
3) Problem symptom: RCSTs are passing intermittent TCP traffic
Category: Software
Description: Network is up however TCP traffic is passing intermittently or there is a saw
tooth effect as seen via the SkyStream SkyAlarm
Problem Resolution: One of the reasons why this might happen is if the TCP window size is not set
correctly
1) To calculate the window size, use the following formula:
Maximum TCP throughput per connection (in bps) =
Window size in bytes / RTT value in seconds
a. For example, if the window size is set to 512 Kbytes (as seen via the
LinkStar NMS Console, TCP PEP Manager Configuration) and the
average satellite RTT delay is 650 ms, the maximum throughput per
connection is (512* 8)/ (650 /1000) = ~6.302 Mbits/s.
b. In a different example, if the window size is set to 64 Kbytes and the
average satellite RTT delay is 650 ms, the maximum throughput per
connection is (64* 8)/ (650 /1000) = ~788 kbits/s
2) This will help resolve the window size issue. If the problem continues,
then troubleshoot with the PEP further per the PEP Troubleshooting Guide

26
GCU Specific Issues

1) Problem symptom: Incorrect TxP(dBm) Readings on GCU tfpr reports
Component: GCU
Category: Software
Description: RCSTs with MAC addresses higher than 0x010000 indicate inaccurate
TxP(dBm) readings
Problem Resolution: This occurs when only BoD and Aloha are configured for the remote
1) Add 1 channel of CIR to the site and begin a continuous ping to that RCST
2) Once CIR is established in the BTP, repeat the TFPR command in the GCU
3) TxP(dBm) should report an accurate reading (approximately 1/2 of the
RCST TxPower setting)
2) Problem symptom: Newly added GCU Down Alarm
Component: GCU/NMS
Category: Software
Description: A GCU was added to a RX Rack and the LinkStar NMS Console, yet there is
an alarm indicating that the GCU is down
Problem Resolution: Verify the following:
1) The GCU is configured in the NMS with and IP address
2) The GCU has the correct software and firmware
3) The GCU has the right population ID in the GCUs bootconf (pconf)
IPE Specific Issues
1) Problem symptom: SkyAlarm is showing an Alarm for the IMS Agent
Component: IPE
Category: Software
Description: The SkyStream SkyAlarm viewer indicates an Alarm for the IMS Agent and
the window intermittently flashes
Problem Resolution: A parameter change needs to be made via the SkyStream SkyPilot application
1) On SkyPilot, select SkyNet on... for the online SMR
2) Select Data Carousel Agent on...
3) In the "Discovery Method" window, select Auto-Discovery
4) On the bottom of the window, select Apply
2) Problem symptom: SkyAlarm is showing an Alarm for the TS In port
Component: IPE
Category: Software
Description: For LinkStar hubs that utilize the ITDU ONLY. The SkyStream SkyAlarm
viewer indicates an Alarm on the TS In port and the window intermittently
flashes
Problem Resolution: A parameter change needs to be made via the SkyStream SkyPilot application.
LinkStar hubs that utilize the ITDU do not supply as ASI signal to the
SkyStream SMR on the TSIO DVB ASI In port. This alarm might be seen after
the IPE Manager on the RNCC is restarted or after an RNCC handover
1) On SkyPilot, select SkyNet on... for the online SMR
2) Expand the selection for SkyLocal on…
3) Expand the selection for TSIO DVB ASI In
4) With the mouse, right click on TSIO DVB ASI In SI Parsed and select
“Stop Now”
5) Select “Yes” on the pop-up window
27
6) In the “Enable/Disable Transport Input” window, select Disable

7) On the bottom of the window, select Apply
RCST Specific Issues
1) Problem symptom: High packet loss seen at the RCSTs
Component: GCUs/RCSTs
Category: Software
Description: TDMA Carrier(s) defined for Aloha reservations and Aloha FCA (Free
Capacity Assignment)
Problem Resolution: GCU attreq values as seen via tfpr are out of range in relation to GCU bootconf
attenuation value (RXAtten)
1) Manually assign attenuation via cacsetatt and save -r commands
a. There might be conflicting configurations on TDMA carrier and
Region Aloha settings
b. Traffic that requires BOD might not get it due to excessive Aloha
settings
2) Problem symptom: RCSTs are unable to browse the Internet or pass any TCP traffic
Component: RCSTs/TCP PEP
Category: Software
Description: Network is up however no TCP traffic is passing
Problem Resolution: Customer calls and complains about traffic not going to internet
1) Ping the PBR Fa1/1 port and then Fa0/0 port to ensure that you can ping to
the router's LinkStar LAN port (Fa1/1) and the Internet connection (Fa0/0)
2) Once this is accomplished, try to telnet to the PBR Fa1/1 port and then to
the Fa0/0 port
3) If telnet to the 0/0 port fails, ensure that the TCP PEP is running and
passing traffic
4) Rttelnet into the online TCP PEP and type the command tc. You will get
the following result:
Terr Satt
IfNetStat Up Up
TxKbps 225.959 697.535
RxKbps 710.960 239.543
TxMbytes 256.651 245.767
RxMbytes 2932.438 278.083
CurrConns 431 431
TotalConns 4759280 4759280
5) Ensure that both Terr and Satt sides show up and not down
6) If they are down, then there is a failure on the TCP Acceleration LAN
Note: Please ensure that the TX and RX kbps are increasing on both sides. If they are not, please troubleshoot
the TCP PEP further or contact the ViaSat Network Operations Center for assistance
VLAN/VPN Specific Issues
1) Problem symptom: VLAN/VPN requirements/troubleshooting
Component: LinkStar Hub
Category: Software/Hardware
Description: VLAN (Virtual LAN)/VPN Traffic is not passing on a specific or all VLAN(s)
Problem Resolution: There are certain requirements to ensure that VLANs/VPNs are implemented
correctly
28
1) The Allot NetEnforcer needs to be placed between the PBR 0/1 interface
and hme0 of TCP PEP
a. This is needed if the customer wants to use the Allot to manage
bandwidth using VLANs
2) There should not be any equipment other than VIASAT provided
equipment within the 192.168.150.x subnet
a. Issues have been noticed that when Cisco routers are placed within the
192.168.150.x/24 subnet, some VLAN traffic ceased functioning
b. For reasons unknown, the newly introduced Cisco router (not the PBR)
responds with a message to the GCU with hme1 interface ip address
not found, or it proxy-arps for that address, causing the GCU:
i) Either to assume that the route is unreachable or,
ii) To cause the GCU to send the packets to that device
c. If there is a router present which cannot be removed (customer
requirements) try performing the following:
i) no cdp enable
ii) no ip-proxy arp
3) After the router is configured with VLAN/VPN configurations, and VRF
routes are defined in the router, the following command will have to be
issued in order to run ping tests:
a. ping vrf <vpn name> <ip address>
i) If VRF routes are not defined, use the following command to ping:
ping <vpn name> <ip address>
4) Ping commands should be used to test basic connectivity in order to test if
the VPN is connected properly
a. The first ping should be done from the RCST VPN IP Address to the
PEP VPN IP Address using the command:
i) ping -v <vpn id in decimal> -i <interface id obtained from prt ifmgr
command> <TCP PEP VPN IP Address>
(1) This will check out the path till from the RCST to the PEP
b. The second ping should be from the TCP PEP to the PBR for a VPN
connection
i) ping -v <vpn id in decimal> <PBR IP Address for this VPN trunk>
c. The third ping should be one from the RCST to the PBR
i) ping -v <vpn id in decimal> -i < interface id obtained from prt
ifmgr command > <PBR VPN IP Address>
2) Problem symptom: A newly added VLAN(s) fails to pass traffic
Component: TX Switch
Category: Software
Description: When utilizing the VLAN/VPN feature on LinkStar software version 1.0.8.14
and above, configurations on the TX Switch need to be implemented in order to
make the newly added VLAN(s) active
Problem Resolution: Follow the below steps to configure the TX Switch to enable and view VLANs
Beginning in privileged EXEC mode, follow these steps to add an Ethernet
VLAN:
1) Enter VLAN configuration mode
a. LinkStar_TX_Switch# configure terminal
b. LinkStar_TX_Switch(config)# vlan database
2) Add a VLAN by assigning a number to it
a. If no name is entered for the VLAN, the default is to append the vlan-id
to the word VLAN. For example, VLAN0004 could be a default
VLAN name for VLAN 4
29
b. LinkStar_TX_Switch(vlan)# vlan vlan-id name vlan-name

3) Update the VLAN database, propagate it throughout the administrative
domain, return to privileged EXEC mode and write the configuration to
memory
a. LinkStar_TX_Switch(vlan)# exit
b. LinkStar_TX_Switch# write mem
4) Verify the VLAN configuration
a. LinkStar_TX_Switch# show vlan name vlan-name
b. LinkStar_TX_Switch# show vlan
c. LinkStar_TX_Switch# show vlan brief
5) (Optional) Save your entries in the configuration file
a. LinkStar_TX_Switch# copy running-config startup-config
6) Example as follows:
LinkStar_TX_Switch# config t
LinkStar_TX_Switch(config)# vlan database
LinkStar_TX_Switch(vlan)# vlan 222
LinkStar_TX_Switch(vlan)# exit
LinkStar_TX_Switch# wri mem
LinkStar_TX_Switch# show vlan name vlan-name
LinkStar_TX_Switch# show vlan
LinkStar_TX_Switch# show vlan brief
3) Problem symptom: VLAN/VPN fails after new RCST to that VPN Membership is added
Component: NMS
Category: Software
Description: After a newly added RCST to a VPN membership, traffic on that VLAN fails
Problem Resolution: This can appear if the RCST is configured as a default route
1) Verify the RCSTs IP Address configuration on the RCST Configuration
screen
2) Ensure that the RCST IP Address and subnet mask are something other
than 0.0.0.0/0.0.0.0
a. Having the RCST that is part of a VLAN/VPN with IP Address of
0.0.0.0/0.0.0.0 causes the RCST to become the default route for that
VLAN
b. VLAN traffic will cease to function if that is the case
3) Change the RCST IP Address to a valid IP Address to fix this condition
4) Problem symptom: Cisco 3660 PBR Memory utilization is high after VRFs are configured
Component: PBR
Category: Hardware
Description: After a VRF is configured on the Cisco 3660 PBR, the PBR memory utilization
is high
Problem Resolution: VRF configurations require that CEF (Cisco Express Forwarding) is enabled
1) The CEF process utilizes high amounts of memory
2) The PBR should have at least 256 MB of RAM installed in order to run
VRFs with CEF enabled
3) Ensure that ip route-cache policy statements are configured for each
interface on the PBR as well
4) No more than 2 to 3 VRFs should be configured on a Cisco 3660 PBR. If
any higher number of VRFs are to be configured, it is recommended to
replace the Cisco 3660 PBR with a Cisco 7206 PBR

30
5) Problem symptom: VLAN traffic fails with Cisco CEF enabled

Component: PBR
Category: Hardware
Description: VLAN traffic might fail on certain routers when Cisco CEF is enabled
Problem Resolution: Disable Cisco CEF on the PBR interfaces while maintaining the global ip cef
configuration
1) On the PBR in privileged EXEC mode, disable CEF on each interface of
the PBR
2) Enter into configuration mode
a. LinkStar_PBR# configure terminal
3) Disable CEF on each interface of the PBR
a. LinkStar_PBR (config)# int fa0/0
b. LinkStar_PBR(config-if)# no ip route-cache cef
c. LinkStar_PBR (config)# int fa0/1
d. LinkStar_PBR(config-if)# no ip route-cache cef
e. LinkStar_PBR (config)# int fa1/0
f. LinkStar_PBR(config-if)# no ip route-cache cef
g. LinkStar_PBR (config)# int fa1/1
h. LinkStar_PBR(config-if)# no ip route-cache cef
4) Return to privileged EXEC mode and write the configuration to memory
a. LinkStar_PBR(config-if)# exit
b. LinkStar_PBR# write mem
a. LinkStar_PBR# copy running-config startup-config
6) Problem symptom: Intermediate VLAN traffic fails
Component: PBR
Category: Hardware
Description: Intermediate VLAN traffic might fail due to ACL (Access Control List) 101 on
the PBR
Problem Resolution: Modify ACL 101 on the PBR (default LinkStar hub installation) to include all
IP, instead of only TCP
1) On the PBR in privileged EXEC mode, modify ACL 101
2) Enter into configuration mode
a. LinkStar_PBR# configure terminal
3) Modify the parameters of ACL 101
a. LinkStar_PBR (config)# no access-list 101
b. LinkStar_PBR (config)# access-list 101 permit ip any any
4) Return to privileged EXEC mode and write the configuration to memory
a. LinkStar_PBR(config-if)# exit
b. LinkStar_PBR# write mem
a. LinkStar_PBR# copy running-config startup-config
7) Problem symptom: Management (native) traffic fails beyond the Ethernet interface of a RCST
Component: Customer Switch
Category: Software
Description: Customer’s traffic might fail if the management (native) VLAN ID is
configured to something other than VLAN 1
Problem Resolution: This will occur if the native VLAN for the customer switch is something other
than VLAN 1
31
1) The RCST sends out all Management (native) VLAN packets untagged on
its Ethernet side
2) The LinkStar network is designed this way in order to support non-VLAN
remote sites, with no trunk port configured to the switch connected to the
RCST
3) If the switch connected to the RCST has the Management (native) VLAN
configured to something other than VLAN 1, the switch will receive these
packets untagged and will not be able to forward them
a. Configure the switch behind the RCST in “native” mode with a non-1
VLAN ID
8) Problem symptom: Unable to configure the Max Data Rate on a specific RCST
Component: NMS
Category: Software
Description: On an already configured RCST, the Max Data Rate: on the IP Forward
Channel configuration screen does not get passed to the SkyStream SMR
Problem Resolution: Manually configuring the Max Data Rate: in the IP Forward Channel
configuration screen on the NMS for a specific RCST that already has an IP
Address configured causes the IPE Manager to crash and restart
1) In order to utilize the Max Data Rate: IP Forward Channel configuration
screen, the IP Forward Channel rate must be configured first, prior to
configuring the RCST IP Address information
a. With an already configured RCST, configure the RCST IP Address and
Sub Net Mask fields to 0.0.0.0/0.0.0.0
b. This will remove any entry on the SkyStream SMR for that RCST
c. Enter in the Max Data Rate: in the IP Forward Channel configuration
screen
2) Once the IP Forward Channel configuration has been submitted on a
specific RCST, enter in the RCST IP Address information
3) The IP Forward Channel rate will then be properly forwarded to the
SkyStream SMR, and the rate will be limited according to the rate specified
on the IP Forward Channel configuration screen
4) This has been fixed in LinkStar software version 1.0.8.17
RCST Specific Issues

1) Problem symptom: Unknown RCST root user password
Component: RCSTs
Category: Software
Description: A customer or operator is unable to gain access to an RCST in “root” mode
Problem Resolution: The root user password can be reset via two different methods, depending on
the RCST status
1) If the RCST is in at least RX Sync with the LinkStar hub (SAT LED slow-
flashing):
a. This means that at least the frequency and symbol rate are correct
b. From the online RNCC prompt, connect to rttelnet <RegionID>, as in
rttelnet 1e
c. Issue the following command
i) senduterm 0xAA.BB passwd -u root -p "" or senduterm
0xAA.BB.CC passwd -u root -p ""

32
(1) Replace AA.BB or AA.BB.CC with the last 2 or last 3 Octets

of the RCST's Ethernet MAC address
(2) This will reset the root user password to blank, so the user at
the RCST will simply press enter when prompted for a
password when connecting to the RCST via telnet
2) If the RCST does not have any sync status with the LinkStar hub (SAT
Light not lit):
a. Warning! Performing this procedure requires that the RCST's top
panel be opened up, which VOIDS any hardware warranty!
b. Turn off (remove power from) the RCST
c. Connect to the RCST via the console port on the RCST motherboard
(LinkStar-I - III chassis) or via the rear panel console port (LinkStar-IV
chassis)
d. Turn on (apply power to) the RCST
e. At the Autoboot: line (after the COSMON Status: WatchDogReset
line), press the Enter key 3 times
i) This places the RCST in COSMON
f. At the COSMON prompt, type zapp
g. Press the Enter key
h. At the COSMON prompt, type boot
i. Press the Enter key
j. After the RCST reboots, press the Enter key at the "Password:" prompt
i) This logs the user into the RCST as the root user
2) Problem symptom: How to reset the root or guest user passwords on all RCSTs
Component: RCSTs
Category: Software
Description: A customer or operator requests to reset the password on all RCSTs on the
LinkStar region or on a specific LinkStar population
Problem Resolution: The root and/or guest user password(s) of all RCSTs on the LinkStar region or
LinkStar population can be reset via connecting to the LinkStar Region
1) To change the RCST root and/or guest password(s) on all RCSTs in the
LinkStar Region, follow these steps
a. This will work if the RCSTs are in at least RX Sync with the LinkStar
hub (SAT LED slow-flashing):
b. This means that at least the frequency and symbol rate are correct
2) From the online RNCC command prompt, connect to rttelnet <RegionID>,
as in rttelnet 1e
3) Issue the following command to reset the root user password for all RCSTs
on the entire LinkStar Region
a. senduterm 0x011efffe passwd -u root -p <pass>
i) Replace <pass> with the actual password that is to be used for the
root user, without the <> symbols
4) Issue the following command to reset the guest user password for all
RCSTs on the entire LinkStar Region
a. senduterm 0x011efffe passwd -u guest -p <guest>
i) Replace <guest> with the actual password that is to be used for the
guest user, without the <> symbols
5) To change the RCST root and/or guest password(s) on all RCSTs in a
specific LinkStar population, follow these steps
a. This will work if the RCSTs are in at least RX Sync with the LinkStar
hub (SAT LED slow-flashing):

33
b. This means that at least the frequency and symbol rate are correct
6) From the online RNCC command prompt, connect to rttelnet <RegionID>,
as in rttelnet 1e
7) Issue the following command to reset the root user password for all RCSTs
on LinkStar population 0x011e0001
a. senduterm 0x011e0001 passwd -u root -p <pass>
i) Replace <pass> with the actual password that is to be used for the
root user, without the <> symbols
8) Issue the following command to reset the guest user password for all
RCSTs on LinkStar population 0x011e0001
a. senduterm 0x011e0001 passwd -u guest -p <guest>
i) Replace <guest> with the actual password that is to be used for the
guest user, without the <> symbols
3) Problem symptom: RCST Is in TX Sync however not passing traffic
Component: RCSTs
Category: Software
Description: The LinkStar NMS Console indicates that the RCST is up (Green) however the
user is unable to pass any data
Problem Resolution: Verify the following:
1) The RCST has an IP address assigned in the NMS
2) Check to see if the IPE is working properly and the RCST has the proper
string in the command file of the IPE
3) Assign a channel of CIR to the RCST
4) Check Internet connectivity to the hub
5) Check RCST TXPower level to ensure that it isn't configured too high
(placing the BUC in saturation)
6) Check RCST and GCU BER to ensure proper link budget is maintained
4) Problem symptom: RCST Is in TX Sync however passing very little to no traffic
Component: RCSTs
Category: Software Configuration
Description: The user complains of DNS timeouts or unable to browse. The RCST is
assigned a public IP address and not a private (RFC 1918 address) IP address
Problem Resolution: It is possible that the RCST in question might be a subject of a Dos or DDoS
(Denial of Service or Distributed Denial of Service) attack from the OUTSIDE
1) Verify connections to/from the RCST via Allot box (if it is inline between
the PBR and the TX Switch)
a. Utilize the acstat -i | grep command and grep for the RCST IP subnet or
portion thereof
2) Block the destination port at the gateway router
3) Use ACLs (Access Control Lists) to block offending traffic prior to
reaching the DVB and the RCSTs
5) Problem symptom: High packet loss on a specific RCST
Component: RCSTs
Category: Software Configuration
Description: Terminal TX/RX BERs were checked and both were good. Terminal was
assigned CIR, problem persisted. Receiving GCU indicates CRC errors on
return channel

34
Problem Resolution: There is a possibility that the RCST has too high of a transmit power
configured
1) Increasing the RCST TXPower worsens the problem
2) Decreasing the RCST TXPower clears up the problem
a. Terminal was transmitting too hot and clipping signal
3) Verify antenna pointing and for proper BUC polarity alignment
6) Problem symptom: RCST IP Accounting records not being collected
Component: RCSTs
Category: Software
Description: A new GCU added to the network after region (RNCC) was started. The RCST
is running on that new GCU
Problem Resolution: TTP port not opened on newly added GCUs after the region has started.
Handover the RNCCs to restore
7) Problem symptom: RCST unable to gain TX Sync while in Maritime mode
Component: RCSTs
Category: Software
Software Version: 1.0.8 and higher
Description: All RCST bootconf parameters are correct, but SAT led remains in fast blink
and terminal fails to acquire network
Problem Resolution: Verify Maritime Mode operation
1) Telnet to the RCST via the static RCST IP address previously assigned per
the Maritime Mode operations as described in the LinkStar 1.0.8 Release
notes, ViaSat document 1003074_001
2) Perform a gps_getpos
3) Verify that the Latitude and Longitude updates are getting reported
correctly
4) If Latitude = 0, Longitude = 0 appears, check the Ethernet connection to
GPS
5) If the Maritime Mode functions do not work after viewing the "Notes On
Troubleshooting Maritime" in the 1.0.8 Release notes, disable the Maritime
Mode function via save -m 0 and call the LinkStar operator with updated
GPS coordinates to update the NMS configuration for that RCST site
8) Problem symptom: ss and prt ipqos RCST commands have different output displays
Component: RCSTs
Category: Software
Description: Comparison of the output display of the two commands is reversed
Problem Resolution: This is how the outputs of the ss vs. prt ipqos line up next to each other in
regards to precedence:
Usr 0 = Expedited Forwarding
Usr 1 = AC 1
Usr 2 = AC 2
Usr 3 = AC 3
Usr 4 = AC 4
Usr 5 = Best Effort
The outputs of each are reversed in regards to the display order because of
where they lie in the signal flow
9) Problem symptom: VPN Membership information remains after RCST is deleted
Component: NMS
Category: Software
35
Software Version: 1.0.8.14 and higher

Description: After a LinkStar RCST is deleted from the LinkStar NMS Console, the VPN
Membership information remains
Problem Resolution: This is not a bug however does occur occasionally
1) Delete the VPN Membership information for the RCST that is to be deleted
from the LinkStar NMS Console
2) Delete the RCST from the LinkStar NMS Console
10) Problem symptom: Traffic fails with MTU greater than 1476
Component: RCST
Category: Hardware
Description: RCST traffic with a MTU greater than 1476 will fail
Problem Resolution: The RCST MTU size is now hard coded to 1476 for both the Ethernet and
TDMA interfaces, to allow for the implementation of the VLAN feature on the
LinkStar system
1) This might pose issues with tunneling services such as GRE and any
application that sets the "Do Not Fragment”, or DF bit
2) This also poses a problems with encryption devices which do not change
the MTU size dynamically
3) For 1.0.8.14 LinkStar systems, the solution is to
a. Configure end devices with a MTU setting less than 1476
b. Configure a policy statement on a gateway router and the end routing
devices to clear the DF bit, in order to allow fragmentation
c. To configure a policy statement on a gateway router, enter in privileged
EXEC mode
i) Router # configure terminal
d. Create a route-map statement with a name of clear-df matching ACL
101
i) ACL 101, for example could read as:
(1) access-list 101 permit tcp any any
ii) Router(config)# route-map clear-df permit 10
iii) Router(route-map)# match ip address 101
iv) Router(route-map)# set ip df 0
e. Apply the route-map statement to the Router interface which accepts all
incoming packets to the LinkStar system (such as a gateway router)
i) Router(route-map)# interface ethernet 0 (as an example)
ii) Router(config-if)# ip policy route-map clear-df
f. Return to privileged EXEC mode and write the configuration to
memory
i) Router(config-if)# exit
ii) Router# write memory
g. (Optional) Save your entries in the configuration file
i) Router# copy running-config startup-config
a. Utilize a software patch release for RCSTs, which will set the MTU of
the RCST to 1500
i) When this RCST software patch is utilized, VLAN traffic will not
function
a. Utilize RCST software patch release 1.0.8.16p2

36
(1) This dynamically adjusts the MTU size of the RCST to 1500
for non-VLAN traffic and 1476 for VLAN traffic
configurations
b. Configure end devices with a MTU setting less than 1476
c. Configure a policy statement on a gateway router and the end routing
devices to clear the DF bit, in order to allow fragmentation
d. To configure a policy statement on a gateway router, enter in privileged
EXEC mode
i) Router# configure terminal
e. Create a route-map statement with a name of clear-df matching ACL
101
i) Router(config)# route-map clear-df permit 10
ii) Router(route-map)# match ip address 101
iii) Router(route-map)# set ip df 0
f. Apply the route-map statement to the Router’s interface
i) Router(route-map)# interface ethernet 0 (as an example)
ii) Router(config-if)# ip policy route-map clear-df
g. Return to privileged EXEC mode and write the configuration to
memory
i) Router(config-if)# exit
ii) Router# write memory
h. (Optional) Save your entries in the configuration file
i) Router# copy running-config startup-config
6) Contact the ViaSat Network Operations Center to obtain the appropriate
RCST software patch
11) Problem symptom: IP Supernetting is not supported on RCSTs
Component: RCST/NMS
Category: Hardware
Description: The IP Address of an RCST is configured with a supernet address, however
traffic fails
Problem Resolution: IP Supernetting at the RCST level is not supported on the LinkStar system.
RCSTs can be assigned CIDR (Classless Inter-Domain Routing) networks,
however not in the supernet category
1) For example, 10.10.10.1 with a subnet mask of 255.255.254.0 is not
supported, however 10.10.10.1 with a subnet mask of 255.255.255.0 or
255.255.255.224 or 255.255.255.248 is supported

37
Additional Troubleshooting Information

LinkStar Users Manual – Appendix B
Document ID USR00091_A http://extranet.viasat.com/vsat/linkstar/manuals/
1) Connecting to devices Page B-1

2) Troubleshooting GCUs Page B-1
3) Troubleshooting RCSTs Page B-3
a) General Approach Page B-3
b) Troubleshooting Page B-3
c) Local RCST Communications Page B-4
d) Network Synchronization Page B-4
e) All LEDs Off Page B-4
f) SAT LED Off Page B-5
g) SAT LED Blinking Page B-5
h) SAT LED Off Page B-4
4) Monitoring Hub Link Conditions Page B-7
a) GPS/10 MHz Reference Page B-7
b) DVB Modulator Page B-7
c) TDU Page B-8
d) IPE Page B-8
e) Multiplexer Page B-8
f) GCU Page B-8
g) Link Troubleshooting: Outbound Page B-9
h) Link Troubleshooting: Inbound Page B-9
i) Link Troubleshooting: Outbound Page B-9
j) Link Monitoring Page B-9
5) Monitoring Burst Reception Page B-10
6) Redundancy Equipment Page B-11
a) I/O Link Initial State of LEDs Page B-11
b) I/O Link Troubleshooting Page B-11
7) Terminal Server Page B-12
8) Modulator Redundancy Switch Page B-12
a) Slow Switching Page B-12
b) Installing Configuration File Page B-12
9) IP Encapsulator Page B-13
a) SMR Redundancy Page B-12
10) LDAP Installation Page B-14

38
Useful Commands
Cisco Switch troubleshooting commands
show int status
The show int status command lists the overall port status of the TX and/or RX Switches. This is a good
command to use to view how all of the ports are configured and their status. Ports that show a Duplex value of
a-full and a Speed value of a-100 means that the port is configured as Auto-Duplex, Auto-Speed and has
negotiated with the connected device (Say, a Sun Server) to a Full-Duplex, 100 Mbits/s Ethernet link.
show int Fa0/X
The show int command lists all of the particulars of a specific port. The items to look for are any of the error
fields, such as: input errors, CRC, frame, overrun, ignored, output errors, collisions, interface resets, babbles,
late collision, deferred lost carrier, no carrier, output buffer failures, output buffers swapped out and any input or
output queue drops. Any of those errors indicate specific problems on the Ethernet link and should be
troubleshot. Reference Cisco’s Ethernet troubleshooting guide at
http://www.cisco.com/warp/public/473/46.html
show vlan or show vlan brief
show vlan or show vlan brief gives information about the VLANs and the ports that belong to a
particular VLAN
show ver
The show ver command will provide you an overview of the switch’s software and memory configurations and
any failure codes that are present from prior software/hardware failures.
show controllers ethernet-controller fastEthernet
The show controllers ethernet-controller fastEthernet 0/1, 0/2 etc command lists in detail the statistics for the
Ethernet Controllers for the selected port.
Sun Server Solaris (UNIX) commands

prstat
prstat is a command that can be issued via the command line on the Sun servers to view the overall performance
of the server. prstat –a reports information about processes and users. In this mode prstat displays separate
reports about processes and users at the same time. The screen can be refreshed quicker by placing a number
after the command, which is in the format of seconds such as: prstat –a 2. This will refresh the screen every 2
seconds. The output should be viewed to ensure that there isn’t excessive CPU or Memory usage by any one
single command. The output is viewed sorted in a top to bottom fashion, where it is sorted by CPU usage in the
default mode. Other sub-commands are prstat –n, where an integer after the –n specifies the number of lines to
display. prstat –m reports microstate usage information.
df
As stated above, The df command displays the amount of disk space occupied by mounted or unmounted file
systems, the amount of used and available space, and how much of the file system's total capacity has been used.
Use df –k to display current partition usage listed in Kilo Bytes.
netstat
netstat displays the contents of certain network-related data structures in various formats, depending on the
options that are selected. Common options are -rn, as in netstat -rn. netstat -arn displays the routing tables (-r)
of the server in number format (-n) with all routes, including cache (-a). This is a useful command if you
believe you have a routing issue to/from the Sun server.
ls
ls lists the contents of the directory; for each file that is an ordinary file, ls repeats its name and any other
information requested. The output is sorted alphabetically by default. When no argument is given, the current
directory is listed. When several arguments are given, the arguments are first sorted appropriately, but file
arguments appear before directories and their contents. Common usage is ls -la, which lists files and sub-
directories in the long format (-l) and all entries (-a), even hidden files that begin with a dot (.).

39
Appendix A – Cisco 3660 Policy Based Router Configuration

The default configuration of the Cisco 3660 PBR is defined below
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname Linkstar_PBR
!
enable password 0 viasat
!
memory-size iomem 10
ip subnet-zero
!
!
!ip name-server x.x.x.x
!ip name-server x.x.x.x
!
lane client flush
!
!
interface FastEthernet0/0
description Connectivity to Customer Network
ip address 172.31.10.15 255.255.0.0
ip nat outside
ip pim sparse-mode
ip policy route-map pbr00
speed auto
duplex auto
no shutdown
!
description Connectivity to TCP Acceleration hme0
ip address 192.168.141.3 255.255.255.0
ip nat inside
speed 100
full-duplex
no shutdown
!
description Connectivity to TCP Acceleration hme1
ip address 192.168.142.3 255.255.255.0
ip nat inside
speed 100
full-duplex
no shutdown
!
description Connectivity to HUB LAN
ip address 192.168.150.51 255.255.255.0
ip pim sparse-mode
ip nat inside
speed 100
full-duplex
no shutdown
!
ip nat inside source list 10 interface FastEthernet0/0 overload
ip classless
ip route 0.0.0.0 0.0.0.0 172.31.254.254
ip route 10.253.0.0 255.255.0.0 192.168.150.50
ip route 10.254.0.0 255.255.0.0 192.168.150.50
no ip http server
!
access-list 10 deny 192.168.150.100
access-list 10 permit 10.254.0.0 0.0.255.255

40
access-list 101 permit tcp any any

access-list 103 permit tcp any 192.168.150.0 0.0.0.255
access-list 104 permit tcp 192.168.150.0 0.0.0.255 any
access-list 105 permit tcp 192.168.150.0 0.0.0.255 10.254.0.0 0.0.255.255
!
route-map pbr00 permit 10
match ip address 103
set interface FastEthernet1/1
!
set ip next-hop 192.168.141.1
!
!
!
!
!
set default interface Null0
!
!
!
line con 0
transport input none
line aux 0
line vty 0 4
exec-timeout 8 0
session-timeout 10
password viasat
login
!
end

41
Appendix B – Cisco 7206 Policy Based Router Configuration

The default configuration of the Cisco 7206 PBR without the VLAN implementation is defined below.
!
hostname Linkstar_PBR
!
boot-start-marker
boot-end-marker
!
enable password 0 viasat
!
no aaa new-model
ip subnet-zero
!
!
ip cef
!
!
ip multicast-routing
!
!
lane client flush
!
interface GigabitEthernet0/1
description Connectivity to Customer Network
ip address 172.31.10.12 255.255.0.0
ip pim sparse-mode
ip nat outside
ip virtual-reassembly
duplex full
speed 100
media-type rj45
no negotiation auto
!
description Connectivity to HUB LAN
ip address 192.168.150.51 255.255.255.0
ip pim sparse-mode
ip nat inside
duplex full
speed 100
media-type rj45
no negotiation auto
!
no ip address
shutdown
duplex auto
speed auto
media-type rj45
no negotiation auto
!
description Connectivity to TCP Acceleration bge2
ip address 192.168.141.3 255.255.255.0
ip nat inside
duplex full
speed 100
hold-queue 100 in
hold-queue 135 out
!

42
description connectivity to TCP Acceleration bge1

ip address 192.168.142.3 255.255.255.0
ip nat inside
duplex full
speed 100
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.31.254.254
ip route 10.253.0.0 255.255.0.0 192.168.150.50
ip route 10.254.0.0 255.255.0.0 192.168.150.50
no ip http server
!
ip pim rp-address 192.168.150.51
ip nat inside source list 10 interface GigabitEthernet0/1 overload
!
!
access-list 101 permit tcp any any
access-list 103 permit tcp any 192.168.150.0 0.0.0.255
access-list 104 permit tcp 192.168.150.0 0.0.0.255 any
!
set interface GigabitEthernet0/2
!
!
!
!
!
!
!
!
!
control-plane
!
dial-peer cor custom
!
!
gatekeeper
shutdown
!
!
line con 0

43
transport preferred all

transport output all
stopbits 1
line aux 0
stopbits 1
line vty 0 4
exec-timeout 8 0
session-timeout 10
password viasat
login
transport input all
!
!
end

44
Appendix C – Cisco 3550 TX Rack Switch Configuration

The default redundant LinkStar hub Cisco 3550 TX Rack Switch configuration, without VLAN implementation
is defined below.
no service pad
!
hostname LinkStar_TX_Switch
!
enable password 7 <removed>
!
ip subnet-zero
!
ip igmp snooping vlan 1 static 0100.5e40.0101 interface Fa0/1
ip igmp snooping vlan 1 static 0100.5e40.0103 in terface Fa0/4
!
!
spanning-tree mode pvst
spanning-tree extend system-id
no spanning-tree vlan 1
!
!
description Connected to NCC1
switchport mode dynamic desirable
!
description Connected to NCC2
!
description Connected to RNCC1
!
description Connected to RNCC2
!
description Connected to TCPACC1 eri0
!
description Connected to TCPACC2 eri0
!
description Connected to NMS PC
!
description Empty Port
!
description Connected to SMR 1 LAN 1
!
45

!
!
!
duplex full
speed 100
!
description Connected to PBR FE1/0
switchport access vlan 3
duplex full
speed 100
!
duplex full
speed 100
!
duplex full
speed 100
!
description Connected to TCPACC1 hme0
!
!
!
!
!
description Connected to LinkStar_Rx_Switch3
duplex full
speed 100
!
duplex full
speed 100
!

46

duplex full
speed 100
!
!
!
interface Vlan1
ip address 192.168.150.52 255.255.255.0
no ip route-cache
!
interface Vlan2
no ip address
!
interface Vlan3
no ip address
!
ip default-gateway 192.168.150.51
ip classless
ip http server
!
!
!
line con 0
line vty 0 4
password 7 <removed>
login
line vty 5 15
login
!
mac-address-table static <NCC1 eri0 MAC Address> vlan 1 interface FastEthernet0/1
mac-address-table static <NCC2 eri0 MAC Address> vlan 1 interface FastEthernet0/2
mac-address-table static <RNCC1 eri0 MAC Address> vlan 1 interface FastEthernet0/3
mac-address-table static <RNCC2 eri0 MAC Address> vlan 1 interface FastEthernet0/4
mac-address-table static <SMR 1 LAN 1 MAC Address> vlan 1 interface FastEthernet0/9
!
!
end

47
Appendix D – Cisco 3550 RX Rack Switch Configuration

The default redundant LinkStar hub Cisco 3550 RX Rack Switch configuration is defined below.
no service pad
!
hostname LinkStar_RX_Switch1
!
enable password 7 <removed>
!
ip subnet-zero
!
ip igmp snooping vlan 1 static 0100.5e40.0103 interface Fa 0/1
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
!
description Connected to GCU1
duplex half
speed 10
!
description Connected to GCU 2
duplex half
speed 10
!
duplex half
48
speed 10
!
duplex half
speed 10
!
duplex half
speed 10
!
duplex half
speed 10
!
duplex half
speed 10
!
duplex half
speed 10
!
duplex half
speed 10
!
duplex half
speed 10
!
duplex half
speed 10
!
duplex half
speed 10
!
duplex half
speed 10
!
duplex half
speed 10
!
duplex half
speed 10
!

49
duplex half
speed 10
!
!
!
!
!
!
!
!
description Connected to Linkstar_Tx_Switch
duplex full
speed 100
!
!
!
interface Vlan1
ip address 192.168.150.53 255.255.255.0
no ip route-cache
!
ip default-gateway 192.168.150.51
ip classless
ip http server
!
!
line con 0
line vty 0 4
login
line vty 5 15
login
!
!
end

50
If you have any questions about this bulletin, please contact our 24/7 Product Customer Support line at
+1-760-476-2600 (outside the U.S.), +1-888-272-7232 (in the U.S.), or send an e-mail to noc-
support@viasat.com.
Publication Information
ViaSat, Inc.
Corporate Headquarters Revision Number Date Released Comments

6155 El Camino Real
Carlsbad, CA 92009-1699
Phone: (760) 476-2200
Fax: (760) 929-3941 000 July 28, 2005 REQ-012663
Clarksburg, MD
22300 Comsat Drive
Clarksburg, MD 20871
Phone: (301) 428-4500
Fax: (301) 428-4700
Norcross, GA
4356 Communications Drive
Norcross, GA 30093-2999
Phone: (678) 924-2400
Fax: (678) 924-2480
© 2005 ViaSat, Inc. All rights reserved.

ViaSat Proprietary—Information in this document is subject to change without
notice. This document is proprietary to ViaSat, Inc., and shall be protected by a
receiving party in accordance with the terms of its contracts and agreements with
ViaSat, Inc., covering ViaSat products.
No part of this document may be reproduced or transmitted in any form or by any
means, electronic or mechanical, for any purpose, without the express written
permission of ViaSat, Inc.

51

000 - LinkStar - Troubleshooting Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

000 - LinkStar - Troubleshooting Guide

Uploaded by

Copyright:

Available Formats

LinkStar LinkStar IP LinkStar Troubleshooting Guide

LinkStar Troubleshooting Guide

1) LinkStar User Manual

Table of Contents – LinkStar Troubleshooting Guide

CONTACT INFORMATION: ..............................................................................................................1

LINKSTAR HCE (HUB COMMON EQUIPMENT) .........................................................................6

LINKSTAR NETWORK RELATED ISSUES ..................................................................................20

ViaSat Proprietary 1038741_000 (July 28, 2005

5) Problem symptom: VLAN traffic fails with Cisco CEF enabled............................................................................. 31

ADDITIONAL TROUBLESHOOTING INFORMATION .............................................................38

1038741_000 (July 28, 2005) ViaSat Proprietary

9) IP Encapsulator Page B-13 ......................................................................................................................... 38

APPENDIX A – CISCO 3660 POLICY BASED ROUTER CONFIGURATION .........................40

ViaSat Proprietary 1038741_000 (July 28, 2005

LinkStar HCE (Hub Common Equipment)

Policy Based Router

1038741_000 (July 28, 2005) ViaSat Proprietary

Cisco 3550 RX Rack Switch

ViaSat Proprietary 1038741_000 (July 28, 2005

LinkStar Knowledge Base Articles

1038741_000 (July 28, 2005) ViaSat Proprietary

4) Implement gateway/edge/border router access-lists to block known exploits

Router(config)# access-list 110 deny tcp any any eq 445

4) More information on this is described in the ViaSat Customer Service

While other disk partitions are set up as follows:

3) Problem symptom: NCC/RNCC/TCP PEP SNMP Failures

ViaSat Proprietary 1038741_000 (July 28, 2005

1038741_000 (July 28, 2005) ViaSat Proprietary

root 303 1 0 May 25 ? 0:39 /home/linkstar/snmp/bin/snmpdx -y -c

ViaSat Proprietary 1038741_000 (July 28, 2005

1038741_000 (July 28, 2005) ViaSat Proprietary

if [ "$SPOOFERPID" != "" ] ; then

if [ "$SPOOFERPID" != "" ] ; then

ViaSat Proprietary 1038741_000 (July 28, 2005

TDU/ITDU Specific Issues

4) Problem symptom: ITDU ASI Rate change, LinkStar Hub is unstable

ViaSat Proprietary 1038741_000 (July 28, 2005

1038741_000 (July 28, 2005) ViaSat Proprietary

ViaSat Proprietary 1038741_000 (July 28, 2005

LinkStar Network Related Issues

1038741_000 (July 28, 2005) ViaSat Proprietary

4) Problem symptom: LinkStar NMS Console is blank

ViaSat Proprietary 1038741_000 (July 28, 2005

6) Problem symptom: LinkStar NMS Console - Unable to process … message on diagnostic

1038741_000 (July 28, 2005) ViaSat Proprietary

ViaSat Proprietary 1038741_000 (July 28, 2005

b. For the group that needs to be restricted, select Read Only or No

1038741_000 (July 28, 2005) ViaSat Proprietary

GCU Specific Issues

6) In the “Enable/Disable Transport Input” window, select Disable

b. LinkStar_TX_Switch(vlan)# vlan vlan-id name vlan-name

1038741_000 (July 28, 2005) ViaSat Proprietary

5) Problem symptom: VLAN traffic fails with Cisco CEF enabled

RCST Specific Issues

1038741_000 (July 28, 2005) ViaSat Proprietary

(1) Replace AA.BB or AA.BB.CC with the last 2 or last 3 Octets

ViaSat Proprietary 1038741_000 (July 28, 2005

1038741_000 (July 28, 2005) ViaSat Proprietary

Software Version: 1.0.8.14 and higher

1038741_000 (July 28, 2005) ViaSat Proprietary

ViaSat Proprietary 1038741_000 (July 28, 2005

Additional Troubleshooting Information

1) Connecting to devices Page B-1