ATTACHMENT 1

STATEMENT OF COMPLIANCE - IPNMS TECHNICAL REQUIRComplied

I. Probe Solution Functionalities
A. Port Density
1 Fixed/Rack Mounted: Minimum of 12x10GE Ports
2 Portable
2.1 1GE
2.2 10/100/1000 Ethernet
B. Should support IPv4/IPv6 - Dual Stack
C. Traffic Classification/Identification/Monitoring
1 Voice-over-IP Protocols/ Applications/ Services such
as, but not limited to, the following:
1.1 SIP

Not
Partially Remarks
Complie Complie
d
d
P

Cascaded chasis with 4 x 10GE ports can

support 12 or more ports

P
P
P
We support majority of the protocols listed
here and we also support the correlation for
VOIP
calls and analyze the traffic associated
Can identify
with the applications

1.2 H.323

Can identify and analyze the traffic associated

with the applications

1.3 MGCP

Can identify and analyze the traffic associated

with the applications

1.4 H.248/Megaco

Can identify and analyze the traffic associated

with the applications

1.5

P
AIX2

Can identify traffic associated with the

applications

1.6 SIGTRAN

Can identify and analyze the traffic associated

with the applications

1.7

Can identify traffic associated with the

applications

Skype

1.8

Can identify traffic associated with the

applications

Can identify traffic associated with the

applications

Vonage

1.9
MagicJack

1.10

Can identify traffic associated with the

applications

Can identify traffic associated with the

applications

Yahoo! /MSN messenger with voice services

1.11
GoogleTalk

P
1.12 Others (pls. specify)
2 Peer-to-Peer Applications such as, but not limited to,
the following:

more than 300 services recognized on IP

transport

2.1 BitTorrent

Can identify and analyze the traffic associated

with the applications

2.2 Gnutella

Can identify and analyze the traffic associated

with the applications

2.3

P
Napster

2.4 Others(pls. specify)

3 Streaming Protocols such as, but not limited to, the
following:

Can identify traffic associated with the

applications

edonkey, directconnect, ares, applejuice,

soulseek

3.1 RTSP

Can identify and analyze the traffic associated

with the applications

3.2 RTP/RTCP

Can identify and analyze the traffic associated

with the applications

P
3.3 Others (pls. specify)
4 Applications/Services such as, but not limited to, the
following:
4.1 Browsing

Can identify and analyze the traffic associated

with the applications

4.2 E-mail

Can identify and analyze the traffic associated

with the applications

4.3 Gaming

1 of 6

4.4

Can identify and analyze the traffic associated

with the applications

P
FTP

4.5

P
ICQ

4.6

Can identify and analyze the traffic associated

with the applications

Can identify and analyze the traffic associated

with the applications

Can identify and analyze the traffic associated

with the applications

more than 300 services recognized on IP

transport

SNMP

4.7
Chat

4.8
TFTP

4.9 Others (pls. specify)

5 Encapsulation/ Tunneling Protocols such as, but not
limited to, the following:
5.1

Can identify traffic associated with the

applications

P
MPLS (strip up to what Label - 1st, 2nd, so on and so forth)

5.2

Can identify traffic associated with the

applications

IPSec is encrypted protocol, we will not be

able to do content analysis over IPSec,
however we can still generate IPDR for this
analysis

L2TP

5.3
GRE/IPSec

5.4 Others (pls. specify)

6 Should allow monitoring based on, but not limited
to, the following:
6.1 Specific IP address
6.2 Specific IP address range or subnet
6.3 Specific Protocol
6.4 Specific Logical Port
6.5 Specific Logical Port Range
6.6 Specific VLAN
6.7 Specific Call/Session ID
6.8 Specific Web site/URL/URI
D. Data Collection, Translation, and Conversion
1 Can generate IPDRs for all types of Application-layer
Protocols

Yes the system supports monitoring of all the

