Why does SWIM require static IP routes or dynamic IP routing protocol for configuration for the upgrade of a run-from-Flash (RFF) partition on a Single Flash Bank (SFB) device?
A. SWIM upgrades SFB devices that are in Rxboot mode. Rxboot mode does not support IP routing, IP bridging, or Simple Network Management Protocol (SNMP). The Rxboot image can support only one IP interface. Before the reboot of the device while in the Rxboot mode, SWIM determines the: • Interface that connects the device to RME servers. SWIM shuts down all interfaces except the one that connects to the RME server. • Default gateway IP address for the forward of all IP traffic when the device is in the Rxboot mode. SWIM queries the ipRouteEntry MIB variables ipRouteDest and ipRouteIfIndex to determine the default gateway IP address and the interface that connects. If the device configuration does not include static IP routes or dynamic IP routing protocol, the ipRouteEntry table is not set on the device. Consequently, SWIM cannot determine the default gateway and the interface that connects to RME.
Related Questions
- Why does Software Management require static IP routes or dynamic IP routing protocol for configuration for the upgrade of a run-from-Flash (RFF) partition on a Single Flash Bank (SFB) device?
- Why does SWIM require static IP routes or dynamic IP routing protocol for configuration for the upgrade of a run-from-Flash (RFF) partition on a Single Flash Bank (SFB) device?
- How do you change the IP default gateway configuration to allow SWIM to upgrade a device?
