Configuring physical ports with CLI

The buffer space is portioned out on a per port basis. Each port gets an amount of buffering which is its fair-share based on the port’s bandwidth compared to the overall active bandwidth.

This mechanism takes the buffer space available and divides it into a portion for each port based on the port’s active bandwidth relative to the amount of active bandwidth for all ports associated with the buffer space. The number of ports sharing the same buffer space depends on the type of MDAs populated on the IOM. An active port is considered to be any port that has an active queue associated. After a queue is created for the port, the system allocates the appropriate amount of buffer space to the port. This process is independently performed for both ingress and egress.

Normally, the amount of active bandwidth is considered as opposed to total potential bandwidth for the port when determining the port’s fair share. If a port is channelized and not all bandwidth is allocated, only the bandwidth represented by the configured channels with queues configured is counted toward the bandwidth represented by the port. Also, if a port may operate at variable speeds (as in some Ethernet ports), only the current speed is considered. Based on the above, the number of buffers managed by a port may change because of queue creation and deletion, channel creation and deletion and port speed variance on the local port or other ports sharing the same buffer space.

configure port 1/2/1 modify-buffer-allocation-rate percentage-of-rate ingress 200

configure port 1/2/1 modify-buffer-allocation-rate ing-percentage-of-rate 200

configure port 1/2/1 modify-buffer-allocation-rate percentage-of-rate egress 200

configure port 1/2/1 modify-buffer-allocation-rate egr-percentage-of-rate 200

[ex:/configure port 1/1/1]
A:admin@node-2# info
    admin-state enable
    access {
        egress {
            pool "default" {
                slope-policy "slopePolicy1"
            }
        }
    }
    network {
        egress {
            pool "default" {
                slope-policy "slopePolicy2"
            }
        }
    }

A:node-2>config>port# info 
----------------------------------------------
        access
            egress
                pool
                    slope-policy "slopePolicy1"
                exit
            exit
        exit
        network
            egress
                pool
                    slope-policy "slopePolicy2"
                exit
            exit
        exit
        no shutdown
----------------------------------------------

[ex:/configure port 1/1/1]
A:admin@node-2# info
    admin-state enable
    access {
        ingress {
            pool "default" {
                amber-alarm-threshold 10
                resv-cbs {
                    cbs 10
                    amber-alarm-action {
                        step 1
                        max 30
                    }
                }
            }
        }
    }
    ethernet {
        mode access
        encap-type dot1q
    }

A:node-2>config>port# info 
----------------------------------------------
        access
            ingress
                pool 
                    amber-alarm-threshold 10
                    resv-cbs 10 amber-alarm-action step 1 max 30
                exit
            exit
        exit
        ethernet
            mode access
            encap-type dot1q
        exit
        no shutdown

The following example shows a hybrid-buffer-allocation value change (from default) for ingress. In this example, the network-egress buffer pool is two times the size of the access-egress.

[ex:/configure port 1/1/2 hybrid-buffer-allocation]
A:admin@node-2# info
    egress-weight {
        access 20
        network 40
    }

A:node-2config>port>hybrid-buffer-allocation# info 
----------------------------------------------
egr-weight access 20 network 40

LAG configurations should include at least two ports. Other considerations include the following.

• A maximum of 64 ports (depending on the lag-id) can be included in a LAG. All ports in the LAG must share the port characteristics inherited from the primary port.

• Auto-negotiation must be disabled or set to limited mode for ports that are part of a LAG, to guarantee a specific port speed.

• Ports in a LAG must be configured as full duplex.

The following example shows the LAG configuration output.

[ex:/configure lag "lag-2"]
A:admin@node-2# info
    description "LAG2"
    mac-address 04:68:ff:00:00:01
    dynamic-cost true
    port-threshold {
        value 4
        action down
    }
    port 1/1/1 {
    }
    port 1/3/1 {
    }
    port 1/5/1 {
    }
    port 1/7/1 {
    }
    port 1/9/1 {
    }
 

A:node-2>config>lag# info detail
----------------------------------------------
        description "LAG2"
        mac 04:68:ff:00:00:01
        port  1/1/1
        port  1/3/1
        port  1/5/1
        port  1/7/1
        port  1/9/1
        dynamic-cost
        port-threshold 4 action down
----------------------------------------------

The 7705 SAR-Hx and 7705 SAR-Mx are equipped with an integrated GNSS receiver and GNSS RF port for retrieval and recovery of GPS and Galileo signals.

Use the commands in the following context to configure integrated GNSS RF ports, including antenna-cable delay, signal recovery, and elevation-mask angle.

configure port gnss

Use the following command to configure an IEEE C37.94 TPIF port on an 8-port RS-232 and C37.94 combination MDA on the 7705 SAR-Hx and 7705 SAR-Mx.

configure port tdm tpif

A:node-2>config>port>tdm>tpif$ info detail
----------------------------------------------
                shutdown
                no loopback
                report-alarm los rai
                channel-group 1
                    shutdown
                    no description
                    timeslots 1
                exit
----------------------------------------------

Use the following CLI syntax to configure raw socket parameters on an RS-232 serial port.

A:node-2>config>port>serial>rs232$ info detail
----------------------------------------------
                shutdown
                no loopback
                character-length 8
                no parity
                stop-bits 1
                control-lead
                    input
                        dtr-dsr high
                        rts-dcd high
                    exit
                    output
                        dcd-rts high
                        cts-alb high
                        ri-rdl high
                    exit
                    monitor
                        dtr-dsr off
                        rts-dcd off
                    exit
                exit
                s-bit-signaling off
                no data-position
                no mon-data-inactivity
                no hold-time
                report-alarm ctrlLeadMon monDataInac
                no report-alarm hcmOof hcmRai
                speed 9600
                socket 1
                    shutdown
                    description "SOCKET"
                    rx
                        eop
                            length 1500
                            idle-timeout 50
                            no special-char
                        exit
                        no squelch-delay
                        no unsquelch-delay
                    exit
                    tx
                        inter-session-delay 10
                    exit
                exit
----------------------------------------------