9. Layer 2 and Layer 3 Services

The 7705 SAR-Hm series of routers support the services listed below:

  1. Layer 2 services:
    1. Virtual Leased Line (VLL) Services
    2. Virtual Private LAN Service (VPLS)
  2. Layer 3 services:
    1. Internet Enhanced Service (IES)
    2. Virtual Private Routed Network Service (VPRN)
    3. IP Transport Services

9.1. Virtual Leased Line (VLL) Services

For general information on VLL support, refer to the topics listed below in the “VLL Services” chapter of the 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 2 Services and EVPN Guide: VLL, VPLS, PBB, and EVPN.

  1. Ethernet Pipe (Epipe) Services
    1. Epipe Service Overview
    2. Epipe Service Pseudo-Wire VLAN Tag Processing
    3. Epipe Up Operational State Configuration Option
  2. Pseudo-Wire Redundancy Service Models
  3. BGP Virtual Private Wire Service (VPWS)
    1. Single-Homed BGP VPWS
    2. Dual-Homed BGP VPWS
  4. VLL Service Considerations
  5. Configuring a VLL Service with CLI
  6. Service Management Tasks

For descriptions of VLL services commands, refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Classic CLI Command Reference Guide and to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Clear, Show, and Tools Command Reference Guide.

9.2. Virtual Private LAN Service (VPLS)

For general information on VPLS support, refer to the topics listed below in the “Virtual Private LAN Service” chapter of the 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 2 Services and EVPN Guide: VLL, VPLS, PBB, and EVPN.

  1. VPLS Service Overview
  2. VPLS Features
    1. VPLS Service Pseudo-Wire VLAN Tag Processing
    2. VPLS MAC Learning and Packet Forwarding
    3. Pseudo-Wire Control Word
    4. Table Management
    5. Split Horizon SAP Groups and Split Horizon Spoke SDP Groups
    6. VPLS and Spanning Tree Protocol
    7. VPLS Access Redundancy
    8. Object Grouping and State Monitoring
    9. MAC Flush Message Processing
    10. ACL Next-Hop for VPLS
    11. SDP Statistics for VPLS and VLL Services
    12. BGP VPLS
    13. BGP Multi-Homing for VPLS
  3. Routed VPLS and I-VPLS
    1. IES or VPRN IP Interface Binding
    2. IP Interface MTU and Fragmentation
    3. ARP and VPLS FDB Interactions
    4. The allow-ip-int-bind VPLS Flag
    5. R-VPLS Caveats
  4. VPLS Service Considerations
  5. Configuring a VPLS Service with CLI
  6. Service Management Tasks

For descriptions of VPLS service commands, refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Classic CLI Command Reference Guide and to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Clear, Show, and Tools Command Reference Guide.

9.3. Internet Enhanced Service (IES)

For general information on IES support, refer to the topics listed below in the “Internet Enhanced Service” chapter of the 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 3 Services Guide: IES and VPRN.

  1. IES Service Overview
  2. IES Features
    1. IP Interfaces
      1. Object Grouping and State Monitoring
    2. SAPs
      1. Encapsulations
      2. Shaping and Bandwidth Control
    3. Routing Protocols
    4. QoS Policies
    5. Filter Policies

For descriptions of IES commands, refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Classic CLI Command Reference Guide and to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Clear, Show, and Tools Command Reference Guide.

On the 7705 SAR-Hm series of routers, IES services are supported on Ethernet ports. IES services are not supported over cellular ports or the WLAN interface.

9.4. Virtual Private Routed Network Service (VPRN)

For general information on VPRN support, refer to the topics listed below in the “Virtual Private Routed Network” chapter of the 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 3 Services Guide: IES and VPRN.

  1. VPRN Service Overview
    1. Routing Prerequisites
    2. Core MP-BGP Support
    3. Route Distinguishers
    4. Route Reflector
    5. CE-to-CE Route Exchange
    6. Constrained Route Distribution (RT constraint)
    7. BGP Best-External in a VPRN Context
  2. VPRN Features
    1. IP Interfaces
      1. Traffic Differentiation Based on Route Characteristics
      2. Associating an FC Priority with a Route
      3. Displaying QoS Information Associated with Routes
      4. Object Grouping and State Monitoring
      5. VPRN IP Interface Applicability
    2. SAPs
      1. Encapsulations
      2. Pseudowire SAPs
    3. QoS Policies
    4. Filter Policies
    5. DSCP Marking
    6. Configuration of TTL Propagation for VPRN Routes
    7. CE to PE Routing Protocols
    8. Spoke SDPs
    9. IP-VPNs
    10. Traffic Leaking to GRT
    11. Traffic Leaking from VPRN to GRT for IPv6
    12. RIP Metric Propagation in VPRNs
    13. NTP within a VPRN Service
    14. VPN Route Label Allocation
  3. QoS on Ingress Binding
  4. FIB Prioritization
  5. Configuring a VPRN Service with CLI
  6. Service Management Tasks

