02 FICOM FIOM 40 Flexi ISN Architecture v1

Flexi ISN Architecture
Flexi ISN 4.0 Commissioning, Integration and O&M
Soc Classification level

1 Nokia Siemens Networks FICOM40_02 / 2009-03-04
Module contents
Module Objectives
General Architecture
Hardware
Software
GUI
Network Interfaces

Module objectives
At the end of this module the participant can:

Describe the general architecture of Flexi ISN
Describe the FlexiServer hardware
Describe the Flexi ISN 4.0 software
Describe the IPSO 3.9.4NET software
Describe the basic functionality of Flexi ISN GUI
List the internal interfaces of Flexi ISN and give short
description of them
List the external interfaces of Flexi ISN and give short
description of them
Name the used protocols and describe their functionalities
List software and system component relation and functionality
Module contents
Module Objectives
Hardware
Software
GUI
Network Interfaces

Flexi ISN general architecture
Flexi ISN uses FlexiServer Blade

hardware
Flexi ISN operating system is Nokia
IPSO
Flexi ISN management takes place
via web based Voyager interface
Configuration via CLI (command line
interface) is supported
Flexi ISN utilizes multiple
processors and provides a high
performance, scalable ISN solution
The built-in high availability in Flexi
ISN makes the ISN transparently
redundant in the network

Flexi ISN is based on NSN IPSO operating system, running in FlexiServer Blade
hardware. Flexi ISN inherits the well-proven Voyager user interface for managing IPSO
operating system and the applications. Management is also possible with NSN NetAct.
Flexi ISN utilises multi-CPU hardware to provide a high performance, scalable ISN
solution. At the same time it uses built-in high availability mechanisms to provide mobile
users with fault tolerant access to services. Redundancy is transparent to the other
network elements because Flexi ISN hides its multi CPU structure, appearing as a single
IP router and application platform.
Structural concept of Flexi ISN
Physical Logical
ISN ISN ISN ISN

SW SW SW SW
IPSO IPSO IPSO IPSO

= CPU_1 CPU_2 CPU_3 CPU_N
i/f i/f i/f i/f i/f i/f i/f i/f i/f i/f

The logical structure of Flexi ISN is shown in Figure 2. Each processing unit is running its
own instance of IPSO operating system. These units, Blades, are connected to each
other via internal networks. These internal networks are called Backplane networks. To
switch packets in the internal networks the system includes two built-in Layer 2 switches.
Some of the Blades also have external network interfaces, which are used to integrate
Flexi ISN to the GPRS/3G network, and for forwarding packets to and from the mobile
users.
The Blades have their specific roles in a functioning Flexi ISN system. In principle, all
important functions can be handled by more than one Blade, and thus the system is very
resilient to failures.
The performance-intensive tasks are distributed to multiple Blades. Flexi ISN has
excellent performance and capacity, since one system can have as much as 10
processing units.
Module contents
Module Objectives
Hardware
Software
GUI
Network Interfaces

TSC Chassis
Telecommunication Server Chassis (TSC)

Single or dual chassis configurations in Flexi
ISN 4.0
Card Cage (slots) for 14 Blades
Backplane
Power Entry Modules
Inlet Air Filter
Blank Blade Filler Plates
Fan and Display Module (FADM)

The Flexi ISN is built into a chassis. The Telecommunication Server Chassis (TSC)
provides a holder for the actual processing units (Blades). Maximum 14 units can be
installed in it, but some of the units have a dedicated function other than processing: the
so called Switch Blades and Hard Disk Blades do not run IPSO or any software
applications. The maximum number of Blades which can be used for processing in Flexi
ISN is therefore 10.
The Chassis has its own power entry modules. The backplane in the Chassis provides
the physical connections between the blades.
Chassis cooling is provided by a separate cooling unit installed in the top. This unit is
called Fan and Display Module (FADM) (Figure 4). It has multiple cooling fans, as well as
a small status display for system messages.
Cabinet
Cabinet body (grounding

parts, side panel set,
adjustable feet,
installation accessories)
Can house four chassis
Rack dummy panels
Chassis support brackets
Cable storage shelf
Anti-topple bracket
Door set (optional)

The rack where the chassis is installed is Cabinet. The Cabinet body comes with
grounding parts, side panel set, adjustable feet, as well as the installation accessories.
Other items provided for neat and stable installations are rack dummy panels, chassis
support brackets, a cable storage shelf, and an anti-topple bracket. An optional door set is
also available.
One Cabinet accepts four chassis in total.
Blades
Blades in Flexi hardware are plug-in units (field replaceable units)

Flexi ISN uses the following blade types:
CPI1 Management Blade CPI1 Blades different in

