Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
05-22-2013, 08:52 PM
|
#1
|
Member
Registered: Jan 2006
Location: USA
Posts: 742
Rep:
|
Does this make sense?
so, below is a how-to for swapping the service iface on a RSA A130/A250 appliance. does this make sense? am i missing something, isnt this the same as just swapping IP in the the files?
Code:
The real fix for this problem is to RMA the non-working appliance, however, it is fairly easy to swap over to the currently unused eth1 from eth0,
as a temporary measure, to keep the appliance in production while awaiting RMA.
Short summary :
a) flip the roles of the /etc/sysconfig/network-scripts ifcfg-eth0 file and ifcfg-eth1 file,
b) and adjust the routing table [if needed], to eth1 with the /sbin/route command.
Detailed steps:
1) establish access to the appliance with a direct keyboard and monitor
2) login as emcsrv
3) become root user with 'sudo su' and emcsrv password
4) become user rsaadmin with 'sudo su rsaadmin'
5) shut down rsa services cleanly with ./rsaam stop all (appliance 3.0), or ./rsaserv stop all (AMX)
6) 'exit' to become root user
7) go to /etc/sysconfig/network-scripts directory
8) make backup copies of ifcfg-eth0 file and ifcfg-eth1
a) cp ifcfg-eth0 bak-ifcfg-eth0
b) cp ifcfg-eth1 bak-ifcfg-eth1
NOTE: the backup files cannot begin with 'ifcfg'
If the system boots and sees any files named 'ifcfg...' it will try to load them.
So here we name the backups 'bak-ifcfg' instead of 'ifcfg-bak...' to prevent problems later
9) get the MAC addresses of each interface
a) cat ifcfg-eth0
make note of the mac address
b) cat ifcfg-eth1
make note of the mac address
10) flip the files and make eth1 the active interface
a) rm ifcfg-eth0
b) rm ifcfg-eth1
c) cp bak-ifcfg-eth0 ifcfg-eth1
d) cp bak-ifcfg-eth1 ifcfg-eth0
e) now edit file ifcfg-eth0 and change the first line to say eth0 (it will say eth1)
f) and also change the mac address in here to be eth0 mac address (should only be the last octet needing change)
g) now edit file ifcfg-eth1 and change the first line to say eth1 (it will say eth0)
h) and also change the mac address in here to be eth1 mac address (should only be the last octet needing change)
11) reboot
|
|
|
05-23-2013, 02:38 PM
|
#2
|
Moderator
Registered: Mar 2011
Location: USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu, Debian
Posts: 9,955
|
It's swapping the physical interfaces to be defined differently in the system. What used to be eth0 will now be eth1, and vice versa. It is not the same as swapping the IP addresses. My guess is that the card for eth0 fulfills a primary activity on their system and the card for eth1 fulfills the backup role. Guessing, but if the eth0 interface is not working properly, they recommend that you swap which interface is named eth0 and use that as your primary. Ultimately they're saying that you should return the appliance via RMA.
|
|
1 members found this post helpful.
|
05-30-2013, 07:39 PM
|
#3
|
Member
Registered: Jan 2006
Location: USA
Posts: 742
Original Poster
Rep:
|
if you edit the two files, swap the eth[x] and MAC, then rename the files one for the other, doesnt that leave only the IP as being different (eth0 IP is now on eth1, and vice-versa)?
sounds like the RSA services are bound to the iface that has specific IP and/or MAC, so to me it seems easier to just swap IP and MAC from one file to the other.
|
|
1 members found this post helpful.
|
05-31-2013, 08:03 AM
|
#4
|
Moderator
Registered: Mar 2011
Location: USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu, Debian
Posts: 9,955
|
Yeah, the IP has been swapped to a different physical card, because the process identifies the cards differently now. My assumption is because there was something wrong with the original primary card which used to be eth0. Seems pretty clear from their statement that the complete solution is to return the appliance; however they have a work-around until you get a replacement.
|
|
1 members found this post helpful.
|
All times are GMT -5. The time now is 05:22 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|