ROMMON 1 has a networking capability, so you can perform a tftp copy. You may also copy a file from USB to flash or bootstrap while in ROMMON 1.

Problems that may occur during ROMMON-2 are:

• IOS bundle was installed but “write mem” was not performed.

• BOOT or BOOT_STRING_IOS variables missing

Resolution would be to boot flash:ir800-universalk9-mz.SPA.<version>

Note	USB can not be used as storage at ROMMON-2

IR829# show platform nvram
....
---------------------------------------------
LICENSE_SERIAL_NUMBER=FGL194520W0
LICENSE_PRODUCT_ID=IR829GW-LTE-GA-EK9
BOOT_HV=bootstrap:ir800-hv.srp.SPA.0.37
BOOT=flash:ir800-universalk9-mz.SPA.156-2.T,12;
EULA_ACCEPTED=TRUE
RET_2_RTS=18:47:19 PST Wed Feb 24 2016
RANDOM_NUM=1610696746
LICENSE_SUITE=
LICENSE_BOOT_LEVEL=
BSI=0
RET_2_RCALTS=
BOOT_IOS_SEQUENCE=4
BOOT_STRING_IOS=flash:ir800-universalk9-mz.SPA.156-2.T
SB_CORE_VER=F01047X15.01ada48ab2015-04-03
SB_ML_VER=MA0061R06.0404022015
SB_BOOT_SRC=upgrade

The Cisco IR800 has LEDs that are discussed in the Hardware Configuration Guide for each model. There is also a command that will show you the status of the LEDs if you are not near the device. Use the show platform led command with options to view the different output.

Note	The following examples are from the IR829. The IR809 differs slightly.

The Cisco IR800 ships with the latest software available with the configuration that was ordered. There should be no reason to have to upgrade unless a failure occurs, or you wish to install a new bundle to benefit from new features. Should the need arise, the following steps will assist in performing a bundle installation.

Note	The bundle install will fail if “ip ssh source-interface” is configured. Make sure that none of the interfaces have ssh running on them before performing the installation.

IR829#show run | inc ip ssh source
ip ssh source-interface GigabitEthernet0
IR829#

The bundle install command has additional options.

The following items are important to remember when using bundle install:

• The default bundle install flash: ensures that the boot system flash: is set each time. The default will bootup all three images - hypervisor, native IOS and guest-os alike.

• Software mix-and-match between the three images is not supported. The router can only be fully functional if all three images are from the same bundle.

• Cellular modem firmware upgrade is not inclusive in a bundle installation.

• In IOS mode, verify show platform nvram does not have BOOT_MCU_FW_UPGRADE=NEVER and BOOT_FPGA_FW_UPGRADE=NEVER.

• After a bundle installation, it is mandatory the router be reloaded. Prior to a reload, most operations will be non-functional.

The IR829 has an optional PoE accessory (IR800-IL-POE). When installed, it supplies a maximum of 30.8W shared between the 4 GE LAN ports (GI1-GI4). The Power can be distributed among the ports in the following manner:

• If one port supports PoE+ (30W), then the other ports have no PoE.

• If 2 ports support PoE (15.4 W), then the other ports have no PoE.

• All 4 ports can support 7.7 W per port.

Note	The router cannot be upgraded for PoE in the field.

IOS supports bi-directional inline power negotiations with Cisco devices through the use of CDP. Cisco Power Devices (PDs) may signal increase or decrease in their demand for power through CDP. Decrease in demand will result in returning unused power to the pool of available power. Increase in demand will be accommodated, subject to the available unused power and the port power limit (and 802.3at classification where applicable). If the PDs do not support CDP, the inline power allocation is based on the classification if they are 802.3at devices or 15.4W if not 802.3at compliant.

IR829(config)#interface gi2
IR829(config-if)#power inline ?
  auto   Automatically detect and power inline devices
  never  Never apply inline power 
  port   Configure Port Power Level
IR829(config-if)#power inline port ?
  max  Maximum power configured on this interface
IR829(config-if)#power inline port max ?
  <4000-30800>  milli-watts
IR829#show power inline
 
PowerSupply   SlotNum.   Maximum   Allocated       Status
-----------   --------   -------   ---------       ------
EXT-PS           0        30.800    30.000          PS GOOD
Interface   Config   Device   Powered    PowerAllocated   State 
---------   ------   ------   -------    --------------   -----  
Gi1         auto     IEEE-4   On        30.000 Watts      PHONE          
Gi2         auto     Unknown  Off        0.000 Watts      UNKNOWN        
Gi3         auto     Unknown  Off        0.000 Watts      UNKNOWN        
Gi4         never    Unknown  Off        0.000 Watts      NO_POWER      

This feature applies to the IR829 only.

Previously, the IR829 supported PoE allocation/negotiation only for the PD (Powered Devices) which communicate using CDP (Cisco Discovery Protocol). With this release, support is added for Link Layer Discovery Protocol.

LLDP is a vendor-neutral CDP like neighbor discovery protocol that is used by network devices to advertise information about themselves to other devices on the network. LLDP supports a set of attributes that it uses to discover neighbor devices. These attributes contain type, length, and value descriptions and are referred to as TLVs. LLDP supported devices can use TLVs to receive and send information to their neighbors.

Details such as configuration information, device capabilities, and device identity can be advertised using this protocol. LLDP for Media Endpoint Devices (LLDP-MED) is an extension to LLDP that operates between endpoint devices such as IP phones and network devices such as switches. LLDP-MED specifically provides support for voice over IP (VoIP) applications and provides additional TLVs for capabilities discovery, network policy, power over Ethernet (PoE), inventory management, and location information. LLDP-MED contains power management TLV which allows PD (power device) to request power. Power TLV defines the format for power request.

