Posts Tagged ‘2000’

FEX configs are retained

Monday, February 15th, 2010

The N5k maintains the config of the FEXs, even when they’re removed (and even though it’s not visible to us). In this article, we’re going to look into this a little further… We’ll start with a working FEX, using Po100 (with Eth1/19-20 being the physical bundle members). (more…)

The FEX information is cached until it’s re-assigned to a different FEX

Tuesday, February 2nd, 2010

Continuing our journey into the world of FEXs on the Nexus 5000 and 2000, today we’re going to look at the behavior of the FEX configs themselves on the Nexus 5000.

All of the configuration and software information (firmware/images) for the FEX (Nexus 2148T) are kept on the parent switch (a Nexus 5000-series switch). Going on this, what happens when the FEX goes offline? Do I lose my config?

A stack of 3750 switches can be provisioned ahead of time, so that as stack members are added (assuming that they’re the correct type/model), no changes must be made – just move on. What kind of behavior is available on the Nexus 5000/2000?

I haven’t found provisioning available yet for FEXs on the N5k, however I did notice that the configurations for the FEX are retained when the FEX goes offline and online. This is great — if the 2148T fails or the fabric interface links are disconnected, the config will still be there (although not visible until the FEX comes back online). This article is looking at it from an association perspective (N2148T association with the N5k, not a configuration (actual port configs on the FEX). With that said, let’s explore this further… (more…)

What happens when the wrong serial number is entered for the FEX?

Sunday, January 31st, 2010

Continuing on the journey of FEXs on the Nexus platform, we’re exploring about serial numbers being statically bound to an FEX instance. It’s possible to allow any N2148T to connect to any FEX instance defined on a N5k. Simply plug in the N2k and off it goes.

This is a good low-maintenance approach, but what if I want to be more granular? What if I have several N2ks and I want to ensure that each N2k is plugged into the correct interfaces on the N5k? The only way to verify this is to tie a serial number to the FEX ID on the N5k, which will only allow that single N2k to come up on that FEX ID… or will it? What happens if the wrong serial number is entered?

Methods for connecting FEXs

Friday, January 29th, 2010

If you’re wondering what an FEX is, check out this article:

FEXs are connected to the parent switch(es) via fabric interfaces.  These are 10Gbps interfaces which connect the two switches (think of a stacking cable on a 3750-series switch).

There are two methods of configuring fabric interfaces:

  • Static pinning
  • EtherChannels

Although these are somewhat differentiated in some of the documentation, the static pinning looks almost the same as that used for EtherChannels.  The main difference is that static pinning uses physical interfaces, whereas EtherChannel uses a single Port-Channel interface for the fabric interface (there are some minor configuration differences and requirements as shown below).


NT/2000 Event Log Archiver & Viewing System

Wednesday, February 23rd, 2005

OBSELENCE NOTE: This was written well over a year ago, so may be outdated (ie. may have broken links — if so, let me know and I’ll update).  Just because it’s old doesn’t mean that it’s not worth sharing!


There are lots of products out there that allow you to remotely view your NT/2000-based event logs.  Not many of these allow for an archival and later viewing of these events.  If you look for something free, it really narrows the field down — so I wrote a program that would archive NT/2000 event logs to a SQL database.

After I had them archived, I noticed that my SQL database was really filling up fast.  I decided to code the ability to export certain events from the SQL DB to an XML file, allowing the file to be burned to a CD/DVD for archival.

Well, now I’ve got a 600MB XML file, and no way to view it.  Naturally, I wrote a program that would view and print the XML file as if you were looking directly at the NT/2000 event log itself.

Obviously there are several pieces to the big picture:

  1. The archiver (reads event log entries – stores them in the SQL DB – exports events to XML file).
  2. The viewer (reads XML file for viewing/printing).
  3. The SQL DB (plan on having a lot of space taken up by these logs).

NOTE: You need to have the MS XML parser installed on the machine that you run any of the first two above programs on to have them work.  If you’re looking for the MS XML Parser 4.0 SP2, go to


Online Requisition System (ORS)

Thursday, January 13th, 2005

OBSELENCE NOTE: This was written well over a year ago, so may be outdated (ie. may have broken links — if so, let me know and I’ll update).  Just because it’s old doesn’t mean that it’s not worth sharing!



This is a requisition and PO management system that I built.  The ORS interfaces with Meditech’s data repository (DR) to provide accurate shipping and status from the Meditech system itself (assuming that your site has Materials Management (MM)).  The system could still be used if you don’t have Meditech, but quite a bit of the code would have to be modified (it was originally designed to tightly integrate with Meditech).

Each user is authenticated against a Windows NT/2000 domain.  Group permission can be setup by the NT group that the user is a member of (mapping NT groups to the appropriate ORS groups requires a manual initial mapping).  There are system-wide limits for how much can be ordered without a super-user’s signature, etc.

Another added bonus for this system is the digital signature component’s integration with digital tablets.  I chose to use the ePad tablets (when originally designed, the only ePad tablets around were serial-based — you could probably get by using the USB just as easily).  The only catch is that the proper Windows drivers must be configured on the workstation that has the ePad for the digital signature piece to work properly (digital signatures need only be received from super-users — people who approve purchases over set limits within the system).

For more info, read over the docs below (go to the downloads section below).


Windows 2000/2003 Directory Services Audit Logging Management Utility

Thursday, January 13th, 2005


There’s a way to get very detailed event logging features for core Active Directory services.  Unfortunately, there’s no GUI for doing this — you have to dig in the registry to do it.  This can be cumbersome if you’ve got a list of servers to monitor/diagnose.  This tools allows you to specify a server, select which Active Directory service to log and what logging level it should be set at.

See;en-us;314980&sd=tech for more information on the registry keys and values.