Cisco 1861 and Cisco 2800, 3800, 2900, 3900, and 3900E Series Integrated Services Router Interoperability with Cisco Unified Communications Manager Data Sheet (PDF - 1 MB) Cisco ISR & ASR Application Experience Routers Ordering Guide (PDF - 158 KB). Effectively, all modules are connected to the motherboard slot on the switch, which is always slot 0 and the first zero in the interface name. If you have a switch installed in a router HWIC or working with a chassis-based system, specify the slot that the card is installed into and then the interface in the format of 0/0/1 — 0 for the.

Related article: Silencing a Cisco 2951 router.

I recently purchased a Cisco 2911 to replace my 1921 for use at home, as I needed an extra WIC slot. Now that they’ve been obsoleted by the ISR 4000 series, they’re starting to appear on eBay for relatively palatable sums. For me, the 2911 was a good choice because it has four WIC slots and fits in a 450mm deep rack, whereas the 2901 requires at least a 600mm deep rack, which is far too large for my home office. The 1941 was another possibility, but it’s not enough of an upgrade, and quite frankly, too damn ugly.

Without even having to bother plugging it in and switching it on, I know this thing is going to be too noisy for a home environment. The good news is that the standard array of leaf-blower strength fans are only needed when this product is used in extreme situations, i.e. loaded up with a four WIC cards, a 24-port Gigabit switch service module, with PoE, all ports at full power, and roasting in a street cabinet on a searing hot day in Egypt.

As this does not remotely resemble my use case, I can do away with most of the cooling. First stop – the fan module:

Top is the original, which I am going deaf just looking at, and below is my modified module.

I’ve removed all four of the original fans and fitted a single 70mm 4-wire fan (Delta AFB0712HHB). In order to prevent the system log from filling up with warnings about failed / missing fans, I’ve connected the tach signal from that one fan to the input for the 3 fans.

A quick run of ‘show env’ reveals that this has done the trick. The router being none the wiser to three of the fans being absent.

Just in case it isn’t obvious – the pinout for that connector (Molex 44133-1208) is as follows:

• 1 TACH – 40mm
• 2 TACH – 70mm (rear-most fan)
• 3 GND + Orange presence strap
• 4 TACH – 70mm (middle fan)
• 5 TACH – 70mm (front-most fan)
• 6 GND (middle and front-most fan)
• 7 PWM – 40mm
• 8 PWM – 70mm (rear-most fan)
• 9 +12V
• 10 PWM – 70mm (middle fan)
• 11 PWM – 70mm (front-most fan)
• 12 Orange presence strap

Fortunately I have the Molex Micro-Fit 3.0 contact extraction tool, and crimp tool handy making this easy, but failing that a new connector and contacts could easily be purchased from Mouser.

In my setup, everything runs from a single battery backed regulated DC +12V source. This is no coincidence, as most I.T. equipment internally runs from +12V, meaning that in almost all cases my gear doesn’t require an internal power supply. This router is no exception, needing only a single +12V source (with 5V standby voltage), so I effectively don’t need the power supply here either.

Good news for this conversion, because that’s another source of heat done away with, in fact it means that I don’t need any cooling in the lower half of the router, so that inlet vent can be blanked up – focusing the cooling Mojo of my single 70mm fan solely on the top (mainboard) half of the router.

But it’s not quite that simple. On my previous router (a 1921) the +12V could be feed straight through to the mainboard with no extra components. On the 2911, we need a bit of extra stuff to satisfy it.

I whipped up a small emulator PCB which fits in place of the power supply’s original PCB, and has all the extra bits needed to satisfy the routers’ software / hardware – i.e. present its’ self as a PWR-2911-AC, leaving the router none-the-wiser to the fact that it is now powered by an impostor power supply. The downside is that there is nothing but empty wasted space in the lower half of the router.

I’m not going to go into the details of this, but you can download its schematic here. While I was at it, I moved the power switch and inlet to the rear and blanked up the front. A little more convenient, because it means I don’t have to grope around in the back of my rack. For anyone else with the desire and patience to construct an emulator board like mine, a 60W power brick can easily replace the internal power supply.

A quick check shows that IOS is happy with my phony power supply, with the temperature sensor working, serial number and model number still reading as per the original AC supply this replaces.

The power consumption of an idle unloaded 2911 at the 12V stage is 1.8 Amps (about 23W) – show environment reports a lot higher (38W), I am assuming this takes into account inefficiency in the power supply.

If we are to assume that this is also the unit TDP – It’s practically bupkis given its large size. According to my scientific ‘finger on heatsink’ tests, all of my WIC cards run very cool. The mainboard ASIC also barely gets warm to the touch.

