<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>ISR - Tag - Fryguy's Blog</title><link>https://hugo.fryguy.net/tags/isr/</link><description>ISR - Tag - Fryguy's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 23 Jan 2011 14:03:15 +0000</lastBuildDate><atom:link href="https://hugo.fryguy.net/tags/isr/" rel="self" type="application/rss+xml"/><item><title>Integrated Switch Modules in Routers (SM-E3SG and NME-XD)</title><link>https://hugo.fryguy.net/2011/01/23/integrated-switch-modules-in-routers-sm-e3sg-and-nme-xd/</link><pubDate>Sun, 23 Jan 2011 14:03:15 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/01/23/integrated-switch-modules-in-routers-sm-e3sg-and-nme-xd/</guid><description>&lt;p>In the Small Branch office type of environment we are commonly limited to the budget of the design, the space for the hardware, as well as the remote supportability of the site.  By supportability I refer to being able to walk someone through what each device it, what it does, and how to check when (not if) there is a problem. Normally this design may look something a router connecting to WAN links (T1/DS3/etc), then that router connecting to some type of switch or switches, and finally the end stations being connected to the switch(es).  Perhaps in a simplistic fashion, the network looks like this:&lt;/p></description></item></channel></rss>