For descriptions of VPRN commands, refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Classic CLI Command Reference Guide and to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Clear, Show, and Tools Command Reference Guide.

9.5. IP Transport Services

This section provides information on the following topics:

  1. Raw Socket IP Transport Service
  2. GNSS NMEA Data IP Transport Service
  3. Serial Raw Socket IP Transport Configuration Commands Hierarchy
  4. IP Transport Show Commands Hierarchy
  5. IP Transport Clear Commands Hierarchy

9.5.1. Raw Socket IP Transport Service

Serial data transport using raw sockets over IP transport services is a method of transporting serial data, in character form, over an IP network using Layer 3-based services. This feature can help transport Supervisory Control and Data Acquisition (SCADA) data from Remote Terminal Units (RTUs) to Front-End Processors (FEPs), or SCADA masters.

The functionality provided by the IP transport service feature for serial raw sockets is summarized as follows:

  1. IP transport local host server function, to listen and open raw socket sessions from remote hosts
  2. IP transport remote host client function, to initiate and open new raw socket sessions to remote hosts
  3. Both local host and remote host functions support either TCP or UDP IP transport services
  4. IP transport over a VPRN service
  5. Enhanced QoS and queuing of sessions to ensure collisions between sessions do not cause serial data to impact RTUs and end-user equipment

Figure 12 illustrates a more detailed view of the local host (server) and remote host (client) functionality that enables multiple communication streams to and from a serial port using raw socket IP transport.

The figure shows a three-node network, a 7705 SAR-Hm (left), a 7705 SAR-8/7705 SAR-18 (top-right) and a 7750 SR/VSR (bottom right). There are two devices, RTU (1) and RTU (2) connected to the serial ports on the 7705 SAR-Hm. The FEP server [A] can reach the RTUs the via socket sessions that originate from the SDI card on the 7705 SAR-8/7705 SAR-18 node.

The bottom right 7750 SR or VSR node is connected to FEP server [B] directly using Ethernet. This FEP server reaches the RTUs via a Layer 3 VPRN service where TCP and UDP sessions originating from the FEP server [B] terminate on the 7705 SAR-Hm to deliver the raw socket serial data to the RTUs.

Through local host and remote host configurations on the 7705 SAR-Hm, 7705 SAR-8, or 7705 SAR-18, serial raw socket IP transport sessions are established to carry serial data over a wireless IP/MPLS network. The source and destination IP addresses and port numbers for these sessions are derived directly from the local/remote host configurations associated with each serial port or master head-end server. Further details are described in the subsequent sections.

Figure 12:  IP Transport Service 

A raw socket IP transport interface can be configured for each serial port. This allows the raw socket IP transport to receive TCP or UDP session packets from multiple remote hosts when operating as a local host (server), or to create new multiple sessions to remote hosts to send and receive serial data when operating as a client.

There are two main configurations required for a serial raw socket IP transport service to be operational and support the sending and receiving of serial data:

  1. Port-level socket configuration—This includes rudimentary serial link parameters such as baud rate, start/stop values, and bits.
    Also, socket-level configuration is required, such as end-of-packet checking parameters (idle-time, length, special character), and the inter-sessions delay for transmitting sessions data out the serial link. For information on the required port-level configuration, refer to the 7705 SAR-Hm and SAR-Hmc Interface Configuration Guide, Command Reference chapter, “Serial Raw Socket Interface Configuration Command Hierarchy”.
  2. IP transport service-level configuration—This includes creating an IP transport subservice to associate the serial port within a Layer 3 VPRN service, so that TCP/UDP encapsulated serial data can be routed within the corresponding Layer 3 service. The IP transport subservice ID is modeled and created identical to creating SAP IDs under the same service types. IP transport configuration includes IP transport local host items and remote host items, such as TCP timers and sessions controls. These are described further in the sections that follow. Also, see Serial Raw Socket IP Transport Configuration Commands Hierarchy for the required information.

