Allied View Network Management System (NMS)

1. AlliedViewNetwork Management System (NMS) Dick Willson

2. MPLS/IP Core Network Video Conferencing Access Network Streaming Server PBX PSTN/Mobile Gateway VoIP Call Server Multi-Service Access Platform Gaming Server Router Internet Intranet/VPN Ethernet Protected Transport Multi-Service Access Network Service demark Network Management System Application Servers Video Conferencing Control Unit Ethernet Ethernet Network Management & Provisioning Telephone wire (Copper) iMAP iMG Fiber Optics

3. Fibre P2P iMAP Ethernet GbE Access Switch FTTB CO iMAP OLT Fibre P2MP GbE ONU Technology vs distance FTTH Fibre 100/100 Mbps Fibre P2MP VDSL Modem ONU GbE FTTC Copper Twisted Pairs GbE OSP iMAP ADSL VDSL 50/10 Mbps VDSL Modem FTTN FTTN VDSL iMAP ADSL 25/3 Mbps ADSL Modem ADSL2+ 2.5/2.5 Mbps CO iMAP ADSL/SHDSL ADSL Modem Copper Twisted Pairs VoIP POTS E1/T1 2/1.544 Mbps Data/PBX NTU Evolution from Copper to Fibre GbE iMAP - Ethernet Aggregation & Protected Transport MPLS/IP PE Edge Router To MPLS Core P Routers EPSR Aggregation & Transport Home Network Access Network Core Network

4. Modem STB DVR Feeder Fiber Copper twisted pairs Evolution of the access network – exploit all forms of drop cable Central Office Customer Premise Outside Plant Services “Siamese twin” drop cable POTS/ADSL2+ / VDSL2 over Copper FTTN/C Video Services Feeder Fiber Coaxial Cable Drop Ethernet-over-Coax Modem STB DVR Metro Ethernet Distribution Fiber ONT STB DVR Splitter Feeder Fiber EPON + CATV Single Mode Single Fibre Drop Siamese Twin Drop FTTP EPON Voice Services POTS/ADSL2+ / VDSL2 over Copper Application Services FTTP Point-to-Point Ethernet over Fiber Data Services

5. NMS Architecture & Network Model

6. NMS CLIENTS AlliedView NMS Architecture OSS/BSS HP OpenView HTTP JAVA RMI XML/SOAP NMS Client Interfaces IP Network Management Northbound Interface (NBI) Java Virtual Machine Apache Web Server & Tomcat Containers AXIS XML/SOAP NMS MySQL Database Provisioning Tools Security Alarms Faults Events Performance Utilization Traffic Configuration Provisioning Topology CLI SNMP Agent SNMP MIBs AlliedView NMS IP Network TR-069 CLI SNMP GET/SET NMS Polling SNMP TRAP Third Party Equipment Allied Telesyn Router & Switches iMG Residential Gateways iMAP Multiservice Access Platform Network Elements

7. Data Data Data Data Data Data Data Data Data Voice Voice Voice Voice Voice Voice Voice Voice Voice Video Video Video Video Video Video Video Video Video 1 1 1 2 2 2 3 3 3 4 4 4 Aggregation L K M Video Conferencing Streaming Server DATA DATA DATA DATA DATA DATA DATA DATA VOICE VOICE VOICE VOICE VOICE VOICE VOICE VOICE PSTN/Mobile Gateway VIDEO VIDEO VIDEO VIDEO VIDEO VIDEO VIDEO VIDEO VoIP Call Server Gaming Server Internet Intranet/VPN Network Model - N:1 VLAN per service Service VLANs = (data, voice, video) Line Card X Line Card Y CFC Line Card Z Customer ID = port DHCP Option 82 Service VLANs = (data, voice, video)

8. Data Data Data Data Data Data Data Data Data Voice Voice Voice Voice Voice Voice Voice Voice Voice Video Video Video Video Video Video Video Video Video 1 1 1 2 2 2 3 3 3 4 4 4 Aggregation K M L Video Conferencing 1, X, C-VLAN 1, X, C-VLAN Streaming Server 3, X, C-VLAN 3, X, C-VLAN 3, Y, C-VLAN K, X, C-VLAN K, X, C-VLAN Node ID, Service provider S-VLAMN 1, Y, C-VLAN 1, Y, C-VLAN C-VLAN 3, Y, C-VLAN PSTN/Mobile Gateway L, Y, C-VLAN L, Y, C-VLAN 1, Z, C-VLAN 3, Z, C-VLAN M, Z, C-VLAN VoIP Call Server Gaming Server S-VLAN Internet Intranet/VPN Network Model - 1:1 VLAN per subscriber Customer ID, service C-VLAN = port, card, (data, voice, video) S –VLAN = Node ID, Service provider Line Card X Line Card Y CFC 1, Z, C-VLAN 3, Z, C-VLAN Line Card Z M, Z, C-VLAN Customer ID, service C-VLAN = port, card, (data, voice, video)

9. Provisioning Services

10. Triple Play Customer Form for RG 634 – Two Voice, Two Video, TLS, and Internet Access General Profile Transparent LAN Service Port Profile Internet Service Profile Video & Data Configuration Voice Profile for derived voice POTS port Profile POTS line Profile Voice Configuration

