I don't understand why people continue to use it, when there are MANY other manufacturers making much better, and much cheaper, gear. I will say that their support is awesome, though. But it has to be, because their products are so weird. Anyone know how much RAM it needs in a ? I've got in mine right now. Just my experience. I don't particularly hate it, but I can't say I've ever had this sort of problem doing a JunOS update.
Not too many people around here seem to use Juniper stuff much though, so maybe it just has a bunch of issues I'm not aware of. I agree with Molo, I've always found the Cisco love a little strange. You didn't read the release notes first? Some NAT commands and features don't even exist in 8. The release notes cover this specifically. Upgrading a full release rev like that without at least a token glance at the release notes is a pretty blind leap. But then, you knew to get the ram upgraded And you had no config backup?
Whose fault is your pain now? Are you really sure it is blank even? Not just completely different looking that you expected?
Quote: You didn't read the release notes first? My biggest complaint with Cisco is that they treat minor versions like major versions. Why the fuck are they changing command sets in a minor version? Sure, once you understand this it is easy to get around, but everytime you go back to ANYONE else's product for a while, you have to remember it again when you come back.
It's not Cisco, it's the ASA product managers that got promoted We have until on these devices for end of support so we're hoping Cisco will put the ASA line out to pasture before then. Good luck with the upgrades. I've found it hard to get a solid answer on who is better and how. I find a number of vendors just slamming Cisco and promoting theirs while not really giving the details, customer reccommendations etc, that would really convince someone from investing in a different product and moving their enterprise to it.
You hate the ASA platform and are not going to upgrade until it is gone The software is the same well, except that the code that supports the PIX dead-ends at 8. Yeah I'm sorry to not help the pain, but I really gotta say it's your own fault here, for not reading the release notes before making a point version upgrade on a network device.
Especially when it's well known to anyone who works with Cisco gear on an ongoing basis that point versions might as well be major versions I swear it's like the major version number is part of the product name and the minor version is the real version But seriously Especially on core devices or internet-facing devices, this was a bad move on your part.
NEVER assume feature, command, or spiritual parity between two versions of software for a network device. This is a common enough issue biting enough people in the ass rightfully so, damn it that you'd think someone would think twice before doing it on a production device Apparently not I made a backup of the config files. But since I had the config files, I simply printed them out and rebuilt them by hand using the "new and improved" 8. But converting nat outside 1 Why not just roll back to the 8.
The upgrade process saves a copy of your 8. We had to do that on our 8. I think the 8. It's just waaaay too different for a minor version change. That said, if you have a failover pair, you could always kill the redundancy and perform the upgrade on the standby unit, move it to active, and then upgrade the primary.
This would give you a rollback safety net for when shit goes south. Sorry to hear things went so badly. IOS is a different ballgame though - most of us live with the quirkiness and occasional feature failure because of TAC and IOS being absurdly feature-rich compared to everyone else.
I'm not sure my company is going to stay with the ASA platform for a whole lot longer though; other players offer so many more features and throughput that it's hard to argue Cisco in that arena any longer. One things I've learned is a lot more features, and a lot more features that actually work properly are often two different things. Who do you recommend? Riverbed and Palo Alto for sure, and depending on the situation Juniper or Force10 or Xsigo have more compelling features.
Quote: IOS is a different ballgame though - most of us live with the quirkiness and occasional feature failure because of TAC and IOS being absurdly feature-rich compared to everyone else.
I am going to be another guy who asks, who would you replace them with? And don't get me started on Checkpoint and their Crossbeams. That has to be the worst platform ever. Cisco's sometimes limited feature set has one huge advantage - the limitations and workarounds are well known.
I have not used Riverbed or Palo Alto, but my company does not use them. What SRX problems are you running into? We got stuck during our initial deployment because for some reason our SRX was just refusing to NAT, but Juniper Support figured out what the actual problem was pretty quick and got it resolved. It's probably the only real issue I've had with that line so far. Biggest problem we have is managing oh, say, devices at the same time. I feel that the per-interface ruleset of Cisco works better than the per-zone ruleset of Junipers and Fortigates when scaling at these numbers.
I wouldn't deploy devices, I'd deploy a more sane remote access solution like Citrix. We have a few hundred remote offices but only manage devices for about a dozen of them where it's a large enough office to justify a dedicated IT infrastructure. This is to keep the average age of the laid-off people under a certain age 50 IIRC and to prevent the big C from being sued for age discrimination. Ask them how it feels going on interview after interview, learning each time how unprepared they are to compete outside of Cisco.
For the ones lucky enough to get a new job quickly, ask them about the culture shock they experienced when they saw how much more effectively and enjoyably most other companies function. They will throw you under the bus. Save as much money as you can for as long as you can stand it. Bad management was mostly to blame, resulting in poor advancement, boring work assignments, and stifling frustration. You can dismiss the people who are telling you to run for the hills as soon as you can as haters, but the self-attrition data is what it is.
How many layoffs have you witnessed? Have you watched an organization be dismantled and outsourced yet? Its a shock changing a company from high tech leader to a financial management company.
All the engineers with their days of pride creating great products at Cisco are in the dusty past. Of course the old company people are shocked and outraged, frustrated. They don't understand whats happening. The top people figured this out long ago and left. All that matters is that you're happy, enjoying what you do and feel recognized. This site is a place for haters to congregate, so you're hearing from a vocal minority. Most folks here left Cisco involuntarily, so they're bitter Kid, I loved it when I was your age too.
Staying there too long is my biggest regret in life. I truly loved the company, and wanted it to be the entity that benefited most from my knowledge and skills. But Cisco is its own worst enemy. It rewards mediocrity, encourages complacency, punishes those that that think outside the box. It discourages innovation. It sh--s on its technical people, paying them a fraction of what they are worth at peer companies. Full disclosure: I still hold Cisco stock but not for much longer. Chuck And Kelly have bolstered the share price with spin and creative math.
They are running out of spin stories to keep analysts happy. The house of cards will crumble at some point. So heed my advice. Enjoy what you like about it. Learn all you can while you are there. In a test environment the device probably would not have shown the issue, but would have been good CYA. The Cisco products list tons of features with just as many caveats. Frustrating for sure, since you can pay for a different product or go opensource and have the same amount of issues.
To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks.
I'm by no means a Cisco expert, so bare with me. I immediately disable "Top Usage Status" and than noticed this little info Popular Topics in Cisco. Which of the following retains the information it's storing when the system power is turned off? Submit ». Pure Capsaicin. Robert Aug 27, at UTC. Jimtheitguyagain This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.
0コメント