dimensions as mentioned below.
P
P
P
P
P
P
P
P
P

2 Generated IPDR should contain, but not limited to,

the following:
2.1 Originating, destination, & forwarding
ID/Telephone no.

2.2
2.3
2.4
2.5
2.6
2.7

Originating, destination, & forwarding IP addressP

P
URI/URL
P
Source and Destination Ports
P
Time stamp (start/end time)
P
Call duration or total conversation time value
P
Type of Content/Codec (for Streaming Media)
2.8 Autonomous System (AS) no. (Source & Destination)
P
P
2.9 Call Type
P
2.10 Gateway ID/Hostname
P
2.11 Subscriber ID
P
2.12 Unique Call/Session ID
2.13 Call disposition/completion code (e.g.
P
successful or unsuccessful)
2.14 Call Setup Duration
2.15 Tear Down Duration
2.16 Post Dialing Delay
2.17 Average Packet Latency
2.18 Bandwidth Utilization
2.19 Others (pls. specify)
3 Generated IPDRs must already be correlated
especially for asymmetric traffic

P
P
P
P
P
P
P

Yes we support both Correlated and noncorrelated Detail records

4 IPDRs can be extracted and exported on-demand or P

based on a user-defined/adjustable schedule

2 of 6

5 Generated IPDRs can be exported to a third-party

system in the following formats:

ASDR stream function enables continuous

streaming of detail records to an external
database server or file system

P
5.1 Binary
P
5.2 ASCII
E. Data Processing and Analysis
P
1 Allows real-time and historical call trace
2 Selective capture and playback of VoIP sessions for QP
3 Allows threshold setting on traffic parameters (ex., P
No. of Conversations/Transactions, Bandwidth
Consumed, etc.)
4

Export using PCAP format

CSV file export is available

P
For encrypted traffic if the PLDT can provide the
encryption key then we can decrypt and analyse the traffic

Able to decrypt/decode all encrypted /coded IP traffic particularly V

5 Can identify, interpret and differentiate VoIP call

scenarios
such
as:(IP/Soft Phone to IP/Soft Phone)
5.1
PC to PC
calls
5.2
5.3
5.4

Soft/IP Phone to PSTN/CMTS

PSTN/CMTS to Soft/IP Phone
PSTN/CMTS to PSTN/CMTS over IP

P
P
P
P

F. Reports Generation
1 Should allow user-customized/drag-and-drop reports P

We support all the reports mentioned here,

and more, please check the attached reports
document for more details

2 Should provide Daily Usage Profile report containing,

but not limited to, the following:
2.1 Source IP address
2.2 Destination IP address
2.3 URL/URI
2.4 Protocol (ex., HTTP, SIP, BitTorrent, etc.)
2.5 Total no. of Conversations/Transactions
2.6 Bandwidth Consumed
2.7 Total Duration
3 Should provide Daily Browsing Profile Report
containing, but not limited to, the following:

P
P
P
P
P
P
P

P
3.1 Source IP address
P
3.2 Destination IP address
P
3.3 URL
P
3.4 No. of Conversation
P
3.5 Total Duration
4 Should provide QoS Measurement Report containing,
but not limited to, the ff:
4.1 Host IP address
4.2 Completion rate
4.3 Subscriber busy
4.4 Congestion Rate
4.5 Address Incomplete
4.6 Jitters
4.7 Packet Loss
4.8 Delay
4.9 MOS
4.10 Others (pls. specify)
5 Should provide Incomplete TCP Session Requests
Report (showing the Source and Destination IP
that Suspected
can be used
to detect
possible
6 addresses)
Should provide
Malicious
Traffic
Report
D/DOS attacks.
7 Real-time and long-term graphs/reports contains:

We support all the QoS Measurements

mentioned here, and more, please check the
attached KPI document for more details

P
P
P
P
P
P
P
P
P
P
malformed packets, specific port attack
We support all the reports mentioned here,
and more, please check the attached reports
document for more details

