Posts Tagged ‘Juniper’

Core vs. Edge Routing Topology

There isn’t a lot of talk about this; however, there is a lot of training material that references this debate and makes recommendations for edge based routing. For those not familiar with the topic I am talking about “Campus LANs” and not ISP networks where you essentially have to push routing to the edge for some customers. In my article I am talking about Core vs Edge in the aspect of where we perform all of our routing in a “Campus LAN” Read the rest of this entry »


If you think that when HP purchased 3com they would have either made everything a single code release (can we say, Juniper) or at least provide interoperability documentation that is easier to find and easier to read? You’re dead wrong and you may end up like me and make an assumption that keeps you here longer than you would like to be trying to fix it. To spare you the agony of it all I will just jump right into it… Read the rest of this entry »


How often do we run into problems and have to contact a third party vendor to get the resolution only to spend a large amount of time getting someone (sometimes ourselves) to stop the blame game and start working together? This seems to happen all the time in the IT field and this is frustrating as all hell and we as IT professionals and engineers need to put our ego and pride aside and work on the problem to benefit our customer and I’ll share my thoughts on the various scenarios… Read the rest of this entry »


There are numerous occasions where we would like to utilize a more “human” name to view our physical switchport and router port connections; however, I find that most people don’t maintain these names/descriptions in a proper manner. While this configuration has no bearing on the operation of the switch it will create confusion for those who have to read through the documentation. Read the rest of this entry »


Quote from Junipers facebook:

JUNOS TIP: Suppose you saw that your Alarm LED is red. Issue either the show
system alarm command or the show chassis alarm command.

One reason for chassis alarm is that the management port is not
connected. To clear this alarm, if you are not actually using the management
port, merely execute the following command: root@Junos#set
chassis alarm management-ethernet link-down ignore.

And one reason for the system alarm is that there is no rescue configuration
created. To fix this alarm, merely save a rescue configuration: root@
Junos#run request system configuration rescue save.
Let’s illustrate this:
root@Junos#run request system configuration rescue save


Just though I would put this out there for the world to read…use new network cables! If the cable doesn’t have a locking clasp you’re begging to have someone just brush by and jiggle it loose and then you’re troubleshooting an issue that looks complex when in reality all you have to is plug in a cable! ALWAYS USE NEW CABLES


Let me start by saying that Superscopes are not a standard mechanism of DHCP, just a “hack” by Microsoft to support networks that don’t understand the concept of “1 IP subnet PER vlan, not 10 IP subnets per VLAN”. The only, and I do mean ONLY, time that you use Superscopes is when you have a network design that has multiple IP subnets inside the same VLAN. Let me explain the ONLY instance where this is needed and WHY you need multiple interfaces configured for this to work… Read the rest of this entry »