![]() For example, you can use a pipe to represent the logical connectivity of a 64 Kbps PVC (Permanent Virtual Circuit) service trail. You can use pipes to represent both physical connectivity and logical connectivity. Pipes are the base entities for representing connectivity in UIM. Other forms of connectivity not implemented by other entities. Physical connections, such as cable pairs and local loops. Pipes can enable Connectivity entities and Connectivity entities can enable pipes. Pipe and Connectivity entities can coexist in the same inventory. If you previously modeled connectivity using pipes, you can continue to use those entities. For example, pipes might be applicable in situations such as:Įxisting UIM implementations. You can still implement solutions by using pipes directly, however. See the following chapters for information about Connectivity entities: Connectivity entities, on the other hand, take advantage of pre-defined rate codes, technologies, functions, and other attributes. Pipe entities are designed for maximum flexibility, so you must define all of their attributes. ![]() Connectivity entities include more built-in functionality than pipes. Most common telecommunications connectivity scenarios can be implemented by using Connectivity entities, which are extensions of Pipe entities. You can use Pipe entities, Connectivity entities, or both to represent connectivity in your inventory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |