managing ipngn networks

72
Dirk Anteunis 9-10 Ekim 2012

Upload: cisco-turkey

Post on 18-Nov-2014

729 views

Category:

Technology


7 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Managing IPNGN Networks

Dirk Anteunis

9-10 Ekim 2012

Page 2: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 2

Cisco Prime Data Center Network ManagerCisco Prime Collaboration ManagerCisco Prime Security Manager

VXI Collaboration ManagementConfigEngine…

Page 3: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 3

• Ekim[Turkish] = Oktober[Flemish]

• Prime[Cisco speak] = Network Management [English]

• Cisco Prime something = Cisco Network Management something

• There are ±60 something and 20 NMS products without ‘Prime’

Presenter
Presentation Notes
For a product to be allowed to be called “Prime” a certain number of engineering criteria need to be met: all “Prime” products have similar GUI layout and colors, must run on UCS and must be virtualizable.
Page 4: Managing IPNGN Networks

Service Management

Analytics

Element & Network Management

Infrastructure

Cisco Workplace / Cloud PortalPrime Order ManagementPrime Service Inventory

Prime Provisioning

Prime Analytics

Prime Central

Prime Performance Manager

Prime NetworkPrime Optical

Prime Network Analysis ModulePrime Assurance Manager

Prime Collaboration Manager

Prime Network RegistrarPrime Access Registrar

Prime PremisesPrime Service Manager for SP Wi-FiPrime Service Manager for BNG

• Unified self-service portal • Business process automation, workflow• Customer impact database• Service catalog, complex workflow

• Business & Operational Analytics

• Central point of access for network information and control• IP element and network management• Optical transport network management• Network performance management & reporting• Visibility into application performance on the network• Aggregate Network Analysis Module information • Assurance for TelePresence and Tandberg sessions

• IPAM, DNS and DHCP Servers• Authentication, Authorization, Accounting• Residential/SOHO equipment activation• Subscriber policy and data management for SP Wi-Fi• Subscriber charging, policy and data management for BNG

For YourReference

Presenter
Presentation Notes
OSS Capabilities: We are investing heavily in OSS capabilities providing everything from element management up the stack to topology, change and configuration, service inventory, performance management, and a service catalog that packages the service provider products. At the bottom we have our portfolio of service provider offerings, we group these into our “high-speed servers”, Prime Suite, and our Fulfillment suite. The high-speed servers provide the scalability and reliability service providers need to deliver their offerings. These include DNS, DHCP, and IP Address Management for dual-stack IPv4 and IPv6; Our triple-A server provides massive scalability and performance for authentication, authorization and accounting. Prime Premises (Broadband Access Center) provides the ability to automatically activate DOCSIS and TR-069 CPE (customer premises equipment). All of these solutions are industry leading in scalability and reliability; example, Prime Network Registrar provides avalanche protection to ensure the reliable and fast recovery from network outages. In the center section we have the Prime Suite. This suite provides the single management environment for packet and transport networks including MPLS-TP. The suit is modular and allows customers to add capabilities as needed. Integration of the domain managers and applications is done through Prime Central, which provides the single point of access to information and the tools required by the network operators to do their jobs. With Prime Central we have done the integration work so customers do not have to. This provides the flexibility to grow your management solution based on business need. Key components of the Prime Suite include: Prime Network for managing packet networks Prime Optical for managing traditional and new carrier packet transport networks Prime Provisioning for the automated provisioning of layer 2 and 3 services Prime Performance Manager which provides a very fast and agile approach for gathering and presenting actionable information related to network devices and services to the operators. Prime Performance Manager is designed to be very fast to implement and to provide fast time-to-value. Unlike other performance management systems that can take months or years to implement do to complex feature sets, we’ve specifically taken the approach with Prime Performance Manager to focus on the network operators and provide them with valuable information. Prime Performance Manager has over 600 reports that span the mobility, video, IP NGN for both packet and core networks. The top section represents our Prime Fulfillment suite. Prime Fulfillment connects the service provider billing and CRM systems to the network services that we have traditionally delivered. The suite is designed to accelerate new product delivery and the reuse of pre-defined service components. Our deep knowledge of Cisco devices and architectures allows us to automate the processes service providers use to deliver their products like quadplay, where multiple network services are activated, CPE devices are lit, and potentially technicians need to go onsite for installation. With the Prime Fulfillment suite we can provide real-time visibility into the network resources and the related estimates for service delivery. Prime Provisioning connects the Prime for IP NGN suite (where it is a component) to the Fulfillment suite. This is where network services are activated through template driven policies. Prime Provisioning makes it possible for operators to easily create new services (leveraging existing policies). Prime Provisioning also automates the activation of services as part of the Prime Fulfillment Suite. Prime Service Inventory discovers existing services, the associated resources, and the customers that are using the services. Discovered services are used in Prime Order Management. Prime Order Management provides network engineers with the ability to define service components. Service components are reusable and can be used to define the services that are made available to the service provider product managers and used in the creation of customer-facing products. Service components provide the flexibility required to rapidly create differentiated services without the need to recreate workflow. The Prime Active Catalog is used by product managers and other business-facing members of the service provider organization to create new services, and new options for existing services.
Page 5: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 5

• Prime InfrastructurePrime LMSPrime NCS

• Prime Network Analysis Module (NAM)NAM-3 Cat 6500 Blade2300 Series ApplianceNAM for Nexus 1100 SeriesNAM for ISR G2 SRENAM for WAAS VB

• Prime Security Manager

• Prime Data Center Network Manager (DCNM)

• Prime CollaborationCUOM, CUPM, CUSM, CUSSMCollaboration Manager (for TelePresence)

