Attachment J-05 - Using BFTT Linux Gold Disk (T46E - 5.1.1A) 12MAY2022.docx

PROCEDURES FOR USING

BFTT LINUX GOLD DISK

(T46E VERSION / BUILD 5.1.1A)

Prepared for:

Naval Surface Warfare Center Dahlgren Division Dam Neck Activity 1922 Regulus Avenue Virginia Beach, VA 23461-2097

Prepared on:

CUI

Original: 24 March 2020 Change 1: 15 July 2020

CONTROLLED UNCLASSIFIED INFORMATION.

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only, Administrative or Operational Use, 3 March 2017. Other requests shall be referred to PEO IWS1IT.

RECORD OF CHANGES

The current revision of this document supersedes all previous revisions of this document.

(ECP 604)

Updated T46E Gold Disk build version and date.

TABLE OF CONTENTSChange 1

LIST OF TABLES

Table 1 - T46E Motherboard BIOS Settings 1

-2-

CUI

1. Introduction This document illustrates the procedures for using the BFTT T46E Linux Gold Disk (aka T46E Gold Disk). Mondo Rescue and Mindi Linux (http://www.mondorescue.org) is the software application that was used to create the Gold Disk.

The main section of the document illustrates the procedures for using the T46E Gold Disk. This Gold Disk creates a BOPC 1 with its network configured for site 511 (USS Forrestal [AVT 59]). No BFTT application software is installed; however, the system will be ready to accept BFTT application software. In doing so, the T46E Gold Disk will format and partition the primary hard drive, resulting in the loss of all data. Keep this in mind before using the T46E Gold Disk.

Within the context of this document, the term “BOPC module” is used to describe a Linux-based component (i.e., BOPC, Gateway, or NAVSIM) of the AN/USQ-T46E(V) BFTT System.

NOTE: It is strongly recommended that a hard drive of 500GB or larger be used, but under no circumstances should the procedures in this document be used with a hard drive smaller than 200GB.

2. Preliminary Installation Procedures

2.1 BIOS Setup

NOTE: In most cases, it will not be necessary to perform this section. However, it may be necessary to verify these settings have been made.

Press <Del> during the boot-up sequence to enter the BIOS.CONTROLLED UNCLASSIFIED INFORMATION.

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only, Administrative or Operational Use, 3 March 2017. Other requests shall be referred to PEO IWS1IT.

Verify the following values (see Table 1) are set in the BIOS, making any changes as necessary. Use the arrow keys to navigate, the plus <+> and minus <-> keys to toggle the values, and <Esc> to return to the main (or previous) menu.

Change all Legacy Boot Order entries that have USB in their title to [Disabled].

Table 1 - T46E Motherboard BIOS Settings

NOTE: Disabling the USB boot capability is required for compliance with Potential Discrepancy Item (PDI) USB02.011.00 of the “Sharing Peripherals Across the Network (SPAN) Security Technical Implementation Guide (STIG),” Version 1, Release 1, dated 28 July 2005.

At the main menu, press <F10> to save changes and exit the BIOS.

2.2 Obtaining the Remote X Server Hardware Address

Power on the remote X station, if available.

During the boot-up process, record the MAC address (i.e., Ethernet Link Level Address) for use in the post-installation procedures (Section 4).

3. Shipboard Recovery Procedures

3.1 Instructions

Power on the BOPC module.

Insert the DVD labeled “BFTT 5.1.1A Linux Gold Disk (T46E), 15 July 2020.”Change 1

NOTE: Waiting too long before inserting the DVD results in one of two conditions.

· If the drive was clean (Linux kernel was not previously installed), the error “No boot device found” will be displayed. If this occurs, press <Ctrl-Alt-Del> without removing the DVD from the drive.

· If the drive already had a Linux kernel installed, the drive will start booting eventually arriving at the login prompt. If this occurs, press Reset or cycle power without removing the DVD from the drive.

You will be presented with four options. DO NOT SELECT ANY OF THEM.

To format and restore all files automatically, type 'nuke' <enter>.

To restore some/all files interactively, type 'interactive' <enter>.

To compare the archives with your filesystem, type 'compare' <enter>.

To boot to a command-line prompt (expert mode), type 'expert' <enter>.

You may add one or more parameters as well as per the function keys below e.g. Type ‘nuke denymods = “fdomain impi_si”’ to not load these 2 modules

If restoring from a local external disk or USB key, do not connect it until the boot-up has finished.

F1-Main | Boot Parameters F2-1/2 | F3-2/2 | F4-PXE boot:

At the “boot:” prompt, press <Enter> without entering anything. This puts the program into graphics mode.

NOTE: If no activity is detected at the keyboard for 30 seconds, the program will enter graphics mode automatically.

NOTE: You may see various error messages scroll by as the Mondo application loads. This is OK. This is a known problem with the Mondo application.

After the Mondo application loads, you are presented with four options similar to the ones presented before:

How should I restore?

Automatically Interactively Compare Only!

Exit to shell Do you want to ‘nuke’ your system, restore interactively, or just compare?

Use the arrow keys to highlight “Automatically.” Press <Enter>.

The Gold Disk installation continues with the following output:

CAUTION

Be advised: I am about to ERASE your hard disk(s)! You may press Ctrl+Alt+Del to abort safely.

At this point, you are given one last chance to abort. To abort the installation, press <Ctrl-Alt-Del> before the timer runs out (APPROXIMATELY 20 SECONDS). Otherwise, the installation continues by partitioning and formatting the hard drive.

NOTE: There is a bug in the Mondo Rescue program that prevents the abort of the installation when <Ctrl-Alt-Del> is pressed before the timer runs out. To abort, press and hold the power button until the machine powers off or turn the key on the hard drive.

Partitioning devices I am now going to partition all your drives.

This should not take more than five minutes.

NOTE: The partition sizes are adjusted automatically to fit the current hard drive.

Formatting partitions I am now formatting your hard disk partitions.

This may take up to five minutes.

NOTE: Due to the size of the hard drive (500GB or more) in the BOPC modules, this action may take several minutes to complete.

Mounting devices I am now mounting all the drives.

This will not take long.

Restoring from archives Restoring data from the archives.

Please wait. This may take some time.

The data restoration process may take up to 10 minutes to complete. At this point, the disk has been partitioned and formatted and most of the system files now are installed.

Reassembling large files I am now reassembling all the large files.

Please wait. This may take some time.

The process of reassembling large files (> 64MB) may take from 2 to 5 minutes to complete, depending on the speed of the machine.

Alert You will now be able to re-generate your initrd.

This is especially useful if you changed of hardware configuration, cloned, made P2V, used multipath… Do you need to do it?

Yes No

Select “No.”

Unmounting devices Unmounting all devices that were mounted in preparation for the post-restoration reboot.

Alert Mondo has restored your system.

Please wait for the command prompt. Then remove the backup media and reboot.

Please visit our website at http://www.mondorescue.org for more information.

OK

Select “OK.”

NOTE: Do NOT type exit as advised on the screen in the following command. At the command prompt, remove the T46E Gold Disk and cycle power on the machine.

A bug report has been submitted to the MondoRescue Mailing List on this issue.

Type ‘less /var/log/mondorestore.log’ to see the output log Type ‘exit’ to reboot the PC

3.2 (CUI) Test/Verification NOTE: With some KVM models, the initial boot after installing the Gold Disk displays a blank screen with some occasional flickering. In addition, the keyboard becomes unresponsive and you are no longer able to switch channels on the KVM. If this is the case, please skip to Section 3.3 and follow the instructions there, then return here and continue.

On initial boot after installing the Gold Disk, you will see the following notice:

*** Warning -- SELinux targeted policy relabel is required.

*** Relabeling could take a very long time, depending on file *** system size and speed of hard drives.

Once the SELinux relabeling has completed (roughly 4 to 5 minutes on a T46E system), the system will automatically reboot.

If the machine is currently connected to a network configured for USS Forrestal (i.e., the network has IP address 192.5.11.0), and there is already a BOPC 1 that is up and running, disconnect the machine from the network before powering it on. Your newly configured machine currently has an IP address of 192.5.11.1, which conflicts with the original BOPC 1.

Power on the machine, if necessary.

Verify the login prompt is “bopc1 login.”

Login as root.

At the command prompt, type: ifconfig eth0 You should see something similar to the following:

eth0 Link encap:Ethernet HWaddr 00:20:CE:81:1A:9F inet addr:192.5.11.1 Bcast:192.5.11.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:168 (168.0 b) Interrupt: 20 Memory: e3100000-e3120000

Verify the C/S LAN (eth0) has IP address (inet addr) 192.5.11.1. If this is not true, see Section 5.

Logout.

3.3 Alternate Boot Procedures for Certain KVMs

If a blank screen is presented upon the initial boot after installing the Gold Disk, and the keyboard becomes unresponsive, then it may be due to an incompatibility between the KVM and the default settings present on the Gold Disk. These instructions will show how to boot the BOPC module with an alternate setting that should allow configuration to continue._

Reboot the machine. You most likely will need to use the POWER or RESET switch to do so.

During the boot sequence, you will see output similar to the following:

Press any key to enter the menu:_

Booting Red Hat Enterprise Linux Server (2.6.32-754.3.5.el6.x86_64) in 5 seconds

Press any key to stop the countdown.

You are then presented with a menu with output similar to the following:

GNU GRUB version 0.97 (630K lower / 523264 upper memory)

Red Hat Enterprise Linux Server (2.6.32-754.3.5.el6.x86_64) Red Hat Enterprise Linux Server (2.6.32-754.3.5.el6.x86_64) (modeset=0)

Use the ↑ and ↓ keys to select which entry is highlighted.

Press enter to boot the selected OS or ‘p’ to enter a password to unlock the next set of features.

Use the arrow keys to select the entry ending with (modeset=0).

Press <Enter> to boot the machine.

Return to Section 3.2 to complete verification.

4. (CUI) Post Installation Procedures

4.1 Instructions

The customize script is a configuration utility that will allow the operator to customize the BOPC module for its desired purpose. It is used to set the machine’s hostname (e.g., BOPC 1, BOPC 2, Gateway, NAVSIM, DBR, etc.) and configure the network interfaces. Moreover, the remote X server (if available) is set up if the platform is configured to be a BOPC 1.

· To customize a BOPC module as a BOPC1, skip to Section 4.1.1.

· To customize a BOPC module as a BOPC other than BOPC1, skip to Section 4.1.2.

· To customize a BOPC module as a Gateway component, skip to Section 4.1.3.

· To customize a BOPC module as a NAVSIM component, skip to Section 4.1.4.

· To customize a BOPC module as a DBR component, skip to Section 4.1.5.

4.1.1 Customizing BOPC 1

Login as root.

Change to the /root directory. At the command prompt, type: cd /root At the command prompt, type: ./customize

WARNING: This script is designed to modify network, host, and routing tables. As such, any errors may result in the system becoming unstable or non-functional. Proceed with caution.

WARNING: This PC is currently configured as a networked BOPC.

Setting up PC with a T46E configuration.

Enter the name of this system (e.g., bopc1, gateway, navsim_tl, DBR) [ default = bopc1 ] :

Enter: bopc1

Enter the site number you wish to configure for [ 0 = quit ] :

Enter the site for which this BOPC will be configured. For ship sites refer to the BFTT VDD Section 1.1 for your applicable site ID. For shore sites enter the site number based on the C/S LAN IP address as established by the shore site.

The script changes the IP addresses and routing tables to match the site it is given. For example (if BOPC 1):

site 702 --> C/S LAN IP Address 192.7.2.1 site 1510 --> C/S LAN IP Address 192.15.10.1

Enter the 12-digit LAN hardware address of the JetDirect print server as a series of 6 two-digit couples separated by colons [ default = none ] :

Just press the <Enter> key. DO NOT ENTER ANYTHING.

Enter the 12-digit LAN hardware address of the Remote X Server station as a series of 6 two-digit couples separated by colons [ default = none ] :

Enter the remote X server’s LAN hardware address (see Section 3.2). If there aren’t 12 digits in your LAN hardware address, prefix the address with zeros (0’s) as needed. If you do NOT have a remote X server station, press <Enter>.

Configure for ACTS access via ALIS ?

y - ACTS backplane is 192.168.120.x n - ACTS backplane is 192.9.203.x Choose [y/n][ default = n ] :

Choose <y> if you must interface with ACTS and ACTS is using the ALIS VLAN 120 addressing scheme for its backplane units. This also will make the necessary changes to the BOPC host and routing tables and to the firewall so that the ACTS units may download their operating system and application software from BOPC1. Choose <n> if you must interface with ACTS and ACTS is using the legacy (192.9.203.x) addressing scheme. If you do not have to interface with ACTS at all, just press <Enter>.

Shutting down NFS daemons and network interfaces.

Which NAVSSI interface to use ?

1. RTS1 - 192.168.171.x

2. RTS2 - 192.168.170.x

3. NSG#1 - 10.16.2.x Choose [1-3][ default = 1 ] :

Choose <1> if you must interface with NAVSSI and NAVSSI is using the RTS1 addressing scheme (i.e., the navssi host is 192.168.171.11). Choose <2> if you must interface with NAVSSI and NAVSSI is using the RTS2 addressing scheme (i.e., the navssi host is 192.168.170.12). Choose <3> if you must interface with NAVSSI and connect via the SSDS NSG#1 (i.e., the navssi host is 10.16.2.2). If you do not have to interface with NAVSSI at all, just press <Enter>.

Fixing security contexts on modified files.

Customization complete. Press <Enter> to reboot.

Press <Enter> to reboot the BOPC.

Reconnect any network connections, if necessary.

4.1.2 Customizing BOPCs Other Than BOPC 1

Login as root.

Change to the /root directory. At the command prompt, type: cd /root At the command prompt, type: ./customize

WARNING: This script is designed to modify network, host, and routing tables. As such, any errors may result in the system becoming unstable or non-functional. Proceed with caution.

WARNING: This PC is currently configured as a networked BOPC.

Setting up PC with a T46E configuration.

Enter the name of this system (e.g., bopc1, gateway, navsim_tl, DBR) [ default = bopc1 ] :

Enter the new name of the BOPC (e.g., bopc2, bopc3, etc.).

Enter the site number you wish to configure for [ 0 = quit ] :

Enter the site for which this BOPC will be configured. For ship sites refer to the BFTT VDD Section 1.1 for your applicable site ID. For shore sites enter the site number based on the C/S LAN IP address established by the shore site.

Shutting down NFS daemons and network interfaces._

Which NAVSSI interface to use ?

1. RTS1 - 192.168.171.x

2. RTS2 - 192.168.170.x

3. NSG#1 - 10.16.2.x Choose [1-3][ default = 1 ] :

Choose <1> if you must interface with NAVSSI and NAVSSI is using the RTS1 addressing scheme (i.e., the navssi host is 192.168.171.11). Choose <2> if you must interface with NAVSSI and NAVSSI is using the RTS2 addressing scheme (i.e., the navssi host is 192.168.170.12). Choose <3> if you must interface with NAVSSI and connect via the SSDS NSG#1 (i.e., the navssi host is 10.16.2.2). If you do not have to interface with NAVSSI at all, just press <Enter>.

Fixing security contexts on modified files.

Customization complete. Press <Enter> to reboot.

Press <Enter> to reboot the BOPC.

Reconnect any network connections, if necessary.

4.1.3 Customizing Gateway

Login as root.

Change to the /root directory. At the command prompt, type: cd /root At the command prompt, type: ./customize

WARNING: This script is designed to modify network, host, and routing tables. As such, any errors may result in the system becoming unstable or non-functional. Proceed with caution.

WARNING: This PC is currently configured as a networked BOPC.

NOTE: If the PC is currently configured as a T46E NAVSIM system, then the 2nd WARNING above will not be displayed.

Setting up PC with a T46E configuration.

Enter the name of this system (e.g., bopc1, gateway, navsim_tl, DBR) [ default = bopc1 ] :

Enter: gateway

Enter the site number you wish to configure for [ 0 = quit ] :

Enter the site for which this PC will be configured. For ship sites refer to the BFTT VDD Section 1.1 for your applicable site ID. For shore sites enter the site number based on the C/S LAN IP address as established by the shore site._

Shutting down NFS daemons and network interfaces.

Configure WAN for Shore Site Virtualization [y/n] ?

Enter yes only if you want to configure the WAN interface for shore site virtualization with NCTE. Otherwise, enter no.

Is SAST ACB13 connected to the Training LAN [y/n] ?

Enter yes only if your configuration has SQQ-89 (SAST ACB13) connected on the Training LAN. Otherwise, enter no.

Which NAVSSI interface to use ?

1. RTS1 - 192.168.171.x

2. RTS2 - 192.168.170.x

3. NSG#1 - 10.16.2.x Choose [1-3][ default = 1 ] :

Choose <1> if you must interface with NAVSSI and NAVSSI is using the RTS1 addressing scheme (i.e., the navssi host is 192.168.171.11). Choose <2> if you must interface with NAVSSI and NAVSSI is using the RTS2 addressing scheme (i.e., the navssi host is 192.168.170.12). Choose <3> if you must interface with NAVSSI and connect via the SSDS NSG#1 (i.e., the navssi host is 10.16.2.2). If you do not have to interface with NAVSSI at all, just press <Enter>.

Fixing security contexts on modified files.

Customization complete. Press <Enter> to reboot.

Press <Enter> to reboot the PC.

Reconnect any network connections, if necessary._

4.1.4 Customizing NAVSIM

Login as root.

Change to the /root directory. At the command prompt, type: cd /root At the command prompt, type: ./customize

WARNING: This script is designed to modify network, host, and routing tables. As such, any errors may result in the system becoming unstable or non-functional. Proceed with caution.

WARNING: This PC is currently configured as a networked BOPC.

NOTE: If the PC is currently configured as a T46E Gateway system, then the 2nd WARNING above will not be displayed.

Setting up PC with a T46E configuration.

Enter the name of this system (e.g., bopc1, gateway, navsim_tl, DBR) [ default = bopc1 ] :

Enter: navsim_tl NOTE: Entering navsim is also accepted; however, the system will be called navsim_tl.

Enter the site number you wish to configure for [ 0 = quit ] :

Enter the site for which this PC will be configured. For ship sites refer to the BFTT VDD Section 1.1 for your applicable site ID. For shore sites enter the site number based on the C/S LAN IP address as established by the shore site.

Shutting down NFS daemons and network interfaces.

Which NAVSSI interface to use ?

1. RTS1 - 192.168.171.x

2. RTS2 - 192.168.170.x

3. NSG#1 - 10.16.2.x Choose [1-3][ default = 1 ] :

Choose <1> if NAVSSI is using the RTS1 addressing scheme (i.e., the navssi host is 192.168.171.11). Choose <2> if NAVSSI is using the RTS2 addressing scheme (i.e., the navssi host is 192.168.170.12). Choose <3> if you must connect with NAVSSI via the SSDS NSG#1 (i.e., the navssi host is 10.16.2.2).

Fixing security contexts on modified files.

Customization complete. Press <Enter> to reboot.

Press <Enter> to reboot the PC.

Reconnect any network connections, if necessary.

4.1.5 Customizing DBR

Login as root._

Change to the /root directory. At the command prompt, type: cd /root At the command prompt, type: ./customize

WARNING: This script is designed to modify network, host, and routing tables. As such, any errors may result in the system becoming unstable or non-functional. Proceed with caution.

WARNING: This PC is currently configured as a networked BOPC.

Setting up PC with a T46E configuration.

Enter the name of this system (e.g., bopc1, gateway, navsim_tl, DBR) [ default = bopc1 ] :

Enter: DBR NOTE: Entering tsa or dbr is also accepted; however, the system will be called DBR.

Enter the site number you wish to configure for [ 0 = quit ] :

Enter the site for which this PC will be configured. For ship sites refer to the BFTT VDD Section 1.1 for your applicable site ID. For shore sites enter the site number based on the C/S LAN IP address as established by the shore site.

Shutting down NFS daemons and network interfaces.

Which NAVSSI interface to use ?

1. RTS1 - 192.168.171.x

2. RTS2 - 192.168.170.x

3. NSG#1 - 10.16.2.x Choose [1-3][ default = 1 ] :

Choose <1> if NAVSSI is using the RTS1 addressing scheme (i.e., the navssi host is 192.168.171.11). Choose <2> if NAVSSI is using the RTS2 addressing scheme (i.e., the navssi host is 192.168.170.12). Choose <3> if you must connect with NAVSSI via the SSDS NSG#1 (i.e., the navssi host is 10.16.2.2).

Fixing security contexts on modified files.

Customization complete. Press <Enter> to reboot.

Press <Enter> to reboot the PC.

Reconnect any network connections, if necessary.

4.2 Test/Verification

· To perform test/verification on a BOPC, skip to Section 4.2.1.

· To perform test/verification on the Gateway component, skip to Section 4.2.2.

· To perform test/verification on the NAVSIM component, skip to Section 4.2.3.

· To perform test/verification on the DBR component, skip to Section 4.2.4._

4.2.1 Verifying BOPC

Power on the machine.

Login as root.

At the command prompt, type: ifconfig You should see something similar to the following:

eth0 Link encap:Ethernet HWaddr 00:20:CE:81:1A:9F inet addr:192.5.11.1 Bcast:192.5.11.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:168 (168.0 b) Interrupt: 20 Memory: e3100000-e3120000 lo Link encap:Local loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:168 (168.0 b) TX bytes:168 (168.0 b)

The above address in bold should have the network address you configured via the customize utility. If this is not true, see Section 5.

Logout.

4.2.2 Verifying Gateway

Power on the machine.

Login as root.

4.2.2.1. Verifying Gateway’s Training LAN Interface

At the command prompt, type: ifconfig eth0 You should see something similar to the following:

eth0 Link encap:Ethernet HWaddr 08:00:27:81:D4:9B inet addr:192.168.30.1 Bcast:192.168.30.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:391 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:23460 (22.9 KiB) TX bytes:252 (252.0 b) Memory: fbb00000-fbbfffff

4.2.2.2. Verifying Gateway’s Client/Server LAN Interface

At the command prompt, type: ifconfig eth1 You should see something similar to the following:

eth1 Link encap:Ethernet HWaddr 08:00:27:81:D4:9C inet addr:192.5.11.8 Bcast:192.5.11.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:379 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1080 (1.0 KiB) TX bytes:15918 (15.5 KiB) Memory: fba00000-fbafffff

The above address in bold should have the network address you configured via the customize utility. If this is not true, see Section 5.

4.2.2.3. Verifying Gateway’s STOW LAN Interface

At the command prompt, type: ifconfig eth2 You should see something similar to the following:

eth2 Link encap:Ethernet HWaddr 08:00:27:81:D4:9D inet addr:164.7.200.3 Bcast:164.7.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:391 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:23460 (22.9 KiB) TX bytes:252 (252.0 b) Memory: fb900000-fb9fffff

4.2.2.4. Verifying Gateway’s WAN Interface

During the configuration of the Gateway component, you were asked whether or not to configure the WAN interface for shore site virtualization (SSV) with NCTE.

· If you chose to configure the WAN interface for shore site virtualization with NCTE, skip to Section 4.2.2.4.1.

· If you chose not to configure the WAN interface for shore site virtualization with NCTE, skip to Section 4.2.2.4.2.

4.2.2.4.1. Gateway’s WAN Interface (w/ SSV)

At the command prompt, type: ifconfig eth3 You should see something similar to the following:

eth3 Link encap:Ethernet HWaddr 08:00:27:81:D4:9E UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:391 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:23460 (22.9 KiB) TX bytes:276 (276.0 b) Interrupt:11 Base address:0xd280

At the command prompt, type: ifconfig eth3.121 You should see something similar to the following:

eth3.121 Link encap:Ethernet HWaddr 08:00:27:81:D4:9E inet addr:64.5.11.2 Bcast:64.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:276 (276.0 b)

The above address in bold should have the network address you configured via the customize utility. If this is not true, see Section 5.

Skip to Section 4.2.2.5.

4.2.2.4.2. Gateway’s WAN Interface (w/o SSV)

At the command prompt, type: ifconfig eth3 You should see something similar to the following:

eth3 Link encap:Ethernet HWaddr 08:00:27:81:D4:9E inet addr:64.5.11.2 Bcast:64.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:168 (168.0 b) Memory: fb800000-fb8fffff

The above address in bold should have the network address you configured via the customize utility. If this is not true, see Section 5.

4.2.2.5. Verifying Gateway’s Loopback Interface

At the command prompt, type: ifconfig lo You should see something similar to the following:

lo Link encap:Local loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:54397 (53.1 KiB) TX bytes:54397 (53.1 KiB)

4.2.3 Verifying NAVSIM

Power on the machine.

Login as root.

At the command prompt, type: ifconfig | more You should see something similar to the following:

eth0 Link encap:Ethernet HWaddr 00:20:CE:81:1A:9F inet addr:192.168.170.10 Bcast:192.168.170.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:168 (168.0 b) Memory: fbb00000-fbb40000 eth1 Link encap:Ethernet HWaddr 00:50:DA:10:4B:18 inet addr:192.168.30.10 Bcast:192.168.30.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:168 (168.0 b) Interrupt: 20 Memory: fbc00000-fbc20000 lo Link encap:Local loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:168 (168.0 b) TX bytes:168 (168.0 b)

The above address in bold should have the network address you configured via the customize utility. If this is not true, see Section 5.

Logout.

4.2.4 Verifying DBR

Power on the machine.

Login as root.

At the command prompt, type: ifconfig | more You should see something similar to the following:

eth0 Link encap:Ethernet HWaddr 00:50:DA:10:4B:19 inet addr:192.168.30.12 Bcast:192.168.30.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:168 (168.0 b) Base address: 0x3000 Memory: e3320000-e3340000 eth1 Link encap:Ethernet HWaddr 00:50:DA:10:4B:1A inet addr:192.168.2.4 Bcast:193.1.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:168 (168.0 b) Base address: 0x1000 Memory: e3100000-e3120000 lo Link encap:Local loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:168 (168.0 b) TX bytes:168 (168.0 b)

Logout.

5. Troubleshooting Tips

· Become familiar with the files /var/log/messages and /var/log/secure. These files contain diagnostic output from kernel processes. If a user is unable to log in, or if a network interface fails to initialize, the reason often is recorded in one of these places.

· Diagnostic output from X-Windows is maintained in the file /var/log/Xorg.0.log.

· Make sure each PMC/PCI module is seated securely in its slot.

· Watch for defective hardware. Bad or failing hardware (e.g., hard drives, PMC modules, etc.) can cause the BOPC or BOPC module to become unresponsive or “freeze.” Often, noting when the BOPC freezes may help to diagnose the problem.

· Watch for defective media. DVDs and CDs (including the Gold Disk and Gold Disk Updater) may become damaged over time. A common symptom of defective media is the presence of cyclic redundancy check (CRC) errors. CRC errors are logged to the console window or to the file /var/log/messages if X is running.

· In the event of severe filesystem corruption, or if there is a significant backward jump in time, the following error message may occur during boot:

Give the emergency (NOT LDAP) root password here. At the filesystem prompt, enter:

fsck -y and initiate the file system check and recovery. The filesystem prompt returns when recovery is complete. At this time, type:

exit and the system will reboot.

Start-up Tips

· Gateway, DBR, and NAVSIM need access to the LDAP server running on BOPC1 in order for non-root users to log in.

· Make sure that BOPC1 is up and running before starting Gateway, and that Gateway and BOPC1 are up and running before starting NAVSIM and DBR.

· Watch for defective hardware. Bad or failing network cabling can hinder access to the LDAP server.

· Verify the switch is configured properly.

· Ethernet interfaces should light up when a carrier signal is present and the hosts on either end of the network cable are powered on. Authorized ports on the network switch initially turn amber, then turn green upon authentication.

6. Procedures for Performing Final System QA The following steps are required to QA a BFTT installation and configuration to ensure correct BFTT operation at delivery site. Validate and check each item:

Pre-software installation:

date MMDDhhmmCCYY where MMDDhhmmCCYY comprises the two-digit month (MM), the two-digit day (DD), the two-digit hour (hh), the two-digit minute (mm), and the four-digit year (CCYY).

CUI

CONTROLLED UNCLASSIFIED INFORMATION.

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only, Administrative or Operational Use, 3 March 2017. Other requests shall be referred to PEO IWS1IT.

image1.png