When you are configuring ExtremeZ-IP as a print server, you will need to set up and configure each printer. However, if you already have setup and configured printer queues for the Windows server, you can import existing queues into ExtremeZ-IP. This can be done programatically via the ExtremeZ-IP EZIPUTIL command line tool. EZIPUTIL has a number of options, whereby the SERVER option is used to configure global settings for ExtremeZ-IP, VOLUME is used to create, edit and delete print queues and PRINT is used to manage shared print queues. Each of the options also has a number of switches for the feature(s) that are being managed. These are structured as…
-
-
Will Any Old GBIC Work?
You have two switches and you’re thinking that you’ll use the GBIC from your old switch on you new switch. You have an Xsan and you have a bunch of GBICs laying around and you want to know if they’ll work. You have a fiber run and you want to use a transceiver. Etc. This is a tricky question. The GBICs should all work. The general rule of thumb though is, if you use the same GBIC on both ends then you shouldn’t have a problem. But, it’s also important that (for whatever reason) some manufacturers do require certain GBICs either to actually interface or just to support an interface.
-
The Changing Mac Switching Infrastructure
No one ever got fired for buying Cisco. But, I recently saw a shop where they went from Cisco to Enterasys (thanks for showing off your backbone Todd). I must say that I really liked the Enterasys switches. I looked them up and they are about 1/2 the cost of Cisco. They have great tech support and are very easy to configure, even though it’s a command line interface. The only complaint I have about them is the web interface is good for reviewing your setup but inadequate for configuration – but is good for looking at the switch configs. Maybe in time this will mature… I don’t know if they can go to the 10,000+ environments…
-
Extreme BlackDiamond 8800 – BAM!
Extreme core switch http://www.extremenetworks.com/products/blackdiamond-8800.aspx
-
Designing the Switch Infrastructure
The functional layers for swiching environments in the Data Center are often architected around three layers, commonly referred to as The Cisco Three-Layered Hierarchical Model: The Core Layer connects the Aggregation Layers. Typically, the Core Layer utilizes high performance low latency Layer 3 switches (often 10 gig Ethernet and/or 10 gig fiber). The Aggregation Layer provides services, such as Load Balancing and SSL Optimization. Access Layer switches typically use the Aggregation Layer for connecting to the Core Layer. The Access Layer includes the hubs and switches that connect client systems.
-
Xsan: Metadata Network
Xsan needs an out-of-band metadata network. This network is used to transfer information, or metadata on files being written to the SAN. The metadata network on an Xsan should be low latency. Nothing should potentially interfere with the transfer of data. Therefore, make sure that you disable all the management features of your switch. But make sure it’s a good switch. I prefer to use a managed switch, disabling all the management features.