05-Layer 3—IP Services Command Reference

HomeSupportSwitchesS7500X-G SeriesReference GuidesCommand ReferencesH3C S7500X-G Switch Series Command References-R7761Pxx-6W10005-Layer 3—IP Services Command Reference
18-WS-Discovery gateway commands
Title Size Download
18-WS-Discovery gateway commands 164.71 KB

WS-Discovery gateway commands

display ws-discovery gateway

Use display ws-discovery gateway to display Web Services Dynamic Discovery (WS-Discovery) gateway configuration.

Syntax

display ws-discovery gateway

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# Display WS-Discovery gateway configuration.

<Sysname> display ws-discovery gateway

WS-Discovery gateway configuration:

 Status: Enabled

Service types supported by WS-Discovery:

 Printer

WS-Discovery gateway session timeout: 120s(default)

Source IP:

 VLAN 10:  Vlan-interface30 (192.168.1.1)

 VLAN 20:  Vlan-interface40 (192.168.2.100)

Probe interval:

 VLAN 30:  600s.

Table 1 Command output

Field

Description

WS-Discovery gateway configuration

Configuration for the WS-Discovery gateway.

Status

WS-Discovery gateway status.

·     Enabled.

·     Disabled.

Service types supported by WS-Discovery

Type of services that the WS-Discovery gateway can learn.

·     Printer: Printing service.

·     --: No services type that the WS-Discovery gateway can learn is configured.

WS-Discovery gateway session timeout

Aging timer for the WS-Discovery gateway service entry, in seconds. When the aging timer for the service entry uses the default setting, this field displays 120s(default).

Source IP

Source IP address of WS-Discovery packets for each VLAN.

·     If the primary IP address of the VLAN interface is used as the source IP address, this field displays the interface name and IP address in the format of Interface-typeInterface-number (x.x.x.x), for example, Vlan-interface30 (192.168.1.1).

·     If the primary IP address of the VLAN interface is used as the source IP address but no IP address is configured for the interface, this field displays the interface name in the format of Interface-typeInterface-number (--), for example, Vlan-interface30 (--).

Probe interval

VLANs enabled with WS-Discovery gateway periodic probing and the probe intervals. This field displays two hyphens (--) if no VLAN is enabled with WS-Discovery gateway periodic probing.

 

display ws-discovery gateway policy

Use display ws-discovery gateway policy to display WS-Discovery gateway policy information, including the policy name, user VLANs, and service VLANs.

Syntax

