Table Of Contents
Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
Prerequisites for the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
Restrictions for the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
Information About the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
General Satellite Network Components
Satellite Network Management and Provisioning
Outbound and Inbound Directions in a Satellite Communications Network
NM-1VSAT-GILAT Network Module LEDs
How to Configure the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
Configuring the Initial VSAT Parameters for the NM-1VSAT-GILAT Network Module
Configuring IP Addresses for the Router Satellite Interface and the NM-1VSAT-GILAT Network Module
Configuring IP Addresses Locally
Configuring IP Addresses from the Hub
Compatibility Between Local Configuration and Configuration from the Hub
Verifying Satellite Network Connectivity for the NM-1VSAT-GILAT Network Module
Troubleshooting Satellite Network Connectivity for the NM-1VSAT-GILAT Network Module
Enabling or Disabling VSAT Route Update Messages to the Hub from the NM-1VSAT-GILAT Network Module
Configuring Hub Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link
Verifying Hub Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link
Configuring Router Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link
Configuring Router Dial Backup by Using a Floating Static Route
Configuring Router Dial Backup by Using a Backup Interface
Verifying Router Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link
Configuring NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link
Configuring Satellite Backup by Using a Floating Static Route
Configuring Satellite Backup by Using a Backup Interface
Verifying NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link—Backup Interface
Configuring HSRP Redundancy for the NM-1VSAT-GILAT Network Module
Configuring Homogeneous HSRP Redundancy with the NM-1VSAT-GILAT Network Module
Configuring Heterogeneous HSRP Redundancy with the NM-1VSAT-GILAT Network Module
Verifying HSRP Redundancy for the NM-1VSAT-GILAT Network Module
Troubleshooting HSRP Redundancy for the NM-1VSAT-GILAT Network Module
Configuring IP Multicast Routing for the NM-1VSAT-GILAT Network Module
Troubleshooting Voice over IP for the NM-1VSAT-GILAT Network Module
Dedicated Access (DA) and Random Access (RA) Modes
Requirements for Automatic Activation and Deactivation of DA Mode
Configuration of Optimum Codec Payload Size in DA Mode
Configuring Integrated TCP Acceleration and Encryption
Configuring the VSAT Router for ITAE
Configuration Examples for the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
Configuring Homogeneous HSRP Redundancy with the NM-1VSAT-GILAT Network Module—Shared ODU: Example
Configuring IP Multicast Routing for the NM-1VSAT-GILAT Network Module: Example
apply (satellite initial configuration)
end (satellite initial configuration)
exit (satellite initial configuration)
password (satellite initial configuration)
service-module backup interface
service-module routing redistribute
service-module satellite backup
service-module satellite configuration
service-module satellite cw-mode
service-module satellite status
show (satellite initial configuration)
test satellite satellite mfg link
Feature Information for the Cisco IP VSAT Satellite WAN Network Module
Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
OL-5899-02First Published: June 12, 2006Last Updated: June 20, 2007The NM-1VSAT-GILAT network module provides Cisco modular access routers with two-way satellite WAN connectivity in Gilat© SkyEdge© or compatible satellite communications networks. The NM-1VSAT-GILAT network module functions as the indoor unit (IDU) of a very small aperture terminal (VSAT), or earthbound station of a satellite communications network. A "very small" dish antenna is called the outdoor unit (ODU) of a VSAT. As the IDU, the NM-1VSAT-GILAT network module serves as the interface between the ODU and the VSAT LAN. The ODU receives and sends signals to a satellite, and the satellite sends and receives signals from an earthbound central hub, which controls the entire operation of the satellite network.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for the Cisco IP VSAT Satellite WAN Network Module" section.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
•
•
•
•
•
Prerequisites for the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
•
–
–
–
•
–
–
•
–
–
–
–
See the "Configuring the Initial VSAT Parameters for the NM-1VSAT-GILAT Network Module" section for more details.
•
•
•
Note
Restrictions for the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
•
Note
•
–
–
–
•
–
–
•
•
•
–
–
–
•
–
–
–
•
–
–
–
For information about these voice applications, see the Cisco IOS Voice Configuration Library.
•
•
•
For more information about using FTP, see the "Copying an Image from an FTP Server to a Flash Memory File System" section of the "Loading and Maintaining System Images" chapter of the Cisco IOS Configuration Fundamentals Configuration Guide.
•
–
–
Note
Information About the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
To configure the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT) feature, you should understand the following concepts:
•
•
•
•
Note
General Satellite Network Components
Figure 1 shows a satellite communications network that includes NM-1VSAT-GILAT network modules.
Note
Figure 1 Satellite Communications Network Using the NM-1VSAT-GILAT Network Module
At a high level, the many components of an enterprise satellite communications network can be divided into three categories:
•
Satellite
Placed in orbit around the earth, a satellite is a specialized repeater that receives radio-frequency signals from earth stations and retransmits them to other earth stations. The satellite also amplifies the signals and switches the frequencies between the uplink and the downlink carriers. Gilat SkyEdge systems use geostationary satellites with a fixed satellite-to-earth delay of about 250 ms.
Hub
The central hub—sometimes referred to as the "master earth station" but most often simply called the "hub"—contains many components, including:
•
•
•
•
Note
VSATs
A very small aperture terminal (VSAT) is an earth station that can be divided into two areas:
•
–
–
–
•
The NM-1VSAT-GILAT network module functions as the IDU of a VSAT and is connected to the ODU through coaxial cables. A power supply is connected to the NM-1VSAT-GILAT network module to provide power over the coaxial cables to the ODU.
Figure 2 ODU Components
Satellite Network Management and Provisioning
The satellite network is provisioned and managed primarily from the central hub, where the network management system (NMS) is used to manage satellite access, configure the VSAT software on the NM-1VSAT-GILAT network module, and monitor and control all components of the satellite network.
From the VSAT, the Cisco IOS software on the router is used to perform the initial configuration of the NM-1VSAT-GILAT network module to establish the backbone link to the hub. The Cisco IOS software is also used to configure VSAT IP addresses and Cisco IOS software features. Some features require configuration from both the hub NMS and the VSAT router Cisco IOS software.
You can use the following tools to monitor your NM-1VSAT-GILAT network module from the VSAT:
•
•
•
Outbound and Inbound Directions in a Satellite Communications Network
The outbound direction applies to signals transmitted from the hub to the VSAT. Within a VSAT network, the outbound direction applies to RF communication from the dish antenna (ODU) to the NM-1VSAT-GILAT network module (IDU). From the VSAT perspective, the outbound direction is the receive path. Gilat SkyEdge outbound signals include user data and timing data that are compatible with the Digital Video Broadcasting-Satellite (DVB-S) standard.
The inbound direction applies to signals transmitted from the VSAT to the hub. Within a VSAT network, the inbound direction applies to RF communication from the NM-1VSAT-GILAT network module to the dish antenna. From the VSAT perspective, the inbound direction is the transmit path. Inbound signals include user data and retransmission requests.
NM-1VSAT-GILAT Network Module LEDs
The NM-1VSAT-GILAT network module has six LEDs, shown in Figure 3 and described in Table 1.
Figure 3 NM-1VSAT-GILAT Network Module LEDs
Table 1 NM-1VSAT-GILAT Network Module LED Descriptions
1
EXT DC
Blinking
ODU power DC level is correct, and the VSAT1 software on the network module is running.
Normal indication. No action required.
Steady on
ODU power supply is connected properly, but the VSAT software on the network module is not running.
Wait until the VSAT software completes the boot process.
Off
ODU power supply is not connected or is outside the specified DC range.
Check ODU power supply connections. See the "Connecting Cisco IP VSAT Satellite WAN Network Modules" chapter of the Cisco Network Modules Hardware Installation Guide.
2
RX LOCK
On
Normal indication. No action required.
Off
NM-1VSAT-GILAT network module does not see or recognize the DVB carrier signal from the hub.
The VSAT parameters are configured incorrectly. See the "Configuring the Initial VSAT Parameters for the NM-1VSAT-GILAT Network Module" section.
The network module is not properly connected to the LNB.4 Check the RF5 cables or contact your satellite service provider.
The dish antenna is misaligned. Contact your satellite service provider.
There is a hub failure, or the hub is configured incorrectly. Contact your satellite service provider.
3
SYNC
On
NM-1VSAT-GILAT network module is synchronized with the hub timing.
Normal indication. No action required.
Off
NM-1VSAT-GILAT network module is not synchronized with the hub timing.
If the RX LOCK LED is also off, then see the corrective actions for RX LOCK.
If the RX LOCK LED is on while the SYNC LED is off, then the following apply:
•
•
4
ON LINE
On
IP connectivity to the hub is fully established.
Normal indication. No action required.
Off
IP connectivity to the hub was unsuccessful.
If the SYNC LED is also off, then see the corrective actions for SYNC.
If the SYNC LED is on while the ON LINE LED is off, then the following apply:
•
•
•
•
5
TX
Flickering
Inbound7 transmission is in progress.
Normal indication. No action required.
Off
No inbound transmission is in progress.
If you are concerned about the TX LED being off, then try to ping the hub or another destination on the other side of the satellite link. If the TX LED does not flicker during the ping, then the network module is not attempting to send data to the hub.
•
•
•
6
EN
On
The router Cisco IOS software recognizes the network module.
Normal indication. No action required.
Off
The router Cisco IOS software does not recognize the network module.
Verify that the network module is properly installed in the router chassis. See the "Installing Cisco Network Modules in Cisco Access Routers" chapter of the Cisco Network Modules Hardware Installation Guide.
1 VSAT = very small aperture terminal
2 DVB = Digital Video Broadcasting
3 The receive direction at the remote VSAT is called the outbound direction from the hub. See the "Outbound and Inbound Directions in a Satellite Communications Network" section.
4 LNB = low noise block converter
5 RF = radio frequency
6 SSPA = solid state block converter and power amplifier
7 The transmit direction at the remote VSAT is called the inbound direction to the hub. See the "Outbound and Inbound Directions in a Satellite Communications Network" section.
How to Configure the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
This section contains the following procedures:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Configuring the Initial VSAT Parameters for the NM-1VSAT-GILAT Network Module
This section describes how to perform the initial configuration of VSAT parameters that are required for the NM-1VSAT-GILAT network module to establish a satellite backbone link to the hub. Typically, this task is performed only once by an installation technician.
After the NM-1VSAT-GILAT network module establishes a link to the hub, the satellite network management system at the hub is used to configure the VSAT software on the NM-1VSAT-GILAT network module.
The initial VSAT parameters are saved directly to the nonvolatile memory on the NM-1VSAT-GILAT network module. The commands do not appear in the router configuration, even though you configure the parameters through the Cisco IOS CLI.
Note
Prerequisites
•
•
–
–
Restrictions
If an installation technician performs this configuration task, then do not attempt to further modify the parameters, and proceed directly to the "Configuring IP Addresses for the Router Satellite Interface and the NM-1VSAT-GILAT Network Module" section.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
or
no mode download8.
or
no mode two-way9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
or
end20.
DETAILED STEPS
Step 1
enable
Example:Router> enable
(Optional) Enables privileged EXEC mode.
•
Note
Step 2
service-module satellite slot/0 configuration
Example:Router# service-module satellite 1/0 configuration
Enters satellite initial configuration mode.
Step 3
Enter the password.
Example:Password: <mypassword>
Reminder: changing any parameters will result in a software reset of the module.
If this is the first time you are accessing this mode, enter the VSAT initial configuration mode password supplied by the service provider. Otherwise, enter the user-defined password.
Step 4
id aa-group number
Example:Router(sat-init-config)# id aa-group 336
Configures the asynchronous acknowledgement group ID.
•
Step 5
id software group number
Example:Router(sat-init-config)# id software group 598
Configures the operational software group ID.
•
Step 6
id vsat number
Example:Router(sat-init-config)# id vsat 1284
Configures the component physical address (CPA).
•
•
Note
Step 7
mode download
or
no mode download
Example:Router(sat-init-config)# mode download
Enables operational code download mode for the NM-1VSAT-GILAT network module.
or
Disables operational code download mode for the NM-1VSAT-GILAT network module.
Step 8
mode two-way
or
no mode two-way
Example:Router(sat-init-config)# mode two-way
Specifies two-way operational mode.
or
Specifies one-way operational mode. This mode is used with third-party hubs. The NM-1 VSAT-GILAT network module is able to operate only outbound (from hub to VSAT) for user traffic when third-party hubs are used.
Step 9
outbound pid management number
Example:Router(sat-init-config)# pid management 3000
Specifies the outbound packet identifier (PID).
•
Step 10
outbound data-rate rate
Example:Router(sat-init-config)# outbound data-rate 450000
Specifies the outbound data rate.
•
Step 11
outbound frequency frequency
Example:Router(sat-init-config)# outbound frequency 950000
Specifies the outbound frequency.
•
Step 12
outbound id number
Example:Router(sat-init-config)# outbound id 95
Specifies the outbound VSAT ID.
•
Step 13
outbound modulation-type {DVB | TURBO_QPSK | 8PSK}
Example:Router(sat-init-config)# outbound modulation-type DVB
Specifies the outbound modulation type.
Step 14
outbound sync ip address address
Example:Router(sat-init-config)# outbound sync ip address 10.2.2.2
Specifies the outbound synchronization IP address.
Step 15
outbound viterbi-rate {1/2 | 1/4 | 2/3 | 3/4 | 3/4(2.05) | 3/4(2.1) | 3/4(2.6) | 5/6 | 6/7 | 7/8 | 8/9}
Example:Router(sat-init-config)# outbound viterbi-rate 3/4(2.6)
Specifies the outbound Viterbi code rate.
Step 16
password <new password>
Example:Router(sat-init-config)# password vsatuser
(Optional) Sets the user-defined password for VSAT initial configuration mode. The command is used the first time this mode is accessed to replace the factory-installed default password with your user-defined password.
Step 17
show
Example:Router(sat-init-config)# show
Displays the initial configuration parameters for the NM-1VSAT-GILAT network module.
•
Step 18
apply
Example:Router(sat-init-config)# apply
Applying changed parameters to the satellite module.Parameter update succeeded. Module is now resetting.Example:Router(sat-init-config)# apply
% No new or changed parameters to apply.
(Optional) Saves any changed parameters to the NM-1VSAT-GILAT network module nonvolatile memory, and resets the NM-1VSAT-GILAT network module.
•
Step 19
exit
or
end
Example:Router(sat-init-config)# exit
Exits satellite initial configuration mode, saves any changed parameters to the NM-1VSAT-GILAT network module nonvolatile memory, and resets the NM-1VSAT-GILAT network module.
•
Step 20
service-module satellite slot/0 status
Example:Router# service-module satellite 1/0 status
Displays status information related to the hardware and software on the NM-1VSAT-GILAT network module.
•
•
Examples
This section provides the following examples:
•
•
•
•
apply Command: Sample Output
The following example shows what appears when you enter the apply command after changing some initial configuration parameters:
Router(sat-init-config)# applyApplying changed parameters to the satellite module.Parameter update succeeded. Module is now resetting.Router(sat-init-config)#The following example shows what appears when you enter the apply command when no parameters have been changed:
Router(sat-init-config)# apply% No new or changed parameters to apply.Router(sat-init-config)#show (satellite initial configuration) Command: Sample Output
The following example shows the satellite initial configuration parameters:
Router(sat-init-config)# show!! Initial Configuration Parameters:!id aa-group 298id software group 598id vsat 6201mode downloadmode two-wayoutbound data-pid 514outbound data-rate 15000000outbound frequency 1201000outbound id 2outbound modulation-type DVBoutbound sync ip address 172.16.0.3outbound viterbi-rate 1/2!!Router(sat-init-config)#end or exit Command in Satellite Initial Configuration Mode: Sample Output
The following example shows what appears when you enter the end or exit command after changing one or more initial configuration parameters:
Router(sat-init-config)# endApplying changed parameters to the satellite module.Parameter update succeeded. Module is now resetting.Router#The following example shows what appears when you enter the end or exit command when no parameters have been changed:
Router(sat-init-config)# endRouter#service-module satellite status Command—Normal Operational Mode: Sample Output
The following example shows that the link to the hub (BackBone Status) is up, indicating that you correctly configured the initial VSAT parameters:
Router# service-module satellite 2/0 statusGetting status from the satellite module, please wait..Software Versions, OS:15.4.5.12, RSP:3.4.5.5, MBC:2.0.4.3HW Version:00008000CPA Number:6101, DPS CPA:5Workgroup: 257, SW Group: 512, Download: YESService Module Uptime:00:06:40, Router Uptime:1 day, 20 hours, 26 minutesCurrent router clocktime:*03:11:22.641 UTC Tue Dec 2 2003Oper Mode:OPERATIONAL, In Dial Backup:NO, Standby:NO, One-Way:NORBCP Received Packets:44, RBCP Sent Packets:41Bit Error Rate:0e-0, Signal to Noise Ratio:12.4453IP Address/Mask:10.22.1.1/255.255.255.252Service Module MAC:00:A0:AC:00:20:60RX Lock:LOCKED, Sync Lock:LOCKEDBackBone Status:UP, Two-Way Mode:YES, DA/RA Mode:RAOutbound Modulation Type:DVB, OB Code Rate:3/4Outbound Unicast Packets:61, OB Multicast Packets:23547Outbound ID:2, OB PID:514, OB Freq:1201000, OB Bit Rate:30000000Outbound Sync IP address: 172.22.0.3Inbound Start Freq:1201176, IB Stop Freq:1209336Inbound Data Rate:307200, IB Freq Offset:0Inbound Packets:3553BackBone Hub Link Status:UPBackBone Received Packets:1, BB Sent:3552BackBone Received Retransmitted:0, BB Sent Retrans:0Service Module Eth RX:3550, TX:47110Service Module Eth Multicast RX:1, Multicast TX:23563Bufs Configured:5000, Bufs Free:4951Internal Software State parameters:Service Module SW State Var:3General IOS FSM:LINK_UP, HSRP FSM:ACTIVE, HSRP VSAT Mode:ACTIVELost Beats Total:0, Lost Beats This Retry:0VOIP DA calls:NONERouter#service-module satellite status Command—During Reset Process: Sample Output
The following examples show what would appear if the NM-1VSAT-GILAT network module was still resetting itself when you entered the service-module satellite status command:
Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..% Satellite1/0 card is busy. Status is not available. Try later.Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS: 15.4.5.12, RSP: 0.0.0.0, MBC: 2.0.4.3HW Version: 00008000CPA Number: 6103, DPS CPA: 0Workgroup: 257, SW Group: 513, Download: YESService Module Uptime: 00:00:20, Router Uptime: 4 days, 4 hours, 29 minutesCurrent router clocktime: *19:07:35.935 UTC Tue Jul 11 2006Oper Mode: BOOT, In Dial Backup: NO, Standby: NORBCP Received Packets: 0, RBCP Sent Packets: 0Eb/No: 10.9283, Flags: 0xEEEEIP Address/Mask: 0.0.0.0/0.0.0.0Service Module MAC: 00:A0:AC:06:15:00RX Lock: LOCKED, Sync Lock: NOT LOCKEDBackBone Status: DOWN, Two-Way Mode: YES, Access Mode: INVALIDOutbound Modulation Type: DVB, OB Code Rate: 3/4Outbound Unicast Packets: 0, OB Multicast Packets: 0Outbound ID: 2, OB PID: 514, OB Freq: 1201000, OB Bit Rate: 30000000Outbound Sync IP address: 172.2.0.3Inbound Start Freq: 1190140, IB Stop Freq: 1193710Inbound Data Rate: 768000, IB Freq Offset: 0COUNTERS OMITTED. Not available at this time.Internal Software State parameters:Service Module SW State Var: 0General IOS FSM: LINK_DOWN, HSRP FSM: N/A, HSRP VSAT Mode: N/ALost Beats Total: 176, Lost Beats This Retry: 0VOIP DA calls:NONETroubleshooting Tips
Make sure that you configure the exact satellite initial configuration parameters that are provided by your satellite service provider. To view the configured parameter values, use one of the following commands:
•
•
What to Do Next
Proceed to the "Configuring IP Addresses for the Router Satellite Interface and the NM-1VSAT-GILAT Network Module" section.
Configuring IP Addresses for the Router Satellite Interface and the NM-1VSAT-GILAT Network Module
This section describes how to configure the two IP addresses that are required to use the NM-1VSAT-GILAT network module. The two required IP addresses are:
•
•
The two methodologies that perform this configuration are:
•
•
Either methodology may be used. See the "Compatibility Between Local Configuration and Configuration from the Hub" section.
Configuring IP Addresses Locally
This section describes how to implement configuration of the IP addresses locally. The IP address for the router satellite interface is configured with the ip address command. The IP address for the NM-1VSAT-GILAT network module is configured with the service-module ip address command.
Both the ip address command and the service-module ip address command are entered in satellite interface configuration mode.
Note
Automatically Configured IP Address and Mask for the NM-1VSAT-GILAT Network Module
If you configure the router satellite interface with an IP address and subnet mask with these conditions:
•
•
then the system automatically configures the IP address and subnet mask on the NM-1VSAT-GILAT network module with these results:
•
•
You can override the automatically configured IP address and mask by manually entering the service-module ip address command.
Note
IP Address Requirements for IP Multicast and Non-RIPv2 Routing Protocols
If you use Protocol Independent Multicast (PIM) or any unicast routing protocols other than Routing Information Protocol Version 2 (RIPv2) on the satellite interface, then you must configure IP addresses and subnet masks as follows:
•
•
To satisfy the above requirements, use the following rules to configure IP addresses:
•
•
Tip
See Figure 4 for sample IP address assignments that enable support of PIM and non-RIPv2 routing protocols on the satellite network.
Figure 4 Sample IP Addresses for PIM or Unicast Routing Protocols Other Than RIPv2
Restrictions
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
interface satellite slot/0
Example:Router(config)# interface satellite 1/0
Enters satellite interface configuration mode.
Step 4
ip address address mask
Example:Router(config-if)# ip address 10.0.0.6 255.255.255.0
Sets the IP address for the router satellite interface, which is the internal interface that connects the router to the installed NM-1VSAT-GILAT network module.
Step 5
service-module ip address address mask
Example:Router(config-if)# service-module ip address 10.0.0.1 255.255.255.252
(Optional) Sets the IP address for the NM-1VSAT-GILAT network module.
•
%VSAT-6-PIMINCOMPADDR:The IP address configured on Satellite1/0 requires a manually configured IP address for the satellite module•
•
Step 6
end
Example:Router(config-if)# end
Returns to privileged EXEC mode.
Step 7
show running-config | begin Satellite
Example:Router# show running-config | begin Satellite
Displays the running configuration, beginning with the first line that contains the text string "Satellite".
•
•
Step 8
ping router-sat-int-address
Example:Router# ping 10.0.0.6
Assesses basic network connectivity.
•
Step 9
ping satellite-nm-address
Example:Router# ping 10.0.0.1
Assesses basic network connectivity.
•
Examples
This section provides the following examples:
Configuring IP Addresses for the Router Satellite Interface and the NM-1VSAT-GILAT Network Module:
Using the Automatically Configured IP Address for the NM-1VSAT-GILAT Network Module: ExampleIn the following example, the router satellite interface IP address is configured as 10.0.0.6. Because the last octet of the IP address leaves a remainder of 2 when divided by 4, the system automatically configures the IP address for the NM-1VSAT-GILAT network module.
Although the NM-1VSAT-GILAT network module IP address and mask do not appear in the router configuration, you know that the IP address is 1 less than the IP address of the router satellite interface and has a subnet mask of /30. In this case, the NM-1VSAT-GILAT network module is automatically configured with the following IP address and mask: 10.0.0.5 255.255.255.252.
!interface Satellite 1/0ip address 10.0.0.6 255.255.255.0!Configuring IP Addresses for the Router Satellite Interface and the NM-1VSAT-GILAT Network Module:
Overriding the Automatically Configured IP Address for the NM-1VSAT-GILAT Network Module: ExampleIn the following example, the router satellite interface IP address is configured as 10.0.0.6. Because the last octet of the IP address leaves a remainder of 2 when divided by 4, the system automatically configures the IP address and mask for the NM-1VSAT-GILAT network module as 10.0.0.5 255.255.255.252.
Nevertheless, the NM-1VSAT-GILAT network module IP address and mask are manually configured as 10.0.0.1 255.255.255.0 to override the automatically derived IP address and mask. Notice that the IP addresses for both the router satellite interface and the NM-1VSAT-GILAT network module appear in the running configuration.
!interface Satellite 1/0ip address 10.0.0.6 255.255.255.0service-module ip address 10.0.0.1 255.255.255.0!Configuring IP Addresses for the Router Satellite Interface and the NM-1VSAT-GILAT Network Module:
Manually Configuring Both IP Addresses: ExampleIn the following example, the router satellite interface is assigned an IP address (10.0.0.7), the last octet of which does not leave a remainder of 2 when divided by 4. The system displays a message to manually configure the IP address for the NM-1VSAT-GILAT network module. Notice that the IP addresses for both the router satellite interface and the NM-1VSAT-GILAT network module appear in the running configuration.
Router(config)# interface satellite 1/0Router(config-if)# ip address 10.0.0.7 255.255.255.0%VSAT-6-PIMINCOMPADDR:The IP address configured on Satellite1/0requires a manually configured IP address for the satellite moduleRouter(config-if)# service-module ip address 10.0.0.6 255.255.255.0Router(config-if)# endRouter# show running-config | begin Satelliteinterface Satellite 1/0ip address 10.0.0.7 255.255.255.0service-module ip address 10.0.0.6 255.255.255.0...Troubleshooting Tips
•
•
–
–
What to Do Next
Proceed to the "Verifying Satellite Network Connectivity for the NM-1VSAT-GILAT Network Module" section.
Configuring IP Addresses from the Hub
This section describes how to implement centralized configuration of the VSAT module IP addresses from the hub. The IP address is configured at the hub NMS by the satellite service provider. The satellite interface is configured with DHCP to obtain the IP address from the VSAT module. A DHCP server is part of the VSAT firmware, and has to be enabled by the service provider.
Because the IP address for the NM-1VSAT-Gilat network module is configured remotely from the hub, the service-module ip address command, which is used to configure the network module locally, is disabled in centralized IP address configuration.
Prerequisites
Your service provider must do the following:
•
•
To verify that all of this is done, examine the value of the Flags parameter in the service module status output.
Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS: 15.4.5.12, RSP: 3.4.5.5, MBC: 2.0.4.3HW Version: 00008000CPA Number: 6101, DPS CPA: 5Workgroup: 257, SW Group: 513, Download: YESService Module Uptime: 00:01:16, Router Uptime: 2 days, 22 hours, 58 minutesCurrent router clocktime: *04:08:44.310 UTC Mon Mar 4 2002Oper Mode: OPERATIONAL, In Dial Backup: NO, Standby: NORBCP Received Packets: 33, RBCP Sent Packets: 38Eb/No: 10.9324, Flags: 0x0007IP Address/Mask: 10.0.0.1/255.255.255.252Service Module MAC: 00:A0:AC:06:14:EDRX Lock: LOCKED, Sync Lock: LOCKEDBackBone Status: UP, Two-Way Mode: YES, Access Mode: RA. . .Table 2 gives the values and interpretations of the Flag bits.
When all of these bits are on (giving the Flags parameter a cumulative value of 0x0007), the NM-1VSAT-GILAT network module can assign the IP address to the satellite interface.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
What to Do Next
Proceed to the "Verifying Satellite Network Connectivity for the NM-1VSAT-GILAT Network Module" section.
Compatibility Between Local Configuration and Configuration from the Hub
If you attempt to configure the satellite interface locally with an address that does not match the address that has already been configured at the hub, the hub address will take precedence, and an error message describing the condition will be generated. To configure the IP address locally, the VSAT IP address at the hub should be configured to 0.0.0.0.
Verifying Satellite Network Connectivity for the NM-1VSAT-GILAT Network Module
This section describes how to verify that your router can connect to the satellite communications network using the NM-1VSAT-GILAT network module.
Prerequisites
Complete the tasks in these sections:
•
•
SUMMARY STEPS
1.
2.
3.
or
telnet {host-name | ip-address}
or
tracerouteDETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
service-module satellite slot/0 status
Example:Router# service-module satellite 1/0 status
Displays status information related to the hardware and software on the NM-1VSAT-GILAT network module.
•
–
–
–
Step 3
ping {host-name | ip-address} source lan-ip-address
or
telnet {host-name | ip-address}
or
traceroute
Example:Router# ping 172.16.0.4 source 10.2.0.1
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
Note
1 Use the IP address of any interface on your router except for the IP addresses assigned to the NM-1VSAT-GILAT network module and to the router satellite interface.
Examples
This section provides the following examples:
•
•
service-module satellite status Command: Sample Output
The following example shows that the backbone link to the hub is up, and that the NM-1VSAT-GILAT network module is not in hub dial backup mode or in Hot Standby Router Protocol (HSRP) standby mode. This means that the NM-1VSAT-GILAT network module has, in fact, established a connection to the hub over the satellite link (air).
Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS: 15.4.5.12, RSP: 3.4.5.5, MBC: 2.0.4.3HW Version: 00008000CPA Number: 6101, DPS CPA: 5Workgroup: 257, SW Group: 513, Download: YESService Module Uptime: 00:00:55, Router Uptime: 3 days, 22 hours, 3 minutesCurrent router clocktime: *03:13:01.924 UTC Tue Mar 5 2002Oper Mode: OPERATIONAL, In Dial Backup: NO, Standby: NORBCP Received Packets: 14, RBCP Sent Packets: 13Eb/No: 10.9483, Flags: 0x0007IP Address/Mask: 9.0.0.1/255.255.255.252Service Module MAC: 00:A0:AC:06:14:EDRX Lock: LOCKED, Sync Lock: LOCKEDBackBone Status: UP, Two-Way Mode: YES, Access Mode: RAOutbound Modulation Type: DVB, OB Code Rate: 3/4Outbound Unicast Packets: 0, OB Multicast Packets: 0Outbound ID: 2, OB PID: 514, OB Freq: 1201000, OB Bit Rate: 30000000Outbound Sync IP address: 172.2.0.3Inbound Start Freq: 1190140, IB Stop Freq: 1193710Inbound Data Rate: 768000, IB Freq Offset: 0Inbound Packets: 0BackBone Received Packets: 0, BB Sent: 2BackBone Received Retransmitted: 0, BB Sent Retrans: 0Service Module Eth RX: 3, TX: 0Service Module Eth Multicast RX: 3, Multicast TX: 0Bufs Configured: 1500, Bufs Free: 1449Internal Software State parameters:Service Module SW State Var: 3General IOS FSM: LINK_UP, HSRP FSM: N/A, HSRP VSAT Mode: N/ALost Beats Total: 53, Lost Beats This Retry: 0VOIP DA calls:NONEping Command: Sample Output
The following example shows the outcome of a successful ping command to a destination on the other side of the satellite link. The specified source IP address belongs to the router LAN interface.
Router# show running-config interface fastethernet0/0Building configuration...Current configuration:110 bytes!interface FastEthernet0/0ip address 10.2.0.1 255.255.255.0load-interval 30speed 100full-duplexendRouter# ping 172.16.0.4 source 10.2.0.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 172.16.0.4, timeout is 2 seconds:Packet sent with a source address of 10.2.0.1!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 136/147/160 msRouter#traceroute Command: Sample Output
The following example shows the outcome of a successful traceroute command to a destination on the other side of the satellite link or hub dial backup link. The source IP address belongs to the router LAN interface.
Router# tracerouteProtocol [ip]:Target IP address: 172.16.0.4Source address: 10.2.0.1Numeric display [n]:Timeout in seconds [3]:Probe count [3]:Minimum Time to Live [1]:Maximum Time to Live [30]:Port Number [33434]:Loose, Strict, Record, Timestamp, Verbose[none]:Type escape sequence to abort.Tracing the route to 172.16.0.41 * * *2 * * *3 192.168.1.5 148 msec 140 msec 160 msec4 172.17.5 140 msec 160 msec 140 msec5 172.16.0.4 160 msec * 152 msecTroubleshooting Tips
•
•
•
What to Do Next
Proceed to the "Enabling or Disabling VSAT Route Update Messages to the Hub from the NM-1VSAT-GILAT Network Module" section.
Troubleshooting Satellite Network Connectivity for the NM-1VSAT-GILAT Network Module
This section describes how to use the Cisco IOS CLI to troubleshoot failure of the router to connect to the satellite communications network using the NM-1VSAT-GILAT network module.
You can also check the LEDs on the NM-1VSAT-GILAT network module faceplate to troubleshoot satellite network connectivity. See the "NM-1VSAT-GILAT Network Module LEDs" section.
Prerequisites
Before using debug commands, read and understand the Important Information on Debug Commands document.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
service-module satellite slot/0 status
Example:Router# service-module satellite 1/0 status
Displays status information related to the hardware and software on the NM-1VSAT-GILAT network module.
•
•
Step 3
show
Example:Router(sat-init-config)# show
Displays the initial configuration parameters for the NM-1VSAT-GILAT network module.
•
•
Step 4
debug satellite rbcp
Example:Router# debug satellite rbcp
Displays Router Blade Configuration Protocol (RBCP) management messages between Cisco IOS software and the network module.
•
•
Step 5
debug satellite errors
Example:Router# debug satellite errors
(Optional) Displays satellite link error conditions.
•
•
Step 6
debug satellite events
Example:Router# debug satellite events
(Optional) Displays debug information for software events, such as the periodic heartbeats from the NM-1VSAT-GILAT network module to the Cisco IOS software on the router.
Step 7
debug scp {data | async | errors | timeouts | packets | all}
Example:Router# debug scp all
(Optional) Displays management messages between Cisco IOS software and the network module that are more detailed than the debug satellite rbcp command output.
Note
Examples
This section provides the following examples:
•
•
•
•
•
service-module satellite status Command: Sample Output
The following example shows that the NM-1VSAT-GILAT network module is in boot mode after a reset, so that the link to the hub (BackBone Status) is down. In this situation, you need to wait until the NM-1VSAT-GILAT network module completes the boot process.
Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS: 15.4.5.12, RSP: 0.0.0.0, MBC: 2.0.4.3HW Version: 00008000CPA Number: 6103, DPS CPA: 0Workgroup: 257, SW Group: 513, Download: YESService Module Uptime: 00:00:20, Router Uptime: 4 days, 4 hours, 29 minutesCurrent router clocktime: *19:07:35.935 UTC Tue Jul 11 2006Oper Mode: BOOT, In Dial Backup: NO, Standby: NORBCP Received Packets: 0, RBCP Sent Packets: 0Eb/No: 10.9283, Flags: 0xEEEEIP Address/Mask: 0.0.0.0/0.0.0.0Service Module MAC: 00:A0:AC:06:15:00RX Lock: LOCKED, Sync Lock: NOT LOCKEDBackBone Status: DOWN, Two-Way Mode: YES, Access Mode: INVALIDOutbound Modulation Type: DVB, OB Code Rate: 3/4Outbound Unicast Packets: 0, OB Multicast Packets: 0Outbound ID: 2, OB PID: 514, OB Freq: 1201000, OB Bit Rate: 30000000...show (satellite initial configuration) Command: Sample Output
The following example shows the satellite initial configuration parameters:
Router(sat-init-config)# show!! Initial Configuration Parameters:!id aa-group 298id software group 598id vsat 6201mode downloadmode two-wayoutbound data-pid 514outbound data-rate 15000000outbound frequency 1201000outbound id 2outbound modulation-type DVBoutbound sync ip address 172.22.0.3outbound viterbi-rate 1/2!!Router(sat-init-config)#debug satellite rbcp Command: Sample Output
With the debug satellite rbcp command enabled, you can verify communication between the router and the NM-1VSAT-GILAT network module by monitoring RBCP messages between the Cisco IOS software and the NM-1VSAT-GILAT network module. In the following example, the NM-1VSAT-GILAT network module requests updates to the routing table, and the router responds to the request.
Router# debug satellite rbcp...The NM-1VSAT-GILAT network module requests IP route information:
*May 16 09:18:54.475:Satellite1/0 RBCP Request msg Recd:IPROUTE_REQ(0x22)The Cisco IOS software acknowledges that it received the message from the NM-1VSAT-GILAT network module:
*May 16 09:18:54.475:Satellite1/0 RBCP Response msg Sent:IPROUTE_REQ(0x22)The Cisco IOS software sends the IP route information to the NM-1VSAT-GILAT network module:
*May 16 09:18:54.475:Satellite1/0 RBCP Request msg Sent:IPROUTE_UPD(0x23)The NM-1VSAT-GILAT network module acknowledges that it received the routing update from the Cisco IOS software:
*May 16 09:18:54.475:Satellite1/0 RBCP Response msg Recd:IPROUTE_UPD(0x23)debug satellite events Command: Sample Output
The following example shows how to monitor the periodic heartbeats that the NM-1VSAT-GILAT network module sends to the Cisco IOS software:
Router# debug satellite eventssatellite major software events debugging is on*May 16 09:32:15.575:Satellite1/0 FSM transition LINK_UP-->LINK_UP, ev=got_heartbeat*May 16 09:32:32.363:Satellite1/0 FSM transition LINK_UP-->LINK_UP, ev=got_heartbeatdebug satellite scp Command: Sample Output
The following example shows management messages between the Cisco IOS software on the router and the NM-1VSAT-GILAT network module.
Router# debug scp all*Aug 31 09:26:19.221:scp-rx:SA:01/02 DA:0F/02 Op:0071 Sq:0D15 Ln:0014 I:00*Aug 31 09:26:19.221:000:10 00 00 03 00 00 00 02 00 0E 0D 08 00 0E 0D 08 ................*Aug 31 09:26:19.225:010:00 00 00 01 ....*Aug 31 09:26:19.229:scp-tx:SA:0F/02 DA:01/02 Op:0071 Sq:0D15 Ln:0014 I:01*Aug 31 09:26:19.229:000:00 00 9C 40 00 00 00 02 00 0E 0D 08 00 0E 0D 08 ...@............*Aug 31 09:26:19.233:010:00 00 00 01 ....*Aug 31 09:26:30.492:scp-rx:SA:01/02 DA:0F/02 Op:0022 Sq:0D17 Ln:0000 I:00*Aug 31 09:26:30.492:scp-rx:SA:01/02 DA:0F/02 Op:0026 Sq:0D18 Ln:0000 I:00*Aug 31 09:26:30.492:scp-tx:SA:0F/02 DA:01/02 Op:0022 Sq:0D17 Ln:0000 I:01*Aug 31 09:26:30.504:scp-tx:SA:0F/02 DA:01/02 Op:0023 Sq:9DC1 Ln:0018 I:00*Aug 31 09:26:30.504:000:00 00 00 01 00 00 00 01 08 7B 60 00 FF FF FF 00 .........{`.....*Aug 31 09:26:30.508:010:3E 01 00 06 00 00 00 01 >.......*Aug 31 09:26:30.508:scp-rx:SA:01/02 DA:0F/02 Op:0023 Sq:9DC1 Ln:0018 I:01*Aug 31 09:26:30.508:000:00 00 00 01 00 00 00 01 08 7B 60 00 FF FF FF 00 .........{`.....*Aug 31 09:26:30.512:010:3E 01 00 06 00 00 00 01 >.......*Aug 31 09:26:30.508:scp-tx:SA:0F/02 DA:01/02 Op:0026 Sq:0D18 Ln:0000 I:01*Aug 31 09:26:30.516:scp-tx:SA:0F/02 DA:01/02 Op:0027 Sq:9DC2 Ln:0008 I:00*Aug 31 09:26:30.516:000:00 00 00 00 00 00 00 00 ........*Aug 31 09:26:30.520:scp-rx:SA:01/02 DA:0F/02 Op:0027 Sq:9DC2 Ln:0008 I:01*Aug 31 09:26:30.524:000:00 00 00 00 00 00 00 00 ........*Aug 31 09:26:36.009:scp-rx:SA:01/02 DA:0F/02 Op:0071 Sq:0D1A Ln:0014 I:00*Aug 31 09:26:36.009:000:10 00 00 03 00 00 00 02 00 0E 0D 0D 00 0E 0D 0D ................*Aug 31 09:26:36.009:010:00 00 00 01 ....*Aug 31 09:26:36.013:scp-tx:SA:0F/02 DA:01/02 Op:0071 Sq:0D1A Ln:0014 I:01*Aug 31 09:26:36.013:000:00 00 9C 40 00 00 00 02 00 0E 0D 0D 00 0E 0D 0D ...@............Enabling or Disabling VSAT Route Update Messages to the Hub from the NM-1VSAT-GILAT Network Module
By default, when a change occurs in the routing table, the router sends RBCP messages to the NM-1VSAT-GILAT network module. In turn, the NM-1VSAT-GILAT network module sends the route updates to the hub, which has a routing database that includes the routing table of every VSAT router in the satellite network.
This section describes how to disable or, if already disabled, how to enable the route update messages to the hub. Disabling the route update messages conserves satellite link bandwidth when the hub does not need to know the entire routing table of the VSAT router. For example, if you enable Network Address Translation (NAT) on the VSAT router, the hub should not learn the NAT local addresses.
Prerequisites
Complete the tasks in these sections:
•
•
Restrictions
•
•
–
–
SUMMARY STEPS
1.
2.
3.
4.
or
service-module routing redistribute5.
6.
DETAILED STEPS
Examples
A configuration example follows.
Disabling VSAT Route Update Messages to the Hub: Example
In the following example, the VSAT router does not send route update messages to the hub:
!interface Satellite 1/0ip address 10.0.0.6 255.255.255.0service-module ip address 10.0.0.1 255.255.255.0no service-module routing redistribute!Configuring Hub Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link
When you use the NM-1VSAT-GILAT network module to provide your primary network connectivity over the satellite link, you can set up a backup terrestrial link in either hub dial backup mode or router dial backup mode. This section describes how to configure hub dial backup mode.
For information about router dial backup mode, see the "Configuring Router Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link" section.
Hub Dial Backup Mode
Hub dial backup mode maintains TCP connections during transitions between primary and backup links. Note, however, that hub dial backup mode provides backup for the satellite link, but not for the NM-1VSAT-GILAT network module hardware, the router satellite interface, or other router interfaces.
If the satellite link goes down (for example, because of rain fade) in hub dial backup mode, the NM-1VSAT-GILAT network module connects to the hub using dial-on-demand routing (DDR). Common DDR backup links use ISDN BRIs, modems on auxiliary ports, and T1/E1 lines.
The NM-1VSAT-GILAT network module always encapsulates packets using a satellite backbone protocol before sending the packets over the satellite link. In hub dial backup mode, the NM-1VSAT-GILAT network module continues to encapsulate the packets using the satellite backbone protocol before sending the packets over the dial backup link to the hub; this is how hub dial backup mode maintains TCP connections during transitions between the primary satellite link and the dial backup link. Therefore, hub dial backup mode works only when the NM-1VSAT-GILAT network module itself is functioning properly.
Figure 5 shows a sample network topology for hub dial backup mode.
Figure 5 Hub Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link—Sample Network Topology
Prerequisites
•
•
•
•
Restrictions
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
What to Do Next
Proceed to the "Verifying Hub Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link" section.
Verifying Hub Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link
This section describes how to verify successful configuration of a backup terrestrial link in hub dial backup mode when you use the NM-1VSAT-GILAT network module to provide your primary network connectivity over the satellite link.
Prerequisites
Complete the task described in the "Configuring Hub Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link" section.
SUMMARY STEPS
1.
2.
or
telnet {host-name | ip-address}
or
traceroute3.
or
Disconnect the external power supply from the ODU PWR connector on the NM-1VSAT-GILAT network module.4.
5.
or
telnet {host-name | ip-address}
or
traceroute6.
or
Reconnect the external power supply to the ODU PWR connector on the NM-1VSAT-GILAT network module.7.
8.
or
telnet {host-name | ip-address}
or
tracerouteDETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
ping {host-name | ip-address} source lan-ip-address
or
telnet {host-name | ip-address}
or
traceroute
Example:Router# ping 172.16.0.4 source 10.2.0.1
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
Note
Step 3
service-module satellite slot/0 backup initiate
or
Disconnect the external power supply from the ODU PWR connector on the NM-1VSAT-GILAT network module.
Example:Router# service-module satellite 1/0 backup initiate
Initiates a test of the hub dial backup link for the NM-1VSAT-GILAT network module.
or
Brings down the satellite link by cutting off power to the dish antenna.
Step 4
service-module satellite slot/0 status
Example:Router# service-module satellite 1/0 status
Displays status information related to the hardware and software on the NM-1VSAT-GILAT network module.
•
Step 5
ping {host-name | ip-address} source lan-ip-address
or
telnet {host-name | ip-address}
or
traceroute
Example:Router# ping 172.16.0.4 source 10.2.0.1
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
Note
Step 6
service-module satellite slot/0 backup terminate
or
Reconnect the external power supply to the ODU PWR connector on the NM-1VSAT-GILAT network module.
Example:Router# service-module satellite 1/0 backup terminate
Terminates the test of the hub dial backup link for the NM-1VSAT-GILAT network module.
or
Brings up the satellite link by reconnecting power to the dish antenna.
Step 7
service-module satellite slot/0 status
Example:Router# service-module satellite 1/0 status
Displays status information related to the hardware and software on the NM-1VSAT-GILAT network module.
•
Step 8
ping {host-name | ip-address} source lan-ip-address
or
telnet {host-name | ip-address}
or
traceroute
Example:Router# ping 172.16.0.4 source 10.2.0.1
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
Note
1 Use the IP address of any interface on your router except for the IP addresses assigned to the NM-1VSAT-GILAT network module and to the router satellite interface.
Examples
This section provides the following examples:
•
•
•
ping Command: Sample Output
The following example shows the outcome of a successful ping command to a destination on the other side of the satellite link or hub dial backup link. The source IP address belongs to the router LAN interface.
Router# show running-config interface fastethernet0/0Building configuration...Current configuration:110 bytes!interface FastEthernet0/0ip address 10.2.0.1 255.255.255.0load-interval 30speed 100full-duplexendRouter# ping 172.16.0.4 source 10.2.0.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 172.16.0.4, timeout is 2 seconds:Packet sent with a source address of 10.2.0.1!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 136/147/160 mstraceroute Command: Sample Output
The following example shows the outcome of a successful traceroute command to a destination on the other side of the satellite link or hub dial backup link. The source IP address belongs to the router LAN interface.
Router# tracerouteProtocol [ip]:Target IP address: 172.16.0.4Source address: 10.2.0.1Numeric display [n]:Timeout in seconds [3]:Probe count [3]:Minimum Time to Live [1]:Maximum Time to Live [30]:Port Number [33434]:Loose, Strict, Record, Timestamp, Verbose[none]:Type escape sequence to abort.Tracing the route to 172.16.0.41 * * *2 * * *3 192.168.1.5 148 msec 140 msec 160 msec4 172.17.5 140 msec 160 msec 140 msec5 172.16.0.4 160 msec * 152 msecservice-module satellite status Command: Sample Output
The following example shows that the NM-1VSAT-GILAT network module is using dial backup to connect to the hub:
Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS: 15.4.5.12, RSP: 3.4.5.5, MBC: 2.0.4.3HW Version: 00008000CPA Number: 6101, DPS CPA: 5Workgroup: 257, SW Group: 513, Download: YESService Module Uptime: 00:00:55, Router Uptime: 3 days, 22 hours, 3 minutesCurrent router clocktime: *03:13:01.924 UTC Tue Mar 5 2002Oper Mode: OPERATIONAL, In Dial Backup: YES, Standby: NORBCP Received Packets: 14, RBCP Sent Packets: 13Eb/No: 10.9483, Flags: 0x0007IP Address/Mask: 9.0.0.1/255.255.255.252Service Module MAC: 00:A0:AC:06:14:EDRX Lock: LOCKED, Sync Lock: LOCKEDBackBone Status: UP, Two-Way Mode: YES, Access Mode: RAOutbound Modulation Type: DVB, OB Code Rate: 3/4Outbound Unicast Packets: 0, OB Multicast Packets: 0Outbound ID: 2, OB PID: 514, OB Freq: 1201000, OB Bit Rate: 30000000Outbound Sync IP address: 172.2.0.3Inbound Start Freq: 1190140, IB Stop Freq: 1193710Inbound Data Rate: 768000, IB Freq Offset: 0Inbound Packets: 0BackBone Received Packets: 0, BB Sent: 2BackBone Received Retransmitted: 0, BB Sent Retrans: 0Service Module Eth RX: 3, TX: 0Service Module Eth Multicast RX: 3, Multicast TX: 0Bufs Configured: 1500, Bufs Free: 1449Internal Software State parameters:Service Module SW State Var: 3General IOS FSM: LINK_UP, HSRP FSM: N/A, HSRP VSAT Mode: N/ALost Beats Total: 53, Lost Beats This Retry: 0VOIP DA calls:NONEshow interfaces summary Command: Sample Output
The following example shows interface packet counters while the hub dial backup link is in use and working properly. Notice that the number of packets that pass through the satellite interface is twice the number of packets that pass through the dial backup interface.
The NM-1VSAT-GILAT network module always encapsulates packets using a satellite backbone protocol before sending the packets over the satellite link. In hub dial backup mode, the NM-1VSAT-GILAT network module continues to encapsulate the packets using the satellite backbone protocol before sending the packets over the dial backup link to the hub; this is how hub dial backup mode maintains TCP connections during transitions between the primary satellite link and the dial backup link. Therefore, all packets from the VSAT to the hub over the dial backup link still need to enter and exit the NM-1VSAT-GILAT network module, even when the satellite link is down because of a rain-fade event.
Router# show interfaces summary*:interface is upIHQ:pkts in input hold queue IQD:pkts dropped from input queueOHQ:pkts in output hold queue OQD:pkts dropped from output queueRXBS:rx rate (bits/sec) RXPS:rx rate (pkts/sec)TXBS:tx rate (bits/sec) TXPS:tx rate (pkts/sec)TRTL:throttle countInterface IHQ IQD OHQ OQD RXBS RXPS TXBS TXPS TRTL------------------------------------------------------------------------Async1 0 0 0 0 0 0 0 0 0* FastEthernet0/0 0 0 0 0 1000 1 1000 1 0* BRI0/0 0 0 0 0 0 0 0 0 0* BRI0/0:1 0 0 0 0 1000 1 1000 1 0BRI0/0:2 0 0 0 0 0 0 0 0 0Async2 0 0 0 0 0 0 0 0 0FastEthernet0/1 0 0 0 0 0 0 0 0 0Serial0/2 0 0 0 0 0 0 0 0 0Serial0/3 0 0 0 0 0 0 0 0 0* Satellite1/0 0 0 0 0 2000 2 2000 2 0* Virtual-Access1 0 0 0 0 1000 1 1000 1 0NOTE:No separate counters are maintained for subinterfacesHence details of subinterface are not shownTroubleshooting Tips
•
•
•
Configuring Router Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link
When you use the NM-1VSAT-GILAT network module to provide your primary network connectivity over the satellite link, you can set up a backup terrestrial link in either hub dial backup mode or router dial backup mode. This section describes how to configure router dial backup mode.
For information about hub dial backup mode, see the "Configuring Hub Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link" section.
Router Dial Backup Mode
If the satellite link goes down in router dial backup mode, the router uses dial-on-demand routing (DDR) to send data out a different interface. Common DDR backup links use ISDN BRIs, modems on auxiliary ports, and T1/E1 lines.
Unlike hub dial backup mode, router dial backup mode does these things:
•
•
Figure 6 shows a sample network topology for router dial backup mode.
Figure 6 Router Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link—Sample Network Topology
Prerequisites
•
•
•
Perform one of the following tasks in this section, depending on your preferred method of configuration:
•
•
Configuring Router Dial Backup by Using a Floating Static Route
This section describes how to use a floating static route to configure a selected interface as the backup to the satellite interface.
In general, floating static routes are static routes that are used to back up other static routes or dynamic routes learned through configured routing protocols. A floating static route is configured with a less efficient administrative distance than the routing protocol or static route it is backing up. As a result, the preferred static route or dynamic route learned through the routing protocol is always used in preference to the floating static route. If the preferred static route or dynamic route is lost, the floating static route will be used in its place.
For more general information about floating static routes, see these tech notes:
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
What to Do Next
Proceed to the "Verifying Router Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link" section.
Configuring Router Dial Backup by Using a Backup Interface
This section describes how to configure a selected interface as the backup interface for the primary satellite interface. A backup interface is an interface that stays idle until the primary line goes down; then it is activated.
For more general information about backup interfaces, see the Evaluating Backup Interfaces, Floating Static Routes, and Dialer Watch for DDR Backup tech note.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
What to Do Next
Proceed to the "Verifying Router Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link" section.
Verifying Router Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link
This section describes how to verify successful configuration of a backup terrestrial link in router dial backup mode when you use the NM-1VSAT-GILAT network module to provide your primary network connectivity over the satellite link.
Prerequisites
Complete one of the tasks in the "Configuring Router Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link" section.
SUMMARY STEPS
1.
2.
or
telnet {host-name | ip-address}
or
traceroute3.
4.
5.
or
telnet {host-name | ip-address}
or
traceroute {host-name | ip-address}6.
7.
8.
or
telnet {host-name | ip-address}
or
tracerouteDETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
ping {host-name | ip-address} source lan-ip-address
or
telnet {host-name | ip-address}
or
traceroute
Example:Router# ping 172.16.0.4 source 10.2.0.1
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
Note
Step 3
Disconnect the external power supply from the ODU PWR connector on the NM-1VSAT-GILAT network module.
Brings down the satellite link by cutting off power to the dish antenna.
Step 4
show interfaces satellite slot/0
Example:Router# show interfaces satellite 1/0
Displays general interface settings and traffic rates for the router satellite interface, which is the internal interface that connects the router to the installed NM-1VSAT-GILAT network module.
•
•
Step 5
ping {host-name | ip-address}
or
telnet {host-name | ip-address}
or
traceroute {host-name | ip-address}
Example:Router# ping 172.16.0.4
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
Step 6
Reconnect the external power supply to the ODU PWR connector on the NM-1VSAT-GILAT network module.
Brings up the satellite link by reconnecting power to the dish antenna.
Step 7
show interfaces satellite slot/0
Example:Router# show interfaces satellite 1/0
Displays general interface settings and traffic rates for the router satellite interface, which is the internal interface that connects the router to the installed NM-1VSAT-GILAT network module.
•
•
Step 8
ping {host-name | ip-address} source lan-ip-address
or
telnet {host-name | ip-address}
or
traceroute
Example:Router# ping 172.16.0.4 source 10.2.0.1
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
Note
1 Use the IP address of any interface on your router except for the IP addresses assigned to the NM-1VSAT-GILAT network module and to the router satellite interface.
Examples
This section provides the following examples:
•
•
ping Command: Sample Output
The following example shows the outcome of a successful ping command to a destination on the other side of the satellite link. The source IP address belongs to the router LAN interface.
Router# show running-config interface fastethernet0/0Building configuration...Current configuration :110 bytes!interface FastEthernet0/0ip address 10.2.0.1 255.255.255.0load-interval 30speed 100full-duplexendRouter# ping 172.16.0.4 source 10.2.0.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 172.16.0.4, timeout is 2 seconds:Packet sent with a source address of 10.2.0.1!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 136/147/160 msRouter#traceroute Command: Sample Output
The following example shows the outcome of a successful traceroute command to a destination on the other side of the satellite link. The source IP address belongs to the router LAN interface.
Router# tracerouteProtocol [ip]:Target IP address: 172.16.0.4Source address: 10.2.0.1Numeric display [n]:Timeout in seconds [3]:Probe count [3]:Minimum Time to Live [1]:Maximum Time to Live [30]:Port Number [33434]:Loose, Strict, Record, Timestamp, Verbose[none]:Type escape sequence to abort.Tracing the route to 172.16.0.41 * * *2 * * *3 192.168.1.5 148 msec 140 msec 160 msec4 172.17.5 140 msec 160 msec 140 msec5 172.16.0.4 160 msec * 152 msecshow interfaces satellite Command: Sample Output
The following example shows that the satellite link is up.
Router# show interfaces satellite 2/0Satellite1/0 is up, line protocol is upHardware is I82559FE, address is 0008.e35f.7370 (bia 0008.e35f.7370)Internet address is 10.0.0.6/24...Troubleshooting Tips
Make sure that your backup terrestrial link is working properly. See the Cisco IOS Dial Technologies Configuration Guide, the Cisco IOS Interface and Hardware Component Configuration Guide, or the Cisco IOS Wide-Area Networking Configuration Guide.
Configuring NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link
This section describes how to configure the satellite link as a backup to a primary terrestrial link such as Frame Relay or DSL.
A backup satellite link provides a higher level of resiliency than modem or ISDN BRI backup links. If the cables of a primary link are severed in a "backhoe" event, then it is likely that all terrestrial circuits from the building are out of service. A satellite communications network provides total path diversity without the need to provide a second cable entrance facility.
Figure 7 shows a sample network topology for NM-1VSAT-GILAT network module satellite backup for a terrestrial link.
Figure 7 NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link—Sample Network Topology
Prerequisites
•
•
•
Perform one of the following tasks in this section, depending on your preferred method of configuration:
•
•
Configuring Satellite Backup by Using a Floating Static Route
This section describes how to use a floating static route to configure the satellite interface as a backup to another interface.
In general, floating static routes are static routes that are used to back up other static routes or dynamic routes learned through configured routing protocols. A floating static route is configured with a less efficient administrative distance than the routing protocol or static route it is backing up. As a result, the preferred static route or dynamic route learned through the routing protocol is always used in preference to the floating static route. If the preferred static route or dynamic route is lost, the floating static route will be used in its place.
For more general information about floating static routes, see the Evaluating Backup Interfaces, Floating Static Routes, and Dialer Watch for DDR Backup tech note.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
What to Do Next
Proceed to the "Verifying NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link—Floating Static Route" section.
Configuring Satellite Backup by Using a Backup Interface
This section describes how to configure the satellite interface as the backup interface for a selected primary interface. A backup interface is an interface that stays idle until the primary line goes down; then it is activated.
For more general information about backup interfaces, see the Evaluating Backup Interfaces, Floating Static Routes, and Dialer Watch for DDR Backup tech note.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
What to Do Next
Proceed to the "Verifying NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link—Backup Interface" section.
Verifying NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link—Floating Static Route
This section describes how to verify successful configuration of satellite backup for a terrestrial link by using a floating static route.
Prerequisites
Complete the task in the "Configuring NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link" section.
SUMMARY STEPS
1.
2.
or
telnet {host-name | ip-address}
or
traceroute {host-name | ip-address}3.
or
If you do not have physical access to the router, proceed to Step 4.4.
5.
6.
7.
8.
9.
or
telnet {host-name | ip-address}
or
traceroute10.
or
If you do not have physical access to the router, proceed to Step 11.11.
12.
13.
14.
15.
or
telnet {host-name | ip-address}
or
traceroute {host-name | ip-address}DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
ping {host-name | ip-address}
or
telnet {host-name | ip-address}
or
traceroute {host-name | ip-address}
Example:Router# ping 172.16.0.4
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
Step 3
Disconnect the cables attached to the primary interface, and proceed to Step 8.
or
If you do not have physical access to the router, proceed to Step 4.
Physically brings down the terrestrial link.
or
Proceeds to instructions for disabling the interface.
Step 4
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 5
interface type number
Example:Router(config)# interface serial 0/2
Enters interface configuration mode.
•
Step 6
shutdown
Example:Router(config-if)# shutdown
Disables the interface.
Step 7
end
Example:Router(config-if)# end
Returns to privileged EXEC mode.
Step 8
show interfaces satellite slot/0
Example:Router# show interfaces satellite 1/0
Displays general interface settings and traffic rates for the router satellite interface, which is the internal interface that connects the router to the installed NM-1VSAT-GILAT network module.
•
•
Step 9
ping {host-name | ip-address} source lan-ip-address
or
telnet {host-name | ip-address}
or
traceroute
Example:Router# ping 172.16.0.4 source 10.2.0.1
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
Note
Step 10
Reconnect the cables attached to the primary interface, and proceed to Step 15.
or
If you do not have physical access to the router, proceed to Step 11.
Physically brings up the terrestrial link.
or
Proceeds to instructions for enabling the interface.
Step 11
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 12
interface type number
Example:Router(config)# interface serial 0/2
Enters interface configuration mode.
•
Step 13
no shutdown
Example:Router(config-if)# no shutdown
Enables the interface.
Step 14
end
Example:Router(config-if)# end
Returns to privileged EXEC mode.
Step 15
ping {host-name | ip-address}
or
telnet {host-name | ip-address}
or
traceroute {host-name | ip-address}
Example:Router# ping 172.16.0.4
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
1 You can use the IP address of any interface on your router except for the IP addresses assigned to the NM-1VSAT-GILAT network module and to the router satellite interface.
Examples
This section provides the following examples:
•
ping Command: Sample Output
The following example shows the outcome of a successful ping command to a destination on the other side of the satellite link. The specified source IP address belongs to the router LAN interface.
Router# show running-config interface fastethernet0/0Building configuration...Current configuration:110 bytes!interface FastEthernet0/0ip address 10.2.0.1 255.255.255.0load-interval 30speed 100full-duplexendRouter# ping 172.16.0.4 source 10.2.0.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 172.16.0.4, timeout is 2 seconds:Packet sent with a source address of 10.2.0.1!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 136/147/160 msRouter#traceroute Command: Sample Output
The following example shows the outcome of a successful traceroute command to a destination on the other side of the satellite link or hub dial backup link. The source IP address belongs to the router LAN interface.
Router# tracerouteProtocol [ip]:Target IP address: 172.16.0.4Source address: 10.2.0.1Numeric display [n]:Timeout in seconds [3]:Probe count [3]:Minimum Time to Live [1]:Maximum Time to Live [30]:Port Number [33434]:Loose, Strict, Record, Timestamp, Verbose[none]:Type escape sequence to abort.Tracing the route to 172.16.0.41 * * *2 * * *3 192.168.1.5 148 msec 140 msec 160 msec4 172.17.5 140 msec 160 msec 140 msec5 172.16.0.4 160 msec * 152 msecTroubleshooting Tips
If the ping and traceroute commands fail to reach a destination on the other side of the satellite link, make sure that you specify a source IP address that is not assigned to the router satellite interface or to the NM-1VSAT-GILAT network module. We recommend using the IP address of a LAN interface on your router, such as a Fast Ethernet interface, as the source IP address for the ping and traceroute commands.
Verifying NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link—Backup Interface
This section describes how to verify successful configuration of satellite backup for a terrestrial link by using a backup interface.
Prerequisites
Complete the task in the "Configuring NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link" section.
Restrictions
Do not enter the shutdown command to bring down the primary interface. The primary interface must be administratively up for the specified backup interface to work.
SUMMARY STEPS
1.
2.
or
telnet {host-name | ip-address}
or
traceroute {host-name | ip-address}3.
or
If you do not have physical access to the router, then access the Cisco IOS CLI of the router on the other end of the primary terrestrial link and proceed to Step 4.4.
5.
6.
7.
8.
9.
10.
or
telnet {host-name | ip-address}
or
traceroute11.
or
If you do not have physical access to the router, then access the Cisco IOS CLI of the router on the other end of the primary terrestrial link and proceed to Step 12.12.
13.
14.
15.
16.
17.
or
telnet {host-name | ip-address}
or
traceroute {host-name | ip-address}DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
ping {host-name | ip-address}
or
telnet {host-name | ip-address}
or
traceroute {host-name | ip-address}
Example:Router# ping 172.16.0.4
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
Step 3
Disconnect the cables attached to the primary interface and proceed to Step 9.
or
If you do not have physical access to the router, then access the Cisco IOS CLI of the router on the other end of the primary terrestrial link and proceed to Step 4.
Physically brings down the terrestrial link.
or
Proceeds to instructions for disabling the terrestrial link by disabling the interface on the neighboring router that connects to the primary interface on which the backup interface command is entered.
Step 4
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 5
interface type number
Example:Router(config)# interface serial 0/2
Enters interface configuration mode.
•
Step 6
shutdown
Example:Router(config-if)# shutdown
Disables the interface.
Step 7
end
Example:Router(config-if)# end
Returns to privileged EXEC mode.
Step 8
Access the Cisco IOS CLI of the router in which the NM-1VSAT-GILAT network module is installed.
—
Step 9
show interfaces satellite slot/0
Example:Router# show interfaces satellite 1/0
Displays general interface settings and traffic rates for the router satellite interface, which is the internal interface that connects the router to the installed NM-1VSAT-GILAT network module.
•
•
Step 10
ping {host-name | ip-address} source lan-ip-address
or
telnet {host-name | ip-address}
or
traceroute
Example:Router# ping 172.16.0.4 source 10.2.0.1
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
Note
Step 11
Reconnect the cables attached to the primary interface, and proceed to Step 17.
or
If you do not have physical access to the router, then access the Cisco IOS CLI of the router on the other end of the primary terrestrial link and proceed to Step 12.
Physically brings up the terrestrial link.
or
Proceeds to instructions for reenabling the terrestrial link by enabling the interface on the neighboring router that connects to the primary interface on which the backup interface command is entered.
Step 12
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 13
interface type number
Example:Router(config)# interface serial 0/2
Enters interface configuration mode.
•
Step 14
no shutdown
Example:Router(config-if)# no shutdown
Enables the interface.
Step 15
end
Example:Router(config-if)# end
Returns to privileged EXEC mode.
Step 16
Access the Cisco IOS CLI of the router in which the NM-1VSAT-GILAT network module is installed.
—
Step 17
ping {host-name | ip-address}
or
telnet {host-name | ip-address}
or
traceroute {host-name | ip-address}
Example:Router# ping 172.16.0.4
Assesses basic network connectivity.
or
Logs in to a host that supports Telnet.
or
Displays the routes that packets take through a network to their destinations.
•
1 You can use the IP address of any interface on your router except for the IP addresses assigned to the NM-1VSAT-GILAT network module and to the router satellite interface.
Examples
This section provides the following examples:
•
ping Command: Sample Output
The following example shows the outcome of a successful ping command to a destination on the other side of the satellite link. The specified source IP address belongs to the router LAN interface.
Router# show running-config interface fastethernet0/0Building configuration...Current configuration:110 bytes!interface FastEthernet0/0ip address 10.2.0.1 255.255.255.0load-interval 30speed 100full-duplexendRouter# ping 172.16.0.4 source 10.2.0.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 172.16.0.4, timeout is 2 seconds:Packet sent with a source address of 10.2.0.1!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 136/147/160 msRouter#traceroute Command: Sample Output
The following example shows the outcome of a successful traceroute command to a destination on the other side of the satellite link or hub dial backup link. The source IP address belongs to the router LAN interface.
Router# tracerouteProtocol [ip]:Target IP address: 172.16.0.4Source address: 10.2.0.1Numeric display [n]:Timeout in seconds [3]:Probe count [3]:Minimum Time to Live [1]:Maximum Time to Live [30]:Port Number [33434]:Loose, Strict, Record, Timestamp, Verbose[none]:Type escape sequence to abort.Tracing the route to 172.16.0.41 * * *2 * * *3 192.168.1.5 148 msec 140 msec 160 msec4 172.17.5 140 msec 160 msec 140 msec5 172.16.0.4 160 msec * 152 msecTroubleshooting Tips
If the ping and traceroute commands fail to reach a destination on the other side of the satellite link, make sure that you specify a source IP address that is not assigned to the router satellite interface or to the NM-1VSAT-GILAT network module. We recommend using the IP address of a LAN interface on your router, such as a Fast Ethernet interface, as the source IP address for the ping and traceroute commands.
Configuring HSRP Redundancy for the NM-1VSAT-GILAT Network Module
This section describes how to configure homogeneous and heterogeneous HSRP redundancy when you use the NM-1VSAT-GILAT network module. To configure HSRP redundancy for the NM-1VSAT-GILAT network module, you should understand the following concepts:
•
•
•
•
HSRP
The Hot Standby Router Protocol (HSRP) provides high network availability because it routes IP traffic from hosts on LANs without relying on the availability of any single router. HSRP is used in a group of routers for selecting an active router and a standby router. An active router is the router of choice for routing packets; a standby router is a router that takes over the routing duties when an active router fails, or when preset conditions are met.
For more information about HSRP, see the "Configuring IP Services" chapter of the Cisco IOS IP Configuration Guide, Release 12.3.
Preemption, Priority, and Tracking
HSRP uses priority and preemption to determine which router is active and which routers are in standby mode. How you configure priority and preemption sets one of the following behaviors:
•
•
Preemption allows a router to become the active router when its priority is higher than that of all other routers in the hot standby group. If preemption is disabled on a router, the router assumes control as the active router only if it receives information indicating that no router is in the active state.
Tracking allows you to specify an interface that the HSRP process should monitor to alter the priority for a given hot standby router. If the specified interface line protocol goes down, the HSRP priority is reduced. This means that another HSRP router with higher priority can become the active router. The amount by which the hot standby priority for the router is decreased (or increased) when the tracked interface goes down (or comes back up) can be configured, but the amount is 10 by default.
For more information on HSRP tracking, preemption, and priority settings, see the How to Use the standby preempt and standby track Commands tech note.
Homogeneous HSRP Redundancy for the NM-1VSAT-GILAT Network Module
Homogeneous HSRP redundancy refers to a setup in which each router in the hot standby group is equipped with an NM-1VSAT-GILAT network module.
If you have only two routers in your hot standby group, then one outdoor unit (ODU) can be shared by two HSRP-redundant NM-1VSAT-GILAT network modules. Note that a Gilat SkyEdge-equipment certified installer must set up this hardware configuration, including connecting the power supply and the NM-1VSAT-GILAT network modules to the ODU.
Figure 8 and Figure 9 show homogeneous HSRP setups for the NM-1VSAT-GILAT network module.
Figure 8 Homogeneous HSRP Redundancy Setup Using Separate ODUs
Figure 9 Homogeneous HSRP Redundancy Setup Using a Shared ODU
Heterogeneous HSRP Redundancy for the NM-1VSAT-GILAT Network Module
Heterogeneous HSRP redundancy refers to a setup in which not all routers in the hot standby group are equipped with an NM-1VSAT-GILAT network module. For example, in a two-router heterogeneous HSRP setup, you can choose one of the following scenarios:
•
•
Figure 10 shows a heterogeneous HSRP setup for the NM-1VSAT-GILAT network module.
Figure 10 Heterogeneous HSRP Redundancy Setup
Perform one of the following tasks, depending on whether or not you have an NM-1VSAT-GILAT network module installed in each router in the hot standby group.
•
•
Configuring Homogeneous HSRP Redundancy with the NM-1VSAT-GILAT Network Module
This section describes how to configure HSRP redundancy for the satellite link when you have an NM-1VSAT-GILAT network module in each router in the hot standby group.
If you instead want to configure HSRP redundancy for the satellite link when not all routers in the hot standby group are equipped with an NM-1VSAT-GILAT network module, then go to the "Configuring Heterogeneous HSRP Redundancy with the NM-1VSAT-GILAT Network Module" section.
Prerequisites
•
•
•
•
•
Restrictions
•
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
DETAILED STEPS
Step 1
Access the Cisco IOS CLI of the primary router.
—
Step 2
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 3
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 4
interface interface
Example:Router(config)# interface fastethernet 0/0
Enters interface configuration mode for the primary LAN interface on which you want to enable HSRP for the router.
Step 5
ip address ip-address mask
Example:Router(config-if)# ip address 10.123.96.3 255.255.255.0
Sets the IP address for the LAN interface.
•
Step 6
standby [group-number] ip [virtual-ip-address]
Example:Router(config-if)# standby 1 ip 10.0.0.100
Activates HSRP and optionally sets the virtual IP address for the hot standby group.
Step 7
standby [group-number] name group-name
Example:Router(config-if)# standby 1 name grp-hsrp
Configures the name of the hot standby group.
•
Step 8
standby [group-number] track satellite slot/0 [decrement priority]
Example:Router(config-if)# standby 1 track satellite 1/0
Monitors the satellite interface and alters the priority of the hot standby router if the satellite interface line protocol goes down.
•
Step 9
standby [group-number] preempt [delay {minimum seconds | reload seconds | sync seconds}]
Example:Router(config-if)# standby 1 preempt
Example:Router(config-if)# standby 1 preempt delay minimum 90
Enables preemption on the router and optionally configures a preemption delay.
•
Step 10
exit
Example:Router(config-if)# exit
Exits interface configuration mode.
Step 11
interface satellite slot/0
Example:Router(config)# interface satellite 1/0
Enters satellite interface configuration mode.
Step 12
service-module ip redundancy group-name
Example:Router(config-if)# service-module ip redundancy grp-x
(Optional) Links the primary HSRP interface status to the satellite interface.
•
•
•
Step 13
end
Example:Router(config-if)# end
Returns to privileged EXEC mode.
Step 14
Access the Cisco IOS CLI of the secondary router.
—
Step 15
—
Step 16
Repeat Step 14 and Step 15 for any additional secondary routers.
—
Configuring Heterogeneous HSRP Redundancy with the NM-1VSAT-GILAT Network Module
This section describes how to configure HSRP redundancy when not all routers in the hot standby group are equipped with an NM-1VSAT-GILAT network module.
If you instead want to configure HSRP redundancy for the satellite link when you have an NM-1VSAT-GILAT network module in each router in the hot standby group, then go to the "Configuring Homogeneous HSRP Redundancy with the NM-1VSAT-GILAT Network Module" section.
For heterogeneous HSRP redundancy, choose one of the following scenarios:
•
•
In both cases of heterogeneous HSRP redundancy, you need to configure the HSRP priority on the primary router to be higher than the HSRP priority of the secondary router. The difference in priority numbers must be small enough that tracking the WAN link (satellite or terrestrial) of the primary router determines which router becomes active, and which router goes to standby. For more information about priority and tracking, see the "Preemption, Priority, and Tracking" section.
Prerequisites
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
or
standby [group-number] track type number [interface-priority]10.
11.
12.
13.
14.
DETAILED STEPS
Step 1
Access the Cisco IOS CLI of the primary router.
—
Step 2
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 3
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 4
interface type number
Example:Router(config)# interface fastethernet 0/0
Enters interface configuration mode for the primary LAN interface on which you want to enable HSRP for the router.
Step 5
ip address ip-address mask
Example:Router(config-if)# ip address 10.123.96.3 255.255.255.0
Sets the IP address for the LAN interface.
•
Step 6
standby [group-number] ip [virtual-ip-address]
Example:Router(config-if)# standby 1 ip 10.0.0.100
Activates HSRP and optionally sets the virtual IP address for the hot standby group.
Step 7
standby [group-number] name group-name
Example:Router(config-if)# standby 1 name grp-x
Configures the name of the hot standby group.
Step 8
standby [group-number] priority priority
Example:Router(config-if)# standby 1 priority 105
(Optional) Configures HSRP priority.
•
•
Step 9
standby [group-number] track satellite slot/0 [decrement priority]
or
standby [group-number] track type number [interface-priority]
Example:Router(config-if)# standby 1 track satellite 1/0
Example:Router(config-if)# standby 1 track serial 1/0
Monitors the satellite interface and alters the priority of the hot standby group if the satellite interface line protocol goes down.
or
Monitors the terrestrial link and alters the priority of the hot standby group if the tracked interface line protocol goes down.
•
•
Step 10
standby [group-number] preempt [delay {minimum seconds | reload seconds | sync seconds}]
Example:Router(config-if)# standby 1 preempt
Example:Router(config-if)# standby 1 preempt delay minimum 90
Enables preemption on the router and optionally configures a preemption delay.
•
Step 11
end
Example:Router(config-if)# end
Returns to privileged EXEC mode.
Step 12
Access the Cisco IOS CLI of the secondary router.
—
Step 13
—
Step 14
Repeat Step 12 and Step 13 for each additional secondary router.
—
What to Do Next
Proceed to the "Verifying HSRP Redundancy for the NM-1VSAT-GILAT Network Module" section.
Verifying HSRP Redundancy for the NM-1VSAT-GILAT Network Module
This section describes how to verify successful HSRP configuration for the NM-1VSAT-GILAT network module.
Prerequisites
Configure HSRP. See the "Configuring HSRP Redundancy for the NM-1VSAT-GILAT Network Module" section.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Examples
This section provides the following examples:
•
•
show standby Command: Sample Output
The following example shows the output of the show standby command when entered on a hot standby router in the active state. The router is equipped with an NM-1VSAT-GILAT network module, and the satellite interface is tracked by the HSRP process.
Router# show standbyFastEthernet0/0 - Group 1State is Active2 state changes, last state change 00:53:09Virtual IP address is 10.123.96.100Active virtual MAC address is 0000.0c07.ac01Local virtual MAC address is 0000.0c07.ac01 (v1 default)Hello time 3 sec, hold time 10 secNext hello sent in 2.556 secsPreemption enabledActive router is localStandby router is 10.123.96.3, priority 100 (expires in 8.168 sec)Priority 100 (default 100)Track interface Satellite2/0 state Up decrement 10IP redundancy name is "grp-x" (cfgd)service-module satellite status Command: Sample Output
The following example shows the status of a hot standby router and NM-1VSAT-GILAT network module in the active state. If the hot standby router was in the standby state, then the "Standby" field would say "YES."
Router# service-module satellite 2/0 statusGetting status from the satellite module, please wait..Software Versions, OS: 15.4.5.12, RSP: 3.4.5.5, MBC: 2.0.4.3HW Version: 00008000CPA Number: 6101, DPS CPA: 5Workgroup: 257, SW Group: 513, Download: YESService Module Uptime: 00:00:55, Router Uptime: 3 days, 22 hours, 3 minutesCurrent router clocktime: *03:13:01.924 UTC Tue Mar 5 2002Oper Mode: OPERATIONAL, In Dial Backup: NO, Standby: NORBCP Received Packets: 14, RBCP Sent Packets: 13Eb/No: 10.9483, Flags: 0x0007IP Address/Mask: 9.0.0.1/255.255.255.252...Troubleshooting HSRP Redundancy for the NM-1VSAT-GILAT Network Module
This section describes how to troubleshoot the HSRP configuration for the NM-1VSAT-GILAT network module.
Prerequisites
Before using debug commands, read and understand the Important Information on Debug Commands tech note.
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Examples
This section provides the following examples:
•
•
•
debug standby Command: Sample Output
The following example shows how to display HSRP state changes and debugging information about the transmission and receipt of HSRP packets:
Router# debug standbyHSRP debugging is onRouter#Two routers, one active and one standby, recognize each other as members of hot standby group 1:
*Dec 6 02:08:46.032:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.3 Standby pri 100 vIP 10.123.96.100*Dec 6 02:08:46.648:HSRP:Fa0/0 REDIRECT adv in, Passive, active 0, passive 1, from 10.123.96.15*Dec 6 02:08:47.364:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.2 Active pri 100 vIP 10.123.96.100*Dec 6 02:08:49.028:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.3 Standby pri 100 vIP 10.123.96.100*Dec 6 02:08:50.365:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.2 Active pri 100 vIP 10.123.96.100*Dec 6 02:08:52.089:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.3 Standby pri 100 vIP 10.123.96.100*Dec 6 02:08:53.365:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.2 Active pri 100 vIP 10.123.96.100*Dec 6 02:08:55.085:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.3 Standby pri 100 vIThe active router is forced to standby status by disabling the primary HSRP interface, Fast Ethernet 0/0:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface fastethernet 0/0Router(config-if)# shutdownRouter(config-if)# exit*Dec 6 02:09:05.365:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.2 Active pri 100 vIP 10.123.96.100*Dec 6 02:09:05.617:HSRP:Fa0/0 REDIRECT adv in, Passive, active 0, passive 2, from 10.123.96.3*Dec 6 02:09:07.085:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.3 Standby pri 100 vIP 10.123.96.100*Dec 6 02:09:07.317:HSRP:Fa0/0 API Software interface going down*Dec 6 02:09:07.317:HSRP:Fa0/0 API Software interface going down*Dec 6 02:09:07.317:HSRP:Fa0/0 Interface down*Dec 6 02:09:07.317:HSRP:Fa0/0 Grp 1 Active:b/HSRP disabled*Dec 6 02:09:07.317:HSRP:Fa0/0 Grp 1 Active router is unknown, was local*Dec 6 02:09:07.317:HSRP:Fa0/0 Grp 1 Standby router is unknown, was 10.123.96.3*Dec 6 02:09:07.317:HSRP:Fa0/0 Grp 1 Resign out 10.123.96.2 Active pri 100 vIP 10.123.96.100*Dec 6 02:09:07.317:HSRP:Fa0/0 Grp 1 Active -> Init*Dec 6 02:09:07.317:%HSRP-6-STATECHANGE:FastEthernet0/0 Grp 1 state Active -> InitRouter#*Dec 6 02:09:07.317:HSRP:Fa0/0 Grp 1 Redundancy "grp-x" state Active -> Init*Dec 6 02:09:07.317:HSRP:Fa0/0 Redirect adv out, Passive, active 0 passive 2*Dec 6 02:09:07.317:HSRP:Fa0/0 Grp 1 Resign out 10.123.96.2 Init pri 100 vIP 10.123.96.100*Dec 6 02:09:07.325:HSRP:Fa0/0 API MAC address update*Dec 6 02:09:07.325:HSRP:Fa0/0 API Add active HSRP addresses to ARP table*Dec 6 02:09:07.817:%SYS-5-CONFIG_I:Configured from console by console*Dec 6 02:09:09.317:%LINK-5-CHANGED:Interface FastEthernet0/0, changed state to administratively down*Dec 6 02:09:09.317:HSRP:API Hardware state change*Dec 6 02:09:10.318:%LINEPROTO-5-UPDOWN:Line protocol on Interface FastEthernet0/0, changed state to down*Dec 6 02:09:35.743:HSRP:Fa0/0 Redirect adv out, Passive, active 0 passive 2*Dec 6 02:10:04.924:HSRP:Fa0/0 Redirect adv out, Passive, active 0 passive 2*Dec 6 02:10:31.834:HSRP:Fa0/0 Redirect adv out, Passive, active 0 passive 2*Dec 6 02:10:59.571:HSRP:Fa0/0 Redirect adv out, Passive, active 0 passive 2*Dec 6 02:11:29.329:HSRP:Fa0/0 Redirect adv out, Passive, active 0 passive 2*Dec 6 02:11:56.034:HSRP:Fa0/0 Redirect adv out, Passive, active 0 passive 1debug satellite hsrp Command: Sample Output
The following example shows the debug satellite hsrp messages that appear when the active router is forced to standby status because the HSRP-tracked satellite interface is shut down:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface satellite 1/0Router(config-if)# shutdownRouter(config-if)# endRouter#01:03:48:%SYS-5-CONFIG_I:Configured from console by console01:03:49:%LINK-5-CHANGED:Interface Satellite1/0, changed state to administratively down01:03:50:%LINEPROTO-5-UPDOWN:Line protocol on Interface Satellite1/0, changed state to down01:04:22:%HSRP-6-STATECHANGE:FastEthernet0/0 Grp 1 state Active -> Speak01:04:22:HSRP-sat:IPred group grp-x update state ACTIVE --> SPEAK01:04:22:Satellite1/0 HSRP-sat:fsm crank ACTIVE-->STANDBY01:04:22:Satellite1/0 HSRP-sat:send standby msg STANDBY01:04:32:HSRP-sat:IPred group grp-x update state SPEAK --> STANDBY01:04:32:Satellite1/0 HSRP-sat:fsm crank STANDBY-->STANDBY01:04:32:Satellite1/0 HSRP-sat:send standby msg STANDBY01:04:42:Satellite1/0 HSRP-sat:send standby msg STANDBY01:04:52:Satellite1/0 HSRP-sat:standby msg STANDBY deferred, not in operational state01:05:02:Satellite1/0 HSRP-sat:standby msg STANDBY deferred, not in operational state01:05:12:Satellite1/0 HSRP-sat:standby msg STANDBY deferred, not in operational state01:05:22:Satellite1/0 HSRP-sat:standby msg STANDBY deferred, not in operational state01:05:32:Satellite1/0 HSRP-sat:standby msg STANDBY not sent, already in state01:06:47:%VSAT-5-STANDBY_MODE:Satellite1/0 module configured for standby mode01:09:32:Satellite1/0 HSRP-sat:fsm crank STANDBY-->STANDBY-UPCombined Sample Output for the debug satellite hsrp and debug standby Commands
The following example shows HSRP-related debug output for both the router and the NM-1VSAT-GILAT network module when the router goes from the standby to active state because the HSRP-tracked satellite interface is reenabled:
Router# show debuggingSATCOM:satellite HSRP events debugging is onHSRP:HSRP Errors debugging is onHSRP Events debugging is onHSRP Packets debugging is onThe satellite interface is reenabled:
Router# configure terminalRouter(config)# interface satellite 1/0Router(config-if)# no shutdownRouter(config-if)# endRouter#The effective HSRP priority of the router changes as the tracked satellite interface comes up:
02:14:37:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Active pri 90 vIP 10.123.96.10002:14:39:HSRP:Fa0/0 API 62.1.0.6 is not an HSRP address02:14:39:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Standby pri 90 vIP 10.123.96.10002:14:39:HSRP:Fa0/0 Grp 1 Track 1 object changed, state Down -> Up02:14:39:HSRP:Fa0/0 Grp 1 Priority 90 -> 100Router#The router changes from standby to active state because its priority is now highest in the hot standby group, and preemption is enabled:
02:14:40:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Active pri 90 vIP 10.123.96.10002:14:40:HSRP:Fa0/0 Grp 1 Standby:h/Hello rcvd from lower pri Active router (90/10.123.96.2)02:14:40:HSRP:Fa0/0 Grp 1 Active router is local, was 10.123.96.202:14:40:HSRP:Fa0/0 Grp 1 Standby router is unknown, was local02:14:40:HSRP:Fa0/0 Redirect adv out, Active, active 1 passive 302:14:40:HSRP:Fa0/0 Grp 1 Coup out 10.123.96.3 Standby pri 100 vIP 10.123.96.10002:14:40:HSRP:Fa0/0 Grp 1 Standby -> Active02:14:40:%HSRP-6-STATECHANGE:FastEthernet0/0 Grp 1 state Standby -> ActiveThe HSRP status of the satellite interface is linked to the primary HSRP interface, Fast Ethernet 0/0, by the service-module ip redundancy command:
02:14:40:HSRP:Fa0/0 Grp 1 Redundancy "grp-x" state Standby -> Active02:14:40:HSRP-sat:IPred group grp-x update state STANDBY --> ACTIVE02:14:40:Satellite1/0 HSRP-sat:fsm crank STANDBY-UP-->ACTIVE-COND02:14:40:HSRP:Fa0/0 Redirect adv out, Active, active 1 passive 202:14:40:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Active pri 100 vIP 10.123.96.10002:14:40:HSRP:Fa0/0 REDIRECT adv in, Passive, active 0, passive 2, from 10.123.96.202:14:40:HSRP:Fa0/0 REDIRECT adv in, Passive, active 0, passive 1, from 10.123.96.1502:14:40:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Speak pri 90 vIP 10.123.96.100Line protocols come up, and HSRP states become fully active:
02:14:41:%LINK-3-UPDOWN:Interface Satellite1/0, changed state to up02:14:42:%LINEPROTO-5-UPDOWN:Line protocol on Interface Satellite1/0, changed state to up02:14:43:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Active pri 100 vIP 10.123.96.10002:14:43:HSRP:Fa0/0 Grp 1 Redundancy group grp-x state Active -> Active02:14:43:HSRP-sat:IPred group grp-x update state ACTIVE --> ACTIVE02:14:43:Satellite1/0 HSRP-sat:fsm crank ACTIVE-COND-->ACTIVE-COND02:14:43:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Speak pri 90 vIP 10.123.96.10002:14:46:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Active pri 100 vIP 10.123.96.10002:14:46:HSRP:Fa0/0 Grp 1 Redundancy group grp-x state Active -> Active02:14:46:HSRP-sat:IPred group grp-x update state ACTIVE --> ACTIVE02:14:46:Satellite1/0 HSRP-sat:fsm crank ACTIVE-COND-->ACTIVE-COND02:14:46:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Speak pri 90 vIP 10.123.96.10002:14:49:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Active pri 100 vIP 10.123.96.10002:14:49:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Speak pri 90 vIP 10.123.96.10002:14:50:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Standby pri 90 vIP 10.123.96.10002:14:50:HSRP:Fa0/0 Grp 1 Standby router is 10.123.96.202:14:51:Satellite1/0 HSRP-sat:send standby msg ACTIVE02:14:52:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Active pri 100 vIP 10.123.96.10002:14:53:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Standby pri 90 vIP 10.123.96.10002:14:55:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Active pri 100 vIP 10.123.96.100Configuring IP Multicast Routing for the NM-1VSAT-GILAT Network Module
This section describes how to configure IP multicast routing over the satellite link.
For general information about IP multicast, see the "IP Multicast" part of the Cisco IOS IP Configuration Guide, Release 12.3.
Prerequisites
•
•
•
Restrictions
•
•
–
–
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
ip multicast-routing
Example:Router(config)# ip multicast-routing
Enables IP multicast routing on the router.
Step 4
ip pim rp-address rp-address [access-list]
Example:Router(config)# ip pim rp-address 192.168.1.5
Configures the IP address of a Protocol Independent Multicast (PIM) rendezvous point (RP) for a particular multicast group.
•
Step 5
interface satellite slot/0
Example:Router(config)# interface satellite 1/0
Enters satellite interface configuration mode.
Step 6
ip pim dr-priority 0
Example:Router (config-if)# ip pim dr-priority 0
Ensures that the VSAT router is never the designated router (DR).
Step 7
ip pim sparse-dense-mode
Example:Router(config-if)# ip pim sparse-dense-mode
Enables PIM on an interface and specifies the sparse-dense mode.
Step 8
exit
Example:Router(config-if)# exit
Exits satellite interface configuration mode.
Step 9
interface type number
Example:Router(config)# interface fastethernet 0/1
Specifies a router interface that is connected to hosts.
Step 10
ip pim sparse-dense-mode
Example:Router(config-if)# ip pim sparse-dense-mode
Enables PIM on an interface and specifies the sparse-dense mode.
Step 11
Repeat Step 9 and Step 10 for all other interfaces that will perform IP multicast routing.
—
Step 12
end
Example:Router(config-if)# end
Returns to privileged EXEC mode.
Step 13
show ip pim neighbor
Example:Router# show ip pim neighbor
Lists the PIM neighbors discovered by the Cisco IOS software.
•
Examples
A sample of command output follows.
Sample Output for the show ip pim neighbor Command
The following example shows that the PIM RP (192.168.1.5) appears to be reachable through the satellite interface:
Router# show ip pim neighborPIM Neighbor TableNeighbor Interface Uptime/Expires Ver DRAddress Prio/Mode192.168.1.5 Satellite1/0 00:24:27/00:01:18 v2 1 / DR STroubleshooting Tips
•
•
–
–
Troubleshooting Voice over IP for the NM-1VSAT-GILAT Network Module
This section describes how to troubleshoot Voice over IP (VoIP) when you have problems making calls over the satellite link. You do not need to perform any special configuration tasks for VoIP to work over the satellite link; however, understanding the following concepts can help you troubleshoot problems.
Dedicated Access (DA) and Random Access (RA) Modes
VoIP calls are extremely sensitive to jitter and delay, both of which are inherent to typical satellite links. Therefore, the NM-1VSAT-GILAT network module provides two modes to connect to the hub:
•
•
Requirements for Automatic Activation and Deactivation of DA Mode
Automatic activation and deactivation of DA mode is available when you set up a VoIP gateway on the router in which the NM-1VSAT-GILAT network module is installed. The integrated VoIP gateway enables the NM-1VSAT-GILAT network module to use RA mode to connect to the hub, except when a VoIP call is placed over the satellite link; then the integrated VoIP gateway automatically activates DA mode. When all calls are terminated, the integrated VoIP gateway automatically deactivates DA mode.
To set up an integrated VoIP gateway that enables automatic activation and deactivation of DA mode, complete one of the following actions on the router in which the NM-1VSAT-GILAT network module is installed:
•
•
•
For information about these voice applications, see the Cisco IOS Voice Configuration Library.
Configuration of Optimum Codec Payload Size in DA Mode
The satellite bandwidth allocation algorithm employed by Gilat SkyEdge satellite service providers uses parameters for bandwidth and packet rate to configure PDA time slot allocations for VoIP calls placed over the satellite link. This results in bandwidth savings or, alternately, in the ability to have more calls in a given bandwidth.
Consult with the service provider on configuration of optimum codec payload size for the NM-1VSAT-Gilat network module. The service provider determines time slot allocations and available bandwidth. The user then determines the optimum payload size, and configures the codecs accordingly in the VoIP gateway solution being used.
For information on optimizing payload size, see the tech note Voice Over IP - Per Call Bandwidth Consumption.
When DA Mode Is Not Available
If you hear a fast busy signal when you try to initiate a VoIP call, or when the call quality is extremely poor, then DA mode is probably not being used for the call. DA mode may be unavailable for one or more of the following reasons:
•
•
•
Restrictions
This section describes how to perform basic VoIP troubleshooting for the NM-1VSAT-GILAT network module. For more general VoIP troubleshooting information, see the Cisco IOS Voice Configuration Library.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Examples
An example of command output follows.
service-module satellite status Command: Sample Output
The following example shows the status of an active VoIP call. Note that dedicated access (DA) mode is in use, and you can see the bandwidth (26 kilobits per second) being used on the DA channels.
Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS: 15.4.5.12, RSP: 3.4.5.5, MBC: 2.0.4.3HW Version: 00008000CPA Number: 6101, DPS CPA: 5Workgroup: 257, SW Group: 513, Download: YESService Module Uptime: 00:00:55, Router Uptime: 3 days, 22 hours, 3 minutesCurrent router clocktime: *03:13:01.924 UTC Tue Mar 5 2002Oper Mode: OPERATIONAL, In Dial Backup: NO, Standby: NORBCP Received Packets: 14, RBCP Sent Packets: 13Eb/No: 10.9483, Flags: 0x0007IP Address/Mask: 10.0.0.1/255.255.255.252Service Module MAC: 00:A0:AC:06:14:EDRX Lock: LOCKED, Sync Lock: LOCKEDBackBone Status: UP, Two-Way Mode: YES, Access Mode: DAOutbound Modulation Type: DVB, OB Code Rate: 3/4Outbound Unicast Packets: 0, OB Multicast Packets: 0Outbound ID: 2, OB PID: 514, OB Freq: 1201000, OB Bit Rate: 30000000Outbound Sync IP address: 172.2.0.3Inbound Start Freq: 1190140, IB Stop Freq: 1193710Inbound Data Rate: 768000, IB Freq Offset: 0Inbound Packets: 0BackBone Received Packets: 0, BB Sent: 2BackBone Received Retransmitted: 0, BB Sent Retrans: 0Service Module Eth RX: 3, TX: 0Service Module Eth Multicast RX: 3, Multicast TX: 0Bufs Configured: 1500, Bufs Free: 1449Internal Software State parameters:Service Module SW State Var: 3General IOS FSM: LINK_UP, HSRP FSM: N/A, HSRP VSAT Mode: N/ALost Beats Total: 53, Lost Beats This Retry: 0VOIP DA calls:VOIP DA calls:Call ID BW (kb) Dst Port Src Port Dest Addr======== ======= ======== ======== ==============16075 26 18310 16866 162.0.0.2What to Do Next
If you continue to encounter VoIP problems while you have sufficient available DA bandwidth, and the service-module satellite slot/0 status command shows that your NM-1VSAT-GILAT network module uses DA mode for the VoIP calls, then troubleshoot your general VoIP setup. See the Cisco IOS Voice Configuration Library.
Configuring Integrated TCP Acceleration and Encryption
Integrated TCP Acceleration and Encryption (ITAE) is used to provide site-to-site VPN connections. An end-to-end VPN tunnel is created between the remote VSAT router and the VPN concentrator. Accelerated traffic is encrypted by Cisco IOS software before being sent over the satellite link. This traffic is first decrypted, and then TCP spoofing information is recovered at the VPN concentrator. Figure 11 shows the topology of such a setup.
Figure 11 Integrated TCP Acceleration and Encryption Setup
The configuration of this setup is done in three parts:
•
•
•
Prerequisites
Do the following before configuring the VSAT router.
•
•
•
•
Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS: 15.4.5.12, RSP: 3.4.5.5, MBC: 2.0.4.3HW Version: 00008000CPA Number: 6103, DPS CPA: 5Workgroup: 257, SW Group: 513, Download: YESService Module Uptime: 18:52:37, Router Uptime: 4 days, 1 hour, 41 minutesCurrent router clocktime: *16:19:52.691 UTC Tue Jul 11 2006Oper Mode: OPERATIONAL, In Dial Backup: NO, Standby: NORBCP Received Packets: 7714, RBCP Sent Packets: 7746Eb/No: 10.8640, Flags: 0x000FIP Address/Mask: 10.0.0.1/255.255.255.252Service Module MAC: 00:A0:AC:06:15:00RX Lock: LOCKED, Sync Lock: LOCKED..............................................Integrated TCP Acceleration and Encapsulation StatisticITAE mode: ENABLED, VPN BB: DOWN, ACL name: Satellite1/0_ITAE_ACLBackbone Link Number: 10, BB Bypass packet sent: 10Accelerated Packet: Source 10.0.0.1, Destination 172.21.0.100Protocol ID: 254</
Guest
