Most of the time when working the help desk we find that we often may have issues with getting all of the information we need with the ticketing systems that are in place. Some companies have painful prompts that have a predetermined scripts that employees go through which often times leads to frustration with customers and less trained staff. I have worked at a NOC or 2 in my lifetime and it seems that only a few people have developed simple common sense when dealing with customers. One NOC I worked at employed the 5W’s system of what to find out when a problem arises. If you employ this system you will learn to create a good baseline of what to ask and further this will help you develop sound T/S skills as you learn where to probe a customer when they are giving you information. I’ll give an example of a situation today.
• Who? Company X, Employee SUE ext 1234
• What? I can’t get Voice mail on my phone
• Where? Office
• When? Just Happened now
• Why? I’m not sure, (this is a place where you can ask has anyone been on the phone system, or where those pesky IT guys playing around again or was the user themselves in there phone settings.
• How? Sometimes they will tell you, other times they really don’t know. Now you have a baseline of types of follow up questions to ask or you can give her a ticket number if you have to escalate to another user.
This simple user today didn’t have the caller search space for her voice mail set correctly. I’m sure only the IT admins at her job had access to this. That was an easy one. Now Imagine getting a ticket that just says “user can’t log into voice mail at company X”. Those are the types of tickets that make people upset. A person who is assigned the ticket doesn’t’ even know where to go. Who the person is, the extension number or where to even start looking. This would require a call back to the customer find out who’s voice mail isn’t working, how long its been and several other things that could have impact on the problem. All in all this will require some support from management on getting everybody on board, but if you could ask yourself those questions as you write a ticket you will save you and your coworkers some sanity as you have tighter tickets for someone to pick up.
Thanks
Happy Networking.
Tuesday, November 23, 2010
Monday, November 8, 2010
New Job
Well as things have been going all over the place for me. I stumbled onto a job with a partner in the area. I will be moving on from the Routing/Switching world and moving back into Voice. Voice is where I had my real break through and its the most fun for me to work on. I haven't decided which IE track I will peruse that will all be determined in the future, but I hope the road comes up soon. Happy Networking!!!!!!!!!!!
Tuesday, October 26, 2010
Changes and more Changes
Things go weird sometimes. As you may have known in my post about management things haven't been working out the best. I found out that they actually mean well, but they maybe in over there head. As the rumor mill turns I have found some info from "insiders" about on going developments. So more than likely its time to jump ship. I have one job that I had a while back, but had to pass due to medical issues. I contacted them and they are looking to see if the position is still open. Its a large Campus netwok with BGP/MPLS/OSPF. Sounds like good technology hopefully it still open.
Saturday, October 9, 2010
Where have I been???
I haven't posted in a while, I've Been busy with work, life, girlfriend and CCIE studies. I haven't covered as much ground on the CCIE as I had hoped. This is a different beast. For study materials, I have used INE CCIE COD, CCIE written exam book and boson netsim, and I have Narbik gap from CCNP to CCIE lab book to work through as I need to back up some areas of my study with labs. I did put together a quick vid of my lab. My gear list will be below. I have some exciting projects coming up with work. My VOIP deployment was completed. It turned out to only be a small installation. There will be others completing the entire deployment. We have been doing a lot of multicast and QOS work in prep for video and VOIP service been deployed enterprise wide for a customer.
3 3725
3 2651xm
3 2610 Frame relay and BB routers
4 3550
1 MRV console server.
3 3725
3 2651xm
3 2610 Frame relay and BB routers
4 3550
1 MRV console server.
Friday, September 3, 2010
TSHOOT Passed
Well the Journey is over. I'm finally a CCNP. When this exam was 1st announced a lot of people cringed about what they would or could ask you. I can say that they can't ask you much since they are running with a limited sim. The best advice I can give you is come up with a lab and get down a structured troubleshooting approach. We have 3 main ones that are discusssed in the exam. TOP DOWN, BOTTOM UP, and DIVIDE and CONQUER. Well TOP down kinda doesn't work here since we are only dealing with Layers 1-3. Divide and conquer and bottom up work great for the exam. If you haven't already you can get the exam topology.
So you already know what to build and what to look at. Next is how we approach it. I'm sure there are several methods and I will share mine. 1st thing I do is go to the Client PC and run a IPCONFIG. I see if there is a IP address and there is a default gateway. If there is one I ping it. If I don't get a reply then I know its a problem between the PC and the Distro Switch. If I do get a reply I know the problem is further up the topology. So lets say I got a reply I go the default gateway and I ping the Sever on the other side of the topology. Then if no reply I run a traceroute. That can usually get me to where the device is having issues. Once I'm at the device in Question I start the process over again with layer 1. Do a sh ip int br check to see if the interfaces are up. if they are move on to layer 3. Check to see if the neighbor relations have formed. If not find out why. If they have why aren't we passing routes. This is just a quick Idea into how I navigated the exam. I did pretty much the same 3-4 commands for every ticket which lead me to solving the majority of the problems. Happy Networking!!!!
So you already know what to build and what to look at. Next is how we approach it. I'm sure there are several methods and I will share mine. 1st thing I do is go to the Client PC and run a IPCONFIG. I see if there is a IP address and there is a default gateway. If there is one I ping it. If I don't get a reply then I know its a problem between the PC and the Distro Switch. If I do get a reply I know the problem is further up the topology. So lets say I got a reply I go the default gateway and I ping the Sever on the other side of the topology. Then if no reply I run a traceroute. That can usually get me to where the device is having issues. Once I'm at the device in Question I start the process over again with layer 1. Do a sh ip int br check to see if the interfaces are up. if they are move on to layer 3. Check to see if the neighbor relations have formed. If not find out why. If they have why aren't we passing routes. This is just a quick Idea into how I navigated the exam. I did pretty much the same 3-4 commands for every ticket which lead me to solving the majority of the problems. Happy Networking!!!!
Wednesday, September 1, 2010
World of Telco Part 2
So did we get a happy ending? Check the break down
Day 2. I got one the national providers to get a local provider on the phone. They actually came out to site and check the smart jack. No problems found. They then did some smoke and mirrors in telco world and cleared the loop. So now we don't see a loop but no circuit. We then looped from the smart jack back to the other site I knew was good before I came out here. UP/UP. Ran a loop from the the providers near me to my equipment across campus. Down/Down, but this time we we are getting AIS errors. More than likely the circuit has not been crosed, or it has been crossed 2 times and canceled out. No time to try to figure out who had a cross and who didn't. The guys in the demark room crossed it from the smart jack to the repeater. UP/UP. Removed the loop from the cloud back to the router UP/UP. OH YEAH!!!! Direct connection. After that turned on Crypto Maps, Up/DOWN to UP/UP. Setup OSPF UP/UP/FULL Came back to my hotel room.
I get to do this in another city after the holiday. FUN FUN FUN.
Day 2. I got one the national providers to get a local provider on the phone. They actually came out to site and check the smart jack. No problems found. They then did some smoke and mirrors in telco world and cleared the loop. So now we don't see a loop but no circuit. We then looped from the smart jack back to the other site I knew was good before I came out here. UP/UP. Ran a loop from the the providers near me to my equipment across campus. Down/Down, but this time we we are getting AIS errors. More than likely the circuit has not been crosed, or it has been crossed 2 times and canceled out. No time to try to figure out who had a cross and who didn't. The guys in the demark room crossed it from the smart jack to the repeater. UP/UP. Removed the loop from the cloud back to the router UP/UP. OH YEAH!!!! Direct connection. After that turned on Crypto Maps, Up/DOWN to UP/UP. Setup OSPF UP/UP/FULL Came back to my hotel room.
I get to do this in another city after the holiday. FUN FUN FUN.
The world of Telco
The world of telco. It seems so simple to us, but at times it can be hair pulling and mind numbing. To most people it just seems like smoke and mirrors on how they get their connections, to us who provide network services it’s a never ending battle of proving who’s right and who’s gear it is. Lets start with todays example. I have been hooking up a series of sites for a client. They are on a quest to get all of there sites off random cable/sat modems to 1 unifed network. By the way hats off to the guy who got the initial setup done, some fancy tricks done with IOS firewall that I will be borrowing from you ☺. The site in particular I had the circuit delivered to one site much earlier so I took advantage and got loops up from the telco’s gear on the other site. UP/UP. I’m thinking this is going to be easy turn up. WRONG. 1st problem. On the other side the circuit was finally delivered, the problem was that the circuit delivery point and my facility had some distance between them. Those guys just extended the circuit not even thinking about that a T1 signal can’t go that far. To be fair this was a free service. I guess paid service they would have thought about that. So I had to rush out and get repeaters(not really rush I just grabbed them off the shelf and get them shipped). Ok done that simple. Site turn up day. The guys had the circuit patched wrong. That took a few min to fix. Then I stripped down a pair got them to the 66 block and Repeater. Got the repeater to the other side and do the same process. Repeaters sink up. Easy day. Nope. After on the phone with the Telco they are telling me we have a pair flipped wrong. Now the guys I were working with where some country bumpkins, but I had a strong feeling they knew what they were doing and the telco’s history has been shaky. So what I do is run back to my equipment use a female loopback and look the circuit back to the telco. They see it up., I unplug it and they see it UP!!!! Power down the Repeater they see it up!!!!!!!!!!!!!!!!. Pull the cable from the smart jack and guess what it was UP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Those bastards have a loop in the circuit after insisting is was our end. I don’t have a happy ending to this story just more of a rant of my world of telco’s. Happy Networking!!!!!!!!
Subscribe to:
Posts (Atom)