Redback Networks

Engineering

CLIPS and DHCP

Enhancements

Issue Date:2008-Sep-23 21:42 a9/p9

Version: 0.3

Document ID: PM-REQ-0803

Document Status: Draft

Feature ID: FT1762

Created by: Srikanth/Chez on: May 2008

Proprietary and Confidential

 Copyright 2008 Redback Networks Inc.

All rights reserved. No part of this publication may be used or
reproduced in any form by any means without prior written
permission from Redback Networks Inc.
Document Approval
Document Approval is handled via EngDoc, the Redback document repository. Required Reviewers can
review the document on-line, make comments, and approve the document through his tool.

http://engdoc.redback.com/

Revision History

Issue Author(s) Date Description

0.1 Chez May 13, 2008 First draft for enhancing CLIPS
0.2 Srikanth May 16, 2008 DHCP enhancements
Chavali
0.3 Srikanth September 03, Removed the CLIPS enhancements as its tracked by a
Chavali 2008 different FT
Table of Contents
1 Introduction............................................................................................................................................... 5
1.1 Scope................................................................................................................................................. 5
1.2 Reference Documents........................................................................................................................ 5
1.3 Relevant Standards............................................................................................................................ 5
1.4 Terminology....................................................................................................................................... 5
1.5 Assumptions, Dependencies and Open Issues..................................................................................5
2 Feature Overview ..................................................................................................................................... 7
2.1 Market Information............................................................................................................................. 7
2.2 Typical Application(s)......................................................................................................................... 7
2.3 Cost Targets....................................................................................................................................... 7
3 Functional Requirements ......................................................................................................................... 7
3.1 DHCP Enhancements........................................................................................................................ 7
4 Management and Interface Requirements................................................................................................ 8
4.1 Configuration Requirements............................................................................................................... 8
4.2 Statistics Requirements...................................................................................................................... 8
4.3 Alarm Requirements........................................................................................................................... 9
4.4 Status, Diagnostics and Maintenance Requirements ........................................................................9
4.5 Logging Requirements....................................................................................................................... 9
4.6 NMS/EMS & Management Interface Requirements...........................................................................9
5 Collateral Requirements........................................................................................................................... 9
6 High Availability Requirements................................................................................................................. 9
7 Performance Expectations........................................................................................................................ 9
8 Standards Compliance.............................................................................................................................. 9
9 Interoperability.......................................................................................................................................... 9
10 Manufacturing & Operations................................................................................................................... 9
11 Homologation.......................................................................................................................................... 9
1 Introduction
This PRD tracks DHCP enhancements to suit Belgacom’s requirements.
DHCP Enhancements:
Belgacom uses DHCP for their VoIP client and STB devices. In their deployments SE acts as a DHCP
proxy. For OAM / troubleshooting / debugging purposes, they require opt-82 info to be displayed in the
existing show command "show dhcp relay hosts x.x.x.x".
In the current SE implementation this functionality is missing. In the absence of this functionality the
customer has to first query the DHCP server for the IP address for a certain opt-82 entry and then query
the SE to validate the address.
Therefore there is a need to enhance DHCP show commands on the SE for the ease of debugability.

1.1 Scope
This features in this FT needs to be supported on XCRP3, XCRP4 and all versions of PPA cards.

1.2 Reference Documents

Document Identifier Title, Author(s), Date

1.3 Relevant Standards

Document Name and Identifier Standards Organization

1.4 Terminology
In this document, several words are used to signify the requirements of the specification. These words
are often capitalized. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in [RFC2119].

Term Definition

1.5 Assumptions, Dependencies and Open Issues

1.
2 Feature Overview
DHCP Enhancement:
This feature requires enhancing an existing CLI show command (“show dhcp relay hosts”) to display
option 82 value and introducing a new CLI show command (TBD) to display the DHCP lease of the host
based on the input (to the show command) option 82 value.

2.1 Market Information

2.1.1 Key Customer(s)

 DHCP Enhancement: Belgacom

2.1.2 Feature Timeline

 6.1.5

2.2 Typical Application(s)

BRAS

2.2.1 Use Case2: DHCP Enhancements

Belgacom currently has to query the DHCP server to obtain the IP address of a subscriber given an
option 82 value (agent-circuit id). They then have to use the IP address to match the subscriber for
debugging purposes. This is a cumbersome task if this process has to be repeated for every subscriber.
Availability of the host’s agent circuit id on the SE helps enormously in the operations and maintenance
for the operator.

2.3 Cost Targets

 N/A

3 Functional Requirements

3.1 DHCP Enhancements

3.1.1 MUST support display of hexa-decimal formatted option 82 received in DHCP messages.

Currently there exists support for displaying ASCII formatted option 82 that is received in DHCP
messages. So it MUST be ensured that this requirement has no impact on the existing
functionality. This can be achieved by introducing a new command at a global level for dhcp and
a per relay interface level command to enable display of hex opt 82.
3.1.2 MUST enhance “show dhcp relay hosts x.x.x.x” command to display option 82
information.

An example of the output displayed MUST be along these lines:

show dhcp relay hosts 10.127.252.183
---------------------------------------------------------------------
Displaying information for host: 10.127.252.183
MAC Address : 00:02:61:08:a7:87
Circuit : 6/1 vlan-id 300
Context : IDTV
Circuit Handle : 6/1:1023:63/1/2/253
Create time : Wed Mar 28 13:30:29 2007
Type : Proxy
Server : 10.127.127.7
OPT-82 :HOST/Agent-circuit-id  this line need to be added
Lease : 5400 Ttl : 4814
giaddr : 0.0.0.0 flags : 0x5805
helper flags : 0xa Standby helper flags: 0x0
Act. File Page # : 0 Act. File Page Elem : 0
Sby. File Page # : 0 Sby. File Page Elem : 0

3.1.3 MUST provide the ability to display a DHCP lease based on that option82

This new show command CLI which is TBD MUST resemble this: show dhcp host [option-82] . The output
for this command MUST be the DHCP lease for the subscriber with the input option-82 value. The
advantages of this command is two fold:

a. For debugging purpose when a customer complaints about his connectivity The first action to be
performed is to check:

o does this customer have an IP address?

o can I ping it?

b. Based on the Phone number of the customer we can make a link to the customer port on the IP
DSLAM.
This port will give the option82 ==> Based on that option82, we can easily find back the DHCP lease of
the customer and we can troubleshoot him better.

4 Management and Interface Requirements

4.1 Configuration Requirements

4.1.1 DHCP enhancement CLI commands are described in section 3.2

4.2 Statistics Requirements

 None
4.3 Alarm Requirements
 None

4.4 Status, Diagnostics and Maintenance Requirements

4.5 Logging Requirements

 None

4.6 NMS/EMS & Management Interface Requirements

 None

5 Collateral Requirements
 N/A

6 High Availability Requirements

Function MUST be available after process restarts, XCRP switchover, card reload, SE reload and ISSU
upgrades. DDL compatibility MUST be maintained for ISSU purposes.

7 Performance Expectations

7.1.1 Feature must not impact subscriber bringup rate.

8 Standards Compliance
 N/A

9 Interoperability

10 Manufacturing & Operations

 N/A

11 Homologation
 N/A