Enhancements have been made for cellular and GPS features as follows:

Trigger points and debug code can be enabled via controller cellular CLIs for generating and trap the debug data automatically without manual intervention. The following CLI options are available:

(config-controller)#lte modem serviceability ?
  gps               GPS debugging
  interface-resets  Interface resets/Bearer deletion
  modem-crash       Modem-crash debugging
  modem-resets      IOS initiated unknown modem-resets

The debug data includes the following:

• Context Based debug logs (tracebacks, and GPS locations).

• Well formatted debug messages.

• Vendor specific debug data at a broader range.

The debug logs are located in the following location of flash:

router#dir flash:servelogs
Directory of bootflash:/servelogs/

259340  -rw-              122   Sep 7 2021 17:40:44 +00:00  gpslog-slot5-20210907-174044
259339  -rw-             1734   Sep 7 2021 12:14:07 +00:00  celllog-slot5-20210905-164628

GPS and cellular log files are created separately with file names using the timestamp at the time of the creation. These files are created as follows:

• If the existing file has reached 10Mb, a new file will be created.

• A new file will be created if the feature (GPS, or cellular) is completely disabled, and then re-enabled.

The GNMI Broker (GNMIB) has been extended to support the gRPC Network Operations Interface (gNOI) reset.proto service. This service provides functionality for restoring the device to its factory defaults via gRPC.

When the service is executed, it behaves similarly to the ‘factory-reset all’ command, and subsequently triggering a reload. Additionally, the service will maintain the current booted image. The additional steps below will be taken to comply with the reset.proto service:

• Set the rommon BOOT variable to the current booted image and maintain it through reload following factory-reset

• Enable autoboot to bring the device up on the current booted image following factory-reset.

gNOI is the gRPC Network Operations Interface. gNOI defines a set of gRPC-based microservices for executing operational commands and procedure on network devices, such as OS Install, Activate, and Verification.

Through gNOI os.proto will be possible to perform operating system related tasks such as OS activation, install, detailed overview, internal OS commands, and finally to output a summary of OS operations.

Furthermore, gNOI os.proto can also be used to display the gnmib detailed state, check the gnmib operational statistics, and also to output modifiers.

This enhancement allows the user to input the maximum number of retries available to the write socket. The range of the number of retries goes from 1 to 1000. The default number of retries is 10. To accommodate this feature, a new CLI has been created, raw-socket tcp max-retries <1-1000>. <1-1000> is the maximum number of retries.

This enhancement provides compatibility with TNB’s WG RTUs, including the following:

• TNB RTUs require Reset-Link message to be sent out along with Link-Status message to ensure correct initialization of the serial. The feature can be selectively turned on using the new configuration CLI scada-gw protocol force reset-link.

• When clock passthru is enabled and if the router hasn’t received the timestamp from the DNP3-IP master, the router’s hardware time will be sent downstream to RTU. Upon receiving a new timestamp from DNP3-IP master, the router will start sending the new timestamp sourced from DNP3-IP master to RTU.

• The number of bufferable DNP3 events in memory will be increased from 600 to 10000.

• The scada-gw protocol interlock command will be supported for DNP3. Previously, the support only existed for T101/T104. With this new enhancement, the router will disconnect Serial link if the DNP3-IP master is down or unreachable. Similarly, when the Serial link to RTU is down, the TCP connection to DNP3-IP master will be untethered.

• Custom “requests” will be automatically ordered based on priority so that the user can specify them in any order that they would like to.

Cisco IOS-XE Release 17.7.1 adds support for LTE modules on the ESR6300 platform in slot 3. The related interface is Cellular 0/3/0.

ESR6300 will only support the following LTE modules:

• P-LTE-MNA (WP7610 modem)

• P-LTEA-LA (EM7430 modem)

• P-LTEA-EA (EM7455 modem)

• P-LTEAP18-GL (LM960 modem)

The cellular interface/module configuration will follow the same as on any other Polaris IOS-XE based platform and LTE modem.

Release 17.7.1 will add support for the following SFPs:

GLC-T-RGD

CWDM-SFP-1470=

CWDM-SFP-1610=

CWDM-SFP-1530=

DWDM-SFP-3033=

DWDM-SFP-3112=

GLC-BX-D-I=

GLC-BX-U-I=

GLC-TE

A Small Form Factor (SFF) transceiver is an optical transceiver that is soldered onto the PCB. It tends to be smaller in size than traditional SFPs.

There was a need for the ESR6300 to support SFFs in order to meet high vibration and shock requirements that can't be met with traditional SFPs. Therefore, support was added in 17.6.1 for the Finisar FTE8501K1LTN.

Since, this is not a Cisco transceiver, the end-user will need to use the service unsupported-transceiver CLI in order to get the router to accept and initialize the SFF.

