This may interest some of you.
---------- Forwarded message ----------
From: ECS Seminar Notification <seminar-admin(a)ecs.vuw.ac.nz>
Date: Thu, May 10, 2012 at 10:56 AM
Subject: [ECS Seminars] Seminar by Foh Chuan Heng
To: ecs-seminars(a)ecs.vuw.ac.nz
Date: Wednesday 16th May 2012
Time: 10:00 AM - 12:00 PM
Location: Cotton Club, Cotton 350
Foh Chuan Heng is scheduled to present a seminar about:
Data Traffic Management in Data Center Networks
School of Engineering and Computer Science Seminar
Abstract:
The emerging of cloud computing has triggered the demand for large
data
centers. One of the key building blocks of data centers is the network
component. Data center networks have received considerable attention in
research in recent years with efforts focusing on transforming the
existing Ethernet technology to support data center networks. One key
missing feature in Ethernet for data center networks is the support of
lossless transmission. To address this shortcoming, a comprehensive data
traffic management is needed for Ethernet to operate in a data center,
and this need has prompted the creation of a number of standards
including IEEE 802.1Qbb for priority flow control, IEEE 802.1Qaz for
enhanced transmission selection, and also IEEE 802.1Qau for Ethernet
congestion management.
This talk presents our recent works on data traffic management in data
center networks. We first introduce two layer-2 solutions to combat
traffic congestion in data center networks. The first solution uses
multipathing technique to balance traffic and prevent congestion at
local links. When the offered load exceeds the network capacity, our
second solution offers controlling of traffic flows based on their
priority to avoid network-wide congestion. In layer-3, we introduce
multiple congestion points TCP specifically design for data center
environment. We show the significant performance benefit when multiple
congestion points can be detected in a data path. The talk concludes
with sharing of some ongoing works and preliminary results.
Short Bio:
Chuan Heng Foh (Ph.D, The University of Melbourne, 2002) is an Assistant
Professor at the School of Computer Engineering, Nanyang Technological
University (NTU) since December 2002. Priority to NTU, he was a lecturer
at Monash University for 6 months. Chuan Heng Foh is the author of 90
research papers and 1 patent. He is the Associate Editor of
International Journal of Communication Systems and guest editor of
International Journal of Distributed Sensor Networks, TPC member of many
mainstream IEEE conferences. His main research interests include
performances of computer networks, network coding, multimedia
transmission, cloud computing, and data center technology.
Any queries about this seminar, please email lindsay(a)ecs.vuw.ac.nz
=============================================================================
This message was automatically generated by the ECS Seminars System.
View seminars at http://ecs.victoria.ac.nz/Events/Seminars
Sub/unsub at http://ecs.victoria.ac.nz/mailman/listinfo/ecs-seminars
Racks need MORE COWBELL!!
Sent from my BEER LOCATING MOBILE DEVICE.
----- Reply message -----
From: "jamie baddeley" <jamie.baddeley(a)vpc.co.nz>
To: "Simon Paterson" <spaterson(a)woosh.com>
Cc: "NZNOG" <nznog(a)list.waikato.ac.nz>
Subject: [nznog] Beeping rack at Sky tower
Date: Tue, May 8, 2012 16:46
Don't fear the beeper.
Jamie
On 8/05/2012, at 11:22 AM, Simon Paterson <spaterson(a)woosh.com> wrote:
>
>> Greetings,
>>
>> It may be of interest to someone out there that rack 20-2 on Level 48 of the Sky Tower has an orange flashing light visible through the door and is emitting a beeping sound. The rack has a label on it reading "Mercury Tele".
>>
>> Cheers,
>> Tim
>>
> Hi,
>
> This is known about. The beepers will go away soon.
>
> Cheers,
> Simon
>
> _______________________________________________
> NZNOG mailing list
> NZNOG(a)list.waikato.ac.nz
> http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________
NZNOG mailing list
NZNOG(a)list.waikato.ac.nz
http://list.waikato.ac.nz/mailman/listinfo/nznog
Greetings,
It may be of interest to someone out there that rack 20-2 on Level 48 of the Sky Tower has an orange flashing light visible through the door and is emitting a beeping sound. The rack has a label on it reading "Mercury Tele".
Cheers,
Tim
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS18015
descr: advertised to AS9439 by Fastcom Limited - AS18015
members: 180.189.192.0/19^19-29,
124.150.160.0/20^20-29,
182.236.120.0/21^21-29,
103.2.120.0/22^22-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: daniel.kinross(a)fastcom.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20111211
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS18015
descr: advertised to AS9439 by Fastcom Limited - AS18015
members: 180.189.192.0/19^19-29,
49.50.240.0/20^20-29,
124.150.160.0/20^20-29,
182.236.120.0/21^21-29,
103.2.120.0/22^22-29,
103.6.28.0/22^22-29,
103.6.144.0/22^22-29,
113.21.224.0/22^22-29,
60.234.40.0/23^23-29,
60.234.67.0/24^24-29,
60.234.68.0/24^24-29,
60.234.71.0/24^24-29,
60.234.72.0/24^24-29,
60.234.75.0/24^24-29,
60.234.127.0/24^24-29,
103.6.212.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: daniel.kinross(a)fastcom.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20120508
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS38477
descr: advertised to AS9439 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
103.11.124.0/22^22-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
202.44.60.0/22^22-29,
122.102.108.0/23^23-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
103.246.250.0/24^24-29,
131.203.133.0/24^24-29,
192.138.251.0/24^24-29,
202.50.102.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20111130
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS38477
descr: advertised to AS9439 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
103.8.232.0/22^22-29,
103.11.124.0/22^22-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
202.44.60.0/22^22-29,
122.102.108.0/23^23-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
103.246.250.0/24^24-29,
131.203.133.0/24^24-29,
192.138.251.0/24^24-29,
202.50.102.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20120502
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS24388:RS-ROUTES:AS38477
descr: advertised to AS24388 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
103.11.124.0/22^22-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
202.44.60.0/22^22-29,
122.102.108.0/23^23-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
103.246.250.0/24^24-29,
131.203.133.0/24^24-29,
192.138.251.0/24^24-29,
202.50.102.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20111130
source: NZRR
REPLACED BY:
route-set: AS24388:RS-ROUTES:AS38477
descr: advertised to AS24388 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
103.8.232.0/22^22-29,
103.11.124.0/22^22-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
202.44.60.0/22^22-29,
122.102.108.0/23^23-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
103.246.250.0/24^24-29,
131.203.133.0/24^24-29,
192.138.251.0/24^24-29,
202.50.102.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20120502
source: NZRR
------------------------------------------------------------
Hoping someone on the right side of the tasman can help out with some advice
I have a customer wanting to put some OOB equipment into a new POP at skytower auckland. Back here in Aus they've generally used a 3g connection.
1) Is there reasonable 3g access in skytower? are there any restrictions on cell/3g use?
2) Anyone recommend a pre-paid data service (NZ telecom, vodafone or other provider?) for say 12 months?
Thanks in advance.
Brendan Baker
Suite 44, 2 Benson St, Toowong, Qld 4066. Australia
T: +61 7 3871 1800 | F: +61 7 3720 8289 | M: +61 407 034 742
brendan.baker(a)opengear.com | www.opengear.com.au
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS17746
descr: advertised to AS9439 by Orcon - AS17746
members: 60.234.0.0/16^16-29,
121.98.0.0/16^16-29,
156.62.0.0/16^16-29,
202.150.96.0/19^19-29,
202.126.192.0/20^20-29,
202.191.32.0/20^20-29,
219.88.128.0/20^20-29,
219.88.240.0/20^20-29,
116.193.144.0/21^21-29,
116.199.208.0/21^21-29,
202.3.88.0/21^21-29,
202.49.64.0/21^21-29,
210.54.56.0/21^21-29,
103.3.232.0/22^22-29,
113.21.224.0/22^22-29,
202.127.8.0/22^22-29,
210.54.148.0/22^22-29,
210.55.12.0/22^22-29,
120.138.22.0/23^23-29,
202.27.76.0/23^23-29,
202.36.230.0/23^23-29,
202.37.82.0/23^23-29,
202.175.142.0/23^23-29,
192.203.216.0/24^24-29,
202.0.151.0/24^24-29,
202.12.104.0/24^24-29,
202.27.8.0/24^24-29,
202.36.12.0/24^24-29,
202.36.174.0/24^24-29,
202.36.198.0/24^24-29,
202.37.19.0/24^24-29,
202.37.78.0/24^24-29,
202.37.173.0/24^24-29,
202.46.189.0/24^24-29,
202.49.140.0/24^24-29,
202.49.233.0/24^24-29,
202.49.246.0/24^24-29,
202.50.164.0/24^24-29,
202.50.246.0/24^24-29,
202.129.253.0/24^24-29,
210.54.12.0/24^24-29,
210.55.199.0/24^24-29,
202.27.188.128/25^25-29,
210.55.0.0/25^25-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: robert.keightley(a)team.orcon.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20120329
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS17746
descr: advertised to AS9439 by Orcon - AS17746
members: 121.98.0.0/15^15-29,
60.234.0.0/16^16-29,
114.23.0.0/16^16-29,
156.62.0.0/16^16-29,
123.100.64.0/18^18-29,
124.198.128.0/18^18-29,
180.189.192.0/19^19-29,
202.89.32.0/19^19-29,
202.150.96.0/19^19-29,
49.50.240.0/20^20-29,
112.109.64.0/20^20-29,
116.199.208.0/20^20-29,
119.47.112.0/20^20-29,
202.126.192.0/20^20-29,
202.191.32.0/20^20-29,
219.88.128.0/20^20-29,
219.88.240.0/20^20-29,
112.109.80.0/21^21-29,
124.150.160.0/21^21-29,
182.23.176.0/21^21-29,
202.3.88.0/21^21-29,
202.49.64.0/21^21-29,
202.175.128.0/21^21-29,
210.54.56.0/21^21-29,
103.3.232.0/22^22-29,
103.6.144.0/22^22-29,
110.44.16.0/22^22-29,
113.21.224.0/22^22-29,
116.193.144.0/22^22-29,
202.14.20.0/22^22-29,
202.36.8.0/22^22-29,
202.49.244.0/22^22-29,
202.127.8.0/22^22-29,
210.54.148.0/22^22-29,
210.55.12.0/22^22-29,
210.55.100.0/22^22-29,
210.55.104.0/22^22-29,
116.193.148.0/23^23-29,
120.138.22.0/23^23-29,
124.150.170.0/23^23-29,
143.96.2.0/23^23-29,
143.96.4.0/23^23-29,
182.236.122.0/23^23-29,
182.236.124.0/23^23-29,
202.14.82.0/23^23-29,
202.27.76.0/23^23-29,
202.36.198.0/23^23-29,
202.36.230.0/23^23-29,
202.175.142.0/23^23-29,
210.54.12.0/23^23-29,
210.54.142.0/23^23-29,
103.2.121.0/24^24-29,
103.6.212.0/24^24-29,
116.193.151.0/24^24-29,
120.138.31.0/24^24-29,
124.150.168.0/24^24-29,
124.150.172.0/24^24-29,
182.236.121.0/24^24-29,
192.88.190.0/24^24-29,
192.203.216.0/24^24-29,
202.6.5.0/24^24-29,
202.12.104.0/24^24-29,
202.14.84.0/24^24-29,
202.14.217.0/24^24-29,
202.27.8.0/24^24-29,
202.27.204.0/24^24-29,
202.36.12.0/24^24-29,
202.36.70.0/24^24-29,
202.36.174.0/24^24-29,
202.36.227.0/24^24-29,
202.36.233.0/24^24-29,
202.37.72.0/24^24-29,
202.37.78.0/24^24-29,
202.37.173.0/24^24-29,
202.37.181.0/24^24-29,
202.37.232.0/24^24-29,
202.46.187.0/24^24-29,
202.46.189.0/24^24-29,
202.49.59.0/24^24-29,
202.49.140.0/24^24-29,
202.49.216.0/24^24-29,
202.49.233.0/24^24-29,
202.50.164.0/24^24-29,
202.50.176.0/24^24-29,
202.50.246.0/24^24-29,
202.129.253.0/24^24-29,
202.175.137.0/24^24-29,
202.175.138.0/24^24-29,
203.6.246.0/24^24-29,
203.97.42.0/24^24-29,
210.55.5.0/24^24-29,
210.55.169.0/24^24-29,
210.55.199.0/24^24-29,
210.55.214.0/24^24-29,
210.55.230.0/24^24-29,
203.167.219.56/29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: robert.keightley(a)team.orcon.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20120501
source: NZRR
------------------------------------------------------------
Hello everyone,
I know most posts to this list are more technical than philosophical but
I thought this question might be relevant to the list.
Many of you are probably in charge of operations for a company and I was
wondering how people approached the day to day running of their ICT
teams.
I am currently studying ITIL foundations which attempts to help you
develop a frame work that fits your company. Has anyone else found this
useful?
Some points of interest:
- Standard operation procedures
- Escalation processes
- Incident and resolution reports
- How do you monitor? Do you monitor everything and sort
through it? Or do you focus on machines/hardware or do you focus on the
service?
- Are there any third party auditing frameworks you strive to
match like SAS70/SSAE/PCI? Is it worth it
- How do you report failures/targets/capacity to the business?
- How do you see Ops teams in 5-10 years?
Gareth Davies
Systems Administrator - Web Applications
DD +64 9 574 0123 EXT 8465
www.fphcare.com
____________________________________________________________
This e-mail and any attachments may contain confidential information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
