Feature Requirements and Limitations

The following apply to this feature:

• The filesystem types supported for USB thumb drives on the IR1101 are: VFAT, EXT2 and EXT3. However, IOx only supports mounting of USB thumb drives with EXT2 and EXT3 filesystem. Cisco recommends EXT3 for the following reasons:

  • EXT3 is a journaling filesystem, which means there are not fragmentation issues.

  • Read/Writes are significantly faster with EXT3 filesystems

  • VFAT has a 4 GB maximum file-size limitation, which is a problem with container continuously writing large files.

• If the USB thumb drive is removed while a write operation by IOx apps is in progress, all the files included in the copy operation will be lost.

• If the USB thumb drive is removed while IOX and the app are using it, IOX will still be in running state. The functionality of the app using USB thumb drive as storage will be severely impacted, since it will not be able to read and/or write on the USB thumb drive.

Making the USB Thumb Drive Available to the IOx App

In order to make the USB thumb drive available to the IOx app, you need to issue a run option. See the following example:

Router(config-app-hosting-docker)#run-opts 1 "-v /mnt/usb0:/usbflash0"

This command will mount the USB thumb drive file system within the IOx application filesystem, and it will be available in the /usbflash0 folder, as showed by the following log from an IOx application:

/ # ls -al usbflash0/
total 705424
drwxrwxrwx    4 root     root          4096 Nov 10 22:42 .
drwxr-xr-x    1 root     root          4096 Nov 15 17:22 ..
-rw-r--r--    1 65534    65534    720025859 Nov 10 22:46 ir1101-universalk9.SSA.bin
drwx------    2 65534    65534        16384 Nov  8 16:32 lost+found
#

Configuration

The recommended configuration is through the Config mode:

interface GigabitEthernet 0/1/0
lte450 credential username username password password

Using the Exec mode:

hw-module subslot 0/1 lte450 set-info username username password password [encrypt]

Note	Execution of this command will create a file called bootflash:lte450.info and should not be deleted.

Guidelines and Limitations

The following are the limitations of the P-LTE-450 with SDWAN/vManage:

• No PNP support on P-LTE-450 as a primary link.

• P-LTE-450 parameter configuration is only supported with CLI templates.

• P-LTE-450 credential configuration via vManage is not supported on this release. Will be supported in the vManage 20.16 release.

Additional Documentation

Additional documentation for SDWAN/vManage is available at the following links:

• User Documentation for Cisco IOS XE Catalyst SD-WAN Release 17

• Cisco Catalyst SD-WAN

• Cisco SD-WAN Support Information

• Cisco vManage Monitor Overview

• Managing the SD-Routing Device Using Cisco SD-WAN Manager

Configuration Commands

The following commands are available:

Router(config)#acc-gyro ?
  enable     Enable
  frequency  Frequency in reading

Router(config)#acc-gyro freq ?
  four/sec  Reading 4 times per second
  one/min   Reading 1 times per minute
  one/sec   Reading 1 time per second (default value)
  ten/min   Reading 10 times per minute

Show Commands

The following command is available:

Router# show platform hardware acc-gyro sensor-data

Date                Time   G-X     G-Y     G-Z    XL-X    XL-Y   XL-Z
2022:10:26:16:58:13.855143 1137.50 -297.50 621.25 -18.056 -3.111 -966.057 
2022:10:26:16:58:14.863668 1058.75 -122.50 735.00 -17.629 -2.989 -965.996 
2022:10:26:16:58:15.869117 1207.50 -140.00 726.25 -18.361 -3.294 -965.813 
2022:10:26:16:58:16.874036 1268.75 -192.50 717.50 -18.178 -3.050 -965.874 
2022:10:26:16:58:17.884764 1163.75 -420.00 717.50 -18.056 -2.989 -965.813 
2022:10:26:16:58:18.894063 1347.50 -148.75 708.75 -18.117 -3.477 -965.935 
2022:10:26:16:58:19.900830 1137.50 -315.00 577.50 -18.239 -3.599 -965.935 
2022:10:26:16:58:20.908765 1137.50 -131.25 726.25 -17.873 -3.538 -965.813 
2022:10:26:16:58:21.916674 1137.50 -262.50 726.25 -18.361 -2.867 -965.935 
2022:10:26:16:58:22.927371 1137.50 -323.75 516.25 -17.934 -3.477 -965.569 
2022:10:26:16:58:23.934275 1120.00 -647.50 516.25 -18.361 -3.416 -965.752 
2022:10:26:16:58:24.940819 1111.25 -262.50 743.75 -18.422 -2.989 -965.386 
2022:10:26:16:58:25.947471 1190.00 -201.25 673.75 -17.995 -3.416 -966.057 
2022:10:26:16:58:26.953120 1093.75 -288.75 577.50 -17.995 -3.233 -965.874 
2022:10:26:16:58:27.961469 1137.50 -428.75 551.25 -18.117 -2.745 -965.996 
2022:10:26:16:58:28.971354 1050.00 -271.25 717.50 -18.361 -3.233 -965.508 
2022:10:26:16:58:29.981967 1172.50 78.75 840.00 -18.117 -3.538 -965.386 