For YourReference

Page 6: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 6

• Change Management

• Visibility

• Deployment support

Page 7: Managing IPNGN Networks

Cisco Public 7© 2011 Cisco and/or its affiliates. All rights reserved.

Page 8: Managing IPNGN Networks

Wherewould you prefer

to walk ?

Presenter
Presentation Notes
Some infrastructures are stable, others aren’t Infra-structure is a structure that supports other things, hence the qualifying part ‘infra’ meaning ‘under’; the things supported can be the structure, or a super-structure. Roads are called infrastructure because they support, or underpin the social structure by enabling transport of goods and people from one place to another. Very often the roads are also the places where the water & sewage, power (electricity, gas, hot water) and telecommunication networks pass. These networks are means of transportation of goods and services.
Page 9: Managing IPNGN Networks

++ IOS 12.4(19)

r1#sh run

...

router bgp 12no synchronizationbgp log-neighbor-changesnetwork 137.1.200.0 mask 255.255.255.0neighbor 137.1.200.2 remote-as 12no auto-summary

...

event manager applet email_hsrp_state_change

action 1.0 info type routernameaction 1.1 cli command "enable"action 1.2 cli command "del /force flash:hsrp_state_change"action 1.3 cli command "show standby | append hsrp_state_change"action 1.4 cli command "show standby brief | append hsrp_state_change"

……

Presenter
Presentation Notes
For a telecommunications network the infrastructure consists of wires, spectrum, physical components and electronics that make the transport of bits of information possible, operating systems to control the electronics and physics, and finally configuration data that determines the behavior of the whole circus.
Page 10: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 10

• Reliable & known hardware• Reliable & known OS

• Well-known configuration• Efficient processes

Presenter
Presentation Notes
3 times the word “known” on this slide is an indication for the main problem tackled by Network Configuration Change Management.
Page 11: Managing IPNGN Networks

expertise

high productivityrequirements

scarce expertise

growth

new servicescritical business

applications

compliance

regulatory standardscorporate/it policies

technology rules

complexity

global networksnetwork applications

web services

increasingchallenges

Result: many IT initiatives are delivered late

The biggest part of IT budget is maintenance & operations

Presenter
Presentation Notes
Compliance is a huge thing these days, whether it be about regulatory compliance, such as SOX, HIPAA, FDA, GLBA, COSO, CobiT, ECI, VISA, or even doing your ITIL framework within your own organization. How is it done? A lot of enterprises don't understand completely what that means to their business processes. And to map that into a network configuration at a device level is really a hard job. Business wanting to achieve compliance need PACE solution. Of course, there are business that are really looking for growth. They want to add new applications to their networks. They might have only data networks, but want to do the voice over IP, or video, perhaps Tele-Presence. But the fact is that most organizations have limited resources to do such kind of a growth. Those resources typically are tied down doing operational activities. So often, strategic growth initiatives can’t be pursued as aggressively as desired. Limited expertise also constrains many businesses. Typically for two reasons. For security reasons, an organization my elect to have only two or three people to make changes, or they may simply have only two or three people who are qualified. So, either they can change those 5000 usernames and passwords, which are required every 40 days, or maybe 10 days, in some organizations –OR- they can focus on growing their networks into adding new functionality over the network. Complexity is the last element, which is a huge concern for businesses. When I talk about complexity I'm talking about having multi-vendor networks, global networks, different devices, different operating systems, different configuration standards and being able to manage those from a single source. Finding the right tools has been a problem. In fact for some, the complexity stands in the way of pursuing areas of growth.
Page 12: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 12

• 70-85% of problems are related to change50-60% of problems cause downtimeMany changes introduce vulnerabilities when errors are made – particularly in network infrastructureRate of change – and complexity – is accelerating

• labor costs are growing at 10% a year, outpacing overall IT services budget growthBetween 5-10% of total budget spend on Security and ComplianceDriving most companies to off shoring, which increases complexity

• Increasing pressure to be keep the infrastructure compliantSarbanes-Oxley, Basel II, PCI, ISO, NERC, DISA, FISMA, HIPAA, etc.

Presenter
Presentation Notes
Everybody knows that change happens. Without real-time visibility of the environment and and control over what changes, we are forced to spend enormous amounts of time finding the source of outages, misconfigurations, and performance degradation. We also have very little ability to report on the current state. With multi-tier applications, virtual and physical environments, wide ranges of hardware, storage and network devices that are all co-dependent in today’s data center, it’s no longer realistic to rely on tribal knowledge.
Page 13: Managing IPNGN Networks

• What do you have?

• How is it configured?Mostly‘tribal knowledge’

• What changed & who changed it?

• Who is impacted?Again ‘tribal knowledge’ seems the only source

• Are you compliant?Only 1 in 10 companies can effectively measure compliance with best practices edicted by Sarbanes-Oxley, HIPAA…