The only thing I need to keep an eye on is the CPU temperature. The CPU in my unit is a Cavium Octeon (MIPS64), which is fairly energy efficient, but still chucks out the loins share of the heat. It has an internal temperature sensor, which we can read out with the ‘show environment’ command.

At 61 degrees, it is 2 degrees hotter than it was with the stock hurricane grade array of fans, where it sat at 59 degrees. Suffice to say that for my light use case, those fans are indeed completely unnecessary.

For anyone thinking of attempting this…

Having a single fan is ideal, because there is no risk of irritating ‘beat patterns’ (which often occur when fans rotating at similar speeds are near each other) – but you can only get away with a single fan if also doing away with the power supply, there’s nothing in the service module bay, and the inlet for the lower half of the router is blanked up. As is the case with mine.

As the PWR-2911-AC does need a little bit of airflow at 30-40 watts, I would suggest replacing with three thinner 70mm fans (like the one I have used) and doing away with / blanking up the 40mm fan, because quiet 40mm fans have so little airflow they’re not really worth it, then strap the tach signal for the 40mm fan to one of the 70mm fans to eliminate software errors.

This post explains the interface numbering scheme used in Cisco 1800, Cisco 2800 and Cisco 3800 Series Routers. It also includes line numbering associated with async interfaces.

Existing router platforms (earlier than Cisco 1800, Cisco 2800, and Cisco 3800) contain a limitation. In some situations, such as when you insert WIC(s) out of order, the configuration of one WIC interface can be lost or applied to another WIC interface.

Example: Assume that you have a serial WIC-2T in WIC slot 1 and WIC slot 0 is empty. The interfaces are named serial 0/0 and serial 0/1. If you insert another WIC-2T into slot 0, the new WIC interfaces are named serial 0/0 and serial 0/1. The old WIC interfaces become serial 0/2 and serial 0/3. Therefore, the old WIC interface configuration moves to the new WIC interfaces.

Refer to How Async Lines are Numbered in Cisco 3600 Series Routers for more information.

In order to overcome this limitation, Cisco 1800, Cisco 2800, and Cisco3800 series platforms now have a three-tiered interface numbering format (slot/subslot/port) for interfaces on WIC slots only.

Note: The slot information for the Cisco 3800 series is the same as the 2800/1800 interface and line numbering. See New Interface and Line Number Conventions for information on interface and line numbering.

New Interface and Line Number Conventions

This section describes the new conventions for interface and line numbering.

1. The interface numbering scheme is the same for async interfaces and non-async interfaces. To configure the line associated with an async interface, use the interface number to specify the async line.For example, line 0/0/0 specifies the line associated with interface serial 0/0/0 on a WIC-2A/S in slot 0. Similarly, line 0/1/1 specifies the line associated with interface async 0/1/1 on a WIC-2AM in slot 1.

   Note: This document uses the following words interchangeably:

   • Network-module-slot and slot.
   • Interface-card-slot and subslot.
2. Ports on network modules are numbered like this:interface-number = network-module-slot/port

   OR

   interface-number = slot/port

3. Ports on interface cards (such as WICs, VWICs and HWICs) installed directly in chassis slots is given here:interface-number = 0/interface-card-slot/port

   OR

   interface-number = 0/subslot/port

4. This numbering convention is used for ports on interface cards that are installed in network module slots:interface-number = network-module-slot/interface-card-slot/port

   OR

   interface-number = slot/subslot/port

   Note: The slot/subslot/port format only applies to WIC interfaces. Interfaces that are native to the network modules still use only the slot/port format. That is:

   • <interface-name> slot/port is used whenever the interfaces are native on the network module.
   • <interface-name> slot/subslot/port is used whenever the interfaces are on the WIC slot of a network module (NM).
5. Here is an example for numbering when the motherboard slot number is always 0. The native interfaces on the motherboard are numbered like this:
   • Fa0/0, Fa0/1 on Cisco 2811.
   • Gi0/0, and Gi0/1 on Cisco 2821 and Cisco 2851.

   The Motherboard WIC slots are numbered from 0 to 3. The number increments from right to left, and from bottom to top.

6. Slot numbers for other slots increase from bottom to top, then right to left. Subslot numbers and port numbers within a slot also increase from bottom to top, then right to left.

Examples

Interfaces native to an extension network module (ENM):

If the ENM carries WIC cards, the WIC slot numbers start from 0:

The extension voice module (EVM) slot analog interfaces are numbered from voice-port 2/0/0 to voice-port 2/0/23, following the NM-HDA convention.

Interface Numbering

This section lists the interface numbering details for Cisco routers.

Table 1 – Interface Numbering on Cisco 1841