Cisco Cisco SM-X Layer 2 3 EtherSwitch Service Module

Page de 34
Cisco SM-X Layer 2/3 EtherSwitch Service Module Configuration Guide for Cisco 4451-X ISR
  Troubleshooting the Cisco SM-X Layer 2/3 ESM Software
27
Cisco SM-X Layer 2/3 EtherSwitch Service Module Configuration Guide for Cisco 4451-X ISR
Example
Following is an example of the configuration assuming a 16 port module is configured in slot 1 and a 24 port 
module in slot 2:-
Configuration on the router: 
interface gigabitethernet 1/1 
 switchport access vlan 10
!
interface gigabitethernet 2/1 
 switchport access vlan 10
Configuration on the 16 port SM-X module in slot 1: 
interface gigabitethernet 0/17
 switchport access vlan 10
!
Configuration on the 24 port SM-X module in slot 2:
interface gigabitethernet 0/25
 switchport access vlan 10
You can apply the trunk port configurations if the port needs to be a trunk port.
Troubleshooting the Cisco SM-X Layer 2/3 ESM Software
This section describes how to troubleshoot the Cisco enhanced EtherSwitch service module:
Recovering from a Corrupted Software Image Using Boot Loader
The Cisco SM-X Layer 2/3 EtherSwitch Service Module software can get corrupted when downloading 
a wrong file during the software upgrade process and when the image is invalid or even when there is no 
image available. 
The load_recovery command allows you to recover from a corrupted software image, an invalid image 
or no image on the flash of the module.
The load_ recovery command boots the ESM with an IOS image (recovery image). Once the module is 
booted, desired Cisco.com switch image can be copied to the module flash through TFTP from the 
router’s flash or through the ESM front panel switch ports. 
Copying a Cisco.com switch image to the ESM flash through module’s front panel switch ports only 
works when there is a connectivity established to the TFTP servers from the front panel ports of your 
ESM.
Note
The router should have the ESM image in the router flash memory or the ESM should have network 
connectivity to TFTP server through its front panel ports.
Note
We recommend that you continue all network operations using the new image and not the recovery 
image.