software configuration
CPI1 Service Blade and network connectivity
CPI1 Interface Blade only, otherwise they are
similar
HDF1-C Hard Disk Blade
SWSE-A Switch and Service Blade

The blades can have different functions which are affected by both hardware and
software. The CPU Blades are the processing units. They can be used in different roles.
They are different in software configuration and network connectivity only.
There are also other blades which have an embedded function: the Hard Disk Blade and
the Switch Blade. The features and differences of the blades are explained in the
following chapters.
A different number of blades are used in different element configurations. A number of
dummy blades are inserted into the empty slots to ensure proper ventilation.
CPI1 Blade
CPI1 Blade is a processing unit

PMC slot in CPI1 accepts a GIPMC (optical) P1
P1
or ETHPMC (copper) network interface PS LINK

PS LINK
adapter for external connectivity in Interface P2 P2
and Management Blades

All other connections via chassis backplane USB USB USB
PMC
PMC slot
slot GIPMC
GIPMC SER SER SER
PORT LINK PORT LINK PORT LINK

STATE STATUS STATE STATUS STATE STATUS
LAN A LAN A LAN A
LAN B LAN B LAN B
RESET RESET RESET
POWER POWER POWER
STATE STATE STATE
HOT SWAP HOT SWAP HOT SWAP
HOTSWAP HOTSWAP HOTSWAP

ENABLE ENABLE ENABLE
CPI1 CPI1+ CPI1+

ETHPMC GIPMC

The CPI Blade is its own processing unit, capable of running an operating system. In Flexi
ISN, each CPI Blade is running its own instance of IPSO. The PMC slot in CPI Blade
accepts a GIPMC (optical) or ETHPMC (copper) network interface adapter for external
connectivity. All other connections to a CPI Blade take place via the chassis backplane.
Depending on which application software components the CPI Blade is running, and
whether it also has additional network interfaces installed in the PMC expansion slot, it
can have three different purposes in Flexi ISN system:
Management Blade
Service Blade
Interface Blade
NOTE: There are different revisions of CPI1 blade hardware (CPI1, CPI1-A, -B and C).
Always check the compatibility of various versions before replacing HW.
HDF1-C Blade
Mass storage unit (300

GB)
Connects its hard drive
to the FC-AL bus
Configurable FC-AL
address
HD activity
HD fault
Power
State
Hot
Swap
HotSwap
Enable
HDF1

The Hard Disk Blade includes a hard drive. Access to the Hard Disk Blade takes place via
a Fibre Channel bus (FC-AL) in the Flexi ISN backplane. In theory, any blade installed in
the system has a physical access to the Fibre Channel bus and thus the Hard Disk Blade,
but in Flexi ISN only the Management Blade utilises the disk. The HDF1 Blade has a
configurable FC-AL address. The Management Blade recognizes the HDF1 disk from its
FC-AL address.
SWSE-A Blade
SWSE-A provides internal CLASS 1 LASER PRODUCT
communication buses
EN:60825-1:1994
FC0
Backplane Ethernet switch TX
RX
FC1
FC-AL hub
FC bypass
S4 S3 S2 S1
S4 S3 S2 S1
IPMB
S4 S3 S2 S1
FC1 FC0
Eth MP
Runs embedded Linux OS TX GbE
Installed in dedicated slots 7 & 8

RX P1
PS LINK
GbE
Interconnections between
TX
P2
RX
PS LINK
chassis (dual chassis mode) ISN ISN ISN ISN

TX
RX
GbE
P3
LINK
SW SW SW SW
PS
TX GbE
P4
RX
PS LINK
IPSO IPSO IPSO IPSO

RESET
POWER
CPU_1 CPU_2 CPU_3 CPU_N STATE
HOT SWAP
HOT SWAP
i/f i/f i/f i/f i/f i/f i/f i/f i/f i/f ENABLE

The backplane switch is provided by the Switch Blade. SWSE-A hardware is used in Flexi
ISN. There are two Switch Blades installed which makes it possible to have redundant
connection between the CPU Blades. The Switch Blade has a pre-installed Linux
operating system running, but it does not run any Flexi ISN software applications.
Hardware configurations
Hardware Dual
Entry Medium Large
configuration chassis
Management Blades 2 2 2 2
Hard Disk Blades 2 2 2 2
Service Blades 2 3 4 13
Interface Blades 2 3 4 7
Switch Blades 2 2 2 4

