Training and Certification

Greetings Ricardo,

I am trying to better understand your question/issue. I looked at the configurations on the devices I have in the self study bundle and I am not sure which chapter or super lab you are referring to. I can see that there is some RIP configurations on the VR2 device for CE2-1 and DC2 in the super lab 1 device configurations, however I don't see any peerings to DC2 for super lab 1. 

For the IGP chapter I do not see any use of the protocol RIP. I do see a policy that included RIP in one of the match criteria, but I think that is leftover from some other configuration in the past and is not even evaluated since there are no RIP routes.

For super lab 2, I do see that in the logical diagram it shows DC-1 connected into the network using RIP, however it is not in the physical diagram or configuration on the core network devices and must have been removed from the lab exercises. I do see configuration on the VR2 device but I don't think they are used.

The VR devices serve as many of the external devices and sometimes the configuration are there but are not used depending on the actual requirements of the labs. Instead of building everything from scratch, we reuse the same configurations with the appropriate modification to accommodate the connections and tasks of the lab and just leave the non-relevant stuff there since there is no impact on the actual functionality of the environment.

Is something not working as expected in regards to the tasks of the labs?

Please clarify the issue for me and I will investigate further as needed.

Hi Josh,

I'm referring to the IGP section where routes from DC2 (a different domain) need to be injected and manipulated into either OSPF or IS-IS. The task description indicates that these routes are learned via BGP, and the verification examples are shown accordingly.

However, when looking at the VR-2 configuration, the DC2 instance is configured to advertise its routes via RIP rather than BGP as described in the workbook. While the end result is the same, it would be helpful if the workbook and lab configuration were consistent in this regard, as it would save students time when working through these scenarios and troubleshooting discrepancies.

Greetings Ricardo,

I am trying to better understand your question/issue. I looked at the configurations on the devices I have in the self study bundle and I am not sure which chapter or super lab you are referring to. I can see that there is some RIP configurations on the VR2 device for CE2-1 and DC2 in the super lab 1 device configurations, however I don't see any peerings to DC2 for super lab 1. 

For the IGP chapter I do not see any use of the protocol RIP. I do see a policy that included RIP in one of the match criteria, but I think that is leftover from some other configuration in the past and is not even evaluated since there are no RIP routes.

For super lab 2, I do see that in the logical diagram it shows DC-1 connected into the network using RIP, however it is not in the physical diagram or configuration on the core network devices and must have been removed from the lab exercises. I do see configuration on the VR2 device but I don't think they are used.

The VR devices serve as many of the external devices and sometimes the configuration are there but are not used depending on the actual requirements of the labs. Instead of building everything from scratch, we reuse the same configurations with the appropriate modification to accommodate the connections and tasks of the lab and just leave the non-relevant stuff there since there is no impact on the actual functionality of the environment.

Is something not working as expected in regards to the tasks of the labs?

Please clarify the issue for me and I will investigate further as needed.

Hi Josh,

I'm referring to the IGP section where routes from DC2 (a different domain) need to be injected and manipulated into either OSPF or IS-IS. The task description indicates that these routes are learned via BGP, and the verification examples are shown accordingly.

However, when looking at the VR-2 configuration, the DC2 instance is configured to advertise its routes via RIP rather than BGP as described in the workbook. While the end result is the same, it would be helpful if the workbook and lab configuration were consistent in this regard, as it would save students time when working through these scenarios and troubleshooting discrepancies.

Greetings Ricardo,

I am trying to better understand your question/issue. I looked at the configurations on the devices I have in the self study bundle and I am not sure which chapter or super lab you are referring to. I can see that there is some RIP configurations on the VR2 device for CE2-1 and DC2 in the super lab 1 device configurations, however I don't see any peerings to DC2 for super lab 1. 

For the IGP chapter I do not see any use of the protocol RIP. I do see a policy that included RIP in one of the match criteria, but I think that is leftover from some other configuration in the past and is not even evaluated since there are no RIP routes.

For super lab 2, I do see that in the logical diagram it shows DC-1 connected into the network using RIP, however it is not in the physical diagram or configuration on the core network devices and must have been removed from the lab exercises. I do see configuration on the VR2 device but I don't think they are used.

The VR devices serve as many of the external devices and sometimes the configuration are there but are not used depending on the actual requirements of the labs. Instead of building everything from scratch, we reuse the same configurations with the appropriate modification to accommodate the connections and tasks of the lab and just leave the non-relevant stuff there since there is no impact on the actual functionality of the environment.

Is something not working as expected in regards to the tasks of the labs?

Please clarify the issue for me and I will investigate further as needed.

Ricardo,

Thanks for the additional details. I looked at the VR-2 devices configurations for the DC2 instance and I do not see where RIP is configured. Can you share the configuration(s) you are talking about?

[edit]
instructor@vr-device-2# show routing-instances DC2 
instance-type virtual-router;
protocols {
    bgp {
        group ebgp {
            export DC2-static-to-bgp;
            local-as 64666;
            multipath;
            neighbor 172.30.0.49 {
                peer-as 54591;
            }
            neighbor 172.30.0.57 {
                peer-as 54591;
            }
        }
    }
}
interface ge-0/0/0.202;
interface ge-0/0/0.204;
interface lo0.32;

According to this configuration the only protocol peering to the two neighbors in the core network is using EBGP.

Hi Josh,

I'm referring to the IGP section where routes from DC2 (a different domain) need to be injected and manipulated into either OSPF or IS-IS. The task description indicates that these routes are learned via BGP, and the verification examples are shown accordingly.

However, when looking at the VR-2 configuration, the DC2 instance is configured to advertise its routes via RIP rather than BGP as described in the workbook. While the end result is the same, it would be helpful if the workbook and lab configuration were consistent in this regard, as it would save students time when working through these scenarios and troubleshooting discrepancies.

Greetings Ricardo,

I am trying to better understand your question/issue. I looked at the configurations on the devices I have in the self study bundle and I am not sure which chapter or super lab you are referring to. I can see that there is some RIP configurations on the VR2 device for CE2-1 and DC2 in the super lab 1 device configurations, however I don't see any peerings to DC2 for super lab 1. 

For the IGP chapter I do not see any use of the protocol RIP. I do see a policy that included RIP in one of the match criteria, but I think that is leftover from some other configuration in the past and is not even evaluated since there are no RIP routes.

For super lab 2, I do see that in the logical diagram it shows DC-1 connected into the network using RIP, however it is not in the physical diagram or configuration on the core network devices and must have been removed from the lab exercises. I do see configuration on the VR2 device but I don't think they are used.

The VR devices serve as many of the external devices and sometimes the configuration are there but are not used depending on the actual requirements of the labs. Instead of building everything from scratch, we reuse the same configurations with the appropriate modification to accommodate the connections and tasks of the lab and just leave the non-relevant stuff there since there is no impact on the actual functionality of the environment.

Is something not working as expected in regards to the tasks of the labs?

Please clarify the issue for me and I will investigate further as needed.