Joffer's Notepad

I found this blogpost about MDT 2013 and handling drivers.. I might have to check it out later in a lab environment. In MDT 2013 (Lite Touch), there are two types of drivers to worry about when deploying Windows. There are drivers for Windows PE 5.0 (the boot image) and there are drivers for the Windows Operating System that you deploy.   Driver management for the boot image is pretty straight , but driver management for the Operating Systems that you deploy is more complex. The real answer is it depends… To simplify I have broken down drivers for the Windows Operating system in to three core scenarios (see later in this post). But first, let’s start with the boot image drivers. Link: http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management

Spanning-tree Loop Troubleshooting and SafeGuards Configuring Root Guard & Loop Guard BPDU Guard, BPDU Filter, Root Guard, Loop Guard & UDLD What Is the Difference Between STP BPDU Guard and STP Root Guard? Of course there are more technical and in depth articles at sites such as Cisco.com ( here , here , here , here  etc.) and others. Google is your friend :-)

According to an article over at  scottlowe.org , the  'the [Intel Xeon] E5 processors integrate PCI Express root ports, providing upwards of 200 Gbps of throughput. This is compared to the use of the “Southbridge” with the 5500/5600 series CPUs, which were limited to about 50 Gbps.' Later you can read you should use specific slots on the motherboard for 10GbE PCIe NICS (and probably other high throughput cards): Going back to the earlier discussion about PCIe root ports being integrated into the E5 CPUs, this leads to a consideration for the placement of PCIe cards. Make sure your high-speed cards aren’t inserted in a slot that runs through the C600 chipset southbridge. Make sure that you are using Gen2 x8 slot, and make sure that the slot is actually wired to support a x8 card (some slots on some systems have a x8 connector but are only wired for x4 throughput). Johnson recommends using either LoM, slot 2, slot 3, or slot 5 for 10 GbE PCIe NICs; this will ensure direct co...

If you keep getting eth1 instead of eth0 as your main ethernet interface on a (newer) linux template/clone in a virtualized environment it's most likely because your udev rules is in affect and creates a new eth1 since eth0 is already defined and bound to the clone/template source's MAC address. This can be fixed in a couple of ways (in your template/clone source image): 1) You can delete the ' SUBSYSTEM ' line in your  /etc/udev/rules.d/70-persistent-net.rules : Edit the rules files   vi /etc/udev/rules.d/70-persistent-net.rules Delete the SUBSYSTEM line(s), feel free to also delete the comment about PCI device just above: # This file was automatically generated by the /lib/udev/write_net_rules # program, run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single # line, and change only the value of the NAME= key. # PCI device 0x8086:0x100e (e1000) SUBSYSTEM=="net", ACTION==...

De to vanligste måtene å tunnelere IPv6-trafikk over IPv4 er "6in4" og "Teredo". Den førstnevnte pakker ned IPv6-pakkene i IPv4-pakker med protokollnummer 41. For å blokkere denne typen kommunikasjon holder det å blokkere IP-protokoll 41 i routere og brannmurer. For å blokkere Teredo-trafikk holder det normalt å blokkere port 3544/UDP i utgående retning. Source: http://telenorsoc.blogspot.com/2010/04/den-kommende-ipv6-protokollen-og.html