Binding a Service Board to a NAT Instance

Only after a NAT instance is created and bound to a NAT service board, a device can direct packets to the NAT service board and run NAT to process the packets.

Context

A service-instance-group is bound to a service-location group. A NAT instance is bound to the service-instance group. The bindings enable a NAT service board to process NAT services.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run service-location service-location-id

    A service-location group is created, and the service-location group view is displayed.

  3. Run location slot slot-id

    A NAT service board is bound to the service-location group.

  4. Run commit

    The configuration is committed.

  5. Run quit

    Return to the system view.

  6. Run service-instance-group service-instance-group-name

    A service-instance group is created, and the service-instance group view is displayed.

  7. Run service-location service-location-id

    The service-instance group is bound to the service-location group.

  8. Run commit

    The configuration is committed.

  9. Run quit

    Return to the system view.

  10. Run nat instance instance-name [ id id ]

    The NAT instance view is displayed.

  11. Run service-instance-group service-instance-group-name

    The NAT instance is bound to the service-instance group.

  12. Run commit

    The configuration is committed.

    • Only one location command can be configured in a service-location group.

    • Note that one NAT instance can be bound to only one service-instance group.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
Next topic >