A raw socket IP transport service configured for a serial port allows the IP transport local host to listen to and open raw socket sessions from remote hosts that need to communicate over the serial port, and for each serial port’s local host to initiate and open raw socket sessions to remote hosts when serial data needs to be sent to those remote hosts. The local and remote host functions support TCP or UDP sessions (but not both concurrently) over the VPRN service.

The serial data is received as characters that represent bytes in a packet. These bytes are packetized into Layer 3 TCP/UDP packets that are then transported or forwarded across the IP/MPLS network using the node's Layer 3 VPRN service constructs for routing. Figure 13 illustrates how serial data is encapsulated into TCP/UDP packets and transported over IP/MPLS. When using a cellular port, GRE-MPLS and encapsulations for the service would be included, but this is not shown in the figure.

Figure 13:  TCP/UDP Packet Transport Over IP/MPLS 

For raw socket packets to be routed within a VPRN service, an IP transport subservice must be configured within a VPRN context. The IP transport subservice context is where users configure local host and remote host information, such as IP addresses and ports for establishing TCP/UDP sessions, and other per-session parameters. TCP/UDP encapsulated serial data is routed within the corresponding Layer 3 VPRN service. Figure 14 illustrates this basic concept.

Figure 14:  VPRN IP Transport Service 

To create an IP transport subservice, the ip-transport command is used with the corresponding serial port as the ipt-id to bind the serial port SAP to the IP transport subservice. After the IP transport service is created, local host and remote host configurations can proceed. A local host must be configured before remote hosts can be configured.

Each local host uses a local address (from a loopback or local interface configured under the VPRN service context) as the local host IP address (that is, the source IP address in the raw socket packets leaving the node within the VPRN service) of the IP transport subservice associated with the serial port. The local host is used to terminate TCP/UDP sessions from remote hosts. The local host can select either the TCP or UDP protocol for raw socket sessions but not both concurrently.

Multiple remote hosts can be configured under the IP transport subservice associated with the serial port so that each remote host receives the serial data that is received on the serial port. Each remote host has its own remote destination IP address and port value for establishing sessions. The configured remote hosts use the TCP or UDP protocol configured for the IP transport subservice.

Note:

It is not necessary to configure remote hosts when the IP transport service is not originating sessions. If sessions are only established towards the IP transport local host (for example, remote servers polling the local host), the remote host configuration is not necessary. Remote host configurations may still be desirable when using filter-unknown-host.

IP transport processing of TCP/UDP packets is performed by the CPM task. Filters configured for protecting the CPM need to take into account the raw socket IP transport packets and ensure the filter is not blocking associated IP transport sessions. For example, operators need to ensure interface IP addresses and ports configured on the node are not blocked, and remote host IP/port combinations are not blocked.

Note:

IP transport-to-IP transport raw socket data on the same node is not supported.

9.5.1.1. Remote Host Manual TCP Connection Check

A manual TCP connection check can be performed for each remote host configured for a raw socket IP transport subservice. When executed by an operator, the TCP connection check attempts to establish a TCP session towards the configured remote host. Only one TCP connection check attempt is made, with a fixed timeout of 5 seconds. If the attempt is successful, the session is torn down immediately without data being sent.

The TCP connection check is initiated in the CLI using the tools>perform>service> ip-transport>remote-host>check-tcp command. The result is displayed in the CLI using the tools>dump>service>ip-transport>remote-host>check-tcp command. Equivalent management is available via SNMP.

If a TCP connection to a remote host already exists due to serial traffic being transmitted, the check returns “successful” without impacting the existing TCP connection.

9.5.1.2. QoS Requirements for IP Transport

Serial raw socket data that is transported using an IP transport service can be DSCP marked at the source node. This allows the source node (local host) of the traffic to mark packets correctly so that downstream nodes prioritize them as needed, and to queue local traffic in the right egress queue based on the classification assigned to the IP transport service.

The node does not support FC classification; instead, it marks the DSCP in packets based on the IP transport subservice DSCP setting. This DSCP setting overrides the DSCP marking that would have otherwise been based on the egress network queue policy FC. These packets will be queued on egress with all other control traffic and will be considered high priority.

Additionally, the DSCP setting is assigned per IP transport subservice for all traffic from the local host and all traffic destined to each remote host. There is no per remote host control for the DSCP setting.

9.5.2. GNSS NMEA Data IP Transport Service