Flexi ISN supports three different hardware configurations (Table 1). All configurations
are built into a single chassis. Positioning of the Blades into the slots in chassis is
incremental: when upgrading to a bigger HW configuration, the already installed Blades
do not have to be moved.
Entry level configuration can support up to simultaneous 333,000 PDP contexts with
maximum 333 Mbit/s throughput (with 512 byte nominal packet size).
Medium configuration can support up to simultaneous 666,000 PDP contexts with
maximum 666 Mbit/s throughput (with 512 byte nominal packet size).
Large configuration can support up to simultaneous 1,000,000 PDP contexts with
maximum 1,000 Mbit/s throughput (with 512 byte nominal packet size).
Dual chassis configuration can support up to simultaneous 2,000,000 PDP contexts with
maximum 5,000 Mbit/s throughput (with 512 byte nominal packet size).
Note: when the average package size is over 512B the throughputs of different Flexi-ISN
configurations are bigger than above mentioned. E.g. the maximum throughput of the
large Flexi-ISN configuration is 2.5 Gbit/s, which can be reached when the packet size is
1460B.
Hardware configuration: Entry
Management Blades
Interface Blades Hard Disk Blades Service Blades
CPI1 with ETHPMC

CPI1 with ETHPMC
CPI1 with GIPMC
CPI1 with GIPMC
SWSE-A
SWSE-A
HDF1
HDF1
CPI1
CPI1
02 03 05 06 07 08 09 10 11 14

Hardware configuration: Medium
Management Blades
CPI1 with ETHPMC

CPI1 with ETHPMC
CPI1 with GIPMC
CPI1 with GIPMC
CPI1 with GIPMC

SWSE-A
SWSE-A
HDF1
HDF1
CPI1
CPI1
CPI1
01 02 03 05 06 07 08 09 10 11 12 14

Hardware configuration: Large
Management Blades
CPI1 with ETHPMC

CPI1 with ETHPMC
CPI1 with GIPMC
CPI1 with GIPMC
CPI1 with GIPMC

CPI1 with GIPMC
SWSE-A
SWSE-A
HDF1
HDF1
CPI1
CPI1
CPI1
CPI1
01 02 03 04 05 06 07 08 09 10 11 12 13 14

Dual chassis layout
FADM-A
16 17 18 19 20 21 22 23 24 25 26 27 28 29
P P P
M M M
C C C
SB IB IB SB SB SB SW SW SB SB SB IB SB SB
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
SWSE-A
SWSE-A
FADM-A
1 2 3 4 5 6 7 8 9 10 11 12 13 14
P P P P P P
M M M M M M
C C C C C C
SB IB IB SB MB HD SW SW HD MB SB IB IB SB
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
CPI1-B/C
SWSE-A
SWSE-A
HDF1-C
HDF1-C

The two chassises are interconnected via the SWSE-A blades on slots 7 and 8. Both the
Fibre Channel and Ethernet buses are extended to the other chassis with the external
cabling between the SWSE-As.
Upgrade to Dual Chassis Configuration
Upgrade Paths
Large Flexi ISN based on CPI1-B

or CPI1-C blades can be extended
to a dual chassis Flexi ISN
CPI1-B / CPI1-C
Two large Flexi ISNs based on

CPI1-B or CPI1-C blades can be
upgraded to one dual chassis Flexi
ISN with minor HW changes
CPI1-B / CPI1-C
Flexi ISN based on CPI1 or CPI1-

A blades cannot be extended to a
dual chassis Flexi ISN
CPI1 / CPI1-A
Flexi ISN Configuration Alternatives in FI 4
Configuration Entry: Medium: Large: Dual Chassis:

2 IB + 2 SB 3 IB + 3 SB 4 IB + 4 SB 7 IB + 13 SB
PDP contexts 330 k 660 k 1M 2M
Throughput 330 Mbps 660 Mbps 1 Gbps 5 Gbps

Positioning Entry level for Extension option Ideal for most High capacity
Greenfield and for operators small and network element
small operators with slow growth medium sized for operators
operators with fast traffic
growth and large
networks.

Module contents
Module Objectives
Hardware
Software
GUI
Network Interfaces

IPSO 3.9.4NET operating system
Manages the platform

User Space
Provides IP routing
functionality ISN SW
APP1 APP2
Component
Hosts applications,
like ISN software
Provides a IPSO daemon IPSO daemon IPSO daemon
management interface
Runs in all CPI Blades
while one of the Kernel
blades will act as a
Loadable
central Management IP
kernel
Packet System Device
Stack forwarding control drivers
Blade for the ISN modules
Solid border: IPSO

Dotted border:
Application net i/f net i/f CPU HD

Flexi ISN 3.2 uses IPSO 3.9.2NET operating system. IPSO provides platform
management, IP routing and forwarding functions, and hosts the upper layer applications.
IPSO operating system is running in each CPI blade in Flexi ISN. One of the blades, the
Management Blade, handles the configuration of the complete ISN. It also takes care of
configuring the blades to run the specific software components for full ISN functionality.
Management Blade functions
Centralised functions in platform