Presenter
Presentation Notes
What do you have? Multiple domains – network, server, storage, applications Multiple device types, card types, IOS (NXOS, ZR …) types, vendors Need to understand the key business services you are offering and how they map to the infrastructure How is it configured? Maintain historical configuration information and eliminate dependencies on ‘tribal knowledge’ Understand dependencies, relationships, and configured services What changed & who changed it? Change management accounts for >60% of data center costs Virtualization & web-based apps break old-management models Who is impacted? Need to manage virtual and physical relationships IT relies on tribal knowledge for infrastructure dependencies Are you compliant? Only 1 in 10 companies can effectively measure compliance Change management accounts for >60% of data center costs What Do We Need to Know? So to take control of configuration, change and compliance across the network, server, application and storage infrastructure, what do we need to know? First, what do we have? Without a foundational understanding of the current state, we have no data to analyze. This data needs to be current, accurate comprehensive, and complete. Second, when problems or outages happen, how is the infrastructure configured? Has a change, authorized or unauthorized affected the availability of services. Having full visibility is key - chasing alerts will not work. We need intelligence to find the cause of the problem – not the symptom. What changed and who did it? We need to know not only the current state, but the history also. And having a series of point-in-time snapshots may not be enough. Who knows what happened between each snapshot – all that data would be lost without continuous discovery. Who is impacted? Without understanding the relationships and interdependencies of the applications, hosts, and other devices in the physical and virtual environments, IT can’t make good decisions for diagnosing and repairing, or even planning changes to the environment. Are we compliant? Applying policies to the environment and having a method to monitoring them against the infrastructure is critical. With compliance, if you can’t prove it, you aren’t compliant!
Page 14: Managing IPNGN Networks

Cisco Public 14© 2011 Cisco and/or its affiliates. All rights reserved.

Page 15: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 15

• Similar to a doctor treating a patient, similar to managing national health

• Because we want to achieve a goal

• Steps:1) Observe or Monitor2) Interfere; i.e. change the behaviour3) Measure; similar to Monitor, but more precise data4) Report; produce intelligible info for others

Presenter
Presentation Notes
This definition is assembled from a collection of definitions found in Webster’s, Cambridge Dictionary Online and other WWW resources. Observe or Monitor: both fault monitoring and performance monitoring fall in this class. In essence one is looking at the network to understand what’s going on. Eventually this triggers action. It is what a doctor does when he examines a patient. Interfere: here one takes action, by means of CLI or assisted by IT applications to make things different. When driving a car, this is when you push the accelerator after the traffic ligts switched from red to green; in case of the doctor’s visit it’s you taking the pills. When it comes to Network Management, more then one term is used. Configuration Management is one, Provisioning is another, Maintenance also appears and in some cases service activation and commissioning are used. All of these are different forms of inferference with either the network or it’s behaviour. Measure: in some cases much more accurate data as compared to the monitoring ones are needed. The doctor will ask you to undergo blood tests, or have an RX of your chest. The collection of accounting data is a perfect example of this. Report: the doctor gives you the diagnosis and the prescription and eventually declare you fit for work. Fault and performance management systems usually have numerous graphs and other formas of reporting. Goals to achieve: the network and the bank acount of the Service Provider move/transition to the desired state. Remember that SPs are in it for the money. A underutilized link is not an issue. A piece of the network not generating revenue is an issue. Goal for visiting a doctor: getting rid of the disease or uncomfort.
Page 16: Managing IPNGN Networks

Cisco Public 16© 2011 Cisco and/or its affiliates. All rights reserved.

Page 17: Managing IPNGN Networks

• Why Network Management Systems ?

• Enable owners of (Cisco) Kit to save on spending €€ while managing the kit

- €€- €€

Manual mgmt

IT assisted mgmt

Presenter
Presentation Notes
Service Providers as well as enterprises large and small, spend money while managing routers. This cost is always regarded as a negative and unwanted. Making money is not the same as saving costs. Most of the ROI models that are thrown at customers by sales people fall in this category. Because the world is becoming more and more computer-assisted, this argument is sometimes counter-productive due to the high costs of the management system and the human process around it. Manual management consists of the various CLI dialects (IOS, IOS-XR, CatOS, and a few others) to handle each box in it’s own right. Many people and companies already observed that this is tedious, and some boxes have built-in GUIs to try to cut down the cost. IOS-XR chose to go the XML way. The only really widespread configuration tools in CiscoWorks focus on some particularly error-prone activities: SNMP Community strings and software image management. All software with “compliancy” in the name falls under this category. A very obvious example is fault and performance management. The reason why SPs and enterprises ask for persistence of the fault records is simply that no human being can remember them, after seen the SNMP trap displayed on a screen for 5 seconds. In the case of performance monitoring the phenomena are often not visible to the naked eye or ear (some old-timers use the noise level of disk drives to measure FTP throughput, but they are a dying breed)
Page 18: Managing IPNGN Networks

• Operations Support Systems help Service Providers to make €€ from (Cisco) Kit

• Typical operational issues are taken care of also, these form substantial differences between service providers.

+ €€OSS

Presenter
Presentation Notes
The term ‘Service Providers’ is used here in it’s most generic meaning: telecommunications SP, ISP, MVNO, CLEC and cloud service providers like Savvis, Terremark, Google or Amazon are part of this collection of organizations. Operations support systems are the IT systems (hw + sw) that are there to help the operational processes of the SP. Cisco’s on-line ordering on CCO together with all our internal and external web sites are Cisco’s OSS. Although it looks like a cost control type of OSS, Cisco generates most of the revenue through its’ OSS. But Cisco is not a SP, we are a traditional enterprise selling products. Large corporations are using more and more OSS systems. Look at the account creation and password maintenance/synchronisation nightmare that we are going through. Because access to networks becomes just as critical as access to the applications and data on those networks the problems encountered will converge also. Configuring a Router in a network is a good thing Being able to bill somebody for the few lines of configuration is a lot better, especially if this bill is recurring, for instance a monthly fee. The minimum need is a database that links payers to network ports or resources. Well, this database is part of the SP’s OSS. Workflow and workforce management, linked to order entry/capturing is another important matter that needs to be covered appropriately, otherwise there is no service to bill for in the first place. These matters are non-networking related, they are needed regardless of the service offered.
Page 19: Managing IPNGN Networks

Cisco Public 19© 2011 Cisco and/or its affiliates. All rights reserved.

Page 20: Managing IPNGN Networks

