Parameter | Length/Range | Description |
|---|
action
| N/A | Action to take when putting the IP interface out of service: |
altIpAddress
| N/A | The alternative (secondary) IP address for the configured packet IP interface. The alternative IP address is optional, but if used must be a different IP address type than ipAddress parameter. The following IP address types are supported: IPv4 – This is IPv4 address in dotted decimal form (for example 128.127.50.224).IPv6 – This is IPv6 address in hexadecimal/colon form (for example, 1280:1276:3350:2224:2222:3333:8888:1245 or fd00:21:445:128::7880).
NOTE: Modify the alternative IP address only after changing the packet IP interface to disabled state. |
altMediaIpAddresses | IPv4 and/or IPv6 address(es) | Use this parameter to specify up to 254 additional IPv4 and/or IPv6 media IP addresses on this IP interface. Any combination of IPv4 and IPv6 is allowed. The following rules apply when configuring alternate media IP addresses: - An IPv4/IPv6 alternate media IP address is only allowed if an IPv4/IPv6 address is defined in the primary or alternate (main) address.
- An alternate media IP address must be in the same network as the primary media address (of the same IP version). Hence, CPX needs to determine the subnet based on the primary/alt IP address and primary/alt prefix, and then verify that the given alternate media address is on the same subnet.
- An alternate media IP address may be added while the IP interface is enabled and in-service. However, the IP can only be deleted when the IP interface state is set to "disabled".
|
altPrefix
| 0-128 | Alternative IP subnet prefix of this interface. |
bandwidth
| 0-2147483647 | Maximum amount of bandwidth allowed in units of bytes per second for this IP interface. 0 – Allow bandwidth subscriptions up to the maximum supported on the physical port.<non-zero> – Allow up to the specified number of bytes per second on this IP interface. The aggregate of this number and all previously provisioned IP interfaces must not exceed the physical port bandwidth.
NOTE: When calculating bandwidth size, keep in mind that an IPv6 header size (40 bytes) is twice as large as IPv4 header (20 bytes), thus reducing the number of messages when using IPv6. |
bfd | 24 | <bfd_session_name> - The BFD session name. For information about BFD, refer to Bidirectional Forwarding Detection.
See bfd Parameters for the bfd parameters. |
bfdStatus | 24 | <bfd_session_name> - The BFD session name.
bfdOperState - The operational state of the BFD session on a LIF. You cannot configure this flag.
down - The BFD session with the peer is not running.up - The BFD session with the peer is running.
|
bwContingency
| 0-100 | The percentage of maximum bandwidth reserved for contingency (that is, non-media). The maximum bandwidth is the bandwidth normally available for media on the interface. (This is based on the configured bandwidth limit or the physical port bandwidth limit minus approximately 5% for signaling traffic). The contingency factor effectively reserves a portion of this bandwidth for non-media. |
ceName
| 1-255 | The name of the computing element that hosts the port used by this IP interface. NOTE: ceName is currently not used by the . |
dryupTimeout
| 1-1440 | The dry-up timeout in minutes (e.g. the number of minutes to wait before taking the interface out of service). This is started at the point where the command to make the interface out of service is issued. This is only applicable for media traffic, if there is no media traffic on the interface then it is immediately taken out of service. (default = 60) NOTE: To do a dry-up for an interface used only for Signaling, perform a dry-up procedure of the sipSigPort associated to the interface. |
ipAddress
| N/A | The primary IP address of the interface. The following IP address types are supported: IPv4 – This is V4 IP address in dotted decimal form (for example 128.127.50.224).IPv6 – This is V6 IP address in hexadecimal/colon form (for example, 1280:1276:3350:2224:2222:3333:8888:1245 or fd00:21:445:128::7880).
NOTE: Duplicate Address Detection procedures are performed on interfaces configured with IPv6 addresses. If a duplicate address is found in the network, a warning message is output to Linux logs at /var/log/syslog and /var/log/messages. Example message: “Nov 12 08:52:35 SBC-1 kernel: [854194.740638] mgt1: IPv6 duplicate address fc00::100:0:0:100:1 detected“
|
mode
| N/A | The operational mode of the IP interface: inService (default) – This state is set by default when state is enabled.outOfService – Set mode to “outOfService” before changing the state to “disabled”.
NOTE: When setting mode to 'outOfService', be sure to also set state to 'disabled'. |
portName
| N/A | The physical port name used by this IP interface. Supported physical port names are: mgmt0 – Primary management Ethernet port for OAM.mgmt1 – Secondary management Ethernet port for OAM.pkt0 – First Gigabit Ethernet port used for signaling and media traffic.pkt1 – Second Gigabit Ethernet port used for signaling and media traffic.pkt2 – Third Gigabit Ethernet port used for signaling and media traffic.pkt3 – Fourth Gigabit Ethernet port used for signaling and media traffic.
Packet ports (pkt) identify the physical ports used for signaling and media, whereas media ports are UDP ports used to carry media traffic. NOTE: ipInterfaceGroup and ipInterface should not be configured for mgmt0 and mgmt1 ports. Instead, configure mgmt0 and mgmt1 ports using mgmtIpInterfaceGroup and mgmtIpInterface. |
prefix
| 0-128 | The IP subnet prefix of this Interface. Default = 16. |
state
| N/A | Administrative state of the IP interface. disabled (default) – In this state the IP interface is inactive and does not respond to a ping.enabled – In this state the IP interface is active and responds to a ping if the Ethernet cable is connected.
|
vlanTag
| 2-4094 | VLAN tags are required if more than one IP Interface is associated with a single physical port on the . Enter a value from 2 to 4094.NOTE: A vlanTag is exclusive to a physical port. Therefore, the does not create two interfaces with the same vlanTag on the same physical port.NOTE: Do not configure more than 2,048 VLAN tags on the SBC 5100 due to memory constraints. |