What is the default BGP group type on a Junos device?
A. internal
B. external
C. multihop
D. null
8 Comments on “What is the default BGP group type on a Junos device?”
Samsays:
Hi
i am not happy with this answer as i haven’t read it anywhere i believe it should be D as there is no default group. anyone can comment on this
0
0
Debsays:
By default BGP is made for External routing. So B is correct.
0
0
Samsays:
saying that by default BGP made for external a bit hard to accept, did you read it somewhere let me know please
0
0
Felixsays:
I configured a Juniper router for BGP without adding the type in the bgp group config.
See the output I got from the Juniper router.
[edit protocols]
‘bgp’
Error in neighbor 10.5.4.1 of group test:
peer AS number must be configured for an external peer
error: configuration check-out failed
It requires by default and external peer as the output implied. I will definitely go with B.
2
0
Felixsays:
Also left out the “peer AS” config obviously. 🙂
0
0
Kaansays:
when you configure bgp on a junos device, you have to specify the local and the remote AS. When you dont specify the remote-as, the device is asking you to specify the “external-peer”. so from that point, i would agree on B
2
0
newtojunipersays:
depends on peer-as and autonomous-system number…
if same peer-as and autonomous-system number = internal
if different = external
so the answer should be null
1
1
Tomsays:
(
…You specify an external session type for EBGP and an internal session type for IBGP. If you omit the session type, you must specify the perr-as number, which can be a remote AS number or the local AS number. If the specified AS number does not match the AS number defined on the router, BGP assumes the session type is external. If the specified AS number does match the AS number defined on the router, BGP assumes the session type is internal. The software notifies you if you did not include the required details, as shown in the following sample output:
[edit protocols bgp]
user@R1# show
group x100 {
neighbor 10.1.1.1;
}
[edit protocols bgp]
user@R1# commit
[edit protocols]
‘bgp’
Error in neighbor 10.1.1.1 of group x100:
peer AS number must be configured for an external peer
error: configuration check-out failed
)
Based on this, you either specify external or internal, or specify the AS peer, which dictates external or internal. Failure to define either the session type or AS peer is not allowed, therefore there should not be a default. I guess null would make most sense then, right?
Hi
i am not happy with this answer as i haven’t read it anywhere i believe it should be D as there is no default group. anyone can comment on this
0
0
By default BGP is made for External routing. So B is correct.
0
0
saying that by default BGP made for external a bit hard to accept, did you read it somewhere let me know please
0
0
I configured a Juniper router for BGP without adding the type in the bgp group config.
See the output I got from the Juniper router.
[edit protocols]
‘bgp’
Error in neighbor 10.5.4.1 of group test:
peer AS number must be configured for an external peer
error: configuration check-out failed
It requires by default and external peer as the output implied. I will definitely go with B.
2
0
Also left out the “peer AS” config obviously. 🙂
0
0
when you configure bgp on a junos device, you have to specify the local and the remote AS. When you dont specify the remote-as, the device is asking you to specify the “external-peer”. so from that point, i would agree on B
2
0
depends on peer-as and autonomous-system number…
if same peer-as and autonomous-system number = internal
if different = external
so the answer should be null
1
1
(
…You specify an external session type for EBGP and an internal session type for IBGP. If you omit the session type, you must specify the perr-as number, which can be a remote AS number or the local AS number. If the specified AS number does not match the AS number defined on the router, BGP assumes the session type is external. If the specified AS number does match the AS number defined on the router, BGP assumes the session type is internal. The software notifies you if you did not include the required details, as shown in the following sample output:
[edit protocols bgp]
user@R1# show
group x100 {
neighbor 10.1.1.1;
}
[edit protocols bgp]
user@R1# commit
[edit protocols]
‘bgp’
Error in neighbor 10.1.1.1 of group x100:
peer AS number must be configured for an external peer
error: configuration check-out failed
)
Based on this, you either specify external or internal, or specify the AS peer, which dictates external or internal. Failure to define either the session type or AS peer is not allowed, therefore there should not be a default. I guess null would make most sense then, right?
3
0