Service-Port Interfaces
The service-port interface controls communications through and is statically mapped by the system to the service port. The service port can be used for out-of-band management.
The service port can obtain an IPv4 address using DHCP, or it can be assigned a static IPv4 address, but a default gateway cannot be assigned to the service-port interface. Static IPv4 routes can be defined through the controller for remote network access to the service port.
If the service port is in use, the management interface must be on a different supernet from the service-port interface.
Similarly, the service port can be statically assigned an IPv6 address or select an IPv6 address using Stateless Address Auto-Configuration (SLAAC). The default gateway cannot be assigned to the service-port interface. Static IPv6 routes can be defined through the controller for remote network access to the service port.
![]() Note |
While IPv6 addressing is used along with stateless address auto-configuration, the controller does not perform the subnet verification; however, you must not connect the service-port in the same subnet as the other interfaces in the controller. |
![]() Note |
This is the only SLAAC interface on the controller, all other interfaces must be statically assigned (just like for IPv4). |
![]() Note |
User does not require IPv6 static routes to reach service port from the same network, but IPv6 routes requires to access service port from different network. The IPv6 static routes should be as same as IPv4. |
The service-port interface supports the following protocols:
-
SSH and Telnet
-
HTTP and HTTPS
-
SNMP
-
FTP, TFTP, and SFTP
-
Syslog
-
ICMP (ping)
-
NTP
![]() Note |
TACACS+ and RADIUS are not supported through the service port. |
This section contains the following subsections: