Transcript 営業SE研修：システム提案 LAN編（IPMLT）

Networking Survivability Features
Summary
Rev1.6 29 Nov., 2012
Case Study
2
Case Study 1
One of NS cabinet can be set up as Stand by CPU
ISP
Master
Slave1
Backup Master
Slave2
Slave3
1) While Master NS failed.
NS assigned as
“ Backup-Master” start
to work like stand by
CPU.
2) Slave 2 and 3 switch to
connect with “BackupMaster” NS.
3) EXT under Master
switch to connect with
“Backup-Master” as
“Secondary PBX”.
4) SIP Trunk can be
backed up by “BackupMaster”.
Item 1) and 2) : Please refer chapter “ 1.Backup-Master”
Item 3) : Please refer chapter “3.Automatic Rerouting to Secondary PBX”
Item 4) : Please refer slide #76-77 “ SIP GW fail over”
3
Case Study 2
NS work independently while Network has trouble
While network down and each cabinet can’t see other then NS can work independently.
IP/Legacy trunk and EXT terminated by each NS cabinet continue to work under each cabinet.
Slave1
Isolated
Master
Isolated
Slave2
Slave3
Isolated
Please refer chapter “ 2. Isolated mode”.
4
Over view
5
Over view
Individual Features
There are below 3 key Features.
1. Backup-master Mode
One of Slave unit become Backup-master and continue Onelook network service.
2.Isolated Mode
Slave become independent system to serve CO and EXT connect own cabinet.
3.Automatic Rerouting to Secondary PBX
NT or UT phone can divert to Secondary PBX and continue to work.
6
1.Back up Master
7
1-1 Over view
8
1-1Over view
4 NS1000 are connected as One look.
And Slave 1 is assigned as “Backup Master”.
Slave1
Backup Master
(Slave1)
Master
Slave2
Slave3
When Master died Slave1 become temporary master to run rest of system
under One-look network .
9
1-2 Condition
10
1-2 Condition 1
4 NS1000 are connected as One-look network.
And Slave 1 is assigned as “Backup Master”.
Slave1
Backup Master
(Slave1)
Master
Slave2
Slave3
Necessary Items;
There is no additional hardware or Activation Key required to use “Backup Master”
feature after establish “One-look Networking” .
Because “Backup Master” feature is a part of “One-look Networking” feature.
*All AK information transfer to “Back up Master” from “Master” and Temporary AK
will be act based on information from Master. Temporary AK valid 10 days from when
“Back up Master” start to act.
11
1-2 Condition 2
4 NS1000 are connected as One-look network.
And Slave 1 is assigned as “Backup Master”.
Slave1
Backup Master
(Slave1)
Master
Slave2
Slave3
Necessary network arrangement;
Full mesh VPN connection may need for all slave units able to connect with
“Backup Master”.
12
1-2 Condition 3
4 NS1000 are connected as One-look network.
And Slave 1 is assigned as “Backup Master”.
Slave1
Backup Master
(Slave1)
Master
Slave2
Slave3
Necessary Programming;
1)Set one of slave units as “Backup Master” from master unit.
<= Only 1 “Backup Master” can be assigned
2)How long Keep Alive packet will be checked under One-look?
-> “Multisite Keep alive Time-out time”
3)How long slave unit search for “Master” or “Backup Master” while start-up?
-> ”Multisite startup monitoring time”
13
1-3 How to work?
14
1-3 How to work? 1
Alive Check –Request from Master/Backup MasterMaster Side
Action
Type of Alive message
Unicast to each Slave unit
Alive Message interval
Interval= Alive time out timer/4
Condition of detection
as error
No response from Slave with in timing of Alive message time out timer.
Alive message time out
timer
Set at System Property “Multisite Keep alive Time-out time”
Action while error
Send restart request to Slave and treat the Slave as FAULT.
Keep Alive message from Master
Master
Slave2
Slave1
Backup Master
(Slave1)
Slave3
Keep Alive message from
Backup Master
15
1-3 How to work? 2
Alive Check –Response from SlaveSlave Side
action
Type of Message
Unicast Message to Master
Condition of detection as error
Not receive alive check message from Master for the timing of “Alive
check timer”.
Alive check timer
“Multisite Keep alive Time-out time” value is down load from Master.
Slave set timer little more than timer value that receive from
Master.
Action when got error
If no Alive request from Master then Slave reboot itself.
Randomize timing of response
To avoid crowding response against Keep Alive from Slave to Master
is randomize.
Keep Alive response to Master
Master
Slave2
Slave1
Backup Master
(Slave1)
Slave3
Keep Alive response to
Back Up Master
16
1-3 How to work? 3
Alive Check – No Keep Alive message from Master
1. Slave 1 not receive Alive Check Message from Master.
2. Slave 1 re-start to act as Backup Master.
Master
No Keep Alive message from Master
Slave2
Slave1
Backup Master
(Slave1)
Slave3
1.Slave 2-3 not receive Alive Check Message from Master.
2.Slave 2-3 re-start and try to connect Backup Master?
17
1-3 Sequence? 1
Change from “Master” to “Backup-master”
Master
Keep alive
Backup-master
Slave
Keep Alive ack. Interval
Keep alive ack.
Keep alive timeout
= Alive time out timer/4
Keep alive timeout
Restart as Backup-master
Slave Restart
Start req.
Start ack.
Slave Restart
18
1-3 Sequence? 2
Start Ack. sequence
Master/
Repeat 3 times to send
Start Req. In 30sec and
Slave
Back up Master
Start Ack. 10[SEC]
Start Req.
Start Req.
Start Req.
Start Ack. 10[SEC]
Hold 60 sec as a 1 cycle
Repeat this cycle until
Multisite Startup time
Start Ack. 10[SEC]
Time out (Default : 300sec)
Hold 60[SEC]
Start Req.
*Under Backup-Master scenario then send Start Ack. for both Master and Backup-master.
19
1-3 How to work? 4
System Data Transfer –From Master to Backup MasterSystem Data from Master to Backup Master
every time when data changed and saved or every 30 min.
Slave1
Backup Master
(Slave1)
Master
Slave2
Slave3
Synchronized data is follow
- Setting data of Extension, Trunk, Group , System Speed Dial, Make/Receive Call setting
Door phone／External Pager／External I/O, Time Service
・Extension base setting such as Station Lock, War-Up, LCS, Auto Answer, Absent Message,
Message Waiting, Incoming-Outgoing Log, FWD/DND
・ICD-G base setting such as Message Waiting, FWD/DND, UCD monitor
・Verification code, Pass word lock status
・All AK
20
1-3 How to work? 5 -resource transitionData on SRAM
Master
Slave1
Backup Master
(Slave1)
Data on SRAM
Not transfer to BackupSlave2
Master
・ SMDR
・Error Log
・EXT setting like
Timed Reminder
Remote Station Lock
Check-In/Out
Ready/Not Ready/Clean Up
Login/Logout
・EXT, CO, Verified Code base Charge Total
Slave3
Call Record can be collected and gathered by CA Call account.
21
1-3 How to work? 6 -service transitionUM
UM & IMAP4 Server is not backed up by “Backup Master”.
If the customer request UM with “Backup Master” environment;
1) To use UM at each cabinet.
2) To use UM on Slave that is assigned as “Backup Master” for entire One-look
network.
Master
Mail box for
EXT-A
Backup Master
Mail box for
EXT-A
EXT-A
22
1-3 How to work? 7-service transitionCA
CA is not backed up by “Backup Master”.
If the customer request CA with “Backup Master” environment;
There is no instant solution to implement CA with “Backup Master”.
1) In case PBX mode
CA client User need to change IP address of CA server
(to Backup Master’s IP address) manually.
2) In case Server mode
It is necessary to prepare separate CS server
for Backup Master. And activate the CA server when Backup Master
become active.
And CA client User need to change IP address of CA server manually.
23
1-3 How to work? 8-resource/service transitionOther Resources/Services
OGM is not backed up by “Backup Master”.
OGM is necessary to record at independent NS cabinet.
Play OGM record at Backup Master without OGM of Master WAV file transferring
them to Backup Master.
Time and Date
Slave NS run own clock by “Manual / ISDN & Call ID(FSK) / SNTP” then
“Time and Date” for Slave system continue to run by own clock under
“Backup Master” environment.
VoIP / Conference / Echo-Canceller / T-SW etc
These resources will be released while One-look start to be controlled by Backup Master.
Programming up date
Automatic program up date will not be act. Manual Program Up date can be done.
24
1-3 How to work? 9- resume from Back Up Master to MasterHow to recover from Backup mode
1)At home screen, select Master ICON and right click.
2)Select “Normal Mode”
3)Confirmation window come up “All site will re-start. OK?”
4)Master re-start and start to work as Master mode.
5)Slave re-start and re-connect to Master.
“Normal Mode” has to be deployed manually to the Master unit to avoid sudden switch back from
Backup-Master mode to interrupt service.
25
1-4 Programming
26
1-4 Programming 1 -WizardDefine Backup Master at Wizard Mode
Select Back up Master mode at end of Unit addition wizard
27
1-4 Programming 2
Programming at Master unit
Assign which Slave will be act as “Backup Master”
Note: When change Slave Unit to Back up Master, the assgined unit will be restarted
28
1-4 Programming 3
Programming at Master unit
300
1.“Multisite Keep alive Time-out time” value is used for Alive check for
both Master and Slave.
2.”Multisite startup monitoring time” is used for Slave how long wait reply
from Master whether start with Master/Backup Master or Isolated mode*.
*Isolated mode describe at chapter “ Isolated mode”.
29
1-5 Error Notification
30
1-5 Error Notification
Error message from NS
When Backup Master will become Active, there will be able to send
below error message by e-mail.
【Subject】
KX-NS1000 System alarm#1 or KX-NS1000 System alarm#2
【text】
[System Name] :KX-NS1000
[MPR-ID]
:AAAA-BBBB-CCCC-DDDD
[Date]
:11/12/31
[Time]
:23:59:59
[Error Code]
:535
[Sub Code]
: 50400
E-mail address
has to be set at
each NS cabinet.
[Error Message] :Change into Backup Master Mode
31
2 Isolated mode
32
2-1 Over view
33
2-1 Over view 1
Isolated mode
4 NS1000 are connected as One-look network.
Slave1
Master
Slave2
Isolated mode
Slave3
Isolated mode
If Slave can’t communicate neither Master or Backup master like
when VPN network down all slave unit can’t talk to Master.
Then each Slave become Isolated mode and run by itself but with some
limitation.
34
2-2 Condition
35
2-2 Condition 1
Necessary Item
4 NS1000 are connected as One-look network.
Isolated mode
Slave1
Master
Slave2
Isolated mode
Slave3
Isolated mode
Necessary Items;
There is no additional hardware or Activation Key required to use “Isolated mode”
feature after establish “One-look Networking” .
Because “Isolated mode” feature is a part of “One-look Networking” feature.
36
2-2 Condition 2
Necessary Network Arrangement
4 NS1000 are connected as One-look network.
Isolated mode
Slave1
Master
Slave2
Isolated mode
Slave3
Isolated mode
Necessary network arrangement;
“Spoke & Hub” or “Full mesh” whatever network arrangement is OK for
“Isolated mode”.
37
2-2 Condition 3
Necessary Programming
4 NS1000 are connected as One-look.
Isolated mode
Slave1
Master
Slave2
Isolated mode
Slave3
Isolated mode
Necessary Programming;
Enable “Isolated mode” to each Slave that is necessary to act as
“Isolated mode”.
38
2-3 How to work?
39
2-3 How to work? 1
Alive Check –Request from MasterMaster Side
Action
Type of Alive message
Unicast to each Slave unit
Alive Message interval
Interval= Alive time out timer/4
Condition of detection
as error
No response from Slave with in timing of Alive message time out timer.
Alive message time out
timer
Set at System Property “Multisite Keep alive Time-out time”
Action while error
Send restart request to Slave and treat the Slave as FAULT.
Keep Alive message from Master
Master
Slave2
Slave1
Slave3
40
2-3 How to work? 2
Alive Check –Response from SlaveSlave Side
action
Type of Message
Unicast Message to Master
Condition of detection as error
Not receive alive check message from Master for the timing of “Alive
check timer”.
Alive check timer
“Multisite Keep alive Time-out time” value is down load from Master.
Slave set timer little more than timer value that receive from Master.
Action when got error
If no Alive request from Master then Slave reboot itself.
Randomize timing of response
To avoid crowding response against Keep Alive from Slave to Master
is randomize.
Keep Alive response to Master
Slave1
Master
Slave2
Slave3
41
2-3 Sequence to be Isolated mode
Change from “Slave” to “Isolated mode”
Master
Keep alive
Backup-master
Slave
Keep alive ack.
Keep alive timeout (Master)
Keep alive timeout (Backup-master)
Slave restart as
Isolated
42
2-3 How to work? 3
System Data Transfer –From Master to SlaveSystem Data from Master to Slave
Slave1
Master
Slave2
Slave3
Synchronized data is follow
.Trunk, Group data Tennant/Trunk-G/Extension-G/UCD-G/Paging-G/Pick UP-G/Hunting-G/PS-G
. System Speed Dial, Make/Receive Call setting Door phone／External Pager／External I/O,
・Extension base setting such as Station Lock, War-Up, LCS, Auto Answer, Absent Message,
Message Waiting, Incoming-Outgoing Log, FWD/DND
・ICD-G base setting such as Message Waiting, FWD/DND, UCD monitor
・Verification code, Pass word lock status and AK which related with Centralized
・etc
System Data transfer from Master to Slave is done at every 30 min.
Also transferring every time while data save at Master.
43
2-3 How to work? 4
Alive Check –Response from Slave1. Slave not receive Alive Check Message from Master.
2. Slave re-start to act as Isolated mode.
Slave1
No Keep Alive message from Master
Master
Slave2
Isolated mode
Slave3
Isolated mode
Isolated mode
44
2-3 How to work? 5
Resources
Special Temporary AK(Centralized AK only) deploy to the
Isolated NS from Master NS.
Other resources is same condition as “Backup Master”
45
2-3 How to work? 6 - resume from Isolated to SlaveHow to release Isolated mode to Slave?
Direct Log-In to the Isolated mode system.
1)At home screen, select Slave ICON and right click.
2)Select “Normal Mode”
3)Confirmation window come up “This site will re-start. OK?”
4)This Slave re-start and start to send Start Ack to Master or Backup
Master.
46
2-4 Programming
47
2-4 Programming 1
Programming at Slave unit
Default: Disable.
48
2-5 Error Notification
49
Error Notification
Error message from NS
When Slave will become Isolated mode, there will be able to send
below error message by e-mail.
【Subject】
KX-NS1000 System alarm#1 or KX-NS1000 System alarm#2
【Message body】
[System Name] :KX-NS1000
[MPR-ID]
:AAAA-BBBB-CCCC-DDDD
[Date]
:11/12/31
[Time]
:23:59:59
[Error Code]
:537
[Sub Code]
: 50400
E-mail address
has to be set at
each NS cabinet.
[Error Message] :Change into ISOLATED Mode
50
3 Recovery by IPPT
-Primary/Secondary PBX-
51
3-1 Over view
52
3-1 Over view
When the IPPT has no communication between NS where they Primary
belong to then those IPPT can divert to connect secondary NS.
IPPT mean UT/NT/UDT(SIP-DECT) except IPCS.
Master (Secondary)
Slave1 (Primary UNIT)
If this primary-secondary feature is set for one EXT then two EXT port will be consumed.
One at Primary NS and the other one at Secondary NS.
The feature is slightly differ from that you knew same feature for TDE/NCP.
The differences are described in following pages.
The software version of UT1xx/248 should be V1.210 or later if use this feature.
53
3-2 Condition
54
3-2 Condition 1
Necessary Item
Temporally AK
Master
(Primary)
Back Up Master
(Secondary)
110,112
110
112
213
214
Necessary Items;
Activation Key may not required while Back Up Master used as “Secondary”
If there is enough AK in Master to cover those EXT who move from Master.
Thus temporary AK deploy for Back Up Master.
55
3-2 Condition 2
Necessary Item
Necessary Items;
Activation Key required to use* IPPT as “Secondary” PBX Extension telephone.
If it is necessary to use “213” and “214” under Master PBX while Slave 1 can’t give
service then 2 IPPT AK necessary to add for Master.
*To assign IPPT to secondary PBX not require AK.
AK is required to support
213/214 on Master
Slave1(Primary)
Master(Secondary)
214
110
112
213
213
214
56
3-2 Condition 3
Necessary Network Arrangement
Necessary network arrangement;
VPN connection necessary to deploy communication in between Master and
“213/214” extensions.
Slave1(Primary)
Master(Secondary)
VPN
214
110
112
213
213
214
57
3-2 Condition 4
Necessary Programming
Necessary Programming;
NS: Assign “Secondary” port for the EXT needs Secondary PBX service.
UT: “Primary” and “Secondary” PBX IP address is download from NS1000.
NT/UDT: Necessary to assign Secondary PBX IP address at each NT/UDT.
Slave1 (Primary)
Master(Secondary)
214
213
110
112
213
214
58
3-3 How to work?
59
3-3 How to work? 1- In case of NT Alive check
In case of NT
1) NS send Alive check packet to NT.
2) NT reply to NS.
3) NT not receive alive packet from Primary PBX then NT look for Secondary PBX with NT reboot.
4) Establish connection with Secondary PBX.
5) EXT 214 start to work with Master PBX.
6) Keep sending ARP to Primary PBX.
Master (Secondary)
110
112
Slave1 (Primary)
214
60
3-3 How to work? 2 - In case of NT Change from “Primary PBX” to “Secondary PBX”
When IP-PT is in “Primary PBX”, it doesn’t send a “ARP” signal to “Secondary PBX”,
because the priority of “Primary” is higher than “Secondary”.
When LAN connection of “Primary PBX” is failed, IP-PT starts to send a “ARP”
signal to “Secondary PBX”.
Secondary PBX
IP-PT(NT)
Primary PBX
Keep Alive (every 5 sec)
Answer for Keep Alive
・
・
ARP
ARP (9 times)
LAN connection of “Primary
PBX” is failed.
IP-PT(NT) starts reboot
IP-PT starts register to
“Secondary PBX”
Keep Alive (every 5 sec)
Answer for Keep Alive
・
・
ARP (every 60sec)
*When IP-PT is in “Primary PBX” and “Primary PBX” stays alive,
IP-PT does not switch to “Secondary PBX”.
61
3-3 How to work? 3- In case of NT Change from “Secondary PBX” to “Primary PBX”
When IP-PT is in “Secondary PBX”, it sends a “ARP” signal to “Primary PBX”
every 60sec.
When LAN connection of “Primary PBX” is retrieved, IP-PT and PBX start the
communication.
“Secondary PBX” sends ”Keep Alive” to IP-PT every 5sec.
“Primary PBX” sends “Keep Alive” to IP-PT every 60sec.
After IP-PT switch back to “Primary PBX”, only “Primary PBX” sends “Keep Alive” to
IP-PT.
Secondary PBX
IP-PT(NT)
Keep Alive (every 5 sec)
Answer for Keep Alive
・
・
・
・
・
Stop communication
Primary PBX
ARP (every 60 sec)
ARP
Keep Alive (every 60sec)
Answer for Keep Alive
・
・
Retrieve LAN connection of
“Primary PBX”
IP-PT(NT) starts reboot
IP-PT(NT) starts register to
“Primary PBX”
Keep Alive (every 5sec)
Answer for Keep Alive
62
3-3 How to work? 4- In case of NT Connect back to Primary PBX
In case of NT
1) Detect ARP response from Primary while connect to Secondary.
2) IPPT connect back to Primary PBX with NT reboot.
Master(Secondary)
110
112
Slave1(Primary)
214
63
3-3 How to work? 5- In case of UT Alive check
In case of UT
1) UT send PERIODIC Inform packet to NS.
2) NS reply to UT.
3) UT not receive reply packet from Primary PBX
then UT look for Secondary PBX with UT reboot.
Master (Secondary)
Slave1 (Primary)
[PERIODIC Inform] is keep alive of UT terminal.
110
112
213
64
3-3 How to work? 6- In case of UT Change from “Primary PBX” to “Secondary PBX”
When IP-PT is in “Primary PBX”, it doesn’t send a “ARP” signal to “Secondary PBX”,
because the priority of “Primary” is higher than “Secondary”.
When LAN connection of “Primary PBX” is failed, IP-PT starts to send a “ARP”
signal to “Secondary PBX”.
Secondary PBX
IP-PT(UT)
Primary PBX
Periodic (Inform Interval)
・
・
LAN connection of “Primary
PBX” is failed.
IP-PT(UT) starts reboot
Periodic (Inform Interval)
Periodic (5sec)
IP-PT starts register to
“Secondary PBX”
ARP
Periodic (10sec)
Resend times
Periodic (20sec)
(5 times)
Periodic (40sec)
Inform(BOOTSTRAP)
*When IP-PT is in “Primary PBX” and “Primary PBX” stays alive,
IP-PT does not switch to “Secondary PBX”.
65
3-3 How to work? 7- In case of UT Connect to Secondary PBX
In case of UT
1)UT send PERIODIC inform to NS.
2)If there is no response against PERIODIC inform from Slave1/Primary.
3)Master send Reply (by PERIODIC inform) to UT with command that mention
connect to Secondary NS.
4)UT start to connect with Master/Secondary.
Master (Secondary)
110
112
Slave1 (Primary)
213
66
3-3 How to work? 8- In case of UT Connect back to Primary PBX
In case of UT
UT will back to connect primary NS while Master or Backup-master send
“SetParameterValue” to UT while changing system back to “Normal” mode.
Master (Secondary)
110
Slave1 (Primary)
213
112
UT can’t move back to primary NS
system that is in Isolated mode.
67
3-3 How to work? 9- In case of UT Change from “Secondary PBX” to “Primary PBX”
When IP-PT is in “Secondary PBX” and “Primary PBX” is back in work (Master or
Backup-master get start ack from primary), then Master or Backup-master send
“SetParameterValue” to UT.
UT send ARP to Primary, Reg to Primary and restart to work with Primary.
Master/B-MAS
Secondary PBX
UT
Primary PBX
Inform (Periodic)
Inform Res. (Periodic)
Retrieve Primary PBX
・
・
Retrieve Primary PBX
SetParameterValues
Device.ManagementServer.URL
Stop communication
Management Server change
ARP
Inform(BOOTSTRAP)
Inform Res. (BOOTSTRAP)
IP-PT starts register to
“Primary PBX”
68
3-3 How to work? 10- Mailbox Connect to Secondary PBX
When user need to use UM on Secondary NS, user need to create same Mail BOX to
secondary Unit
Mail box214
Mailbox has to be created
at both PBX independently.
Mail box214
These Mailbox has no integration.
They work completely independent.
Master (Secondary)
110
112
Slave1 (Primary)
214
69
3-4 Programming
70
3-4 Programming 1
Programming at NS - Virtual EXT card -
Create EXT is assigned as “Secondary” port
as preparation.
71
3-4 Programming 2
Programming at NS - Virtual EXT card “Secondary Port Wizard” let you assign the EXT need Secondary connection to
which NS1000.
Primary NS location
Choosing Secondary NS location
Primary NS EXTs that doesn’t program
Primary NS EXTs that program
with Secondary NS
with Secondary NS at this site.
72
3-4 Programming 3
Programming at NS - Virtual EXT card You can check at which EXT is paired with which EXT like below;
Information of
Clarify assign as
Pair EXT.
Primary/Secondary PBX
73
3-5 Error Notification
74
Error Notification
Error message from NS
There is no Error message while IP telephone
connect to Secondary NS.
75
Other Back up features
76
SIP GW 1
SIP GW Fail over
In case of SIP GW on Slave assign as Backup-master and back up SIP GW,
when Master become defective then Backup-Master start to send register
requirement to ISP.
ISP
Master(Primary)
Slave1 (Secondary)
Back Up Master
77
SIP GW 2
SIP GW Fail over
If the SIP trunk that are used at Master need to be back up while
Back up Master become active then it is necessary to assign as
“Backup” at here.
Assign as “Backup” means that this port will not send “REGISTOR”
request to SIP provider unless unit become Back up Master.
78
UM Group 1
UM Group Fail over
When Master NS running some of Trunk call is terminated by UM:500 on Master.
If Master has failure and Back Up Master become active then those call automatically
divert to UM:501 on Back up Master.
Incoming call from Tunk/Ext
Master(Primary)
UM
UM
500
501
Slave1 (Secondary)
Back Up Master
79
UM Group 2
UM Group Fail over
UM Group Fail Over work against call like below;
・Call through Trunk
・Call through DISA
・Call from EXT
80
Appendix
81
END
86
Modification
20120828-01 Networking Survivability_Rev1_28Aug2012Mar.ppt
- 1st release
20120906-02 Networking Survivability_Rev1_1_6Sep2012Mar.ppt
- Add comment to slide #73
20120926-03 Networking Survivability_Rev1_2_26Sep2012Mar.pptx
- Change slide position to make better explanation flow.
- Revise and add explanation to slide #40
- Add default value to slide #43
- Add slide #63
20121025-04 Networking Survivability_Rev1_3_25Oct2012Mar.pptx
- Add slide #24
20121031-05 Networking Survivability_Rev1_4_31Oct2012Mar.pptx
- Revise back ground picture on slide #21
- Add e-mail setting place to Slide #27 and #46
- Add remarks for Slide #49
- Add slide #67, swap slide order 68<->69.
87
Modification
20121106-06 Networking Survivability_Rev1_5_6Nov2012Mar.pptx
- Change “Combined Feature” to “Case study” and move to first part of this PPT.
20121129-29 Networking Survivability_Rev1_6_29Nov2012Mar.pptx
- #53 Add following comment
“The software version of UT1xx/248 should be V1.210 or later if use this feature.”
- #64 Modify wrong sentence “PERIDIC” -> “PERIODIC”
88