• Archive and Versioning of Configuration Files Fetch & store all the configurations on network

devices. Store multiple versions of configurations. Job based. for periodic archival Detect changes done outside the PI

server and archive the change

• Compare Configuration Files View configurations Compare configurations between

versions of same or different devices Reporting configuration mismatches

• Rollback Configuration Files from NMS to Device Update the configuration on a device in the network Ability to specify which configurations to download. Ability to specify options like reboot, write mem etc. Job based.

For YourReference

Page 21: Managing IPNGN Networks
Presenter
Presentation Notes
From the same or from different devices !
Page 22: Managing IPNGN Networks

Configuration Comparison

Configuration RestoreConfiguration Change Log

Presenter
Presentation Notes
Cisco Prime can automatically detect a device configuration change using syslog messages and triggers a device configuration backup to start automatically. It can also be set to upload device configuration periodically, verifying if the configuration actually changed over the past cycle. Backups are stored with revision informtion, and users can compare any couple of stored files from the running or start-up config and have differences highlighted with different colours.
Page 23: Managing IPNGN Networks

Import Analyze Distribute

Page 24: Managing IPNGN Networks
Page 25: Managing IPNGN Networks

Data Center(Nexus 7000 Series)

Nexus 7000

Nexus5000

Nexus1000

Enterprise Campus& WAN Edge

(Cisco Catalyst switchesCisco 7x00, ASR 1000 and 10000 Series)

Cisco 6500Cisco 4500Cisco 3560/3750

Cisco 2960

Cisco 7600

Cisco ASR1000

Enterprise Branch(Integrated Services Routers)

Cisco 3800

Cisco800

Cisco 1800

Cisco 2800

Support for over 500 Cisco device families Routers, Switches, Firewalls, Service Blades, Access Points; Data Center, Campus, Branch

Day-one device support initiativeEnsures all new platforms are supported the day they ship (recent examples; Nexus, ISR-G2, 2k-S, 3k-X)

Presenter
Presentation Notes
“What do you have?” Provides Comprehensive Device Coverage – To manage a Borderless Network effectively, device coverage is essential, no matter where the device is located. CiscoWorks provides support for more than 560 different Cisco hardware platforms, from an 800 series router to a CRS-1 and everything in between. No other product in the industry provides the breadth and depth of support for Cisco platforms. And with the new “day-one” device support initiative, you can be assured that when a new platform ships from Cisco, manageability support will be provided at the same time.
Page 26: Managing IPNGN Networks

• Monthly Device Driver Pack updates to keep current with HW releases

• Over 300 variations of all main Cisco device families covering access, aggregation, edge, and core

• Over 150 variations of third-party devices from DragonWave, RAD, Alcatel-Lucent, Huawei and Juniper products.

Routers:

Cisco 800, 1600, 1700, 1800, 1900, 2500, 2600, 2800, 2900, 3600, 3700, 3800, 3900, 4700, 7200, 7300, 7400, 7500, 7600,

10000 series

Metro switches, DC switches, gateways:

ME3400, ME3400E, CAT3750ME, ME3600X,

ME3800X, ME4900, Nexus5000, Nexus7000,

ACE4700, AS5800, AS5300, ASA5500, SCE series

Edge, Core and Service Routers:

Cisco 12000, XR12000, CRS, ASR1000, ASR9000, ASR901,

MWR2941, UBR7200, UBR10000 series

Support for All Major Cisco Device Families and OS Changes

Switches:

Catalyst 1900, CAT2900, CAT3500XL, CAT3550,

CAT3560, CAT3750, CAT4000, CAT4500, CAT4900, CAT5000,

CAT6500(CatOS) CAT6500(IOS) series

Presenter
Presentation Notes
Prime© Network supports Over 300 variations of Cisco device families, and more than 150 variations of third party devices, including Alcatel-Lucent, Huawei and Juniper products . For a complete list of non-Cisco device support please contact your local account team.
Page 27: Managing IPNGN Networks
Page 28: Managing IPNGN Networks

SP

Inte

grat

ion

Man

agem

ent

& P

olic

y

Smart Services OS / ASICs IPv6 SDN/API Systems Test

INTELLIGENT NETWORK ARCHITECTURE

Cloud ConnectUnified Access

Connected Industries

Unified Compute SystemUnified Fabric

TelePresence Collaboration Apps

Unified CommsCustomer Collaboration

Data CenterBorderless Collaboration

Secure Access Threat Defense App Visibility & Control Cloud Sec

Secure-XCis

co P

rim

e LifecycleEnd-to-end lifecycle management- Design, Deploy, Operate, AdminAssuranceApplication/ end-user visibility- Monitor, Troubleshoot, RemediateComplianceRegulatory and best practices- Monitor, Report, Remediate

Prime Infrastructure

Data Center Network MgrManagement of virtual resources•Network, Compute, StorageNetwork Analysis ModuleRich instrumentation for application troubleshootingNetFlow Generation ApplianceVisibility of Data Center applications and services

Data Center

LifecycleEnd-to-end lifecycle management- Design, Deploy, Operate, AdminAssuranceVoice/video/telepresence visibility- Monitor, Troubleshoot, Remediate

Prime Collaboration

Page 29: Managing IPNGN Networks

Cisco Public 29© 2011 Cisco and/or its affiliates. All rights reserved.

