In this section:
Host information, DNS settings, and other Node-Level options are configured in the SBC Edge Portfolio via the WebUI as outlined below. The Host Information contains system information attributes that are used by the SNMP manager.
Changing Host Information
To change the host information for your SBC Edge Portfolio:
- In the WebUI, click the Settings tab.
In the left navigation page, go to System > Node-Level Settings.
Node-Level - Field Definitions
Node-Level Network Settings
Defines whether the node level settings are set through dynamic or static configuration. Available options: Dynamic (configured by system) or Static (configured manually). The Dynamic option is available only when one or more logical interfaces are configured to use Dynamic addressing.
Host Information - Field Definitions
Host Name
Specifies the DNS host name for the system.
Domain Name
Specifies the DNS domain name for the system. This field is available only if Node-Level Network Settings is set to Static.
You must populate this field for Microsoft Teams Direct Routing deployments or if you are using certificates for TLS.
System Description
Sets the SNMP attribute 'sysDescription' in the System-Group MIB. Operator may use this field to record a short description of the system. By convention, this field should include the full name and the hardware type.
System Location
Sets the SNMP attribute 'sysLocation' in the System-Group MIB. Operator may use this field to record the physical location of the system.
System Contact
Sets the SNMP attribute 'sysContact' in the System-Group MIB. Operator may use this field to record the contact person for this system and information about how to contact this person.
Domain Name Service - Field Definitions
Primary vs. Secondary DNS
The SBC contacts the secondary DNS server if the DNS service (UDP port 53) on the primary DNS server is unreachable. The SBC does not contact the secondary DNS server if the primary DNS server responds to a DNS query with either a positive or negative response. If the primary DNS server responds with the result no such domain, no such host. or no such name: the negative response is cached for one hour. Consequently, that FQDN is not queried by the SBC for the next one hour. If the operator updates the DNS server with a proper record for the FQDN for which the earlier query failed, the DNS cache should be manually cleared. Positive responses are cached for a period specified by the TTL in the DNS record.
The Primary and/or Secondary DNS server addresses can be IPv6. If the domain name being resolved has both an IPv4 and IPv6 as the Primary and or Secondary IP address, the SBC gives priority to the IPv6 address. For example, if the domain maps to both192.168.20.143 and fc00:50::50, the fc00:50::50 address is used first.
Use Primary DNS
Specifies whether or not the SBC uses DNS. Available options: Yes or No. This field is available only if Node-Level Network Settings is set to Static.
Primary Server IP
Specifies the IPv4 or IPv6 address of the Primary DNS server. If the Node-Level Network Settings drop down box is set to Dynamic, this field is configured automatically. Field is displayed when Use Primary DNS is set to Yes.
Primary Source
Field lists all Logical Interfaces for the Primary DNS. The IP address selected is used as the source IP for the corresponding DNS queries.
Definitions for available options include:
- <IP Address>: Source IP is the IP address associated with the source IP for the corresponding DNS queries.
- Auto: Source IP is the IP address of the interface which is used for the DNS query.
Use Secondary DNS
Specifies whether or not a secondary DNS server is used.
Secondary Server IP
Specifies the IPv4 or IPv6 address of the Secondary DNS server. If Node-Level Network Settings is set to Dynamic, this field is configured automatically. Field is displayed when Use Secondary DNS is set to Yes.
Secondary Source
Field lists all Logical Interfaces for the Secondary DNS. The IP address selected is used as the source IP for the corresponding DNS queries.
- <IP Address>: Source IP is the IP address associated with the source IP for the corresponding DNS queries.
- Auto: Source IP is the IP address of the interface which is used for the DNS query.
Enable DNS Service
This field not applicable to the SBC SWe Edge.
When enabled, the SBC accepts DNS requests, and either serves them locally or forwards them as necessary. Valid entry: Yes (DNS request is forwarded or served locally as necessary) or No (DNS requests are not handled by the SBC). Default entry: No.
Time Management - Field Definitions
Time Zone
Sets the time zone for the node.
Use NTP
Determines whether to use Network Time Protocol (NTP) as a time source.
NTP Server
Specifies the FQDN, IPv4, or IPv6 address of the first NTP server. If the host name is supplied, the SBC uses the DNS to connect to the NTP server. This field is available only when the Use NTP field is set to Yes.
NTP Server Authentication
Specifies whether or not to use authentication when communicating with the NTP server. Available options: Enabled or Disabled. This field is available only when Yes is selected from the Use NTP list box.
NTP Server - MD5 Key ID
Specifies the MD5 Key ID to be used in authenticating the first NTP server. This field is available only when the NTP Server Authentication field is Enabled.
NTP MD5 Key
Specifies the MD5 key used when authenticating the first NTP Server. This field is available only when the NTP Server Authentication field is Enabled.
Use NTP Server 2
Specifies whether or not to use a second NTP Server as a time source.
NTP Server 2
Specifies the FQDN, IPv4 or IPv6 address of the second NTP server. If the hostname is supplied, the SBC uses the DNS to connect to the NTP server. This field is available only when Yes is selected from the Use NTP Server 2 list box.
NTP Server 2 Authentication
Specifies whether or not to use authentication when communicating with the second NTP server. This field is available only when Yes is selected from the Use NTP Server 2 list box.
NTP Server 2 - MD5 Key ID
Specifies the MD5 Key ID to be used in authenticating the second NTP server. This field is available only when Enabled is selected from the NTP Server 2 Authentication list box.
NTP Server 2 - MD5 Key
Specifies the MD5 key used when authenticating the second NTP Server. This field is available only when Enabled is selected from the NTP Server 2 Authentication list box.
DHCP Server - Field Definitions
Enable DHCP Server
This field not applicable to the SBC SWe Edge.
System LEDs
System LEDs are only supported on SBC 1000/2000.
Power LED
This field is automatically populated with the current status of the Power LED. Options are: Green (indicates the system is connected to a power source) or Off (unit is not connected to power source). For additional information about the Power LED's color and status definitions, refer to SBC 1000-2000 Status LEDs.
Alarm LED
This field is automatically populated with the current status of the Alarm LED on the front panel. Possible entries: Green (no alarm), Off (warning), Amber (minor alarm), Red (major alarm), Red Blinking (critical alarm). For additional information about the Alarm LED's color and status definitions, see SBC 1000-2000 Status LEDs.
Ready LED
This field is automatically populated with the current status of the Ready LED on the front panel. Options are: Green (indicates the system is fully initialized) or Off (system is not fully initialized). For additional information about the Ready LED's color and status definitions, see SBC 1000-2000 Status LEDs.
Locator LED
This field provides the option to set the Locater LED on the front of the SBC unit to either Off (LED is off), On Green (LED is green) or Blinking Green (LED blinks one time per second). Default entry: On Green. This option helps network personnel easily locate the SBC unit in a rack with other equipment. This LED is also recognized as the Peer Node Status LED. For additional information about the Locator LED's color and status definitions, see SBC 1000-2000 Status LEDs.
Ribbon Application Management Platform - Field Definitions
Ribbon Application Management Platform
Configure this field to enable or disable the Ribbon Application Management Platform
- No (default) - The Ribbon Application Management Platform is disabled.
- Yes - The Ribbon Application Management Platform is enabled.
Ribbon Application Management Platform Address
Configure this field with the IP address or FQDN of the Ribbon Application Management Platform.
This field applies only when the Ribbon Application Management Platform field is set to Yes.
Management ID
When you enter the Management ID, you must insert a colon every two characters (00:00:00). Otherwise, the SBC SWe Edge cannot connect to the Ribbon Application Management Platform.
Configure this field with the Management ID. For information about retrieving the Management ID, refer to Obtaining and Installing an SBC SWe Edge Production Node-Locked License.
This field only applies to the SBC SWe Edge, and only when the Ribbon Application Management Platform field is set to Yes. The SBC 1000/2000 automatically sends the MAC address to the Ribbon Application Management Platform.
Ribbon Application Management Platform Connection
The status of the SBC’s connection to the Ribbon Application Management Platform. This status may be one of the following:
- Down
- Up
This field only applies when the Ribbon Application Management Platform field is set to Yes.
Ribbon Application Management Platform Tunnel Status
The status of the HTTPS tunnel from the Ribbon Application Management Platform to the SBC. This status may be one of the following:
- Not Connected
- Up
This field only applies when the Ribbon Application Management Platform field is set to Yes.
RAMP Online Licensing
The status of the NWDL Licensing on the SBC. This status may be one of the following:
- NWDL
- SBCaaS (Ribbon Connect)
- None
This field only applies to the SBC SWe Edge, and only when the RAMP field is set to Yes.
Country Level Information
Configure this field with the country code in which the SBC resides.
Configuring Node Level Options
The following Configuration options are available from the Node Level Settings menu bar:
Node Level Options