IP transport services are used to send GNSS National Marine Electronics Association (NMEA) data to remote hosts. All IP transport functionality supported for serial data over raw sockets is also available for NMEA data. See Raw Socket IP Transport Service for information.

An IP transport subservice within a Layer 3 VPRN service can be configured to transmit GNSS NMEA data from the GNSS receiver (as the IP transport local host) to one or more remote hosts. See Figure 15. Any packets sent from remote hosts toward the local host of the IP transport subservice are dropped.

Figure 15:  GNSS NMEA Data Over IP Transport Service 

Use the syntax shown below to create an IP transport subservice within a VPRN service.

CLI Syntax:
config>service
vprn service-id [customer customer-id] [create]
ip-transport ipt-id [create]
description description-string
filter-unknown-host
local-host ip-addr ip-addr port-num port-num protocol {tcp | udp}
remote-host host-id [ip-addr ip-addr] [port-num port-num] [create]
description description-string
name host-name
exit
shutdown
tcp
inactivity-timeout seconds
max-retries number
retry-interval seconds
exit
exit
exit
exit

To enable the transport of NMEA data from the local host, configure the ipt-id as gnss. The following example is an IP transport subservice configuration output for the transport of NMEA data.

A:NOK-B>config>service>vprn# info
----------------------------------------------
        ip-transport gnss create
                description "ip-transport to send NMEA data to multiple hosts"
                filter-unknown-host
                local-host ip-addr 192.0.2.1 port-num 2000 protocol tcp
                remote-host 1 create ip-addr 128.5.5.1 port-num 32000
                exit
                remote-host 2 create ip-addr 128.4.4.2 port-num 32000
                exit
                no shutdown
            exit
            no shutdown
----------------------------------------------
A:NOK-B>config>service>vprn#

For information about configuring NMEA parameters on the GNSS receiver, refer to the 7705 SAR-Hm and SAR-Hmc Interface Configuration Guide, “GNSS Configuration”.

9.5.3. Serial Raw Socket IP Transport Configuration Commands Hierarchy

config
— service
— vprn service-id [customer customer-id] [create]
— ip-transport ipt-id [create]
— no ip-transport ipt-id
— description description-string
— no description
— dscp dscp-name
— [no] filter-unknown-host
— local-host ip-addr ip-addr port-num port-num protocol {tcp | udp}
— no local-host
— remote-host host-id [ip-addr ip-addr] [port-num port-num] [create]
— no remote-host
— description description-string
— no description
— name host-name
— no name
— [no] shutdown
— tcp
— inactivity-timeout seconds
— max-retries number
— retry-interval seconds

9.5.3.1. IP Transport Configuration Command Descriptions

ip-transport

Syntax 
ip-transport ipt-id [create]
no ip-transport ipt-id
Context 
config>service>vprn
Description 

This command creates an IP transport subservice within a VPRN service. An IP transport subservice can be used to transmit serial raw socket data to and from a local host and remote host. An IP transport subservice can also be used to transmit GNSS NMEA data from the GNSS receiver to one or more remote hosts.

All IP transport subservices must be explicitly created using the create keyword. An IP transport subservice is owned by the service within which it is created. An IP transport subservice can only be associated with a single service. The create keyword is not needed when editing parameters for an existing IP transport subservice. An IP transport subservice must first be shut down before changes can be made to the configured parameters.

The no form of this command deletes the IP transport subservice with the specified ipt-id. When an IP transport subservice is deleted, all configured parameters for the IP transport subservice are also deleted.

Default 

no ip-transport

Parameters 
ipt-id—
the physical port associated with the IP transport subservice
Values—
For serial raw sockets, the ipt-id must reference an RS-232 serial port that has been configured as a socket and be expressed in the format slot/mda/port
For a GNSS receiver, the ipt-id must be configured as gnss

 

create —
creates this IP transport subservice

description

Syntax 
description description string
no description
Context 
config>service>vprn>ip-transport
config>service>vprn>ip-transport>remote-host
Description 

This command creates a text description for a configuration context to help identify the content in the configuration file.

The no form of this command removes any description string from the context.

Default 

no description

