# Hello padding

Load **isis.cfg**

```
#IOS-XE
config replace flash:isis.cfg

#IOS-XR
configure
load bootflash:isis.cfg
commit replace
y
```

Configure R1 and XR2 so that Hellos are only padded the first six times.

## Answer <a href="#id-1c3ce97f-865b-417f-914e-85500f6b4222" id="id-1c3ce97f-865b-417f-914e-85500f6b4222"></a>

```
#R1
int Gi2.12
 no isis hello padding

! or

router isis
 no hello padding [multi-point|point-to-point]

#XR2
router isis 1
 int Gi0/0/0/0.1920
  hello-padding sometimes [level 2]
```

## Explanation <a href="#id-1b38dde3-d4d1-80ff-81b2-ebff19a2a6b8" id="id-1b38dde3-d4d1-80ff-81b2-ebff19a2a6b8"></a>

By default, the router will always pad Hellos. This can be considered an unnecessary waste of bandwidth, as once you’ve verified MTU via the padded Hellos, you no longer really need to continue to pad Hellos.

When using the above configuration, the router will only pad the first 6 Hellos. After this, all subsequent Hellos are not padded, which saves some bandwidth.

If for some reason you wanted to never pad Hellos, not even at the beginning of the adjacency, you can use **no isis hello padding always** under the interface on IOS-XE, or **hello-padding disable** on IOS-XR. This is similar to OSPF’s **ip ospf mtu-ignore** setting.

Verfiy that R1 is not padding Hellos on Gi2.12:

<div align="left"><figure><img src="/files/x78pIiJaIbY44ERAon3M" alt=""><figcaption></figcaption></figure></div>

When you use **no isis hello padding always**, you will instead see “Never pad hello PDU”:

<div align="left"><figure><img src="/files/a6FTp8ILjUpCxIzIYB42" alt=""><figcaption></figcaption></figure></div>

I cannot find an equivalent way to verify on IOS-XR.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ccie-sp.gitbook.io/ccie-spv5.1-labs/labs/isis/hello-padding.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.