11. Provisioning a subscriber with Services DHCP Relay Option 82 DHCP Server Adds the Remote ID, slot.port, and VID BOOT VLAN POWER Authenticates BOOTSTRAP location & directory tftp server address, Management VLAN REQUEST BOOT CODE tftp server Adds the Remote ID, slot.port, and VID REBOOT, DHCP DISCOVERY Listener MANAGEMENT VLAN Telnet & CLI CONFIGURATION SERVICES

12. Zero Touch Configuration (AlliedView NMS) DHCP Server (Option 82 support) 2. DHCP server provides to RG: - its IP address and also the - IP address of the tftp server (NMS) - “bootstrap” directory (per RG type) 6. Use DHCP Listener to Discover RG. DHCP Server “Listener” 6 5. DHCP server provides new “RGMgmt” IP address to RG NMS iMAP’s DHCP Relay configured to send DHCP to both Server and Listener Via MAPMgmt VLAN 7 2 4,5 7. NMS configures RG 8 DHCP Relay 3 tftp Server (usually resides on NMS also) 8. RG gets configuration and provides requested services. RGMgmt VLAN Bootstrap VLAN 4. RG reboots using the RGMgmt VLAN. Requests new IP address to DHCP Server 3. RG loads “bootstrap” file from tftp server into Flash and reboots 1. RG Asks for DHCP Address over Bootstrap VLAN Residential Gateway