Functionally, an SFF operates in the same way as an SFP.

This feature functions the same as it does on the IR1101 running 17.5.1

See the section on VXLAN in the IR1101 Software Configuration Guide.

RFC 4884 redefines selected ICMP error messages to support multi-part operation.

A multi-part ICMP message carries all of the information that ICMP messages carried previously, as well as additional information that applications may require.

RFC 4884 feature introduces an 8-bit length attribute to the following ICMPv6 messages with extensions.

• Destination Unreachable (type = 1)

• Time Exceeded (type = 3)

As part of RFC 4884 feature, for applications like MPLS/trace route which add extensions to type 1 and type 3 ICMPv6 error messages, original datagram length will be added in ICMPv6 header.

Also, infra is added as part of RFC 4884 support. If any new application is adding extensions it has to call defined registries to be compliant with RFC 4884.

Backward compatibility is also taken care of as part of this feature.

This feature is enabled by default and a CLI [no] ipv6 icmp od-length enable is provided which is enabled by default.

The Netboot (TFTP boot) feature is now supported on the ESR6300. The ESR6300 has two Combo ports, Copper and Fiber ports (SFP) ports that support TFTP boot.

The Netboot (TFTP boot) feature allows the user to recover their router in the case that there is no image in the bootflash or USB.

The following configuration needs to be in place in ROMMON:

• WAN port Gigabit-Ethernet 0/0/0 or 0/0/1 should be connected to a TFTP network

• Path to image should be in a TFTP directory

• set IP_ADDRESS=<IP address of router>

• set IP_SUBNET_MASK=<mask>

• set DEFAULT_GATEWAY=<IP address of gateway>

• boot tftp://<server IP address>/<path to image>

There is one alarm port available on the ESR6300. The IOS name for the alarm port is Alarm Contact 0.

The following configuration commands are available in IOS:

• alarm contact 0 enable

• alarm contact 0 description

• alarm contact 0 severity

• alarm contact 0 trigger

The configuration commands also have their equivalent no prefaces.

Alarm Trigger Command

The trigger command has two options as shown below:

closed	Assert alarm when contact is closed. Closed means that no current flows through the contact (normally open contact). The alarm is generated when current does flow.
open	Assert alarm when contact is open. Open means that the normal condition has current flowing through the contact (normally closed contact). The alarm is generated when the current stops flowing.

Note	See the Alarm Port Configuration Examples for command examples.

Alarm LEDs

The alarm LED behavior is described in the following table:

Severity	LED Status
Critical	Flashing Red
Major	Flashing Red
Minor	Red

Note	The LED behavior depends on both the trigger configuration as well as the severity configuration. The LED behavior does not differentiate between the Critical and Major severity.

This release enables PnP to work the same as on the IR1101. See the IR1101 Software Configuration Guide.

Security-Enhanced Linux is a set of patches to the Linux kernel and some utilities to incorporate a strong, flexible mandatory access control (MAC) architecture into the major subsystems of the kernel. SELinux provides an enhanced mechanism to enforce the separation of information based on confidentiality and integrity requirements, which allows threats of tampering and bypassing of application security mechanisms to be addressed and enables the confinement of damage that can be caused by malicious or flawed applications.

SELinux enforces mandatory access control policies that confine user programs and system servers to the minimum amount of privilege they require to do their jobs. This reduces or eliminates the ability of these programs and daemons to cause harm when compromised (for example, via buffer overflows or mis-configurations). This confinement mechanism operates independently of the traditional Linux access control mechanisms.

The are no additional requirements or configuration steps required to enable or operate the SELinux feature. The solution is enabled/operational by default as part of the base IOS-XE software on supported platforms.

The following are enhanced show commands that have been defined for viewing SELinux related audit logs.

show platform software audit all

show platform software audit summary

show platform software audit switch <<1-8> | active | standby> <FRU identifier from a drop-down list>

The ESR6300 supports SDWAN with release 17.3.1 or later. This release brings the ESR6300 into feature parity with the IR1101. The ESR6300 will require controller version 20.2 or later.

All of the available SDWAN documentation can be found here:

https://www.cisco.com/c/en/us/support/routers/sd-wan/series.html

Additional protocol capabilities have been added to the ESR6300 to bring it into feature compatibility with the IR1101. These include:

• SCADA Gateway functionality (IEC10x and DNP3)

• Raw Socket (TCP and UDP)

• Line Relay

• Reverse Telnet

All of the configuration and show commands will be the same as are available on the IR1101 platform.

https://www.cisco.com/c/en/us/td/docs/routers/access/1101/software/configuration/guide/b_IR1101config.html

Support has been added in order to boot the device from configuration files located on the pluggable USB. Customized startup configuration files can be booted from IOS or from ROMMON.