o2 homebox

read access

1. In die o2 Box (http://o2.box/) (Router Arcadyan IAD4421, ARE 6431) login and download the config.bin: “System” -> "Save settings" -> "Save Configuration".
2. Tool “Arcadyan IAD Decrypter” download (arcadyan_decrypter_v0.04.zip) and extract.
3. Microsoft “strings” download, so unpack and head off on the bin file folder.
4. Run the batch, which belongs to the box. (decrypt_o2_box_6431.bat)

In the o2box6431_strings.txt exists:
PPPoE1 -> Standing here login, these also apply for VoIP.
PPPoE2 -> If only something, these are the data for Internet access with VLAN 7. Danger: If it is not a T-COM VDSL resale Adapters applies VLAN ID = 11.

search

$NOTIFY
$PROXY
sip.alice-voip.de
sip.alice-voip.de
sip.alice-voip.de

sip.alice-voip.de
49XXXYYYYYY
49XXXYYYYYY
0XXXYYYYYYbb45

configure VoIP:

Internetrufnummer = 49XXXYYYYYY
Username = 49XXXYYYYYY (identical)
Password = 0XXXYYYYYYbb45
Register = sip.alice-voip.de

In the FritzBox Telephony menu! there is a list of other providers. When you interrupt “My numbers” on “new” followed by a wizard of it one makes the Internet phone book.

Automatic configuration of SIP

Connects to your Fritzbox (note enclosed instructions) and go to the configuration page via http://fritz.box / or 192.168.178.1
Now follow the Wizard - For the DSL connection is the Internet Service Provider "O2 DSL" to use, the username is your (Head-)Phone number and password does not exist; give anything here. - If the data is not correct just call o2 and ask for your DSL access. These give them out in contrast to the VoIP data.
Now go to the left menu click "System" and then on the sub-item "Update" - Ensures that its latest FRITZ!OS version for your Fritzbox have - Should this not be the case you have to update this
Now it may happen quickly or take some. Via the "Telephony" and then the sub-heading "Own numbers" should be in the foreseeable future your numbers be listed (the page must be manually updated!). These are accessed by o2 and automatically set.
If your numbers but be not set up after ten minutes patience, you have to disconnect your Fritzbox the current now. After a minute, you can connect this again. After the Fritz box is now completely started and did you logged back on the configuration page, should now your numbers exist.

Utilities Forum:
http://www.ip-phone-forum.de/showthread.php?t=159016

sources:
http://www.randnotizen.org/fritzbox-7490-an-o2-anschluss/
http://netfreak.dynpc.net/netfreak/index.php/it-und-technik/469-zwangsrouter-ersetzen

Bad RAID controller

IMG_26022014_084034

If you have a UCS chassis where the VMs go offline and you can’t access the VMs with vSphere, you may have to reboot the chassis via the IMC web interface. But, when you reboot it and watch it via the IP KVM console, this is what you don’t want to see:

OK, so get TAC on the phone and have them send you the replacement controller. Hopefully, you have 4 hour response. Here is the link to replace the RAID controller in the UCS chassis:
After replacing the RAID controller, you will want to make sure to copy the drive configuration to the newly replaced controller. This was not documented in the card replacement documentation. Here is the link to do this. Follow the instructions EXACTLY:
Verify the virtual devices show up on the RAID controller during bootup. Things still might go south. The vSphere client may show CUCM and UCXN as missing. This is because the datastores are not there. TAC will need to re-add the datastores for you, possibly via CLI. More than likely, the file system will have errors on the VMs. It may be so bad that the won’t boot, so you will need to mount the Recovery CD, boot to it, then choose the option to fix the file system errors. After that, grab a beer. The servers should come up just fine.
see -> http://iptbuzz.blogspot.de/2011/10/bad-raid-controller-on-ucs-c210-m2.html

Netwerkverkabelung in the old building

In my view, the best cabling is a mixture of all 3 opportunities and this, in the following order:

1. copper cabling
2. Power Line
3. WLAN

Powerline

8861_addition

speed:
up to 260 Mbit/s

Pro:
– No installation work
– using existing wiring

against:
– Slower
– More prone disorder
– Expensive when purchasing
– abhörbar / uncertain
– can not be used over several floors mostly

WLAN

AmTV-bdd13efb6e491b16

speed:
up to 300 Mbit/s

Pro:
– No laying of cables
– Flexiebler Arbeitsplatz

against:
– Many users relatively slow
– fault-prone
– High cost

 

copper / ROLLING

I recommend volgendes tape -> tesa POWERBOND® INDOOR mounting tape for indoor use (5 m x 19 mm)

attachment

41nNzZy-FrL

speed:
up to 10 Gbit / s

Pro:
– Fast
– Current standards
– For sure
– fix Flat cable per tape everywhere
– Can be fixed with Heiskleberpunkten
– Can under / are placed next to doors
– PoE capable

against:
– Verlgearbeiten in the old building
– No flexible jobs

Mini / analyze DUMP file

To open the DUMP file you will need a corresponding debugging tool, which you can download from Microsoft:

Download (11,3 MB): http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.4.7.2.exe

After you install the program, you can use the debugger “Start” -> “Programme” -> “Debugging Tools for Windows” -> “WinDbg” start.

In order to really make sense to work with the debugger, are also the so-called. Symbol files needed. Since the full but with ca. 170 beat MByte to book, they but certainly want to evaluate such dump files not daily, should you choose to prefer, that WinDbg itself the necessary files from the Internet brings.

To Make for a:

in the menu “File” -> “Sybol File Path” enter them in the input box:

SRV*C:Symbols*http://msdl.microsoft.com/download/symbols

Then open the program the dump file from the directory “%SystemRoot%Minidump” about “File” -> “Open Crash Dump”

Now the file is loaded and the information displayed. Two windows are opened “Command” and “Disassembly”. The window “Disassembly” you can quietly close again, because their evaluation but already presupposes considerable programming skills.

The “Command”-usually already quite window contains valuable information on the other hand. The interesting information, see:

***************************

* Bugcheck Analysis *

***************************

Find e.g.: Behind “BugCheck” an error code. This error code you can then also search the Microsoft Knowledge Base (http://support.microsoft.com/search/) use. If the error code known, You find here most accurate information to, which driver caused this problem and often appropriate solutions.

but you can also in the debugger already more determined about this error code. Enter it in the command window, type the command “!analyze -v” on.

Then a lot of information is output; Here is the first line in the written word Capitals, representing the type of error.

If you still need further information in the help, enter in the Command window “.hh [The Word in uppercase]” on.

Furthermore, you can find the line “Probably caused by” (= Error caused by:). This indicates, which file has probably caused the error. With this file you can also restart a relevant search on the Internet.

If you have a file name, itself can also be in the Command window can display more information to. The command “lm v m[filename]” get more info. Here, the file name must be entered without extension. The file name is directly, right behind the parameter m (without space) entered.

The command “!devnode 0 1” can you can still print a list of all loaded drivers.

Come therefore not, If you would like the command “!thread” in the Command window, Show more information. Find in the output line “IRP List”, then you should seek out more information about the addresses. For this purpose call the command “!irp [Addresse]” on. In the collection you find driver name, were involved in the error.

For information about errors and debugging can be found at:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/ddtools/TOC_Debugging_b61a3911-d5dc-42de-96af-deb0d7df233b.xml.asp?frame=true

If you get stuck by you and such requests in forums, etc.. want to make, You should always see everything from section “Bugcheck Analysis” to pass on information as.

(Those) winfaq