Parameters 
description-string—
a description character string. Allowed values are any string up to 80 or 160 characters long (depending on the command, composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

dscp

Syntax 
dscp dscp-name
Context 
config>service>vprn>ip-transport
Description 

This command configures the DSCP name used to mark the DSCP field in IP transport packets originating from this node.

Default 

ef

Parameters 
dscp-name—
the DSCP name used to mark the DSCP field in IP transport packets. Table 6 lists the valid DSCP names.
Table 6:  Valid DSCP Names 

dscp-name

be, ef, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cp9, cs1, cs2, cs3, cs4, cs5, nc1, nc2, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cp11, cp13, cp15, cp17, cp19, cp21, cp23, cp25, cp27, cp29, cp31, cp33, cp35, cp37, cp39, cp41, cp42, cp43, cp44, cp45, cp47, cp49, cp50, cp51, cp52, cp53, cp54, cp55, cp57, cp58, cp59, cp60, cp61, cp62, cp63

filter-unknown-host

Syntax 
[no] filter-unknown-host
Context 
config>service>vprn>ip-transport
Description 

This command filters connections from unknown hosts. An unknown host is any host that is not configured as a remote host.

The no form of this command disables the filter.

Default 

no filter-unknown-host

local-host

Syntax 
local-host ip-addr ip-addr port-num port-num protocol {tcp | udp}
no local-host
Context 
config>service>vprn>ip-transport
Description 

This command creates the local host within the IP transport subservice.

The local host is required to accept TCP/UDP sessions initiated from far-end remote hosts, and for the node to initiate sessions towards the far-end remote hosts.

Note:

When the IP transport ID is configured as gnss, any packets sent from remote hosts to the local host are dropped.

The local host must be created before a remote host is created.

The no form of this command deletes the local host.

Default 

no local-host

Parameters 
ip-addr—
the IP address that is used for this local host. The IP address must be the same as a loopback or local interface IP address that is already configured within this service.
Values—
a.b.c.d (IPv4 address)

 

port-num—
the port number that is used by remote hosts to establish TCP/UDP sessions to this local host
Values—
1026 to 49150

 

protocol {tcp | udp} —
the protocol type that is used for all sessions to and from this local host, either tcp or udp

remote-host

Syntax 
remote-host host-id ip-addr ip-addr] port-num port-num [create]
no remote-host host-id
Context 
config>service>vprn>ip-transport
Description 

This command creates a remote host within the IP transport subservice. Multiple remote hosts can be created in order to send serial raw socket date or GNSS NMEA data to remote destinations. The create keyword must be used for each remote host that is created.

The no form of this command deletes the remote host.

Default 

no remote-host

Parameters 
host-id—
the remote host identifier
Values—
1 to 2147483647or a name string up to 64 characters

 

ip-addr—
the IP address that is used to reach the remote host in order to route IP transport packets to that remote host
Values—
a.b.c.d (IPv4 address)

 

port-num—
the destination port number that is used to reach the serial port socket or the GNSS receiver on the remote host
Values—
1 to 65535

 

create —
creates this remote host

name

Syntax 
name host-name
no name
Context 
config>service>vprn>ip-transport>remote-host
Description 

This command configures a unique name for this remote host.

The no form of this command deletes the remote host name.

Default 

n/a

Parameters 
host-name—
a unique name for this remote host, up to 64 characters long

shutdown

Syntax 
[no] shutdown
Context 
config>service>vprn>ip-transport
Description 

This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.

The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they can be deleted.

The no form of this command administratively enables an entity.

Default 

no shutdown

Special Cases 
VPRN IP transport subservice —
when an IP transport subservice within a VPRN service is shut down, all TCP/UDP packets received from remote hosts are dropped and any serial data received from the serial port is dropped. Any TCP connections that were up are closed and no new TCP connection requests are accepted.

It is not possible to make configuration changes to an IP transport subservice without performing a shutdown first.

The operational state of an IP transport subservice is relative to the operational state of the serial port or GNSS receiver for which the IP transport subservice is defined. When a serial port or GNSS receiver is shut down, the IP transport subservice associated with the serial port or GNSS receiver becomes operationally down.

When the no shutdown command is executed for an IP transport subservice, it becomes operationally up. Serial data from the serial port or NMEA sentence data from the GNSS receiver is encapsulated in TCP/UDP packets destined for remote hosts, and TCP/UDP packets can be received by the local host, where raw serial data is then sent out the serial port.

tcp

Syntax 
tcp
Context 
config>service>vprn>ip-transport
Description 

This command creates the context to configure TCP parameters within this IP transport subservice.

Default 

n/a

inactivity-timeout

Syntax 
inactivity-timeout seconds
Context 
config>service>vprn>ip-transport>tcp
Description 