Other

The existing debug hardware acc-gyro sensor-data command has been enhanced to provide additional debug messages for better serviceability. The debug messages will cover the following:

• How frequent the sensor data are pushed from the module to IOS, it must at least once per second.

• The latest sensor data received from the module.

IR1835 Limitations

The following are product specific limitations:

• UTD container requires a minimum space of 1.8 GB.

• UTD is supported in both Autonomous mode and Controller Mode, but in Autonomous mode, only IPS/IDS features are supported.

• The UTD configuration supports the Cloud-Low profile only.

• On-Box Web-Filtering Database is not supported.

• SSL proxy is not supported.

License and Supported Features

To enable UTD features the DNA Essentials license is required, in addition to Network Essentials. The license is required only in sd-router (autonomous mode).

If Cisco Secure Malware Analytics is also desired, then DNA Advantage license is required, in addition to Network Advantage.

Feature Configuration

Configuration on the IR1835 is the same as on other products. For information please refer to:

• Intrusion Prevention System

• URL Filtering

• Advanced Malware Protection

Additional Documentation

Additional documentation for SDWAN/vManage is available at the following links:

• User Documentation for Cisco IOS XE Catalyst SD-WAN Release 17

• Cisco Catalyst SD-WAN

• Cisco SD-WAN Support Information

• Cisco vManage Monitor Overview

• Managing the SD-Routing Device Using Cisco SD-WAN Manager

Enhancement to WPAN IOSd logging

The WPAN subsystem in IOSd only supports the legacy buginf-based logging controlled by debug CLIs inherited from the classic IOS version of WPAN. IOS XE has binary trace logging support (btrace), which has several advantages such as, some log levels can be on-by-default and even when enabling more detailed logging, the storage is more compact and allows logs to be available for a longer period of time. As part of this enhancement, support for btrace-based logging will be added to the WPAN and meshsec subsystems in IOSd. The feature enablement/disablement can be controlled via the standard set platform software trace CLIs.

Packet capture for WPAN

Previous versions of IOS XE did not support the monitor capture feature. This release enables part of this feature to be able to capture packets on the WPAN interface, including the IPv6 packets.

There are also enhancements to the existing mechanism of capturing all 802.15.4 packets sent and received by the WPAN module. The enhancement will be to make it possible to create 802.15.4 pcap files on the IR8140 locally, which canthen be downloaded. 802.15.4 captures will be implemented using WPAN exec commands wpan 0/X/0 ieee154 <options> rather than integrating with “monitor capture” CLIs because this type of capture is sufficiently different from the type that “monitor capture” supports.

The following CLIs are available:

Note	File captures are buffered in memory. Before copying the file, you should run the flush command as described above to make sure the file has the latest captured data in it, or use the stop command to stop the capture which will also flush it.

Feature Scenarios

The design of PTP over HSR feature considers the following scenarios:

• HSR Node Type: The switch can operate in either DANH mode or Redbox mode. However, the IR8340 switch is most likely to be deployed in Redbox mode with SAN devices connected via the interlink port. Only HSR-SAN mode is supported in IR8340 with one ring instance.

• Location of the PTP GMC / PTP Secondary Device: The PTP GMC or secondary device can be located either outside the HSR ring connected via the Redbox or it can be located within the HSR ring on a DANH device.

• PTP Mode: For PTP over HSR, the IR8340 can operate in either Power profile Boundary Clock mode or P2P Transparent Clock mode. Forward mode is not applicable in Power Profile and will not be supported. Default profile Boundary Clock mode and E2E Transparent Clock mode will also not be supported.

• PTP Message Type: The following PTP message types are considered:

  • Sync, Announce and FollowUp

  • PDelayRequest, PDelayResponse & PDelayResponseFollowup

• Source/Destination Port: The PTP packets can be received from or be sent out of the following ports:

  • HSR Port

  • b. Interlink port of Redbox

  • CPU Originated/Terminated