Runs O&M system
Handles disk access
Provides management interface to external control systems
Voyager
NetAct
Handles alarms
Delivers OS image and configuration data to other CPI1 Blades
Handles IP routing and distributes forwarding tables to other
CPI1 Blades
Centralised functions in ISN application
CDR sending interface to Charging Gateways (Ga)
Lawful interception interface (X)
IP address pool management for PDP contexts
The Management Blade is running the functions which are centralised for the whole Flexi
ISN system. The centralised functions in Flexi ISN platform for the Management Blade
are:
Runs O&M system
Handles disk access
Provides management interface to external control systems, like Voyager, NetAct, and
CNSM
Handles alarms
Delivers OS image and configuration data to other CPI1 Blades
Handles IP routing and distributes forwarding tables to other CPI1 Blades
In Flexi ISN application level the centralised functions for the Management Blade are:
CDR sending interface to Charging Gateways (Ga)
Lawful interception interface (X)
IP address pool management for PDP contexts
Loading IPSO from disk
All CPI1 Blades run IPSO 3.9.4NET

Only Management Blades access the disks and load IPSO from there
IPSO
HD
CPU_5 CPU_11 CPU_12 CPU_14
FC- FC- FC- FC- FC-

AL AL AL AL AL

The Management Blade is accessing the hard drive directly via FC-AL bus. The
Management Blade is able to boot its operating system from disk. The other Management
Blade does the same, using its own HDF1 hard disk.
Loading IPSO from internal network
Other CPI1 Blades run Diskless IPSO (IPSO-DL)

IPSO-DL is booted from internal backplane network with PXE
Management Blade serves the DL image with dhcp6 and tftp6
IPSO IPSO-DL IPSO-DL IPSO-DL

HD
FC- FC- FC- FC- FC-

Eth Eth Eth Eth
AL AL AL AL AL

The diskless blades are able to load their operating systems after the Management Blade
has booted up. The Management Blade acts as a dhcp6 and tftp6 server in the internal
backplane network. The diskless blades load their OS images via the backplane network.
Handling configuration data
Configuration data is kept on disk by the Management Blade

Other CPI1 Blades fetch their configuration via internal network with
proprietary management protocol
slot11/config
config config config
slot12/config IPSO IPSO-DL IPSO-DL IPSO-DL
HD
slot14/config CPU_5 CPU_11 CPU_12 CPU_14
FC- FC- FC- FC- FC-

Eth Eth Eth Eth
AL AL AL AL AL

The Management Blade provides all configuration interfaces (Voyager, CNSM, SNMP,
and CLISH). It also keeps the configuration data on the hard drive. The operating systems
on the diskless Blades get their configuration parameters delivered from the Management
Blade whenever necessary.
Management Blade and HDF1 redundancy
Management Blade forms a pair with one HDF1 and runs active
The other MB uses another HDF1 and remains standby
If anything fails inside a pair, there is switchover to the other pair
Active Standby
IPSO IPSO
HD HD
CPU_5 CPU_10
FC- FC- FC- FC-

Eth Eth
AL AL AL AL

The Management Blade in slot 5 forms a pair with the HDF1 in slot 6. This pair runs then
active. The other Management Blade in slot 10 uses another HDF1 in slot 9 and remains
standby. If anything fails inside a pair either in the CPI1 Blade or HDF1 Blade the
system switches over to the other pair. That is, a hard drive failure always triggers a CPI1
switchover and vice versa.
The system frequently synchronises the hard drive and CPI1 state information to the
standby pair.
O&M network interface redundancy
The Management Blades share their IP address

The interfaces must be connected to the same network
Interface configuration parameters are automatically mirrored by the
system
Only the active Blade interface has its link up
In switchover, the new active Blade sends Gratuitous ARP (G-ARP)
message to advertise the interface change
The neighbouring L2 switch must perform its MAC table update when
switchover occurs
Other directly connected network elements like L3 routers must
update their ARP table similarly

The Management Blade has at least one network interface active for providing a
management connection to the system. When the standby pair switches over to active, it
also activates the IP address previously used by the active Management Blade.
Because the Management Blades share their IP address, their interfaces must also be
connected to the same network. Interface configuration parameters are automatically
mirrored by the system.
Only the active Management Blade interface has its link up. In switchover, the new active
Blade sends Gratuitous ARP (G-ARP) message to advertise the interface change. The
neighbouring L2 switch must perform its MAC table update when switchover occurs.
Other directly connected network elements like L3 routers must update their ARP table
similarly.
O&M network interface in switchover
Active Standby Failed Active!
IPSO IPSO IPSO IPSO
Eth Eth Eth Eth
0/23 0/24 0/23 G-ARP 0/24
MAC_addr switchport
MAC_addr switchport
MAC_blade5 0/23
MAC_blade10 0/24
MAC_addr IP_addr MAC_addr IP_addr