13. Flows • To start with: • - Use NMS Configurator to easily Setup a bootstrap environment on NMS • ?This sets up a tftp server on the NMS along with a set of boot up configuration files?. • - Setup a DHCP server (and if G6 is used a DNS server too) for required number of Access Islands. • - Use NMS Configurator to Setup a RG profile corresponding to a iMAP Shelf, card, port. Alternatively could on RG’s MAC and ignore the port. The operator has combinations of 4 profiles to choose from {General, video, internet, voice). From this the Configurator builds the RG configuration files. Note: the NMS does not auto-config the iMAP’s port based on these profiles. This still must be done manually. • Out of the BOX - RG is powered up and looks for a DHCP Server as part of the ‘Discover’ Process • Uses an untagged VLAN as the factory default configuration. (iMAP must be configured for this untagged VLAN) • DHCP server responds to RG with its IP address and also the IP address of the tftp server (which is the NMS) and a “bootstrap” directory (per RG type) • DHCP chooses IP range based on Circuit-ID, (Port.VID) Remote Agent ID (MAP) provided by iMAP, and Option 60 Vendor-Class ID (RGType) (RG634A vs. RG624A vs. iMG646DB provided by RG. • RG asks tftp server for “MD5SUM” file • MD5SUM file is used to determine if additional files are needed. This includes the RGMgt VLAN config. It will download im.conf and any other files that are needed (Note the LED will flash its System LED at 4Hz) , then it will update its flash (LED will flash at 2Hz) and reboot. MD5SUM may be done twice if recovery files are also updated [This “bootstrap is only done ONCE!] • After RG reboots it comes up and operates using the RGMgmt VLAN (untagged VLAN is de-configured due to RG only supports one or the other). RG Requests new IP address to DHCP Server • iMAP’s DHCP Relay has to be configured to send DHCP DISCOVERY and REQUEST to both Server and Listener along with Circuit ID Info for RGMgmt VLAN(s) only over the RGMgmt VLAN; all other VLANs would be forwarded only to the DHCP server. • DHCP server chooses IP range based on Circuit-ID, (Port.VID) Remote Agent ID (MAP), and Vendor-Class ID (RGType) • DHCP server provides new “RGMgmt” IP address • The RG will likely always use this address as long as it remains in the access island. • NMS as DHCP Listener will Discover RG • NMS as Listener uses the circuit ID and Remote Agent ID and RGType to determine which configuration profile to apply. NMS will also discover the RG’s management IP address by listening to DISCOVERY messages from the RG (which contains the assigned IP address). NMS then finishes populating the database with RGType, MAC address. • If DHCP is not used, and the IP address of the RG is static, the NMS will have to be configured with the MAC address of the RG to determine which configuration profile to apply. The NMS will also have to be configured with a subnet address and subsequently will ping all the potential hosts on this subnet until it discovers an RG. • NMS will then use SNMP to find the WAN interface and its corresponding MAC address (via ifPhysAddress). Note: User can manually configure the MAC if desired in the profile. • NMS connects to the newly learned RG & configures/saves/reboots it • NMS takes the MAC address of the client (RG) learned from DHCP listening and derives a DNS name for the RG (in order to configure MGCP endpoints on the RG). Using Dynamic DNS, the NMS can determine the IP address of the RG’s management interface and subsequently configures it. • RG reboots, comes back up and provides requested services

14. Configuring RG and Call Agent for Voice • Problem: • MGCP endpoints need to be configured for both the RG voice port and the CA. Endpoint should be identified using a Name of the Voice IP interface and not an IP address (since addresses change over time). • NMS Configures RG voice port as voip mgcp protocol set endpointid aaln/0@Name port tel1 • Ideally, the RG’s Voice IP Interface (on the Voice VLAN) would be configured with a Hostname by NMS. This Hostname would be used to configure MGCP endpoints in the RG and G6. The RG would announce the hostname during DHCP assignment time which would in turn allow DHCP to assign to DNS (thus dynamic DNS). However, the RG does not include Hostname when doing DHCP. • Solution: • DHCP Server and NMS derive a Name from the RG’s MAC address. • When DHCP server assigns an address, it also runs a script to derive a name. • Name is “rgvoip-MacaddressOfRG-domainname”. MAC address is the RG’ MAC address ?found in chaddr field of a REQUEST message ? • DHCP will assign this name to DNS. • NMS also derives the same name from the REQUEST message it receives

15. Misc. • PPPoE and RG • If RG uses PPPoE, it must be untagged without any other tagged traffic. Thus all other tagged traffic must exist on another PVC.

16. Provisioning “Triple Play” Service Profiles Triple Play Provisioning Form Service Profiles Transparent LAN VoIP POTS Internet General Video & Data EPSR VLAN VLANs Policy Rules Actions Flows QoS iMAP Routers iMG Switches Devices XDSL EPON NTE8 POTS Ethernet T1/E1 Cards Ports

17. Operating the Network

18. Operations Application • Security Management • User Roles, • Fine grained User Access Permissions, • User Authentication via RADIUS • Network Inventory • Network Discovery • Network Inventory • Inventory of Devices, Ports, Interfaces, VLANs, Physical Links • Automatic Discovery & Surveillance of Network Devices • Network Maps • Multiple Network Views (Layer 1(Physical), 2(VLAN), 3(IP))

19. VLAN View

20. Operations Applications • Alarm Propagation • Traps & events, faults, system log • Manage the Propagation of alarms from Device, Card, Port & Link • Fault Management • Real-time Display of Network Events & Alarms • Configurable Event to Alarm mapping • Configurable Response to Events/Alarms • Performance Management • Statistic Collection, Threshold Alerts, Port Utilization, Graphs & Reports • Configuration Management • Schedule Automatic Device Backups • Store/Edit/Deploy Device Configurations and Command Scripts • Device Configuration File Comparison • Network Upgrade • Scheduled Network Upgrades • Mgmt of Firmware Files & Feature Keys • Ethernet Protection Switching Ring (EPSR)

21. Device Traps Trap Parser processes standard SNMP fields Trap Filter NMS Events Event Parser Text passed from Trap Parser Customise • Action • Trap • Email • New command • suppress NMS Alarms Event Filter Device Alarms Correlation Device Syslog Alert Filter Events Alerts Syslog NMS Database Events Alarms Fault Management Processing

22. Split Management

23. iMG Split Management • Subscriber views and modifies Home Network attributes via the My Account part of the Service Providers Web Portal • Service Provider authorizes all changes • Changes are implemented via the NMS northbound interface • Subscriber does not have direct access to any attributes via the local interface Customer’s Home Network Service Provider’s Web Portal iMAP NMS Northbound Interface AlliedView™ NMS Subscriber request changes

24. Communicating with OSS/BSS Systems

25. AXIS XML/SOAP • Open source - www.apache.org • AXIS - Apache eXtensible Interaction System • XML – eXtensible Markup Language • SOAP – Simple Object Access Protocol • WSDL - Web Service Definition Language • Current implementation - Apache Axis 1.4 • Many companies use Axis for Web services support in their products

26. RPC Methods RPC Methods XML Doc XML Doc AXIS for Northbound OSS Applications Managed DEVICES NMS Functions OSS/BSS Applications RPC API Programming Language/OS Map XML RPC Methods to NMS Functions WSDLWeb Services Definition Language Programming Language API to XML RPC Transformation AXIS SOAP SOAP HTTP(S) HTTP(S) SSL/TLS SSL/TLS TCP/IP TCP/IP XML text doc

27. Faults (wsdl) getTrapParsers getTotalEventsCount getEvents getEventFilters getEventParsers setEventTarget removeEventTarget getEventTargets getTotalAlertsCount getAlertsCount getAlerts getAlertFilters getAlertAnnotation getAlertHistory AdminService (wsdl) AdminService Version (wsdl) getVersion Inventory (wsdl) getNodeNames getNetworks getNodes getCards getPorts getIpInterfaces getVlanInterfaces getVlans getPhysicalLinks getEpsrDomains getProfiles getTasks getInventoryObjects getDiscoveryProperties Mdti (wsdl) getDeviceInfo Current Rel.9 Northbound APIs Rel. 9.0 read-onlyinterfaces

28. Summary • NMS key differentiators • Single screen for Multi-service Provisioning • Network node (iMAP) + Customer Premise CPE (iMG + iBG) • Multi-services - VoIP POTS, E1/T1 lease lines, Multicast IPTV, High Speed Internet Access • Multiple media - copper twisted pairs and fibre (P2P & P2MP) • GbE & 10GbE Protected Transport Rings • XML/SOAP northbound interface • Split Management

29. Thank You Visit us online at www.alliedtelesis.com