7.1 Inbound, outbound and total bandwidth statistic P

per monitored link; can be aggregated or
individual.
P
7.2 Live
connections and new connections-persecond statistic per monitored link
7.3 In and out packets statistic
7.4 Protocol/Application Distribution
7.4.1 No. of Host

P
P

3 of 6

7.4.2 Bandwidth Consumed

7.5 Most Active Protocols
7.6 Most Active Internal/External Hosts
7.6.1 No. of Calls/Sessions
7.6.2 Duration
7.7 Most Active Conversations
7.8 Most active VLANS
7.9 Web Destinations
7.10 Typical time report
7.11 Internet Users
7.12 Others (pls. specify)
8 Can generate a report containing users/hosts that
violated set thresholds.
9 Can provide visibility of application traffic in realtime online mode refresh every second, minute,
etc.
10 hour,
Can monitor
real-time traffic or long-term usage,
based on specific date, selected period, or relative
last
n hour(s),
or month(s).
11 time
For long
term
graphs,day(s)
data can
be displayed by Rate
(example - Mbps) or Volume (example - Mbytes).
12 Schedule of reports can be adjusted per day, per
week, or per month
13 Reports can be exported to a third-party system in
CSV format
14 Reports can be generated and exported on-demand
or on user-defined/adjustable schedule (ex. Daily or
Hourly)
G. Built-in
Management System/Application

1
2
3
4

Should be web based

Should allow Command Line Interface (CLI)
Should be SNMPv3 compliant
Can provide the following modules/features:
4.1 Fault Management
4.2 Configuration/Provisioning Management
4.3 Performance Management - provides
status/health monitoring such as CPU, memory,
disk space, ports, links, and power supply
status.
4.4 Security Management
4.4.1 User administration
4.4.2 Event logs
4.4.3 User activity logs (audit logs) containing
the Time Stamp, User name, and the
commands
entered (login,
4.4.4 specific
All logs should
be exportable
in CSV
logout, and
creation,
modification,
or
format
should
have a retention
deletion)
period
of 3 months.

H. Allows for on-the-fly SW updates including Protocol

Decodes/Signatures of new types of traffic

P
P
P
P
P
P
P
P
P
P
P
P
P
P
Minimum generation period is 15 minutes,
Maximum is configurable for day/week/month
etc

P
P
P

Yes the solution has built-in self management

system, which supports all the functionalities
mentioned here.
P
P
P
P
P
P

P
P
P
P

II. Optical Switch Solution Functionalities

We are not proposing the optical switch

methodology, so this section will be nonapplicable at this context