MAC_blade5 IP_OM MAC_blade10 IP_OM

Service Blades
Distributed processing
Application specific tasks
PDP context handling and GTP tunnelling
Traffic analysis
Charging counters
Policy control
No direct external connections, all communication via
backplane

The Service Blades are running tasks which are performance and capacity intensive.
With distributed processing, the system becomes easily scalable by increasing the
number of processing units.
The important application specific tasks which are handled by the Service Blades are:
PDP context handling and GTP tunnelling
Traffic analysis
Collecting charging information
Policy control (Gx interface functionality)
The Service Blades do not have external connections, so they are entirely relying on the
backplane communications for data exchange.
Interface Blades
External network connections via GIPMC or ETHPMC

IP connectivity
Application traffic usually with common loopback IP
Traffic forwarding to/from Service Blades
High availability options:
Dynamic IP routing
L2 RAG (Redundant Aggregation Group)
Load balancing for application traffic

The Interface Blades provide the external network connections via GIPMC or ETHPMC
interface adapters.
All traffic in Flexi ISN is IP based. The Interface Blades have their own IP addresses for
example for the purpose of advertising dynamic IP routes, but most importantly they are
acting as forwarders towards the common loopback IP address in the Flexi ISN. The
application traffic like GTP usually takes place with this common loopback IP address.
The high availability options in Interface Blades are:
Dynamic IP routing
L2 RAG (Redundant Aggregation Group)
Dynamic IP routing is best done with OSPF protocol. It provides fast convergence in
failure cases, is multi-vendor compatible, and also supports traffic sharing when multiple
interfaces and Interface Blades are used.
L2 redundancy is targeted primarily for those environments where dynamic IP routing is
not feasible. With L2 RAGs it is possible to combine two physical interfaces into a single
aggregate interface. Behaviour of this function is similar to the interface redundancy
model of the Management Blades.
The Interface Blades automatically support load balancing for application traffic inside
Flexi ISN system. They play important role in distributing the application traffic and PDP
contexts to the multiple Service Blades. The number of Interface Blades is equally
important to the number of Service Blades in terms of performance, since they also have
to recognise the individual PDP contexts and have a database of them in their memory.
To guarantee good service to the mobile users, their packets should be switched as fast
as possible. Multiple Interface Blades help with this.
Flexi ISN application
Flexi ISN application runs in all CPI1 Blades

It is loaded similarly to IPSO and configuration data
ISN ISN ISN ISN

SW SW SW SW
IPSO IPSO-DL IPSO-DL IPSO-DL

HD
FC- FC- FC- FC- FC-

Eth Eth Eth Eth
AL AL AL AL AL

The Flexi ISN 3.2 application package is installed and activated in each CPI Blade in the
Flexi ISN system.
The Flexi ISN system and application functionality is distributed into multiple processes,
which can be running in one or more CPI Blades. The software components will run as
application processes in the IPSO operating system in each blade, or in some cases as
kernel modules in IPSO.
For monitoring the important applications functions and their high availability, it is possible
to check the status for the following software components using the graphical user
interface.
Flexi ISN system and application components 1/2
Component Function
Run time database that holds mainly the statistical
pmd data. The pmd task is active on the service and
management blades.
Maintains static routes that the Flexi ISN creates for
routemgr access points of the type Normal IPv4, IPIP/GRE (not
'All'), Normal IPv6, and 6in4.
tracer Collects tracing data.
ippoold Allocates dynamic IP addresses for mobiles.

The charging data record (CDR) sender always runs
on the management blade. The CDR role runs in the
active or standby mode, so there must be two
ggsncs instances running if high availability (HA) is desired.
The CDR role on the active management blade will
always try to be the active one.
Lawful Interception Extension functionality.
lied Communicates with LIG.

