vrouter-ospf-area-add
This command is used to add areas and stubs as well as prefixes to an OSPF configuration.
Syntax vrouter-ospf-area-add
vrouter-name name-string |
Specify the name of the vRouter. |
Specify the following OSPF area arguments: |
|
area area-number |
Specify the stub area number for the configuration. Stub areas are shielded from external routes but receive information about networks that belong to other areas of the same OSPF domain |
stub-type none|stub|stub-no- |
Specify the stub type as stubby or not-so-stubby areas (NSSA). You can define totally stubby areas. Routers in totally stubby areas keep their Link State Database (LSDB)-only information about routing within their area, plus the default route. Not-so-stubby areas (NSSAs) are an extension of OSPF stub areas. Like stub areas, they prevent the flooding of AS-external link-state advertisements (LSAs) into NSSAs, relying instead on default routing to external destinations. As a result, NSSAs (like stub areas) must be placed at the edge of an OSPF routing domain. NSSAs are more flexible than stub areas in that an NSSA can import external routes into the OSPF routing domain, thereby providing transit service to small routing domains that are not part of the OSPF routing domain |
prefix-list-in vrouter prefix-list name |
Specify an inbound prefix list name to filter incoming packets. |
prefix-list-out vrouter prefix-list name |
Specify an outbound prefix list name to filter outgoing packets. |
Defaults None
Access CLI
History Command introduced in Version 2.2.3.
Usage An OSPF network can be divided into sub-domains called areas. An area is a logical collection of OSPF networks, routers, and links that have the same area identification.. A router within an area must maintain a topological database for the area to which it belongs. The router doesn't have detailed information about network topology outside of its area, thereby reducing the size of its database.
Areas limit the scope of route information distribution. It is not possible to do route update filtering within an area. The link-state database (LSDB) of routers within the same area must be synchronized and be exactly the same. However, route summarization and filtering is possible between different areas. The main benefit of creating areas is a reduction in the number of routes to propagate through the filtering and the summarization of routes.
Examples To add an OSPF area, 0, with the stub type, stub, use the following syntax:
CLI network-admin@switch > vrouter-ospf-area-add vrouter-name vrouter-ospf area 0 stub-type stub
vrouter-ospf-area-modify
This command is used to modify areas and stubs as well as prefixes to an OSPF configuration.
Syntax vrouter-ospf-area-modify
vrouter-name name-string |
Specify the name of the vRouter. |
Specify the following OSPF area arguments: |
|
area area-number |
Specify the stub area number for the configuration. Stub areas are shielded from external routes but receive information about networks that belong to other areas of the same OSPF domain |
stub-type none|stub|stub-no- |
Specify the stub type as stubby or not-so-stubby areas (NSSA). You can define totally stubby areas. Routers in totally stubby areas keep their Link State Database (LSDB)-only information about routing within their area, plus the default route. Not-so-stubby areas (NSSAs) are an extension of OSPF stub areas. Like stub areas, they prevent the flooding of AS-external link-state advertisements (LSAs) into NSSAs, relying instead on default routing to external destinations. As a result, NSSAs (like stub areas) must be placed at the edge of an OSPF routing domain. NSSAs are more flexible than stub areas in that an NSSA can import external routes into the OSPF routing domain, thereby providing transit service to small routing domains that are not part of the OSPF routing domain |
prefix-list-in vrouter prefix-list name |
Specify an inbound prefix list name to filter incoming packets. |
prefix-list-out vrouter prefix-list name |
Specify an outbound prefix list name to filter outgoing packets. |
Defaults None
Access CLI
History Command introduced in Version 2.2.3.
Usage An OSPF network can be divided into sub-domains called areas. An area is a logical collection of OSPF networks, routers, and links that have the same area identification.. A router within an area must maintain a topological database for the area to which it belongs. The router doesn't have detailed information about network topology outside of its area, thereby reducing the size of its database.
Areas limit the scope of route information distribution. It is not possible to do route update filtering within an area. The link-state database (LSDB) of routers within the same area must be synchronized and be exactly the same. However, route summarization and filtering is possible between different areas. The main benefit of creating areas is a reduction in the number of routes to propagate through the filtering and the summarization of routes.
Examples To modify an OSPF area, 0, and change the stub type to nssa, use the following syntax:
CLI network-admin@switch > vrouter-ospf-area-modify vrouter-name vrouter-ospf area 0 stub-type nssa
vrouter-ospf-area-remove
This command is used to remove an areas from an OSPF configuration.
Syntax vrouter-ospf-area-remove
vrouter-name name-string |
Specify the name of the vRouter. |
Specify the following OSPF area arguments: |
|
area area-number |
Specify the area number. |
Defaults None
Access CLI
History Command introduced in Version 2.2.3.
Usage An OSPF network can be divided into sub-domains called areas. An area is a logical collection of OSPF networks, routers, and links that have the same area identification.. A router within an area must maintain a topological database for the area to which it belongs. The router doesn't have detailed information about network topology outside of its area, thereby reducing the size of its database.
Areas limit the scope of route information distribution. It is not possible to perform route update filtering within an area. The link-state database (LSDB) of routers within the same area must be synchronized and be exactly the same. However, route summarization and filtering is possible between different areas. The main benefit of creating areas is a reduction in the number of routes to propagate through the filtering and the summarization of routes.
Examples To remove an OSPF area, 0, use the following syntax:
CLI network-admin@switch > vrouter-ospf-area-remove vrouter-name vrouter-ospf area 0
vrouter-ospf-area-show
This command is used to display information about areas and stubs as well as prefixes in an OSPF configuration.
Syntax vrouter-ospf-area-show
vrouter-name name-string |
Specify the name of the vRouter. |
Specify the following OSPF area arguments: |
|
area area-number |
Specify the stub area number for the configuration. Stub areas are shielded from external routes but receive information about networks that belong to other areas of the same OSPF domain |
stub-type none|stub|stub-no- |
Specify the stub type as stubby or not-so-stubby areas (NSSA). You can define totally stubby areas. Routers in totally stubby areas keep their Link State Database (LSDB)-only information about routing within their area, plus the default route. Not-so-stubby areas (NSSAs) are an extension of OSPF stub areas. Like stub areas, they prevent the flooding of AS-external link-state advertisements (LSAs) into NSSAs, relying instead on default routing to external destinations. As a result, NSSAs (like stub areas) must be placed at the edge of an OSPF routing domain. NSSAs are more flexible than stub areas in that an NSSA can import external routes into the OSPF routing domain, thereby providing transit service to small routing domains that are not part of the OSPF routing domain |
prefix-list-in vrouter prefix-list name |
Specify an inbound prefix list name to filter incoming packets. |
prefix-list-out vrouter prefix-list name |
Specify an outbound prefix list name to filter outgoing packets. |
Defaults None
Access CLI
History Command introduced in Version 2.2.3.
Usage An OSPF network can be divided into sub-domains called areas. An area is a logical collection of OSPF networks, routers, and links that have the same area identification.. A router within an area must maintain a topological database for the area to which it belongs. The router doesn't have detailed information about network topology outside of its area, thereby reducing the size of its database.
Areas limit the scope of route information distribution. It is not possible to do route update filtering within an area. The link-state database (LSDB) of routers within the same area must be synchronized and be exactly the same. However, route summarization and filtering is possible between different areas. The main benefit of creating areas is a reduction in the number of routes to propagate through the filtering and the summarization of routes.
Examples To display information about an OSPF area, use the following syntax:
CLI network-admin@switch > vrouter-ospf-area-show vrouter-name vrouter-ospf area 0 stub-type stub