Link to home
Start Free TrialLog in
Avatar of jchri66
jchri66

asked on

How to connect to network for config restore

I have a replacement unit from Cisco that I need to drop our config onto.  I can access the PIX via the Console and have configured the int1 IP but I can't ping out to my laptop that is running a TFTP server.   I've tried a normal patch cable, & cross-over cable.  I feel like I'm missing something easy.   Any ideas what I'm missing?  All I want to do is to be able to copy over a config to the replacement unit.  Maybe this is not the best way to do this?  
ASKER CERTIFIED SOLUTION
Avatar of Les Moore
Les Moore
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jchri66
jchri66

ASKER

I knew I could do that, but is there a way to connect to a TFTP server to download the config?  Right now I can't connect to it attached to Eth1 port.  I just want to know how to do it.  Also, when ever I make a change to the PIX right now I get:
Warning ... Configuration Replication is NOT performed..... " 
Does this mean it's configured for failover and will putting the config on it clear that.  Also, will putting the config on it update the license or will I have to that?
Avatar of jchri66

ASKER

And actually, I just tried to copy and paste the config and that didn't work.  In between each command it errored with Type help ot '?'.
Avatar of jchri66

ASKER

Opps forgot config.  Most of it took but again I feel like this is setup as a failover I keep getting the warnings after each entry.  Do I need to do anything for DES licensing?  The production PIX had it but this doesn't and I got error messages during the config paste.  
Avatar of jchri66

ASKER

OK, interesting......  After I pasted the config I reloaded the PIX without saving so when it came back up the config was the same as before I ran it.  All the replication warnings are gone and I can now get to the interfaces without any issues by connecting to the inside interface with a normal patch cable.  Any suggestions on why this happened?  
Not sure, but sometimes Hyperterm shoves the data too fast for the console to accept it and you have to add a 2-3 ms line delay in the hyperterm settings.
If you were not in config mode then of course you would get the errors after each line.
Avatar of jchri66

ASKER

OK, I worked everything out in the last week.  Cisco support said the PIX was probably configured as a failover in the past and was holding on to that internal configuration for some reason.  He didn't give me any other reason for it but said these things happen....  
After I copied and pasted my config with tons of errors and sync messages the PIX came out of that mode and allowed me give the inside interface an IP and let me go through the TFTP process to pull down the config.  Swapped it out with the old PIX and everything is good to go now.  So I think the answer is really just a bug and I wasn't doing anything wrong in the first place.  I'm sure someone out there would read this and know the reason for the initial issues I had but the Cisco rep didn't so I'll leave it at that.