Once power is applied to the port, LLDP-MED (Power TLV) is used to determine the actual power requirement of PDs and the system power budget is adjusted accordingly. The router processes the request and either grants or denies power based on the current power budget. If the request is granted, then the router simply updates the power budget. If the request is denied, the router turns OFF power to the port, generates a syslog message, and updates the power budget and LEDs.

If LLDP-MED is disabled or if the PD does not support the LLDP-MED power TLV, then the initial allocation value is used throughout the duration of the connection. No new CLIs are added and the following commands can be used to troubleshoot.

IR800>show power inline
 
PowerSupply   SlotNum.   Maximum   Allocated       Status 
-----------   --------   -------   ---------       ------ 
EXT-PS           0        30.800    14.389          PS GOOD 
Interface   Config   Device   Powered    PowerAllocated   State 
---------   ------   ------   -------    --------------   ----- 
Gi1         auto     Unknown  Off        0.000 Watts      NOT_PHONE 
Gi2         auto     Unknown  Off        0.000 Watts      UNKNOWN 
Gi3         auto     IEEE-4   On        14.389 Watts      PHONE 
Gi4         auto     Unknown  Off        0.000 Watts      UNKNOWN 

IR800(config-if)#power inline auto
 
IR800(config-if)#power inline never
 
IR800(config-if)#power inline port max 30000

IR800# show lldp entry * 
  
Capability codes: 
    (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device 
    (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other 
  
Total entries displayed: 0 
Switch#show lldp entry * 
  
Capability codes: 
    (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device 
    (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other 
------------------------------------------------ 
Chassis id: 192.168.1.11 
Port id: 002584184414:P1 
Port Description: SW PORT 
System Name: SEP002584184414.DMSBU.com 
System Description: 
Cisco IP Phone 9971, V1, sip9971.9-3-0RT1-100dev 
  
Time remaining: 154 seconds 
System Capabilities: B,T 
Enabled Capabilities: B,T 
Management Addresses: 
    IP: 192.168.1.11 
Auto Negotiation - supported, enabled 
Physical media capabilities: 
    1000baseT(HD) 
    1000baseX(FD) 
    Symm, Asym Pause(FD) 
    Symm Pause(FD) 
    Other/unknown 
Media Attachment Unit type: 16 
Vlan ID: - not advertised 
  
MED Information: 
  
    MED Codes: 
          (NP) Network Policy, (LI) Location Identification 
          (PS) Power Source Entity, (PD) Power Device 
          (IN) Inventory 
  
    H/W revision: 1 
    F/W revision: sboot9971.031610R1-9-3-0RT1-100d 
    S/W revision: sip9971.9-3-0RT1-100dev 
    Serial number: FCH1321927B 
    Manufacturer: Cisco Systems, Inc. 
    Model: CP-9971 
    Capabilities: NP, PD, IN 
    Device type: Endpoint Class III 
    Network Policy(Voice): VLAN data, untagged, Layer-2 priority: 5, DSCP: 46 
    Network Policy(Voice Signal): VLAN data, untagged, Layer-2 priority: 4, DSCP: 32 
    PD device, Power source: PSE, Power Priority: High, Wattage: 10.6 
    Location - not advertised 
  
  
Total entries displayed: 1 

Ensure that your router is running IOS version 15.6(3)M1 or above.

IR829(config)#[no] gyroscope-reading enable

Once this is enabled, gyroscope reading will start by the frequency currently set. Prior to IOS release 15.7(3)M1, the format of the command was:

IR829 (config)#gyroscope-reading frequency ?
1/min Reading 1 times per minute
1/sec Reading 1 time per second
10/min Reading 10 times per minute

From IOS release 15.7(3)M1 going forward, the format has been modified to:

IR829 (config)#gyroscope-reading frequency ?
one/min Reading 1 times per minute
one/sec Reading 1 time per second (default value)
ten/min Reading 10 times per minute

Note	After upgrading to IOS release 15.7(3)M1, the router will have to be reconfigured.

Default frequency is 1/sec. If this is configured, it would overwrite default frequency and any later reading would be according to the newly set frequency.

IR829 #show platform gyroscope-data
Starting Entry = 0, next_entry = 1003, start time = , wrap_around = 0
Date Time G-X G-Y G-Z XL-X XL-Y XL-Z
2016:09:19 18:23:09.26 -1636.25 -367.50 1400.00 -5.795 16.470 1026.203
2016:09:19 18:24:09.23 -2073.75 -481.25 1382.50 -10.309 24.705 1016.504
2016:09:19 18:25:09.28 2152.50 -253.75 1496.25 -7.564 27.267 1016.443
2016:09:19 18:26:08.83 402.50 -647.50 1295.00 -8.113 43.493 1030.046
2016:09:19 18:27:08.90 -1706.25 -1058.75 1295.00 -6.771 41.724 1017.419
2016:09:19 18:28:08.85 253.75 -498.75 1452.50 -4.819 31.110 1030.168

This CLI would only show data if "gyroscope-reading" is enabled. All readings since start (unless wrap-around occurs, which means table is full), would be shown in the order from the most recent to the oldest.

Each entry shows G-X, Y, Z(3D gyroscope data) in mdps (Milli Degrees Per Second) and XL-X,Y, Z (3D accelerator data) in unit mg (milli g forces) where g is ≈ 9.81 m/s 2 .

Note	Configurations would be in running-config and would stay over reload if saved.

The entity OID value is iso.3.6.1.4.1.9.12.3.1.8.230.

The show platform gyroscope command gives information about this MIB.