Page 30: Managing IPNGN Networks
Presenter
Presentation Notes
Inventory is not the only asset, the most important once is customers, and employees and the skills of these employees are another asset of a company. Finally there are intellectual property and/or commercial rights to use images, software or other “non tangible” assets. Network inventory management is an essential component of a robust network management architecture. The network inventory is an important business asset (regardless of the environment) that requires ongoing tracking and management. The ability to access up-to-date network information is essential to high-reliability environments. Typical network operations rely on physical network management that identifies element failures. Network operators need to uniquely determine the exact location of a network element, their associated attributes and drill down to specific network element information. Most networks already employ network management systems for fault detection. However, network inventory management is often missing because of network complexity and a lack of integration time. The network inventory function implemented in a network management application should provide an automated device discovery to catalogue and to update what the network actually contains. This information should be available in a central database repository with a GUI user access and open APIs for NBI integrations. The discovery should also be flexible to detect network elements and import asset information for all hardware, software, and infrastructure from any system in the network. This information should be gathered and updated regularly
Page 31: Managing IPNGN Networks

Many discovery tools available •Slots •Modules•Serial Number•.... Etc

Presenter
Presentation Notes
What most of the network management provides today is just Physical Inventory This is either done with a financial or deprecation focus or else with a technical focus: spare parts, types, interoperability.
Page 32: Managing IPNGN Networks
Page 33: Managing IPNGN Networks

167

PW

CFM

VRF

Device Configuration Logical ModelConfiguration Objects

Presenter
Presentation Notes
The new trend to IP convergence with IP NGN networks and the introduction of new technologies such as Carrier Ethernet increases network complexity and makes an effective inventory management presence more important. This requires also network management systems to have new approaches to network inventory other that just physical inventory. Logical Inventory The logical inventory reflects dynamic data such as configuration and performance data, forwarding and service-related attributes, label switching tables, tunnels, protocols, etc. Every artefact we create within our device configurations In a model! Need logical structure Relations between items of configuration (same service) (depends on) Between items of service configuration and customers services. The physical assets are just the enabler, it’s how we connect them, and how we configure them that actually creates the services our customers rely on. Logical inventory is a representation of the configurations, but just collecting lines of cli equivalent to having full set of photos of a warehouse Does not answer: How do I identify which services exist, whether they are correctly configured, Across devices Across different logical entities Acls Policies, Classes, SubInterfaces How do I see which logical resources are in use where? Move sub bullts into speech/notes add a diagram showing a mode – e.g. ANA has a pic of how a VNE is built
Page 34: Managing IPNGN Networks

NMS can investigate device configuration and represent it in its user interface

Page 35: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 35

show mpls forwarding-table

Local Outgoing Prefix Bytes tag Outgoing Next Hoptag tag or VC or Tunnel Id switched interface200 Pop tag 10.10.3.0/24 0 Se0/0 point2point201 Pop tag 10.10.1.0/24 0 Se0/0 point2point202 20 10.10.2.0/24 0 Se0/0 point2point203 21 10.10.4.0/24 0 Se0/0 point2point204 16 10.10.5.0/24 0 Se0/0 point2point205 23 11.11.1.1/32 0 Se0/0 point2point206 Pop tag [T] 11.11.3.1/32 0 Tu0 point2point

Leveraging device instrumentation

Presenter
Presentation Notes
Look at the hyperlinks in the GUI, they permit you to navigate to another interesting part of this piece of logical inventory and topology.
Page 36: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 36

show lacp bundle Bundle-Ether 17

Bundle-Ether17Bandwidth (Kbps) Min active Max activeEffective Available MAC address Links B/W (Kbps) Links---------- ---------- -------------- ----- ---------- -----

20000000 20000000 4000.0000.0001 1 1 8

Port State Flags Port ID Key System-ID------------ ----- ----- -------------- ------ -------------------Te0/1/0/2 4p AF 0x8000, 0x0001 0x0011 0x8000, 00-24-98-eaPEER 4 AF 0x8000, 0x0001 0x0011 0x8000, 00-24-f7-1aTe0/1/0/3 4 AF 0x8000, 0x0002 0x0011 0x8000, 00-24-98-eaPEER 4 AF 0x8000, 0x0002 0x0011 0x8000, 00-24-f7-1a

snmpwalk -c public -v1 172.23.104.23 .1.2.840.10006.300.43.1.1.1.1

iso.2.840.10006.300.43.1.1.1.1.2.12 = Hex-STRING: 40 00 00 00 00 01iso.2.840.10006.300.43.1.1.1.1.3.12 = INTEGER: 32768iso.2.840.10006.300.43.1.1.1.1.4.12 = Hex-STRING: 00 24 98 EA C3 FCiso.2.840.10006.300.43.1.1.1.1.5.12 = INTEGER: 1iso.2.840.10006.300.43.1.1.1.1.6.12 = INTEGER: 17iso.2.840.10006.300.43.1.1.1.1.7.12 = INTEGER: 17iso.2.840.10006.300.43.1.1.1.1.8.12 = Hex-STRING: 00 24 F7 1A 5C ECiso.2.840.10006.300.43.1.1.1.1.9.12 = INTEGER: 32768iso.2.840.10006.300.43.1.1.1.1.10.12 = INTEGER: 17iso.2.840.10006.300.43.1.1.1.1.11.12 = INTEGER: 65535

CLI and MIBs

Page 37: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 37

Nested hierarchy

Page 38: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 38

Logical Topology

Page 39: Managing IPNGN Networks

L3VPN

VPLS

VPWS

Presenter
Presentation Notes
ANA can create graphical representations of various network topologies, either as an overlay on top of a physical network map or through dedicated service maps. VPWS – Virtual Private Wire Service VPLS – Virtual Private LAN Service L3VPN – Layer 3 VPN These topologies provide network operators: How customer traffic is mapped to different network transport technologies At-a-glance views of network elements traversed by VLANs, VPLS, EVCs or MPLS VPNs Spanning Tree Protocol and Resilient Ethernet Protocol overlay icons for quick determination of actual forwarding paths across a VLAN during problem investigation and verification of backup paths. Pseudowire (single-segment and multi-segment) topology views to help visualize emulated service paths, such as TDM circuits within IP RAN backhaul networks or point-to-point Ethernet connections across Ethernet-over-MPLS (EoMPLS) emulations.
Page 40: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 40