Pmd: Sending it a SIGUSR1 signal can dump the contents. First find the pid with the command ps -ax | grep pmd and
then use kill -USR1 pid. By default, the content is printed in the file /var/tmp/pmd_dump.txt.
The blade where this component (ippoold) runs is providing the dynamic IP address pool
for the Access Points. The IP pool role runs in the active or standby mode in the
Managements Blades: the active Management Blade runs the active IP pool role.
The blade where CDR sender (ggsncs) runs is responsible for sending Charging
Records (CDRs). The CDR role runs in the active or standby mode. One CDR role will
always be enabled on the management blade. The CDR role on the active management
blade is the active one. If it fails, the process on the standby Management Blade switches
to active.
Flexi ISN system and application components 2/2
Component Function
Monitors the uniqueness of all the SGSN tunnel endpoint identifiers (TEID) and
NAS accounting session identifiers (ASID). In addition, the conflict manager
sends GTP echo messages to all SGSNs that have created PDP contexts to
the Flexi ISN system, and checks the recovery identifiers in the echo replies.
If the same SGSN TEID or NAS ASID appears twice in Flexi ISN, this
indicates that signalling messages have not been delivered successfully to
conflictd Flexi ISN, and that obsolete sessions are still present in Flexi ISN. The conflict
manager is responsible for mandating the service blades to remove the old
and obsolete sessions. Whenever the conflict manager commands a service
blade to terminate a session, it writes a log entry.
The conflict manager commands the service blades to remove all PDP
contexts originating from an SGSN if the recovery identifier of the SGSN
changes, or the SGSN does not respond to the GTP echo requests.
This is the Flexi ISN main process. It performs the following functionalities:
tunnelling, signalling, Quality of Service, and charging This process should
ggsntunnel always be running.
The GGSN server task is active on the service blades.

The conflict manager conflictd monitors the uniqueness of all the SGSN Tunnel Endpoint
Identifiers (TEIDs) and NAS Accounting Session Identifiers (ASIDs) within the system.
The conflict manager is also responsible for sending GTP echo messages to all SGSNs
that have created PDP contexts to the Flexi ISN system. It then checks the recovery
identifiers in the echo replies. If the conflict manager identifies obsolete sessions present
in Flexi ISN, it requests the service blades to remove them. A log entry is written in such a
case. The conflict manager runs on the active management blade in the Flexi ISN.
Components for proxy analysis
Component Function
ita_httpd HTTP/WAP2 Analyser
ita_wapd WAP1.x Analyser
ita_rtspd RTSP Analyser
ita_smtpd SMTP Analyser
ita_ftpd FTP Analyser

The proxy analysis part of Flexi ISN application functionality is handled by the following
application processes:
ita_httpd HTTP/WAP2 Analyser
ita_wapd WAP1.x Analyser
ita_rtspd RTSP Analyser
ita_smtpd SMTP Analyser
ita_ftpd FTP Analyser
These processes run in Service Blades only. They are needed if Flexi ISN is running in
service aware mode, and if proxy services are used.
Optional P2P modules
All CPU Blades are running Flexi ISN base software application
The Service Blades are running the optional P2P SW modules
Pluggable Protocol Modules (PPMs)
NOTE: Since Flexi ISN 4.0, a 3rd party deep packet inspection suite (Sandvine)
can be integrated with FI for P2P detection
OS P2P P2P
image SW SW
SW
ISN ISN ISN ISN ISN
SW SW SW SW SW
Config
data
IPSO IPSO-DL IPSO-DL IPSO-DL IPSO-DL
files
HD CPU 5 CPU 2 CPU 3 CPU 11 CPU 14
FC- FC- FC- FC- FC- FC-

Eth Eth Eth Eth Eth
AL AL AL AL AL AL

The L7 traffic analysis options include a set of so called Peer-to-Peer (P2P) protocols. These
implementations of these protocols can potentially be changed often, and Flexi ISN may have to
be upgraded thereafter to guarantee compatibility. To help in this, the analysis functions are
carried out by Pluggable Protocol Modules (PPMs), which can be upgraded separately whenever
needed.
P2P software components in Service Blades
Component Function
PPM_bittorrent.o BitTorrent
PPM_dc.o Direct Connect
PPM_emule.o eMule/eDonkey
PPM_fasttrack.o FastTrack
PPM_msn.o Microsoft Messenger
PPM_oscar.o AOL Oscar
PPM_sip.o SIP
PPM_skype.o Skype
PPM_xmpp.o XMPP
PPM_ymsg.o Yahoo Messenger

Each PPM module analyses a specific P2P application. The PPM modules are loaded dynamically
to IPSO kernel. You can verify which modules have been loaded with the modstat command:
# modstat
Type Id Off Loadaddr Size Info Rev Module
DEV 0 97 bd977000 27e1 bda361d0 1 kgtp
MISC 1 0 be3ae000 0008 be3af050 1 PPM_bittorrent
MISC 2 0 be3b1000 0008 be3b2090 1 PPM_dc
MISC 3 0 be3ba000 000c be3bc050 1 PPM_edonkey
MISC 4 0 be43a000 0008 be43b090 1 PPM_fasttrack
MISC 5 0 be43e000 0008 be43f130 1 PPM_msn
MISC 6 0 be441000 0008 be442050 1 PPM_oscar
MISC 7 0 be447000 0015 be44b730 1 PPM_sip
MISC 8 0 be44f000 000d be451090 1 PPM_skype
MISC 9 0 be456000 0008 be457070 1 PPM_xmpp
MISC 10 0 be459000 0008 be45a050 1 PPM_ymsg
#
Module contents
Module Objectives
Hardware
Software
GUI
Network Interfaces

