User Requirement Specification (Network Service, Mobile Network Technical Support) URS Form No.: *Name: Location: *Contact No. *Request Type:
Tang, Calvin SS *Staff No: LHK 12 *Business Unit / Branch: 2883 4139 New Application Enhancement of Development Existing System Complete Section F1 for the above items
RDIS0031 CASCADE/R&D/INS Other
Firewall & Routing Configuration Complete Session F2 for the above items *Priority: *Charging related:
Business Critical Yes Complete Section B
*Duration of request:
Permanent
*Request Date: *Signature:
7/29/2008
Business Noncritical No Temporary Specify end date : ___________________ *Completion Date:
**The request will be acknowledged in 3 working days starting from the time of form submission** Section A – Requestor management approval (Non NS use) Name in block letters :
Endorsed by manager or above:
Staff Number :
Section B – BU management approval (Non NS use) Name in block letters :
Endorsed by BU manager or above:
Staff Number :
* Mandatory field
Confidential
Page 1
Effective Date on 08/05/2008 Version: 1.5
URS Form No.:
(For NS use only)
Section C Feasibility Study ( NS use only) Request:
Risk Level (High / Medium / Low): Accept Reject, reason:
Effort Estimated: Agreed Completion Date:
(man day) Planned Start Date :
Name in block letters : Handled by: Staff Number : Name in block letters :
Approved by NS Manager:
Staff Number :
Section D – Maintenance procedure and planning (Use separate sheets if needed)(optional) Action date : Impact :
Action time : Name in block letters :
Approved by NS manager:
Staff Number :
Section E – User Acceptance Test (Use separate sheets if needed) UAT:
Accept Reject, reason:
Name in block letters : Accepted by requestor: Staff Number : Name in block letters :
Endorsed by NS Management:
Confidential
Staff Number :
Page 2
Effective Date on 08/05/2008 Version: 1.5
User Requirement Specification (Network Service, Mobile Network Technical Support) URS Form No.:
Section F1 – Request detail information (Use separate sheets if needed) Description of Request / Functional Requirement: Our RADIUS servers (ydbizrad02, wdbizrad02 & imswng19) need to be added as clients to mobile RADIUS servers (10.140.22.1 & 10.140.22.2) in order to accept our proxy request.
Reason/Justification of Request: 2 new business wifi RADIUS servers (ydbizrad02 & wdbizrad02) and 1 UAT RADIUS server (imswng19) need to proxy Natvigator Everywhere RADIUS requests to mobile RADIUS servers.
Section F2(Use separate sheets if needed)
No
Source (IP address/ hostname)
Destination (IP address/ hostname)
Service (TCP/UDP Port #)
Action (Permit / Deny)
1
218.102.23.22 / ydbizrad02
10.140.22.1
1812
Permit
2
218.102.23.22 / ydbizrad02
10.140.22.2
1812
Permit
3
219.76.95.108 / wdbizrad02
10.140.22.1
1812
Permit
4
219.76.95.108 / wdbizrad02
10.140.22.2
1812
Permit
5
219.76.67.117 /imswng19
10.140.22.1
1812
Permit
6
219.76.67.117 / imswng19
10.140.22.2
1812
Permit
Other requirements (e.g. routing) 1. Secret key of RADIUS is “sawlan” 2.
New routings may need to be added into router.
Confidential
Page 3
Effective Date on 08/05/2008 Version: 1.5