cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3149
Views
0
Helpful
4
Replies

Loading SMA configuration file from old appliance to new appliance - mac address values

amelo@
Level 1
Level 1

I’m doing a SMAs hardware upgrade. The procedure in the SMA User Guide for "Making a Backup Appliance the Primary Appliance" (SMA_User_Guide_10_1, p.320) says to import the configuration file (from old/primary appliance) into the new/backup appliance as one of the steps.

 

While checking the configuration file I noticed that in the ethernet_settings section, each interface has the mac address defined.

 

My question is, when loading the configuration file in the new SMA, would this create any issues since the mac addresses of the new appliance won’t match the ones from the old one?

 

Thanks,


<ethernet_settings>

 <ethernet>

  <ethernet_interface>Data 2</ethernet_interface>

   <media>autoselect</media>

   <media_opt></media_opt>

    <macaddr>b4:de:31:e5:59:e7</macaddr>

</ethernet>

<ethernet>

 <ethernet_interface>Data 1</ethernet_interface>

  <media>autoselect</media>

  <media_opt></media_opt>

   <macaddr>b4:de:31:e5:59:e6</macaddr>

</ethernet>

</ethernet_settings>

1 Accepted Solution

Accepted Solutions

Actually I removed everything between <ports> and <ethernet_settings> in the config file. It worked.

View solution in original post

4 Replies 4

Libin Varghese
Cisco Employee
Cisco Employee

I have not seen that in particular generating errors.

 

As long as the hardware model is similar with equal number of interfaces the configuration file should load. 

 

If it does mention any specific errors that section of the can be removed and loaded again. 

 

Regards 

Libin Varghese 

We are going from a M170 to M190.

 

Thanks,

There are differences in the number of interfaces between the two models so best to remove the ip_interfaces and ethernet_settings settings part of the configuration file.

 

Regards 

Libin Varghese 

Actually I removed everything between <ports> and <ethernet_settings> in the config file. It worked.