Voyager management interface
Flexi ISN can be managed by using Voyager interface

Flexi ISN can be managed via Voyager, which is the traditional management interface for
IPSO based systems.
Flexi ISN configuration
Management
Blade is used to
manage the
configuration of the
whole ISN
Switch Blade and
Hard Disk Blade
configuration need Management
not be managed Blade Voyager
as they are strictly
part of the
embedded
hardware
Switch Service Service Interface Hard Disk

Blade Blade 1 Blade 2 Blade 1 Blade

As the Management Blade provides the Voyager Interface, the top Voyager level is really
the Management Blade plus the common parameters for the complete Flexi ISN system.
The common parameters are automatically delivered to the other relevant Blades, so the
administrator does not have to worry about it.
Navigating to CPI Blade configuration

To configure parameters directly for the other Blades, it is possible to navigate to each
individual CPI1 Blade configuration, but the options here are restricted to those which can
really be necessary.
Module contents
Module Objectives
Hardware
Software
GUI
Network Interfaces

SWSE-A Blade
SWSE-A has physical interfaces on

the front panel
CLASS 1 LASER PRODUCT
EN:60825-1:1994
FC0
The optical connectors are logically TX
RX
FC1
part of internal Ethernet backplane
FC bypass
S4 S3 S2 S1
S4 S3 S2 S1
and FC-AL bus, and must not be S4 S3 S2 S1
FC1 FC0
Eth MP
used in single chassis

configuration TX
RX
GbE
P1
In dual chassis mode, the external

PS LINK
TX GbE
P2
Ethernet ports are used for

RX
PS LINK
connecting the chassises TX
RX
PS LINK
GbE
P3
together TX GbE
P4
The RJ-45 Ethernet port is

RX
PS LINK
RESET
connected to the SWSE-A host POWER
STATE
operating system, and can be used HOT SWAP
HOT SWAP
ENABLE
for its maintenance

The SWSE-A switch Blades provide the backplane communication buses for Ethernet
and FC-AL. They also have connectors in the front plane, which are directly connected to
these backplane buses. Although they are physically external, they connect to strictly
internal networks and therefore must not be used. The external connections to Flexi ISN
system are always provided via GIPMC and ETHPMC adapters in the CPI1 Blades.
The RJ-45 connector in SWSE-A front panel is the 10/100 Mbit/s Ethernet port connected
to the SWSE-A host operating system. By default, the host OS port has IP address
10.0.0.1, and it can be used for maintenance purposes, e.g. firmware upgrades if
necessary. It is best used with a cross-over cable instead of connecting to any O&M
networks directly.
CPI1 Blades
All CPI1 Blades have two physical

CPI1 + GIPMC
network interfaces connected to
backplane (eth1 + eth2)
OS backplane communication IPSO
uses aggregate interface (ae0 or
sfab0) CPU_5
O&M and Interface Blades have
two additional physical interfaces GIPMC
in GIPMC or ETHPMC (eth-s1p1
+ eth-s1p2) sfab
ae0
0
eth- eth-
s1p1 s1p2
eth1 eth2

All CPI1 Blades have two physical network interfaces connected to backplane (eth1 +
eth2). The Flexi ISN system never uses these interfaces directly, since communication
would not be resilient. OS backplane communication uses aggregate interface (ae0 or
sfab0). This aggregate interface uses either of the physical backplane interfaces.
Management and Interface Blades have two additional physical interfaces in GIPMC or
ETHPMC (eth-s1p1 + eth-s1p2).
Backplane interface details (1/2)
Aggregate backplane interfaces for internal management are

separated from other traffic by
Having VLAN tagging enabled
Belonging to a separate routing instance internal_mgmt
Aggregate i/f addressing is automatic
Aggregate i/f addresses for the diskless CPI1 Blades:
fe80::550N (sfab0)
fe80::N (ae0)
where N=slot#
E.g., fe80::2 and fe80::5502 both refer to slot 2 backplane interfaces

Aggregate backplane interfaces for internal communication and management are

