On question QID:AN791

I believe the answer is not listed and should be:

"Configure the switchport trunk add vlan 300 on interface Fa0/2 on SW1"

The test states that it is just "switchport trunk allowed vlan 300"  but if you entered that CLI it would remove the existing trunk allowed vlans and only use vlan 300 rather than adding the vlan 300 to the existing trunk which is what you need.

The "add vlan 300 to interface Fa0/2 on SW1 is not even an option for an answer.

Passed, questions are good. Labs are good too but still got some wrong even with the right stuff from here. I studied them with CML and still could not get all of them working yet must have scored good enough on them and the questions to pass.

Thanks H2P

I think there's an issue with the answer of this question. The answer is listed as OSPF and BGP, but I believe the answer is LDP and RSVP.

The two protocols used by P routers to transfer VPN traffic between PE routers in an MPLS network are:
LDP (Label Distribution Protocol)
RSVP (Resource Reservation Protocol)

Explanation:

LDP is a protocol used in MPLS networks to distribute labels between adjacent label switch routers (LSRs). It allows P routers to assign and exchange MPLS labels for forwarding labeled packets along the Label Switched Path (LSP).
RSVP is a signaling protocol used in MPLS Traffic Engineering (MPLS-TE) to establish and maintain LSPs with specific bandwidth and quality of service (QoS) requirements. RSVP is used to reserve network resources along the LSP path.
The other options mentioned:

BGP (Border Gateway Protocol) is used for exchanging routing information between autonomous systems (AS) but not for transferring VPN traffic within an MPLS network.
OSPF (Open Shortest Path First) is an interior gateway protocol (IGP) used for routing within an AS but not for transferring VPN traffic in an MPLS network.
MP-BGP (Multiprotocol BGP) is used by PE routers to exchange VPN routing information and MPLS labels between VPN instances, but it is not used by P routers for transferring VPN traffic.


Please someone let me know if my understanding is not correct. Thanks!

The answer should be Monitor not Local

is 172.16.1.3 an FTP server?  Or is it supposed to be the TACACS Server?

It appears the exhibit forgot to name the route-maps.

the route-map is named 'deny'  

the second route-map is named 'permit'

neither route-map contains a permit or deny clause.  GNS3 shows that Route-maps can be configured without a permit or deny clause.  Configuring a route-map this way results in an implicit permit.

The exhibit is either wrong, or the answers are wrong.

If we assume the route-maps are intended to be named 'deny' and 'permit' we do not know which route map is applied.




!!! Route-map named 'deny' with no permit/deny clause defaults to permit
R4(config)#route-map ?
  WORD  Route map tag

R4(config)#route-map deny ?
  <0-65535>  Sequence to insert to/delete from existing route-map entry
  deny      Route map denies set operations
  permit    Route map permits set operations
  <cr>

R4(config)#route-map deny 10
R4(config-route-map)#match address 10
R4(config-route-map)#do sh route-map
route-map deny, permit, sequence 10
  Match clauses:
    ip address (access-lists): 10
  Set clauses:
  Policy routing matches: 0 packets, 0 bytes

!!! route-map named 'deny' with a deny clause denies any match.

R5(config)#route-map deny deny 10
R5(config-route-map)#match address 10
R5(config-route-map)#do sh route-map
route-map deny, deny, sequence 10
  Match clauses:
    ip address (access-lists): 10
  Set clauses:
  Policy routing matches: 0 packets, 0 bytes

Line 30 of ACL is wrong.  Should be host 2001:abc:20:2:2::2
or the answer is to remove line 70 from the acl

Default-information originate can only be configured under ospfv3 ipv6 address-gamily instance.

R1(config)#ipv6 unicast-routing
R1(config)#router ospfv3 1

R1(config-router)#default?
default

R1(config-router)#address-family ipv6 unicast
R1(config-router-af)#default?
default  default-information  default-metric

R1(config-router-af)#default-information ?
  originate  Distribute default route

There is no need for a flow exporter on R1.  The problem is that the netflow collector cannot receive flows from R1.

only making changes to R3, the secondary link is not the correct choice.

R1 Flow exporter shows the traffic destined to 10.60.66.66 port 1090, the actual IP address of the collector is 10.66.66.66.  This needs to be corrected.

The other problem is that R4 is the primary link and has an ACL blocking udp 1090.

there is a debug log shown in the exhibit not an syslog.

It would make more sense, to configure "service timestamps debug datetime localtime msec"