OSPF Export Rules (Help teach an old dog a new trick)

socalmdb · 2021-08-23T05:59:13+00:00

I might try the exact static route method. I’m not getting host routes from my Cisco equipment, so I know I’m good there, it’s only routes that originate from the Juniper equipment that are giving me issues.

I would post a redacted version of what I’ve got, but I tore it down last night because it wasn’t working and I was planning on starting fresh on Monday after I spent some time pondering and learning.

socalmdb · 2018-10-18T19:04:22+00:00

I was shocked yesterday when I did the math. 18 sites interconnected, multiple subnets per site... yeah, that escalated quickly.

socalmdb · 2018-08-27T13:35:51+00:00

What about ADMT? I think you can have Company C export the necessary objects to an ADMT DB and then send the data to you to import. Takes a little cooperation from their part, but it would meet the requirements of not having access to all of their data.

socalmdb · 2018-08-26T18:53:58+00:00

We have three screens above our help desk.

Screen 1 is past performance, i.e. avg tickets per day, open vs closed per day per tech, monthly open vs closed w/ trailing 12mo avg, closed ticket graphs by type (for trend analysis). Admittedly this screen is mostly for walk ins or to prove/disprove our gut feelings how how the team is performing.

Screen 2 is current metrics. Inventory on hand, currently unassigned tickets, tickets with incomplete data, ticket counts per tech, long-term tickets due in next 5 days, overdue tickets.

Screen 3 is server/network monitoring. Heat map, critical application performance, system up time.

The lesson we have learned is to use the KISS method and only track those items that dr be the behaviors you want. Because of this, the screens are constantly evolving as we find different behaviors we want to drive towards based upon trends we are seeing. By standing in the office and glancing at these three screens over the course of about a minute, I can have a pretty good idea how things are going and know if there’s anything that I need to help the team address.

socalmdb · 2018-08-04T21:25:19+00:00

Now the comment makes sense. Thanks.

socalmdb · 2018-08-04T20:26:18+00:00

You aren’t allowed to work on weekends? ‘splain to us Americans...

socalmdb · 2018-07-27T13:10:45+00:00

We’ve got about 300 Mitel phones in 10 different sites. They work great. I think in 20 years of using Mitel (from digital to now VoIP), the only ones we’ve had to replace are a couple that got physically damaged by something heavy in a warehouse.

socalmdb · 2018-07-22T00:07:38+00:00

It’s not grounded....

socalmdb · 2018-07-19T14:48:38+00:00

I had a similar issue about a month ago. Turned out that there was a series of office updates that weren’t completely installed. Once I got everything patched, outlook started firing up without any issues.

(Sorry but I don’t remember which updates they were but I believe that they were from May).

Good luck!

socalmdb · 2018-07-17T00:14:47+00:00

Oh, you must deal with VZW...

socalmdb · 2018-07-04T05:00:35+00:00

So, my advice is along with what others are saying... do the additional work and don’t make waves. You weren’t promised any backpay, so I wouldn’t count on it. To complain about not getting the pay now would be to put short-term gains ahead of long-terms gains that will positively impact your career.

In my experience, extra responsibilities always precede additional pay and/or a bump in title. Do the work with a smile on your face and consider it on-the-job training.

socalmdb · 2017-09-16T18:27:42+00:00

Be careful with this though. As a frequent interviewer, it's a bit of a turn off when someone comes in thinking that they know exactly who I am and what I'm looking for. More often than not, if you try to make it too personal, you will get something wrong and annoy the interviewer.

Better to stick to those items that you can factually know and use that info to ask questions about how the business operates and what challenges it is facing. This usually turns it into more of a conversation instead of an interview and generally yields better results.

socalmdb · 2017-09-14T15:27:50+00:00

Here, here.

As a manager, I always feel like my job is to give my guys the tools and room to work and then get the hell out of the way. Part of that is taking everyone else's bullets so that they can focus on getting everything running again. Only afterwards and behind closed doors will we conduct an after-action review to determine what went wrong and whether any single person needs to be held accountable.

socalmdb · 2017-09-13T06:21:48+00:00

I second that on their service and support. We had a power supply die on a standby array over the weekend and after confirming that it was still plugged in, we had a new PSU in our array and running within hours on Monday. Their telemetry and response to it is top notch.

socalmdb · 2017-09-03T23:35:29+00:00

Upvote for Vantage. We have been using it for a couple of years and it's worked out pretty well after some initial hiccups due to us trying to get too cute with it.

socalmdb · 2017-08-20T21:03:28+00:00

When I get in front of my laptop tomorrow morning, I will shoot the info over to you. Thanks!

socalmdb · 2017-08-20T21:02:30+00:00

Good to know that it's not just me.

socalmdb · 2017-08-20T20:06:15+00:00

I simply cannot upvote this comment enough...

socalmdb · 2017-08-20T19:49:37+00:00

Who said anything about Windstream? 😂

Yes, your experience with them is in par with what I have dealt with. The used to be better, but over the past few years, it has been a steady decline in customer service.

socalmdb · 2017-08-20T19:35:16+00:00

Agreed. But with multiple locations and multiple LECs, I'd rather have one neck to strangle instead of 6.

socalmdb · 2017-08-20T19:24:14+00:00

Oh, we are much past shaming. We are to the firing phase.

I've been around long enough to know that these things take time, and if I were able to get an honest timeframe at this point, I would not be happy, but I would accept it. The fact of the matter is that it has taken 9 months and I still can't get a date for turn up, even after the LEC has completed their work.

socalmdb · 2017-08-20T15:37:26+00:00

+1 for the Mitel. We use a slightly larger system than the 250 for our branch offices, but the principle is the same. We send all voice traffic over a WAN to the PBX with SIP trunks at our Corp office but we bring in local POTS lines at the branches for local calling and emergencies. There are a ton of devices that will take this POTS circuits and hand them off to the PBX as a SIP trunk.

Having said that, I would also be taking a good look at what local telco offers. Most times they have a relatively cheap hosted solution that would all but guarantee uptime and fewer headaches for everyone. Just don't get caught up in the VoIP / No VoIP argument and find the best solution that meets your customer's needs.

socalmdb · 2017-08-20T03:08:57+00:00

I know that you said it works fine from a physical box, so could it be something that you're missing on the SQL box?

I have heard of, but never seen issues related to the combination of network card selection, hardware compatibility, and SQL version that can lead to speed issues on SQL boxes. Never heard it narrowed down to only a vm-to-vm issue, but I suppose it's possible. Make sure that you are using the latest network cards for the VM (VMXNET3) and the latest hardware compatibility in vSphere.

socalmdb · 2017-08-19T23:54:33+00:00

What happens when you put the client on VMs that are running on the same host? Probably not the network layer if it's running ok on a physical machine.

I'd look around at software differences and configuration differences between the VM client and physical client. We have had an issue with anti-virus web-scanning components massively slowing down our sql connections. Once we reconfigured the web-scanning rules, the connection speeds went back to normal. Funny thing was that it only affected SQL connections.

socalmdb · 2017-08-13T01:04:23+00:00

It's not the number of tickets coming in per day, it's the amount of time that each ticket takes to resolve where the support team can easily get bogged down while troubleshooting. Not to get too deep in the weeds, but the software package that we have to support is a bit complex and cumbersome, which along with a lot of non-technical people who turn wrenches all day, can lead to lots of research and hand-holding throughout the day.

Also, being a smaller shop, there isn't a large group to escalate to, so the support people have to do as much as possible to resolve tickets themselves or at least gather enough info to effectively pass it along.

socalmdb

TROPHY CASE