separated from other traffic, especially from the routing domains where end user traffic is
being carried. These interfaces have VLAN tagging enabled, and they belong to a
separate routing instance internal_mgmt. This routing instance is automatically created
by the system, and it is hidden from the graphical user interface.
The aggregate interface IP addresses are automatically configured by Flexi ISN. For the
diskless CPI1 Blades the addresses are:
fe80::550N (sfab0)
fe80::N (ae0)
where N = slot number.
7.7.7.1 (ae0c1, VLAN 7, active Blade in slot 5, in SWSE-A slot 7 segment)
8.8.8.1 (ae0c2, VLAN 8, active Blade in slot 5, in SWSE-A slot 8 segment)
7.7.7.2 (ae0c1, VLAN 7, standby Blade in slot 10, in SWSE-A slot 7 segment)
8.8.8.2 (ae0c2, VLAN 8, standby Blade in slot 10, in SWSE-A slot 8 segment)
The host operating system of SWSE-A Blades is also connected to the backplane with IP
addresses 7.7.7.7 (slot 7) and 8.8.8.8 (slot 8). Usually it is not necessary to access the
SWSE-A host operating system at all. Neither is it manageable via graphical user
interface, since it is considered as part of hardware platform from Flexi ISN point of view.
For the Management Blades the interfaces addresses are:
fe80::5500 (sfab0)
fe80::N (ae0, N = slot number)
Backplane interface details (2/2)
Aggregate i/f addresses for the Management Blades:

fe80::5500 (sfab0)
fe80::N (ae0)
fe80::110N
fe80::fe (active MB)
7.7.7.1 (ae0c1, active)
8.8.8.1 (ae0c2, active)
7.7.7.2 (ae0c1, standby)
8.8.8.2 (ae0c2, standby)

Centralised routing
External network interfaces are exported to the Management Blade

The interfaces get a slot number identifier
CPI1 + GIPMC
CPI1 + GIPMC CPI1 + GIPMC CPI1 + GIPMC
IPSO
IPSO-DL IPSO-DL IPSO-DL
GIPMC GIPMC ETHPMC GIPMC
eth-s2/ eth-s2/ eth-s3/ eth-s3/ eth- eth- eth-s12/ eth-s12/

s1p1 s1p2 s1p1 s1p2 s1p1 s1p2 s1p1 s1p2

The diskless Blades export their external network interfaces (GIMPC and ETHPMC) to
the Management Blade. The exported interfaces get a slot number identifier. This
centralised routing facility makes it possible to handle Flexi ISN system as a single IP
router. This must be considered in network planning, since the Blades are not
independent routers, although they are all running their own instance of IPSO operating
system.
View from Management Blade
Management Blade handles the exported interfaces like its own

Thus the system behaves as a single IP router
Management
Blade ETHPMC
Exported
GIPMC from
slot 2


02 FICOM FIOM 40 Flexi ISN Architecture v1

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

02 FICOM FIOM 40 Flexi ISN Architecture v1

Загружено:

Авторское право:

Доступные форматы

Flexi ISN Architecture

Flexi ISN 4.0 Commissioning, Integration and O&M

Soc Classification level

Soc Classification level

At the end of this module the participant can:

Soc Classification level

Flexi ISN uses FlexiServer Blade

Soc Classification level

ISN ISN ISN ISN

IPSO IPSO IPSO IPSO

Soc Classification level

Soc Classification level

Telecommunication Server Chassis (TSC)

Soc Classification level

Cabinet body (grounding

Soc Classification level

Blades in Flexi hardware are plug-in units (field replaceable units)

CPI1 Management Blade CPI1 Blades different in

Soc Classification level

CPI1 Blade is a processing unit

or ETHPMC (copper) network interface PS LINK

adapter for external connectivity in Interface P2 P2

and Management Blades

PORT LINK PORT LINK PORT LINK

LAN A LAN A LAN A

LAN B LAN B LAN B

RESET RESET RESET

POWER POWER POWER

STATE STATE STATE

HOT SWAP HOT SWAP HOT SWAP

HOTSWAP HOTSWAP HOTSWAP

CPI1 CPI1+ CPI1+

Soc Classification level

Mass storage unit (300

Soc Classification level

SWSE-A provides internal CLASS 1 LASER PRODUCT

Backplane Ethernet switch TX

Runs embedded Linux OS TX GbE

Installed in dedicated slots 7 & 8

chassis (dual chassis mode) ISN ISN ISN ISN

IPSO IPSO IPSO IPSO

Soc Classification level

Soc Classification level

Interface Blades Hard Disk Blades Service Blades

CPI1 with ETHPMC

Soc Classification level

CPI1 with ETHPMC

CPI1 with GIPMC

Soc Classification level

Interface Blades Hard Disk Blades Service Blades

CPI1 with ETHPMC

CPI1 with GIPMC

Soc Classification level

Soc Classification level

Large Flexi ISN based on CPI1-B

Two large Flexi ISNs based on

Flexi ISN based on CPI1 or CPI1-

Configuration Entry: Medium: Large: Dual Chassis:

PDP contexts 330 k 660 k 1M 2M

Throughput 330 Mbps 660 Mbps 1 Gbps 5 Gbps

Soc Classification level

Soc Classification level

Manages the platform

Solid border: IPSO