The Guest OS Ethernet port (eth0) connects to a GigabitEthernet interface on Cisco IOS. The IR829 uses GigabitEthernet 5, and the IR809 uses GigabitEthernet 2.

To configure the GigabitEthernet interface with the default gateway address of the DHCP pool, enter the following commands:

Note	IPv6 must always be enabled on the GigabitEthernet interface.

Note	The IR809 uses Gigabit Ethernet 2, and the IR829 uses Gigabit Ethernet 5.

The Guest OS starts after installation.

During start up, Guest OS sends a DHCP request and is assigned an IP address from the local DHCP pool and an IPv6 address through IPv6 stateless auto-configuration. Guest OS is then configured with a hostname and sync time from IOS.

Note	It can take a few minutes for the Guest OS to start.

Log files related to the Guest OS file system are stored on the /var/log directory of IOx. This is a volatile location because they may be lost when the IOS or IOx receives a reload command. for this reason, the caf.log, daemon.log, tpmc.log and syslog files from /var/log are now moved to a persistent storage location under /software/downloads (i.e. /dev/sdb filesystem) and the data in it will be restored upon multiple reloads. On reinstallation, the files under /software/downloads will be removed.

The command is persistent across IOS reloads unless a new GOS image is loaded or a bundle install to the new GOS image.

Additional CLIs are available for persistent logging:

• To enable persistent logging from IOS use following command:

  IR800# iox host exec enable_persistent_logging <GOS>

• To enable persistent logging from IOS use following command:

  IR800# iox host exec disable_persistent_logging <GOS>

• •To enable persistent logging from Guest-OS use following command:

  IR800-GOS:/etc/scripts# ./enable_persistent_logging

• •To disable persistent logging from Guest-OS use following command:

  IR800-GOS:/etc/scripts# ./disable_persistent_logging

The Guest OS running on the IR800 series have had a higher likelihood for file system corruptions after an abrupt power failure. Upon Guest OS start or restart, a mandatory FSCK is performed on the rootfs and the datafs in order to attempt file system recovery.

This feature can be enabled or disabled using the config command iox recovery-enable <timeout>, where timeout specifies the TPMS timer timeout value in minutes. If unspecified, the default value is 5 and maximum is 15. If no registration request is received from TPMC before the timer expires, the Guest OS will be reinstalled. By default, the feature is disabled so that the customers who do not use Guest OS will not run into a situation where the Guest OS is reinstalled because networking is not configured correctly for Guest OS. The command is persistent across IOS reloads.

IOXVM Graceful Shutdown

On the IR800 router, the Guest OS will now perform a graceful shutdown before a reload of the device. Previously, the GOS would not go through the shutdown command, which sometimes would result in unexpected behavior.

Logrotate of IR8x9 Guest-OS logs

The logrotate feature has been uniformly implemented across all logs in the Guest-OS /var/log path. If persistent-logging is enabled, the specific logs will be saved on /software/downloads and logrotate is implemented on those as well. By default, log-rotate takes effect every day at 7:30am.

This feature allows for enabling the AAA login to IOx applications. There are different options:

• If your device shows no aaa new-model in the configuration, it will use local authentication.

• If your device shows aaa new-model in the configuration, there are two different methods of authentication.

  • If your device shows no iox aaa authentication in the configuration, it will use the default authentication list, for example: "aaa authentication login default..."

  • If your device shows iox aaa authentication WORD in the configuration, it will use the newly created list/group you specify.

  • To create a login authentication group/list, use aaa authentication login WORD. Then specify the name to use for IOX authentication using iox aaa authentication WORD For example

There is a condition in authentication that may case some confusion. The following provides more details:

Scenario: When a user enables a separate AAA Radius server to authenticate and authorize Guest-OS, instead of using local login.

Observation: In such a scenario, when a privilege 15 user logs into the Guest-OS console port 2070 from within IOS, the first login request is for the IOS username/password . The second login prompt is for the AAA Radius credential specific to Guest-OS.

Note	Users will need to configure the aaa iox username in IOS.

IR800# show run | inc aaa
aaa new-model
aaa authentication login default local
aaa authentication login ioxList group radius local <-implies 1st preference radius, 2nd preference: local login
aaa session-id common
iox aaa authentication ioxList <-to apply the newly created list above

This enhancement to the IR800 series is to provide more flexibility to provide a customizable disk partitioning. With a smaller partition for system files, the user can put larger applications in the remaining partition.

A new CLI is introduced for this purpose:

IR829# guest-os 1 ?
disk-repartition Guest OS disk repartition
image Guest OS bootable image
restart Restart Guest OS
start Start Guest OS
stop Stop Guest OS

IR829# guest-os 1 disk-repartition ?
<30-90> Percentage Guest OS system partition takes