Feature Limitations

Only power profile will be supported.

• Boundary Clock (BC) – Power profile

• Transparent Clock (TC) – Peer-to-peer transparent (P2P) power profile

The PTP over HSR will be supported for only one PTP clock domain at any given time.

Only one HSR ring at a time is supported on the IR8340.

• Ports Gig0/1/4 and Gig0/1/5

• Ports Gig0/1/6 and Gig0/1/7

PTP over HSR shall be supported with GNSS/Telecom enabled on the system. The Redbox shall be in PRTC/Wan to LAN conversion mode with ports being in Primary state only.

The other clock domains can have non HSR interfaces configured with PTP over HSR enabled on one domain.

New Command Option

A new command ntp refclock timing-card has been added, which adds the timing card local clock as a refclock. This CLI will be present only when timing card is detected in the IR8340.

NTP polls for time from the timing card at stipulated intervals.

Configuration Examples

To configure the device to use the timing card as the reference:

router(config)#ntp master
router(config)#ntp refclock timing-card

To view the status:

router#show ntp status
Clock is synchronized, stratum 4, reference is 127.127.7.1
nominal freq is 250.0000 Hz, actual freq is 249.9997 Hz, precision is 2**10
ntp uptime is 6200 (1/100 of seconds), resolution is 4016
reference time is E8DB7E3A.DC6A8158 (15:36:50.861 IST Thu Oct 19 2023)
clock offset is 1.0000 msec, root delay is 0.00 msec
root dispersion is 3940.44 msec, peer dispersion is 3938.29 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000001064 s/s
system poll interval is 16, last update was 11 sec ago.

router#show ntp associations

address ref clock st when poll reach delay offset disp
~127.127.1.1 .LOCL. 7 14 16 7 0.000 0.000 1938.4
*~127.127.7.1 .TCLO. 3 15 16 3 0.000 1.000 3938.2
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured

T1/E1 Configuration Guidelines

• Use CLI template to enable the card type for T1/E1 followed by reboot. The following is a configuration example:

  card type t1 0 2

• After reboot, apply the controller configurations using CLI template. The following is a configuration example:

  controller T1 0/2/0
  framing esf
  linecode b8zs
  cablelength long 0db
  channel-group 0 timeslots 1
  channel-group 1 timeslots 2
  channel-group 2 timeslots 3
  interface Serial0/2/0:0
  ip address 1.1.1.1 255.255.255.0

IRM-NIM-RS232 Module

The 8-port Asynchronous/Synchronous Network Interface Module (NIM) IRM-NIM-RS232 provides asynchronous/synchronous serial connections supporting EIA-RS232 for the Cisco IR8340 Router.

The IR8340 router has two NIM slots, 0/2 and 0/3. The serial NIMs can be installed in these two slots.

Each RS-232 Serial Module has 8 serial interfaces. The interface numbers are:

• serial 0/2/0 - serial 0/2/7 — If the serial module is in slot 0/2

• serial 0/3/0 - serial 0/3/7 — If the serial module is in slot 0/3

Feature Support

The following features are supported:

• Supports DCE and DTE

• Each serial port can be configured as either Asynchronous or Synchronous mode

• A maximum speed of 256 kbps is supported for RS232 Synchronous port

• A maximum speed of 230.4 kbps is supported for Asynchronous port

Serial Port Configuration Guidelines

Guidelines for configuring serial ports:

• Use CLI template to enable the operational mode for the serial port (either sync or async)

  Note	The default is sync.

• Use CLI template to enable the supported configurations for sync and async ports

Sample configuration for serial async which could be applied using CLI template from vManage:

interface Serial0/3/0
physical-layer async
no ip address
encapsulation raw-tcp
end

Additional Documentation

Additional documentation for SDWAN/vManage is available at the following links:

• User Documentation for Cisco IOS XE Catalyst SD-WAN Release 17

• Cisco Catalyst SD-WAN

• Cisco SD-WAN Support Information

• Cisco vManage Monitor Overview

• Managing the SD-Routing Device Using Cisco SD-WAN Manager

Additional Documentation

Additional documentation for SDWAN/vManage is available at the following links:

• User Documentation for Cisco IOS XE Catalyst SD-WAN Release 17

• Cisco Catalyst SD-WAN

• Cisco SD-WAN Support Information

• Cisco vManage Monitor Overview

• Managing the SD-Routing Device Using Cisco SD-WAN Manager