Michael McNamara https://blog.michaelfmcnamara.com technology, networking, virtualization and IP telephony Sat, 18 May 2024 17:52:24 +0000 en-US hourly 1 https://wordpress.org/?v=6.7.1 Juniper EX4100-F-12P power supply failed? https://blog.michaelfmcnamara.com/2024/05/juniper-ex4100-f-12p-power-supply-failed/ https://blog.michaelfmcnamara.com/2024/05/juniper-ex4100-f-12p-power-supply-failed/#comments Sat, 18 May 2024 17:48:43 +0000 https://blog.michaelfmcnamara.com/?p=7478
Juniper EX4100-F-12P

We use a few Juniper EX2300C and recently EX4100-F-12P switches where we have a need. Interesting issue with the EX4100-F-12P, it appears that you can power it over PoE. However, if you power it from a standard power supply you’ll get syslog messages indicating that there is a power supply failure. Junos seems to think because the switch isn’t being powered by PoE that there’s a power supply failure.

Mar 18 16:20:55  EX4100F chassisd[17857]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply failed (jnxContentsContainerIndex 2, jnxContentsL1Index 1, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 1 @ 0/1/*, jnxOperatingState 6)
Mar 18 16:20:55 EX4100F chassisd[17857]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply failed (jnxContentsContainerIndex 2, jnxContentsL1Index 1, jnxContentsL2Index 3, jnxContentsL3Index 0, jnxContentsDescr Power Supply 2 @ 0/2/*, jnxOperatingState 6)
Mar 18 17:20:56 EX4100F chassisd[17857]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply failed (jnxContentsContainerIndex 2, jnxContentsL1Index 1, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 1 @ 0/1/*, jnxOperatingState 6)
Mar 18 17:20:56 EX4100F chassisd[17857]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply failed (jnxContentsContainerIndex 2, jnxContentsL1Index 1, jnxContentsL2Index 3, jnxContentsL3Index 0, jnxContentsDescr Power Supply 2 @ 0/2/*, jnxOperatingState 6)

We opened a ticket with Juniper and they believe it’s a flaw. Issue is that we monitor over 1,000 switches and we use the syslog feed to create alerts and tickets for review, now we’ve need to build exemptions into our logging to deal with these false positive alerts.

Hopefully Juniper will fix this bug.

Cheers!

]]>
https://blog.michaelfmcnamara.com/2024/05/juniper-ex4100-f-12p-power-supply-failed/feed/ 1
100% Cable Patching in the Closet? https://blog.michaelfmcnamara.com/2014/06/100-cable-patching-in-the-closet/ https://blog.michaelfmcnamara.com/2014/06/100-cable-patching-in-the-closet/#comments Sun, 22 Jun 2014 13:32:00 +0000 http://blog.michaelfmcnamara.com/?p=4302 With the move to a new organization comes some adjustment and occasionally some surprises. While my last employer was very rigid and bureaucratic, my new employer is extremely flexible, deplores ‘process for the sake of process’ and is extremely fast paced. There are pros and cons to everything in life although I’m not going to talk about my employers today.

Instead let’s talk about patching in the closet, sometimes referred to as the ICR (Intermediate Communications Room) but more often referred to as the IDF (Intermediate Distribution Frame).  There are a few different mindsets when it comes to patching the data jack to the network switch. Some organizations, including my new employer, believe in 100% patching to eliminate the need for any local technician to patch ports. Some organizations believe in running lots of cabling, and only patching what’s needed at that point in time. In July 2012 I showed off some of the closets that I personally built and others that I inherited in a post titled, Wiring Closets – Done Right!

IMG_20140428_074659617Here’s a recently constructed IDF with a stack of Cisco 3850X switches and 6″ patch cables. It looks pretty clean doesn’t it? Although, you can see that the 6″ patch cable doesn’t allow too many options when patching the data jack. You essentially need to connect the data jack to the switch port either directly above or below the patch panel.

I would probably personally choose a 1′ patch cable to allow a little more freedom and slack. There are no free rack units in that layout so replacing a failed switch will require the engineer to label  some if not all of the ports, remove the cables, remove the failed switch and reverse the process. In previous switch stack deployments I had left 1 open RU below every switch so a technician could place a new switch in the rack (put the switch in from the rear if necessary then install the ears) and then just move the patch cables to the new switch.

There are pros and cons to each approach, it really depends on the organization and what makes sense for them and how they do business.

How to you patch your closets?

Are you still using chassis based switches?

Cheers!

]]>
https://blog.michaelfmcnamara.com/2014/06/100-cable-patching-in-the-closet/feed/ 2
And the winner is – Avaya https://blog.michaelfmcnamara.com/2009/07/and-the-winner-is-avaya/ https://blog.michaelfmcnamara.com/2009/07/and-the-winner-is-avaya/#comments Mon, 20 Jul 2009 17:00:24 +0000 http://blog.michaelfmcnamara.com/?p=825 avaya-thumbAs with the sale of Nortel’s wireless division, Avaya is now the “stalking horse” for the enterprise division. I had heard that Avaya had walked away from the table but I guess for $475 million it’s too cheap to resist.

With the overlap of voice solutions I’m really curious how this will play out with the voice solutions. As for the networking components I don’t believe Avaya has much of anything so it should certainly help them sell complete solutions.

Cheers!

References;

http://www2.nortel.com/go/news_detail.jsp?cat_id=-8055&oid=100259133&locale=en-US
http://www.avaya.com/gcm/master-usa/en-us/corporate/pressroom/pressreleases/2009/pr-090720.htm
http://www.allaboutnortel.com/2009/07/20/mike-z-s-zmail-about-nortels-enterprise-sale/
http://www.allaboutnortel.com/2009/07/20/nortel-to-sell-enterprise-business-to-avaya/

]]>
https://blog.michaelfmcnamara.com/2009/07/and-the-winner-is-avaya/feed/ 5