Transcript 没有幻灯片标题 - Institut Teknologi Bandung

Thoughts on TEIN2
Operation and Collaboration
Xing Li
<2005-08-23>
Outline

Background

Experience

TEIN2 NOC

Challenges

Remarks
Background
EU
North America
(via TransPAC2)
JP
622
KR
CN
tba
622
622
Approved
TEIN2 Topology
(as of 8-8-05)
155
tba
45
HK
VN
PH
622
TH
EU
2
155
or
MY
3
x
SG
62
2
45
622
45
ID
AU
Dear All
Following careful evaluation of the TEIN2 NOC Services tender offers, DANTE is pleased to
announce that it has accepted in principle Tsinghua University's offer to provide the TEIN2
NOC service. A contractual agreement is now being drawn up between DANTE and
Tsinghua University for providing the service, based in Hong Kong, for the duration of the
TEIN2 project, to end December 2007.
As well as directly managing the planned TEIN2 PoPs in Beijing, Hong Kong and
Singapore, Tsinghua University will establish a close operational relationship with APANJP and the Japanese networks providing the Tokyo TEIN2 PoP, and also with other
partners or third parties providing capacity available for use by the TEIN2 project.
While there is much work still to do to finalise the contract and develop the NOC service, this
announcement marks an important step towards establishing the TEIN2 network.
Regards
David West
20050815
Experience
NOC
CERNET/CERNET2/DRAGONTAP
1.4G
Internet
10G
CERNET 2
CERNET
CNGI
Peering
10G
Domestic
Peering
DRAGONTAP
CNGI-BJIX
DRAGONLIGHT
155M
100M
1G
155M
45M
45M
HARNET
JANET
TANET
APAN
KOREN
STARLIGHT
TEIN2 NOC
TEIN2 NOC

Connectivity management



IP management



Hardware, software and configuration
Provide online information


Pro-active and reactive monitoring
Problem management
Inventory Control


implementation
incident and problem management
trouble ticket and statistics
Collaboration with other NOCs

APAN-JP, ...
Procedures

Configuration

Performance monitoring

Problem handling

Security

Online access of the operation information
Fault Management Procedure






Problem alert
Tracking
Problem identification and isolation
Trouble ticket assignment and engineer contact
Trouble shooting
Problem notification




initial status report
identification
updates
closure
IP Monitoring Procedure


Pro-active monitoring

link statistics

packet statistics

routing statistics

loss and delay statistics

network equipment statistics

advanced application monitoring
Reactive monitoring

taking fault reports around the clock
Advanced Management

IPv6



IP Multicast



Ethernet over MPLS management
QoS



multicast beacon
traffic monitoring
VPN management


fault monitoring
traffic and performance monitoring
CoS statistics
flow ranking
Security


IDS
host flaw scanner and the database
Challenges
Challenges
 Connectivity
 BGP
problem management
policy
 Open
access of the NOC information
 Shared
trouble system
 Security
 Level
2 services
 Advanced
services
Possible Paths
policy based routing and politics based routing
The Real World Routing
Meet requirement by user AS network

Policy


Database



Under the framework of TEIN2
IRR (who)
AS A
AS B
Configuration

AS-path prepend

Predefined community
Fine tune

Traffic and flow monitoring

End-to-end performance tools
AS D
AS C
BGP Routing
 Under

the framework of TEIN2
Try to provide the BGP routing as more
flexible as possible to the connected networks

Provide the online access to the routing, traffic
and flow information
BGP Implementation (draft)

Implement BOGON filters

Implement prefix length filtering

Implement authenticated BGP sessions

Implement maximum prefixes

Implement route dampening

Implement route filtering (prefix-list or access-list or/and
filter-list)
 Accept community tag
 Accept MED
 Accept aggregated prefixes, except for the policy based
routing
Open Access of the NOC Information
 Access

Under the framework of TEIN2
 Tools

policy
and user interface
Open software tools
• APAN NOC
• Abilene Observatory
• etc.

In-house developed tools
• status/performance/routing/traffic/flow/equipment
Status
Performance
Routing
Traffic
Flow
Equipment
Trouble Ticket System
Remarks
Remarks

Under the framework of the TEIN2, we welcome
suggestions and comments for the TEIN2 NOC
operation

SLA

BGP routing

Monitoring and measurement
Thoughts

Global Academic NOC meeting

NANOG, APRICOT, RIPE
 Video

phone
no time zone problem
 Shared

trouble shooting
 Shared

trouble ticket system
end-to-end measurement data
optimize routing