It’s the networks fault #3
0I’m still alive and well just been super busy over the past few months. I’m just about to start deploying our second data center utilizing Cisco Nexus 7010, 5010, and 2248s. This time around we’ll be utilizing a Ciena 5200 DWDM platform (formerly Nortel) managed by AboveNet to provide 4 10Gbps wavelengths between our primary and secondary data center. We’ll use 2 for our SAN and 2 for our MAN over which we’ll probably utilize vPC. On top of that huge project we’re physically relocating our offices (former Data Center) so I also need to plan all that work as well.
Ethernet Routing Switch 8600 Software Release v7.1.3.2
Avaya has released software v7.1.3.2 for the Ethernet Routing Switch 8600/8800.
- Every 5 seconds, on a timer, the CPU sends the clock time to all the line cards. A timer was created each time a card came online, so when there are multiple IO cards, multiple messages were sent every 5 seconds to all cards. Eventually a lockup resulted, and when it was detected by the CPU, the chassis was reset. (wi00996291)
Please refer to the release notes for all the details.
Motorola RFS7000 WiNG v5.2.21 Software Release
You may also want to review software release 5.2.3 and 5.2.4 before deciding to check out software release 5.2.21 which was intended to resolve several MESH issues with the AP7131.
RFS Controllers with WiNG v5.2.21 can adopt and provision the following 802.11n and legacy Access Points:
Dependent Access Points:
- AP621
- AP650
- Legacy: AP300
Adaptive/ Independent Access Points:
- AP6511
- AP6521
- AP6532
- AP7131 (Including the D-mode SKUs)
- AP7161
You should check over the release notes for all the details.
Cheers!
It’s the networks fault #2
3Ethernet Routing Switch 8600 Software Release v7.1.3.1
Avaya has released software v7.1.3.1 for the Ethernet Routing Switch 8600/8800.
- L3VSN default route was not correctly installed in the RTM when it was received via ISIS. As a result L3VSN traffic that needs to use the default route was being dropped. This problem is specific to L3VSN only. It did not affect GRT default routes via ISIS. (wi00996566)
Please refer to the release notes for all the details.
Avaya IP Softphone 2050 Release 4.3
Avaya has released the IP Softphone 2050 Release 4.3.081 for Microsoft Windows.
There is specific mention of support for 64bit versions of Microsoft Windows 7 and Microsoft Windows Vista;
Important Note : It is strongly recommended to install the next updates for Microsoft Windows 7 to the PC
including the specific updates noted below. Failure to install these Windows 7 updates may cause the
2050 IP Softphone to crash or not work as intended.
KB981679 (part of Service Pack 1 for Windows 7)
KB979303
The following issues are resolved;
- wi00715416 External – Improved robustness of Licensing Server in releasing licenses, if IP Connection drops
- wi00903652 External – Issue with node-locked licensing not working with CS1000 R7.5 and 2050 R4.2
wi00906095 - wi00867565 External – Error message when starting IP Softphone on Windows 7™
- wi00908928 External – Graphics issue on Windows 7™
- wi00896132 External – Dual stream recording does not work properly with 2050 after a call is transferred to the 2050
- wi00951184 External – 2050 reverts to PC speaker and soundcard instead of USB device when PC is restarted
- wi00889263 External – SR 1-1462175541: IP Softphone trace route shows only final destination, not intermediate hops.
Please refer to the release notes for all the details.
Cheers!
CentOS 6.2 KVM – VirtIO paravirtualized drivers for Windows
0I’ve just recently been playing around with KVM on a HP DL360 running CentOS 6.2 x64. I had a very difficult time finding the VirtIO paravirtualized drivers for Windows in a virtual floppy format (vfd). I was looking for the vfd format so I could easily install the drivers in a Windows XP guest I was building and testing.
I’m going to post a link here to the file, not quite sure why it was pulled from RedHat’s site.
virtio-win-1.1.16.vfd (MD5SUM: 7437f5d81fc43e8da3be01802fa4e9fb)
Cheers!