display ws-discovery gateway policy [ policy-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

policy-name: Specifies a policy name, a case-sensitive string of 1 to 31 characters. If you do not specify a policy name, the command displays information about all WS-Discovery gateway policies.

Examples

# Display information about all WS-Discovery gateway policies.

<Sysname> display ws-discovery gateway policy

Total WS-Discovery gateway policies: 3

 

WS-Discovery policy name: p1

 User VLANs : 10

 Service VLANs : 30

 

WS-Discovery policy name: p2

 User VLANs : 20

 Service VLANs : 40

 

WS-Discovery policy name: p3

 User VLANs : 4 Second-VLANs : 15

 Service VLANs : 5 Second-VLANs : 30

Table 2 Command output

Field

Description

Total WS-discovery gateway policies

Total number of WS-discovery gateway policies.

Policy name

Name of the policy.

User VLANs : xx Second-VLANs : yy

User VLANs indicates user VLANs and xx indicates IDs of the user VLANs. This field displays two hyphens (--) if no user VLAN is specified. In QinQ scenarios, User VLANs indicates outer user VLANs.

Second-VLANs indicates inner user VLANs and yy indicates IDs of the inner user VLANs in QinQ scenarios.

Service VLANs : xx Second-VLANs : yy

Service VLANs indicates service VLANs and xx indicates IDs of the service VLANs. This field displays two hyphens (--) if no service VLAN is specified. In QinQ scenarios, Service VLANs indicates outer service VLANs.

Second-VLANs indicates inner service VLANs and yy indicates IDs of the inner service VLANs in QinQ scenarios.

 

Related commands

service vlan

user vlan

ws-discovery gateway policy

display ws-discovery gateway service

Use display ws-discovery gateway service to display information about services learned by the WS-discovery gateway.

Syntax

In standalone mode:

display ws-discovery gateway service printer [ vlan vlan-id ] [ slot slot-number ] [ verbose ]

display ws-discovery gateway service vlan vlan-id ip ip-address [ slot slot-number ][ verbose ]

In IRF mode:

display ws-discovery gateway service printer [ vlan vlan-id ] [ chassis chassis-number slot slot-number ] [ verbose ]

display ws-discovery gateway service vlan vlan-id ip ip-address [ chassis chassis-number slot slot-number ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

printer: Specifies the printing service.

vlan vlan-id: Specifies a VLAN by its ID in the range of 1 to 4094.

ip ip-address: Specifies an IP address.

verbose: Displays detailed service information. If you do not specify this keyword, this command displays brief service information.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays service information for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays service information for the global active MPU. (In IRF mode.)

Examples

# Display brief information about the printing service learned by the WS-Discovery gateway.

<Sysname> display ws-discovery gateway service printer

UUID: 298423a6-9188-4ab1-83bb-1cbfc0f3f0c4

Xaddrs: https://192.168.199.254:3702/298423a6-9188-4ab1-83bb-1cbfc0f3f0c4

Service type: printer

VLAN: 1

IP: 192.168.199.254

# Display detailed information about the printing service learned by the WS-Discovery gateway.

<Sysname> display ws-discovery gateway service printer verbose

UUID: 298423a6-9188-4ab1-83bb-1cbfc0f3f0c4

Xaddrs: https://192.168.10.2:3702/298423a6-9188-4ab1-83bb-1cbfc0f3f0c4

Service type: printer

VLAN: 1

IP: 192.168.10.2

Scope: ”ldap:///ou=engineering,o=exampleorg,c=us”,

       ”ldap:///ou=floor1,ou=b42,ou=anytown,o=exampleorg,c=us”

InstanceID: 70

MessageNum: 1

MetadataVersion: 75965

Table 3 Command output

Field

Description

UUID

Universal Unique Identifier (UUID).

Xaddrs

URL address used by the Web service server to provide the service.

Service type

Web service type. Only Printer is supported in the current software version.

VLAN

Service VLAN to which the Web service belongs.

IP

IP address used by the Web service server.

Namespace

XML namespace.

Scope

Collections of URI ranges for the Web service client, specified by the Web service server. If the Web service client is not in the specified ranges, the Web service server or WS-Discovery gateway does not respond to the client's requests.

InstanceID

Instance ID. The receiver distinguishes the order of WS-Discovery packets based on the instance ID and packet number.

MessageNum

Number of the packet. The receiver distinguishes the order of WS-Discovery packets based on the instance ID and packet number.

MetadataVersion

Version number of metadata, used by the Web service server to control metadata cache.

 

Related commands

reset ws-discovery gateway service

display ws-discovery gateway statistics

Use display ws-discovery gateway statistics to display WS-Discovery gateway packet statistics.

Syntax

display ws-discovery gateway statistics

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Usage guidelines

Use this command to display statistics about WS-Discovery packets received and sent by the WS-Discovery gateway. WS-Discovery packets have the following types:

·     Hello—A packet sent by a Web service server when it joins the network.

·     Bye—A packet sent by a Web service server when it leaves the network.

·     Probe—A packet sent by a client to detect Web service servers.

·     ProbeMatch—A packet sent by a Web service server after it receives a Probe packet and matches the requested service in the Probe packet. The ProbeMatch packet contains information required for communication with the Web service server.

·     Resolve—A packet sent by a client when the client receives a ProbeMatch packet that contains only the UUID of the Web service server. The destination IP address of the Resolve packet is the WS-Discovery multicast address. The Resolve packet carries the UUID of the Web service server.

·     ResolveMatch—A packet sent by a Web service server when it receives a Resolve packet and matches the UUID and requested service in the Resolve packet. The ResolveMatch packet contains information required for communication with the Web service server.

Examples

# Display WS-Discovery gateway packet statistics.

<Sysname> display ws-discovery gateway statistics

WS-Discovery gateway packet statistics:

  Total received  : 601

    Hello received: 0                   Probe received: 0

    ProbeMatch received: 3              Resolve received: 0

    ResolveMatch received: 598          Bye received: 0

  Total send  : 2409

    Hello send: 1800                    Probe send: 5

    ProbeMatch send: 0                  Resolve send: 598

    ResolveMatch send: 0                Bye send: 6

Total WS-Discovery gateway statistics: 3010

Table 4 Command output

Field

Description

WS-Discovery gateway packet statistics

Statistics about WS-Discovery packets received and sent by the WS-Discovery gateway.

Total received

Total number of packets received by the WS-Discovery gateway.

Hello received

Total number of Hello packets received by the WS-Discovery gateway.

Probe received

Total number of Probe packets received by the WS-Discovery gateway.

ProbeMatch received

Total number of ProbeMatch packets received by the WS-Discovery gateway.

Resolve received

Total number of Resolve packets received by the WS-Discovery gateway.

ResolveMatch received

Total number of ResolveMatch packets received by the WS-Discovery gateway.

Bye received

Total number of Bye packets received by the WS-Discovery gateway.

Total send

Total number of packets sent by the WS-Discovery gateway.

Hello send

Total number of Hello packets sent by the WS-Discovery gateway.

Probe send

Total number of Probe packets sent by the WS-Discovery gateway.

ProbeMatch send

Total number of ProbeMatch packets sent by the WS-Discovery gateway.

Resolve send

Total number of Resolve packets sent by the WS-Discovery gateway.

ResolveMatch send

Total number of ResolveMatch packets sent by the WS-Discovery gateway.

Bye send

Total number of Bye packets sent by the WS-Discovery gateway.

Total WS-discovery gateway statistics

Total number of packets received and sent by the WS-Discovery gateway.

 

Related commands

reset ws-discovery gateway statistics

reset ws-discovery gateway service

Use reset ws-discovery gateway service to clear information about services learned by the WS-Discovery gateway.

Syntax

reset ws-discovery gateway service printer [ vlan vlan-id ]

reset ws-discovery gateway service vlan vlan-id ip ip-address

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

printer: Specifies the printing service.

vlan vlan-id: Specifies a VLAN by its ID in the range of 1 to 4094. If you do not specify a VLAN, this command clears information about services learned by the WS-Discovery gateway for all VLANs.

ip ip-address: Specifies an IP address. If you do not specify an IP address, this command clears information about services learned by the WS-Discovery gateway for all IP addresses.

Examples

# Clear information about services learned by the WS-Discovery gateway in VLAN 10.

<Sysname> reset ws-discovery gateway service printer vlan 10

Related commands

display ws-discovery gateway service

reset ws-discovery gateway statistics

Use reset ws-discovery gateway statistics to clear packet statistics on the WS-Discovery gateway.

Syntax

reset ws-discovery gateway statistics

Views

User view

Predefined user roles

network-admin

mdc-admin

Examples

# Clear packet statistics on the WS-Discovery gateway.

<Sysname> reset ws-discovery gateway statistics

Related commands

display ws-discovery gateway statistics

service vlan

Use service vlan to specify service VLANs in a WS-Discovery gateway policy.

Use undo service vlan to remove service VLANs in a WS-Discovery gateway policy.

Syntax

service vlan vlan-id-list [ second-vlan vlan-id-list ]

undo service vlan [ vlan-id-list [ second-vlan vlan-id-list ] ]

Default

No service VLAN is specified in a WS-Discovery gateway policy.

Views

WS-Discovery gateway policy view

Predefined user roles

network-admin

mdc-admin

Parameters

vlan vlan-id-list: Specifies a space-separated list of up to 10 VLAN items. Each VLAN item specifies a VLAN by VLAN ID or specifies a range of VLANs in the form of vlan-id1 to vlan-id2. The value range for the VLAN IDs is 1 to 4094. If you specify a VLAN range, the value for the vlan-id2 argument must be greater than the value for the vlan-id1 argument. In QinQ scenarios, this option specifies a space-separated list of up to 10 outer VLAN items.

second-vlan vlan-id-list: Specifies a space-separated list of up to 10 inner VLAN items. Each inner VLAN item specifies an inner VLAN by VLAN ID or specifies a range of inner VLANs in the form of vlan-id1 to vlan-id2. The value range for the VLAN IDs is 1 to 4094. If you specify a VLAN range, the value for the vlan-id2 argument must be greater than the value for the vlan-id1 argument. You must specify this option in QinQ scenarios.

Usage guidelines

Application scenarios

A WS-Discovery gateway policy controls user access to services by using service VLANs. Users in the user VLANs defined in the gateway policy can only access services in the service VLANs.

On a QinQ network, packets sent from both the client and server to the WS-Discovery gateway carry two layers of VLAN tags. The inner VLAN tag (also called CVLAN tag) identifies the VLAN to which the frame belongs when it is transmitted in the customer network. The outer VLAN tag (also called SVLAN tag) identifies the VLAN to which the QinQ frame belongs when it is transmitted in the service provider network. When you specify service VLANs and users VLANs for a WS-Discovery gateway policy, you must specify inner VLANs. If you do not specify inner VLANs, the WS-Discovery gateway does provide service discovery.

Restrictions and guidelines

You can specify the same service VLAN in multiple WS-Discovery gateway policies and specify multiple service VLANs in the same WS-Discovery gateway policy.

When you specify service VLANs and user VLANs for a WS-Discovery gateway policy on a QinQ network, you must specify both the outer VLANs and inner VLANs. A client can access services in the service VLANs only when both the two layers of VLAN tags of the packets sent by the client match the WS-Discovery gateway policy.

Examples

# Specify service VLANs 100 through 200 in WS-Discovery gateway policy test.

<Sysname> system-view

[Sysname] ws-discovery gateway policy test

[Sysname-ws-discovery-gateway-policy-test] service vlan 100 to 200

# Specify outer service VLAN 10 and inner service VLANs 100 through 105 in WS-Discovery gateway policy p1

<Sysname> system-view

[Sysname] ws-discovery gateway policy p1

[Sysname-ws-discovery-gateway-policy-p1] service vlan 10 second-vlan 100 to 105

Related commands

display ws-discovery gateway policy

user vlan

user vlan

Use user vlan to specify user VLANs in a WS-Discovery gateway policy.

Use undo user vlan to remove user VLANs in a WS-Discovery gateway policy.

Syntax

user vlan vlan-id-list [ second-vlan vlan-id-list ]

undo user vlan [ vlan-id-list ] [ second-vlan vlan-id-list ]

Default

No user VLAN is specified in a WS-Discovery gateway policy.

Views

WS-Discovery gateway policy view

Predefined user roles

network-admin

mdc-admin

Parameters

vlan-id-list: Specifies a space-separated list of up to 10 VLAN items. Each VLAN item specifies a VLAN by VLAN ID or specifies a range of VLANs in the form of vlan-id1 to vlan-id2. The value range for the VLAN IDs is 1 to 4094. If you specify a VLAN range, the value for the vlan-id2 argument must be greater than the value for the vlan-id1 argument. In QinQ scenarios, this argument specifies a space-separated list of up to 10 outer VLAN items.

second-vlan vlan-id-list: Specifies a space-separated list of up to 10 inner VLAN items. Each inner VLAN item specifies an inner VLAN by VLAN ID or specifies a range of inner VLANs in the form of vlan-id1 to vlan-id2. The value range for the VLAN IDs is 1 to 4094. If you specify a VLAN range, the value for the vlan-id2 argument must be greater than the value for the vlan-id1 argument. You must specify this option in QinQ scenarios.

Usage guidelines

Application scenarios

A WS-Discovery gateway policy controls user access to services by using user VLANs. Only service queries from users in the user VLANs defined in the gateway policy are processed by the WS-Discovery gateway.

On a QinQ network, packets sent from both the client and server to the WS-Discovery gateway carry two layers of VLAN tags. The CVLAN tag identifies the VLAN to which the frame belongs when it is transmitted in the customer network. The SVLAN tag identifies the VLAN to which the QinQ frame belongs when it is transmitted in the service provider network. When you specify service VLANs and users VLANs for a WS-Discovery gateway policy, you must specify inner VLANs. If you do not specify inner VLANs, the WS-Discovery gateway does provide service discovery.

Restrictions and guidelines

You cannot specify the same user VLAN in multiple WS-Discovery gateway policies, but you can specify multiple user VLANs in the same WS-Discovery gateway policy.

When you specify service VLANs and user VLANs for a WS-Discovery gateway policy on a QinQ network, you must specify both the outer VLANs and inner VLANs. A client can access services in the service VLANs only when both the two layers of VLAN tags of the packets sent by the client match the WS-Discovery gateway policy.

Examples

# Specify user VLANs 100 through 200 in WS-Discovery gateway policy test.

<Sysname> system-view

[Sysname] ws-discovery gateway policy test

[Sysname-ws-discovery-gateway-policy-test] user vlan 100 to 200

# Specify outer user VLAN 20 and inner user VLANs 106 to 120 in WS-Discovery gateway policy p1.

<Sysname> system-view

[Sysname] ws-discovery gateway policy p1

[Sysname-ws-discovery-gateway-policy-p1] user vlan 20 second-vlan 106 to 120

Related commands

display ws-discovery gateway policy

service vlan

ws-discovery gateway enable

Use ws-discovery gateway enable to enable the WS-Discovery gateway.

Use undo ws-discovery gateway enable to disable the WS-Discovery gateway.

Syntax

ws-discovery gateway enable

undo ws-discovery gateway enable

Default

The WS-Discovery gateway is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

Application scenarios

WS-Discovery is a UDP-based communication protocol that uses destination port 3702. WS-Discovery can automatically discover Web services on the network. Web services include clients and servers. Clients discover Web services within a Layer 2 broadcast domain by sending protocol packets in which the destination IP address is multicast address 239.255.255.250 and the destination port number is 3702. Clients can only discover Web services that reside on the same VLAN and cannot find Web services on other VLANs.

After you enable the WS-Discovery gateway on a device connecting to clients and servers in different VLANs, the WS-Discovery gateway can provide across-VLAN Web service discovery.

The WS-Discovery gateway provides the following functionalities:

·     Replying to service queries in a non-QinQ scenario.

·     Discovering Web services in a non-QinQ scenario.

·     Discovering Web services in a QinQ scenario.

Operating mechanism (in a non-QinQ scenario)

In a non-QinQ scenario, the WS-Discovery gateway can record information about the services provided by the Web service servers. It also helps Web service clients discover Web service servers on other VLANs. The WS-Discovery gateway works as follows:

1.     Upon receiving a Hello packet from a Web service server, the WS-Discovery gateway creates a service entry for the Web service server when the following requirements are met:

¡     The Hello packet contains the Web service server IP address.

¡     The service type and service VLAN in the Hello packet match the gateway policy.

If the Hello packet does not contain the Web service server IP address, the WS-Discovery gateway sends a Resolve packet. Upon receiving a ResolveMatch packet, the WS-Discovery gateway creates a service entry for the Web service server if the service type and service VLAN in the packet match the gateway policy.

After it creates a service entry, the WS-Discovery gateway broadcasts the service information to each user VLAN defined in the gateway policy.

2.     After the WS-Discovery gateway receives a Probe packet from a Web service client, it looks up the local service list for a match. If a match is found, it replies with a unicast packet to the client. If no match is found, the WS-Discovery gateway broadcasts the Probe packet to each service VLAN defined in the gateway policy to help the client search for the service. After receiving a ProbeMatch packet, the WS-Discovery gateway records the service information if the service type and service VLAN in the packet match the gateway policy. When the WS-Discovery gateway receives another Probe packet from the Web service client, it directly replies to the client after looking up the local service list.

Operating mechanism (in a QinQ scenario)

In a QinQ scenario, packets sent from both the client and server to the WS-Discovery gateway carry two layers of VLAN tags. The CVLAN tag identifies the VLAN to which the frame belongs when it is transmitted in the customer network. The SVLAN tag identifies the VLAN to which the QinQ frame belongs when it is transmitted in the service provider network. To provide Web service discovery, the WS-Discovery gateway must identify both layers of VLAN tags.

The Web service client discovers a Web service server as follows:

1.     Specify both outer and inner VLANs based on the actual network when you specify service VLANs and user VLANs for a WS-Discovery gateway policy.

2.     Upon receiving a Probe packet from a Web service client, the WS-Discovery gateway forwards it to the corresponding Web service server based on the mapping between the user and service VLANs in the WS-Discovery gateway policy.

If the outer and inner VLAN tags carried by the packet do not match the outer and inner user VLANs in the WS-Discovery gateway policy, the WS-Discovery gateway discards the Probe packet. It does not perform the following procedure.

3.     Upon receiving the Probe packet from the WS-Discovery gateway, the Web service server replies with a ProbeMatch packet.

4.     Upon receiving the ProbeMatch packet that carries two layers of VLAN tags, the WS-Discovery gateway forwards it to the BRAS gateway. The BRAS gateway performs QinQ termination on a Layer 3 subinterface.

5.     The BRAS gateway looks up for a route based on the IP address carried in the ProbeMatch packet and forwards the packet to the Web service client.

Then, the Web service client obtains the transmission address used for communication with the Web service server as follows:

1.     The WS-Discovery gateway receives a Resolve packet from the Web service client.

2.     The WS-Discovery gateway forwards the Resolve packet to the corresponding Web service server based on the mapping between the user and service VLANs in the WS-Discovery gateway policy.

3.     Upon receiving the Resolve packet from the WS-Discovery gateway, the Web service server replies with a ResolveMatch packet.

4.     Upon receiving the ResolveMatch packet that carries two layers of VLAN tags, the WS-Discovery gateway forwards it to the BRAS gateway. The BRAS gateway performs QinQ termination on a Layer 3 subinterface.

5.     The BRAS gateway looks up for a route based on the IP address carried in the ResolveMatch packet and forwards the packet to the Web service client.

6.     Then, the Web service client can use the services provided by the Web service server.

Examples

# Enable the WS-Discovery gateway.

<Sysname> system-view

[Sysname] ws-discovery gateway enable

Related commands

display ws-discovery gateway

ws-discovery gateway permit service-type

Use ws-discovery gateway permit service-type to specify a permitted Web service type for entry learning.

Use undo ws-discovery gateway permit service-type to remove a permitted Web service type for entry learning

Syntax

ws-discovery gateway permit service-type printer

undo ws-discovery gateway permit service-type printer

Default

The WS-Discovery gateway cannot learn any Web service.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

printer: Specifies the printing Web service.

Usage guidelines

Application scenarios

When a Web service server joins a LAN, it sends a WS-Discovery packet within the Layer 2 broadcast domain to advertise its UUID, service type, and communication address. The destination address in the packet is multicast IP address 239.255.255.250. After receiving the packet, the WS-Discovery gateway immediately creates an entry to record the VLAN and service information for the interface that receives the packet. At the same time, the WS-Discovery gateway sets an aging timer for the entry, which is 120 seconds by default. Then, the WS-Discovery gateway replies to WS-Discovery queries and discovers Web services based on the service entry.

Recommended configuration

Recording service entries occupies the memory space of the device. You can adjust the permitted Web service types for the WS-Discovery gateway as required.

Restrictions and guidelines

To have this feature take effect, you must first enable the WS-Discovery gateway by using the ws-discovery gateway enable command.

Examples

# Permit the WS-Discovery gateway to learn the printing service.

<Sysname> system-view

[Sysname] ws-discovery gateway permit service-type printer

Related commands

display ws-discovery gateway service

ws-discovery gateway enable

ws-discovery gateway policy

Use ws-discovery gateway policy to create a WS-Discovery gateway policy and enter its view or enter the view of an existing WS-Discovery gateway policy.

Use undo ws-discovery gateway policy to delete a WS-Discovery gateway policy.

Syntax

ws-discovery gateway policy policy-name

undo ws-discovery gateway policy policy-name

Default

No WS-Discovery gateway policy exists.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

policy-name: Specifies a policy name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

Application scenarios

Use gateway policies to control access of Web service clients to the WS-Discovery gateway and the services in VLANs that can be accessed by the Web service clients. This allows for flexible control over the usage scope of Web services. You can define the following items when you create a WS-Discovery gateway policy:

·     User VLANs—Control access to the WS-Discovery gateway. Only service queries from users in the user VLANs defined in the gateway policy are processed by the WS-Discovery gateway.

·     Service VLANs—Control access to Web services. Users in the user VLANs defined in the gateway policy can only access Web services in the service VLANs.

You can create multiple WS-Discovery gateway policies by repeating this command.

Restrictions and guidelines

To have this feature take effect, you must first enable the WS-Discovery gateway by using the ws-discovery gateway enable command.

Examples

# Create a WS-Discovery gateway policy named test.

<Sysname> system-view

[Sysname] ws-discovery gateway policy test

[Sysname-ws-discovery-gateway-policy-test]

Related commands

display ws-discovery gateway policy

ws-discovery gateway enable

ws-discovery gateway probe interval

Use ws-discovery gateway probe interval to enable periodic probing on the WS-Discovery gateway and set the probe interval.

Use undo ws-discovery gateway probe interval to disable periodic probing on the WS-Discovery gateway.

Syntax

ws-discovery gateway probe interval interval

undo ws-discovery gateway probe interval

Default

Periodic probing is disabled on the WS-Discovery gateway.

Views

VLAN view

Predefined user roles

network-admin

mdc-admin

Parameters

interval: Specifies a probe interval in seconds. The value range is 60 to 38400.

Usage guidelines

Application scenarios

The WS-Discovery gateway can receive service information advertised only by Web service servers that join the network after it joins the network. It cannot obtain information about services advertised before it joins the network. With this feature, the WS-Discovery gateway proactively probes Web service servers on the network at the specified intervals, and updates the service list on the gateway based on the received responses.

Recommended configuration

Enabling this feature increases the number of multicast packets in VLANs. As a best practice to reduce the number of multicast packets on the network, do not set the probe interval to a small value.

Restrictions and guidelines

·     To have this feature takes effect, you must first enable the WS-Discovery gateway by using the ws-discovery gateway enable command.

·     If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Enable periodic probing and set the probe interval to 240 seconds in VLAN 10.

<Sysname> system-view

[Sysname] vlan 10

[Sysname-vlan10] ws-discovery gateway probe interval 240

Related commands

display ws-discovery gateway

ws-discovery gateway enable

ws-discovery gateway session timeout

Use ws-discovery gateway session timeout to set the aging timer for service entries on the WS-Discovery gateway.

Use undo ws-discovery gateway session timeout to restore the default.

Syntax

ws-discovery gateway session timeout time

undo ws-discovery gateway session timeout

Default

The aging timer for service entries on the WS-Discovery gateway is 120 seconds.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

time: Specifies the aging timer in seconds. The value range for this argument is 60 to 3600.

Usage guidelines

Application scenarios

The WS-Discovery gateway sets a global aging timer for all service entries. When the aging timer expires, the WS-Discovery gateway deletes the service entries. This reduces memory consumption of invalid service entries.

Restrictions and guidelines

To have this feature take effect, you must first enable the WS-Discovery gateway by using the ws-discovery gateway enable command.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the aging timer for service entries on the WS-Discovery gateway to 150 seconds.

<Sysname> system-view

[Sysname] ws-discovery gateway session timeout 150

Related commands

display ws-discovery gateway

ws-discovery gateway enable

ws-discovery gateway source-ip

Use ws-discovery gateway source-ip to specify the source address for WS-Discovery packets.

Use undo ws-discovery gateway source-ip to restore the default.

Syntax

ws-discovery gateway source-ip interface interface-type interface-number

undo ws-discovery gateway source-ip

Default

The WS-Discovery gateway uses the primary IP address of the VLAN interface connected to the destination VLAN as the source IP address of WS-Discovery packets.

Views

VLAN view

Predefined user roles

network-admin

mdc-admin

Parameters

interface interface-type interface-number: Specifies an interface whose primary IP address will be used as the source address. The interface-type argument represents the interface type and the interface-number argument represents the interface number.

Usage guidelines

Application scenarios

When the WS-Discovery gateway sends Probe packets or Resolve packets to a specific VLAN or responds to Probe requests, the source IP address of the packets is the primary IP address of the VLAN interface connected to the destination VLAN. If the WS-Discovery gateway connects to a large number of VLANs, specifying an IP address for each VLAN interface greatly wastes IP address resources. To avoid such an issue, use this command to specify the source address for WS-Discovery packets.

Operating mechanism

This feature enables the WS-Discovery gateway to first change the source IP address of the packet to the primary IP address of the specified interface before it sends the packet to a specific VLAN. If the primary IP address of the specified interface is deleted, the WS-Discovery gateway uses the primary IP address of the output interface as the source IP address of WS-Discovery packets. If the output interface is not configured with a primary IP address, the WS-Discovery gateway cannot send packets.

Restrictions and guidelines

·     The specified interface must have a primary IP address. If the specified interface does not have a primary IP address, the configuration will fail.

·     To have this feature take effect, you must first enable the WS-Discovery gateway by using the ws-discovery gateway enable command.

·     You can specify only one source address for WS-Discovery packets in each VLAN. If you execute this command multiple times, the most recent configuration takes effect.

·     You do not need to execute this command on a QinQ network.

Examples

# Specify the primary IP address of VLAN-interface 30 as the source address for WS-Discovery packets in VLAN 10.

<Sysname> system-view

[Sysname] vlan 10

[Sysname-vlan10] ws-discovery gateway source-ip interface vlan-interface 30

Related commands

display ws-discovery gateway

ws-discovery gateway enable

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Intelligent Storage
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
  • Technical Blogs
All Support
  • Become A Partner
  • Partner Policy & Program
  • Global Learning
  • Partner Sales Resources
  • Partner Business Management
  • Service Business
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网