Virtual Routing and Forwarding

Customer Edge

Access Circuit

Presenter
Presentation Notes
ANA automatically discovers virtual connections such as Layer 3 VPNs (MPLS), Virtual Private LAN Service (VPLS), and Ethernet Virtual Connections (EVCs). ANA visualizes these virtual connections via service maps and service overlays (on top of network maps). The VPNs are visualized in VPN Service maps and overlays, enabling to drill down into specific VPNs and to view which sites are contained under each VPN. Service = vpn Tecnnology implementation vrf, ac, routing params – represented in discovered log. Inv.h Associate logical inventory to paying customer – to create service Show cli for this Config wrong -> picture will look wrong Show cli – and say how this means we can intrpret that cli and therefore conclude the 2 are linked together (based on RT) Also show vrf forwarding
Page 41: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 41

PE3#sh ip vrfName Default RD InterfacesCust3VPN 100:3 FastEthernet0/1....

PE2#sh ip vrfName Default RD InterfacesCust3VPN 100:3 Serial0/2....

Page 42: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 42

PE2#sh ip vrf detail Cust3VPNVRF Cust3VPN; default RD 100:3; default VPNID <not set>Interfaces:Serial0/2

Connected addresses are not in global routing tableExport VPN route-target communitiesRT:100:3

Import VPN route-target communitiesRT:100:3

No import route-mapNo export route-map

Page 43: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 43

Page 44: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 44

Primary and alternate ports for REP segments

Locally significant VLAN tags

Presenter
Presentation Notes
Locally significant vlan tracing We get correct scope exact domian ending a router Vlan 205 – one of many within my network Colore del link
Page 45: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 45

EVC

Potential UNI

Page 46: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 46

VLAN Manipulation

Access VLAN terminating on the EVC

Presenter
Presentation Notes
EVCs topologies are created by concatenating sub-domains, such as VLANs and VPLS instances, that are traversed by the EVC. From an EVC topology a user can drill down into the traversed VLAN or VPLS topologies and, for there, into the device-level inventories. VLANs, Pseudowires, VPLS instances, and EVCs are dynamically discovered solely from network configuration information. ANA uses configuration information discovered by ANA's VNEs to construct a network-level representation of VLANs, Pseudowires, and VPLS instances. ANA creates EVCs by discovering and concatenating connected VLANs, Pseudowires, or VPLS instances.
Page 47: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 47

PW Tunnel supporting the VPLS

Page 48: Managing IPNGN Networks

Cisco Public 48© 2011 Cisco and/or its affiliates. All rights reserved.

Page 49: Managing IPNGN Networks

Out-of-the-box default settings quickly isolate network problems

Contextual dashboards

Centralized alarm browser

Troubleshooting workflow

NAM integration

Page 50: Managing IPNGN Networks
Page 51: Managing IPNGN Networks
Page 52: Managing IPNGN Networks
Page 53: Managing IPNGN Networks
Presenter
Presentation Notes
Threshold Crossing alarms in Prime Performance Manager This show a sliding window measurement of uptime of an EFP, with a 5 minute window and a threshold of 95%; this is information coming from E-OAM CFP functionality in the devices and is polled by Prime Performance Manager every minute. The top lines show that the availability is 100%, a situation that has been signaled 2 times. It’s actually the IOS (-XR) devices that do the majority of the work, and keep the results in a specific MIB. That MIB is polled by P.Performance. It is P.Perfomance that applies the 95% rule on the measurements and generates an alarm. An Alarm is just a record in a DB. P.Performance can also send the alarm as a SYSLOG message or an SNMP trap to other systems. The Critical alarms are easier to interpret: the Multicast+ Broadcast traffic is higher then the 20% of bandwidth threshold that was specified. This is a simple comparison between a polled value and a configured threshold.
Page 54: Managing IPNGN Networks

-

Cisco 7200 Series

Cisco WAASCisco WAAS

VM VM VM VM

Cisco Nexus® 1000V

Campus

Cisco® Unified CommunicationsManager Cluster

SiSi

SiSi Cisco 7200 Series

NetFlow Data Export Cisco Catalyst®

6500 NAM

Cisco NAM Appliance

Cisco NAM on SRENetFlow Data Export

Cisco WAAS

Cisco NAM on SRE

Inte

r-B

ranc

h Tr

affic

Branch Office-to-Data Center Traffic

WAN

Remote LocationsData Center

Application Servers

Cisco Prime™ NAM on Nexus 1010

Page 55: Managing IPNGN Networks

Application Performance Visibility

Traffic Analysis Troubleshooting

• Application response time analysis

• Voice quality analysis

• URL monitoring

• Applications, host, conversations, DSCP and QoS, and VLAN

• Per-application and per-user details

• Advanced filters, packet capture, decoder, and error scan

• Port and interface statistics

Cisco Nexus® 1010 Virtual Services Appliance

Cisco Nexus 7000 Series Switches

Cisco Catalyst®6500 Series

Cisco® 7600 Series Routers

Cisco Catalyst 4000 Series Switches

Cisco 2800, 2900, 3800, and 3900 Series ISRs

Cisco WAAS Appliances

Page 56: Managing IPNGN Networks

Filter by Site, Host, VLAN, Data Source, or Time Range Data Export Descriptive Summary