The user can input a number between 30 and 90 which would be rounded up to multiples of 5.

For example, typing in 30 means the system partition would take 30% of total space.

IOS communicates with VDS, which will actually perform disk repartition for GOS. After the action is completed by VDS, VDS will send a notification message back to IOS to indicate the status of operation.

After the disk repartitioning, the user will need to reinstall the GOS.

IR829# guest-os 1 disk-repartition 1
WARNING - Running this command will delete all application data in IOx. This operation cannot be undone. Continue? [no]: yes
Guest-OS disk repartitioning with option 1................................ Done!

After the repartition is successful, you should see the following syslog message:

%IR800_GOS_DISK_REP-6-SUCCESS_GOS_OPERATION: Successfully performed DISK REPARTITION operation for GOS.

After the disk is repartitioned, the GOS needs to be reinstalled by one of two methods:

IR800# bundle install flash:ir800-universalk9-bundle.SSA.156-3.M1 exclude HV-IOS
-or
IR800# guest-os install flash:ir800-ref-gos.img.1.40.gz

Finally, manually restart the GOS.

IR800# guest-os 1 start

If you have an IR809 or IR829 that was originally configured with an IOS version before 15.6(3)M1, then the GOS was partitioned in a different manner than later releases. For example:

• If the router was initially booted up (first time power up) with an image older than 15.6(3)M1b, then the GOS is partitioned the old way with: disk1 (1530 MB) and the rest is disk2 (800 MB)

• If the router was initially booted up (first time power up) with an image at 15.6(3)M1b or newer, then the GOS is initially partitioned with profile 1: disk 1 (500MB) and the rest is disk2 (1800 MB)

In either case, once the router is running 15.6(3)M1b or newer, you can use the following CLI to repartition it with different options:

IR800# guest-os 1 disk-repartition ?
1  disk1: 500MB vs disk2: 1800MB
2  disk1: 700MB vs disk2: 1600MB
3  disk1: 900MB vs disk2: 1400MB
4  disk1: 1100MB vs disk2: 1200MB
5  disk1: 1300MB vs disk2: 1000MB
6  disk1: 1500MB vs disk2: 800MB
7  disk1: 1700MB vs disk2: 600MB

(Note: Actual storage available for apps will be less than the value chosen for disk2 for all profiles.)

IR800 IOS releases don’t support an external USB storage directly accessible from IOS. However, USB as external storage is provided as an option during IOx application deployment from Local Manager or Fog Director.

P

Guest OS enhancements include:

• Cisco distribution is based on Yocto Project 1.8 Reference Distro, with basic services enabled:

  • IPv4/IPv6

  • DHCP

  • NTP

  • AAA (Radius)

  • Python 2.7

  • Basic debugging tools (tcpdump, top, etc)

  • bash

• Serial relay for Guest OS control of the Serial Interface

  • Async 0 and Async 1 respectively reserve line 1/5 and 1/6 to relay serial data to the corresponding Guest OS /dev/ttyS1 and /dev/ttyS2

Guest OS enhancements include:

Guest OS enhancements include:

• IOx Radius authentication

  This feature allows for enabling the AAA login to IOx applications

• IOx IPv6 Networking Option

  IOx interfaces on IOS now support IPv6 addressing. See the IOx documentation for further information.

  https://developer.cisco.com/docs/iox/

• Guest OS persistent logging through reload

  Log files related to the Guest OS file system are stored on the /var/log directory of IOx. This is a volatile location because they may be lost when the IOS or IOx receives a reload command. for this reason, the caf.log, daemon.log, tpmc.log and syslog files from /var/log are now moved to a persistent storage location under /software/downloads (i.e. /dev/sdb filesystem) and the data in it will be restored upon multiple reloads. On reinstallation, the files under /software/downloads will be removed.

• Guest OS file system corruption detection and recovery

  The Guest OS running on the IR800 series have had a higher likelihood for file system corruptions after an abrupt power failure. Now, upon Guest OS start or restart, a mandatory FSCK is performed on the rootfs and the datafs in order to attempt file system recovery.

• IOS APIs to Enable Native IOx Applications

  Note	The IOx Host Device Management service package needs to be installed for this feature to work.

  A new configuration command, hdm-enable, has been added in this release to enable the Host Device Management service.

  ir829-01(config)#iox ?          
    aaa              IOX AAA options
    client           Configure iox client
    hdm-enable       Enable IOX Host Device Management(HDM) service
    hypervisor       Configure hypervisor policy
    recovery-enable  Set Guest OS image recovery

  For more information on IOx, please visit:

  https://www.cisco.com/c/en/us/support/cloud-systems-management/iox/tsd-products-support-series-home.html

Use standard Linux tools (for example, ping and traceroute) to check Guest OS connectivity.