Dell Service Tag

If you have Dell servers, and the service tag isn't set in BIOS for whatever reason (motherboard replacement and etc), you can use this tool to update the service tag.

Found this post in the Dell community forum on how to do this:

http://en.community.dell.com/support-forums/servers/f/956/p/19101767/19226362.aspx

You can use the Asset tag utility to do this. There are hidden switches to asset.com to change the service tag.
ASSET.com version 2.09 from the resource CD would be the likely candidate.

ASSET 209 Asset Version 2.09
Release Title: System Utilities:
Dell Asset Utility, Utility, English, Multi System, 2.09
Release Date: 09/27/2005
Description: Asset Utility
http://support.dell.com/support/downloads/download.aspx?c=us&cs=19&l=en&s=dhs&releaseid=R109071&formatcnt=1&fileid=141647

boot from dell resource CD
choose "Q" to quit the diagnostics and go to command prompt
navigate to "asset209.exe" tools
cd csd\tools\bios
run "asset209.com"

Usage:
ASSET new_asset_tag Specify new asset tag
ASSET /d Delete asset tag
ASSET /o new_owner_tag Specify new owner tag (if applicable)
ASSET /o /d Delete owner tag (if applicable)
ASSET /? This help screen

Hidden Options:
ASSET /s new_service_tag Specify new service tag
ASSET /s /d Delete service tag
ASSET /b Specify new system board tag
system board tag must be "ssssssssssssssssssss-vvv-", where
s..s is the 20 digit system board Part number string,
vvv is the 3 digit system board rev,
- is a don't care character, but must be present
ASSET /b /d Delete system board tag
ASSET /f [other_options] Force Affirmative response
ASSET /x [other options] eXtended display - displays all tags

Another Option would be the DCCU:
Release Title: System Utilities:
Dell Client Configuration, Utility, Windows 2000, Windows XP, English, v.1.1.111.0, A00
Release Date: 02/13/2004
Description: The Dell Client Configuration Utility (DCCU)
is a tool for managing Dell clients through BIOS updating,
shutdown/restart, asset/inventory reporting, and SMBIOS,
CMOS and OS parameter setting.

http://support.dell.com/support/edocs/software/smdccu/

ftp://ftp.dell.com/utility/R73202.EXE

http://www.dell.com/downloads/global/solutions/dccu_infobrief.pdf

UPDATE:

It looks like the tool is also available in the "Dell 32 Bit Diagnostics" kit: http://support.us.dell.com/support/downloads/format.aspx?releaseid=R247886&c=us&l=en&cs=19&s=dhs

You can find it in the driver download page for your specific model. Get the non-GUI version.

You create a boot media (floppy, USB key, CD..) with that tool, and you boot the server with it. Once booted you select #4 on the menu, which will drop you off into a DOS environment.

Navigate to c:\util (at least thats where it is for USB boot media), and asset.com is in there. Just use the switches above to do whatever you want.

SNMP for Cisco devices

Here a quick tip getting SNMP data off a Cisco device. You can get the MIBs, search by OID and even search by description using this web tool on Cisco.com. I wish every vendor have such a thing.

http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en

D-Link Internal Routes

We all know that D-Link is lacking in some important features, as most home routers are. But an important feature to any router is the ability to uhhh "route". D-Link does not allow the feature of routing to for your LAN on some of their routers only allowing you to select the WAN option.

This can be bypassed by adding the following lines into the address bar to change the routing information incase you want to route in your internal network.

Here are the Steps:

1. Log into the router
2. Go to Advanced>Routing and paste the following in the URL with the information you need

http://192.168.0.1/Advanced/Routing.shtml?config.route_table[0].enabled=true&config.route_table[0].used=1&config.route_table[0].entry_name=MediaShare&config.route_table[0].dest_ip=X.X.X.X&config.route_table[0].metric=1&config.route_table[0].dlink=LAN&config.route_table[0].subnet=X.X.X.X&config.route_table[0].gw=X.X.X.X

Note: The number in the brackets represent which row you wish to change. The other information to configure should be self explanatory such as: Subnet, gw=Gateway, dest_ip=destination IP etc.

CPU temp and scaling in Linux

To see your processor temperature in linux, you need the lm-sensor package:

apt-get install lm-sensors

Then you need to setup the sensors specific to your machine:

sensors-detect

It scans your system, accepting the default is pretty safe. Follow instructions at the end to load the required modules for your sensors

benedict@benedict-laptop:~$ sudo sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: Dell Inc. Inspiron 910

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
Intel Core family thermal sensor... No
Intel Atom thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7
Module i2c-i801 loaded successfully.
Module i2c-dev loaded successfully.

Next adapter: intel drm CRTDDC_A (i2c-0)
Do you want to scan it? (YES/no/selectively):

Next adapter: intel drm LVDSDDC_C (i2c-1)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `coretemp':
* Chip `Intel Atom thermal sensor' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/module-init-tools start'
to load them.

Unloading i2c-dev... OK
Unloading i2c-i801... OK


Then run 'sensors':

benedict@benedict-laptop:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +58.0°C (crit = +102.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +40.0°C (crit = +90.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +40.0°C (crit = +90.0°C)


Chances are, your linux distro are already doing frequency scaling, you just want to see how its doing. You need the cpufrequtils package.

Then run cpufreq-info to view the current freq and other relevant info:


benedict@benedict-laptop:~$ cpufreq-info
cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 1.60 GHz
available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 800 MHz and 1.60 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.60 GHz:18.06%, 1.33 GHz:0.81%, 1.07 GHz:1.00%, 800 MHz:80.12% (2083337)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 1.60 GHz
available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 800 MHz and 1.60 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
cpufreq stats: 1.60 GHz:2.42%, 1.33 GHz:0.12%, 1.07 GHz:0.12%, 800 MHz:97.33% (139908)


That's all!

Note to self: format this... learn how to use Blogger.