Satellite communications

routergal · ‎06-21-2004

Hello,

I am relatively new to this company and just inherited a WAN that has some challenges...I could use some advice.

I have 3 ships out at sea that access our network in Los Angeles for email and mainframe systems. Each ship is equipped with a cisco router. Cisco 1600. The router connects via (AT&T) to our C-Band provider...a Land Station then sends to a MTN Satellite to us in LA. When this fails (shadowing). It is then switched to what is called an InMarSat Satellite or (B-Sat) it uses a separate Cisco 1600 router that transmits to the Marlink (Earth Station) to the Satellite then to us via ISDN.

OK...now my problem is that the ships claim they can connect to our LA office but it only stay up for 1 min and 7 seconds.

I've checked with the satellite company and they have full access to dial out; my question is, what would you check on my end in the LA office and what would you check on the ships?

Any advice would be greatly appreciated.

Georg Pauwen · ‎06-21-2004

Hello,

the first thing I would try to find out is which side is initiating the disconnect. There might be some timeouts configured, hard to say. Can you post the configuration of one of the 1600s and of the router at the LA office ?

Regards,

Georg

routergal · ‎06-21-2004

This is the router in Los Angeles

User Access Verification

Username: admin

Password:

CCI_BSAT>en

Password:

CCI_BSAT#show config

Using 3591 out of 29688 bytes

!

version 12.2

service timestamps debug uptime

service timestamps log uptime

no service password-encryption

!

hostname CCI_BSAT

!

aaa new-model

!

aaa authentication login default local

aaa authentication ppp default local

aaa session-id common

enable secret xxxx

enable password xxxx

!

username harmony password 0 xxxx

username symphony password 0 xxxx

username admin privilege 15 password 0 xxxx

username serenity password 0 xxxx

ip subnet-zero

!

isdn switch-type basic-ni

!

interface Loopback0

description Harmony_BSAT_Link

ip address 192.168.6.2 255.255.255.0

ip directed-broadcast

!

interface Loopback1

description Symphony_BSAT_Link

ip address 192.168.7.2 255.255.255.0

ip directed-broadcast

!

interface Loopback2

description Serenity_BSAT_Link

ip address 192.168.8.2 255.255.255.0

ip directed-broadcast

!

interface BRI0

no ip address

encapsulation ppp

load-interval 30

dialer pool-member 1

isdn switch-type basic-ni

isdn spid1 31020304870101 2030487

isdn spid2 31020305720101 2030572

ppp authentication chap

!

interface Ethernet0

description CUatSEA Network

ip address 192.168.104.8 255.255.255.0

half-duplex

!

interface FastEthernet0

ip address 192.168.2.253 255.255.255.0

speed auto

half-duplex

!

interface Dialer1

no ip address

no cdp enable

!

interface Dialer2

description Connection_to_CH

ip unnumbered Loopback0

ip directed-broadcast

encapsulation ppp

dialer pool 1

dialer remote-name harmony

dialer idle-timeout 60

dialer wait-for-carrier-time 60

dialer-group 1

compress stac

ppp authentication chap

!

interface Dialer3

description Connection_to_Symphony

ip unnumbered Loopback1

ip directed-broadcast

encapsulation ppp

dialer pool 1

dialer remote-name symphony

dialer idle-timeout 60

dialer wait-for-carrier-time 60

dialer-group 2

compress stac

ppp authentication chap

!

interface Dialer4

description Connection_to_Serenity

ip unnumbered Loopback2

ip directed-broadcast

encapsulation ppp

dialer pool 1

dialer remote-name serenity

dialer idle-timeout 60

dialer wait-for-carrier-time 60

dialer-group 3

compress stac

ppp authentication chap

!

ip classless

ip route 10.1.2.0 255.255.255.0 192.168.7.1

ip route 10.1.2.2 255.255.255.255 192.168.7.1

ip route 10.2.1.0 255.255.255.0 192.168.6.1

ip route 10.2.1.7 255.255.255.255 192.168.6.1

ip route 10.3.1.0 255.255.255.0 192.168.8.1

ip route 10.3.1.7 255.255.255.255 192.168.8.1

ip route 192.168.6.1 255.255.255.255 Dialer2

ip route 192.168.7.1 255.255.255.255 Dialer3

ip route 192.168.8.1 255.255.255.255 Dialer4

ip route 192.168.100.0 255.255.255.0 192.168.7.1

ip route 192.168.100.4 255.255.255.255 192.168.7.1

ip route 192.168.101.0 255.255.255.0 192.168.6.1

ip route 192.168.101.4 255.255.255.255 192.168.6.1

ip route 192.168.102.0 255.255.255.0 192.168.8.1

ip route 192.168.102.4 255.255.255.255 192.168.8.1

ip route 192.168.104.0 255.255.255.0 192.168.104.9

ip route 192.168.105.0 255.255.255.0 192.168.104.9

ip route 192.168.106.0 255.255.255.0 192.168.104.9

no ip http server

!

access-list 101 permit ip host 192.168.2.22 host 10.2.1.7

access-list 101 permit ip host 192.168.104.10 host 192.168.100.4

access-list 102 permit ip host 192.168.2.22 host 10.1.2.2

access-list 102 permit ip host 192.168.105.10 host 192.168.101.4

access-list 103 permit ip host 192.168.2.22 host 10.3.1.7

access-list 103 permit ip host 192.168.106.10 host 192.168.102.4

dialer-list 1 protocol ip list 101

dialer-list 2 protocol ip list 102

dialer-list 3 protocol ip list 103

!

line con 0

line aux 0

line vty 0 4

password xxxx

!

end

smif101 · ‎06-21-2004

I would take out the command dialer wait-for-carrier-time 60. That command is only to be used with async interfaces and not BRI's. Try it and see if it helps.

Jason Smith

www.smif101.com

dbellazetin · ‎06-25-2004

I wouldn't worry about the carrier timeout command. That wouldn't have an effect on this problem. Since this handed to you via ISDN you can run the following debugs to see what is initiating the disconnect.

debug dialer - To see interesting traffic flow. If traffic passes, but it not interesting the idle timer will tick until it expires.

debug isdn q931 - Shows call set up/ tear down. This will show an ISDN disconnect message and whether it was received or transmitted.

debug ppp neg - This will show if the termination request is via LCP TermReq

This will help you narrow things down. While connections are up you can also use "show caller timeout" to see the current idle timer to verify that the idle timer is working properly.

Hope this helps.

Dan

dbellazetin@hotmail.com