CHECKING AND REPAIRING A NETWORK CONFIGURATION
First Claim
1. An article of manufacture embodied as one of hardware logic and a computer readable storage medium including program logic for performing configuration checking of a network, wherein the program logic causes operations to be performed, the operations comprising:
- scanning a network data store for at least one transaction, wherein said transaction includes one of connecting components in said network, adding components to said network, updating components in said network, and rezoning components in said network;
generating at least one event for said transaction using a mapping of events to transactions;
for said event, obtaining configuration data associated with components in said transaction;
generating at least one trigger for said event, wherein said trigger is associated with at least one configuration policy;
comparing said configuration policy associated with said trigger with said configuration data associated with said event for which said trigger was generated; and
determining whether said configuration policy has been violated based on the comparison.
0 Assignments
0 Petitions
Accused Products
Abstract
A technique for performing configuration checking of a network is provided. A network data store is scanned for at least one transaction. At least one event is generated for the transaction. At least one configuration policy is associated with the event. The configuration policy is compared with configuration data associated with the event. It is determined whether the configuration policy has been violated based on the comparison.
-
Citations
28 Claims
-
1. An article of manufacture embodied as one of hardware logic and a computer readable storage medium including program logic for performing configuration checking of a network, wherein the program logic causes operations to be performed, the operations comprising:
-
scanning a network data store for at least one transaction, wherein said transaction includes one of connecting components in said network, adding components to said network, updating components in said network, and rezoning components in said network; generating at least one event for said transaction using a mapping of events to transactions; for said event, obtaining configuration data associated with components in said transaction; generating at least one trigger for said event, wherein said trigger is associated with at least one configuration policy; comparing said configuration policy associated with said trigger with said configuration data associated with said event for which said trigger was generated; and determining whether said configuration policy has been violated based on the comparison. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. An article of manufacture embodied as one of hardware logic and a computer readable storage medium including program logic for performing proactive configuration checking of a network, wherein the program logic causes operations to be performed, the operations comprising:
-
receiving a hypothetical network scenario, wherein said hypothetical network scenario represents a new network configuration that a system administrator wants to create; generating at least one transaction based on said hypothetical network scenario, wherein said transaction includes one of connecting components in said hypothetical network scenario, adding components to said hypothetical network scenario, updating components in said hypothetical network scenario, and rezoning components in said hypothetical network scenario; populating a network data store with configuration data for said transaction, wherein said configuration data includes configuration data for components in said hypothetical network scenario described by said transaction; generating at least one event for said transaction using a mapping of events to transactions; and using configuration data associated with said event to determine whether a configuration policy has been violated. - View Dependent Claims (12)
-
-
13. An article of manufacture embodied as one of hardware logic and a computer readable storage medium including program logic for performing reactive configuration checking of a network, wherein the program logic causes operations to be performed, the operations comprising:
-
receiving a request to perform configuration checking on an existing network configuration; scanning a network data store for at least one transaction, wherein said transaction includes one of connecting components in said network, adding components to said network, updating components in said network, and rezoning components in said network; generating at least one event for said transaction using a mapping of events to transactions; and using configuration data associated with said event to determine whether a configuration policy has been violated by determining whether the at least one transaction results in incompatibilities, performance issues, and availability issues, wherein said incompatibilities are conflicts between components in the network, said performance issues relate to whether a desired performance level is met, and said availability issues relate to whether there is a single point of failure in the network. - View Dependent Claims (14)
-
-
15. A system for performing configuration checking of a network, comprising:
-
a processor; a computer readable storage medium accessible to the processor; and program logic including code that causes the processor to perform; scanning a network data store for at least one transaction, wherein said transaction includes one of connecting components in said network, adding components to said network, updating components in said network, and rezoning components in said network; generating at least one event for said transaction using a mapping of events to transactions; for said event, obtaining configuration data associated with components in said transaction; generating at least one trigger for said event, wherein said trigger is associated with at least one configuration policy; comparing the said configuration policy associated with said trigger with said configuration data associated with said event for which said trigger was generated; and determining whether said configuration policy has been violated based on the comparison. - View Dependent Claims (16, 17, 18, 19, 20, 21, 22, 23, 24)
-
-
25. A system for performing proactive configuration checking of a network, comprising:
-
a processor; a computer readable storage medium accessible to the processor; and program logic including code that causes the processor to perform; receiving a hypothetical network scenario, wherein said hypothetical network scenario represents a new network configuration that a system administrator wants to create; generating at least one transaction based on said hypothetical network scenario, wherein said transaction includes one of connecting components in said hypothetical network scenario, adding components to said hypothetical network scenario, updating components in said hypothetical network scenario, and rezoning components in said hypothetical network scenario; populating a network data store with configuration data for said transaction, wherein said configuration data includes configuration data for components in said hypothetical network scenario described by said transaction; generating at least one event for said transaction using a mapping of events to transactions; and using configuration data associated with said event to determine whether a configuration policy has been violated. - View Dependent Claims (26)
-
-
27. A system for performing reactive configuration checking of a network, comprising:
-
a processor; a computer readable storage medium accessible to the processor; and program logic including code that causes the processor to perform; receiving a request to perform configuration checking on an existing network configuration; scanning a network data store for at least one transaction, wherein said transaction includes one of connecting components in said network, adding components to said network, updating components in said network, and rezoning components in said network; generating at least one event for said transaction using a mapping of events to transactions; and using configuration data associated with said event to determine whether a configuration policy has been violated by determining whether the at least one transaction results in incompatibilities, performance issues, and availability issues, wherein said incompatibilities are conflicts between components in the network, said performance issues relate to whether a desired performance level is met, and said availability issues relate to whether there is a single point of failure in the network. - View Dependent Claims (28)
-
Specification