Deathmage wrote: » this has interested me too.... since I deal with allot of process manufacturing.
ITNewbie2 wrote: » I am not 100% sure what topics the Cisco's industrial certification exam will cover...
broli720 wrote: » You're better of going the routing and switching path. Information here seems a bit redundant. Half of what I learned in the industrial environment was through experience. Core fundamentals in networking were key though.
TWX wrote: » Sounds like if you're going into infrastructure design this plus a BICSI cert might be a good thing to have if you expect to do commercial/industrial.
realPSI wrote: » CCNA R&S or Security is much more valuable breaking in. Look for companies such as ABB, Emerson Pws, Siemens, Toshiba, Alstom, or a utilities.
Deathmage wrote: » this would be good to have after a R&S and Security. I will contest most of that blueprint above I worked with on a daily basis at my previous employer, they made corrugated boxes in a 1.5 million square foot factory with about 5 separate /22 networks on your typical medium sized campus network. Having a understanding of high voltage and I mean multiple 240a breakers right next to a IDF switch causes all kinds of problems.... learning how to properly divide traffic and shielding so that converting, manufacturing, tooling, shipping and receiving process data is no easy task when a building is literally a EMI nightmare... I mean I do Cat5e/Cat6 cabling myself because I used to run miles upon miles of cabling, and STP not UTP, STP isn't the easiest to work with... ...then QoS was a big deal so everything was on a small vlan with traffic priorities.... ....then you throw sockets into the mix, every device on the PLC's had their own sockets.... Glad wireless is on there, cause in plants you sometimes have Honeywell PC's on countless forklifts that all need wireless access in real time to ERP systems, and troubleshooting those issues while sitting on a forklift was very interesting to say the least.... glad they have redundancy on there cause in a factory if a plant is offline for 5 minutes it can be millions of dollars of lost revenue and deadlines not meet by planning. So I remember I always saw a price tag for stuff and tripled it cause I needed a backup of a backup of a backup. When you start factoring that in for switches, routers, firewalls, servers, ether-channels, etc.... it starts adding up.... but the costs involved with everything offline was worth the cost.... I remember one upgrade to run a distro expansion costs a frak ton of money, we used brand-new Cisco 4500E's and we need two of them even if one just sat there for like forever....we bought 12 of them.... that was a fun project to deploy but god dam was it pricey... moral of story you need everything redundant in an industrial network... as many know, my experience far outpaces my certifications, but that's normal with everyone. Completely agree. Industrial has so many factor it's nutso, you won't find them on a typical network...So glad I had the experience of it all so easy in my career. My problem is it made me a JOAT's which carried me into my current employer and I'm doing it fine solo.....
ITNewbie2 wrote: » Wow! That was a lot of things you've mentioned that I've never even realized. From the get go, I had a feeling that industrial networking is probably very different than your typical enterprise networking, but just how different is something I am dying to find out. So this is my story: I worked for a company that manufactures industrial grade switches for years, but I was not in a technical role. A year ago I decided to pursue my first I.T. certifications starting with Network+, then CCNA, then Security. I took a real interest in networking because for years I was talking to customers like you about the specifications of the products, but was always half-ass in knowing exactly how the devices functioned and how it impacted the plant floor, except the knowledge that customers are buying industrial grade devices because of the IP30/67 ratings. But spanning tree protocol, IGMP, redundant power input, SFP slot availability, hello?????(that was then) I memorized all of the specs the products came with and can rehearse them out load like today's special on a menu, but didn't know what all the fuzz is about when customers starts talking about those things I mentioned above. I guess you could be one of those guys I may have talked to in the past, then happily transferred the call to a real engineer in my company when the conversation starts getting technical. I guess I turned that feeling of embarrassment into motivation when I started pursuing my CCNA. So what's a JOAT? that sounds interesting.
Deathmage wrote: » Industrial is very much a different animal. For me that job was interesting, it had the Industry side and then a campus building attached to it that was the Executive branch that is your typical Medium Sized Campus network, so moving from Industrial to R&S was interesting. Since Industrial is so much tech is so many directions I was a Jack-of-all-trade or JOAT's, so I was pressed from a helpdeks into Wintel/Networking/VMware/Storage/Wyse-Thin-Clients out my ass and on top of it all it was a 24/7 operation so I never had time off. Some of you think I'm insane now with my studies imagine working a 70 hour week and that being normal.... With that being said, be careful what you wish for Industrial is a 24/7 job literally....took lots of trial-n-error for me to figure it all out.