This command specifies how long to wait before disconnecting a TCP connection due to traffic inactivity over the connection.

Default 

30 s

Parameters 
seconds—
how long to wait, in seconds, before disconnecting a TCP connection
Values—
1 to 65535

 

max-retries

Syntax 
max-retries number
Context 
config>service>vprn>ip-transport>tcp
Description 

This command specifies the number of times that a remote host, acting as a client, tries to establish a TCP connection after the initial attempt fails.

Default 

5

Parameters 
number—
the number of attempts to establish a TCP connection after the initial attempt fails
Values—
0 to 10

 

retry-interval

Syntax 
retry-interval seconds
Context 
config>service>vprn>ip-transport>tcp
Description 

This command specifies how long to wait before each TCP max-retries attempt.

Default 

5 s

Parameters 
seconds—
how long to wait, in seconds, before each TCP max-retries attempt
Values—
1 to 300

 

9.5.4. IP Transport Show Commands Hierarchy

show
— service
— id service-id
— ip-transport [ip-transport ipt-id]
— remote-host host-id [detail | statistics]
— ip-transport-using [ip-transport ipt-id]

9.5.4.1. IP Transport Show Commands Descriptions

id

Syntax 
id service-id
Context 
show>service
Description 

This command displays information for a particular service ID

Parameters 
service-id—
identifies the service in the domain by service number or name

ip-transport

Syntax 
ip-transport ipt-id [detail | statistics]
Context 
show>service>id
Description 

This command displays information for a specified IP transport subservice within this service. If no IP transport subservice is specified, summary information is displayed for all IP transport subservices associated with the service.

Parameters 
ipt-id—
the physical port associated with the IP transport subservice
Values—
For serial raw sockets, the ipt-id must reference an RS-232 serial port that has been configured as a socket and must be expressed in the format slot/mda/port
For a GNSS receiver, the ipt-id must be configured as gnss

 

create —
creates this IP transport subservice
detail—
displays detailed information for the specified IP transport subservice
statistics—
displays statistical information for the specified IP transport subservice
Output 

The following output is an example of IP transport subservice summary and detailed information for a specified service.

Output Example
*A:Dut# show service id 100 ip-transport
=============================================================================
IP Transport (Summary), Service 100
=============================================================================
IptId     LocalIP         LocalPort Proto RemHost DSCP FltrUnkn Adm  Opr
-----------------------------------------------------------------------------
1/3/1     192.168.1.1     1026      udp   1       ef   enabled  Up   Down
-----------------------------------------------------------------------------
Entries found: 1
=============================================================================
*A:Dut#
*A:Dut# show service id 100 ip-transport 1/3/1 detail
===============================================================================
IP Transport
===============================================================================
Service Id         : 100 (VPRN)
IP Transport Id    : 1/2/4
Description        : (Not Specified)
Admin State        : Up                        Oper State          : Down
Oper Flags         : svcAdminDown portOperDown noIfAddress
Local IP Address   : 192.168.1.1               Local Port Number   : 1026
Local IP Protocol  : udp
DSCP               : ef                        Filter Unknown Host : enabled
TCP Inact Timeout  : 30
TCP Max Retries    : 5
TCP Retry Interval : 5
Num Remote Hosts   : 1
Last Mgmt Change   : 06/02/2017 11:15:50
Last Oper Change   : 06/02/2017 11:02:52
-------------------------------------------------------------------------------
IP Transport Accumulated Statistics
-------------------------------------------------------------------------------
Known Remote Hosts
  Packets sent                           : 0
  Characters sent                        : 0
  Packets received                       : 0
  Characters received                    : 0
  Connections                            : N/A
    To                                   : N/A
    From                                 : N/A
  Connection retries                     : N/A
  Connection failures                    : N/A
  Currently connected                    : N/A
Unknown Remote Hosts
  Packets sent                           : 0
  Characters sent                        : 0
  Packets received                       : 0
  Characters received                    : 0
  Successful connections from            : N/A
  Rejected due to unknown host filter    : 0
  Rejected due to out of resources       : 0
  Inactivity timeouts                    : N/A
  Last RemIp:RemPort                     : 0.0.0.0:0
  Currently connected                    : N/A
Dropped packets due to no remote hosts   : 0
===============================================================================

remote-host

Syntax 
remote-host host-id [detail | statistics]
Context 
show>service>id>ip-transport
Description 

