You can manage your local gateway through a GUI. A local gateway route table is owned by an Amazon Web Services account ID. If you want to manage multiple local gateways, you can use the describe operation. This operation returns results matching all the filters in the route table. You can also add emergency routing to your local gateway.
Interface specific route option
The Interface specific route option allows you to configure a local gateway to use an IP address that is not directly assigned to an IP address on your router. This is useful in cases where the gateway does not reside in the same subnet as the interface. This option is found under Advanced Gateway Settings. Once you have configured this setting, the router will use the most specific route for the destination Subnet.
In order to configure an interface specific route, you need to select the flag R, M, C, or I. The R flag indicates that the route is specific to Linux, while the M and C flags indicate that the interface is for a network other than your router. You can also use the I flag to specify an IP address that is specific to your router, but this is optional.
The next step in configuring a local gateway is to define the destination. You can either enter the IP address of the router directly, or you can use the IP address of the computer to specify the destination. You can also specify a mask for the destination. Once you know which interface is being used, the gateway IP address will be added to the router’s routing table.
Automatic metric feature
Automatic Metric is a feature of the Windows operating system that configures a metric for each IP route of a network interface. The metric can be defined in terms of hop count, link speed, or time delay. By default, Automatic Metric will automatically configure the metric for a local route based on the link speed. However, if you aren’t satisfied with the default value, you can manually configure the metric.
The default value of this metric is 256. You can change it to a higher or lower value. You can also assign a metric to each gateway independently. This will give you more flexibility over the network interface routes. The lower the metric, the higher connection priority will be for the network adapter.
GUI for managing local gateways
The GUI provides users with the ability to configure and manage local gateways. Among the many options available, the GUI allows users to configure the IP address, Name and Interface of a gateway. Depending on the type of gateway, the IP address may be IPv4 or IPv6. The name is also important, since it will appear in the gateway list. The name should only contain alphanumeric characters, underscore, and no spaces.
The interface field is used to specify which gateway should be accessed by the client. Normally, the value is one. However, some clients may need more than one interface. Hence, you can set the interface metric to a value between one and eight. However, there are some cases in which the interface may not be in the same subnet. In such cases, a special setting is available in the Advanced Gateway Settings.
The Node Manager application provides a user interface for managing the local gateways. It is used for configuring policies, and it also offers a way to protect the local gateways. By default, a Node Manager instance has a name of Gateway1 and a group name of Group1. By default, SSL/HTTP connection is selected, and the port is 8085 or 8080.
The main menu contains several tabs, including System, Gateway, and Status. There is also an option to change the gateway password. To do this, you must enter the current password of the gateway and confirm it. You can also see statistics, which shows the data sent over LAN, WLAN, and Cellular.
Configuring emergency routing to a local gateway
The first step in configuring emergency routing is to configure the system to use the local gateway. You can do this in the System Configuration interface. You can change the number of routes to use and to specify a feature access code. Then, you can configure a route pattern for emergencies.
Next, you can configure emergency numbers, masks, and PSTN routes per emergency number. You can assign emergency numbers to users, network sites, or both. To configure emergency routing, you must have an IP address and a corresponding ALI database. Configure the emergency routing policy for all sites, users, or both. You can also configure the policy for each network site. The configuration of emergency numbers varies depending on the type of emergency.
Another important configuration step is to configure the emergency routing policy on the teams client. Once you’ve done this, you can log in the Avaya IP Softphone to the new location. This configuration is also required when using the Direct Routing service or OnlineVoiceRoute.
Once the routing policy is configured, the EGW will send emergency calls to the PSAP using the ERL and route list you configure. The PSAP will then look up the ALI number in the ALI database and route the call. The PSAP can then make a call back to the emergency caller if necessary.
You can also use an ERL debug tool to check the ERL for the phones that have emergency routing. If the ERL is not set properly, the routing can be incorrect. If you don’t want to use emergency routes, you can configure the network manager to use a default gateway that is not defined.