Reporting Time Interval Zoom and Pan to Select Time Range Host Conversation Details

Presenter
Presentation Notes
This is an example of Host Traffic Analysis
Page 57: Managing IPNGN Networks

Cisco Public 57© 2011 Cisco and/or its affiliates. All rights reserved.

Page 58: Managing IPNGN Networks

Cisco Manufacturing

Substantial Planning and

Design

1

Order2

NMS/OSS

Staging, testing4

3 Bare delivery

Enterprise IT – or –Service Provider

Cisco.com +internal systems

Partner/Cisco Warehouse

ProductionService Config

5

Page 59: Managing IPNGN Networks

Cisco Manufacturing

Customer places an order

1

- Unconfigured- custom configured2

NMS/OSS

drop ship to customer

4 3 InitialService Config

Enterprise IT – or –Service Provider

Cisco.com +internal systems

SP Warehouse

ProductionService Config

5

Page 60: Managing IPNGN Networks
Page 61: Managing IPNGN Networks

Work Center Configuration Monitoring & Reporting

EnergyWise Large-scale switch configurationManage EW domains and policies

Power consumption, Cost savings, policy compliance, alarms & events

Identity Large-scale Identity deploymentDay-N configuration changes

ACS integration:Auth success failure trends, userinfo, login stats

Smart Install Centrally manage Smart Install DirectorsManage client switch configuration and sw images

Smart Install-specific LMS job management

Auto Smartports Large-scale ASP deployment and day-N configuration changesEvent/trigger managementMAC-based group configuration

Auto Smartports-specific LMS job management

• Highlight key Cisco technologies and solutions• Simplify technology and solution adoption• Centrally organizes Day 1-to-n management tasks

• Contextual status & monitoring dashboards• Readiness assessment and remediation• Instructional configuration workflows

