Title: NSP Demonstration Scenarios
1NSPDemonstrationScenarios
John DeHartjdd_at_cs.wustl.eduhttp//www.arl.wustl
.edu/arl
2NOTES
- GUI things to watch out for
- line graphs that creep apart
- I believe this has something to do with the fact
that the different lines are coming from
different CPs. - The only way to get them back in sync is to kill
the graph and restart it. - for the demo we will probably have one
comprehensive GUI spec file and also have
individual ones for each graph. - so, you should be able to just kill the affected
graph and restart it. - line graphs disappearing from the display
- if the entry in the legend on the right side goes
away, then the TCP connection for that sample has
been lost. - The only way to get it back is to kill the graph
and restart it. (See note above) - also see notes below about SIGPIPE.
- line graphs that display up and down tight
zig-zag lines when they should be flat - we dont know yet what causes this.
- you need to close all the graphs and kill the gui
and restart it
3NOTES (continued)
- We still occasionally get a data source that
spontaneously turns off - I havent had time to investigate this yet.
- They always seem to come back with the next
iteration so it shouldnt be a big deal. - SIGPIPE
- if MSRC or newGBNSC.init gets a SIGPIPE
- you will need to kill the GUI
- it will probably have lost some or all of its
line graphs - then kill and restart the offending MSRC or
newGBNSC.init - in PI_MTG_DEMO/COMBINED you should find runGBNSC
and runMSRC scripts. - then restart the GUI
- If it appears that the FPX has crashed
- you will need to kill and restart everything.
- All the way back to the INITALL.
- See PI_MTG_DEMO/README for directions on
restarting everything.
4Throughput Demo (Formerly Demo 1)
5Queuing DEMO (formerly Demo 2A)
6Routes/Filters Priority Resolution
7OLD DEMO 1
8OLD DEMO 2A
9OLD DEMO 3A
10Demo Config
CP
WUGS Monitor
M
P0
NSP-0
SW-1
SW-1
4 vcis
FPX2ing
950Mb/s
FPX2eg
950Mb/s
M
M
950Mb/s
4
FPX3ing
950Mb/s
FPX3eg
M
M
950Mb/s
4
FPX4ing
950Mb/s
FPX4eg
0-4 VCIs
M
M
H1
FPX5ing
FPX5eg
4
950Mb/s
950Mb/s
M
M
H2
0-4
FPX6ing
FPX6eg
950Mb/s
4
950Mb/s
M
M
950Mb/s
FPX7ing
FPX7eg
4
950Mb/s
M
M
11Demo Config
- Each VCI turned on and off for each Demo.
- SA, DA and rate individually controlled for each
VCI. - 8 flows turned at initialization time.
SW-1
F1 VCI128
H1
F2 VCI129
F3 VCI130
F4 VCI131
F5 VCI128
H2
F6 VCI129
F7 VCI130
F8 VCI131
12JST V1 Hardware Performance Demo
- Objective - to showcase major performance
characteristics of initial hardware
configuration. - Outline
- Scenario 1 all inputs receive data at 950 Mb/s
- alternate between sending packets randomly to all
outputs sending to 3 - Phase 1 (10 seconds) all outputs receive 950
Mb/s - Phase 2 ( 1 second) ½ outputs receive 1.1
Gb/s, ½ outputs receive 800 Mb/s - Scenario 2 Two flows
- one bursty DG flow building up a backlog, but not
overflowing - one constant rate flow
- monitor lengths of the two queues
- Scenario 3 highlight one input
- exercise route table, general match filters,
exact match filters - demonstrate priority mechanism between routes and
filters
13Demo Config Scenario 1
CP
WUGS Monitor
M
P0
NSP-0
SW-1
SW-1
3 vcis
FPX2ing
950Mb/s
FPX2eg
950Mb/s
M
M
950Mb/s
3
FPX3ing
950Mb/s
FPX3eg
M
M
950Mb/s
3
FPX4ing
950Mb/s
FPX4eg
2 VCIs
M
M
H1
FPX5ing
FPX5eg
3
950Mb/s
950Mb/s
M
M
H2
1 VCI
FPX6ing
FPX6eg
950Mb/s
3
950Mb/s
M
M
950Mb/s
FPX7ing
FPX7eg
3
950Mb/s
M
M
14Demo Config Scenario 1
Phase 1
RAD_LC
RAD_LC
RAD_SW
RAD_SW
FPX2ing
FPX2eg
950 Mb/s
950 Mb/s
950 Mb/s
FPX3ing
FPX3eg
950 Mb/s
Dst Addr
950 Mb/s
FPX4ing
FPX4eg
950 Mb/s
F1 192.168.40.2 F2 192.168.44.2 F7 192.168.48.2
FPX5ing
FPX5eg
950 Mb/s
950 Mb/s
FPX6ing
FPX6eg
950 Mb/s
950 Mb/s
950 Mb/s
FPX7ing
FPX7eg
950 Mb/s
15Demo Config Scenario 1 (alternative)
Phase 2
RAD_LC
RAD_LC
1.1 Gb/s
Arriving rate 1.10 Gb/s
RAD_SW
RAD_SW
FPX2ing
FPX2eg
980 Mb/s
FPX3ing
FPX3eg
800 Mb/s
Dst Addr
FPX4ing
FPX4eg
980 Mb/s
F1 192.168.41.2 F2 192.168.45.2 F7 192.168.49.2
FPX5ing
FPX5eg
800 Mb/s
FPX6ing
FPX6eg
980 Mb/s
FPX7ing
FPX7eg
800 Mb/s
Egress DG QID 448 OVIN(10)SA(10)DA(10) QI
D 448 001010 458
16JST V1 Hardware Performance Demo
- Objective - to showcase major performance
characteristics of initial hardware
configuration. - Outline
- Scenario 1 all inputs receive data at 950 Mb/s
- alternate between sending packets randomly to all
outputs sending to 3 - Phase 1 (10 seconds) all outputs receive 950
Mb/s - Phase 2 ( 1 second) ½ outputs receive 1.1
Gb/s, ½ outputs receive 800 Mb/s - Scenario 2 Two flows
- one bursty DG flow building up a backlog, but not
overflowing - one constant rate flow
- monitor lengths of the two queues
- Scenario 3 highlight one input
- exercise route table, general match filters,
exact match filters - demonstrate priority mechanism between routes and
filters
17Scenario 2A 2 DG Flows
G L I n k
FPX7eg
Bursty(600 Mb/s,0,0.5)
H1
FPX4ing
DA192.168.56.2
SA192.168.128.2
VCI 128 SP 0
448001010b 44810458
1Gb/s
VCI 129 SP 1
H2
FPX5ing
DA 192.168.56.2
SA192.168.132.2
448011010b 44826474
Constant(400 Mb/s)
Egress DG QID 448 OVIN(10)SA(10)DA(10)
During Burst periods, total traffic is 20Mb/s
over Link rate
18HW Perf Scenario 2A (Expected Results)
Rate
Qlength
Bursty Flow Queue QID-1
Constant Rate Flow QID-2 (always 0)
1000 Mb/s
13 MB
800 Mb/s
Bursty Rate
600 Mb/s
Constant Rate
400 Mb/s
t
0
12
6
24
18
36
30
seconds
19Scenario 2A
Egress Queue Length Monitor
Q
NSP-0
R1 DA192.168.56.0/24 OVIN0x1C
P4
R2 DA192.168.56.0/24 OVIN0x1D
Bursty(600 Mb/s,0,0.5)
R1
H1
P7
W
F3, vci130
SA192.168.128.2
VCI 128, SubPort 0
W
DA192.168.56.2
QID448001010b458
VCI 129, SubPort 1
W
P5
Constant(400 Mb/s)
QID448011010b474
R2
H2
W
F8, vci131
SA192.168.132.2
DA192.168.56.2
Egress DG QID 448 OVIN(10)SA(10)DA(10)
20JST V1 Hardware Performance Demo
- Objective - to showcase major performance
characteristics of initial hardware
configuration. - Outline
- Scenario 1 all inputs receive data at 950 Mb/s
- alternate between sending packets randomly to all
outputs sending to 3 - Phase 1 (10 seconds) all outputs receive 950
Mb/s - Phase 2 ( 1 second) ½ outputs receive 1.1
Gb/s, ½ outputs receive 800 Mb/s - Scenario 2 Two flows
- one bursty DG flow building up a backlog, but not
overflowing - one constant rate flow
- monitor lengths of the two queues
- Scenario 3 highlight one input
- exercise route table, general match filters,
exact match filters - demonstrate priority mechanism between routes and
filters
21Demo Config Scenario 3
- Scenario 3 highlight one input
- exercise route table, general match filters,
exact match filters - Use 3 Flows
- Each flow hits a different route
- Each of these 3 routes goes to a different output
port - Use an overriding EM filters for each flow
- Use an overriding GM filter for 2 flows
- Demonstrate Priorities
- EM gt GM gt Routes
22Demo Config Scenario 3
CP
RAD Ctr Monitor
R
P0
NSP-0
WUGS Monitor
W
SW-1
SW-1
FPX3eg
400 Mb/s
H1
W
FPX2ing
FPX4eg
900 Mb/s
W
W
3 VCIs
FPX5eg
300 Mb/s
H2
W
200 Mb/s
FPX6eg
W
FPX7eg
W
23Demo Config Scenario 3A
- Phase 1
- Just Routes
- Phase 2
- Add GM Filter
- Phase 3
- 3A Add EM Filter 1
- 3B Add EM Filter 2
- 3C Add EM Filter 3
- 3D Delete EM Filter 1
- 3E Delete EM Filter 2
- 3F Delete EM Filter 3
- Phase 4
- Delete GM Filter
- Back to Phase 1
24Scenario 3A Phase 1
Egress SubPort Pkt Ctr Monitor
R
NSP-0
P3
200 Mb/s
Just Routes
VCI 128, SubPort 0
P2
P4
300 Mb/s
200 Mb/s
DA192.168.64.2
VCI 128, SubPort 0
R1
H1
SA192.168.128.2
P5
400 Mb/s
300 Mb/s
VCI 128, SubPort 0
DA192.168.68.2
R2
H2
SA192.168.132.2
P6
400 Mb/s
DA192.168.72.2
R3
H2
SA192.168.132.2
P7
25Scenario 3A Phase 2
Egress SubPort Pkt Ctr Monitor
R
NSP-0
P3
Add GM Filter
P2
P4
200 Mb/s
DA192.168.64.2
GM
H1
SA192.168.128.2
P5
400 Mb/s
300 Mb/s
VCI 128, SubPort 0
DA192.168.68.2
GM
H2
SA192.168.132.2
P6
200 Mb/s
VCI 128, SubPort 0
400 Mb/s
DA192.168.72.2
VCI 128, SubPort 0
R3
H2
300 Mb/s
SA192.168.132.2
P7
26Scenario 3A Phase 3A
Egress SubPort Pkt Ctr Monitor
R
NSP-0
P3
Add EM Filter 1
P2
P4
200 Mb/s
DA192.168.64.2
E1
H1
SA192.168.128.2
P5
400 Mb/s
300 Mb/s
VCI 128, SubPort 0
DA192.168.68.2
GM
H2
SA192.168.132.2
P6
400 Mb/s
DA192.168.72.2
VCI 128, SubPort 0
R3
H2
300 Mb/s
SA192.168.132.2
P7
200 Mb/s
VCI 128, SubPort 0
27Scenario 3A Phase 3B
Egress SubPort Pkt Ctr Monitor
R
NSP-0
P3
300 Mb/s
Add EM Filter 2
VCI 129, SubPort 1
P2
P4
200 Mb/s
DA192.168.64.2
E1
H1
SA192.168.128.2
P5
400 Mb/s
300 Mb/s
VCI 128, SubPort 0
DA192.168.68.2
E2
H2
SA192.168.132.2
P6
400 Mb/s
DA192.168.72.2
R3
H2
SA192.168.132.2
P7
200 Mb/s
VCI 128, SubPort 0
28Scenario 3A Phase 3C
Egress SubPort Pkt Ctr Monitor
R
NSP-0
P3
300 Mb/s
Add EM Filter 3
VCI 129, SubPort 1
P2
P4
400 Mb/s
200 Mb/s
DA192.168.64.2
VCI 129, SubPort 1
E1
H1
SA192.168.128.2
P5
300 Mb/s
DA192.168.68.2
E2
H2
SA192.168.132.2
P6
400 Mb/s
DA192.168.72.2
E3
H2
SA192.168.132.2
P7
200 Mb/s
VCI 128, SubPort 0
29Scenario 3A Phase 3D
Egress SubPort Pkt Ctr Monitor
R
NSP-0
P3
300 Mb/s
Remove EM Filter 1
VCI 129, SubPort 1
P2
P4
400 Mb/s
200 Mb/s
DA192.168.64.2
VCI 129, SubPort 1
GM
H1
SA192.168.128.2
P5
300 Mb/s
DA192.168.68.2
E2
H2
SA192.168.132.2
P6
200 Mb/s
VCI 129, SubPort 1
400 Mb/s
DA192.168.72.2
E3
H2
SA192.168.132.2
P7
30Scenario 3A Phase 3E
Egress SubPort Pkt Ctr Monitor
R
NSP-0
P3
Remove EM Filter 2
P2
P4
400 Mb/s
200 Mb/s
DA192.168.64.2
GM
VCI 128, SubPort 1
H1
SA192.168.128.2
P5
300 Mb/s
DA192.168.68.2
GM
H2
SA192.168.132.2
P6
200 Mb/s
VCI 129, SubPort 1
400 Mb/s
DA192.168.72.2
VCI 129, SubPort 1
E3
H2
300 Mb/s
SA192.168.132.2
P7
31Scenario 3A Phase 3F
Egress SubPort Pkt Ctr Monitor
R
NSP-0
P3
Remove EM Filter 3
P2
P4
200 Mb/s
DA192.168.64.2
GM
H1
SA192.168.128.2
P5
400 Mb/s
300 Mb/s
VCI 128, SubPort 0
DA192.168.68.2
GM
H2
SA192.168.132.2
P6
200 Mb/s
VCI 129, SubPort 1
400 Mb/s
DA192.168.72.2
VCI 129, SubPort 1
R3
H2
300 Mb/s
SA192.168.132.2
P7
32Scenario 3A Back to Phase 1
Egress SubPort Pkt Ctr Monitor
R
NSP-0
P3
200 Mb/s
Delete GM Filter 1
VCI 128, SubPort 0
P2
P4
300 Mb/s
200 Mb/s
DA192.168.64.2
VCI 128, SubPort 0
R1
H1
SA192.168.128.2
P5
400 Mb/s
300 Mb/s
VCI 128, SubPort 0
DA192.168.68.2
R2
H2
SA192.168.132.2
P6
400 Mb/s
DA192.168.72.2
R3
H2
SA192.168.132.2
P7