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: 254Local classifier:Network Mask Packet Sent10.1.0.0 255.255.255.0 0Remote classifier:Network Mask Packet Sent172.24.0.0 255.255.255.0 0The Accelerated Packet IP address pair shows the service module IP address as the source and the VPN router address as the destination.
Table 3 gives the values and interpretations of the Flag bits.
Table 3 Flag Bits for Enabling of ITAE
00-02
0x0007
Remote IP address configuration. See Table 2.
03
0x0008
The VPN feature is enabled.
04
0x0010
The VPN backbone is up (there is connection to the VPNA).
Configuring the VSAT Router for ITAE
To configure the VSAT router for ITAE, perform the following procedures:
•
•
•
Configuring the IPsec Tunnel Between the VSAT and the VPN Concentrator
To configure the IPsec tunnel between the VSAT and the VPN concentrator, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring the Satellite Interface for ITAE
To configure the satellite interface for ITAE, perform the following steps.
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Configuring the VSAT Access List
The VSAT access list specifies the traffic that needs to be directed to the satellite interface after acceleration. There are two ways to specify an access list: manually and automatically.
Automatic Configuration
Perform the following steps to enable automatic configuration of the ITAE access list.
Summary Steps
1.
2.
Detailed Steps
Manual Configuration
Perform the following steps to manually configure the ITAE access list.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Note
Examples
This section provides examples for the following:
•
•
•
service-module status Command: Sample Output
The following example gives the output of the service-module status command when ITAE is enabled.
Router#service-module sat 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: 02:07:06, Router Uptime: 4 days, 4 hours, 19 minutesCurrent router clocktime: *18:58:23.455 UTC Tue Jul 11 2006Oper Mode: OPERATIONAL, In Dial Backup: NO, Standby: NORBCP Received Packets: 923, RBCP Sent Packets: 932Eb/No: 10.8586, Flags: 0x001FIP Address/Mask: 10.0.0.1/255.255.255.252Service Module MAC: 00:A0:AC:06:15:00RX Lock: LOCKED, Sync Lock: LOCKEDBackBone Status: UP, Two-Way Mode: YES, Access Mode: RAOutbound Modulation Type: DVB, OB Code Rate: 3/4Outbound Unicast Packets: 173, 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: 173, BB Sent: 2BackBone Received Retransmitted: 0, BB Sent Retrans: 0Service Module Eth RX: 786, TX: 724Service Module Eth Multicast RX: 282, Multicast TX: 0Bufs Configured: 1500, Bufs Free: 1436Internal Software State parameters:Service Module SW State Var: 3General IOS FSM: LINK_UP, HSRP FSM: N/A, HSRP VSAT Mode: N/ALost Beats Total: 176, Lost Beats This Retry: 0VOIP DA calls:NONEIntegrated TCP Acceleration and Encapsulation StatisticITAE mode: ENABLED, VPN BB: UP, ACL name: Satellite1/0_ITAE_ACLBackbone Link Number: 10, BB Bypass packet sent: 166Accelerated Packet: Source 10.0.0.1, Destination 172.21.0.100Protocol ID: 254Local classifier:Network Mask Packet Sent10.1.0.0 255.255.255.0 5Remote classifier:Network Mask Packet Sent172.24.0.0 255.255.255.0 5ITAE Configuration for VSAT Router: Example
Current configuration: 1599 bytes!version 12.4service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname Router!boot-start-markerboot-end-marker!logging buffered 50000000 debugging!no aaa new-model!resource policy!!!ip cef!!ip multicast-routing!!!!crypto isakmp policy 1hash md5authentication pre-sharecrypto isakmp key rtrkey address 172.20.0.2crypto isakmp keepalive 12 3!!crypto ipsec transform-set rtr_trans esp-3des!crypto map mymap 1 ipsec-isakmpset peer 172.20.0.2set transform-set rtr_transmatch address Satellite1/0_ITAE_ACL!!interface GigabitEthernet0/0no ip addressshutdown!interface GigabitEthernet0/1ip address 10.1.0.1 255.255.255.0!interface Satellite1/0ip address dhcpservice-module itae auto-aclcrypto map mymap!router ripversion 2network 8.0.0.0!!no ip http serverno ip http secure-server!!control-plane!!line con 0exec-timeout 0 0line aux 0line vty 0 4passwordlogintransport input all!scheduler allocate 20000 1000!EndITAE Configuration of VPN Concentrator: Example
Current configuration: 1989 bytes!! Last configuration change at 12:20:00 EDT Thu Jul 6 2006! NVRAM config last updated at 10:13:48 EDT Fri Jul 7 2006!version 12.4no service padservice timestamps debug datetime msec localtimeservice timestamps log datetime msec localtimeno service password-encryption!!boot-start-markerboot-end-marker!!no aaa new-modelclock timezone EST -5clock summer-time EDT recurringip cef!!ip multicast-routing!!crypto isakmp policy 1hash md5authentication pre-sharecrypto isakmp key rtrkey address 10.0.0.2crypto isakmp keepalive 12 3!!crypto ipsec transform-set rtr_trans esp-3des!crypto map mymap 1 ipsec-isakmpset peer 10.0.0.2set transform-set rtr_transmatch address itae_acl!!interface FastEthernet0/0ip address 172.20.0.2 255.255.255.0crypto map mymap!interface FastEthernet1/0ip address 172.21.0.1 255.255.255.0!interface FastEthernet2/0ip address 172.22.0.2 255.255.255.0crypto map mymap2!router ripversion 2network 172.20.0.0!no ip http serverno ip http secure-server!!ip access-list extended itae_aclpermit ip host 172.21.0.100 host 10.0.0.1!logging alarm informational!!control-plane!!line con 0exec-timeout 0 0stopbits 1line aux 0stopbits 1line vty 0 4exec-timeout 0 0password lablogin!no scheduler max-task-time!endUpgrading VSAT Firmware
This section describes an alternate method of upgrading NM-1VSAT-GILAT firmware.
In the standard method, the VSAT compares the firmware image at the hub with its own firmware image every time it goes online. If the image at the hub is newer, the VSAT will download the newer version.
The alternate method provides a firmware upgrade of VSATs locally at remote sites through TFTP. This method reduces dependency on a central hub, and allows for ease of update when connected to a service provider who uses third-party hubs that operate in one-way mode only.
When the VSAT firmware is sent to the router flash memory, the TFTP server is configured on the router so that when the upgrade command is issued from the VSAT, the VSAT is able to find the file on the router flash memory. The TFTP server configuration would be as follows:
tftp-server flash:< <firmware filename>This configuration would be within the overall router configuration.
When this configuration is done, the upgrade is accomplished by pointing the VSAT to the router IP address in the upgrade command.
The upgrade is accomplished by using the following command in privileged EXEC mode.
Caution
Examples
Examples of responses to the upgrade command and verification of upgrade follow.
upgrade satellite satellite Command: Sample Output
The following example shows the response of the VSAT to a firmware upgrade command.
Router# upgrade satellite satellite 1/0 10.1.0.1 VSAT_99.06.01.26_Bin.binDownload of new firmware will proceed after a reboot ofthe satellite network module. This could take up to two minutes.Please wait...*Mar 4 03:18:15.006: %LINEPROTO-5-UPDOWN: Line protocol on Interface Satellite1/0, changed state to upThe upgrade process will complete in several minutes.It will take place in the background.Please monitor the console for errors.*Mar 4 03:21:16.006: %LINEPROTO-5-UPDOWN: Line protocol on Interface Satellite1/0, changed state to down*Mar 4 03:27:20.842: %LINEPROTO-5-UPDOWN: Line protocol on Interface Satellite1/0, changed state to upservice-module satellite status Command: Sample Output
After a successful firmware upgrade, the user can use the service-module status command to verify the downloaded image version.
Router# service-module sat 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS: 99.6.282, RSP: 3.4.0.6, MBC: 2.0.4.3HW Version: 00008000...Configuration Examples for the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
This section provides the following configuration examples:
•
•
Configuring Hub Dial Backup for the NM-1VSAT-GILAT Network Module—Primary Satellite Link with a Backup ISDN BRI Link: Example
In the following example, hub dial backup is configured. If the primary satellite link goes down, then the VSAT router connects directly to the remote access server (RAS) at the hub using an ISDN BRI backup link. Figure 12 shows the network topology for this setup.
Figure 12 Hub Dial Backup—ISDN BRI Backup Link: Sample Network Topology
See the following sample configurations:
•
Router1—VSAT Router with NM-1VSAT-GILAT Network Module
!---Backup interface configurationinterface BRI0/0ip address 192.168.3.1 255.255.255.0encapsulation pppload-interval 30dialer string 5550150dialer-group 1isdn switch-type basic-5ess...!---Primary satellite link configuration!---Notice that hub dial backup mode is configured.interface Satellite2/0ip address 172.24.1.3 255.255.0.0service-module backup interface BRI0/0service-module backup mode hubservice-module ip address 172.24.1.1 255.255.0.0...!---RIPv2 configuration!---The 172.24.0.0 network connects to the hub over the primary satellite link.!---The 192.168.3.0 network connects to the hub over the backup ISDN BRI linkrouter ripversion 2network 172.24.0.0network 192.168.3.0no auto-summary...!---Static route over the BRI link to the hub dial backup server.ip route 192.168.255.0 255.255.255.255 BRI0/0...!---Dial-on-Demand Routing (DDR) Dialer List Definitiondialer-list 1 protocol ip permit!Router2—RAS at the Hub
!---LAN interface that connects to the hub dial backup serverinterface FastEthernet0/0ip address 192.168.255.222 255.255.255.0speed 10full-duplex...!---BRI interface that connects to the VSAT router with the NM-1VSAT-GILAT network moduleinterface BRI0/0ip address 192.168.3.2 255.255.255.0encapsulation pppisdn switch-type basic-5ess...!---RIPv2 configuration!---The 192.168.3.0 network connects to the VSAT router with the NM-1VSAT-GILAT!---network module.router ripversion 2network 192.168.3.0...!---Dial-on-Demand Routing (DDR) Dialer List Definitiondialer-list 1 protocol ip permit!Configuring Hub Dial Backup for the NM-1VSAT-GILAT Network Module—Primary Satellite Link with a Backup Modem Link: Example
In the following example, hub dial backup is configured. If the primary satellite link goes down, then the VSAT router uses a modem to connect directly to the remote access server (RAS) at the hub. Figure 13 shows the network topology for this setup.
Figure 13 Hub Dial Backup—Backup Modem Link: Sample Network Topology
See the following sample configurations:
•
Router1—VSAT Router with NM-1VSAT-GILAT Network Module
!---Create a script that will place a call over a modem.chat-script dial ABORT ERROR "" "ATDT \T" TIMEOUT 60 CONNECT...!---Primary satellite link configuration!---Notice that hub dial backup mode is configured.interface Satellite2/0ip address 172.24.1.3 255.255.0.0service-module backup interface Async3service-module backup mode hubservice-module ip address 172.24.1.1 255.255.0.0...!---Backup interface configurationinterface Async3ip address 10.3.0.1 255.255.255.0encapsulation pppdialer in-banddialer enable-timeout 20dialer wait-for-carrier-time 60dialer map ip 192.168.255.99 broadcast 102dialer-group 1async mode dedicatedno peer default ip addressppp authentication chap callinppp chap hostname myhostnameppp chap password 0 mypasswordrouting dynamic...!---RIPv2 configuration!---The 10.0.0.0 network connects to the hub over the backup modem link.!---The 172.24.0.0 network connects to the hub over the primary satellite link.router ripversion 2network 10.0.0.0network 172.24.0.0...!---Static route over the modem link to the hub dial backup serverip route 192.168.255.99 255.255.255.255 Async3!!---Dial-on-demand routing (DDR) dialer list definitiondialer-list 1 protocol ip permit...!---Modem line configurationline 3exec-timeout 0 0script dialer dialmodem InOuttransport input allstopbits 1speed 115200flowcontrol hardware!Router2—RAS at the Hub
!---Define username and password for Challenge Handshake Authentication Protocol (CHAP).username myhostname password 0 mypassword...!---LAN interface that connects to the dial backup serverinterface FastEthernet0/0ip address 192.168.255.222 255.255.255.0speed 10full-duplex...!---Backup interface configuration!---The async interface and dialer interface configurations are linked together.interface Group-Async0no ip addressencapsulation pppdialer in-banddialer pool-member 1async default routingasync mode dedicatedno peer default ip addressppp authentication chapgroup-range 3 4!interface Dialer1ip address 10.3.0.2 255.255.255.0encapsulation pppdialer pool 1dialer remote-name myhostnamedialer-group 1no cdp enableppp authentication chap callin...!---RIPv2 configuration!---The 10.0.0.0 network connects to the VSAT router over the modem linkrouter ripversion 2network 10.0.0.0...!---Dial-on-demand routing (DDR) dialer list definitiondialer-list 1 protocol ip permit...!---Modem line configurationline 3 4exec-timeout 0 0flush-at-activationmodem InOuttransport input allstopbits 1speed 115200flowcontrol hardware!Configuring Router Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link—Floating Static Route: Example
In the following example, a floating static route is used to configure router dial backup for the NM-1VSAT-GILAT network module satellite link. If the primary satellite link goes down, then the VSAT router connects to the Internet or an intranet through an ISDN BRI link. Figure 14 shows the network topology for this setup.
Figure 14 Router Dial Backup: Sample Network Topology
See the following sample configurations:
•
•
Router1—VSAT Router with NM-1VSAT-GILAT Network Module
!---Backup interface configurationinterface BRI0/0ip address 192.168.3.1 255.255.255.0ip rip v2-broadcastencapsulation pppdialer string 5550100dialer-group 1isdn switch-type basic-5ess...!---Primary satellite link configuration:!---Notice that the service-module backup mode router command!---does not appear because router dial backup mode is the default setting.interface Satellite2/0ip address 172.24.1.3 255.255.0.0ip rip v2-broadcastservice-module ip address 172.24.1.1 255.255.0.0...!---RIPv2 configuration:!---Redistribute static routes to RIPv2.!---The 172.24.0.0 network connects to the hub over the primary satellite link.!---The 192.168.3.0 network connects to the Internet or an intranet!---over the backup ISDN BRI link.router ripversion 2redistribute staticnetwork 172.24.0.0network 192.168.3.0no auto-summary...!---Floating static route configuration:!---Enter an administrative distance that is greater than!---the administrative distance of the satellite link.ip route 0.0.0.0 0.0.0.0 BRI0/0 200...!---Access list and dial-on-demand routing (DDR) dialer list definitionsaccess-list 100 deny ip any host 255.255.255.255access-list 100 permit ip any anydialer-list 1 protocol ip list 100!Router2—Dial Peer Router That Connects to an Intranet or the Internet
!---BRI interface that connects to the VSAT router with the NM-1VSAT-GILAT network moduleinterface BRI0/0ip address 192.168.3.2 255.255.255.0encapsulation pppisdn switch-type basic-5ess...!---RIPv2 configuration:!---The 192.168.3.0 network connects to the VSAT router with the NM-1VSAT-GILAT!---network module.router ripversion 2network 192.168.3.0no auto-summary!Configuring Router Dial Backup for the NM-1VSAT-GILAT Network Module Satellite Link—Backup Interface: Example
In the following example, the backup interface command is used to configure router dial backup for the NM-1VSAT-GILAT network module satellite link. If the primary satellite link goes down, then the VSAT router connects to the Internet or an intranet through an ISDN BRI link.
Figure 15 shows the network topology for this setup.
Figure 15 Router Dial Backup: Sample Network Topology
See the following sample configurations:
•
•
Router1—VSAT Router With NM-1VSAT-GILAT Network Module
!---Backup interface configurationinterface BRI0/0ip address 192.168.3.1 255.255.255.0encapsulation pppdialer string 5550100dialer-group 1isdn switch-type basic-5ess...!---Primary satellite link configuration:!---Notice that the service-module backup mode router command!---does not appear because router dial backup mode is the default setting.interface Satellite2/0ip address 172.24.1.3 255.255.0.0backup interface BRI0/0service-module ip address 172.24.1.1 255.255.0.0...!---RIPv2 configuration:!---The 172.24.0.0 network connects to the hub over the primary satellite link.!---The 192.168.3.0 network connects to an intranet or Internet!---over the backup ISDN BRI link.router ripversion 2network 172.24.0.0network 192.168.3.0no auto-summary...!---Dial-on-Demand Routing (DDR) Dialer List Definitiondialer-list 1 protocol ip permitRouter2—Dial Peer Router That Connects to an Intranet or the Internet
!---BRI interface that connects to the VSAT router with the NM-1VSAT-GILAT network moduleinterface BRI0/0ip address 192.168.3.2 255.255.255.0encapsulation pppisdn switch-type basic-5ess...!---RIPv2 configuration:!---The 192.168.3.0 network connects to the VSAT router with the NM-1VSAT-GILAT!---network module.router ripversion 2network 192.168.3.0no auto-summary!Configuring NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link—Floating Static Route: Example
In the following example, the satellite link backs up a Frame Relay link. Both links are configured as static routes, but the satellite link has a higher administrative distance. Figure 16 shows the network topology for this setup.
Figure 16 NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link: Sample Network Topology
!---Because Cisco Express Forwarding (CEF) is enabled,!---the ip cef table adjacency-prefix validate command is required.ip cef table adjacency-prefix validateip cef...!---Primary link configuration:!---Frame Relay requires a subinterface configurationinterface Serial0/2no ip addressencapsulation frame-relay!interface Serial0/2.1 point-to-pointip address 192.168.3.1 255.255.255.0frame-relay interface-dlci 200...!---Backup link configurationinterface Satellite1/0ip address 172.24.1.3 255.255.0.0service-module ip address 172.24.1.1 255.255.0.0...!---RIPv2 configuration:!---Redistribute static routes to RIPv2.!---The 192.168.3.0 network is the primary Frame Relay link.!---The 172.24.0.0 network is the backup satellite link.router ripversion 2redistribute staticnetwork 192.168.3.0network 172.24.0.0no auto-summary...!---Static route configuration:!---Notice that the satellite link has a higher administrative distance.ip route 0.0.0.0 0.0.0.0 Serial0/2.1ip route 0.0.0.0 0.0.0.0 Satellite1/0 200!Configuring NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link—Backup Interface: Example
In the following example, the satellite interface backs up the subinterface on which the Frame Relay link is configured. Figure 17 shows the network topology for this setup.
Figure 17 NM-1VSAT-GILAT Network Module Satellite Backup for a Terrestrial Link: Sample Network Topology
!---Primary link configuration:!---Frame Relay requires a subinterface configurationinterface Serial0/2no ip addressencapsulation frame-relay!interface Serial0/2.1 point-to-pointip address 192.168.3.1 255.255.255.0backup interface Satellite1/0frame-relay interface-dlci 200...!---Backup link configurationinterface Satellite1/0ip address 172.24.1.3 255.255.0.0service-module ip address 172.24.1.1 255.255.0.0...!---RIPv2 configuration:!---Redistribute static routes to RIPv2!---The 192.168.3.0 network is the primary Frame Relay link.!---The 172.24.0.0 network is the backup satellite link.router ripversion 2redistribute staticnetwork 192.168.3.0network 172.24.0.0no auto-summary!Configuring Homogeneous HSRP Redundancy with the NM-1VSAT-GILAT Network Module—Shared ODU: Example
In the following example, the hot standby group consists of two routers, each equipped with an NM-1VSAT-GILAT network module. Both NM-1VSAT-GILAT network modules are connected to the same ODU.
The routers are each connected through interface Fast Ethernet 0/0 to the same subnet to establish the hot standby group, named "grp-hsrp." Although the routers have unique IP addresses, the designated IP address for the hot standby group is 10.0.0.100.
Because preemption is enabled on both routers, the router with the higher priority takes over as the active router. Both routers have the default priority value of 100, and they each track the installed satellite interface. If a satellite link goes down, that router's HSRP priority drops to 90, and the other router, which still has a priority of 100, becomes the active router.
Figure 18 shows the network topology for this setup.
Figure 18 Homogeneous HSRP Redundancy: Sample Network Topology
See the following sample router configurations:
Router1
!---For both routers, preemption and tracking are enabled.!---Also, both routers have the same priority (default 100).!interface FastEthernet0/0ip address 10.0.0.9 255.255.255.0standby 1 ip 10.0.0.100standby 1 preemptstandby 1 name grp-hsrpstandby 1 track Satellite1/0!!---Note that the hot standby group name (in this example,!---"grp-hsrp") must match exactly on the primary HSRP interface!---(Fast Ethernet 0/0) and on the satellite interface.!interface Satellite1/0ip address 10.1.1.2 255.255.255.0service-module ip redundancy grp-hsrp!!---The last command is required because two NM-1VSAT-GILAT network modules!---on separate routers are connected to the same ODU.Router2
!---Aside from the IP address of the Fast Ethernet interface,!---the Router1 and Router2 configurations are identical.interface FastEthernet0/0ip address 10.0.0.8 255.255.255.0standby 1 ip 10.0.0.100standby 1 preemptstandby 1 name grp-hsrpstandby 1 track Satellite1/0...interface Satellite1/0ip address 10.1.1.2 255.255.255.0service-module ip redundancy grp-hsrp!Configuring Heterogeneous HSRP Redundancy with the NM-1VSAT-GILAT Network Module—Primary Satellite Link with a Backup Terrestrial Link: Example
In the following example, the primary router (Router1) uses a satellite link, whereas the secondary router (Router2) uses a serial link. This setup provides terrestrial network connectivity when the satellite link fails.
Because preemption is enabled on both routers, the router with the higher priority takes over as the active router. Router1 tracks its satellite interface and has a higher configured priority (105) than Router2, which has a configured priority of 100. In normal working conditions, Router1 is the active router. If the tracked satellite interface goes down, the Router1 priority drops to 95. Because Router2 now has a higher priority (100), Router2 takes over as the active router. When the tracked satellite interface comes up again, the Router1 priority returns to 105, and Router1 becomes the active router.
Figure 19 shows the network topology for this setup.
Figure 19 Heterogeneous HSRP Redundancy: Sample Network Topology
See the following sample router configurations:
•
•
Router1 (Primary—Satellite Link)
!---For both routers, preemption is enabled.!---Note, however, that the HSRP priority value of Router1 (105)!---is higher than the HSRP priority value of Router2 (100).!interface FastEthernet0/0ip address 10.0.0.9 255.255.255.0standby 1 ip 10.0.0.100standby 1 priority 105standby 1 preemptstandby 1 track Satellite1/0!!---Router1 tracks the satellite interface. If the satellite!---link goes down, the Router1 priority falls below the Router2!---priority, so Router2 takes over as the active router.!---Because preemption is enabled, Router1 takes over as the active!---router as soon as the satellite link comes back up.!interface Satellite1/0ip address 10.1.1.2 255.255.255.0!Router2 (Secondary—Serial Link)
!---For both routers, preemption is enabled.!---Note, however, that the HSRP priority value of Router1 (105)!---is higher than the HSRP priority value of Router2 (100).!interface FastEthernet0/0ip address 10.0.0.8 255.255.255.0standby 1 ip 10.0.0.100standby 1 priority 100standby 1 preempt!!---Because preemption is enabled, Router2 takes over as the active!---router if the Router1 tracked satellite link goes down!---and reduces the Router1 priority to 95.!---When the satellite link comes back up, Router1 becomes the!---active router because Router1 has preemption enabled and!---has a higher priority (105).!interface Serial 1/0ip address 10.1.1.3 255.255.255.0!Configuring Heterogeneous HSRP Redundancy with the NM-1VSAT-GILAT Network Module—Backup Satellite Link for a Primary Terrestrial Link: Example
In the following example, the primary router (Router1) uses a serial link, whereas the secondary router (Router2) uses a satellite link. This setup preserves network connectivity when there is a problem at the terrestrial Internet service provider (ISP) or when the terrestrial network cables fail because of a backhoe event.
Because preemption is enabled on both routers, the router with the higher priority takes over as the active router. Router1 tracks its serial interface and has a higher configured priority (105) than Router2, which has a configured priority of 100 and tracks its satellite interface. Under normal working conditions, Router1 is the active router. If the tracked serial interface goes down, the Router1 priority drops to 95. Because Router2 now has a higher priority (100), Router2 takes over as the active router. When the tracked serial interface comes up again, Router1 once again becomes the active router.
If the tracked satellite link goes down, the Router2 priority drops to 90, which is always lower than that of Router1. Therefore, Router2 is always in standby mode when the satellite link is down.
Figure 20 shows the network topology for this setup.
Figure 20 Heterogeneous HSRP Redundancy: Sample Network Topology
See the following sample router configurations:
•
•
Router1 (Primary—Serial Link)
!---For both routers, preemption and tracking are enabled.!---Note, however, that the HSRP priority value of Router1 (105)!---is higher than the HSRP priority value of Router2 (100).interface FastEthernet0/0ip address 10.0.0.8 255.255.255.0standby 1 ip 10.0.0.100standby 1 priority 105standby 1 preemptstandby 1 track Serial 1/0!!---Router1 tracks the serial interface. If the serial!---link goes down, the Router1 priority falls below the Router2!---priority, so Router2 takes over as the active router.!---Because preemption is enabled, Router1 takes over as the active!---router as soon as the serial link comes back up.!interface Serial 1/0ip address 10.1.1.3 255.255.255.0!Router2 (Secondary—Satellite Link)
!interface FastEthernet0/0ip address 10.0.0.9 255.255.255.0standby 1 ip 10.0.0.100standby 1 preemptstandby 1 track Satellite1/0!!---Because Router2 tracks the satellite interface,!---Router2 cannot become the active router!---if the satellite link is down, because the!---effective priority of Router2 is still lower!---than that of Router1.!interface Satellite1/0ip address 10.1.1.2 255.255.255.0!Configuring IP Multicast Routing for the NM-1VSAT-GILAT Network Module: Example
In the following example, IP multicast routing is configured on the satellite and Fast Ethernet links. Note that certain IP address requirements apply when you use IP multicast routing over the satellite network. See the "IP Address Requirements for IP Multicast and Non-RIPv2 Routing Protocols" section.
!---Enable IP multicast routingip multicast-routing...!---LAN with hosts that can join the multicast groupinterface FastEthernet0/0ip address 10.1.0.1 255.255.255.0ip pim sparse-dense-modeduplex autospeed auto...!---Satellite link configuration:!---Notice that the NM-1VSAT-GILAT network module IP address!---does not appear in the configuration because it is!---automatically configured to 192.168.1.137 255.255.255.252.interface Satellite1/0ip address 192.168.1.138 255.255.255.0ip pim dr-priority 0ip pim sparse-dense-mode...!---The PIM RP is the hub router interface that connects to the hub protocol server.ip pim rp-address 192.168.1.5Additional References
The following sections provide references related to the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT) feature.
Related Documents
Installing and connecting the NM-1VSAT-GILAT network module
Regulatory compliance and safety information
Cisco Network Modules and Interface Cards Regulatory Compliance and Safety Information
IP multicast routing
Configuring terrestrial links
Cisco IOS Dial Technologies Configuration Guide
Cisco IOS Interface and Hardware Component Configuration Guide
Routing Information Protocol (RIP), RIP version 2 (RIPv2), and other routing protocols
Configuring backup links using backup interfaces or floating static routes
Evaluating Backup Interfaces, Floating Static Routes, and Dialer Watch for DDR Backup
Hot Standby Router Protocol (HSRP)
Cisco IOS IP Configuration Guide
Voice over IP
Rate Based Satellite Control Protocol (RBSCP)
Rate Based Satellite Control Protocol, Cisco IOS software feature module
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Command Reference
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.3 and Cisco IOS Release 12.3T command reference publications.
The following commands in Cisco IOS Release 12.3(14)T apply to the setup and operation of the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-Gilat).
•
•
•
•
•
•
•
•
•
The following commands in Cisco IOS Release 12.4(15)T apply to the security and QoS feature enhancements for the Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-Gilat).
•
apply (satellite initial configuration)
To save new or changed satellite initial configuration parameters and to reset the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the apply command in satellite initial configuration mode.
apply
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Satellite initial configuration mode
Command History
Usage Guidelines
The apply command saves any new or changed satellite initial configuration parameters to the nonvolatile memory of the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT) and initiates a network module software reset. Commands entered in satellite initial configuration mode do not appear in the router configuration.
When you enter the exit or end command to exit satellite initial configuration mode, the system automatically saves any changed parameters to the NM-1VSAT-GILAT network module's nonvolatile memory and resets the NM-1VSAT-GILAT network module.
Note
Examples
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)#Related Commands
debug satellite firmware
To enable debugging output for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT) firmware, use the debug satellite firmware command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug satellite firmware {all | level number | option}
no debug satellite firmware
Syntax Description
all
Displays all satellite firmware events.
level number
Satellite debug level. The debug level affects what information is displayed for subsequently entered debug satellite firmware commands. See Table 4.
option
One of the following options. See Table 1.
•
•
•
•
•
•
•
•
•
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The output from this command is generally useful for diagnostic tasks performed by technical support.
The level number affects which debug messages the system displays for subsequently entered debug satellite firmware commands. Table 4 describes what each command option displays at each debug level.
Note
Examples
This section provides the following sample output for the debug satellite firmware command:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Sample Output for the debug satellite firmware all Command
The following example shows all satellite firmware events and statistics:
Router# debug satellite firmware all2d06h: Satellite2/0buffers 4856 min 4486 list_str 683798 list_end 6885c8emp 686030 fil 685de0 start 6885c8 end fb4fe82d06h: Satellite2/0TCP stats: NetRXBytes=223 NetTXBytes=4775126 NetRxPkts=104213 ToIOSPkts=1041662d06h: Satellite2/0SAT stats: OUTbound_pkts=114131, INbound_pkts=1823472d06h: Satellite2/0RBCP statistics: TXcount=975 RXCount=9752d06h: Satellite2/0RPA stats: ToTunnel=0 FromTunnel=0TunnelGets=0 TunnelNotGets=0BlksUsed=0 BlksIn-Use=0 Max=3002d06h: Satellite2/0EN:RX encrypted bytes received = 0RX: compressed=0 -> Uncompressed=0TX: compressed=0 -> Uncompressed=02d06h: Satellite2/0BB 6 LINK state=INFO_STATEStatus = 0x79, LOW NOT READY, HI PRI READYRSP Q free=230, Max HI=228, Max LOW=224, Max DG=232IN RA modeCurr DG BW=50000, HighDG BW=100000, Curr BW=98094MaxDG BW=1250000, Max BW=2500000PD Queue lengths:q_wtog=0, q_wtos=57, q_wtos_high=0, q_defrag=dDG Queue lengths:q_dg_wtos=0, q_dg_wtos_hi=0, q_dg_defrag=0Congestion Levels: TX LOCAL = 7, TX NET = 02d06h: Satellite2/0IP stats: ToIOS_Pkts=234193, ToIOS_Bytes=183444492 FromIOS_Pkts=143 From_IOS_Bytes=122042d06h: Satellite2/0 NO Trace at levels 1 or 22d06h: Satellite2/0 NO Trace at levels 1 or 2Sample Output for the bb Option at Level 1
The following example shows backbone link information:
Router# debug satellite firmware level 1Router# debug satellite firmware bbsatellite BackBone events debugging is onRouter#2d06h: Satellite2/0BB 6 LINK state=INFO_STATEStatus = 0x79, LOW NOT READY, HI PRI READYRSP Q free=240, Max HI=228, Max LOW=224, Max DG=232IN RA modeCurr DG BW=50000, HighDG BW=100000, Curr BW=96188MaxDG BW=1250000, Max BW=2500000PD Queue lengths:q_wtog=0, q_wtos=95, q_wtos_high=0, q_defrag=dDG Queue lengths:q_dg_wtos=0, q_dg_wtos_hi=0, q_dg_defrag=0Congestion Levels: TX LOCAL = 7, TX NET = 02d06h: Satellite2/0BB 6 LINK state=INFO_STATEStatus = 0x7b, LOW READY, HI PRI READYRSP Q free=27, Max HI=228, Max LOW=224, Max DG=232IN RA modeCurr DG BW=50000, HighDG BW=100000, Curr BW=92376MaxDG BW=1250000, Max BW=2500000PD Queue lengths:q_wtog=0, q_wtos=24, q_wtos_high=0, q_defrag=dDG Queue lengths:q_dg_wtos=0, q_dg_wtos_hi=0, q_dg_defrag=0Congestion Levels: TX LOCAL = 4, TX NET = 0Sample Output for the bb Option at Level 2
The following example shows frame statistics for the backbone link to the hub:
Router# debug satellite firmware level 2Router# debug satellite firmware bbsatellite BackBone events debugging is onRouter#2d06h: Satellite2/0 BB link statisticsFrame Type # Received # Transmitted------------ ---------- -------------INFORMATION 00096238 00184811UNNUMBERED 00000000 00000067RETRANSMITTED 00000000 00000000POLLS 00000000 00000000ACKS 00006640 00000455NAKS 00000000 00000000PACKS 00000000 00000000UA 00000001 00000000SABME 00000000 00000001DISC 00000000 00000000Sample Output for the buf Option at Level 1
The following example shows buffer information:
Router# debug satellite firmware level 1Router# debug satellite firmware buf*May 13 15:58:54.498:Satellite1/0buffers 4951 min 4945 list_str 681858 list_end 686688emp 683abc fil 6839e8 start 686688 end fb30a8Sample Output for the buf Option at Level 2
The following example shows buffer owners:
Router# debug satellite firmware level 2Router# debug satellite firmware buf*May 13 15:59:13.438:Satellite1/0 inuse 49 free 4951Trace byte 1Trace byte = 0x169 Count = 49Trace byte 2Trace byte = 0x 0 Count = 490 buffers with BB Rel only0 buffers with in lower layer set0 buffers with do not transmit set0 buffers on BB retransmit queuesSample Output for the ip Option at Level 1
The following example shows IP statistics:
Router# debug satellite firmware level 1Router# debug satellite firmware ip*Nov 7 08:27:56.440: Satellite3/0IP stats: ToIOS_Pkts=0, ToIOS_Bytes=0 FromIOS_Pkts=84751 From_IOS_Bytes=5941124Sample Output for the rbcp Option at Level 1
The following example shows the number of RBCP messages transmitted and received since the most recent reset of the Cisco IOS software on the router or the VSAT software on the NM-1VSAT-GILAT network module:
Router# debug satellite firmware level 1Router# debug satellite firmware rbcpRBCP statistics:TXcount=301154 RXCount=301155Sample Output for the rpa Option at Level 1
The following example shows RPA statistics:
Router# debug satellite firmware level 1Router# debug satellite firmware rpa*Nov 7 08:27:13.488:Satellite3/0RPA stats:ToTunnel=0 FromTunnel=0TunnelGets=0 TunnelNotGets=0BlksUsed=0 BlksIn-Use=0 Max=400Sample Output for the rpa Option at Level 2
The following example shows a tunnel being disconnected:
Router# debug satellite firmware level 2Router# debug satellite firmware rpa*May 13 18:27:59.779:Satellite1/0 RPA Tunnel DOWNRPA:InitTunnelConn Successful locIP e000006 locPort 1090, RemIP c0a80186,RemPort 9876RPA Tunnel DOWNRPA:InitTunnelConn Successful locIP e000006 locPort 1091, RemIP c0a80186,RemPort 9876RPA Tunnel DOWNRPA:InitTunnelConn Successful locIP e000006 locPort 1092, RemIP c0a80186,RemPort 9876RPA Tunnel DOWNRPA:InitTunnelConn Successful locIP e000006 locPort 1093, RemIP c0a80186,RemPort 9876RPA Tunnel DOWNRPA:InitTunnelConn Successful locIP e000006 locPort 1094, RemIP c0a80186,RemPort 9876Sample Output for the sat Option at All Levels
The following example shows inbound and outbound packet statistics. Note that for all levels, the debug output is the same for the sat option.
Router# debug satellite firmware level 1Router# debug satellite firmware satsatellite related trace events debugging is onRouter#1d16h: Satellite2/0SAT stats: OUTbound_pkts=25660796, INbound_pkts=32359321d16h: Satellite2/0SAT stats: OUTbound_pkts=25660800, INbound_pkts=32359341d16h: Satellite2/0SAT stats: OUTbound_pkts=25660803, INbound_pkts=32359341d16h: Satellite2/0SAT stats: OUTbound_pkts=25660803, INbound_pkts=3235934Sample Output for the tcp Option at Level 1
The following example shows TCP statistics:
Router# debug satellite firmware level 1Router# debug satellite firmware tcpsatellite tcp events debugging is onRouter#2d06h: Satellite2/0TCP stats: NetRXBytes=631292 NetTXBytes=4009436 NetRxPkts=49244 ToIOSPkts=492462d06h: Satellite2/0TCP stats: NetRXBytes=1154356 NetTXBytes=4086106 NetRxPkts=49621 ToIOSPkts=49629Sample Output for the tcp Option at Level 2
The following example shows the TCP connections:
Router# debug satellite firmware level 2Router# debug satellite firmware tcpsatellite tcp events debugging is onRouter#2d06h: Satellite2/0 TCP connections:ID=48, locIP=192.168.107.2 remIP=172.25.1.2, locP=2962, remP=21 state=17 iosQ=0ID=49, locIP=192.168.107.2 remIP=172.25.1.2, locP=2963, remP=20 state=17 iosQ=0ID=58, locIP=192.168.107.2 remIP=172.25.1.28, locP=2972, remP=21 state=17 iosQ=0ID=59, locIP=192.168.107.2 remIP=172.25.1.28, locP=2973, remP=20 state=17 iosQ=72d06h: Satellite2/0 TCP connections:ID=48, locIP=192.168.107.2 remIP=172.25.1.2, locP=2962, remP=21 state=17 iosQ=0ID=49, locIP=192.168.107.2 remIP=172.25.1.2, locP=2963, remP=20 state=7 iosQ=0ID=60, locIP=192.168.107.2 remIP=172.25.1.28, locP=2974, remP=21 state=3 iosQ=0Sample Output for the tcp Option at Level 3
The following example shows TCP statistics and connections:
Router# debug satellite firmware level 3Output may be extensive and affect performance. Continue? [yes]: yesRouter# debug satellite firmware tcpsatellite tcp events debugging is onRouter#2d06h: Satellite2/0TCP stats: NetRXBytes=279 NetTXBytes=9436111 NetRxPkts=64991 ToIOSPkts=649992d06h: Satellite2/0 TCP connections:ID=48, locIP=192.168.107.2 remIP=172.25.1.2, locP=2962, remP=21 state=7 iosQ=0ID=49, locIP=192.168.107.2 remIP=172.25.1.2, locP=2963, remP=20 state=7 iosQ=0ID=62, locIP=192.168.107.2 remIP=172.25.1.28, locP=2976, remP=21 state=7 iosQ=02d06h: Satellite2/0TCP stats: NetRXBytes=382 NetTXBytes=9582924 NetRxPkts=64993 ToIOSPkts=650012d06h: Satellite2/0 TCP connections:ID=48, locIP=192.168.107.2 remIP=172.25.1.2, locP=2962, remP=21 state=17 iosQ=0ID=49, locIP=192.168.107.2 remIP=172.25.1.2, locP=2963, remP=20 state=17 iosQ=0ID=62, locIP=192.168.107.2 remIP=172.25.1.28, locP=2976, remP=21 state=7 iosQ=0Sample Output for the trc Option at Level 3
The following example shows detailed receive and transmit traces for the backbone link:
Router# debug satellite firmware level 3Output may be extensive and affect performance. Continue? [yes]: yesRouter# debug satellite firmware trcsatellite BackBone trace debugging is onRouter#2d06h: Satellite2/0 strrec 0, rec 0, count 256, trc 1a6dd78, str 1a5c600, end 1a74600count 4096, emp 1a6dd78, fil 1a6d8b0, lnknum=60 xmt 6 len 951 9 pd con 0 PF 3 ns 169 nr 15 a c12 0 0.0001 xmt 6 len 951 9 pd con 0 PF 3 ns 170 nr 15 a c12 0 0.0102 xmt 6 len 951 9 pd con 0 PF 3 ns 171 nr 15 a c12 0 0.0103 xmt 6 len 951 9 pd con 0 PF 3 ns 172 nr 15 a c12 0 0.0104 xmt 6 len 951 9 pd con 0 PF 3 ns 173 nr 15 a c12 0 0.0305 xmt 6 len2d06h: Satellite2/0 9512d06h: Satellite2/0 9 pd con 0 PF 3 ns 174 nr 15 a c12 0 0.0106 xmt 6 len 951 9 pd con 0 PF 3 ns 175 nr 15 a c12 0 0.0107 xmt 6 len 951 9 pd con 0 PF 3 ns 176 nr 15 a c12 0 0.0108 xmt 6 len 951 9 pd con 0 PF 3 ns 177 nr 15 a c12 0 0.0109 xmt 6 len 951 9 pd con 0 PF 3 ns 178 nr 15 a c12 0 0.01010 xmt 6 len 951 9 pd con 0 PF 3 ns 179 nr 15 a c12 0 0.01011 xmt 6 len 951 9 pd con 0 PF 3 ns 180 nr 15 a c12 0 0.010Related Commands
debug satellite
Enables debugging output for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT).
debug satellite
To enable debugging output for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the debug satellite command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug satellite {all | errors | events | hsrp | rbcp}
no debug satellite {all | errors | events | hsrp | rbcp}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug satellite errors command is useful for catching unusual conditions when troubleshooting unexpected behavior. Because this command typically generates very little output, you can enter the debug satellite errors command every time you troubleshoot satellite network connectivity.
Examples
This section provides the following examples:
•
•
•
•
Sample Output for the debug satellite rbcp Command
Every 2 minutes, the NM-1VSAT-GILAT network module sends the router an RBCP message requesting any updates to the routing table. The following example shows how to monitor the route-update messages:
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)Sample Output for the debug satellite events Command
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.Dec 16 12:57:52.108:Satellite1/0 FSM transition LINK_UP-->LINK_UP, ev=got_heartbeat.Dec 16 12:58:08.888:Satellite1/0 FSM transition LINK_UP-->LINK_UP, ev=got_heartbeat.Dec 16 12:58:25.664:Satellite1/0 FSM transition LINK_UP-->LINK_UP, ev=got_heartbeat.Dec 16 12:58:42.440:Satellite1/0 FSM transition LINK_UP-->LINK_UP, ev=got_heartbeatSample Output for the debug satellite hsrp Command
The following example shows the debug satellite hsrp command 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 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 10.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 also changes from standby to active state because the service-module ip redundancy command was previously entered to link the HSRP status of the satellite interface to the primary HSRP interface, Fast Ethernet 0/0.
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.100Related Commands
end (satellite initial configuration)
To exit satellite initial configuration mode, save any new or changed parameters, and reset the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the end command in satellite initial configuration mode.
end
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
The end command is identical to the exit command in satellite initial configuration mode.
When you enter the exit or end command to exit satellite initial configuration mode, the system automatically saves any changed parameters to the NM-1VSAT-GILAT network module nonvolatile memory and resets the NM-1VSAT-GILAT network module.
Examples
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#Related Commands
exit (satellite initial configuration)
To exit satellite initial configuration mode, save any new or changed parameters, and reset the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the exit command in satellite initial configuration mode.
exit
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
The exit command is identical to the end command in satellite initial configuration mode.
When you enter the exit or end command to exit satellite initial configuration mode, the system automatically saves any changed parameters to the NM-1VSAT-GILAT network module nonvolatile memory and resets the NM-1VSAT-GILAT network module.
Examples
The following example shows what appears when you enter the exit or end command after changing one or more initial configuration parameters:
Router(sat-init-config)# exitApplying changed parameters to the satellite module.Parameter update succeeded. Module is now resetting.Router#The following example shows what appears when you enter the exit or end command when no parameters have been changed:
Router(sat-init-config)# exitRouter#Related Commands
id aa-group
To configure the asynchronous acknowledgement group ID, use the id aa-group command in satellite initial configuration mode. To remove the ID configuration, use the no form of this command.
id aa-group number
no id aa-group
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the asynchronous acknowledgement group identification number:
Router(sat-init-config)# id aa-group 336id software group
To configure the operational software group identification number, use the id software group command in satellite initial configuration mode. To remove the ID configuration, use the no form of this command.
id software group number
no id software group
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the operational software group identification number:
Router(sat-init-config)# id software group 598id vsat
To configure the component physical address (CPA), use the id vsat command in satellite initial configuration mode. To remove the CPA configuration, use the no form of this command.
id vsat number
no id vsat number
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
12.3(14)T
This command was introduced.
12.4(22)T
The CPA number range was increased to 32766.
Usage Guidelines
The CPA uniquely identifies the VSAT endpoint in the satellite network.
Note
Examples
The following example shows how to configure the CPA number:
Router(sat-init-config)# id vsat 1284interface satellite
To enter satellite interface configuration mode, use the interface satellite command in global configuration mode.
interface satellite slot/unit
Syntax Description
slot
Router chassis slot in which the network module is installed.
unit
Interface number. For NM-1VSAT-GILAT network modules, always use 0.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Examples
The following example shows how to enter satellite interface configuration mode:
Router(config)# interface satellite 1/0Router(config-if)#Related Commands
mode download
To enable operational code download mode for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the mode download command in satellite initial configuration mode. To disable operational code download mode, use the no form of this command.
mode download
no mode download
Syntax Description
This command has no arguments or keywords.
Defaults
Operational code download mode is enabled.
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to disable operational code download mode:
Router(sat-init-config)# no mode downloadmode two-way
To enable two-way operational mode for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the mode two-way command in satellite initial configuration mode. To revert to one-way operational mode, use the no form of this command.
mode two-way
no mode two-way
Syntax Description
This command has no arguments or keywords.
Defaults
Two-way mode is enabled.
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to specify two-way operational mode:
Router(sat-init-config)# mode two-wayThe following example shows how to specify one-way operational mode:
Router(sat-init-config)# no mode two-wayoutbound data-pid
Note
To specify the outbound data packet identification (PID) number, use the outbound data-pid command in satellite initial configuration mode. To remove the PID number configuration, use the no form of this command.
outbound data-pid number
no outbound data-pid
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
12.3(14)T
This command was introduced.
12.4(2)T
This command was superseded by the outbound pid management command.
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to specify the outbound data PID number:
Router(sat-init-config)# outbound data-pid 3000outbound data-rate
To specify the VSAT data rate, use the outbound data-rate command in satellite initial configuration mode. To remove the data rate configuration, use the no form of this command.
outbound data-rate rate
no outbound data-rate
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to specify the VSAT data rate:
Router(sat-init-config)# outbound data-rate 450000outbound frequency
To specify the VSAT outbound frequency, use the outbound frequency command in satellite initial configuration mode. To remove the outbound frequency configuration, use the no form of this command.
outbound frequency frequency
no outbound frequency
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the VSAT outbound frequency:
Router(sat-init-config)# outbound frequency 950000outbound id
To specify the VSAT outbound ID, use the outbound id command in satellite initial configuration mode. To remove the outbound ID configuration, use the no form of this command.
outbound id number
no outbound id
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the VSAT outbound ID:
Router(sat-init-config)# outbound id 95outbound modulation-type
To specify the VSAT modulation type, use the outbound modulation-type command in satellite initial configuration mode. To remove the VSAT modulation type configuration, use the no form of this command.
outbound modulation-type {DVB | TURBO_QPSK | 8PSK}
no outbound modulation-type
Syntax Description
DVB
Digital Video Broadcasting for satellite.
TURBO_QPSK
Turbo-coded quadrature Phase Shift Keying.
8PSK
Phase Shift Keying.
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the VSAT modulation type:
Router(sat-init-config)# outbound modulation-type DVBoutbound sync ip address
To specify the outbound synchronization IP address, use the outbound sync ip address command in satellite initial configuration mode. To remove the outbound synchronization IP address configuration, use the no form of this command.
outbound sync ip address address
no outbound sync ip address
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the outbound synchronization IP address:
Router(sat-init-config)# outbound sync ip address 10.2.2.2outbound viterbi-rate
To specify the VSAT Viterbi code rate, use the outbound viterbi-rate command in satellite initial configuration mode. To return to the default rate, use the no form of this command.
outbound viterbi-rate rate
no outbound viterbi-rate
Syntax Description
rate
Viterbi code rate. It can be one of the following values:
•
•
•
•
•
•
•
•
•
•
•
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the VSAT Viterbi code rate:
Router(sat-init-config)# outbound viterbi-rate 3/4(2.6)password (satellite initial configuration)
To define or to change the password of the NM-1VSAT-GILAT network module required to enter satellite initial configuration mode, use the password command in the satellite initial configuration mode.
password password
Syntax Description
Command Default
The factory-supplied default password is active.
Command Modes
Satellite initial configuration.
Command History
12.4(11)XJ2
This command was introduced.
12.4(15)T
This command was integrated into Cisco IOS Release 12.4(15)T.
Usage Guidelines
The NM-1VSAT-GILAT network module has a factory-supplied unique default password to enter satellite initial configuration mode for initial configuration. During this configuration, the password command is used to set a user-defined password for subsequent entries to satellite initial configuration mode. The user-defined password consists of up to 32 alphanumeric characters.
Examples
The following example shows how to enter a user-defined password:
Router(sat-init-config)# password vsatuserservice-module backup interface
To configure an interface as a secondary or dial backup to the satellite interface, use the service module backup interface command in satellite interface configuration mode. To remove the backup interface configuration, use the no form of this command.
service module backup interface interface
no service module backup interface interface
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite interface configuration
Command History
Examples
The following example shows how to set interface async 1 as the backup to the satellite link:
Router(config-if)# service-module backup interface async1Related Commands
service-module backup mode
Sets the terrestrial backup mode for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT).
service-module backup mode
To set the terrestrial dial backup mode for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the service-module backup mode command in satellite interface configuration mode. To return to the router (default) dial backup mode, use the no form of this command.
service-module backup mode [hub | router]
no service-module backup mode
Syntax Description
Defaults
Router dial backup mode
Command Modes
Satellite interface configuration
Command History
Usage Guidelines
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.
Router Dial Backup Mode
If the satellite link goes down in router dial backup mode, the router uses DDR to send data out a different interface. Unlike hub dial backup mode, router dial backup mode does these things:
•
•
Examples
The following example shows how to specify hub backup mode:
Router(config-if)# service-module backup mode hubThe following example shows how to specify router backup mode:
Router(config-if)# service-module backup mode routerRelated Commands
service-module backup interface
Specifies the interface to use to back up the satellite interface.
service-module ip address
To define the IP address for the internal network-module-side interface on a content engine network module (NM-CE-BP) or Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the service-module ip address command in content-engine interface configuration mode or satellite interface configuration mode. To delete the IP address associated with this interface, use the no form of this command.
service-module ip address nm-side-ip-addr subnet-mask
no service-module ip address
Syntax Description
Defaults
No default behavior or values
Command Modes
Content-engine interface configuration
Satellite interface configurationCommand History
Usage Guidelines
Content Engine Network Module (NM-CE-BP)
There are no usage guidelines for this command.
Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
For the NM-1VSAT-GILAT network module, the service-module ip address command is typically not used. The NM-1VSAT-GILAT network module IP address is automatically configured when you enter the ip address command in satellite interface configuration mode to configure the IP address and subnet mask of the router satellite interface with these conditions:
•
•
If you use this method to configure the IP address for the router satellite interface, 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
Examples
This section provides the following examples:
•
Content Engine Network Module (NM-CE-BP) Example
The following example shows how to define an IP address for the internal network-module-side interface on the CE network module in slot 1:
Router(config)# interface content-engine 1/0Router(config-if)# service-module ip address 172.18.12.26 255.255.255.0Router(config-if)# exitCisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
Example—Manually Configuring the IP AddressIn 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...Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
Example—Using the Automatically Configured IP AddressIn 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!Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-GILAT)
Example—Overriding the Automatically Configured IP AddressIn 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!Related Commands
service-module ip redundancy
To link the primary HSRP interface status to that of the satellite interface, use the service-module ip redundancy command in satellite interface configuration mode. To remove the link between the primary HSRP interface status and the satellite interface status, use the no form of this command.
service-module ip redundancy group-name
no service-module ip redundancy group-name
Syntax Description
group-name
Name of the hot standby group. This name must match the hot standby group name configured for the primary HSRP interface, which is typically an Ethernet interface.
Defaults
HSRP is disabled.
Command Modes
Satellite interface configuration
Command History
12.3(14)T
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Use the service-module ip redundancy command only when you have two Cisco IP VSAT satellite WAN network modules (NM-1VSAT-GILAT) on separate HSRP-redundant routers that connect to the same outdoor unit (ODU).
This command enables the satellite interface to spoof the line protocol UP state.
Examples
The following example shows how to link the primary HSRP interface status to that of the satellite interface:
service-module ip redundancy grp-hsrpRelated Commands
service-module itae
To configure a pre-built access list for integrated TCP acceleration and encryption (ITAE) in the NM-1VSAT-GILAT network module, use the service-module itae command in the satellite initial configuration mode. To disable the packet acceleration configuration, use the no form of this command.
service-module itae {auto-acl}
no service-module itae
Syntax Description
auto-acl
Enables automatic configuration of the service provider-supplied pre-built access list for packet acceleration and encryption.
Command Default
Packet acceleration and encryption is not enabled for traffic between the hub and the NM-1VSAT-GILAT network module.
Command Modes
Satellite initial configuration.
Command History
12.4(11)XJ2
This command was introduced.
12.4(15)T
This command was integrated into Cisco IOS Release 12.4(15)T.
Examples
The following example shows how to enter satellite configuration mode and configure the pre-built access list for ITAE:
Router> interface Satellite1/0Router(sat-init-config)# service module itae auto-aclRelated Commands
service-module status
Verifies that ITAE is enabled and configured properly on the VSAT from the hub.
service-module routing redistribute
To enable the router to send its routing database to the satellite network central hub, use the service-module routing redistribute command in satellite interface configuration mode. To prevent the router from sending its routing database over the satellite network, use the no form of this command.
service-module routing redistribute
no service-module routing redistribute
Syntax Description
This command has no arguments or keywords.
Defaults
The router is enabled to send its routing database to the hub.
Command Modes
Satellite interface configuration
Command History
Usage Guidelines
The service-module routing redistribute command is used on a VSAT router, that is, an earthbound modular access router equipped with a Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT) that connects to a satellite network. When VSAT route updates are enabled, the NM-1VSAT-GILAT network module uses Router Blade Configuration Protocol (RBCP) messages to communicate VSAT routing table changes to the hub.
Entering the no service-module routing redistribute command is useful when you do not want the hub to be aware of all the routes known by the VSAT router, such as when Network Address Translation (NAT) is configured on the router.
The hub must learn the remote VSAT routing database for the satellite network to function properly. Therefore, if you enter the no service-module routing redistribute command, then one of the following actions is required:
•
•
Examples
The following example shows how to prevent the VSAT router from sending its routing database to the satellite network central hub:
Router(config-if)# no service-module routing redistributeservice-module satellite backup
To test the hub dial backup connection for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the service-module satellite backup command in privileged EXEC mode.
service module satellite slot/unit backup {initiate | terminate}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The service-module satellite backup command is used only when you configure hub dial backup for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT).
Normally, the hub dial backup connection comes up only when the satellite link goes down (for example, because of a rain-fade event). The service-module satellite backup command allows you to artificially bring down the satellite link to test the hub dial backup connection.
Examples
The following example shows how to initiate a satellite backup test:
Router# service-module satellite 1/0 backup initiateThe following example shows how to terminate a running satellite backup test:
Router# service-module satellite 1/0 backup terminateRelated Commands
service-module satellite configuration
To enter satellite initial configuration mode, use the service-module satellite configuration command in user EXEC or privileged EXEC mode.
service-module satellite slot/unit configuration
Syntax Description
slot
Router chassis slot in which the network module is installed.
unit
Interface number. For NM-1VSAT-GILAT network modules, always use 0.
Defaults
No default behavior or values.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
You need a password from your satellite service provider to enter satellite initial configuration mode.
The parameters that you configure in satellite initial configuration mode are saved directly to the network module and do not appear in the router configuration, even though you configure the parameters through the Cisco IOS CLI.
To view the parameter values that were configured in satellite initial configuration mode, use one of the following commands:
•
•
Note
Examples
The following example shows how to enter satellite initial configuration mode:
Router> service-module satellite 1/0 configurationPassword: <mypassword>Reminder:changing any parameters will result in a software reset of the module.Router(sat-init-config)>Related Commands
service-module satellite cw-mode
To enable or disable continuous wave mode, use the service-module satellite cw-mode command in satellite interface configuration mode.
service-module satellite slot/unit cw-mode {off | on frequency frequency [time time]}
Syntax Description
Defaults
Continuous wave mode is disabled.
If the time is not specified, continuous wave mode continues until turned off.
Command Modes
Privileged EXEC
Command History
12.3(14)T
This command was introduced.
12.4(2)T
A password challenge was added to the command-line interface when continuous wave mode is enabled.
Usage Guidelines
Continuous wave mode can be enabled only when the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT) is in boot mode.
When continuous wave mode is enabled, the NM-1VSAT-GILAT network module transmits unmodulated carrier waves that can be used for dish antenna orientation adjustments and for signal quality measurements.
Note
Note
Examples
The following example shows how to enable continuous wave mode for 2 minutes, at 900000 kilohertz:
Router# service-module satellite 1/0 cw-mode on frequency 900000 time 120Password: <mypassword>CW mode obtained.The following example shows how to disable continuous wave mode:
Router# service-module satellite 1/0 cw-mode offCW mode released.The following example shows the message that appears when you try to enable continuous wave mode while the NM-1VSAT-GILAT network module is not in boot mode:
Router# service-module satellite 1/0 cw-mode on frequency 900000 time 120Password <mypassword>% CW mode NOT obtained! Valid during boot mode only.service-module satellite status
To display status information related to the hardware and software on the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), including the initial configuration parameters, use the service-module satellite status command in privileged EXEC mode.
service-module satellite slot/unit status [log]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the service-module satellite status command to troubleshoot the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT).
Examples
See Table 5 for service-module satellite status command output field descriptions.
This section provides the following examples:
Normal Operation Example
The following example shows that the link to the hub (backbone status) is up, as is expected in normal working conditions:
Router# service-module satellite 2/0 statusGetting status from the satellite module, please wait..Software Versions, OS:14.2.2, RSP:1.5.1.3, MBC:1.0.0.5HW Version:00008100CPA Number:6204, HPS CPA:1, HSP Link:2AA Group: 258, 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:NONEBoot Mode Example
The following example shows that the NM-1VSAT-GILAT network module is in boot mode after a software reset, so that the link to the hub (backbone status) is down:
Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS:0.0.0, RSP:1.0.0.5, MBC:0.0.0.0HW Version:001D1757CPA Number:6204, HPS CPA:0, HSP Link:2AA Group: 258, SW Group: 512, Download: YESService Module Uptime:00:00:14, Router Uptime:1 day, 20 hours, 19 minutesCurrent router clocktime:*03:04:38.017 UTC Tue Dec 2 2003Oper Mode:BOOT, In Dial Backup:NO, Standby:NO, One-Way:NORBCP Received Packets:1, RBCP Sent Packets:8Bit Error Rate:0e-0, Signal to Noise Ratio:12.4453IP Address/Mask:172.27.1.54/255.255.255.252Service Module MAC:00:A0:AC:00:20:60RX Lock:LOCKED, Sync Lock:NOT LOCKEDBackBone Status:DOWN, Two-Way Mode:YES, DA/RA 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.22.0.3Inbound Start Freq:1201176, IB Stop Freq:1209336Inbound Data Rate:307200, IB Freq Offset:0COUNTERS OMITTED. Not available at this time.Internal Software State parameters:Service Module SW State Var:3General IOS FSM:LINK_DOWN, HSRP FSM:ACTIVE, HSRP VSAT Mode:ACTIVELost Beats Total:0, Lost Beats This Retry:0VOIP DA calls:NONESoftware Reset Example
The following example shows what appears during the beginning stages of a software reset:
Router# service-module satellite 2/0 statusGetting status from the satellite module, please wait..% Satellite2/0 card is busy. Status is not available. Try later.Hub Dial Backup Example
The following example shows that the hub dial backup link is being used instead of the satellite link. Note, however, that hub dial backup keeps the backbone status up. In hub dial backup mode, the NM-1VSAT-GILAT network module connects to the hub over a specified dial backup link and maintains TCP connections.
Router# service-module satellite 1/0 statusGetting status from the satellite module, please wait..Software Versions, OS:14.2.3, RSP:1.5.1.3, MBC:1.0.0.5HW Version:00008100CPA Number:3201, HPS CPA:1, HSP Link:2AA Group: 258, SW Group: 512, Download: YESService Module Uptime:02:09:38, Router Uptime:2 hours, 10 minutesCurrent router clocktime:*19:28:20.195 UTC Wed Apr 7 2004Oper Mode:OPERATIONAL, In Dial Backup:YES, Standby:NO, One-Way:NORBCP Received Packets:31511, RBCP Sent Packets:31358Bit Error Rate:0e-0, Signal to Noise Ratio:12.4453IP Address/Mask:10.0.0.100/255.255.255.0Service Module MAC:00:A0:AC:00:20:66RX Lock:LOCKED, Sync Lock:NOT LOCKEDBackBone Status:UP, Two-Way Mode:YES, DA/RA Mode:RAOutbound Modulation Type:DVB, OB Code Rate:3/4Outbound Unicast Packets:39944, OB Multicast Packets:45612Outbound 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:8281BackBone Hub Link Status:UPBackBone Received Packets:37894, BB Sent:39162BackBone Received Retransmitted:1, BB Sent Retrans:12Service Module Eth RX:37840, TX:129000Service Module Eth Multicast RX:202, Multicast TX:45970Bufs Configured:5000, Bufs Free:4949Internal Software State parameters:Service Module SW State Var:3General IOS FSM:LINK_UP, HSRP FSM:N/A, HSRP VSAT Mode:N/ALost Beats Total:0, Lost Beats This Retry:0VoIP Example
The following example shows the status of VoIP calls. 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:14.2.3, RSP:1.5.1.3, MBC:1.0.0.5HW Version:00008100CPA Number:6202, HPS CPA:1, HSP Link:2AA Group: 258, SW Group: 512, Download: YESService Module Uptime:00:34:53, Router Uptime:2 days, 21 hours, 23 minutesCurrent router clocktime:*08:33:51.301 UTC Mon Feb 16 2004Oper Mode:OPERATIONAL, In Dial Backup:NO, Standby:NO, One-Way:NORBCP Received Packets:335, RBCP Sent Packets:332Bit Error Rate:0e-0, Signal to Noise Ratio:12.4453IP Address/Mask:10.2.0.2/255.255.0.0Service Module MAC:00:A0:AC:00:20:67RX Lock:LOCKED, Sync Lock:LOCKEDBackBone Status:UP, Two-Way Mode:YES, DA/RA Mode:DAOutbound Modulation Type:DVB, OB Code Rate:3/4Outbound Unicast Packets:758, OB Multicast Packets:139823Outbound 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:346BackBone Hub Link Status:UPBackBone Received Packets:335, BB Sent:288BackBone Received Retransmitted:0, BB Sent Retrans:0Service Module Eth RX:356, TX:280163Service Module Eth Multicast RX:1, Multicast TX:139918Bufs Configured:5000, Bufs Free:4951Internal Software State parameters:Service Module SW State Var:3General IOS FSM:LINK_UP, HSRP FSM:N/A, HSRP VSAT Mode:N/ALost Beats Total:0, Lost Beats This Retry:0VOIP DA calls:Call ID BW (kb) Dst Port Src Port Dest Addr======== ======= ======== ======== ==============16075 26 18310 16866 162.0.0.2Firmware Debug Log Example
The following example includes the firmware debug message log:
Router# service-module satellite 1/0 status logGetting status from the satellite module, please wait..Software Versions, OS:14.2.3, RSP:1.5.1.3, MBC:1.0.0.5HW Version:00008100CPA Number:1203, HPS CPA:1, HSP Link:2AA Group: 258, SW Group: 512, Download: YESService Module Uptime:19:01:32, Router Uptime:1 week, 4 days, 16 hours,15 minutesCurrent router clocktime:*15:12:45.310 UTC Mon May 13 2002Oper Mode:OPERATIONAL, In Dial Backup:NO, Standby:NO, One-Way:NORBCP Received Packets:9279, RBCP Sent Packets:9276Bit Error Rate:0e-0, Signal to Noise Ratio:12.4453IP Address/Mask:14.0.0.6/255.255.255.0Service Module MAC:00:A0:AC:00:20:72RX 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:11099797, OB Multicast Packets:429401Outbound 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:674619BackBone Hub Link Status:UPBackBone Received Packets:11084921, BB Sent:93899BackBone Received Retransmitted:352, BB Sent Retrans:2Service Module Eth RX:10001424, TX:18532485Service Module Eth Multicast RX:2615, Multicast TX:431486Bufs Configured:5000, Bufs Free:1240Internal Software State parameters:Service Module SW State Var:3General IOS FSM:LINK_UP, HSRP FSM:N/A, HSRP VSAT Mode:N/ALost Beats Total:4, Lost Beats This Retry:0VOIP DA calls:NONELast forced reset log from card===============================bb 01 e3 a3 28 00 00 10 00 01 ff 6f f0 00 00 1000 00 2a aa 00 4f f9 5f c4 00 00 01 2a ff ff ffff 00 00 80 00 01 ff 6f f0 00 00 00 00 01 ff 76b0 01 e3 a3 28 00 00 90 02 00 00 00 00 00 00 0013 00 18 84 1c 00 00 00 00 01 e3 a3 28 00 2b 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 2b 00 00 01 ff 76 b0 00 2a a2 80 00 00 8888 00 00 90 02 00 0a 7f 58 00 00 00 00 00 00 0000 40 00 00 43 20 00 00 00 00 00 00 00 01 ff 76b0 00 00 00 00 01 ff 70 20 ff ff ffTable 5 describes the significant fields shown in the displays.
Related Commands
show (satellite initial configuration)
To display the initial configuration parameters for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the show command in satellite initial configuration mode.
show
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
You can view the satellite initial configuration parameters by entering the service-module satellite slot/0 status command in privileged EXEC mode.
Examples
The following example shows the satellite initial configuration parameters for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT):
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)#Related Commands
show controllers satellite
To display controller information about the internal router interface that connects to an installed Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the show controllers satellite command in user EXEC or privileged EXEC mode.
show controllers satellite slot/unit
Syntax Description
slot
Router chassis slot in which the network module is installed.
unit
Interface number. For NM-1VSAT-GILAT network modules, always use 0.
Defaults
No default behavior or values.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The output from this command is generally useful for diagnostic tasks performed by technical support.
The show controllers satellite command displays information about initialization block, transmit ring, receive ring, and errors for the Fast Ethernet controller chip in the internal router interface that connects to an installed Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT).
Examples
The following example shows how to display controller information about the internal router interface that connects to an installed NM-1VSAT-GILAT network module:
Router# show controllers satellite 2/0Interface Satellite2/0Hardware is Intel 82559 FastEthernetIDB:640B6584, FASTSEND:60A585E0, MCI_INDEX:0INSTANCE=0x640B7D84Rx Ring entries = 64Rx Shadow = 0x640B8054Rx Ring = 0x 70FEE80Rx Ring Head = 51Rx Ring Last = 50Rx Buffer Descr = 0x 70FF2C0Rx Buffer Descr Head = 51Rx Buffer Descr Last = 50Rx Shadow (malloc) = 0x640B8054Rx Ring (malloc) = 0x 70FEE80Rx Buffer Descr (malloc) = 0x 70FF2C0Tx Ring entries = 128Tx Shadow = 0x640B8184Tx Shadow Head = 78Tx Shadow Tail = 78Tx Shadow Free = 128Tx Ring = 0x 70FF700Tx Head = 80Tx Last = 79Tx Tail = 80Tx Count = 0Tx Buffer Descr = 0x 7100740Tx Buffer Descr Head = 0Tx Buffer Descr Tail = 0Tx Shadow (malloc) = 0x640B8184Tx Ring (malloc) = 0x 70FF700Tx Buffer Descr (malloc) = 0x 7100740CONTROL AND STATUS REGISTERS (CSR)=0x3E000000SCB Intr Mask = 00SCB CU/RU Cmd = 00SCB Intr Status = 00SCB CU Status = 01SCB RU Status = 04SCB General Ptr = 00000000PORT = 00000000EEPROM = 0008FLASH = 0002MDI = 1821780DRx Byte Count = 00000608PMDR = 80FC Cmd = 00FC Threshold = 03Early Rx = 00General Status = 03General Control = 00PHY REGISTERSRegister 0x00: 2000 780D 02A8 0154 0081 0000 0000 0000Register 0x08: 0000 0000 0000 0000 0000 0000 0000 0000Register 0x10: 0202 0000 0001 0005 0000 0000 0000 0000Register 0x18: 0000 0000 8B10 0000 0010 0000 0000 0000HARDWARE STATISTICSRx good frames: 420979Rx CRC: 0Rx alignment: 0Rx resource: 0Rx overrun: 0Rx collision detects: 0Rx short: 0Tx good frames: 653125Tx maximum collisions: 0Tx late collisions: 0Tx underruns: 0Tx lost carrier sense: 9Tx deferred: 86Tx single collisions: 1Tx multiple collisions:1Tx total collisions: 3FC Tx pause: 0FC Rx pause: 0FC Rx unsupported: 0INTERRUPT STATISTICSCX = 653136FR = 420979CNA = 0RNR = 0MDI = 0SWI = 0FCP = 0Receive All Multicasts = enabledReceive Promiscuous = disabledLoopback Mode = disabledTable 6 describes the significant fields shown in the display.
Related Commands
show interfaces satellite
To display general interface settings and traffic rates for the internal router interface that connects to an installed Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the show interfaces satellite command in user EXEC or privileged EXEC mode.
show interfaces satellite slot/unit
Syntax Description
slot
Router chassis slot in which the network module is installed.
unit
Interface number. For NM-1VSAT-GILAT network modules, always use 0.
Defaults
No default behavior or values.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show interfaces satellite command shows these items:
•
•
•
–
–
Line Protocol Status Exception—Hub Dial Backup Mode
If you configure hub dial backup mode on the satellite interface, then the show interfaces satellite command always displays Line Protocol Up status, even when the line protocol is down. To view the actual line protocol status, enter the show controllers satellite command or the service-module satellite slot/0 status command in privileged EXEC mode.
Line Protocol Status Exception—Hot Standby Router Protocol (HSRP) Standby Mode
If the router is in a hot standby group and is in standby mode, then the show interfaces satellite command displays "line protocol is up (standby)", even though a link to the hub is not established from the standby router. To view the actual line protocol status, enter the show controllers satellite command or the service-module satellite slot/0 status command in privileged EXEC mode.
Examples
For output field descriptions, see Table 7.
This section provides the following examples:
•
•
•
Normal Operation or Hub Dial Backup Mode Example
In the following example, the satellite interface is up and the line protocol is up.
If you configure hub dial backup for the NM-1VSAT-GILAT network module, the line protocol appears to be up even if the satellite link is actually down. To view the actual line protocol status while hub dial backup mode is configured, use the show controllers satellite command or the service-module satellite slot/0 status command instead.
Router# show interfaces satellite 2/0Satellite2/0 is up, line protocol is upHardware is I82559FE, address is 0008.e35f.7370 (bia 0008.e35f.7370)Internet address is 10.22.1.2/24MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive not setARP type:ARPA, ARP Timeout 04:00:00Last input 00:00:02, output 00:00:00, output hang neverLast clearing of "show interface" counters neverInput queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0Queueing strategy:fifoOutput queue:0/40 (size/max)5 minute input rate 13000 bits/sec, 6 packets/sec5 minute output rate 8000 bits/sec, 9 packets/sec419433 packets input, 108329352 bytes, 0 no bufferReceived 11792 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 input packets with dribble condition detected650568 packets output, 73969720 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outSatellite Backup for a Terrestrial Link—Standby Mode Example
In the following example, the satellite interface is in standby mode because the primary terrestrial link is up:
Router# show interfaces satellite 1/0Satellite1/0 is standby mode, line protocol is downHardware is I82559FE, address is 00e0.f7ff.f310 (bia 00e0.f7ff.f310)Internet address is 10.0.0.1/24MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive not setARP type:ARPA, ARP Timeout 04:00:00Last input 00:00:00, output 00:00:03, output hang neverLast clearing of "show interface" counters 00:00:04Input queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0Queueing strategy:fifoOutput queue:0/40 (size/max)30 second input rate 13000 bits/sec, 6 packets/sec30 second output rate 0 bits/sec, 0 packets/sec30 packets input, 7474 bytes, 0 no bufferReceived 1 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 input packets with dribble condition detected1 packets output, 82 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outHot Standby Router Protocol (HSRP)—Standby Mode Example
In the following example, homogeneous HSRP is configured on two routers, each of which contains an NM-1VSAT-GILAT network module that connects to the same dish antenna (ODU). The following output from the standby router shows that the line protocol is "up (standby)," even though the satellite link on the standby router is actually down. To view the actual line protocol status, use the show controllers satellite command or the service-module satellite slot/0 status command.
Router# show interfaces satellite 2/0Satellite2/0 is up, line protocol is up (standby)Hardware is I82559FE, address is 0008.e35f.7370 (bia 0008.e35f.7370)Internet address is 10.22.1.2/24MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive not setARP type:ARPA, ARP Timeout 04:00:00Last input 00:00:02, output 00:00:00, output hang neverLast clearing of "show interface" counters neverInput queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0Queueing strategy:fifoOutput queue:0/40 (size/max)5 minute input rate 13000 bits/sec, 6 packets/sec5 minute output rate 8000 bits/sec, 9 packets/sec419433 packets input, 108329352 bytes, 0 no bufferReceived 11792 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 input packets with dribble condition detected650568 packets output, 73969720 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outTable 7 describes the significant fields shown in the display.
Table 7 show interfaces satellite Field Descriptions
Satellite2/0 is...
•
•
•
State of the interface hardware:
•
•
•
line protocol is
State of the backbone link to the hub: up or down. See the following exceptions:
•
•
Hardware is
Hardware type (for example, Fast Ethernet) and address.
Internet address
Internet address followed by subnet mask.
MTU
Maximum transmission unit of the interface.
BW
Bandwidth of the interface, in kilobits per second.
DLY
Delay of the interface, in microseconds.
reliability
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
txload and rxload
Transmitted and received load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
Encapsulation
Encapsulation method assigned to the interface.
loopback
Indicates whether loopback is set or not.
keepalive
Indicates whether keepalives are set or not.
ARP type
Type of Address Resolution Protocol assigned.
Last input
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
output
Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.
output hang
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
Last clearing
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231 ms (and less than 232 ms) ago.
Input queue
Input queue information:
•
•
•
•
Total output drops
Total number of output packets dropped.
Queueing strategy
First-in, first-out queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).
Output queue
Number of packets in the output queue and the maximum size of the queue,
5 minute input rate
5 minute output rate
Average number of bits and packets transmitted per second in the last 5 minutes.
The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.
packets input
Total number of error-free packets received by the system.
bytes
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.
no buffer
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
broadcasts
Total number of broadcast or multicast packets received by the interface.
runts
Number of packets that are discarded because they are smaller than the minimum packet size of the media.
giants
Number of packets that are discarded because they exceed the maximum packet size of the media.
throttles
Number of times that the interface requested another interface within the router to slow down.
input errors
Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.
CRC
Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.
frame
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device.
overrun
Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
ignored
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different from the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can increase the ignored count.
input packets with dribble condition detected
Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame.
packets output
Total number of messages transmitted by the system.
bytes
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
underruns
Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.
output errors
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
collisions
Number of messages retransmitted because of an Ethernet collision. A packet that collides is counted only once in output packets.
interface resets
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
babbles1
Indicates that the transmit jabber timer expired.
late collision1
Number of late collisions. Late collision happens when a collision occurs after the preamble has been transmitted. The most common cause of late collisions is that your Ethernet cable segments are too long for the speed at which you are transmitting.
deferred1
Deferred indicates that the chip had to defer transmission while ready to transmit a frame, because the carrier was asserted.
lost carrier1
Number of times the carrier was lost during transmission.
no carrier1
Number of times the carrier was not present during the transmission.
output buffer failures
Number of failed buffers.
output buffers swapped out
Number of buffers swapped out.
1 This field applies to the router internal interface that connects to the installed Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT). This field typically does not apply to the external satellite interface.
Related Commands
test satellite satellite mfg link
To force the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT) to show that the backbone link to the hub is up, even when the link is actually down, use the test satellite satellite mfg link command in privileged EXEC mode.
test satellite satellite slot/unit mfg link {force | normal}
Syntax Description
Defaults
The actual status (UP or DOWN) of the satellite link is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the test satellite satellite mfg link command only when instructed by your satellite service provider or a technical support representative.
Examples
The following example shows how to force the NM-1VSAT-GILAT network module to show that the backbone link to the hub is up, even if the link is actually down:
Router# test satellite satellite 1/0 mfg link forceThe following example shows how to allow the NM-1VSAT-GILAT network module to show the actual status (UP or DOWN) of the satellite link:
Router# test satellite satellite 1/0 mfg link normalupgrade satellite satellite
To upgrade the firmware of an NM-1VSAT-GILAT network module through TFTP, use the upgrade satellite satellite command in privileged EXEC mode.
upgrade satellite satellite slot/unit <tftp server address> <firmware filename>
Syntax Description
Command Default
Firmware will not be upgraded through TFTP.
Command Modes
Privileged EXEC
Command History
12.4(11)XJ2
This command was introduced.
12.4(15)T
This command was integrated into Cisco IOS Release 12.4(15)T.
Usage Guidelines
The upgrade satellite satellite command is used to provide a firmware upgrade of VSATs locally at remote sites through TFTP. This method reduces dependency on a central hub, and allows for ease of update when connected to a service provider who uses third-party hubs.
When the TFTP server is configured on the router, the VSAT firmware is copied to the router flash memory. The TFTP server configuration would be as follows:
tftp-server flash:< <firmware filename>This configuration would be within the overall router configuration.
When this configuration is done, the upgrade is accomplished by pointing the VSAT to the router IP address in the upgrade satellite satellite command. The upgrade process will take several minutes.
Examples
The following example shows the response of the NM-1VSAT-GILAT network module to a firmware upgrade command.
Router# upgrade satellite satellite 1/0 9.1.0.1 VSAT_99.06.01.26_Bin.binDownload of new firmware will proceed after a reboot ofthe satellite network module. This could take up to two minutes.Please wait...*Mar 4 03:18:15.006: %LINEPROTO-5-UPDOWN: Line protocol on Interface Satellite1/0, changed state to upThe upgrade process will complete in several minutes.It will take place in the background.Please monitor the console for errors.*Mar 4 03:21:16.006: %LINEPROTO-5-UPDOWN: Line protocol on Interface Satellite1/0, changed state to down*Mar 4 03:27:20.842: %LINEPROTO-5-UPDOWN: Line protocol on Interface Satellite1/0, changed state to upRelated Commands
service-module satellite status
Verifies the image version of the downloaded firmware.
Feature Information for the Cisco IP VSAT Satellite WAN Network Module
Table 8 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 8 Feature Information for Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-Gilat)
Cisco IP VSAT Satellite WAN Network Module (NM-1VSAT-Gilat)
12.3(14)T
12.4(15)T
Provides Cisco modular access routers with satellite WAN connectivity in Gilat© SkyEdge© or compatible satellite communications networks.
Security and QoS Feature Enhancements for the Cisco IP VSAT Satellite WAN Network Module
12.4(11)XJ2
12.4(15)T
Security and QoS feature enhancements have been introduced to provide user-configurable VSAT passwords, centralized IP address management, support for GA mode, support for integrated TCP acceleration and encryption (ITAE), and local firmware upgrade for the Cisco IP VSAT Satellite WAN network module.
The following section provides information about user-configurable VSAT passwords:
•
The following section provides information about centralized IP address management:
•
The following section provides information about support for GA mode:
•
The following section provides information about support for ITAE:
•
The following section provides information about local firmware upgrade:
The following commands were introduced by these enhancements: password (satellite initial configuration), service-module itae, and upgrade satellite satellite.
Glossary
access list—A list kept by routers to control access to or from the router for a number of services (for example, to prevent packets with a certain IP address from leaving a particular interface on the router). Also called access control list (ACL).
BRI—Basic Rate Interface. ISDN interface composed of two B channels and one D channel for circuit-switched communication of voice, video, and data.
CDP— Cisco Discovery Protocol. Media- and protocol-independent device-discovery protocol that runs on all equipment manufactured by Cisco, including routers, access servers, bridges, and switches. Using CDP, a device can advertise its existence to other devices and receive information about other devices on the same LAN or on the remote side of a WAN. Runs on all media that support SNAP, including LANs, Frame Relay, and ATM media.
DDR—dial-on-demand routing. Technique whereby a router can automatically initiate and close a circuit-switched session as transmitting stations demand. The router spoofs keepalives so that end stations treat the session as active. DDR permits routing over ISDN or telephone lines using an external ISDN terminal adapter or modem.
DVB—Digital Video Broadcasting. Consortium of around 300 companies in the fields of broadcasting, manufacturing, network operation, and regulatory matters, working to establish common international standards for the move from analog to digital broadcasting. The DVB Project Office is based in Geneva, Switzerland. There are many standards within the DVB family, including subspecifications for satellite (DVB-S), cable (DVB-C), and terrestrial (DVB-T) transmission and reception.
feed horn—A device mounted at the focal point of a dish antenna that captures the signals reflected from the dish surface and channels them into an amplifier. The feed horn also transmits energy to the dish antenna reflector, which then transfers the energy to a satellite.
FTDMA—Frequency and Time Division Multiple Access. Transmission technology that divides an allocated radio-frequency (RF) band into multiple RF channels and then further divides each RF channel into multiple time slots. These divisions enable the RF band to support multiple, simultaneous users by allocating unique time slots to each user.
HSRP—Hot Standby Router Protocol. Provides high network availability and transparent network topology changes. HSRP creates a hot standby router group with a lead router that services all packets sent to the hot standby address. The lead router is monitored by other routers in the group, and if it fails, one of these standby routers inherits the lead position and the hot standby group address.
HTTP acceleration—Sometimes called Internet page acceleration (IPA). Feature that improves the performance of web browsing over a satellite link. In a typical HTTP exchange, the web browser requests a web page, and the web server responds with the HTML text of the requested page. The HTML text also contains requests for objects (such as images, embedded media, or scripts), each of which requires a separate HTTP request from the web browser and an HTTP response from the web server. The resulting traffic from HTTP requests and responses can cause delays in satellite communications networks. With HTTP acceleration, most of the HTTP requests are handled locally by software at the central hub and VSAT IDUs. For example, the central hub intercepts the web server's initial response, which is the HTML text of the requested page. The hub immediately initiates HTTP requests for all the page objects using a high-speed, low-latency terrestrial link between the hub and the Internet. As the objects are received by the hub, they are immediately forwarded over the satellite link to the web browser. This results in the web browser receiving the HTML text and the pre-fetched page objects in rapid, uninterrupted succession. When the web browser sends requests for the objects in the HTML text, the VSAT IDU terminates the requests locally without sending them over the satellite link.
hub—Central hub for a satellite communications network; sometimes referred to as the "master earth station" but most often simply called the "hub." The hub contains many components, including a large dish antenna (15 to 36 feet [4.5 to 11 m] in diameter), provisioning stations, and the satellite network management system (NMS), from which a network operator can monitor and control all components of the satellite network. The hub also contains baseband equipment that handles satellite access, routing between the hub and remote earth stations, dial backup, quality of service (QoS), TCP acceleration, and HTTP acceleration. Depending on the satellite network usage, the hub may also contain web caches, MPEG transport coder/decoders, application server farms, and audio/video broadcast programming devices.
IDU—indoor unit. Part of the earthbound VSAT in a satellite communications network, the IDU generally serves to connect the local network to the hub through the satellite link.
IF—intermediate frequency. A frequency to which a carrier frequency is shifted as an intermediate step in transmission or reception. The IF is typically lower than the RF in frequency, which facilitates further amplification and processing.
inbound—Direction of satellite network traffic from the VSAT to the hub.
IRD—Integrated Receiver Decoder. A satellite receiver with a built-in decoder for unscrambling subscription channels.
ISDN—Integrated Services Digital Network. Communication protocol offered by telephone companies that permits telephone networks to carry data, voice, and other source traffic.
ISP—Internet service provider. Company that provides Internet access to other companies and individuals.
L-band—The 1- to 2-GHz frequency range of the electromagnetic spectrum that is used for satellite transmission.
LNB—low noise block converter. Mounted at the focal point of a dish antenna, this small device amplifies and converts high-frequency satellite signals into lower-frequency signals. Satellite service providers have satellites in multiple orbital positions, and a separate LNB is needed to access each satellite position.
MII—media-independent interface. Standard specification for the interface between network controller chips and their associated media interface chips. The MII automatically senses 10- and 100-Mbps Ethernet speeds.
MPEG—Moving Picture Experts Group, a joint committee of ISO and the International Electrotechnical Commission. MPEG is more commonly known as the series of hardware and software standards involving the reduction of storage requirements (compression schemes) for full-motion video.
multicast—A routing technique that allows IP traffic to be sent from one source or multiple sources and delivered to multiple destinations. Instead of sending individual packets to each destination, a single packet is sent to a group of destinations known as a multicast group, which is identified by a single IP destination group address. Multicast addressing supports the transmission of a single IP datagram to multiple hosts.
NMS—network management system. System responsible for managing at least part of a network. An NMS is generally a reasonably powerful and well-equipped computer, such as an engineering workstation. The NMS communicates with agents to help keep track of network statistics and resources.
NTSC—National Television Standards Committee. A United States TV technical standard, named after the organization that created the standard in 1941. Specifies a 6 MHz-wide modulated signal.
ODU—outdoor unit. Mounted outdoors in direct line of sight to the satellite, the ODU is part of the earthbound VSAT in a satellite communications network. The ODU includes a small dish antenna (2 to 6 feet [0.5 to 2 m] in diameter) and its parts, such as the low noise block converter (LNB), solid state block converter and power amplifier (SSPA), orthomode transducer (OMT), and the feed horn. The ODU is connected to the indoor unit (IDU) by a coaxial RF cable similar to a cable TV connection.
orthomode transducer—Antenna feed component that separates transmitted signals from received signals, which have different polarization and frequency.
outbound—Direction of satellite network traffic from the hub to the VSAT.
PIM— Protocol Independent Multicast. Multicast routing architecture that allows the addition of IP multicast routing on existing IP networks. PIM is unicast routing protocol independent and can be operated in two modes: dense and sparse. See also PIM dense mode and PIM sparse mode.
PIM dense mode—One of the two PIM operational modes. PIM dense mode is data-driven and resembles typical multicast routing protocols. Packets are forwarded on all outgoing interfaces until pruning and truncation occur. In dense mode, receivers are densely populated, and it is assumed that the downstream networks want to receive and will probably use the datagrams that are forwarded to them. The cost of using dense mode is its default flooding behavior. Sometimes called dense mode PIM or PIM DM. Contrast with PIM sparse mode. See also PIM.
PIM sparse mode—One of the two PIM operational modes. PIM sparse mode tries to constrain data distribution so that a minimal number of routers in the network receive it. Packets are sent only if they are explicitly requested at the rendezvous point (RP). In sparse mode, receivers are widely distributed, and the assumption is that downstream networks will not necessarily use the datagrams that are sent to them. The cost of using sparse mode is its reliance on the periodic refreshing of explicit join messages and its need for RPs. Sometimes called sparse mode PIM or PIM SM. Contrast with PIM dense mode. See also PIM and rendezvous point.
POTS—Plain old telephone service. Basic telephone service supplying standard single-line telephones, telephone lines, and access to the public switched telephone network.
QoS—quality of service. QoS refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies.
rendezvous point—Router specified in PIM sparse mode implementations to track membership in multicast groups and to forward messages to known multicast group addresses. See also PIM sparse mode.
RF—radio frequency. Generic term referring to frequencies that correspond to radio transmissions, that is, wireless communications with frequencies below 300 GHz. Cable TV and broadband networks use RF technology. In a satellite communications network, the term RF is often used to distinguish signals that are transmitted to and from the satellite from signals that are processed at other frequencies within the same communication system, such as intermediate frequencies (IFs).
RIP—Routing Information Protocol. Interior Gateway Protocol (IGP) supplied with UNIX BSD systems. The most common IGP in the Internet. RIP uses hop count as a routing metric.
SIP—Session Initiation Protocol. An application-layer protocol originally developed by the Multiparty Multimedia Session Control (MMUSIC) working group of the Internet Engineering Task Force (IETF). Their goal was to equip platforms to signal the setup of voice and multimedia calls over IP networks. SIP features are compliant with IETF RFC 2543, published in March 1999.
spoofing—A method of fooling network end stations into believing that keepalive signals have come from and return to the host. Spoofing maintains network connectivity, such as TCP connections, during periods of inactivity that would otherwise result in network connections being torn down and reestablished unnecessarily.
SSPA—Solid state block converter and power amplifier. Outdoor unit (ODU) device which amplifies the signal from the indoor unit (IDU) and which converts the low-frequency signal to a high-frequency signal for transmission across the satellite link.
TCP— Transmission Control Protocol. Connection-oriented transport layer protocol that provides reliable full-duplex data transmission. TCP is part of the TCP/IP protocol stack.
TCP acceleration—Feature that improves the utilization efficiency of a satellite link by minimizing the number of TCP acknowledgement packets that are sent over the satellite link. In a typical terrestrial network, TCP provides reliable network connectivity by requiring a receiving host to send an acknowledgement for each packet (or set of packets) received before the transmitting host sends the next packet (or set of packets). In a satellite communications network, the satellite backbone protocol provides reliable delivery of data, so the TCP acknowledgements are unnecessary. With TCP acceleration, most of the TCP acknowledgements are handled locally by software at the central hub and VSAT IDUs, so that only the application data and the data required to establish TCP sessions are transmitted over the satellite link. For example, the central hub sends acknowledgements to the transmitting host while forwarding all content packets (as they are received) over the satellite link to the receiving host. At the remote side of the satellite link, the VSAT IDU locally terminates the TCP acknowledgements sent by the receiving host. Only in the case of delivery problems are any TCP acknowledgement packets sent over the satellite link.
TDMA—Time Division Multiple Access. Transmission technology that enables a single radio-frequency (RF) channel to support multiple, simultaneous users by dividing a radio frequency into time slots and then allocating unique time slots to each user.
UDLR—Unidirectional Link Routing Protocol. A routing protocol that provides a way to forward multicast packets over a physical unidirectional interface (such as a satellite link of high bandwidth) to stub networks that have a back channel.
VoIP—Voice over IP. The capability to carry normal telephony-style voice over an IP-based internetwork with POTS-like functionality, reliability, and voice quality. VoIP enables a router to carry voice traffic (for example, telephone calls and faxes) over an IP network. In VoIP, the digital signal processor (DSP) segments the voice signal into frames, which then are coupled in groups of two and stored in voice packets. These voice packets are transported using IP in compliance with ITU-T specification H.323.
VSAT—very small aperture terminal. An earthbound station of a satellite communications network. A VSAT consists of two parts, an outdoor unit (ODU) and an indoor unit (IDU). The ODU is a "very small" transceiver dish antenna (2 to 6 feet [0.5 to 2 m] in diameter) that is placed outdoors in direct line of sight to the satellite. The IDU generally serves to connect the local network to the dish antenna and satellite network. The ODU receives and sends signals to a satellite. The satellite sends and receives signals from an earthbound central hub, which controls the entire operation of the satellite network.
Note
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
