NFM-P service audit

Service audit description

An NFM-P service is defined as a collection of service sites with the same customer ID, service type, and service ID. The NFM-P discovers services that are configured on a 7210 SAS, 7450 ESS, 7750 SR, or 7950 XRS, using the service ID on the NE. Configuration errors may occur in networks where the services were created and deployed on the NEs using CLI before the NEs were managed by the NFM-P.

For example, when two VPLSs with the same service ID and the same mesh VC ID on an NE are discovered by the NFM-P, they are discovered as a single service in the NFM-P.

Another example of a configuration error is when a switching Epipe has multiple Epipe sites and multiple VC IDs for different segments. If different service IDs are used when the sites are created, the NFM-P assumes that the sites are connected and creates multiple VLL services within a composite service.

RCA audit policies allow you to modify the component membership of your NFM-P services to detect possible configuration problems. In addition, you can use the RCA audit to correct most configuration problems that are discovered in the audit.

Note: An NFM-P user who is assigned the Administrator or RCA scope of command role can create, modify, and execute all RCA audit policies. An NFM-P user who is assigned the Administrator or Service scope of command role can execute service audit adjustments.

Service membership rules

The NFM-P uses the rules outlined in the following figure to identify whether two service sites are connected. When two sites are identified as connected, they should belong to same service.

Figure 95-1: Rules to check whether two sites are connected

If service sites have different customer IDs, the NFM-P discovers the sites as belonging to different services. After the audit, the NFM-P generates a problem for each service. You can specify to which service the NFM-P should move the site and whether the empty service should be removed after the sites are moved.

For VPLS or VLL services, if the same service ID is used for two groups of sites that are not connected, the NFM-P detects a duplicate service ID. Two problems are generated for one of the group of sites, and the solution is to separate the services. If there are other groups of isolated sites, additional problems are generated for each group.

Consider the following when you perform an audit of a VPLS.

• Although different service IDs may be used, I-sites that are bound to same backbone VPLS and have the same ISID are considered to be in the same VPN.

• For VPLS sites that use BGP auto-discovery, the VPLS ID is used to determine service membership.

• H-VPLS is discovered as composite service in the NFM-P if different service IDs are used.

Consider the following when you perform an audit of a VLL service.

• Service sites with different customer IDs are discovered as two services, and can be reconfigured as one service.

• More than two groups of sites that are connected can be detected and can be separated into different services.

• Redundant VLLs are not affected by the audit and are considered correctly configured.

• If two Epipe sites are connected to the same PBB with same B-VPLS service ID, and the source and destination MAC addresses match, the NFM-P determines that the two sites are connected. If they are in different NFM-P services, a problem is generated during the audit.

Consider the following when you perform an audit of a VPRN service.

• VPRN service membership is based on the RTs defined in the VRFs.

• Sites that are in different services but have common import and export route targets. Import target of Site 1 is equal to the Export target of Site 2.

RCA audit for services with multi-vendor NE sites

The NFM-P attempts to place MV sites into the correct service during discovery. For MV sites which are not placed into the correct service, the MV Complete Service Topology function moves the MV sites and matches them with the service. When you click the MV Complete Service Topology button on the Manage Services form, the NFM-P performs a search for services containing MV sites. If a service does not contain any MV NEs, the NFM-P skips that service. For each service, the NFM-P performs an RCA audit and the following actions occur:

• Epipe service

  The NFM-P determines if an Epipe service has at least one MV site, and then checks all other Epipe services for a site with the same VC ID and with SDP bindings pointing to each other. If a matching site is found, the NFM-P moves the site from the first service to the second (matching) service. As a result, the two services are collated. If a service has two or more MV sites which do not meet the same criteria, one site is moved to either the correct matching service, or a new service. This action results in two services potentially assigned to different customers being merged into one service. No changes are made on the NE.

• VPLS service

  A VPLS service can have one or more sites. The RCA audit only supports mesh SDPs. The MV Complete Service Topology function does not support VPLS sites with spoke SDPs.

  When the NFM-P finds a VPLS service with at least one MV site, it checks all VPLS services for a site with the same mesh VC ID and the mesh SDPs pointing to each other. All of the matching sites that are in different services are moved to a single service. Any mismatched sites are moved to either the correct matching service, or a new service. This action results in two services potentially assigned to different customers being merged into one service. No changes are made on the NE.

• VPRN service

  Note: Do not re-use route targets on the NEs. Route targets must be unique because the RCA audit uses route targets to match VPRN sites that are in different NFM-P services or that have different service IDs. Reusing route targets causes the sites to be moved to the same service and the sites are physically separate.

  When the NFM-P finds a VPRN service with a MV site, it checks for all of the VPRN sites (MV or SR) that use the same RT value. The NFM-P then moves the MV sites from the first service to the second service that has other MV or SR sites. This step is repeated for all of the MV sites that have the same RT value. This action results in two services previously assigned to different customers being merged into one service.