A. Minimum of 72x10GE Ports (60 as 'Source Ports'

connected
to the
TAPs and interface
12 ports connected to the
B. Should
support
multimode
C. Can filter the traffic according to the type of application
or protocol
D. Can aggregate the traffic from multiple sources
E. Switching should be transparent and non-blocking
F. Should allow automatic switching between source port/s
based on user-defined schedule
G. Should support IPv4/IPv6 - Dual Stack

H. Built-in Management System/Application

1 Should be web based
2 Should allow Command Line Interface (CLI)
3 Should be SNMPv3 compliant
4 Can provide the following modules/features:

4 of 6

4.1 Fault Management

4.2 Configuration/Provisioning Management
4.3 Performance Management: provides
status/health monitoring such as CPU, memory,
disk space, ports, links, and power supply
status.
4.4 Security Management
4.4.1 User administration
4.4.2 Event logs
4.4.3 User activity logs (audit logs) containing
the Time Stamp, User name, and the
specific
commands
entered (login,
4.4.4 All
logs should
be exportable
in CSV
logout,
creation,
modification,
or
format and
should
have a retention
deletion)
period of 3 months.
I.

Allows for on-the-fly SW updates.

III. Optical TAP

A.

Minimum of 60x10GE links to be tapped

B. Passive - requires no power supply

C. Insertion Loss (please indicate)
D. Chassis and/or Rack mountable
E. 10GE-capable
F. Should support different Split Ratios

P
P
P
P
P
P

IV. General System Requirements

A. Proposed System must be complete with Probe Solution P
(Probe, Application, Server, and
Peripherals/Accessories), Optical Switch Solution (Optical
Switch, Application, Server, and
Peripherals/Accessories), and Optical TAPs
P
B. All components/elements of the Proposed
System/Solution must be compatible with each other.
C. The Vendor must provide, at no additional cost to PLDT, P
both the MIBS and APIs, which should come with
complete documentation, upon signing of the Contract.
P
Should inter-operate with existing and future Network Management
D. Systems (NMS); integration must not entail additional cost to PLDT

E. Should support synchronization with existing NTP

servers of PLDT

F. Should provide Physical Specifications & Platform

Certifications such as:
1 Physical Description/Form Factor
2 Chassis Architecture
3 Slot Configuration

P
P
P

19" rack mounted

4U
2 x 10GE Card (2 ports per card; 4 ports in
total per unit)

4 Dimensions

(175 x 437 x 650) mm (HxWxD)

Power Requirements (AC / DC)

Power Draw & Thermal Output
Weight
Rack Units (RU)
Chassis/Rack (not applicable to Portable Probes)
Agency Approvals

P
P
P
P
P
P

Optional DC 48V power supply

900W
40.8 kg
4U
19" rack
USA - UL listed, FCC Part 15; Canada CUL listed; China - CCC Mark; Europe/CE
Mark - EN 60950/IEC 60950-Compliant;
Germany - TUV Certified FCC Part 15

NEBS Compliance

5
6
7
8
9
10

11

G. Capable of data retention and dumping of historical data to external stor

1 1 month data on line and in readable format
2 With DVD-Writer or better

H. Vendor should provide:

1 Detailed Server (SW/HW) specifications required to
support the whole/complete system.
2 Details of the various software packages, licenses
and restrictions on use such as quantity of allowed
users.

P
P
P
P

Export to FTP available

5 of 6

3 Documentation detailing the implementation of

server upgrade within the Design Life whether it is
on-line or off-line.

4 Racks, KVM accessories (if required), cabling, cable

runways, conduits and other mounting devices
conforms
with
industry
standards.
I. Vendor
must be
willing
to subject
Proposed
System/Solutions to field testing (Proof-of-Concept).

V. Technical Support
Vendor should provide:
A. Minimum of 2-years Service and Parts Warranty

Please check the attached support and

services document for details

B. Training and/or Technology Transfer (for Administrators

and Users separately)
1 Provide Training Materials/Documentations via
CBT/On-Line or in DVD (for Administrators and
separately)
2 Users
Trainings
to be conducted in PLDT InnoLab

Please check the attached training document

for details
P

P
(Dansalan)
P
3 Trainings
should include modules in Installation,
Operations & Maintenance, Development, Planning,
and Engineering
4 On-the-Job/Hands-on/On-site Training during Project P
duration.
5 Good for 10 personnel per Batch; 2 Batches per
Module
C. System
(HW/SW Components) support and Design Life of up to a

P
P

minimum of 10 years (Spares/Parts & Services)

D. Service Level Agreements (SLA) for both HW and SW (i.e., Critical,

Major, and Minor)
1
9x7 On-site Technical Support
2
Response Time of 4 Hrs upon notification
3
Resolution Time of 24 Hrs. upon notificaiton
4
Repair & Retun within 20 days
5

E.

In-Country (preferably within Metro Manila) storage site for

Spares/Parts

Necessary updates (Patches, Upgrades, and Protocol

Decode/Signature updates) whenever available; no longer than 1month upon request in case Protocol Decodes/Signature update
requires development.

P
P
P
P
P
P

6 of 6