Presenter
Presentation Notes
Simplifying the Deployment and Management of Cisco Value-added Technologies– With the introduction of the new switching platforms, additional new capabilities; EnergyWise, Identity, Auto Install, Auto Smartports; are being provided that further differentiate Cisco from its’ competitors. CiscoWorks LMS helps promote these differentiated features with the introduction of a new concept known as WorkSpaces. WorkSpaces will provide a single user experience for the complete lifecycle management of Cisco differentiated services and technologies, providing an end-to-end capabilities for enabling, provisioning and monitoring these valued-added capabilities. Examples of the Workspace workflows include: Getting Started – overview and initial configuration Status and Monitoring Dashboard Readiness assessment and remediation Day 1 to End provisioning tasks Energywise – enable Ewise on switches, create, populate and adminster Ewise domains, manage ewise policies (create assign and administer, report on power consumption, cost savings and compliance Identity - device config for radius, ACS registration, Port security assignment, authentication and authorization reporting – success, failures trends, 802.1x agentless success and failures, user summary information, method, status and port location, login statistics, ACS health and cross launch Zero-touch – manage config images for clients, manage smart install directors, configure autosmartports, enable interfaces for autosmartports, MAC-based group configuration These are a few examples of whats’ provided in the new WorkSpace user experience, “drop-in” support for additional technologies can be added as new workflows evolve without a need to revise the entire LMS application..
Page 62: Managing IPNGN Networks

provide (SUPPLY) verb [T]to give someone something that they need

provider noun [C]someone who provides something

• It’s possible to organise this by paper (4 copies min.)• It’s possible to organise this by phone• It’s possible to execute this with mouse clicks

http://dictionary.cambridge.org/

Presenter
Presentation Notes
Webster : 1. To look out for in advance; to procure beforehand; to get, collect, or make ready for future use; to prepare. Provide us all things necessary." Shak. 2. To supply; to afford; to contribute. Bring me berries, or such cooling fruit As the kind, hospitable woods provide. Milton. 3. To furnish; to supply; -- formerly followed by of, now by with. And yet provided him of but one." Jer. Taylor. Rome . . . was well provided with corn." Arbuthnot. 4. To establish as a previous condition; to stipulate; as, the contract provides that the work be well done. 5. To foresee. [A Latinism] [Obs.] B. Jonson. 6. To appoint to an ecclesiastical benefice before it is vacant. See Provisor. Prescott. Cambridge: provide (SUPPLY)   Show phonetics�verb [T] �to give someone something that they need:�This booklet provides useful information about local services.�All meals are provided throughout the course.�The author provides no documentary references to support her assertions.�We have concerns about whether the government will be able to provide viable social services for poorer families/provide poorer families with viable social services.�Putting more police on patrol doesn't provide a real solution to the problem of increasing violence.��provider   Show phonetics�noun [C] �someone who provides something:�an Internet service provider�The bank is now a major provider of financial services to industry.�Until her illness she was the main provider (= earned most of the money) in the family.��provision   Show phonetics�noun [C or U] �1 when something is provided:�The provision of good public transport will be essential for developing the area.�Of course there's provision in the plan for population increase.�When designing buildings in this area, you have to make provision against earthquakes.�See also provisions.��2 make provision for sth to make arrangements to deal with something, often financial arrangements:�He hasn't made any provision for his retirement yet.�
Page 63: Managing IPNGN Networks

• Design• Assign• Activate• Audit

Remember

Page 64: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 64

• Create CarrierE (ELINE) Service

• met1-7609-agg1 GE1/0/4

• met3-3400-acc10 GE0/9

Page 65: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 65

• met3-3400-acc10 GE0/9

• FlexUNI

Page 66: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 66

• SR in Requested State

• Configlet Preview

Page 67: Managing IPNGN Networks

Cisco Public 67© 2011 Cisco and/or its affiliates. All rights reserved.

Page 68: Managing IPNGN Networks

Service Management

Analytics

Element & Network Management

Infrastructure

Cisco Workplace / Cloud PortalPrime Order ManagementPrime Service Inventory

Prime Provisioning

Prime Analytics

Prime Central

Prime Performance Manager

Prime NetworkPrime Optical

Prime Network Analysis ModulePrime Assurance Manager

Prime Collaboration Manager

Prime Network RegistrarPrime Access Registrar

Prime PremisesPrime Service Manager for SP Wi-FiPrime Service Manager for BNG

• Unified self-service portal • Business process automation, workflow• Customer impact database• Service catalog, complex workflow

• Business & Operational Analytics

• Central point of access for network information and control• IP element and network management• Optical transport network management• Network performance management & reporting• Visibility into application performance on the network• Aggregate Network Analysis Module information • Assurance for TelePresence and Tandberg sessions

• IPAM, DNS and DHCP Servers• Authentication, Authorization, Accounting• Residential/SOHO equipment activation• Subscriber policy and data management for SP Wi-Fi• Subscriber charging, policy and data management for BNG

For YourReference

Presenter
Presentation Notes
OSS Capabilities: We are investing heavily in OSS capabilities providing everything from element management up the stack to topology, change and configuration, service inventory, performance management, and a service catalog that packages the service provider products. At the bottom we have our portfolio of service provider offerings, we group these into our “high-speed servers”, Prime Suite, and our Fulfillment suite. The high-speed servers provide the scalability and reliability service providers need to deliver their offerings. These include DNS, DHCP, and IP Address Management for dual-stack IPv4 and IPv6; Our triple-A server provides massive scalability and performance for authentication, authorization and accounting. Prime Premises (Broadband Access Center) provides the ability to automatically activate DOCSIS and TR-069 CPE (customer premises equipment). All of these solutions are industry leading in scalability and reliability; example, Prime Network Registrar provides avalanche protection to ensure the reliable and fast recovery from network outages. In the center section we have the Prime Suite. This suite provides the single management environment for packet and transport networks including MPLS-TP. The suit is modular and allows customers to add capabilities as needed. Integration of the domain managers and applications is done through Prime Central, which provides the single point of access to information and the tools required by the network operators to do their jobs. With Prime Central we have done the integration work so customers do not have to. This provides the flexibility to grow your management solution based on business need. Key components of the Prime Suite include: Prime Network for managing packet networks Prime Optical for managing traditional and new carrier packet transport networks Prime Provisioning for the automated provisioning of layer 2 and 3 services Prime Performance Manager which provides a very fast and agile approach for gathering and presenting actionable information related to network devices and services to the operators. Prime Performance Manager is designed to be very fast to implement and to provide fast time-to-value. Unlike other performance management systems that can take months or years to implement do to complex feature sets, we’ve specifically taken the approach with Prime Performance Manager to focus on the network operators and provide them with valuable information. Prime Performance Manager has over 600 reports that span the mobility, video, IP NGN for both packet and core networks. The top section represents our Prime Fulfillment suite. Prime Fulfillment connects the service provider billing and CRM systems to the network services that we have traditionally delivered. The suite is designed to accelerate new product delivery and the reuse of pre-defined service components. Our deep knowledge of Cisco devices and architectures allows us to automate the processes service providers use to deliver their products like quadplay, where multiple network services are activated, CPE devices are lit, and potentially technicians need to go onsite for installation. With the Prime Fulfillment suite we can provide real-time visibility into the network resources and the related estimates for service delivery. Prime Provisioning connects the Prime for IP NGN suite (where it is a component) to the Fulfillment suite. This is where network services are activated through template driven policies. Prime Provisioning makes it possible for operators to easily create new services (leveraging existing policies). Prime Provisioning also automates the activation of services as part of the Prime Fulfillment Suite. Prime Service Inventory discovers existing services, the associated resources, and the customers that are using the services. Discovered services are used in Prime Order Management. Prime Order Management provides network engineers with the ability to define service components. Service components are reusable and can be used to define the services that are made available to the service provider product managers and used in the creation of customer-facing products. Service components provide the flexibility required to rapidly create differentiated services without the need to recreate workflow. The Prime Active Catalog is used by product managers and other business-facing members of the service provider organization to create new services, and new options for existing services.
Page 69: Managing IPNGN Networks

© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 69

• Prime InfrastructurePrime LMSPrime NCS

• Prime Network Analysis Module (NAM)NAM-3 Cat 6500 Blade2300 Series ApplianceNAM for Nexus 1100 SeriesNAM for ISR G2 SRENAM for WAAS VB

• Prime Security Manager

• Prime Data Center Network Manager (DCNM)

• Prime CollaborationCUOM, CUPM, CUSM, CUSSMCollaboration Manager (for TelePresence)

For YourReference

Page 70: Managing IPNGN Networks

Cisco Public 70© 2011 Cisco and/or its affiliates. All rights reserved.

Page 71: Managing IPNGN Networks

Thank you.

Page 72: Managing IPNGN Networks

“Cisco Prime Infrastructure has enabled our IT dept to become a knowledge base of what's on our network. Prime has simplified management of both the wired and wireless network. This in turn has given us time to use reporting tools and educate our users about their impact on our network. Our management capabilities are light years ahead of where they were before Prime.” – Bill Bowser, Telecommunications Manager, Sheetz

Cisco has made good progress with consolidating the network management options at the edge of the network for managing wired and wireless components. Enterprises should review the functionality in Prime NCS and Prime LMS before making a single decision and if needed, wait for the consolidation of both applications into a single solution. - Gartner Unified Access MQ Report