Creating a Virtual Router for the CMTS Device with SDX Admin
You need to add a virtual router object called default to the CMTS device. To add a virtual router with SDX Admin:
The New EdgeDevice dialog box appears.
The default virtual router appears in the navigation pane, and information about the virtual router appears in the VirtualRouter pane.
![]()
- Configure virtual router parameters in the Main Tab. See Configuration Parameters for Virtual Routers.
- Select the SAE Connection tab of the VirtualRouter pane, and add SAEs that are connected to the CMTS device. This list becomes the community of SAEs.
Configuration Parameters for Virtual Routers
Use the fields in this section to define virtual router objects. If you are using assigned IP subscribers along with the NIC, you need to configure either a local or static address pool so that the NIC can resolve the IP-to-SAE mapping.
SNMP Read Community
- SNMP community name associated with SNMP read-only operations for this VR.
- Value—Text string
- Example—admin
SNMP Write Community
- SNMP community name associated with SNMP write operations for this VR.
- Value—Text string
- Example—public
Scope
- Service scopes assigned to this VR—See Configuring Service Scopes in SRC-PE Services and Policies Guide, Chapter 2, Managing Services on a Solaris Platform.
- Value—Text string
- Example—POP-Westford
Local Address Pools
- List of IP address pools that the VR currently manages and stores. You must configure either a local address pool or a static address pool so that the NIC can resolve the IP-to-SAE mapping.
- Value—List of IP address pools. You can specify an unlimited number of IP address pools. You can specify either the first and last addresses in a range, or you can specify a subnet address, a subnet mask, and a list of addresses to exclude from the subnet.
The IP pool syntax has the following format:
([<ipAddressStart> <ipAddressEnd>] |
{<ipBaseAddress>/(<mask> | <digitNumber>)(,<ipAddressExclude>)*})
- <ipAddressStart>—First IP address (version 4 or 6) in a range
- <ipAddressEnd>—Last IP address (version 4 or 6) in a range
- <ipBaseAddress>—Network base address
- <mask>—Subnet mask
- <digitNumber>—Integer specifying the length of the subnet mask
- <ipAddressExclude>—List of IP addresses to be excluded from the subnet
- |—Choice of expression; choose either the expression to the left or the expression to the right of this symbol
- *—Zero or more instances of the preceding group
You can use spaces in the syntax only to separate the first and last explicit IP addresses in a range.
Static Address Pools
- List of IP address pools that the VR manages but does not store. You can configure these address pools only in the SRC software. You must configure either a local address pool or a static address pool so that the NIC can resolve the IP-to-SAE mapping.
- Value—See the field Local Address Pools.
- Default—No value
- Example—([10.10.10.5 10.10.10.250] {10.20.20.0/24})
Managing SAE IOR
- Common Object Request Broker Architecture (CORBA) reference for the SAE managing this VR.
- Value—One of the following items:
- The actual CORBA reference for the SAE
- The absolute path to the interoperable object reference (IOR) file
- A corbaloc URL in the form corbaloc::<host>:8801/SAE
- Guidelines—The PoolPublisher and IorPublisher router initialization scripts provide this information when the router connects to the SAE. For information about configuring router initialization scripts, see SRC-PE Network Guide, Chapter 6, Using JUNOSe Routers in the SRC Network with a Solaris Platform or SRC-PE Network Guide, Chapter 8, Using JUNOS Routing Platforms in the SRC Network with a Solaris Platform. If you do not select one of these router initialization scripts, enter a value in this field.
- Default—No value
- Example—One of the following items:
- Absolute path— /opt/UMC/sae/var/run/sae.ior
- corbaloc URL—boston:8801/sae
- Actual IOR— IOR:000000000000002438444C3A736D67742E6A756E697...
Tracking Plug-in
- Plug-in instances that track interfaces that the SAE manages on this VR. The SAE calls these plug-ins after an interface comes up, when new policies are installed on the interface, and when the interface goes down.
- Value—Comma-separated list of plug-in instances
- Guidelines—Enter plug-in instances and NIC SAE plug-in agents that are specific to this VR. For information about configuring tracking plug-ins, see SRC-PE Subscribers and Subscriptions Guide, Chapter 11, Configuring Accounting and Authentication Plug-Ins with the SRC CLI.
- Default—No value
- Example—nicsae, flexRadius
Configuring SAE Communities
You define SAE communities by entering the SAEs in a community in the connected SAE field of the virtual router object.
When you modify a community, wait for passive session stores on the new community members to be updated before you shut down the current active SAE. Otherwise, if you add a new member to a community, and then a failover from the current active SAE to the new member is triggered immediately, the new member's session store may not have received all data from the active SAE's session store.
To define a community, select the SAE Connection tab of the VirtualRouter pane, and add the addresses of SAEs that can manage this CMTS device.
- Double-click the IP address of the SAE in the Connected SAE box.
- Modify the IP address in the field below the Connected SAE box.
- Click Modify.
- Double-click the IP address of the SAE in the Connected SAE box.
- Remove the IP address from the field below the Connected SAE box.
- Click Delete.
Connected SAE