A P P E N D I X

Plug and Play Call Flow Sequence Diagrams

This appendix contains sequence diagrams for the following scenarios:

Redirection of Subscribers Using Web Proxy, page B-2

Subscribers Requesting an Unresovable DNS Name, page B-3

Cisco Subscriber Edge Services Manager Plug and Play Guide

OL-4565-01

B-1

Appendix B

Plug and Play Call Flow Sequence Diagrams

Redirection of Subscribers Using Web Proxy

Redirection of Subscribers Using Web Proxy

Gateway

Browser

Captive Portal

Web Portal

Web Proxy

1: HTTP request to configured Web

Proxy
Here the browser is making
a request to a IP address that
will not be reachable as there
is no session, or is not routable
in general.

1.1: Record source IP address,

source port, destination IP
address and destination port.
1.2:[not authenticated] //Session
tcp-redirect
1.2.1.1: Set permanent
tcp-redirection to the SESM Web
Proxy

1.2.1: Detect Web

Proxy request

1.2.2: HTTP redirect to Web Portal

1.2.2.1: HTTP request to

WebPortal via configured
Web Proxy

1.2.2.1.1: Permanent
tcp-redirection to SESM Captive
Portal unauthenticated redirection
port

The forwarded request here has the client IP address

and remote port added to the header as the Cisco
specific headers:
com-cisco-sesm-RemoteAddress: <clientOrSsgIP>
com-cisco-sesm-RemotePort: <clientOrSsgPort>

1.2.2.1.2.1: Forwarded HTTP

request to the Web Portal
1.2.2.1.2: Redirected HTTP
request to Web Proxy

1.2.2.1.2.1.1: HTTP response

to browser with authentication
page

99316

The SESM web portal uses the headers inserted by

the web proxy:
com-cisco-sesm-RemoteAddress: <clientOrSsgIP>
com-cisco-sesm-RemotePort: <clientOrSsgPort>
To determine the IP address of the client.

Cisco Subscriber Edge Services Manager Plug and Play Guide

B-2

OL-4565-01

Appendix B

Plug and Play Call Flow Sequence Diagrams

Subscribers Requesting an Unresovable DNS Name

Subscribers Requesting an Unresovable DNS Name

DNS Proxy

Gateway

Client

1: DNS request

1.1: Redirect requests to

default DNS servers

Primary DNS Server

1.1.1: Proxy request to

primary DNS server

1.1.2:[no ip address in reply]//Insert

IP address of web proxy into reply
The gateway should be configured with an open garden
server similar to this:

Where 192.168.10.1 should be the IP address of the DNS proxy

Any DNS request for a domain will match the domain config
here, so should be redirected to the DNS proxy. The DNS
proxy should forward the request to the primary DNS server.

99315

local-profile DNS
attribute 26 9 251 "O*"
attribute 26 9 251 "D192.168.10.1"
attribute 26 9 251 "R192.168.10.0;255.255.255.0"

Cisco Subscriber Edge Services Manager Plug and Play Guide

OL-4565-01

B-3

Appendix B

Plug and Play Call Flow Sequence Diagrams

Subscribers Requesting an Unresovable DNS Name

Cisco Subscriber Edge Services Manager Plug and Play Guide

B-4

OL-4565-01