This command displays information for a specified remote host within this IP transport subservice within this service. If no remote host is specified, summary information is displayed for all remote hosts within this IP transport subservice.

Parameters 
host-id—
the remote host identifier
Values—
1 to 2147483647or a name string up to 64 characters long

 

detail—
displays detailed information for a specified remote host
statistics—
displays summary information for a specified remote host
Output 

The following output is an example of IP transport subservice remote host summary and detailed information.

Output Example
*A:Dut# show service id 100 ip-transport remote-host
=============================================================================
IPT Remote Host (Summary), Service 100 IPT 1/3/1
=============================================================================
RemId      RemIp:RemPort         Rcvd Chars Sent Chars Drop Chars State
                                 Rcvd Pkts  Sent Pkts  Drop Pkts  Up Time
-----------------------------------------------------------------------------
2          192.168.1.1:1027      0          0          0          N/A
                                 0          0          0          N/A
-----------------------------------------------------------------------------
Number of known remote hosts: 1
Number of unknown remote hosts: N/A
Total entries found: 1
=============================================================================
*A:Dut#
Output Example
*A:Dut#  show service id 100 ip-transport 1/3/1 remote-host 2 detail
===============================================================================
IPT Remote Host
===============================================================================
Service Id         : 100 (IES)
IP Transport Id    : 1/3/1
Remote Host Id     : 2
Name               : (Not Specified)
Description        : (Not Specified)
IP Address         : 192.168.1.6               Port Number         : 4000
Last Mgmt Change   : 12/07/2016 16:48:44
Session State      : connected                 Up Time             : 00h01m44s
Last Connect       : successful
-------------------------------------------------------------------------------
IPT Remote Host Statistics
-------------------------------------------------------------------------------
Sent Pkts       : 134                   Sent Chars      : 201000
Dropped Pkts    : 0                     Dropped Chars   : 0
Rcvd Pkts       : 267                   Rcvd Chars      : 201000
Session information
  Connections                            : 2
    To                                   : 1
    From                                 : 1
  Connection retries                     : 0
  Connection failures                    : 0
  Closed by far end                      : 1
  Inactivity timeouts                    : 0
===============================================================================
*A:Dut#

ip-transport-using

Syntax 
ip-transport-using [ip-transport ipt-id]
Context 
show>service
Description 

This command displays IP transport subservice information for a specified port. If no port is specified, the command displays a summary of all IP transport subservices defined for this service.

Parameters 
ipt-id—
the physical port associated with the IP transport subservice
Values—
For serial raw sockets, the ipt-id must reference an RS-232 serial port that has been configured as a socket and must be expressed in the format slot/mda/port
For a GNSS receiver, the ipt-id must be configured as gnss

 

Output 

The following output is an example of ip-transport-using information.

Output Example
*A:Dut# show service ip-transport-using
=========================================
IP Transports
=========================================
IptId     SvcId      Type      Adm  Opr
-----------------------------------------
1/3/1     1          VPRN      Down Down
1/3/2     2          VPRN      Up   Down
-----------------------------------------
Entries found: 2
=========================================
*A:Dut#

9.5.5. IP Transport Clear Commands Hierarchy

clear
— service
— id service-id
— ip-transport ipt-id
— remote-host host-id
— statistics
— statistics

9.5.5.1. IP Transport Clear Commands Descriptions

id

Syntax 
id service-id
Context 
clear>service
Description 

This command clears commands for a specific service.

Parameters 
service-id—
uniquely identifies a service by service number or name

ip-transport

Syntax 
ip-transport ipt-id
Context 
clear>service>id
Description 

This command clears IP transport statistics for this service.

Parameters 
ipt-id—
the physical port associated with the IP transport subservice
Values—
For serial raw sockets, the ipt-id must reference an RS-232 serial port that has been configured as a socket and must be expressed in the format slot/mda/port
For a GNSS receiver, the ipt-id must be configured as gnss

 

remote-host

Syntax 
remote-host host-id
Context 
clear>service>id>ip-transport
Description 

This command clears statistics pertaining to a specified remote host assigned to this IP transport subservice.

Parameters 
host-id—
the remote host identifier
Values—
1 to 2147483647or a name string up to 64 characters long

 

statistics

Syntax 
statistics
Context 
clear>service>id>ip-transport
clear>service>id>ip-transport>remote-host
Description 

This command clears statistics-related information pertaining to all configured IP transport subservices or to all configured remote hosts for a specified IP transport subservice.